Re: helping with tracking commits across repos

[D M German <dmg@uvic.ca>]

Greg KH twisted the bytes to say:

 Greg> But, for the linux-next stuff, that could be very interesting.  We
 Greg> always like seeing what commits in a -rc1 release did NOT previously
 Greg> show up in linux-next.  Stephen has some tools on how to do this, it
 Greg> would be interesting to see if your tools could do something like that
 Greg> to track down the "rouge" commits that don't get community testing.


Hi Greg,

Let me see if I understood you.

I looked into commits created during 2013 that satisfy the following
condition:

* We observed them in Linus repo _before_ Linux-next (that does not
necessarily mean they didn't appear in linus before linux next)
* Are not merge commits
* Were committed in 2013 (no point of showing you 2012, i guess).

they are listed here (it takes a couple of minutes to create the list... so
it is not a realtime list, but I that can be fixed
if it is useful):

http://o.cs.uvic.ca:20810/perl/next.pl

is this what you had in mind? obviously Linus commits appear in his repo
before Next, so I could drop him from the report.

I have also added the commit that merges each commit, which is probably
useful too. If it is empty either we haven't update the data or it
was done straight into linus repo (as in 3e2e0d2c222bdf5bafd722dec1618fa6073ef372).

--daniel


--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .