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

Re: How do you best store structured data in git repositories?

From
Avery Pennarun <apenwarr@gmail.com>
Date
Dec 4, 2009, 01:45 UTC
Message-ID
<32541b130912031745i60dc918dk3e510ef1a3b28526@mail.gmail.com>
In-Reply-To
<20091204001359.GA6709@gmail.com>
On Thu, Dec 3, 2009 at 7:14 PM, David Aguilar <davvid@gmail.com> wrote:
> JSON's not too bad for data structures and is known to
> be friendly to XML expats.
>
> http://json.org/

yaml is also really good for storing structured data, and its line-by-line format lends itself to easy merging (if you don't feel like writing a custom merge algorithm).

Have fun,
Avery
Previous: David AguilarNext: jamesmikedupont@googlemail.com
Message 4 of 7 in “How do you best store structured data in git repositories?”
  1. Sebastian SetzerDec 2, 2009
  2. Avery PennarunDec 2, 2009
  3. David AguilarDec 4, 2009
  4. Avery PennarunDec 4, 2009
  5. jamesmikedupont@googlemail.comDec 4, 2009
  6. Sebastian SetzerDec 7, 2009
  7. David AguilarDec 8, 2009

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.