On Fri, Apr 12, 2013 at 01:22:09PM -0700, D M German wrote: > > Hi Everybody, > > I am professor of computer science at the University of Victoria > (Canada). > > During the last year and a half, we have been trying to track the > commits as they move in the entire linux git repos ecosystem. We have > amassed a good amount of data that tell us for every commit (and in fact > for every unique patch inside a commit) where it has been and whether it > has reached linus or not ---or any other repository, as a matter of > fact. > > please look at the following URLs: > > http://o.cs.uvic.ca:20810/perl/cid.pl?cid=9753dfe19a85e7e45a34a56f4cb2048bb4f50e27 > > http://o.cs.uvic.ca:20810/perl/cid.pl?cid=55345fb9ff68e2e5c0259c814542e72aec972c02 > > or > > http://o.cs.uvic.ca:20810/perl/cid.pl?cid=e59bcdae87ec116dde25da6d725f79fefb253693 > > it will give you an idea of the data we have. You can also track other > commits using the input box, if you are interested. Very interesting, thanks for the links. > I wonder if this information is of use to any of you. If you have > specific needs on how you think this info (and some more we have) can be > of use, please let me know. For stable releases, I can't think of anything, other than the tracking of commits from a stable tree into a distro tree, as you do show happening above into the openSUSE kernel, which is really nice. But, for the linux-next stuff, that could be very interesting. We always like seeing what commits in a -rc1 release did NOT previously show up in linux-next. Stephen has some tools on how to do this, it would be interesting to see if your tools could do something like that to track down the "rouge" commits that don't get community testing. > By the way, I'll be at the Linux Collaboration Summit next week (I am > involved with the development of SPDX). If any of you is interested to > meet, please let me know, I'll be there as well, if you want to talk about this in person, just grab me if you see me around. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html