Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Thu, 2 May 2002 19:13:00 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: MD5 support Message-ID: <20020502231300.GA29858@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Fri, May 03, 2002 at 08:44:01AM +1000, Robert Collins wrote: > > >> -----Original Message----- >> From: Christopher Faylor [mailto:cgf AT redhat DOT com] >> Sent: Friday, May 03, 2002 2:55 AM > >> >Thank you. Is it ok with you if I call it setup.ini and put >> it in a dir >> >called test after inserting ../ in front of every instance of >> >'release/'? >> >> I guess so. I wonder if it would make sense to have a >> completely separate test site for this kind of thing so as >> not to have the mirrors update testing stuff and, more >> importantly, so that we can make changes in real time. > >If you've got the bandwidth and disk space... cool. I figured that a >single copy of setup.ini getting mirrored was a low-cost solution (vs a >completely separate site). By "site" I meant something besides sources.redhat.com that wouldn't rely on accessing a mirror site to be useful. cgf