From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, chrisw@osdl.org, torvalds@osdl.org,
akpm@osdl.org
Subject: Re: Linux 2.6.11.2
Date: Wed, 09 Mar 2005 13:21:36 -0800 [thread overview]
Message-ID: <422F68E0.90607@osdl.org> (raw)
In-Reply-To: <20050309210631.GY3163@waste.org>
Matt Mackall wrote:
> On Wed, Mar 09, 2005 at 12:39:23AM -0800, Greg KH wrote:
>
>>And to further test this whole -stable system, I've released 2.6.11.2.
>>It contains one patch, which is already in the -bk tree, and came from
>>the security team (hence the lack of the longer review cycle).
>>
>>It's available now in the normal kernel.org places:
>> kernel.org/pub/linux/kernel/v2.6/patch-2.6.11.2.gz
>>which is a patch against the 2.6.11.1 release.
>
>
> Argh! @*#$&!!&!
I have to Argh this also (with Matt).
>>If consensus arrives
>>that this patch should be against the 2.6.11 tree, it will be done that
>>way in the future.
It would be much easier on users/testers to have to apply
only one patch to base (2.6.11 e.g.) to get to 2.6.x.y
(2.6.11.3 e.g.). One Patch File. Not three.
> Consensus arrived back when 2.6.8.1 came out.
>
> Please, folks, there are automated tools that "know" about kernel
> release numbering and so on. Said tools broke with 2.6.11.1 because it
> wasn't in the same place that 2.6.8.1 was and now this breaks with all
> precedent by being an interdiff along a branch.
>
> Fixing it in the future is too #*$%* late because you've now turned it
> into a special case.
--
~Randy
next prev parent reply other threads:[~2005-03-09 21:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 8:39 Linux 2.6.11.2 Greg KH
2005-03-09 8:39 ` Greg KH
2005-03-17 15:18 ` Gene Heskett
2005-03-09 9:52 ` Marcos D. Marado Torres
2005-03-09 10:04 ` Geert Uytterhoeven
2005-03-09 10:17 ` Marcos D. Marado Torres
2005-03-09 10:41 ` Geert Uytterhoeven
2005-03-09 11:23 ` Jesper Juhl
2005-03-09 21:26 ` Wakko Warner
2005-03-09 10:21 ` Dominik Karall
2005-03-09 10:28 ` Marcos D. Marado Torres
2005-03-09 10:51 ` Adrian Bunk
2005-03-09 15:35 ` Greg KH
2005-03-09 11:11 ` Pavel Machek
2005-03-09 23:57 ` Matt Mackall
2005-03-10 5:16 ` Willy Tarreau
2005-03-11 18:45 ` Bill Davidsen
2005-03-11 19:08 ` Matt Mackall
2005-03-11 19:19 ` Chris Wright
2005-03-11 22:01 ` Greg KH
2005-03-14 17:10 ` Bill Davidsen
2005-03-14 17:32 ` Greg KH
2005-03-15 20:38 ` Bill Davidsen
2005-03-16 8:56 ` David Greaves
2005-03-09 12:38 ` Andy Whitcroft
2005-03-09 14:03 ` Marcelo Tosatti
2005-03-09 18:38 ` Greg KH
2005-03-09 20:32 ` Bill Davidsen
2005-03-09 21:06 ` Matt Mackall
2005-03-09 21:21 ` Randy.Dunlap [this message]
2005-03-09 23:11 ` Greg KH
2005-03-09 23:38 ` Matt Mackall
2005-03-10 12:54 ` Gene Heskett
2005-03-11 19:23 ` Bill Davidsen
2005-03-11 23:33 ` Gene Heskett
2005-03-11 14:53 ` Krzysztof Halasa
2005-03-11 17:38 ` Chris Wright
2005-03-11 19:28 ` Bill Davidsen
2005-03-11 21:07 ` Krzysztof Halasa
2005-03-11 21:11 ` Chris Wright
[not found] <fa.dan38um.1m4gojq@ifi.uio.no>
[not found] ` <fa.animhpl.r201hh@ifi.uio.no>
2005-03-10 1:46 ` Bodo Eggert
2005-03-10 3:08 ` Matt Mackall
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=422F68E0.90607@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=torvalds@osdl.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