X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Gary R. Van Sickle" <g DOT r DOT vansickle AT att DOT net>
To: <cygwin AT cygwin DOT com>
References: <20081210203400 DOT GA15192 AT calimero DOT vinschen DOT de> <494061C2 DOT 9070306 AT etr-usa DOT com> <20081211025042 DOT GA3571 AT ednor DOT casa DOT cgf DOT cx> <494092AE DOT 6060902 AT etr-usa DOT com> <20081211091718 DOT GE15192 AT calimero DOT vinschen DOT de>
Subject: RE: Public Cygwin 1.7 test starts today
Date: Thu, 11 Dec 2008 03:59:00 -0600
Message-ID: <62E5192A6E10484E881E2E521557F533@DFW5RB41>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20081211091718.GE15192@calimero.vinschen.de>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

> From: Corinna Vinschen
[snip]
> > Do you have a sense for what would make the next major release 
> > cygwin2.dll and not cygwin1.dll?  Obviously an API or ABI breakage 
> > would require a new DLL name, but do you have something on the wish 
> > list that would require that, which was put off this time around?
> 
> Windows will run under Cygwin 2.0 instead of vice versa.
> 

Now THAT'S comedy! ;-)))

Well, unless you were serious, in which case it's still good comedy.

-- 
Gary R. Van Sickle


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