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

Revisiting metadata storage

From
Richard Hartmann <richih.mailinglist@gmail.com>
Date
Nov 14, 2011, 00:07 UTC
Message-ID
<CAD77+gQB+0zJG62jrtPn_MwLLR7zgH=5gBtkvPxrKgiLPZsbsw@mail.gmail.com>
Hi all,

every few months, a thread seems to pop up regarding metadata storage, be it owner, mtime, xattr or what have you.

As of today there is (ttbomk) still no sane way to carry & restore metadata across different repositories.

metastore[1] is closest to a working solution but its storage format is binary and merge-unfriendly and it does not store mtime which is a deal-breaker, for me. I tried extend & fix metastore, but failed. Others looked at it, deemed it possible and lost interest and/or their development box.

I know from Joey Hess [2] that the GitTogether 2011 saw some discussion about metadata, but I was unable to find any follow-up to this issue.

To make a long story short: Does anyone have a working solution, today? If not, is anyone working on one? If not, is anyone interested in working on one? And is there any follow-up to the GitTogether discussion?

The feature set of any solution should probably include save, display, diff, and apply on a per-metadata and per-file basis.

Thanks, Richard

[1] http://david.hardeman.nu/software.php [2] http://kitenet.net/~joey/blog/entry/GitTogether2011/

Next: Jonathan Nieder
Message 1 of 7 in “Revisiting metadata storage”
  1. Richard HartmannNov 14, 2011
  2. Jonathan NiederNov 24, 2011
  3. Richard HartmannDec 14, 2011
  4. Hilco WijbengaDec 15, 2011
  5. Jonathan NiederDec 16, 2011
  6. Hilco WijbengaDec 16, 2011
  7. Jonathan NiederDec 17, 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.