Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268260AbUJVWph (ORCPT ); Fri, 22 Oct 2004 18:45:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268170AbUJVWpg (ORCPT ); Fri, 22 Oct 2004 18:45:36 -0400 Received: from linux01.gwdg.de ([134.76.13.21]:17309 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S268260AbUJVWok (ORCPT ); Fri, 22 Oct 2004 18:44:40 -0400 Date: Sat, 23 Oct 2004 00:44:33 +0200 (MEST) From: Jan Engelhardt To: Linus Torvalds cc: Kernel Mailing List Subject: Re: The naming wars continue... In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1149 Lines: 29 >Should it be "-rc1"? Or "-pre1" to show it's not really considered release >quality yet? Or should I make like a rocket scientist, and count _down_ >instead of up? Should I make names based on which day of the week the >release happened? Questions, questions.. > >And the fact is, I can't see the point. I'll just call it all "-rcX", >because I (very obviously) have no clue where the cut-over-point from >"pre" to "rc" is, or (even more painfully obviously) where it will become >the final next release. It's not only Linux which has this problem. For some of my own regularly updated "projects" (i.e. a collection of scripts) I use an always increasing number, preferably date, and do not care at all about -pre, -post, -beta, -rc, -etc. "2.6.10-27" (read: try #27)... sound funny. Jan Engelhardt -- Gesellschaft f?r Wissenschaftliche Datenverarbeitung Am Fassberg, 37077 G?ttingen, www.gwdg.de - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/