From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Jarek Poplawski" <jarkao2@o2.pl>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
"Petr Baudis" <pasky@suse.cz>,
linux-kernel@vger.kernel.org, git@vger.kernel.org
Subject: Re: gitweb: kernel versions in the history (feature request, probably)
Date: Wed, 21 Nov 2007 17:06:39 +0100 [thread overview]
Message-ID: <3ae72650711210806v1e7daa2fq729a7593def99ef7@mail.gmail.com> (raw)
In-Reply-To: <20071121075217.GA1642@ff.dom.local>
On Nov 21, 2007 8:52 AM, Jarek Poplawski <jarkao2@o2.pl> wrote:
> On Tue, Nov 20, 2007 at 10:20:09PM -0500, J. Bruce Fields wrote:
> > On Wed, Nov 21, 2007 at 12:30:23AM +0100, Jarek Poplawski wrote:
> > > I don't know git, but it seems, at least if done for web only, this
> > > shouldn't be so 'heavy'. It could be a 'simple' translation of commit
> > > date by querying a small database with kernel versions & dates.
> >
> > If I create a commit in my linux working repo today, but Linus doesn't
> > merge it into his repository until after he releases 2.6.24, then my
> > commit will be created with an earlier date than 2.6.24, even though it
> > isn't included until 2.6.25.
> >
> > So you have to actually examine the history graph to figure this out
> > this sort of thing.
>
> Of course, you are right, and I probably miss something, but to be
> sure we think about the same thing let's look at some example: so, I
> open a page with current Linus' tree, go to something titled:
> /pub/scm / linux/kernel/git/torvalds/linux-2.6.git / history
>
> and see:
> 2007-10-10 Stephen Hemminger [NET]: Make NAPI polling independent ...
> and just below something with 2007-08-14 date.
>
> Accidentally, I can remember this patch introduced many changes, and
> this big interval in dates suggests some waiting. Then I look at the
> commit, and there are 2 dates visible, so the patch really was created
> earlier. Then I go back to:
> /pub/scm / linux/kernel/git/torvalds/linux-2.6.git / summary
>
> and at the bottom I can see this:
>
> ...
> tags
> 4 days ago v2.6.24-rc3 Linux 2.6.24-rc3
> 2 weeks ago v2.6.24-rc2 Linux 2.6.24-rc2
> 4 weeks ago v2.6.24-rc1 Linux 2.6.24-rc1
> 6 weeks ago v2.6.23 Linux 2.6.23
>
> which drives me crazy, because, without looking at the calendar, and
> calculator, I don't really know which month was 6 weeks ago, and 4
> days ago, either!
>
> So, I go to the: http://www.eu.kernel.org/pub/linux/kernel/v2.6/,
> do some scrolling, look at this:
> ChangeLog-2.6.23 09-Oct-2007 20:38 3.8M
>
> and only now I can guess, this napi patch didn't manage to 2.6.23.
> Of course, usually I've to do a few more clicks and reading to make
> sure where it really started.
>
> So, this could suggest this 2007-10-10 (probably stored with time
> too), could be useful here... but it seems, I'm wrong.
>
> Of course, this problem doesn't look so hard if we forget about
> git internals: I can imagine keeping a simple database, which
> could simply retrieve commit numbers from these ChangeLogs, and
> connecting this with gitweb's commit page as well... For
> performance reasons, doing it only for stable and testing, so with
> -rc 'precision' would be very helpful too.
The "plain" view of the patch has the "version" included:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=bea3348eef27e6044b6161fd04c3152215f96411
From: Stephen Hemminger <shemminger@linux-foundation.org>
Date: Wed, 3 Oct 2007 23:41:36 +0000 (-0700)
Subject: [NET]: Make NAPI polling independent of struct net_device objects.
X-Git-Tag: v2.6.24-rc1~1454^2~841
Is that what you are looking for?
Kay
next prev parent reply other threads:[~2007-11-21 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071120142042.GA4157@ff.dom.local>
2007-11-20 21:59 ` gitweb: kernel versions in the history (feature request, probably) Petr Baudis
2007-11-20 23:30 ` Jarek Poplawski
2007-11-21 3:20 ` J. Bruce Fields
2007-11-21 7:52 ` Jarek Poplawski
2007-11-21 8:09 ` Jarek Poplawski
2007-11-21 15:18 ` Petr Baudis
2007-11-21 16:44 ` Jakub Narebski
2007-11-21 20:16 ` Jarek Poplawski
2007-11-21 16:06 ` Kay Sievers [this message]
2007-11-21 19:29 ` Jarek Poplawski
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=3ae72650711210806v1e7daa2fq729a7593def99ef7@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=pasky@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).