From: Claudio Scordino <claudio@evidence.eu.com>
To: "Artem S. Tashkinov" <t.artem@lycos.com>
Cc: linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>
Subject: Re: On Linux numbering scheme
Date: Thu, 06 Jan 2011 09:31:42 +0100 [thread overview]
Message-ID: <4D257DEE.40009@evidence.eu.com> (raw)
In-Reply-To: <28654042.253821287691362834.JavaMail.root@mail-zbox20.bo3.lycos.com>
Hi,
> As time passes by, the Linux numbering scheme makes even less sense.
> Some time ago there was a discussion on LKML about a new numbering
> scheme but it didn't come to any positive conclusion and then the
> subject was forgotten entirely. Not meaning to raise a clamour here
> (and I suppose I represent a large group of Linux users here). I'm
> willing to suggest a numbering scheme which I hope will answer all
> known complaints and criticism.
This seems to be a periodically recurrent topic on the list.
If I've correctly understood all points of view, there are currently two
groups of developers:
1. Those who want to maintain the current numbering scheme, because they
feel comfortable with it, and because they can easily understand the
number of releases between one release and another.
2. Those who prefer having a scheme somehow related to the date, so they
can easily understand when a certain kernel has been released (i.e. how
"old" it is).
Does really exist a numbering scheme that can satisfy both groups of
people ? Probably not.
My only idea would be to maintain the usual numbering scheme, and just
replace the second number (6) with the year of release.
For example:
2.6.36 would be 2.10.36
2.6.37 would be 2.11.37
2.6.38 would be 2.11.38
and so on...
This way, you put some information about the year of release without
loosing all the benefits of the current scheme.
But this means having two independent incremental numbers, which maybe
is a too insane scheme.
Regards,
Claudio
next prev parent reply other threads:[~2011-01-06 8:31 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
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 [this message]
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=4D257DEE.40009@evidence.eu.com \
--to=claudio@evidence.eu.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=t.artem@lycos.com \
/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