From: Simon <turner25@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: esr@thyrsus.com, Eric Raymond <esr@snark.thyrsus.com>,
git@vger.kernel.org
Subject: Re: More git status --porcelain lossage
Date: Sat, 10 Apr 2010 17:24:35 -0400 [thread overview]
Message-ID: <p2u5f14cf5e1004101424q2d6a871fs2466988f7a4202fe@mail.gmail.com> (raw)
In-Reply-To: <h2t51dd1af81004101239pe340cc54lcbb1a5b3702ec091@mail.gmail.com>
> A lot of web services (like some Catalyst-based applications) support
> all of these equally. If Git had machine readable output like this it
> would be nice if every git-* program just had --format=* where * could
> be xml, json, yaml, sexp, perl etc.
>
> The program would just construct a native datastructure and then there
> would be an output driver to generate the textual representation.
>
I had something just like this in mind when I suggested XML...
I would personally avoid it for same reasons others have pointed out, but...
There are lots of tools out there that can parse and display XML very
well natively. Firefox is one such example.
My intention is not to start a flame here, rather try to keep our
options flexible. ASCII would clearly remain the default though! ;)
Simon
prev parent reply other threads:[~2010-04-10 21:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 19:06 More git status --porcelain lossage Eric Raymond
2010-04-09 19:09 ` Eric Raymond
2010-04-09 19:22 ` Jakub Narebski
2010-04-09 19:50 ` Eric Raymond
2010-04-10 4:12 ` Jeff King
2010-04-10 4:14 ` Jeff King
2010-04-10 18:48 ` Simon
2010-04-10 19:01 ` Jakub Narebski
2010-04-10 19:41 ` Eric Raymond
2010-04-10 20:31 ` Martin Langhoff
2010-04-10 22:28 ` Paolo Bonzini
2010-04-10 23:06 ` Eric Raymond
2010-04-11 11:04 ` David Aguilar
2010-04-10 21:21 ` Jakub Narebski
2010-04-10 22:57 ` Eric Raymond
2010-04-10 19:30 ` Eric Raymond
2010-04-10 19:39 ` Ævar Arnfjörð Bjarmason
2010-04-10 21:24 ` Simon [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=p2u5f14cf5e1004101424q2d6a871fs2466988f7a4202fe@mail.gmail.com \
--to=turner25@gmail.com \
--cc=avarab@gmail.com \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
/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).