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:50 UTC
Message-ID
<xmqqbn5djhz7.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAGZ79kY_C9wSS+z7XwPEWiM+8vhYuZzs_SPZ0mQR=LB+MPzTJg@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
> But it should not be just tags?
>
> We also want to have 4b9ab0ee0130~1^2 to work `right`,

I'd consider that just "crazy", though. I'd be just happy to see 4b9ab0ee0130 highlighted and lead to the named commit, i.e. as long as ~1^2 is not part of the link, it is sufficient.

Previous: Stefan BellerNext: Stephen Kelly
Message 5 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.