Re: cherry picking changesets instead of commits
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:44:39
Possibly related (same subject, not in this thread)
- 2016-06-15 · cherry picking changesets instead of commits · Geoffrey Irving <hidden>
- 2016-06-15 · Re: cherry picking changesets instead of commits · Junio C Hamano <hidden>
- 2016-06-15 · Re: cherry picking changesets instead of commits · Geoffrey Irving <hidden>
- 2016-06-15 · Re: cherry picking changesets instead of commits · Junio C Hamano <hidden>
- 2016-06-15 · Re: cherry picking changesets instead of commits · Geoffrey Irving <hidden>
"Geoffrey Irving" [off-list ref] writes:
quoted hunk
commit a1bac5e1aa52f9a78733aa35a0a7e820df618301 Author: Geoffrey Irving [off-list ref] Date: Wed May 28 12:38:11 2008 -0700 doc: mention git-patch-id in git-cherry documentationdiff --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 commitid. 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.