All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Mustapha Rabiu <muztapha@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.0-rc1
Date: Mon, 30 May 2011 16:50:07 -0400	[thread overview]
Message-ID: <20293.1306788607@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 30 May 2011 20:33:29 -0000." <loom.20110530T221016-75@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]

On Mon, 30 May 2011 20:33:29 -0000, Mustapha Rabiu said:
> Linus Torvalds <torvalds <at> linux-foundation.org> writes:
> 
> > 
> > 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.
> > 
> 
> Unsurprising, however, congratulations on yet another major release! 
> We applaud the fact that it'll be just as hideous as 2.6.x, without any 
> new or modified features. Might you explain why you didn't just 
> use 2.8.x ?
> 
> Also, given that multiple people have asked for a handful of things
> to be merged into the kernel, re: security, I'm puzzled about how 
> you managed to develop this self-styled 'alpha-male' based versioning 
> scheme without addressing unsettling discrepancies such 
> as /proc/pid/auxv, /proc/pid/stack and /proc/pid/syscall based 
> info-leaks or slub cache merging, etc, all of which have been publicly 
> discussed over varying periods of time, (circa ~2008)

We can come back and revisit those issues after we get done fixing
*all* the software that made a blind assumption that the kernel
release number matches '2\.[46]\.[0-9]+' (said assumption being
broken at *both* ends by a 3.0 release.

I have to agree with Linus on this one - if we're ruling out ABI-breaking
changes, we want to make this kernel release as little different as
we can.

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2011-05-30 20:50 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
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 [this message]
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=20293.1306788607@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muztapha@gmail.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 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.