From: Harald Arnesen <skogtun.harald@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Kernel version numbering scheme change
Date: Thu, 16 Oct 2008 21:14:39 +0200 [thread overview]
Message-ID: <87ej2g5p40.fsf@basilikum.skogtun.org> (raw)
In-Reply-To: <20081016153512.GE12962@mit.edu> (Theodore Tso's message of "Thu, 16 Oct 2008 11:35:12 -0400")
Theodore Tso <tytso@mit.edu> writes:
> On Thu, Oct 16, 2008 at 04:26:19PM +0200, markus reichelt wrote:
>> Why not just keep it? It has worked so far, and from a strictly
>> end-user point of view I cannot see any advantages at all with a new
>> scheme. The ideas mentioned so far don't cut it either.
>
> I'd cast a vote for keeping it as well. "2.6" is actually a great
> marker so that people know that it's highly likely the version number
> is for the Linux kernel. Contrast "I'm running 2.6.27" versus "I'm
> running 27" (huh, what does that mean?) or "I'm running the 27 kernel"
> or "I'm running Linux kernel version 27" or worse yet "I'm running
> 2008-03". Something like "2.6.27" is just easier to say, and less
> prone to misunderstanding/confusion.
>
> Let's just leave things the way they are.
My suggestion: When 2.6.28 is released, rename it to 2.8 (or 2.8.0).
The next one will be 2.9, then 2.10 and so on. Today's 2.6.x.y will be
2.8.y.
It should minimise breakage of userspace programs.
Or wait til 2.6.30, and rename that to 3.0.
--
Hilsen Harald.
next prev parent reply other threads:[~2008-10-16 19:14 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 0:25 Greg KH
2008-10-16 1:03 ` H. Peter Anvin
2008-10-16 1:51 ` David Sanders
2008-10-16 2:18 ` Greg KH
2008-10-16 7:02 ` Thorsten Leemhuis
2008-10-16 7:34 ` david
2008-10-18 21:44 ` Jan Engelhardt
2008-10-19 1:52 ` david
2008-10-19 2:44 ` Jan Engelhardt
2008-10-16 8:21 ` el es
2008-10-16 9:09 ` H. Peter Anvin
2008-10-16 9:33 ` el es
2008-10-16 10:05 ` el es
2008-10-16 10:14 ` Kristoffer Ericson
2008-10-16 17:30 ` david
2008-10-16 9:15 ` Hans J. Koch
2008-10-16 15:21 ` Geert Uytterhoeven
2008-10-18 21:56 ` Jan Engelhardt
2008-10-16 12:49 ` Adrian Bunk
2008-10-16 15:17 ` Greg KH
2008-10-16 15:30 ` Bill Nottingham
2008-10-16 15:47 ` Greg KH
2008-10-16 17:16 ` Adrian Bunk
2008-10-17 4:02 ` Greg KH
2008-10-17 4:26 ` Grant Coady
2008-10-17 4:53 ` Randy Dunlap
2008-10-17 9:31 ` Alan Cox
2008-10-17 16:40 ` H. Peter Anvin
2008-10-17 17:42 ` Greg KH
2008-10-18 7:18 ` H. Peter Anvin
2008-10-18 7:38 ` 2.6.28-rc1 --> 2.8.0-rc1; 2.6.27.y --> 2.6.28 [Re: [RFC] Kernel version numbering scheme change] Dominik Brodowski
2008-10-18 7:47 ` Mikael Abrahamsson
2008-10-20 3:48 ` [RFC] Kernel version numbering scheme change Alexandre Oliva
2008-10-20 5:29 ` H. Peter Anvin
2008-10-20 7:13 ` Alexandre Oliva
2008-10-20 18:55 ` Alex Howells
2008-10-20 20:21 ` Greg KH
2008-10-21 19:52 ` Alex Howells
2008-10-22 0:41 ` Valdis.Kletnieks
2008-10-22 4:15 ` Grant Coady
2008-10-22 8:58 ` Alex Howells
2008-10-22 9:11 ` Alan Cox
2008-10-22 18:11 ` Stefan Richter
2008-10-21 18:54 ` Stefan Richter
2008-10-17 17:41 ` Greg KH
2008-10-17 19:45 ` Alan Cox
2008-10-17 21:42 ` Greg KH
2008-10-16 16:46 ` Adrian Bunk
2008-10-17 3:47 ` Greg KH
2008-10-17 6:47 ` Adrian Bunk
2008-10-17 7:55 ` Greg KH
2008-10-17 8:16 ` Steven Noonan
2008-10-17 17:46 ` Greg KH
2008-10-17 19:06 ` Bartlomiej Zolnierkiewicz
2008-10-17 21:44 ` Greg KH
2008-10-17 19:47 ` Alan Cox
2008-10-17 21:44 ` Greg KH
2008-10-17 22:14 ` Matthias Schniedermeyer
2008-10-17 22:49 ` Rafael J. Wysocki
2008-10-18 1:23 ` david
2008-10-18 23:14 ` Jiri Kosina
2008-10-19 1:50 ` david
2008-10-19 12:51 ` Rafael J. Wysocki
2008-10-19 16:29 ` david
2008-10-19 17:45 ` Rafael J. Wysocki
2008-10-19 17:47 ` david
2008-10-19 17:57 ` Rafael J. Wysocki
2008-10-18 8:45 ` Willy Tarreau
2008-10-18 23:17 ` Jiri Kosina
2008-10-19 3:35 ` Willy Tarreau
2008-10-20 20:30 ` Greg KH
2008-10-20 20:54 ` Felipe Balbi
2008-10-20 21:06 ` Greg KH
2008-10-20 21:58 ` Arnd Bergmann
2008-10-20 22:24 ` Felipe Balbi
2008-10-21 19:11 ` Stefan Richter
2008-10-21 19:16 ` Felipe Balbi
2008-10-18 22:33 ` Jan Engelhardt
2008-10-19 18:33 ` Greg KH
2008-10-19 19:51 ` Jan Engelhardt
2008-10-19 23:40 ` david
2008-10-18 22:38 ` Jan Engelhardt
2008-10-18 1:20 ` david
2008-10-18 8:32 ` Willy Tarreau
2008-10-17 8:56 ` Adrian Bunk
2008-10-17 10:06 ` Peter Zijlstra
2008-10-17 11:18 ` Alexey Dobriyan
2008-10-17 11:26 ` Peter Zijlstra
2008-10-17 11:32 ` Alexey Dobriyan
2008-10-17 15:30 ` Chris Friesen
2008-10-17 17:45 ` Greg KH
2008-10-18 9:01 ` Willy Tarreau
2008-10-18 10:04 ` Adrian Bunk
2008-10-18 11:08 ` Willy Tarreau
2008-10-18 11:50 ` Adrian Bunk
2008-10-18 12:28 ` Willy Tarreau
2008-10-18 13:48 ` Adrian Bunk
2008-10-18 14:13 ` Willy Tarreau
2008-10-16 14:26 ` markus reichelt
2008-10-16 15:35 ` Theodore Tso
2008-10-16 18:05 ` John Stoffel
2008-10-16 19:14 ` Harald Arnesen [this message]
2008-10-17 1:53 ` Dave Young
2008-10-17 9:05 ` Jike Song
2008-10-17 9:14 ` Dave Young
2008-10-20 3:49 ` Daniel Phillips
2008-10-16 15:18 ` Geert Uytterhoeven
2008-10-17 1:26 ` Rob Landley
2008-10-17 12:46 ` Giacomo A. Catenazzi
2008-10-17 17:40 ` Greg KH
2008-10-18 1:32 ` david
2008-10-16 2:10 H. Peter Anvin
2008-10-20 6:05 Denys Fedoryshchenko
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=87ej2g5p40.fsf@basilikum.skogtun.org \
--to=skogtun.harald@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
Powered by JetHome