From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Julian Phillips <julian@quantumfyre.co.uk>,
git@vger.kernel.org, Eric Raymond <esr@thyrsus.com>
Subject: Re: [RFC/PATCH v2 0/4] A new library for plumbing output
Date: Sat, 17 Apr 2010 15:02:39 +0200 [thread overview]
Message-ID: <201004171502.42044.jnareb@gmail.com> (raw)
In-Reply-To: <20100417095259.GA23110@coredump.intra.peff.net>
On Sat, 17 Apr 2010, Jeff King wrote:
> On Thu, Apr 15, 2010 at 11:07:32AM +0200, Jakub Narebski wrote:
> > [1] A question: we have working area version, index version, and HEAD
> > version of file. Isn't it possible for *each* of them to have
> > different filename? What about the case of rename/rename merge
> > conflict?
[cut]
Thanks for detailed explanation.
> > Although if possible I'd like to have it wrapped in utility macros,
> > like parseopt, so one does not need to write output_str / output_int
> > etc.... but currently it is very, very vague sketch of an idea, rather
> > than realized concept.
>
> I'm not sure I understand what utility macros you would want.
Something like that (please remember that it is still in vague beginnings
of an idea stage:
OUT_OBJECT(
OUT_FIELD("mode", OUT_MODE, tree.mode), SP,
OUT_FIELD("type", "%s", tree.object.type), SP,
OUT_FIELD("object", OUT_SHA1, tree.object.sha1), TAB,
OUT_FIELD("file", OUT_FILE(sep), tree.filename),
sep
);
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-04-17 13:02 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 ` [RFC/PATCH v2 0/4] A new library for plumbing output Sverre Rabbelier
2010-04-12 0:46 ` 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 [this message]
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=201004171502.42044.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julian@quantumfyre.co.uk \
--cc=peff@peff.net \
--cc=srabbelier@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).