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

[RFC/PATCH 0/5] add a --strategy option to "git cherry-pick"

From
Christian Couder <chriscool@tuxfamily.org>
Date
Mar 25, 2010, 04:58 UTC
Message-ID
<20100325045519.14832.65964.chriscool@tuxfamily.org>

The purpose of this series is to make it possible to test how "git cherry-pick" would work with another merge strategy than the recursive one.

Junio suggested:

"It might not be a bad idea to teach a hidden primarily-for-debugging option to "cherry-pick" to let it use resolve instead of recursive for cases like this."

Christian Couder (5):
  revert: use strbuf to refactor the code that writes the merge message
  revert: refactor merge recursive code into its own function
  merge: refactor code that calls "git merge-STRATEGY"
  merge: make function try_merge_command non static
  revert: add "--strategy" option to choose merge strategy
 builtin/merge.c   |   81 ++++++++++++++-----------
 builtin/revert.c  |  174 ++++++++++++++++++++++++++++++----------------------
 cache.h           |    3 -
 merge-recursive.h |    4 +
 4 files changed, 149 insertions(+), 113 deletions(-)
Next: Christian Couder
Message 1 of 6 in “add a --strategy option to "git cherry-pick"”
  1. 0/5 add a --strategy option to "git cherry-pick"Christian Couder, Mar 25, 2010
  2. 1/5 revert: use strbuf to refactor the code that writes the merge messageChristian Couder, Mar 25, 2010
  3. 2/5 revert: refactor merge recursive code into its own functionChristian Couder, Mar 25, 2010
  4. 3/5 merge: refactor code that calls "git merge-STRATEGY"Christian Couder, Mar 25, 2010
  5. 4/5 merge: make function try_merge_command non staticChristian Couder, Mar 25, 2010
  6. 5/5 revert: add "--strategy" option to choose merge strategyChristian Couder, Mar 25, 2010

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.