Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Mon, 13 Oct 2003 23:25:04 -0400
From: Christopher Faylor <cgf-rcm@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: merging mingw and cygwin
Message-ID: <20031014032504.GC31727@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20031013220827.13993.qmail@web21405.mail.yahoo.com> <20031013223537.GA26012@mdssirds.comp.pge.com> <Pine.GSO.4.56.0310131745230.791@eos>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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/

