From: Martin Langhoff <martin.langhoff@gmail.com>
To: esr@thyrsus.com
Cc: Jakub Narebski <jnareb@gmail.com>, Simon <turner25@gmail.com>,
Eric Raymond <esr@snark.thyrsus.com>,
git@vger.kernel.org
Subject: Re: More git status --porcelain lossage
Date: Sat, 10 Apr 2010 16:31:55 -0400 [thread overview]
Message-ID: <s2i46a038f91004101331g1cdca78cya3e125275446a0a9@mail.gmail.com> (raw)
In-Reply-To: <20100410194154.GB28768@thyrsus.com>
On Sat, Apr 10, 2010 at 3:41 PM, Eric Raymond <esr@thyrsus.com> wrote:
>> I could understand providing JSON format, specified using --json
>> option.
>
> You know, that's actually an interesting idea. I mentioned it
> previously as the not-XML if we want to build on a metaprotocol;
One issue is that there's no stream-parser JSON implementations that
I'm aware of.
Everthing I've seen is in-memory, therefore apt only for memory-bound
operations. Not sure if all commands with -z output options can be
assumed to produce bound-sized datasets.
cheers,
martin
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2010-04-10 20:32 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 [this message]
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
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=s2i46a038f91004101331g1cdca78cya3e125275446a0a9@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=turner25@gmail.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).