From: Jakub Narebski <jnareb@gmail.com>
To: Lars Hjemli <hjemli@gmail.com>
Cc: Jean Delvare <khali@linux-fr.org>,
Git mailing list <git@vger.kernel.org>
Subject: Re: [feature request] gitweb: tags in history
Date: Sat, 21 Aug 2010 19:21:21 +0200 [thread overview]
Message-ID: <201008211921.22495.jnareb@gmail.com> (raw)
In-Reply-To: <AANLkTi=JHzQm4hm-nuTyZq2CL_2z785KtMvVcmaqtgyF@mail.gmail.com>
Lars Hjemli wrote:
> On Sat, Aug 21, 2010 at 11:15, Jean Delvare <khali@linux-fr.org> wrote:
>> On Sat, 21 Aug 2010 01:22:05 -0700 (PDT), Jakub Narebski wrote:
>>> Jean Delvare <khali@linux-fr.org> writes:
>>>
>>>> I have a feature request for gitweb. In the history view, I would like
>>>> to be (optionally) able to see the tags, interlaced with the actual
>>>> commits. The idea is to get an immediate view of all commits that
>>>> happened between specific tags.
>>>>
> ....
>>
>> But shortlog is a repository-wide view, while I need the same for
>> history which is a file-specific view.
>
> <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
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-08-21 17:21 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 [this message]
2010-08-21 17:47 ` Lars Hjemli
2010-08-21 18:07 ` Jean Delvare
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=201008211921.22495.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=khali@linux-fr.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;
as well as URLs for NNTP newsgroup(s).