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: linux-next stats (Was: Linux 3.13-rc1 is out)
Date: Mon, 25 Nov 2013 11:10:05 +1100 [thread overview]
Message-ID: <20131125111005.e85b207a474ef992c385c8df@canb.auug.org.au> (raw)
In-Reply-To: <CA+55aFxK5hkhteiL5cyPtHX5reup6aOiHQTCDKKdBsHiWsroGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4444 bytes --]
On Fri, 22 Nov 2013 12:36:37 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> Talking about mistakes... I suspect it was a mistake to have that
> extra week before the merge window opened, and I probably should just
> have done a 3.12-rc8 instead. Because the linux-next statistics look
> suspicious, and we had extra stuff show up there not just in that
> first week. Clearly people took that "let's have an extra week of
> merge window" and extrapolated it a bit too much. Oh, well. Live and
> learn.
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20131105 was the linux-next based on v3.12)
Commits in v3.13-rc1 (relative to v3.12): 10518 (v3.12-rc11: 9474)
Commits in next-20131105: 9029 (next-20130903: 8891)
Commits with the same SHA1: 7979 ( 7991)
Commits with the same patch_id: 621 (1) ( 472)
Commits with the same subject line: 70 (1) ( 70)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20131105: 8670 82.4% (8533 90.1%)
Commits in -rc1 that were not in next-20131105: 1848 17.6% ( 941 9.9%)
So worse than last time, probably because of the 1 week delay.
[Aside: if I use next-20131111 as a base (when Linus' starting doing
merges in earnest), the stats look like this:
Commits in next-20131111: 9906
Commits with the same SHA1: 9156
Commits with the same patch_id: 354 (1)
Commits with the same subject line: 41 (1)
So commits in -rc1 that were in next-20131111: 9551 90.8%
Commits in -rc1 that were not in next-20131105: 967 9.2%
So, much more in line with previous releases.
]
Some breakdown of the list of extra commits (relative to next-20131105)
in -rc1:
Top ten first word of commit summary:
337 drm
115 btrfs
83 perf
68 alsa
50 asoc
49 arm
46 net
31 powerpc
27 netfilter
27 acpi
Top ten authors:
66 Ben Skeggs <bskeggs@redhat.com>
63 Takashi Iwai <tiwai@suse.de>
63 Al Viro <viro@zeniv.linux.org.uk>
46 Alex Deucher <alexander.deucher@amd.com>
39 Ben Widawsky <benjamin.widawsky@intel.com>
33 Josef Bacik <jbacik@fusionio.com>
31 Johannes Berg <johannes.berg@intel.com>
29 J. Bruce Fields <bfields@redhat.com>
29 Dan Carpenter <dan.carpenter@oracle.com>
27 Peter Zijlstra <peterz@infradead.org>
Top ten commiters:
195 David S. Miller <davem@davemloft.net>
117 Chris Mason <chris.mason@fusionio.com>
95 Daniel Vetter <daniel.vetter@ffwll.ch>
94 Al Viro <viro@zeniv.linux.org.uk>
86 Ben Skeggs <bskeggs@redhat.com>
82 Arnaldo Carvalho de Melo <acme@redhat.com>
74 Alex Deucher <alexander.deucher@amd.com>
69 Takashi Iwai <tiwai@suse.de>
53 Dave Airlie <airlied@redhat.com>
52 Mark Brown <broonie@linaro.org>
There are also 358 commits in next-20131105 that didn't make it into
v3.13-rc1.
Top ten first word of commit summary:
51 arm
40 crypto
21 block
11 x86
11 ocfs2
11 dm
10 ceph
10 bluetooth
9 iov_iter
9 9p
Top ten authors:
27 Kent Overstreet <kmo@daterainc.com>
22 Dave Kleikamp <dave.kleikamp@oracle.com>
19 Andrew Morton <akpm@linux-foundation.org>
9 Zach Brown <zab@zabbo.net>
9 Denis Carikli <denis@eukrea.com>
8 Geyslan G. Bem <geyslan@gmail.com>
7 Sachin Kamat <sachin.kamat@linaro.org>
7 Kees Cook <keescook@chromium.org>
7 Alex Porosanu <alexandru.porosanu@freescale.com>
6 Yan, Zheng <zheng.z.yan@intel.com>
Some of Andrew's patches are fixes for other patches in his tree (and
have been merged into those).
Top ten commiters:
93 Stephen Rothwell <sfr@canb.auug.org.au>
48 Herbert Xu <herbert@gondor.apana.org.au>
33 Dave Kleikamp <dave.kleikamp@oracle.com>
30 Jens Axboe <axboe@kernel.dk>
27 Shawn Guo <shawn.guo@linaro.org>
17 Kukjin Kim <kgene.kim@samsung.com>
11 Mauro Carvalho Chehab <m.chehab@samsung.com>
10 Jason Wessel <jason.wessel@windriver.com>
9 Sage Weil <sage@inktank.com>
9 Eric Van Hensbergen <ericvh@gmail.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: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-11-25 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 20:36 Linux 3.13-rc1 is out Linus Torvalds
2013-11-23 0:43 ` Matthew Garrett
2013-11-23 1:08 ` Linus Torvalds
2013-11-23 0:51 ` James Cloos
2013-11-23 2:32 ` Jongman Heo
2013-11-23 0:58 ` Shuah Khan
2013-11-25 0:10 ` Stephen Rothwell [this message]
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=20131125111005.e85b207a474ef992c385c8df@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;
as well as URLs for NNTP newsgroup(s).