public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: On Linux numbering scheme
Date: Fri, 22 Oct 2010 13:36:10 -0400	[thread overview]
Message-ID: <i9si2a$gcv$1@dough.gmane.org> (raw)
In-Reply-To: <20101022095333.GA10047@fysh.org>

Athanasius wrote:
> On Fri, Oct 22, 2010 at 03:00:06AM +0100, Al Viro wrote:
>> On Thu, Oct 21, 2010 at 07:06:23PM -0500, kevin granade wrote:
>>
>>> Any particular reason not to continue the date-oriented format and
>>> have the third number be the numerical representation of the month
>>> rather than an incrementing numbering of the releases?  It would still
>>> be monotonically increasing, which is the only requirement, right?
>>
>> Why do we need to change it, anyway?
>
>    /agree
>
>    For the most part it's only distribution maintainers that see or care
> about the kernel version number anyway.  Anyone else knows what they're
> getting into if they compile a kernel themselves, and otherwise is more
> likely to say they're using "Linux 10.10" right now ....
>
>    Having said that I had a lovely suggestion in the last round on this
> topic which would allow you to know when a kernel was released just from
> its version number :).
>
I thought the odd/even numbering used to 2.5.xx was fine, and I think having the 
numbering reflect feature set (as it more or less does now) is better than any 
scheme based on date.

That said, this topic will be decided by the vote of the electorate, from a 
voter pool of one (Linus). Unless he has changed his mind this is all moot anyway.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


  reply	other threads:[~2010-10-22 17:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18536664.253751287691209904.JavaMail.root@mail-zbox20.bo3.lycos.com>
2010-10-21 20:02 ` On Linux numbering scheme Artem S. Tashkinov
2010-10-22  0:06   ` kevin granade
2010-10-22  2:00     ` Al Viro
2010-10-22  9:53       ` Athanasius
2010-10-22 17:36         ` Bill Davidsen [this message]
2010-10-22 21:57       ` Jeremy Fitzhardinge
2010-10-25  9:08       ` Tejun Heo
2010-10-25  9:45         ` Artem S. Tashkinov
2010-10-25  9:56           ` Tejun Heo
2010-10-25 10:04           ` Bernd Petrovitsch
2010-10-25 20:30           ` Nick Bowler
2010-10-26 10:24             ` Dick Streefland
2010-10-26 10:50               ` Martin Nybo Andersen
2011-01-06  8:31   ` Claudio Scordino
2011-01-06  8:59     ` Geert Uytterhoeven
2011-01-08 14:49       ` Artem S. Tashkinov
2011-01-08 16:11         ` Greg KH
2011-01-09 12:54           ` Mark Hounschell
     [not found] <5600814.270321287742009359.JavaMail.root@mail-zbox20.bo3.lycos.com>
2010-10-22 10:33 ` Artem S. Tashkinov
2010-10-22 10:41   ` Alexey Dobriyan
2010-10-22 11:18     ` Artem S. Tashkinov
2010-10-22 13:25     ` Genes MailLists
2010-10-22 16:51       ` kevin granade
     [not found] <18673709.2121294505029740.JavaMail.root@mail-zbox20.bo3.lycos.com>
2011-01-08 16:45 ` Artem S. Tashkinov
2011-01-08 18:31   ` Greg KH
2011-01-09 17:38   ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='i9si2a$gcv$1@dough.gmane.org' \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox