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

Storing state in $GIT_DIR

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Aug 25, 2005, 03:32 UTC
Message-ID
<46a038f905082420323b025e3b@mail.gmail.com>

Is there a convention of where/how it is safe to store additional (non-git) data in $GIT_DIR?

The arch import needs to keep a cache with arch-commit-id = git-commit-id mappings, and some notes about what patch-trading Arch recorded. It'd be great to be able to store those in $GIT_DIR/archimport/ . Is that supported?

It does not need to be replicated with push or pull, merely preserved. 
cheers,
martin
Next: Linus Torvalds
Message 1 of 17 in “Storing state in $GIT_DIR”
  1. Martin LanghoffAug 25, 2005
  2. Linus TorvaldsAug 25, 2005
  3. Martin LanghoffAug 26, 2005
  4. Linus TorvaldsAug 26, 2005
  5. Martin LanghoffAug 26, 2005
  6. Junio C HamanoAug 26, 2005
  7. Daniel BarkalowAug 26, 2005
  8. Linus TorvaldsAug 26, 2005
  9. Junio C HamanoAug 26, 2005
  10. Linus TorvaldsAug 27, 2005
  11. Junio C HamanoAug 26, 2005
  12. Martin LanghoffAug 26, 2005
  13. Eric W. BiedermanAug 26, 2005
  14. Martin LanghoffAug 26, 2005
  15. Eric W. BiedermanAug 26, 2005
  16. Accept -m and friends for initial commits and merge commits.Junio C Hamano, Aug 26, 2005
  17. Martin LanghoffAug 26, 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.