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

Re: Feature Request: Branch Annotations

From
Peter Krefting <peter@softwolves.pp.se>
Date
Oct 10, 2008, 08:24 UTC
Message-ID
<Pine.LNX.4.64.0810100922180.10709@ds9.cixit.se>
In-Reply-To
<32541b130810081621k32493e20occba9cd97671775d@mail.gmail.com>
Avery Pennarun:
Show 5 quoted lines
> I guess bash completions would help with this (if you're using bash),
> but even then it's kind of unreasonable to name branches something
> like "bug-111234-widget-performance-improvements-for-customer-x",
> which is the sort of information that would be awfully helpful two
> months later when you're looking at old unmerged branches.

That's exactly what I do for one of the projects I am working on (well, minus the "bug-" prefix, that's implied). Bash completion works quite well for that, and the merge commits do give meaningful information.

But I would still like to be able to annotate it. Especially for long-living bug-fix branches, it could be useful to be able to add describe a branch with what state it is in, for instance.

-- 
\\// Peter - http://www.softwolves.pp.se/
Previous: Miklos Vajna
Message 10 of 10 in “Feature Request: Branch Annotations”
  1. Rotem YaariOct 8, 2008
  2. Thomas AdamOct 8, 2008
  3. BazOct 8, 2008
  4. Marc WeberOct 8, 2008
  5. David Soria ParraOct 8, 2008
  6. Junio C HamanoOct 8, 2008
  7. David Soria ParraOct 8, 2008
  8. Avery PennarunOct 8, 2008
  9. Miklos VajnaOct 9, 2008
  10. Peter KreftingOct 10, 2008

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.