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

RE: git branch descriptions

From
JRJoel Reed <jreed@lantekcs.com>
Date
May 11, 2010, 12:38 UTC
Message-ID
<657A681BEF27534399890012B8C8E50E1AD63D2241@lcs-exchange01.Lantekcs.com>
In-Reply-To
<F658FEF6-8957-4815-8917-8545E166F6CC@adacore.com>
Geert Bosch wrote:
<snip>
Show 5 quoted lines
> It seems if we'd do branch descriptions at all, their main use
> would be fore remote repositories. When you publish a branch,
> you'd typically not rewrite it on a whim, so attaching a description
> makes sense. Similarly, if you're tracking a remote repository,
> it would be helpful to get some information for the branch.
For my usage, I have to strongly disagree! I _primarily_ wish I could add a description to LOCAL branches.
jr
Previous: Geert BoschNext: Michael J Gruber
Message 5 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.