From: D M German <dmg@uvic.ca>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: helping with tracking commits across repos
Date: Tue, 23 Apr 2013 23:26:35 -0700 [thread overview]
Message-ID: <87k3nsv3z8.fsf@mn.cs.uvic.ca> (raw)
In-Reply-To: <20130416044049.GA6162@kroah.com> (Greg KH's message of "Mon, 15 Apr 2013 21:40:49 -0700")
Greg> On Mon, Apr 15, 2013 at 05:13:45PM -0700, D M German wrote:
>>
>>
>> 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.
Greg> You want to look at the commits from the last major release (i.e. 3.8)
Greg> to the -rc1 release, (i.e. 3.9-rc1). You can't look at the dates,
Greg> that's not going to reflect when the patch landed in Linus's branch.
Hi Greg,
It took me longer than expected, but I finally got it working.
I have a heuristic to estimate when a commit is merged by Linus. It
seems to work well in commits since 2008.
The commits that mark the releases are nicely labeled by Linus. Since I
know in which commit any commit is merged by Linus I can determine what
release the commit is part of.
Take a look:
http://o.cs.uvic.ca:20810/perl/next.pl
It is only doing 2013, but if needed, I can expand the range of
dates. Is suspect older are not that interesting any more.
I still have to "cron" the update of some data to fully do this report
automatically. I hope to do that very soon.
It will help to have some extra eyes. If anybody finds a bug please let
me know.
I also improved some of the other reports to include the log of the
commit whenever is makes sense.
I haven't tried the suggestions on how to reduce space... that is my
next goal.
--daniel
--
Daniel M. German "Beauty is the first test; there is no
permanent place in the world for ugly
G. H. Hardy -> mathematics."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
next prev parent reply other threads:[~2013-04-24 6:26 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
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 [this message]
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=87k3nsv3z8.fsf@mn.cs.uvic.ca \
--to=dmg@uvic.ca \
--cc=greg@kroah.com \
--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