From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 2.6.33-rc1
Date: Thu, 17 Dec 2009 18:05:53 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912171745160.15740@localhost.localdomain> (raw)
So the merge window is closed, and -rc1 is out there now.
Talking about the merge window: there were a _lot_ of trees that left
their pull requests pretty dang late. Not everything I merged yesterday
and today were late pull requests, but a lot of it was. I'm used to have a
fairly busy last day of the merge window, but it was a busy last two days
this time - definitely worse than usual.
The two-week merge window is _not_ supposed to be "one day merge window
after thirteen days of silence". In fact, I think that next time around
I'll make the merge window be 11-12 days instead, and people who try to
game the system and do a last-minute pull request will get a surprise, and
get unceremoniously bumped to 2.6.35 instead.
Anyway, apart from that grumbling, it's been a fairly normal merge window,
I think. According to git dirstat (which got fixed to give more accurate
numbers), the distribution of changes is pretty much
- 1/3rd staging
- 1/3rd "rest of drivers"
- 1/3rd "everything else"
with about half of that final "everything else" third being arch stuff,
and half being random other things (firmware, fs, net).
Notable additions? There's a number of drivers, and depending on which
ones you use, you'll find them more or less notable. I personally like how
I finally got to merge the Nouveau code, for example. Others will care
about other things.
Please give it a good testing, so that we can start figuring out the
inevitably regressions,
Linus
next reply other threads:[~2009-12-18 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 2:05 Linus Torvalds [this message]
2009-12-19 19:54 ` Torsten Kaiser
2009-12-20 17:53 ` Torsten Kaiser
2009-12-20 19:14 ` Borislav Petkov
2009-12-20 19:36 ` Torsten Kaiser
2009-12-20 19:40 ` Torsten Kaiser
2009-12-21 14:05 ` Borislav Petkov
2009-12-21 14:31 ` Torsten Kaiser
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=alpine.LFD.2.00.0912171745160.15740@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®