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

Re: [RFC] GIT Repository Annotation Convention

From
Matthias Urlichs <smurf@smurf.noris.de>
Date
Sep 13, 2005, 17:46 UTC
Message-ID
<pan.2005.09.13.17.45.59.307129@smurf.noris.de>
In-Reply-To
<43247298.2010500@gmail.com>
Hi, A Large Angry SCM wrote:
>> I propose using no extensions whatsoever: simply mirror the refs/ tree.
> 
> The extensions allow the annotation of directories as well as files. 
> That's something that can't be done if extensions are not used.

IMHO, that is the sort of information that's best saved in the "how is our source organized" section of your ./HACKING file.

Or you can simply use reiserfs4, with its files-are-directories feature. (*ducks and runs*)

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
Ask yourself whether you are happy and you cease to be so.
Previous: A Large Angry SCMNext: A Large Angry SCM
Message 9 of 11 in “git/gitweb - feature request: Add description to the branches.”
  1. Santi BéjarSep 6, 2005
  2. A Large Angry SCMSep 6, 2005
  3. Junio C HamanoSep 8, 2005
  4. [RFC] GIT Repository Annotation ConventionA Large Angry SCM, Sep 8, 2005
  5. Junio C HamanoSep 8, 2005
  6. A Large Angry SCMSep 8, 2005
  7. Matthias UrlichsSep 11, 2005
  8. A Large Angry SCMSep 11, 2005
  9. Matthias UrlichsSep 13, 2005
  10. A Large Angry SCMSep 8, 2005
  11. A Large Angry SCMSep 9, 2005

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.