Since b814da8 (pull: add pull.ff configuration, 2014-01-15), running git-pull with the configuration pull.ff=false or pull.ff=only is equivalent to passing --no-ff and --ff-only to git-merge. However, if pull.ff=true, no switch is passed to git-merge. This leads to the confusing behavior where pull.ff=false or pull.ff=only is able to override merge.ff, while pull.ff=true is unable to. This patch series adds a failing test to demonstrates the above, and fixes it. The documentation is also tweaked to clarify that pull.ff is meant to override merge.ff. The last patch makes pull.ff consistent with merge.ff by supporting the config aliases of true and false (on, off, 0, 1). Paul Tan (4): t7601: test for pull.ff=true overrides merge.ff=false pull: make pull.ff=true override merge.ff Documentation/config.txt: clarify that pull.ff overrides merge.ff pull: parse pull.ff as a bool or string Documentation/config.txt | 2 +- git-pull.sh | 5 ++++- t/t7601-merge-pull-config.sh | 8 ++++++++ 3 files changed, 13 insertions(+), 2 deletions(-) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html