From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Julian Phillips <julian@quantumfyre.co.uk>,
git@vger.kernel.org, Eric Raymond <esr@thyrsus.com>
Subject: Re: [RFC/PATCH 2/3] add a library of code for producing structured output
Date: Sun, 11 Apr 2010 20:26:00 +0200 [thread overview]
Message-ID: <s2hfabb9a1e1004111126i6822abc1ne0e0e5bad6f4ac7@mail.gmail.com> (raw)
In-Reply-To: <7vy6gtonwt.fsf@alter.siamese.dyndns.org>
Heya,
On Sun, Apr 11, 2010 at 20:16, Junio C Hamano <gitster@pobox.com> wrote:
> I was hoping that the existing low-level -z routines (e.g. "diff-* -z")
> follow similar enough patterns to have a corresponding output-z.c and be
> handled inside output.c library. But that is not a requirement, just
> "would have been nicer if the original were written that way".
I like that idea, I think it would make our plumbing interface more
consistent, and further validate the API design. Any plumbing command
(once converted) can then be used with -z (or --format=zero or
whatever it is) and give a similar output format, very nice.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-04-11 18:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 11:37 [RFC/PATCH 0/3] JSON/XML output for scripting interface Julian Phillips
2010-04-11 11:37 ` [RFC/PATCH 1/3] strbuf: Add strbuf_vaddf function Julian Phillips
2010-04-11 12:42 ` Erik Faye-Lund
2010-04-11 12:59 ` Julian Phillips
2010-04-11 11:37 ` [RFC/PATCH 2/3] add a library of code for producing structured output Julian Phillips
2010-04-11 12:51 ` Erik Faye-Lund
2010-04-11 13:03 ` Julian Phillips
2010-04-11 15:46 ` Jakub Narebski
2010-04-11 18:16 ` Junio C Hamano
2010-04-11 18:26 ` Sverre Rabbelier [this message]
2010-04-11 19:21 ` Julian Phillips
2010-04-11 20:34 ` Jakub Narebski
2010-04-11 20:46 ` Julian Phillips
2010-04-11 20:57 ` Eric Raymond
2010-04-11 11:37 ` [RFC/PATCH 3/3] status: add support for " Julian Phillips
2010-04-11 15:48 ` [RFC/PATCH 0/3] JSON/XML output for scripting interface Sverre Rabbelier
2010-04-11 17:30 ` Julian Phillips
2010-04-11 17:34 ` Sverre Rabbelier
2010-04-11 17:45 ` Julian Phillips
2010-04-11 17:50 ` Sverre Rabbelier
2010-04-11 22:22 ` Jon Seymour
2010-04-11 22:34 ` Eric Raymond
2010-04-11 23:25 ` Jon Seymour
2010-04-11 23:30 ` Julian Phillips
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=s2hfabb9a1e1004111126i6822abc1ne0e0e5bad6f4ac7@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julian@quantumfyre.co.uk \
/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).