"I said I was hoping that -rc8 was the last -rc, and I hate doing this, but we've had more changes since -rc8 than we had in -rc8. And while most of them are pretty trivial, I really couldn't face doing a 2.6.23 release and take the risk of some really stupid brown-paper-bag thing," Linus Torvalds said, announcing the 2.6.23-rc9 kernel. He added, "so there's a final -rc out there, and right now my plan is to make this series really short, and release 2.6.23 in a few days. So please do give it a last good testing, and holler about any issues you find!" He went on to warn developers that the first thing planned for 2.6.24 was to merge the unified x86 architecture:
"This is also a good time to warn about the fact that we're doing the x86 merge very soon (as in the next day or two) after 2.6.23 is out, so if you have pending patches for the next series that touch arch/i386 or x86-64, you should get in touch with Thomas Gleixner and Ingo Molnar, who are the keepers of the merge scripts, and will help you prepare..
"Doing it as early as possible in the 2.6.24-rc4 series (basically I'll do it first thing) will mean that we'll have the maximum amount of time to sort out any issues, and the thing is, Thomas and Ingo already have a tree ready to go, so people can check their work against that, and don't need to think that they have to do any fixups after it his *my* tree. It would be much better if everybody was just ready for it, and not taken by surprise."
From: Linus Torvalds <torvalds@...>
Subject: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..
Date: Oct 1, 11:41 pm 2007
I said I was hoping that -rc8 was the last -rc, and I hate doing this, but
we've had more changes since -rc8 than we had in -rc8. And while most of
them are pretty trivial, I really couldn't face doing a 2.6.23 release and
take the risk of some really stupid brown-paper-bag thing.
So there's a final -rc out there, and right now my plan is to make this
series really short, and release 2.6.23 in a few days. So please do give
it a last good testing, and holler about any issues you find!
This is also a good time to warn about the fact that we're doing the x86
merge very soon (as in the next day or two) after 2.6.23 is out, so if you
have pending patches for the next series that touch arch/i386 or x86-64,
you should get in touch with Thomas Gleixner and Ingo Molnar, who are the
keepers of the merge scripts, and will help you prepare..
Doing it as early as possible in the 2.6.24-rc4 series (basically I'll do
it first thing) will mean that we'll have the maximum amount of time to
sort out any issues, and the thing is, Thomas and Ingo already have a tree
ready to go, so people can check their work against that, and don't need
to think that they have to do any fixups after it his *my* tree. It would
be much better if everybody was just ready for it, and not taken by
surprise.
In other words, people who know they may be affected and would want to
prepare can look at (for example)
git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git x86
and generally get ready for the switch-over.
Linus
-
> take the risk of some
> take the risk of some really stupid brown-paper-bag thing.
Can somebody clarify this for me, please? What does it mean exactly? Thanks.
(i am not a native english speaker)
> take the risk of some
use the paper bag to hide your identity by putting the bag over the head.
brown-paper-bag
http://linux.about.com/cs/linux101/g/brown-paper-bag.htm
Ingo Molnar has plenty of them, in case you need some..
http://lkml.org/lkml/2007/9/30/72
:)
Andi Kleen and the planned x86 merge
Why is Andi Kleen being such a baby when it comes to the x86 merge?
Thomas Gleixner and Ingo Molnar have provided a script which automatically converts a patch for the old tree into a patch for the merged tree. Still Andi whines about huge amounts of work to fix up the patches in his queue. He also talks about letting people "create whatever mess they like" presumably referring to the merge.
I like Thomas reaction of posting Andi's patch queue all fixed up some 20 minutes after Andi claimed it to be "huge amount of work".
nothing happent
There was no flamewar at all, just some misunderstanding, from my reading of the thread. Thomas showed that it was not much work, and Andi accepted and they moved on. Nothing to see here.