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

git-cherry and fork-point

From
FMFrancis Moreau <francis.moro@gmail.com>
Date
Feb 16, 2011, 15:13 UTC
Message-ID
<AANLkTimNqzQc9vJmW_oKOgkGdM0bbff1SB9ZZBoXx--E@mail.gmail.com>
Hello
I'd like to understand what's the 'fork-point' in the git-cherry documentation.
For example, if I have this configuration:
                                 __*__*__*__*__> <upstream>
                                /
                 *__A__*__*__*__B__*
                     \
                      \__+__+__-__+__+__-__+__> <head>
what's the 'fork-point' for respectively those two commands:
       $ git cherry upstream head B
       $ git cherry head upstream A
I would say A and B, but I'm not sure and the documentation doesn't help.
Could anybody clarify this point ?
Thanks
-- 
Francis
Message 1 of 1 in “git-cherry and fork-point”
  1. Francis MoreauFeb 16, 2011

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.