Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 13 Sep 2001 13:29:46 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: frivolous naming suggestion Message-ID: <20010913132946.A13823@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20010913160206 DOT 12047 DOT qmail AT web20006 DOT mail DOT yahoo DOT com> <001601c13c6e$befa5330$391e10ac AT dmonknt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001601c13c6e$befa5330$391e10ac@dmonknt> User-Agent: Mutt/1.3.21i On Thu, Sep 13, 2001 at 11:11:28AM -0500, David Monk wrote: >>My suggestion is, how about giving the cygwin dll releases nicknames >>for either rush songs ("Tom Sawyer", "Hold Your Fire") or stars >>("Polaris", "Sirius"). I'm not sure anyone is having trouble with >>keeping 1.3.1 and 1.3.3 apart, but if so this might help. And, it >>would give something for people to put in /etc/issue if they wanted. >>:) > >If the releases were to begin receiving codenames, similar to how Linux >systems do, it would be nice to follow suit and store the information >in a common file and format, such as /etc/cygwin-release. This would >be right along the lines of RedHat's /etc/redhat-release. The Cygwin net release process is more related to Linus's release of kernels than to Red Hat's release of commercial packages. AFAIK, Linus does not code name his releases. Since Red Hat does not really release a commercial product called "Cygwin", I think that the analogy doesn't really holds up. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/