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: Wed, 1 May 2002 11:31:54 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: MD5 support Message-ID: <20020501153154.GL6736@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 Wed, May 01, 2002 at 06:42:46PM +1000, Robert Collins wrote: > > >> -----Original Message----- >> From: Christopher Faylor [mailto:cgf AT redhat DOT com] >> Sent: Wednesday, May 01, 2002 2:35 AM > >> I have upset ready to go for this. Will it actually break >> setup.exe if I check in my changes? I'm away from a Windows >> system right now so I can't check myself. > >It will cause parsing errors, so even though setup is (somewhat) >resilient, it will generate questions. > >If you could get upset to make a ini in a new location (perhaps test) >that refers to the release directory source files, that would be a great >test, and let me be sure that nothing will go ... wrong. Hmm. Dueling "you do the work" scenarios. Why not just release an interim version of setup that silently ignores the third field? That's what we've done in the past. cgf