Linux Today: Linux News On Internet Time.
Search Linux Today
Linux News Sections:  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Contribute
Contribute
Link to Us
Linux Jobs


Top White Papers

More on LinuxToday


Linux 3.8 rc6

Feb 01, 2013, 23:00 (0 Talkback[s])
(Other stories by Linus Torvalds)
From Linus Torvalds <>
Date Fri, 1 Feb 2013 12:43:33 +1100
Subject Linux 3.8-rc6
It's been a week since -rc5 (perhaps not counting timezone changes),
so -rc6 is out now.

I have to say, -rc6 is bigger than I'd like it to be. I'd really like
things to calm down by rc6, because usually I aim for rc7 to be
roughly the last rc in the series, and that means that I don't want to
see hundreds of patches. But hundreds of patches it is. Not good.

That said, I'm hoping that the bulk of this was due to Davem catching
the flu and the networking pull being delayed by that. Because while
there's been a few other worrisome patterns (x86 changes, EFI stuff
etc), it is largely true that a lot of the rc6 patches were
network-related.

So I'm hoping that rc7 would be better quite quite on its own.

But since I don't trust you sneaky bastards, I have a CleverPlan(tm)
to make *sure* that rc7 will be better and much smaller. That plan
largely depends on me being unreachable for the next week due to the
fact that there is no internet under water.

Paraphrasing the Alien films: "Under water, nobody can read your email".

And once I dry off enough, I'm going to be really pissy ("And how is
that different from the normal Linus, pray tell?") if people send me
pull requests that I think you shouldn't have sent. There will be
cursing. More cursing than normal. Don't send me stuff that doesn't
fix major security issues, big user-reported regressions, or nasty
oopses. Seriously. Just don't.

So think twice - or thrice - before sending me patches or a pull
request for -rc7. You need to have some seriously good reasons for
doing so, and you need to state those reasons very clearly. And I
don't just mean for the pull request in general, I mean for every
single patch in it. So don't ask me to pull three patches, because
_one_ of the three patches fixes a bad regression. Because while I can
see myself doing an rc8 (and I may just have to), I'm not going to
enjoy it much. So please help make sure that rc7 really is tiny and
only contains fixed that absolutely *have* to go in.

In other words, "It fixes a bug" just isn't good enough. The bug needs
to be something that actually matters.

Linus

Complete Story

Related Stories: