From: Junio C Hamano <gitster@pobox.com>
To: Peter Vereshagin <peter@vereshagin.org>
Cc: git@vger.kernel.org
Subject: Re: 'show' pretty %B without a diff
Date: Mon, 20 Dec 2010 10:05:16 -0800 [thread overview]
Message-ID: <7v4oa8cobn.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20101220111214.GD10354@external.screwed.box> (Peter Vereshagin's message of "Mon\, 20 Dec 2010 14\:12\:15 +0300")
Peter Vereshagin <peter@vereshagin.org> writes:
> JCH> Especially if you are doing a script, you probably should be using
> JCH> "cat-file commit" anyway, no?
>
> cat-file doesn't seem to support formatting option?
That is exactly why I suggested "cat-file", as you are scripting. We
reserve the right to change the human-visible formatting output from
Porcelain commands like "show" any time to make it "prettier" (we may
start coloring strings that look like object names in the commit log
message in "git show" output, for example), while giving scripts more
stable output through the plumbing commands like "cat-file" so that they
can parse and process without having to worry about the output format
changing under them.
If your script is _not_ parsing the git command output, but is just
blindly spewing it out to the invoking user, it is Ok to use "show",
though. Check "-s" option to the "show" command in that case.
next prev parent reply other threads:[~2010-12-20 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 7:38 'show' pretty %B without a diff Peter Vereshagin
2010-12-20 9:05 ` Junio C Hamano
2010-12-20 11:12 ` Peter Vereshagin
2010-12-20 18:05 ` Junio C Hamano [this message]
2010-12-21 11:04 ` Peter Vereshagin
2010-12-21 12:56 ` Jakub Narebski
2010-12-21 18:04 ` Jonathan Nieder
2010-12-21 20:27 ` Martin Langhoff
2010-12-21 20:40 ` Jakub Narebski
2010-12-22 18:33 ` peter
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=7v4oa8cobn.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peter@vereshagin.org \
/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).