diff options
| author |  Junio C Hamano <junkio@cox.net> | 2006-07-09 00:42:26 -0700 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2006-07-13 23:10:19 -0700 |
| commit | 06d30f4f3eea71bce4cf48db3ea384976b3983b7 (patch) | |
| tree | f3b1d0ba712cc976dba5bc1d7d9dc5f104d81bee /git-rebase.sh | |
| parent | Status update on merge-recursive in C (diff) | |
| download | tgif-06d30f4f3eea71bce4cf48db3ea384976b3983b7.tar.xz | |
recur vs recursive: help testing without touching too many stuff.
During git-merge-recur development, you could set an environment
variable GIT_USE_RECUR_FOR_RECURSIVE to use WIP recur in place
of the recursive strategy.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'git-rebase.sh')
| -rwxr-xr-x | git-rebase.sh | 15 |
1 files changed, 13 insertions, 2 deletions
diff --git a/git-rebase.sh b/git-rebase.sh index 2a4c8c8a89..8c5da7219e 100755 --- a/git-rebase.sh +++ b/git-rebase.sh @@ -35,7 +35,13 @@ If you would prefer to skip this patch, instead run \"git rebase --skip\". To restore the original branch and stop rebasing run \"git rebase --abort\". " unset newbase -strategy=recur +case "${GIT_USE_RECUR_FOR_RECURSIVE}" in +'') + strategy=recursive ;; +?*) + strategy=recur ;; +esac + do_merge= dotest=$GIT_DIR/.dotest-merge prec=4 @@ -198,6 +204,11 @@ do shift done +case "$strategy,${GIT_USE_RECUR_FOR_RECURSIVE}" in +recursive,?*) + strategy=recur ;; +esac + # Make sure we do not have .dotest if test -z "$do_merge" then @@ -292,7 +303,7 @@ then exit $? fi -if test "@@NO_PYTHON@@" && test "$strategy" = "recur" +if test "@@NO_PYTHON@@" && test "$strategy" = "recursive" then die 'The recursive merge strategy currently relies on Python, which this installation of git was not configured with. Please consider |