git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Git mailing list <git@vger.kernel.org>
Subject: [feature request] gitweb: tags in history
Date: Sat, 21 Aug 2010 09:26:16 +0200	[thread overview]
Message-ID: <20100821092616.5e57135b@hyperion.delvare> (raw)

Hi there,

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.

The actual format for displaying the tags can certainly be discussed, I
have no strong opinion on this myself. We may want to let the admin
filter which tags should show up that way, maybe even letting him/her
define primary and secondary tag formats (think main releases vs.
release candidates) for nicer output. Then we may want to group (or
hide) tags when a file hasn't been modified in a long time. But these
are implementation details, even the raw functionality would be quite
useful IMHO, and hopefully not too difficult to implement.

At the moment I am using a custom tool when I need to answer this kind
of question, but being backed-up by quilt, it's quite slow and
disk-consuming. I would love to be able to get rid of it and use only
gitweb.

Thanks,
-- 
Jean Delvare

             reply	other threads:[~2010-08-21  7:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21  7:26 Jean Delvare [this message]
2010-08-21  8:22 ` [feature request] gitweb: tags in history 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
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=20100821092616.5e57135b@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=git@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;
as well as URLs for NNTP newsgroup(s).