From: "Marco Costalba" <mcostalba@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Paul Mackerras" <paulus@samba.org>,
git@vger.kernel.org, "Jonas Fonseca" <fonseca@diku.dk>
Subject: Re: Gitk feature - show nearby tags
Date: Sat, 3 Jun 2006 13:16:45 +0200 [thread overview]
Message-ID: <e5bfff550606030416s2ef6182crbde1395dd29e5b94@mail.gmail.com> (raw)
In-Reply-To: <7vslmm8rcd.fsf@assigned-by-dhcp.cox.net>
On 6/3/06, Junio C Hamano <junkio@cox.net> wrote:
> Paul Mackerras <paulus@samba.org> writes:
>
> > 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.
>
> Another thing that would equally be useful is to show which
> branch a particular commit is on, so for example I can pick one
> commit while doing "gitk next" to view the next branch and see
> which topic it belongs to, and "gitk this-topic" to see which
> commits on that topic, if any, are not yet in the "next" branch.
>
If I have understood correctly the patch runs a 'git rev-list --all
--topo-order --parents'
and then does a tree walking.
I am wandering if there exist any native git way to found the previous tag.
As example given a selected revision with id <sha> is it possible to
do something like this to fond the ancestor?
1) get the tag list with git-peek-remote or something similar if tags
are not already loaded
2) given the tagList vector with n elements run
git-rev-list --topo-order <sha> ^tagList[0] ^tagList[1] ....
^tagList[n-1]
3) take the last sha spit out by git-rev-list, be it <lastSha>.
4) Previous nearest tag is the parent of lastSha
I've missed something?
Marco
next prev parent reply other threads:[~2006-06-03 11:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 9:38 Gitk feature - show nearby tags Paul Mackerras
2006-06-03 10:29 ` Junio C Hamano
2006-06-03 11:16 ` Marco Costalba [this message]
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=e5bfff550606030416s2ef6182crbde1395dd29e5b94@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=paulus@samba.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).