From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 28 May 2008 20:46:10 GMT
Subject: Re: cherry picking changesets instead of commits
Message-ID: <7v3ao2tawd.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <7f9d599f0805281242w5769a100s1153c2101992ff55@mail.gmail.com>

"Geoffrey Irving" <irving@naml.us> writes:

> commit a1bac5e1aa52f9a78733aa35a0a7e820df618301
> Author: Geoffrey Irving <irving@naml.us>
> Date:   Wed May 28 12:38:11 2008 -0700
>
>     doc: mention git-patch-id in git-cherry documentation
>
> diff --git a/Documentation/git-cherry.txt b/Documentation/git-cherry.txt
> index b0468aa..9817fb5 100644
> --- a/Documentation/git-cherry.txt
> +++ b/Documentation/git-cherry.txt
> @@ -41,6 +41,8 @@ has been applied <upstream> under a different commit
> id.  For example,
>  this will happen if you're feeding patches <upstream> via email rather
>  than pushing or pulling commits directly.
>
> +For details about how patches are compared, see git-patch-id.
> +

Thanks.

In manual pages, "SEE ALSO" section is a more appropriate place to do this
kind of thing.