From: "Artem S. Tashkinov" <t.artem@lycos.com>
To: Tejun Heo <htejun@gmail.com>
Cc: kevin granade <kevin.granade@gmail.com>,
linux-kernel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: On Linux numbering scheme
Date: Mon, 25 Oct 2010 05:45:13 -0400 (EDT) [thread overview]
Message-ID: <234909.335371287999912985.JavaMail.root@mail-zbox20.bo3.lycos.com> (raw)
In-Reply-To: <4CC548F8.1090307@gmail.com>
----- "Tejun Heo" wrote:
> On 10/22/2010 04:00 AM, 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?
>
> Agreed. These days, I use just the last digit, as in kernel 36, in
> casual contexts. It's a number as good as any other. I don't think
> it needs to be changed actively. If the 2.6. prefix is bothering,
> just use the last number and maybe that will become semi-official in
> the future, or maybe not. Doesn't really matter.
>
> --
> tejun
That's my point. "2.6" prefix is totally meaningless nowadays. I just
want to rejuvenate the numbering scheme and make it easy to understand
and comprehend. What's the difference between .16 and .36? Besides, I
just think these huge numbers look unsightly. Do you know any other
piece of software which has the same huge numbers?
next prev parent reply other threads:[~2010-10-25 9:45 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 ` 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 [this message]
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=234909.335371287999912985.JavaMail.root@mail-zbox20.bo3.lycos.com \
--to=t.artem@lycos.com \
--cc=htejun@gmail.com \
--cc=kevin.granade@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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