git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Why doesn't gitk highlight commit references from git-describe?

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 13, 2016, 21:32 UTC
Message-ID
<xmqqk2k1jita.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAGZ79kZVC0FxUN45KgLh-2tEK2=j2-yyTajYOc=s-LECgx+yqQ@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
Show 6 quoted lines
> 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.

Previous: Stefan BellerNext: Stefan Beller
Message 3 of 8 in “Why doesn't gitk highlight commit references from git-describe?”
  1. Stephen KellyApr 13, 2016
  2. Stefan BellerApr 13, 2016
  3. Junio C HamanoApr 13, 2016
  4. Stefan BellerApr 13, 2016
  5. Junio C HamanoApr 13, 2016
  6. Stephen KellyApr 13, 2016
  7. Stephen KellyApr 13, 2016
  8. Stephen KellyApr 13, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.