From: Chris Jones <chrisjones@spin.net.au>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 3-10-rc1
Date: Sun, 12 May 2013 11:32:10 +1000 [thread overview]
Message-ID: <518EF11A.7060706@spin.net.au> (raw)
In-Reply-To: <CA+55aFwfK661zATyUpjkXJo1av51nmMweYdPJE7Le7S2KS3xwg@mail.gmail.com>
On 05/12/2013 11:00 AM, Linus Torvalds wrote:
> 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
>
> <snip>
Thanks for the summary of changes. That helps.
Regards
Chris Jones
--
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.13 (GNU/Linux)
mQENBFF7bwcBCADREEkM0EcEvY6Zt3Zot5RWk5+a6qMZzj6Qf8tZnG2mjyb/NrOa
ujQhakpkmUj2Cpf04jacEKnjxO5Bk6794QPoSelHAkLFol9XRO6j+94tp+21mrGL
GRHppU8LGGCTrllIJOmKdx2dmqIfYKoRcLs/gA1z0ZrNNz+J3OrcWfDWfVz0eWg6
TeXn4PBAQYr8Ci1fF9/vwxeSQx3PGzJjlzKXsbx/etjICDVVkUAxYkEPbazV1LGx
gwDlhCT5YWQQXdESIbUkQFAbCyglM/HkMNEm23AI/z4PhgjdHBCg8LeQTEUiO+a+
b1ypRMZRpn/je96/PE1ZP5TxaEhaimL+OA+dABEBAAG0JENocmlzIEpvbmVzIDxj
aHJpc2pvbmVzQHNwaW4ubmV0LmF1PokBPgQTAQIAKAUCUXtvBwIbAwUJACdPGQYL
CQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQxifpw+rbaJQQBwf+M+arauGqAtkA
LP3Duk0FdDZ3cIbKST3oQd10eACdkH7fQibvtVadkiCeC7CbozSI50o+Snk8/Azd
5V32LkmzUcUEGrnx3B9oZlWMSKZFz5y1rN0YiplQwc4KLq1cSYOZFpVHUZ/ivcJn
k+p+cuLWQrNUI5kiFV+x6lOKIkKgmMrmuKxbwYskPPtE1DIJ7Qh8H/N9aTJ34KAD
+O4dMwDlA2dYDoQYmyCMcly6W6NdPQmww1XX5qmY+obokScIJE5mYUyiFz0kiN6C
NsosjMsUxbrNEPjAfzyU5Y+LqffYJzgyTjlORRqldZU6IDhsmtyDBoshGQFAEm6W
dRQOrNYx6A==
=FJFi
-----END PGP PUBLIC KEY BLOCK-----
next prev parent reply other threads:[~2013-05-12 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 1:00 Linux 3-10-rc1 Linus Torvalds
2013-05-12 1:32 ` Chris Jones [this message]
2013-05-13 1:18 ` linux-next stats (Was: Linux 3-10-rc1) Stephen Rothwell
2013-05-13 5:05 ` Benjamin Herrenschmidt
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=518EF11A.7060706@spin.net.au \
--to=chrisjones@spin.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.