From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: 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: Wed, 14 Apr 2010 22:12:32 +0200 [thread overview]
Message-ID: <201004142212.33162.jnareb@gmail.com> (raw)
In-Reply-To: <7vwrw9q18m.fsf@alter.siamese.dyndns.org>
Dnia środa 14. kwietnia 2010 21:32, Junio C Hamano napisał:
> Jakub Narebski <jnareb@gmail.com> writes:
>
> > I don't think it is needed for either command.
> >
> > 'git blame' has --porcelain and --incremental output, which is line-based
> > and pretty much self-describing (with "header-name value" syntax for most
> > of it), and well documented. JSON output would only add unnecessary
> > chatter and different quoting rules.
>
> Wouldn't the exact same argument apply equally well to the output format
> of "status --porcelain", by the way? It is line-based and pretty much
> self-describing (once you know the mnemonic but you can make an educated
> guess from previous SCM experience).
No, current "git status --porcelain" output is record-based (tabular);
the meaning is not described by header but depends on field in record,
i.e. position in line.
Self describing output of "git status --porcelain" would be
filename <maybe-quoted filename>
renamed-from <maybe-quoted filename>
similarity 95%
worktree ...
index ...
or something like that...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-04-14 20:12 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 [this message]
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=201004142212.33162.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.