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

Re: FEATURE REQUEST: Comment assignment on branches

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Mar 16, 2010, 14:36 UTC
Message-ID
<fcaeb9bf1003160736w7749f358p6ee8f86e6c3a32c6@mail.gmail.com>
In-Reply-To
<4B9EA22E.1010103@lsrfire.ath.cx>
On 3/16/10, René Scharfe <rene.scharfe@lsrfire.ath.cx> wrote:
Show 25 quoted lines
> Am 15.03.2010 09:33, schrieb Maxim Treskin:
>
> > Hello
>  >
>  > Is it possible to add comments assignment to branches?
>  > Something like:
>  >
>  > $ git branch --comment="New branch with implementation of some features" br14
>  >
>  > $ git branch
>  >   br14
>  > * master
>  >
>  > $ git branch --comments
>  >   br14           (New branch with implementation of some features)
>  > * master
>  >
>  > and when configuration variable branch.comments == true, this behavior
>  > is default.
>
>
> Hmm.  You could name your branch
>  "br14/new-branch-with-implementation-of-some-features" instead of
>  "br14".  With command line completion you would only have to hit two
>  extra keys (slash tab) and could enjoy a meaningful branch name everywhere.

If only completion works across shells. Another idea: put notes in a blob, tagged with "notes/branchname" or another convention.

Then if you want to see description of branch "br14", do "git show notes/br14". Teaching "git branch" to show it is easy.

-- 
Duy
Previous: Junio C HamanoNext: Nicolas Sebrecht
Message 6 of 13 in “FEATURE REQUEST: Comment assignment on branches”
  1. Maxim TreskinMar 15, 2010
  2. René ScharfeMar 15, 2010
  3. Junio C HamanoMar 15, 2010
  4. Mark LodatoMar 16, 2010
  5. Junio C HamanoMar 16, 2010
  6. Nguyen Thai Ngoc DuyMar 16, 2010
  7. Nicolas SebrechtMar 15, 2010
  8. Junio C HamanoMar 15, 2010
  9. Miles BaderMar 16, 2010
  10. Junio C HamanoMar 16, 2010
  11. Miles BaderMar 16, 2010
  12. Sverre RabbelierMar 16, 2010
  13. Matthieu MoyMar 16, 2010

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.