git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: cherry picking changesets instead of commits

From
Junio C Hamano <gitster@pobox.com>
Date
May 28, 2008, 20:46 UTC
Message-ID
<7v3ao2tawd.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<7f9d599f0805281242w5769a100s1153c2101992ff55@mail.gmail.com>
"Geoffrey Irving" <irving@naml.us> writes:
Show 17 quoted lines
> 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.

Previous: Geoffrey IrvingNext: Geoffrey Irving
Message 6 of 13 in “cherry picking changesets instead of commits”
  1. Geoffrey IrvingMay 28, 2008
  2. Junio C HamanoMay 28, 2008
  3. Geoffrey IrvingMay 28, 2008
  4. Junio C HamanoMay 28, 2008
  5. Geoffrey IrvingMay 28, 2008
  6. Junio C HamanoMay 28, 2008
  7. Geoffrey IrvingMay 28, 2008
  8. Jeff KingMay 28, 2008
  9. Jeff KingMay 28, 2008
  10. Junio C HamanoMay 28, 2008
  11. Jeff KingMay 29, 2008
  12. Documentation: git-cherry uses git-patch-idJunio C Hamano, May 29, 2008
  13. Geoffrey IrvingMay 29, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.