From: Stephen Rothwell <sfr@canb.auug.org.au>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-next@vger.kernel.org, Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: linux-next: stats
Date: Fri, 3 Aug 2012 14:38:56 +1000 [thread overview]
Message-ID: <20120803143856.26e37ac47cb11871669a19bd@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Hi all,
Well here are this merge windows' stats:
(No merge commits counted, next-20120722 is the first linux-next after
v3.5)
Commits in v3.6-rc1 (relative to v3.5): 8587
Commits in next-20120521: 9245
Commits with the same SHA1: 6711
Commits with the same patch_id: 640 (1)
Commits with the same subject line: 72 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were "in" next-20120722: 7423 86.4%
Commits in -rc1 that were not in next-20120722: 1164 13.6%
Again, not too bad, but it would be 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 onlines list:
grep for btrfs gives 68 commits
media gives 155
rdb gives 43
ceph gives 62
drm gives 69
As for the 1823 commits left in linux-next ... 1191 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 ...)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-08-03 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 4:38 Stephen Rothwell [this message]
2019-05-19 23:15 Linux 5.2-rc1 Linus Torvalds
2019-05-20 3:37 ` linux-next: stats Stephen Rothwell
2020-10-25 22:40 Linux 5.10-rc1 Linus Torvalds
2020-10-25 23:43 ` linux-next: stats Stephen Rothwell
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=20120803143856.26e37ac47cb11871669a19bd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--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).