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

Re: Improve tags

From
Jakub Narebski <jnareb@gmail.com>
Date
Mar 27, 2009, 14:15 UTC
Message-ID
<m3bprn2gs7.fsf@localhost.localdomain>
In-Reply-To
<49CCAAD3.4070104@gmail.com>
"Etienne Vallette d'Osia" <dohzya@gmail.com> writes:
Show 18 quoted lines
>  > You described your motivation and use case very clearly!
>  >
>  > Maybe "label" would be an appropriate name for "non-unique tags". I
>  > assume they should be local and non-versioned. It sounds as if a file
>  > storing a list of sha1s could be the simplest approach (one file per
>  > label in a new subdir of .git), although this may not scale well. A
>  > first step could be implementing a command "git label" in shell which
>  > sets and displays labels. Later on, various builtins would need to be
>  > taught about it if you want labels displayed in log etc.
> 
> Thanks a lot
> 
> "label" is perfect !
> 
> In fact, I was thinking about non-local labels.
> But keeping information in a separate file and not in commit directly
> is a very nice idea (and closer than the current tag implementation).
> I love your approach, you have just make this idea realizable

This is a bit argument for (abandoned / dropped) 'notes' commit header idea... But only a tiny bit.

More seriously: take a look at 'notes' idea; I'm not sure what state they are currently, but they are in active (more or less) development. They are extension of tags, allowing post-fact annotation of commits.

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Etienne Vallette d'OsiaNext: Etienne Vallette d'Osia
Message 4 of 7 in “Improve tags”
  1. Etienne Vallette d'OsiaMar 26, 2009
  2. Michael J GruberMar 26, 2009
  3. Etienne Vallette d'OsiaMar 27, 2009
  4. Jakub NarebskiMar 27, 2009
  5. Etienne Vallette d'OsiaMar 27, 2009
  6. Nanako ShiraishiMar 26, 2009
  7. Etienne Vallette d'OsiaMar 27, 2009

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.