From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: Linux 4.0-rc1 out..
Date: Mon, 23 Feb 2015 16:15:41 +1100 [thread overview]
Message-ID: <20150223161541.22df98cc@canb.auug.org.au> (raw)
In-Reply-To: <CA+55aFzS==STcTbwabdvw=7_xX08kkUd=g2Q4XbWJzKbpjyN1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2772 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
I haven't done these for a while, so I haven't included a previous
release for comparison.
(No merge commits counted, next-20150209 was the last linux-next before
the merge window opened.)
Commits in v4.0-rc1 (relative to v3.19): 8950
Commits in next-20140804: 8279
Commits with the same SHA1: 7492
Commits with the same patch_id: 452 (1)
Commits with the same subject line: 70 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20150209: 8014 89.5%
Some breakdown of the list of extra commits (relative to next-20150209)
in -rc1:
Top ten first word of commit summary:
103 mips
79 staging
37 drm
32 lguest
25 ib
22 arm
19 rdma
19 input
19 alsa
18 sunrpc
Top ten authors:
51 rusty@rustcorp.com.au
50 markos.chandras@imgtec.com
25 trond.myklebust@primarydata.com
21 leonid.yegoshin@imgtec.com
19 hch@lst.de
17 richard.alpe@ericsson.com
16 abbotti@mev.co.uk
15 zyan@redhat.com
15 arnd@arndb.de
14 dhowells@redhat.com
Top ten commiters:
81 gregkh@linuxfoundation.org
75 davem@davemloft.net
64 markos.chandras@imgtec.com
59 rusty@rustcorp.com.au
47 torvalds@linux-foundation.org
43 roland@purestorage.com
38 ralf@linux-mips.org
31 trond.myklebust@primarydata.com
26 mingo@kernel.org
26 idryomov@gmail.com
There are also 265 commits in next-20150209 that didn't make it into
v4.0-rc1.
Top ten first word of commit summary:
25 rcu
24 arm
20 selftests
19 mm
11 arm-soc
6 documentation
5 tracing
5 staging
5 libceph
5 ceph
Top ten authors:
36 akpm@linux-foundation.org
34 paulmck@linux.vnet.ibm.com
20 shuahkh@osg.samsung.com
11 olof@lixom.net
9 minchan@kernel.org
7 rostedt@goodmis.org
6 zyan@redhat.com
6 behanw@converseincode.com
5 tapaswenipathak@gmail.com
4 namjae.jeon@samsung.com
Some of Andrew's patches are fixes for other patches in his tree (and
have been merged into those).
Top ten commiters:
102 sfr@canb.auug.org.au
35 paulmck@linux.vnet.ibm.com
21 shuahkh@osg.samsung.com
11 olof@lixom.net
10 idryomov@redhat.com
9 kgene@kernel.org
7 rostedt@goodmis.org
7 behanw@converseincode.com
7 arnd@arndb.de
4 treding@nvidia.com
Those commits by me are from the quilt series (mainly Andrew's mmotm
tree).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-02-23 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+55aFzS==STcTbwabdvw=7_xX08kkUd=g2Q4XbWJzKbpjyN1A@mail.gmail.com>
2015-02-23 5:15 ` Stephen Rothwell [this message]
2015-02-23 8:22 ` Linux 4.0-rc1 out Sedat Dilek
2015-02-23 23:14 ` Olof Johansson
2015-02-24 19:40 ` Steven Rostedt
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=20150223161541.22df98cc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox