Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT 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 <ford AT vss DOT fsi DOT com>
X-X-Sender: ford AT eos
To: cygwin AT cygwin DOT com
Subject: Re: merging mingw and cygwin
In-Reply-To: <20031013223537.GA26012@mdssirds.comp.pge.com>
Message-ID: <Pine.GSO.4.56.0310131745230.791@eos>
References: <20031013220827 DOT 13993 DOT qmail AT web21405 DOT mail DOT yahoo DOT com>
 <20031013223537 DOT GA26012 AT mdssirds DOT comp DOT pge DOT 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/