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

Re: More support on branch description?

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 19, 2012, 22:22 UTC
Message-ID
<7v4nvrib7u.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CACsJy8D0_EB6jN7KxpzLtnPnj0HjdU6sNHJRyqXJf-2-ZNatFA@mail.gmail.com>
Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
> The coming v1.7.9 will introduce branch description, mainly used in
> integration process. I think we could make it useful for users who
> don't extensively use request-pull/format-patch. Showing a short
> summary along with branch name in "git branch" would be nice.

I agree that it would be nice to give users access to the information even if the branch ends up being merged to the master branch by you and never leaves your repository by itself.

You however are misguided to say "Showing a short summary along...".

The branch description support is to give users a place to record detailed explanation about a branch, similar in size to what you would normally place in a log message of a commit or a cover letter of a series. There wasn't any convenient place to do so for a branch that is (1) inherently a moving target while it is being developed and (2) is not a good match for tags and notes.

There already is a good place for a brief summary and it is called "branch name". Name your branches just like you name your functions.

Previous: Nguyen Thai Ngoc DuyNext: Nguyen Thai Ngoc Duy
Message 4 of 5 in “More support on branch description?”
  1. Nguyen Thai Ngoc DuyJan 19, 2012
  2. Michael SchubertJan 19, 2012
  3. Nguyen Thai Ngoc DuyJan 19, 2012
  4. Junio C HamanoJan 19, 2012
  5. Nguyen Thai Ngoc DuyJan 20, 2012

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.