From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Stephen Kelly <steveire@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Why doesn't gitk highlight commit references from git-describe?
Date: Wed, 13 Apr 2016 14:32:49 -0700 [thread overview]
Message-ID: <xmqqk2k1jita.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kZVC0FxUN45KgLh-2tEK2=j2-yyTajYOc=s-LECgx+yqQ@mail.gmail.com> (Stefan Beller's message of "Wed, 13 Apr 2016 14:27:12 -0700")
Stefan Beller <sbeller@google.com> writes:
> How would you know(/code) that v1.6.0-rc0~120^2 is a text worth linking?
> "v1.6.0-rc0" is a custom string as that is how we name tags in this project.
> It can follow any convention in other projects.
>
> Maybe a first approximation is if there is a `~` followed by numbers
> or a ^ character, inspect the whole thing if it is a reference into the history?
You (as a gitk process running in a repository) know what tags are
in your repository, so you can find the above pattern and see if the
prefix matches any of the known tag. That way, you do not have to
worry about having to special case HEAD etc.
next prev parent reply other threads:[~2016-04-13 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 20:36 Why doesn't gitk highlight commit references from git-describe? Stephen Kelly
2016-04-13 21:27 ` Stefan Beller
2016-04-13 21:32 ` Junio C Hamano [this message]
2016-04-13 21:45 ` Stefan Beller
2016-04-13 21:50 ` Junio C Hamano
2016-04-13 21:55 ` Stephen Kelly
2016-04-13 21:57 ` Stephen Kelly
2016-04-13 21:41 ` Stephen Kelly
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=xmqqk2k1jita.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
--cc=steveire@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.