Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: David Bremner <david@tethera.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: doc bug for git-patch-id ?
Date: Mon, 21 May 2012 15:15:24 -0700	[thread overview]
Message-ID: <7vipfp6v0j.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <87zk911wpy.fsf@zancas.localnet> (David Bremner's message of "Mon, 21 May 2012 10:37:29 -0300")

David Bremner <david@tethera.net> writes:

> I just discovered that 
>   
>   git log -p $ref | git patch-id 
>
> works in place of a corresponding loop using git show | git patch-id

I think it has been designed to work that way from very early days.
Patches to clarify documentation, if the current one is lacking, is very
much welcomed.

Thanks.

      reply	other threads:[~2012-05-21 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 13:37 doc bug for git-patch-id ? David Bremner
2012-05-21 22:15 ` Junio C Hamano [this message]

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=7vipfp6v0j.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=david@tethera.net \
    --cc=git@vger.kernel.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