git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: git@vger.kernel.org
Subject: Gitk feature - show nearby tags
Date: Sat, 3 Jun 2006 19:38:27 +1000	[thread overview]
Message-ID: <17537.22675.678700.118093@cargo.ozlabs.ibm.com> (raw)

I just pushed out an update to the "new" branch of the gitk.git
repository, which adds a feature that I have often wished for: it will
now show the nearest preceding and following tags when you select a
commit.  This is very useful if you need to identify which release was
the first to incorporate a particular patch, or if you need to know
which release a patch might have been based on.

(Specifically, it shows the tags for all tagged descendents that are
not descendents of another tagged descendent of the selected commit,
and the tags for all tagged ancestors that are not ancestors of
another tagged ancestor of the selected commit.)

Since there is a one-off computation that gitk does to work this out,
which takes an appreciable time (about 1.5 seconds on my G5 on the
kernel repository), I have made gitk do the computation in the
background, and update the diff/file display window when it's done.
There is also a checkbox in the preferences window where you can turn
it off if you don't want gitk to do this computation.

Comments/suggestions welcome.

Paul.

             reply	other threads:[~2006-06-03  9:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-03  9:38 Paul Mackerras [this message]
2006-06-03 10:29 ` Gitk feature - show nearby tags Junio C Hamano
2006-06-03 11:16   ` Marco Costalba
2006-06-04  1:59     ` Paul Mackerras
2006-06-04  7:08       ` Marco Costalba
2006-06-04  9:25         ` Junio C Hamano
2006-06-04  9:40           ` Marco Costalba
2006-06-04  9:21     ` Junio C Hamano
2006-06-04  9:54       ` Marco Costalba
2006-06-04 10:06         ` Junio C Hamano
2006-06-04 10:10           ` Junio C Hamano
2006-06-04 10:33           ` Marco Costalba
2006-06-04 10:42             ` Marco Costalba
2006-06-04 10:42             ` Junio C Hamano
2006-06-04 13:57               ` Marco Costalba
2006-06-05  6:20                 ` Junio C Hamano
2006-06-05 11:54                   ` Marco Costalba
2006-06-03 12:23   ` Paul Mackerras
2006-06-03 16:50     ` Junio C Hamano
2006-06-04  1:51       ` Paul Mackerras
2006-06-03 15:12   ` Jonas Fonseca
2006-06-03 15:33     ` Jakub Narebski
2006-06-03 16:19       ` Jonas Fonseca
2006-06-04 20:58     ` Junio C Hamano
2006-06-05  0:04       ` Jonas Fonseca
2006-06-05  1:37         ` Junio C Hamano
2006-06-05 20:08           ` Junio C Hamano
2006-06-05 20:19           ` Jonas Fonseca
2006-06-05 21:11       ` Jonas Fonseca

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=17537.22675.678700.118093@cargo.ozlabs.ibm.com \
    --to=paulus@samba.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).