From: David Bremner <david@tethera.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: doc bug for git-patch-id ?
Date: Mon, 21 May 2012 10:37:29 -0300 [thread overview]
Message-ID: <87zk911wpy.fsf@zancas.localnet> (raw)
I just discovered that
git log -p $ref | git patch-id
works in place of a corresponding loop using git show | git patch-id
This makes a script I'm hacking on about 10 times faster.
Am I correct in thinking this should be documented better in the man
page? At least the intent of the source "generate_id_list" seems to be
to support multiple patches on stdin.
I can probably work up a doc patch; of course if somebody else actually
knows what the doc should say is welcome to write it ;).
David
next reply other threads:[~2012-05-21 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 13:37 David Bremner [this message]
2012-05-21 22:15 ` doc bug for git-patch-id ? Junio C Hamano
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=87zk911wpy.fsf@zancas.localnet \
--to=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