[PATCH] Documentation: git-cherry uses git-patch-id
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 29, 2008, 00:04 UTC
- Message-ID
- <7v7idern4q.fsf_-_@gitster.siamese.dyndns.org>
- In-Reply-To
- <7f9d599f0805281414x6b97070ag7a1cc36f5d3c5a36@mail.gmail.com>
"Geoffrey Irving" <irving@naml.us> writes:
Show 8 quoted lines
> On Wed, May 28, 2008 at 1:46 PM, Junio C Hamano <gitster@pobox.com> wrote: > >> Thanks. >> >> In manual pages, "SEE ALSO" section is a more appropriate place to do this >> kind of thing. > > Here's an improved patch.
Thanks, I'll do this instead...
-- >8 -- Geoffrey Irving noticed that git-cherry talks about comparing commits without hinting how they are compared.
Signed-off-by: Junio C Hamano <gitster@pobox.com> --- Documentation/git-cherry.txt | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-cherry.txt b/Documentation/git-cherry.txt index b0468aa..d8e0a5b 100644 --- a/Documentation/git-cherry.txt +++ b/Documentation/git-cherry.txt @@ -13,6 +13,8 @@ DESCRIPTION ----------- The changeset (or "diff") of each commit between the fork-point and <head> is compared against each commit between the fork-point and <upstream>. +The commits are compared with their 'patch id', obtained from linkgit:git-patch-id[1] +program. Every commit that doesn't exist in the <upstream> branch has its id (sha1) reported, prefixed by a symbol. The ones that have @@ -56,6 +58,10 @@ OPTIONS <limit>:: Do not report commits up to (and including) limit. +SEE ALSO +-------- +linkgit:git-patch-id[1] + Author ------ Written by Junio C Hamano <junkio@cox.net>
-- 1.5.6.rc0.43.g823ea