From: Jarek Poplawski <jarkao2@o2.pl>
To: Petr Baudis <pasky@suse.cz>
Cc: 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 00:30:23 +0100 [thread overview]
Message-ID: <47436E0F.6080003@o2.pl> (raw)
In-Reply-To: <20071120215904.GF1001@machine.or.cz>
Petr Baudis wrote, On 11/20/2007 10:59 PM:
> Hi,
>
> On Tue, Nov 20, 2007 at 03:20:42PM +0100, Jarek Poplawski wrote:
>> I see gitweb is much more usable (faster) than a few months ago, but
>> there is one thing a bit problematic: in the history of patches I'm
>> very often interested in which kernel version of Linus' tree the patch
>> appeared for the first time. If it's not some big problem, and maybe
>> somebody else finds this useful too, I'd really appreciate adding such
>> a feature.
>
> in git terms, you'd like gitweb to provide output for command:
>
> git describe --contains
>
> This is interesting feature request. I guess the support would be nice,
> though in theory this operation can be a bit resource-intensive in case
> there is not many tags and a lot of development (with uncached
> repository, this query took quite a bit of time on my copy of the kernel
> git tree). Probably this should be an optional feature and somehow dwell
> on a separate page, which doesn't fit too well in the current gitweb
> page structure...
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. And it
would suffice if it were shown on the commit page only. But, of course,
it's not urgent at all! (And alas I'm no webmaster, so I can miss
something.)
>> Petr, I hope there is no necessity to subscribe to the git list for
>> this one question, so I'd really feel greteful for forwarding, if you
>> find this request reasonable.
>
> Yes, there is no necessity - you can post this on the git mailing list
> without subscribing yourself.
Great! I misunderstood the page message. Btw., I know it's not the kernel,
but IMHO there should be some place for it in the MAINTAINERS!
Thanks,
Jarek P.
next prev parent reply other threads:[~2007-11-20 23:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 14:20 gitweb: kernel versions in the history (feature request, probably) Jarek Poplawski
2007-11-20 21:59 ` Petr Baudis
2007-11-20 23:30 ` Jarek Poplawski [this message]
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
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=47436E0F.6080003@o2.pl \
--to=jarkao2@o2.pl \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.