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: mdssirds.comp.pge.com: esp5 set sender to esp5@pge.com using -f Date: Mon, 13 Oct 2003 16:44:42 -0700 From: Edward Peschko To: Brian Ford Cc: cygwin@cygwin.com Subject: Re: merging mingw and cygwin Message-ID: <20031013234442.GC26012@mdssirds.comp.pge.com> 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 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Mon, Oct 13, 2003 at 05:48:47PM -0500, Brian Ford wrote: > 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. and compound the problem by making 3 distinct distributions instead of two? That isn't solving anything at all. Ed -- 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/