public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: maximilian attems <max@stro.at>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Michal Marek <mmarek@suse.cz>,
	pefoley2@verizon.net, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT] kbuild fixes for 3.0
Date: Fri, 10 Jun 2011 10:03:39 +0000	[thread overview]
Message-ID: <20110610100339.GE22466@vostochny.stro.at> (raw)
In-Reply-To: <BANLkTinZGuOE3G5Ro0=LB9Y8wcHVgk-3ug@mail.gmail.com>

On Thu, Jun 09, 2011 at 10:53:34PM -0700, Ray Lee wrote:
> On Thu, Jun 9, 2011 at 10:16 PM, Arnaud Lacombe <lacombar@gmail.com> wrote:
> > Beside that, no matter what, you are about to break
> > `/usr/sbin/sensors-detect' (from my Fedora 14), which rely on a 3
> > digits version number:
> 
> Is there really any compelling technical reason to _not_ have Linus
> release the kernels with a superfluous .0 on the end, with the
> understanding that the -stable team gets to increment it for their
> future releases? It'd make every kernel.org release exactly three
> dotted decimals from here on out, which certainly simplifies things.
> 
> It seems like we're just borrowing trouble here by trying to drop it
> down to two numbers.
> 
> (Not, mind you, that I give a damn at all one way or the other, but it
> feels like you all are going to be spending a lot of time tripping
> over poor assumptions in userspace rather than doing actual work.)

you have forgotten the rule that linus himself is allowed to break userland. :P

in Debian an three digit 3.0.0 release would also be very much appreciated as
dpkg will order wrongly 3.0.0~rcX to 3.0.

-- 
maks

  reply	other threads:[~2011-06-10 10:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 21:42 [GIT] kbuild fixes for 3.0 Michal Marek
2011-06-10  0:10 ` Linus Torvalds
2011-06-10  3:14   ` Arnaud Lacombe
2011-06-10  3:37     ` Linus Torvalds
2011-06-10  3:41       ` Arnaud Lacombe
2011-06-10  3:45       ` Arnaud Lacombe
2011-06-10  3:57         ` Linus Torvalds
2011-06-10  5:16           ` Arnaud Lacombe
2011-06-10  5:53             ` Ray Lee
2011-06-10 10:03               ` maximilian attems [this message]
2011-06-10 15:22                 ` Linus Torvalds
2011-06-10 20:45                   ` Michal Marek
2011-06-10 20:56                     ` Linus Torvalds
2011-06-10 15:06               ` Andy Whitcroft
2011-06-10 15:26                 ` Milan Broz
2011-06-10 16:30             ` Arnaud Lacombe
2011-06-10 19:31               ` [lm-sensors] " Jean Delvare
2011-06-10 12:13           ` Michal Marek

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=20110610100339.GE22466@vostochny.stro.at \
    --to=max@stro.at \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=pefoley2@verizon.net \
    --cc=ray-lk@madrabbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox