# [PATCH] Use resolve in git-pull if NO_PYTHON

2 messages from 2006-03-14 to 2006-03-14. Participants: Mark Hollomon, Johannes Schindelin.
Thread: https://gitlist.dev/t/3646

## Mark Hollomon, 2006-03-14 17:16

Subject: [PATCH] Use resolve in git-pull if NO_PYTHON
Message-ID: <1142356355-4772-markhollomon@comcast.net>
URL: https://gitlist.dev/e/1142356355-4772-markhollomon%40comcast.net

```
git-pull is hardcoded to use the recursive merge strategy
for the twohead case. But if git has been built with NO_PYTHON,
that strategy is not available. Teach git-pull to use resolve
if built with NO_PYTHON.

Signed-off-by: Mark Hollomon <markhollomon@comcast.net>


---

 git-pull.sh |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)

1eb3abec6f4811e3eeafa50445ed0f2ce5d85b08
diff --git a/git-pull.sh b/git-pull.sh
index 6caf1aa..ae9c346 100755
--- a/git-pull.sh
+++ b/git-pull.sh
@@ -8,6 +8,11 @@ USAGE='[-n | --no-summary] [--no-commit]
 LONG_USAGE='Fetch one or more remote refs and merge it/them into the current HEAD.'
 . git-sh-setup
 
+default_twohead_strategy='recursive'
+if test "@@NO_PYTHON@@"; then
+    default_twohead_strategy='resolve'
+fi
+
 strategy_args= no_summary= no_commit=
 while case "$#,$1" in 0) break ;; *,-*) ;; *) break ;; esac
 do
@@ -82,7 +87,7 @@ case "$merge_head" in
 	var=`git repo-config --get pull.twohead`
 	if test '' = "$var"
 	then
-		strategy_default_args='-s recursive'
+		strategy_default_args="-s $default_twohead_strategy"
 	else
 		strategy_default_args="-s $var"
 	fi
-- 
1.2.4.g967a

```

## Johannes Schindelin, 2006-03-14 17:26

Subject: Re: [PATCH] Use resolve in git-pull if NO_PYTHON
Message-ID: <Pine.LNX.4.63.0603141825200.22344@wbgn013.biozentrum.uni-wuerzburg.de>
URL: https://gitlist.dev/e/Pine.LNX.4.63.0603141825200.22344%40wbgn013.biozentrum.uni-wuerzburg.de
In-Reply-To: <1142356355-4772-markhollomon@comcast.net>

```
Hi,

On Tue, 14 Mar 2006, Mark Hollomon wrote:

> git-pull is hardcoded to use the recursive merge strategy
> for the twohead case. But if git has been built with NO_PYTHON,
> that strategy is not available. Teach git-pull to use resolve
> if built with NO_PYTHON.

D'oh. I forgot to send that patch when I was doing the NO_PYTHON stuff. 
But I did it differently: There is no good reason that git-pull should 
insist on its own default strategy when git-merge already has one.

Ciao,
Dscho

```