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

Re: branch description

From
MDMichael Dressel <michaeltilodressel@t-online.de>
Date
Apr 22, 2008, 17:57 UTC
Message-ID
<alpine.DEB.1.10.0804221945060.3452@pollux.milkiway.cos>
On Friday 18 April 2008, Jakub Narebski wrote:
> Let me sum up here proposals where to put branch description:

what's the opinion of having a new branch object? Actually the tag object probably already does the job? This would spoil the elegant light weight current branch references. But tags are not that heavy.

In this approach the tags would not reference commits but tags. And tags have annotation. The difference to the normal tags would be that these tags are referenced from refs/heads/<branch> instead of refs/tags.

I have no clue how involved this change would become and if the benefit would justify the effort. I guess using proper objects for branches would only be justified if additional advantages could be achieved.

Cheers,
 	Michael
Next: Johan Herland
Message 1 of 3 in “Re: branch description”
  1. Michael DresselApr 22, 2008
  2. Johan HerlandApr 22, 2008
  3. Jakub NarebskiApr 22, 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.