From: Mark Hollomon <markhollomon@comcast.net>
To: git@vger.kernel.org
Subject: [PATCH] Use resolve in git-pull if NO_PYTHON
Date: Tue, 14 Mar 2006 17:16:04 +0000 (UTC)
Date: Tue, Mar 14 12:12:35 2006 -0500 [thread overview]
Message-ID: <1142356355-4772-markhollomon@comcast.net> (raw)
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
next reply other threads:[~2006-03-14 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 17:16 Mark Hollomon [this message]
2006-03-14 17:26 ` [PATCH] Use resolve in git-pull if NO_PYTHON Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1142356355-4772-markhollomon@comcast.net \
--to=markhollomon@comcast.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox