public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: D M German <dmg@uvic.ca>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: helping with tracking commits across repos
Date: Fri, 12 Apr 2013 13:22:09 -0700	[thread overview]
Message-ID: <87r4ifxzwu.fsf@mn.cs.uvic.ca> (raw)


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.

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.

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,


--daniel german
dmg@uvic.ca
http://turingmachine.org

             reply	other threads:[~2013-04-12 20:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 20:22 D M German [this message]
2013-04-12 20:31 ` helping with tracking commits across repos Greg KH
2013-04-13 18:01   ` D M German
2013-04-13 18:56     ` D M German
2013-04-16 12:50     ` Luis Henriques
2013-04-15 21:49   ` D M German
2013-04-15 23:09     ` Greg KH
2013-04-16  0:13       ` D M German
2013-04-16  4:40         ` Greg KH
2013-04-24  6:26           ` D M German
2013-04-13 16:18 ` Vinod Koul
2013-04-14  4:01 ` Ben Hutchings
2013-04-15 18:21   ` dmg
2013-04-15 18:39     ` Ben Hutchings

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r4ifxzwu.fsf@mn.cs.uvic.ca \
    --to=dmg@uvic.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox