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.8-rc1)
Date: Mon, 24 Dec 2012 09:04:26 +1100 [thread overview]
Message-ID: <20121224090426.99ba9400c9097f5567dfae0d@canb.auug.org.au> (raw)
In-Reply-To: <CA+55aFyd0Wk=hPqiRmk5MMnrwPhse5k1Aih9P-j-Badr7kwhbw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
On Fri, 21 Dec 2012 18:00:58 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> The longest night of the year is upon us (*), and what better thing to
> do than get yourself some nice mulled wine, sit back, relax, and play
> with the most recent rc kernel?
>
> This has been a big merge window: we've got more commits than any
> other kernel in the v3.x kernel series (although v3.2-rc1 was *almost*
> as big). It's been a rather busy merge window, in other words.
Well here are this merge windows' stats:
(No merge commits counted, next-20121211 is the last linux-next before
v3.7)
Commits in v3.8-rc1 (relative to v3.7): 10901
Commits in next-20121211: 11857
Commits with the same SHA1: 9322
Commits with the same patch_id: 492 (1)
Commits with the same subject line: 99 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were "in" next-20121211: 9913 90.9%
(up from 83.5% last time)
Commits in -rc1 that were not in next-20120722: 988 9.1%
Pretty good, but it would be still nice to figure out where the last lot
came from. I have the "git log --oneline --no-walk" list if someone wants them.
Some break down of the onelines list:
grep for drm gives 100
btrfs gives 117
Quite a few of the rest appear to be bug fixes.
As for the 1944 commits left in linux-next ... 1303 are in the kvmtool
tree (most of these are in the tip tree as well - this has been pending a
merge to Linus since before 3.2 ...). There are another 254 commits in
the tip tree (maybe pending fixes), 118 in the xen-two tree and 81 in the
drop-experimental tree.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-12-23 22:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 2:00 Linux 3.8-rc1 Linus Torvalds
2012-12-22 2:57 ` Steven Rostedt
2013-01-16 9:25 ` David Nyström
2012-12-23 13:39 ` [Regression w/ patch] Media commit causes user space to misbahave (was: Re: Linux 3.8-rc1) Rafael J. Wysocki
2012-12-23 14:08 ` Mauro Carvalho Chehab
2012-12-23 17:36 ` Linus Torvalds
2012-12-23 20:21 ` Mauro Carvalho Chehab
2012-12-23 22:29 ` Linus Torvalds
2012-12-24 19:28 ` Mauro Carvalho Chehab
2012-12-23 20:39 ` Laurent Pinchart
2012-12-23 22:04 ` Stephen Rothwell [this message]
[not found] ` <50D764BA.1030501@gmail.com>
2012-12-23 22:35 ` Linux 3.8-rc1 - another regression on USB :-( Linus Torvalds
2012-12-23 23:27 ` Greg Kroah-Hartman
2012-12-24 3:46 ` Woody Suwalski
2012-12-28 23:12 ` Woody Suwalski
2013-01-01 15:17 ` INVALID " Woody Suwalski
2013-01-02 13:41 ` Woody Suwalski
2013-01-12 13:16 ` Andreas Mohr
2013-01-12 16:54 ` Oliver Neukum
2013-01-12 17:38 ` Alan Stern
2013-01-16 4:26 ` Woody Suwalski
2013-01-16 8:25 ` Oliver Neukum
2013-01-16 15:00 ` Alan Stern
2013-01-17 2:25 ` Woody Suwalski
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=20121224090426.99ba9400c9097f5567dfae0d@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).