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