public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>
Subject: linux-next: stats (Was: Merge window over - Linux 4.13-rc1 out)
Date: Mon, 17 Jul 2017 17:10:18 +1000	[thread overview]
Message-ID: <20170717171018.75fb9afd@canb.auug.org.au> (raw)
In-Reply-To: <CA+55aFwfFyKnHdM5xsxShKEFFt-b0-EEF_CYF4Tsa0sE_V1XtQ@mail.gmail.com>

Hi all,

As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)

(No merge commits counted, next-20170704 was the first linux-next after
the merge window opened.)

Commits in v4.13-rc1 (relative to v4.12):          11258
Commits in next-20170704:                          10626
Commits with the same SHA1:                         9739
Commits with the same patch_id:                      489 (1)
Commits with the same subject line:                   60 (1)

(1) not counting those in the lines above.

So commits in -rc1 that were in next-20170704:     10288 91%

Some breakdown of the list of extra commits (relative to next-20170704)
in -rc1:

Top ten first word of commit summary:

     71 net
     41 drm
     32 ovl
     30 perf
     29 kvm
     28 powerpc
     23 rtc
     20 ubifs
     20 sunrpc
     20 nfs

Top ten authors:

     85 mchehab@kernel.org
     45 elena.reshetova@intel.com
     40 hch@lst.de
     31 chuck.lever@oracle.com
     29 yamada.masahiro@socionext.com
     21 arvind.yadav.cs@gmail.com
     20 dhowells@redhat.com
     20 adrian.hunter@intel.com
     19 joe@perches.com
     19 amir73il@gmail.com

Top ten commiters:

    109 davem@davemloft.net
     89 corbet@lwn.net
     68 anna.schumaker@netapp.com
     52 torvalds@linux-foundation.org
     35 richard@nod.at
     33 mszeredi@redhat.com
     32 acme@redhat.com
     30 mpe@ellerman.id.au
     29 yamada.masahiro@socionext.com
     28 rostedt@goodmis.org

There are also 340 commits in next-20170704 that didn't make it into
v4.13-rc1.

Top ten first word of commit summary:

     49 media
     34 ib
     23 arm
     18 keys
     16 clocksource
     15 mm
     12 dlm
     12 coresight
     12 arc
     10 rcu

Top ten authors:

     26 paulmck@linux.vnet.ibm.com
     23 akpm@linux-foundation.org
     16 ebiggers@google.com
     14 elfring@users.sourceforge.net
     11 mchehab@kernel.org
     11 d.scheller@gmx.net
     10 leo.yan@linaro.org
     10 daniel.lezcano@linaro.org
     10 arnd@arndb.de
      8 ghe@suse.com

Some of Andrew's patches are fixes for other patches in his tree (and
have been merged into those).

Top ten commiters:

     85 sfr@canb.auug.org.au
     49 mchehab@kernel.org
     34 dledford@redhat.com
     29 paulmck@linux.vnet.ibm.com
     22 dhowells@redhat.com
     17 mathieu.poirier@linaro.org
     17 daniel.lezcano@linaro.org
     12 vgupta@synopsys.com
     12 tony@atomide.com
     12 teigland@redhat.com

Those commits by me are from the quilt series (mainly Andrew's mmotm
tree).

-- 
Cheers,
Stephen Rothwell

      reply	other threads:[~2017-07-17  7:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-15 22:37 Merge window over - Linux 4.13-rc1 out Linus Torvalds
2017-07-17  7: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=20170717171018.75fb9afd@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