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

[PATCH 2/3] git-rebase--interactive.sh: Don't pass a strategy to git-cherry-pick.

From
Björn Steinbrink <b.steinbrink@gmx.de>
Date
Oct 31, 2007, 02:20 UTC
Message-ID
<1193797232-1062-2-git-send-email-B.Steinbrink@gmx.de>
In-Reply-To
<1193797232-1062-1-git-send-email-B.Steinbrink@gmx.de>

git-cherry-pick doesn't support a strategy paramter, so don't pass one. This means that --strategy for interactive rebases is a no-op for anything but merge commits, but that's still better than being broken. A correct fix would probably need to port the --merge behaviour from plain git-rebase.sh, but I have no clue how to integrate that cleanly.

Signed-off-by: Björn Steinbrink <B.Steinbrink@gmx.de>
diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
index f667ae8..cc949db 100755
--- a/git-rebase--interactive.sh
+++ b/git-rebase--interactive.sh
@@ -116,7 +116,7 @@ pick_one () {
 		sha1=$(git rev-parse --short $sha1)
 		output warn Fast forward to $sha1
 	else
-		output git cherry-pick $STRATEGY "$@"
+		output git cherry-pick "$@"
 	fi
 }
 
@@ -184,7 +184,7 @@ pick_one_preserving_merges () {
 			fi
 			;;
 		*)
-			output git cherry-pick $STRATEGY "$@" ||
+			output git cherry-pick "$@" ||
 				die_with_patch $sha1 "Could not pick $sha1"
 			;;
 		esac
-- 
1.5.3.4.456.g072a
Previous: Björn SteinbrinkNext: Björn Steinbrink
Message 2 of 5 in “Fix --strategy parsing in git-rebase--interactive.sh”
  1. 1/3 Fix --strategy parsing in git-rebase--interactive.shBjörn Steinbrink, Oct 31, 2007
  2. 2/3 git-rebase--interactive.sh: Don't pass a strategy to git-cherry-pick.Björn Steinbrink, Oct 31, 2007
  3. 3/3 git-rebase--interactive.sh: Make 3-way merge strategies work for -p.Björn Steinbrink, Oct 31, 2007
  4. Johannes SchindelinOct 31, 2007
  5. Björn SteinbrinkOct 31, 2007

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.