From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: linux-next: stats (was: Linux 5.0-rc1)
Date: Mon, 7 Jan 2019 16:07:56 +1100 [thread overview]
Message-ID: <20190107160756.7c502d5a@canb.auug.org.au> (raw)
In-Reply-To: <CAHk-=wgKYnrL3LjhVkH2Fp+ecmWhLqezT9zmR6CzfcpwcJX0qA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2663 bytes --]
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20181224 was the last linux-next before
the merge window opened.)
Commits in v5.0-rc1 (relative to v4.20): 10843
Commits in next-20181224: 10867
Commits with the same SHA1: 10044
Commits with the same patch_id: 301 (1)
Commits with the same subject line: 52 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20181224: 10397 95%
Some breakdown of the list of extra commits (relative to next-20181224)
in -rc1:
Top ten first word of commit summary:
49 drm
26 cifs
24 perf
19 net
16 um
16 thermal
16 dt-bindings
16 csky
11 arm64
9 pci
Top ten authors:
20 yamada.masahiro@socionext.com
15 ren_guo@c-sky.com
12 torvalds@linux-foundation.org
12 palcantara@suse.de
11 anton.ivanov@cambridgegreys.com
11 acme@redhat.com
10 vvs@virtuozzo.com
10 hch@lst.de
9 julia.lawall@lip6.fr
9 daniel@iogearbox.net
Top ten commiters:
51 davem@davemloft.net
46 alexander.deucher@amd.com
29 acme@redhat.com
28 stfrench@microsoft.com
23 torvalds@linux-foundation.org
22 edubezval@gmail.com
19 yamada.masahiro@socionext.com
19 ren_guo@c-sky.com
17 richard@nod.at
14 axboe@kernel.dk
There are also 470 commits in next-20181224 that didn't make it into
v5.0-rc1.
Top ten first word of commit summary:
43 asoc
37 mm
23 mfd
23 arm
19 vfs
18 leaking_addresses
15 xtensa
13 nios2
11 nfc
11 dt-bindings
Top ten authors:
34 dhowells@redhat.com
32 akpm@linux-foundation.org
18 me@tobin.cc
17 kuninori.morimoto.gx@renesas.com
13 olof@lixom.net
13 jcmvbkbc@gmail.com
13 ebiggers@google.com
11 npiggin@gmail.com
10 david@redhat.com
9 dan.carpenter@oracle.com
Some of Andrew's patches are fixes for other patches in his tree (and
have been merged into those).
Top ten commiters:
125 sfr@canb.auug.org.au
45 broonie@kernel.org
36 dhowells@redhat.com
26 lee.jones@linaro.org
25 tytso@mit.edu
18 me@tobin.cc
16 jcmvbkbc@gmail.com
13 p.zabel@pengutronix.de
13 olof@lixom.net
13 ley.foon.tan@intel.com
Those commits by me are from the quilt series (mainly Andrew's mmotm
tree).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-07 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 2:14 Linux 5.0-rc1 Linus Torvalds
2019-01-07 5:07 ` Stephen Rothwell [this message]
2019-01-07 19:26 ` Linux 5.0-rc1 (test results) Guenter Roeck
2019-01-07 23:21 ` Linus Torvalds
2019-01-08 9:51 ` Guo Ren
2019-01-08 15:40 ` Michal Hocko
2019-01-08 16:16 ` Guo Ren
2019-01-08 17:29 ` Michal Hocko
2019-02-09 19:42 ` Linux 5.0-rc1 Paul Bolle
2019-02-11 0:01 ` isdn
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=20190107160756.7c502d5a@canb.auug.org.au \
--to=sfr@canb.auug.org.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 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).