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
Date:	Mon, 13 Oct 2003 23:25:04 -0400
From:	Christopher Faylor <cgf-rcm AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: merging mingw and cygwin
Message-ID:	<20031014032504.GC31727@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
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> <Pine DOT GSO DOT 4 DOT 56 DOT 0310131745230 DOT 791 AT eos>
Mime-Version:	1.0
In-Reply-To:	<Pine.GSO.4.56.0310131745230.791@eos>
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.

AFAIK, mingw doesn't coordinate releases either.

cgf

--
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/

- Raw text -