public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	Kevin Hilman <khilman@linaro.org>
Subject: Re: linux-next stats (Was: Linux 3.12-rc1)
Date: Wed, 18 Sep 2013 08:53:42 -0400	[thread overview]
Message-ID: <20130918125342.GK19937@titan.lakedaemon.net> (raw)
In-Reply-To: <20130917155057.2125aa5f69fb9cf9bbe01166@canb.auug.org.au>

Stephen,

On Tue, Sep 17, 2013 at 03:50:57PM +1000, Stephen Rothwell wrote:
> There are also 358 commits in next-20130701 that didn't make it into v3.11-rc1.
> 
> Top ten first word of commit summary:
> 
>      56 arm
> 
> Top ten authors:
> 
>      13 Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> 
> Top ten commiters:
> 
>      22 Jason Cooper <jason@lakedaemon.net>

:(  That's my mistake.  I should've been tracking my pull requests to
arm-soc more closely.  We've already tweaked the process to prevent this
in the future.

thx,

Jason.

  parent reply	other threads:[~2013-09-18 12:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 22:08 Linux 3.12-rc1 Linus Torvalds
2013-09-17  5:50 ` linux-next stats (Was: Linux 3.12-rc1) Stephen Rothwell
2013-09-18  0:23   ` Nicholas A. Bellinger
2013-09-18  0:37     ` Stephen Rothwell
2013-09-18  6:32       ` Geert Uytterhoeven
2013-09-18 12:53   ` Jason Cooper [this message]
2013-09-19 15:45   ` Mark Brown
2013-09-23 14:33 ` Linux 3.12-rc1 Rob Landley
2013-09-23 16:36   ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2013-09-17  7:26 linux-next stats (Was: Linux 3.12-rc1) Sedat Dilek

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=20130918125342.GK19937@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=arnd@arndb.de \
    --cc=khilman@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sfr@canb.auug.org.au \
    --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