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

Re: git branch descriptions

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 11, 2010, 12:54 UTC
Message-ID
<AANLkTimhCBNyJv6b9AT578AC4H1_zsB2CgfsrveNpNNE@mail.gmail.com>
In-Reply-To
<657A681BEF27534399890012B8C8E50E1AD63D1FEA@lcs-exchange01.Lantekcs.com>
On Mon, May 10, 2010 at 14:56, Joel Reed <jreed@lantekcs.com> wrote:
> I like to keep branch names short so they're easy to switch to and
> from, but being able to attach a description that would display when
> doing a "git branch" would be a huge help.

Or you could just use long branch names coupled with bash completion (or something like that) so it isn't hard to switch between branches with long names.

I use branch names that are long enough so that I can tell what they're for by looking at the name, using them isn't a pain due to bash/magit completion.

Previous: Joel ReedNext: Joel Reed
Message 9 of 10 in “git branch descriptions”
  1. Joel ReedMay 10, 2010
  2. Ramkumar RamachandraMay 10, 2010
  3. Jonathan NiederMay 10, 2010
  4. Geert BoschMay 11, 2010
  5. Joel ReedMay 11, 2010
  6. Michael J GruberMay 11, 2010
  7. Joel ReedMay 11, 2010
  8. Joel ReedMay 11, 2010
  9. Ævar Arnfjörð BjarmasonMay 11, 2010
  10. Joel ReedMay 11, 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.