From: Vinod Koul <vkoul@infradead.org>
To: dmg@uvic.ca
Cc: vinod.koul@intel.com, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: helping with tracking commits across repos
Date: Sat, 13 Apr 2013 21:48:55 +0530 [thread overview]
Message-ID: <1365869935.2348.15.camel@vkoul-udesk3> (raw)
In-Reply-To: <87r4ifxzwu.fsf@mn.cs.uvic.ca>
On Fri, 2013-04-12 at 13:22 -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.
i see some of the commits shown not in linus tree, although they are...
perhaps a bug?
http://o.cs.uvic.ca:20810/perl/cid.pl?cid=765024697807ad1e1cac332aa891253ca4a339da
It shows the same for linus's merge!
http://o.cs.uvic.ca:20810/perl/cid.pl?cid=cfb63bafdb87bbcdc5d6dbbca623d3f69475f118
--
Vinod Koul
Intel Corp.
next prev parent reply other threads:[~2013-04-13 16:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 20:22 D M German
2013-04-12 20:31 ` 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 [this message]
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=1365869935.2348.15.camel@vkoul-udesk3 \
--to=vkoul@infradead.org \
--cc=dmg@uvic.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vinod.koul@intel.com \
/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
all inboxes | Powered by JetHome®