git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: David Aguilar <davvid@gmail.com>
Cc: sebastianspublicaddress@googlemail.com, git@vger.kernel.org
Subject: Re: How do you best store structured data in git repositories?
Date: Thu, 3 Dec 2009 20:45:21 -0500	[thread overview]
Message-ID: <32541b130912031745i60dc918dk3e510ef1a3b28526@mail.gmail.com> (raw)
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

  reply	other threads:[~2009-12-04  1:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 21:08 How do you best store structured data in git repositories? Sebastian Setzer
2009-12-02 21:17 ` Avery Pennarun
2009-12-04  0:14   ` David Aguilar
2009-12-04  1:45     ` Avery Pennarun [this message]
2009-12-04  8:00       ` jamesmikedupont
2009-12-07 21:20     ` Sebastian Setzer
2009-12-08  7:14       ` David Aguilar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32541b130912031745i60dc918dk3e510ef1a3b28526@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sebastianspublicaddress@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).