Re: helping with tracking commits across repos

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

 Greg KH twisted the bytes to say:

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

 Greg> Yes, that's a great thing.  Maybe the ability to see the subject: line
 Greg> of the commit somewhere easier than having to click through to the patch
 Greg> would be nice, so we can just glance at the report and say, "Look at all
 Greg> of the btrfs patches that showed up out of nowhere, what happened?"

 Greg> Oh, and if you could do it for a specific kernel release, not a date
 Greg> range, that would be nice (i.e. report for 3.9-rc1, 3.8-rc1, 3.7-rc1,
 Greg> etc.)

What would be the simplest approach to getting the date? I suspect that
it can be done by doing some command line magic in Linus git repo.

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

 Greg> That's just a tiny number so it's probably not needed.

 >> 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).

I's not difficult to do. I'll take care of it.

--dmg


--
Daniel M. German                  "Trying is the first step
   Homer Simpson ->                towards failure."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .