From: David Aguilar <davvid@gmail.com>
To: Sebastian Setzer <sebastianspublicaddress@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: How do you best store structured data in git repositories?
Date: Mon, 7 Dec 2009 23:14:09 -0800 [thread overview]
Message-ID: <20091208071356.GA4970@gmail.com> (raw)
In-Reply-To: <1260220821.3545.12.camel@nord26-amd64>
On Mon, Dec 07, 2009 at 10:20:21PM +0100, Sebastian Setzer wrote:
> On Thursday, Dec 03 2009 at 16:14 -0800, David Aguilar wrote:
> > On Wed, Dec 02, 2009 at 04:17:10PM -0500, Avery Pennarun wrote:
> > > On Wed, Dec 2, 2009 at 4:08 PM, Sebastian Setzer
> > > <sebastianspublicaddress@googlemail.com> wrote:
> > > > Do you use XML for this purpose?
> > >
> > > XML is terrible for most data storage purposes.
> >
> > I agree 100%.
> >
> > JSON's not too bad for data structures and is known to
> > be friendly to XML expats.
> >
> Sorry, I didn't want to start a flamewar against XML. I'm no big friend
> of XML myself, but I don't know of an (open source) diff-/merge tool for
> any general purpose file format other than XML or plain text.
> When you mention other formats, I'd be interested in
> - why this format is good for storage in git
> - if there are merge tools available which ensure that, after a merge,
> the structure (and maybe additional contraints) is still valid.
>
> Thanks for your comments,
> Sebastian
Sorry, didn't mean to sound xml-flaming. The only reason for
mentioning json, yaml, etc. is that they're good data structure
formats. They're all plain text formats, so you can use existing
diff/merge tools.
I guess none of this has much to do with git aside from being
able to write custom merge drivers to operate on them as data.
If there's a diff/merge tool for xml that works well then
hooking it up to git-{diff,merge}tool might be something
to try too.
--
David
prev parent reply other threads:[~2009-12-08 7:13 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
2009-12-04 8:00 ` jamesmikedupont
2009-12-07 21:20 ` Sebastian Setzer
2009-12-08 7:14 ` David Aguilar [this message]
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=20091208071356.GA4970@gmail.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.