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 Subject: RE: ready to push setup.exe to release MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 12 May 2002 02:00:54 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Gary R. Van Sickle" , "Cygwin-Apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4BG1A317479 > -----Original Message----- > From: Gary R. Van Sickle [mailto:g DOT r DOT vansickle AT worldnet DOT att DOT net] > Sent: Sunday, May 12, 2002 1:53 AM > To: Cygwin-Apps > Subject: RE: ready to push setup.exe to release > > > > Any objections to making the latest snapshot a release? > > > > None here if the latest snapshot == current cvs. Latest snapshot == cvs tag setup-200205. Head is a little more unstable with all the refactoring going on. > > The only remaining bug is the XP Pro hang that Mark is > experiencing, > > and if / when we find out how to reproduce it I'll fix it on the > > branch. > > ? Do you mean Ronald Anderssen/"Is cygwin setup.exe really > compatible to WinXP Pro ?"? I'm on XP here and I haven't > seen the problem he's seeing FWIW. Ronald appeared to be running the pre-MD5 stack fixed setup, it's likely just crashing on him. Rob