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

Re: Feature Request: Branch Annotations

From
David Soria Parra <sn_@gmx.net>
Date
Oct 8, 2008, 23:20 UTC
Message-ID
<48ED404C.2000405@gmx.net>
In-Reply-To
<7vwsgiptph.fsf@gitster.siamese.dyndns.org>
Show 9 quoted lines
> Haven't people watched Linus on google tech talk?  Here is an excerpt from
> the transcript (http://git.or.cz/gitwiki/LinusTalk200705Transcript):
> 
>     ... well actually you shouldn't call it "test", you should basically
>     name your branches the way you name your functions, you should call
>     them something short and sweet and to the point -- What is that branch
>     doing.
> 
> IOW, why did you name the branch "ds/fix" and not "ds/fix-bla"?

Okay I just choosed a bad example. Actually I call it ds/fix-function, but nevertheless more additional description can be useful when dealing with a lot of branches. But yes, there might be porcelains that can do that.

Previous: Junio C HamanoNext: Avery Pennarun
Message 7 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.