git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Peter Vereshagin <peter@vereshagin.org>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: 'show' pretty %B without a diff
Date: Tue, 21 Dec 2010 12:04:59 -0600	[thread overview]
Message-ID: <20101221180459.GA25812@burratino> (raw)
In-Reply-To: <m38vzjl1yr.fsf@localhost.localdomain>

Jakub Narebski wrote:

> I guess that `-s' should be present also in git-show manpage.

It is mentioned in the examples section since v1.7.3.3~42.  That
manpage needs a rework in general, though.

> There is also `git log -1` (or `git log -1 --no-walk` for paranoid).

Or even "git diff-tree -s --pretty=%B <commit>" if that is the intent.

As much as a person might dislike plumbing, plumbing is git's current
stable API.  Maybe the libgit2 project will come up with something
better[1].  Until then, I am happy to have some commands that avoid
user-friendliness niceties (like implied "HEAD") that would create
pitfalls when scripting.

Maybe it would be worth adding a plumbing example under the EXAMPLES
for each porcelain?  I can see that having to learn a second set of
commands might make life hard (like scripting in the bourne shell
when one is a csh user).

[1] I am pessimistic since that project has not made itself very
visible for feedback from the git list or submitted changes back to
git.  It would be great to be surprised.

  reply	other threads:[~2010-12-21 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
2010-12-21 11:04       ` Peter Vereshagin
2010-12-21 12:56         ` Jakub Narebski
2010-12-21 18:04           ` Jonathan Nieder [this message]
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=20101221180459.GA25812@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --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).