All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.0-rc1
Date: Mon, 30 May 2011 09:38:16 +0300	[thread overview]
Message-ID: <4DE33B58.5030204@panasas.com> (raw)
In-Reply-To: <BANLkTinsO2=tO_UyzzgeU6LE1fObgq+p1Q@mail.gmail.com>

On 05/30/2011 04:47 AM, Linus Torvalds wrote:
> Oh, and as some people already noticed, the numbering means that the
> tar-balls and patches are now in a new directory:
> 
>     /pub/linux/kernel/v3.0
> 
> (under "testing/", since that's what we do with -rc releases).
> However, I did *not* rename the git tree, because that would just be a
> huge inconvenience to git users, so it's still in the same old place
> and yes, that means that my git tree is still called "linux-2.6.git"
> on kernel.org. But it has the v3.0-rc1 tag in it.
> 
> I'll probably add a symlink or something, if people really hate being
> reminded about our long history with the "2.6" numbering. But that
> won't be until closer to the real release, methinks.
> 
>                             Linus

If you are leaving the three digits system, then I still think my system
was the best. Perhaps you have not seen it?

D.Y.N

D = the decade from 1991. So it always changes on 20?1

Y = The year in the decade. Since it all started in 1991 then
    1 <= Y <= 10. To also denote that we never have a zero version

N = The release number of that year. Also start from 1.
    1 <= Y <= 5

Y and D gets advanced not in the first release of the year around
march, but on the last release of the Year the one close to Christmas

So this Kernel is 3.1.3, then 3.1.4 3.2.1 ... 3.10.4, 4.1.1 and so
on. Always beautiful numbers. single increment, the one that knows
can easily calculate the date it was released.

Also alternatively the middle number (Y) can jump every two years
so 1 <= Y <= 5 and 1 <= N <= 9 to make it more even

If you read this and ignored it for been boring then I apologize.
I thought that your original idea was to drop a digit, but if it is
here to stay, then perhaps this is a good way to fight it back.

Cheers
Boaz

  parent reply	other threads:[~2011-05-30  6:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  1:30 Linux 3.0-rc1 Linus Torvalds
2011-05-30  1:47 ` Linus Torvalds
2011-05-30  2:29   ` Américo Wang
2011-05-30  6:38   ` Boaz Harrosh [this message]
2011-05-30 20:03   ` Mariusz Kozlowski
2011-05-30 22:48     ` david
2011-05-31  5:40       ` Mariusz Kozlowski
2011-05-31  7:25         ` Geert Uytterhoeven
2011-05-30  1:59 ` Rafael J. Wysocki
2011-05-30 15:07   ` Steven Rostedt
2011-05-30  2:04 ` Greg KH
2011-05-30  6:39   ` Tarkan Erimer
2011-05-30  9:46   ` Miles Bader
2011-05-30 10:09     ` Anca Emanuel
2011-05-30 10:37       ` Pekka Enberg
2011-05-30 12:03         ` Wanlong Gao
2011-05-30 12:05           ` Zhang, Shijie
2011-05-30 12:58         ` Valdis.Kletnieks
2011-05-30  2:07 ` CaT
2011-05-30  6:01   ` Arkadiusz Miskiewicz
2011-05-30  6:43 ` [GIT PULL] small perf fix for v3.0-rc1 Ingo Molnar
2011-05-30 13:38 ` Linux 3.0-rc1 Camille Moncelier
2011-05-30 14:07 ` 15Hz
2011-05-30 14:33   ` trapDoor
2011-05-30 20:33 ` Mustapha Rabiu
2011-05-30 20:50   ` Valdis.Kletnieks
2011-05-31  5:59 ` Benjamin Herrenschmidt
2011-05-31 10:34   ` Steven Rostedt
2011-05-31  6:01 ` Dave Airlie
2011-05-31  9:23 ` Willy Tarreau
2011-05-30  9:28 Sedat Dilek
2011-05-31 19:27 ` Sedat Dilek

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=4DE33B58.5030204@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.