[Ksummit-2012-discuss] [ATTEND] linux-next and process

James Bottomley James.Bottomley at HansenPartnership.com
Tue Jun 19 07:37:41 UTC 2012


On Tue, 2012-06-19 at 13:47 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Mon, 18 Jun 2012 19:14:09 -0700 Brian Norris <computersforpeace at gmail.com> wrote:
> >
> > > Someone published statistics a couple of months ago - I think it was for 3.2 or
> > > 3.3. My memory may be wrong, but at as far as I recall the percentage of commits
> > > in the commit window which did not go through -next was quite high, something
> > > in the range of 20 or even 30%.
> > 
> > How does something qualify as "in -next"? Residing for a certain time
> > period, with the same commit ID? If so, then some stats might be
> > misleading, as I know a submaintainer whose tree is in -next but is
> > constantly rebased and tweaked as development progresses and bugs are
> > fixed. Eventually, these commits make it into mainline, but their
> > commit ID may or may not have been present in -next simply because of
> > rebasing.
> 
> OK, I forgot to publish the stats for v3.5-rc1, but here they are:
> 
> (No merge commits counted, next-20120521 is the first linux-next after
> v3.4, script attached, I ran "do_stats v3.4 next-20120521 v3.5-rc1")
> 
> Commits in v3.5-rc1 (relative to v3.4): 9534
> Commits in next-20120521:		9899
> Commits with the same SHA1:		7669
> Commits with the same patch_id:		 521	(1)
> Commits with the same subject line:	  66	(1)
> 
> (1) not counting those in the lines above.
> 
> So commits in -rc1 that were "in" next-20120521:	8256	86.6%
> Commits in -rc1 that were not in next-20120521:		1278	13.4%
> 
> Again, not too bad, but it would be nice to figure out where the last lot
> came from.  I have the "git log --oneline" list if someone wants them.

I'd also be interested in the other statistic:  What were the 1643
commits that were in next-20120521 but never made it to v3.5-rc1 doing
there (that's 17% of the next tree)?  next is supposed to be our merge
canary, so in theory, only commits destined for the next merge window
should be in there.

James




More information about the Ksummit-2012-discuss mailing list