From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13479 invoked by alias); 8 Apr 2008 21:39:41 -0000 Received: (qmail 13469 invoked by uid 22791); 8 Apr 2008 21:39:40 -0000 X-Spam-Check-By: sourceware.org Received: from pool-72-74-94-32.bstnma.fios.verizon.net (HELO ednor.cgf.cx) (72.74.94.32) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 08 Apr 2008 21:39:23 +0000 Received: by ednor.cgf.cx (Postfix, from userid 201) id 9078B6085F8; Tue, 8 Apr 2008 17:39:21 -0400 (EDT) Date: Tue, 08 Apr 2008 21:39:00 -0000 From: Christopher Faylor To: cygwin-apps@cygwin.com Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Message-ID: <20080408213921.GA728@ednor.casa.cgf.cx> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <20080402123551.GB4468@calimero.vinschen.de> <20080404004949.GA10978@ednor.casa.cgf.cx> <20080404121534.GB3606@calimero.vinschen.de> <20080408162646.GC23852@calimero.vinschen.de> <20080408172646.GA2089@ednor.casa.cgf.cx> <20080408174013.GD23852@calimero.vinschen.de> <20080408184148.GA2448@ednor.casa.cgf.cx> <20080408210726.GA7867@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080408210726.GA7867@calimero.vinschen.de> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-04/txt/msg00096.txt.bz2 On Tue, Apr 08, 2008 at 11:07:26PM +0200, Corinna Vinschen wrote: >On Apr 8 14:41, Christopher Faylor wrote: >> On Tue, Apr 08, 2008 at 07:40:13PM +0200, Corinna Vinschen wrote: >> >On Apr 8 13:26, Christopher Faylor wrote: >> >> cygwin-xp? cygwin-2008? >> > >> >cysta? :) >> > >> >cygwin-2008 isn't bad, though. >> > >> >> cygwin-nextgen? >> > >> >Or just cygwin-new, maybe. I'd take any of them, -new or -2008. >> >> In my experience, adding a "new" to any directory or file is a >> guaranteed way of ensuring that the name will not always be accurate. > >Why, we could always name the next versions "cygwin-newer", >"cygwin-evenmorenew", "cygwin-newerthannew" and >"cygwin-reallyreallynew-imeanit". > >> How about cygwinng? > >With a dash? cygwin-ng? Like syslog-ng. I was going to suggest this >too, but I didn't want to copy the naming too bluntly. We actually use "ng" internally to Netapp. I actually wanted to call my project either "ds9" or "voyager" but I got vetoed. >I guess we should use "cygwin-notasnewbutstillnewenough". I'm still >more leaning towards cygwin-2008. You shouldn't have suggested the >name. It's all your fault. I hate the name! Hate it! But I don't really care. cygwin-2008 is fine with me. However, I predict that cgf-2012 will probably be grumbling about that name eventually. cgf