From: Jean Delvare <khali@linux-fr.org>
To: Lars Hjemli <hjemli@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
Git mailing list <git@vger.kernel.org>
Subject: Re: [feature request] gitweb: tags in history
Date: Sat, 21 Aug 2010 20:07:07 +0200 [thread overview]
Message-ID: <20100821200707.6cca565e@hyperion.delvare> (raw)
In-Reply-To: <AANLkTik+NBvdVkN-TvC_F5MWGZrtgEZMPOXr=Tsr1eA_@mail.gmail.com>
On Sat, 21 Aug 2010 19:47:12 +0200, Lars Hjemli wrote:
> On Sat, Aug 21, 2010 at 19:21, Jakub Narebski <jnareb@gmail.com> wrote:
> > Lars Hjemli wrote:
> >> <shameless plug>
> >> With cgit, you can answer such questions by combining path limiting
> >> and range queries, e.g.
> >> http://hjemli.net/git/cgit/log/scan-tree.c?qt=range&q=v0.8.2..v0.8.3
> >> shows all commits affecting scan-tree.c between v0.8.2 and v0.8.3.
> >> Maybe gitweb could implement something similar?
> >> </shameless plug>
> >
> > Gitweb also supports range limiting in log-like views from some time,
> > but currently there is no UI for that, and you have to handcraft the URL,
> > e.g.:
> >
> > http://gitweb.example.com/repo.git?a=history;f=foo.c;hpb=v0.8.2;hb=v0.8.3
> >
> > or (in the path_info form)
> >
> > http://gitweb.example.com/repo.git/history/v0.8.2..v0.8.3:/foo.c
>
> Nice, I didn't know gitweb supported this - maybe it's all Jean needs?
Well, as long as there is no UI for it, it's not too useful: I'm can
run git on the command line for the same result (with git log.)
Also, it doesn't exactly suits my needs. I don't necessarily know in
advance the range in which the change happened. Quite often, the
question I have to answer is the other way around, that is: when did a
given change happen? Sometimes I know the commit ID and I can just call
"git name-rev" (although it's somewhat slow and the output isn't
friendly), but sometimes I don't know even that, and this is when I'd
like to be able to just browse the history for a given file with
all relevant tags printed. This also gives a more general picture
of what happened to the file over time immediately, which is sometimes
useful.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2010-08-21 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 7:26 [feature request] gitweb: tags in history Jean Delvare
2010-08-21 8:22 ` Jakub Narebski
2010-08-21 9:15 ` Jean Delvare
2010-08-21 10:17 ` Jakub Narebski
2010-08-21 16:31 ` Lars Hjemli
2010-08-21 17:21 ` Jakub Narebski
2010-08-21 17:47 ` Lars Hjemli
2010-08-21 18:07 ` Jean Delvare [this message]
2010-08-21 18:50 ` Lars Hjemli
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=20100821200707.6cca565e@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=jnareb@gmail.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;
as well as URLs for NNTP newsgroup(s).