Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 34771 invoked from network); 20 Mar 2004 20:16:29 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Mar 2004 20:16:29 -0000 Received: (qmail 5119 invoked by uid 500); 20 Mar 2004 20:16:19 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 5082 invoked by uid 500); 20 Mar 2004 20:16:18 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: repository@apache.org Delivered-To: mailing list repository@apache.org Received: (qmail 5069 invoked from network); 20 Mar 2004 20:16:18 -0000 Received: from unknown (HELO latte.harvard.edu) (140.247.210.252) by daedalus.apache.org with SMTP; 20 Mar 2004 20:16:18 -0000 Received: from latte.harvard.edu (207-172-79-45.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com [::ffff:207.172.79.45]) (AUTH: PLAIN mdiggory, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by latte.harvard.edu with esmtp; Sat, 20 Mar 2004 15:16:21 -0500 Message-ID: <405CA821.4080406@latte.harvard.edu> Date: Sat, 20 Mar 2004 15:22:57 -0500 From: "Mark R. Diggory" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7a) Gecko/20040219 X-Accept-Language: en-us, en, zh, zh-cn, zh-hk, zh-sg, zh-tw MIME-Version: 1.0 To: repository@apache.org Subject: Re: Avalon currently is not a paradise! References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Thnx, I would like to see where discussion goes first. The duplication has been there for some time, resolving it immediately is not high on my list. Making any significant changes has to be well thought out in directories that are mirrored. Establishing a path of convergence for the contents is at the top of my list concerning this issue. -M. Noel J. Bergman wrote: >>While that is a possible solution, it creates alot of maintence issues >>and isn't very scalable. I think there could be a cleaner solution if >>both parties got involved with making adjustments. > > > Understood. Just trying to propose something that can be done immediately, > while the adjustments are discussed. > > --- Noel > -- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu