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

Re: [RFC] Support for arbitrary tags in commits

From
Thomas Rast <trast@student.ethz.ch>
Date
Jan 11, 2011, 12:40 UTC
Message-ID
<201101111340.50508.trast@student.ethz.ch>
In-Reply-To
<74b0628dffbd2bc0adabe5e8b0a10960.squirrel@webmail.hitco.org>
Philipp Marek wrote:
> 
> The best way I've found (so far) is to put an additional header line in the
> commit header that references an additional blob.

This comes up every few months. The last large discussion about this that we had IIRC was

  http://thread.gmane.org/gmane.comp.version-control.git/138848

Can you please look through that thread and state in what way your use-case invalidates the previous reasoning?

In particular, in what way do notes (as in git-notes(1)) fail to solve your problem?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Philipp MarekNext: Philipp Marek
Message 2 of 4 in “[RFC] Support for arbitrary tags in commits”
  1. Philipp MarekJan 11, 2011
  2. Thomas RastJan 11, 2011
  3. Philipp MarekJan 11, 2011
  4. Thomas RastJan 11, 2011

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.