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

Re: [PATCH 0/6] Provide for config to specify tags not to abbreviate

From
IJIan Jackson <ijackson@chiark.greenend.org.uk>
Date
Nov 8, 2016, 13:42 UTC
Message-ID
<22561.54876.646018.985175@chiark.greenend.org.uk>
In-Reply-To
<0d7ff8e5-230a-c6e1-6663-eaecee5d5620@jump-ing.de>
Markus Hitter writes ("Re: [PATCH 0/6] Provide for config to specify tags not to abbreviate"):
> TBH, I see a violation of tool independence with the choice of
> preference storage. Abbreviation of tags isn't a property of the
> repository, but a pure visual thing (screen real estate, whatever),
> so it should be handled by the tool doing the visuals, only.

As I explained in my cover letter, the set of tags which are important enough not to abbreviate, even if they would normally be abbreviated, is indeed a property of the repository.

The alternative would be for a tool like gitk to grow an ever-increasing set of heuristics. Or, worse, for a tool like dgit (which knows that archive/* are special) to edit the user's personal gitk settings.

Show 5 quoted lines
> Your use case looks like a nice opportunity for
> 
> - adding a Gitk user preference on how long displayed tags are
>   allowed to be (instead of distinguishing between abbreviated and
>   unabbreviated ones; set it to 999 for your use case) and/or

This would be wrong, because it's only certain tags that ought not to be abbreviated. The right way to identify those tags is by 1. what repo they are in 2. what their name is. (It might be possible to identify them by content or something - for example, the interesting archive/* tags all refer to commits whose trees contain debian/ - but that is getting quite out of hand.)

What you propose are possible general improvements to the abbreviation system in gitk. But they do not address the fundamental point that some tags are much more interesting than others. It is this latter point that I am trying to deal with.

Ian.
-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Previous: Markus Hitter
Message 18 of 18 in “Provide for config to specify tags not to abbreviate”
  1. 0/6 Provide for config to specify tags not to abbreviateIan Jackson, Nov 8, 2016
  2. 3/6 gitk: drawtags: Introduce concept of unabbreviated marksIan Jackson, Nov 8, 2016
  3. 2/6 gitk: Internal: drawtags: Idempotently reset "ntags"Ian Jackson, Nov 8, 2016
  4. 1/6 gitk: Internal: drawtags: Abolish "singletag" variableIan Jackson, Nov 8, 2016
  5. 4/6 gitk: Provide for config to specify tags not to abbreviateIan Jackson, Nov 8, 2016
  6. 5/6 config docs: Provide for config to specify tags not to abbreviateIan Jackson, Nov 8, 2016
  7. Jacob KellerNov 8, 2016
  8. Ian JacksonNov 8, 2016
  9. Jeff KingNov 8, 2016
  10. Ian JacksonNov 9, 2016
  11. Junio C HamanoNov 9, 2016
  12. Ian JacksonNov 9, 2016
  13. Junio C HamanoNov 9, 2016
  14. Ian JacksonNov 9, 2016
  15. Markus HitterNov 10, 2016
  16. Ian JacksonNov 8, 2016
  17. Markus HitterNov 8, 2016
  18. Ian JacksonNov 8, 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.