From: Luis Henriques <luis.henriques@canonical.com>
To: D M German <dmg@uvic.ca>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: helping with tracking commits across repos
Date: Tue, 16 Apr 2013 13:50:52 +0100 [thread overview]
Message-ID: <20130416125052.GC3054@hercules> (raw)
In-Reply-To: <87ppxyqphn.fsf@mn.cs.uvic.ca>
Hi Daniel,
On Sat, Apr 13, 2013 at 11:01:24AM -0700, D M German wrote:
> vinod>
> vinod>
> vinod>
> vinod> On Fri, 2013-04-12 at 13:22 -0700, D M German wrote:
> vinod> > Hi Everybody,
> vinod> >
> vinod> > I am professor of computer science at the University of Victoria
> vinod> > (Canada).
> vinod> >
> vinod> > During the last year and a half, we have been trying to track the
> vinod> > commits as they move in the entire linux git repos ecosystem. We have
> vinod> > amassed a good amount of data that tell us for every commit (and in fact
> vinod> > for every unique patch inside a commit) where it has been and whether it
> vinod> > has reached linus or not ---or any other repository, as a matter of
> vinod> > fact.
> vinod> i see some of the commits shown not in linus tree, although they are...
> vinod> perhaps a bug?
> vinod> http://o.cs.uvic.ca:20810/perl/cid.pl?cid=765024697807ad1e1cac332aa891253ca4a339da
> vinod>
> vinod> It shows the same for linus's merge!
> vinod> http://o.cs.uvic.ca:20810/perl/cid.pl?cid=cfb63bafdb87bbcdc5d6dbbca623d3f69475f118
>
> Hi Vinod,
>
> the tracking of the path-to-linus is something that is not done
> automatically yet (I have to start the process manually, as there are
> some issues I need to verify--it is a heuristic), but I plan to run it
> automatically.
>
> Nonetheless, it might be run once a day, so the commits of the day will
> always be slightly behind.
>
> One thing that will help me is that if any of you feel I am not tracking
> your repository, please send me an email with its address.
While looking at the repos list, I realised you are tracking some ubuntu
git trees that are not actually useful, namely:
git://kernel.ubuntu.com/roc/linux-2.6
git://kernel.ubuntu.com/rtg/net-next
I would like to ask if you could remove these two and add instead the
linux-3.5.y branch in the git://kernel.ubuntu.com/ubuntu/linux.git repo
(I'm not sure if you track the branches separately).
Cheers,
--
Luis
next prev parent reply other threads:[~2013-04-16 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 20:22 helping with tracking commits across repos 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 [this message]
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=20130416125052.GC3054@hercules \
--to=luis.henriques@canonical.com \
--cc=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