Honor pull.{twohead,octopus} in git-merge.
If git-merge is invoked without a strategy argument it is probably being run as a porcelain-ish command directly and is not being run from within git-pull. However we still should honor whatever merge strategy the user may have selected in their configuration, just as `git-pull .` would have. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
This commit is contained in:
parent
bf699582fd
commit
de811948ba
16
git-merge.sh
16
git-merge.sh
@ -227,9 +227,21 @@ case "$use_strategies" in
|
||||
'')
|
||||
case "$#" in
|
||||
1)
|
||||
use_strategies="$default_twohead_strategies" ;;
|
||||
var="`git-repo-config --get pull.twohead`"
|
||||
if test -n "$var"
|
||||
then
|
||||
use_strategies="$var"
|
||||
else
|
||||
use_strategies="$default_twohead_strategies"
|
||||
fi ;;
|
||||
*)
|
||||
use_strategies="$default_octopus_strategies" ;;
|
||||
var="`git-repo-config --get pull.octopus`"
|
||||
if test -n "$var"
|
||||
then
|
||||
use_strategies="$var"
|
||||
else
|
||||
use_strategies="$default_octopus_strategies"
|
||||
fi ;;
|
||||
esac
|
||||
;;
|
||||
esac
|
||||
|
Loading…
Reference in New Issue
Block a user