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

Re: Tracking file metadata in git -- fix metastore or enhance git?

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Apr 8, 2011, 18:59 UTC
Message-ID
<20110408185924.GA25840@elie>
In-Reply-To
<4D9EDCEA.9010903@drmicha.warpmail.net>
Hi,
Michael J Gruber wrote:
Show 5 quoted lines
> Note that etckeeper and metastore predate our notes feature. By now, a
> notes tree is a perfect place to store meta information. You can attach
> notes to blobs perfectly (see textconv-cache). That may be an option for
> a reimplementation, depending on how you want the versioning of the
> files to be related with the versioning of the meta data.

Wouldn't that mean the same content couldn't have one owner in one commit and a different owner in another commit?

I think the most native-looking way to store metadata associated to paths is .gitattributes. It also has the nice feature of allowing a single attribute to apply to multiple files. But the tools for looking them up (e.g., git check-attr) do not get much use yet so they probably could use a lot of improvement.

Previous: Michael J GruberNext: Thorsten Glaser
Message 5 of 19 in “Tracking file metadata in git -- fix metastore or enhance git?”
  1. Richard HartmannApr 7, 2011
  2. Thorsten GlaserApr 7, 2011
  3. Richard HartmannApr 8, 2011
  4. Michael J GruberApr 8, 2011
  5. Jonathan NiederApr 8, 2011
  6. Thorsten GlaserApr 8, 2011
  7. Jonathan NiederApr 8, 2011
  8. Thorsten GlaserApr 8, 2011
  9. Richard HartmannApr 8, 2011
  10. Chris WebbApr 9, 2011
  11. Richard HartmannApr 9, 2011
  12. Jonathan NiederApr 10, 2011
  13. Junio C HamanoApr 10, 2011
  14. Richard HartmannApr 10, 2011
  15. Richard HartmannApr 11, 2011
  16. Richard HartmannApr 18, 2011
  17. Jonathan NiederApr 18, 2011
  18. johnnyutahhDec 14, 2011
  19. Richard HartmannDec 20, 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.