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.10 rc1

May 12, 2013, 11:00 (0 Talkback[s])
(Other stories by Linus Torvalds)
So this is the biggest -rc1 in the last several years (perhaps ever)
at least as far as counting commits go, even if not necessarily in
actual lines (I didn't check the statistics on that).

Which was unexpected, because while linux-next was fairly big, it
wasn't exceptionally so. I'm sure Stephen Rothwell will talk about the
statistics of commits that weren't in -next, we'll see if that was the
reason..

Anyway, despite the large number of commits, hopefully it's all
boringly straigthforward. Sure.

Now, even normally, there's no way to list all the changes, much less
so when it's an unusually large -rc1. But I can do my "merge shortlog"
again, and it's worth mentioning (again) that the name attributed to
the merge is *not* necessarily the author of any of the code, it's
literally just the person who emailed me the pull request. So you can
see this as an approximation of "first-level maintainership" or
something, although even that is somewhat misleading since some of
these things are really done by groups and then there's one person who
end up sending me the end result.

But it's somewhat readable, and gives you a reasonable idea of what is
going on. A better idea can be gotten by looking at git directly,
especially since the merge commits often do contain a better
description of what happened. Not that all submaintainers necessarily
always send me that, but most of the merges actually do have
human-readable background information.

It's possible that I missed something. This really was a busier merge
window than usual. Holler if so,

Linus

Complete Story