Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Mon, 13 Oct 2003 17:48:47 -0500 (CDT) From: Brian Ford X-X-Sender: ford@eos To: cygwin@cygwin.com Subject: Re: merging mingw and cygwin In-Reply-To: <20031013223537.GA26012@mdssirds.comp.pge.com> Message-ID: References: <20031013220827.13993.qmail@web21405.mail.yahoo.com> <20031013223537.GA26012@mdssirds.comp.pge.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 13 Oct 2003, Edward Peschko wrote: > And anyways, the version numbers in itself are enough to warrant a > merge. Coordinate releases of mingw and cygwin, and the version issues > go away. > Cygwin itself doesn't "coordinate releases". By that I mean Cygwin, w32api, gcc, mingw gcc, etc. are never release together as a package. Each is updated on its own schedule. If you want a "distribution", and it has been discussed before (see the archives), start your own. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/