From: Sverre Rabbelier <srabbelier@gmail.com>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: git@vger.kernel.org, Jakub Narebsk <jnareb@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Eric Raymond <esr@thyrsus.com>
Subject: Re: [RFC/PATCH v2 0/4] A new library for plumbing output
Date: Mon, 12 Apr 2010 01:35:26 +0200 [thread overview]
Message-ID: <l2jfabb9a1e1004111635v16e4dc86g405883ca12d316b9@mail.gmail.com> (raw)
In-Reply-To: <20100411231824.67460.24844.julian@quantumfyre.co.uk>
Heya,
On Mon, Apr 12, 2010 at 01:21, Julian Phillips <julian@quantumfyre.co.uk> wrote:
> Probably the biggest change from v1 is an expanded aim. Now the output library
> is aimed at controlling _all_ plubming output. This series includes a patch for
> ls-tree that has all it's output going through the library, and a patch for
> status that has all the --porcelain output going through the library.
I like where this is going, a lot, especially since we don't have to
convert everything in one go, but we can do it as desired, similar to
optparsification. I still think more commands than just these two
should be converted to validate the design though, perhaps something
like 'git blame', or 'git for-each-ref'?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-04-11 23:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 23:21 [RFC/PATCH v2 0/4] A new library for plumbing output Julian Phillips
2010-04-11 23:21 ` [RFC/PATCH v2 1/4] output: Add a " Julian Phillips
2010-04-13 9:43 ` Ilari Liusvaara
2010-04-13 11:46 ` Julian Phillips
2010-04-11 23:21 ` [RFC/PATCH v2 2/4] ls-tree: complete conversion to using output library Julian Phillips
2010-04-11 23:21 ` [RFC/PATCH v2 3/4] status: use output library for porcelain output Julian Phillips
2010-04-11 23:21 ` [RFC/PATCH v2 4/4] output: WIP: Add XML backend Julian Phillips
2010-04-11 23:35 ` Sverre Rabbelier [this message]
2010-04-12 0:46 ` [RFC/PATCH v2 0/4] A new library for plumbing output Eric Raymond
2010-04-14 19:10 ` Jakub Narebski
2010-04-14 19:13 ` Sverre Rabbelier
2010-04-14 21:42 ` Jakub Narebski
2010-04-14 19:32 ` Junio C Hamano
2010-04-14 20:12 ` Jakub Narebski
2010-04-14 20:38 ` Junio C Hamano
2010-04-14 21:29 ` Jakub Narebski
2010-04-14 21:34 ` Junio C Hamano
2010-04-15 6:57 ` Jeff King
2010-04-15 9:07 ` Jakub Narebski
2010-04-17 9:53 ` Jeff King
2010-04-17 13:02 ` Jakub Narebski
2010-04-17 14:00 ` Jeff King
2010-04-18 21:46 ` [RFC/PATCH v2 0/4] A new library for plumbing output (inc. current status) Julian Phillips
2010-04-19 19:40 ` Jeff King
2010-04-14 20:57 ` [RFC/PATCH v2 0/4] A new library for plumbing output Julian Phillips
2010-04-14 21:16 ` Jakub Narebski
2010-04-14 21:28 ` Julian Phillips
2010-04-15 7:15 ` Jeff King
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=l2jfabb9a1e1004111635v16e4dc86g405883ca12d316b9@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.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).