All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.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 10:04:57 +0800	[thread overview]
Message-ID: <20110530020457.GA6494@kroah.com> (raw)
In-Reply-To: <BANLkTinE8eSSovGx6CPPkTeCpqv8AsS2nw@mail.gmail.com>

On Sun, May 29, 2011 at 06:30:32PM -0700, Linus Torvalds wrote:
> Yay! Let the bikeshed painting discussions about version numbering
> begin (or at least re-start).
> 
> I decided to just bite the bullet, and call the next version 3.0. It
> will get released close enough to the 20-year mark, which is excuse
> enough for me, although honestly, the real reason is just that I can
> no longe rcomfortably count as high as 40.
> 
> The whole renumbering was discussed at last years Kernel Summit, and
> there was a plan to take it up this year too. But let's face it -
> what's the point of being in charge if you can't pick the bike shed
> color without holding a referendum on it? So I'm just going all
> alpha-male, and just renumbering it. You'll like it.
> 
> Now, my alpha-maleness sadly does not actually extend to all the
> scripts and Makefile rules, so the kernel is fighting back, and is
> calling itself 3.0.0-rc1. We'll have the usual 6-7 weeks to wrestle it
> into submission, and get scripts etc cleaned up, and the final release
> should be just "3.0". The -stable team can use the third number for
> their versioning.

Wonderful, I personally really appreciate this, as I think the numbering
sequence of the kernel affects me the most at times with the stable
work.

What kind of whiskey should I get for you in Tokyo.  Any
recommendations?

greg "happy as a clam" k-h

  parent reply	other threads:[~2011-05-30  2:03 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
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 [this message]
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=20110530020457.GA6494@kroah.com \
    --to=greg@kroah.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.