diff options
| author | Paul Tan <pyokagan@gmail.com> | 2015-05-18 21:45:41 +0800 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2015-05-18 11:22:27 -0700 |
| commit | eb8dc05c3d364174a6b694e2850ffd6cfe32c6d3 (patch) | |
| tree | f462cc65dabea04bdf6e6ea0441bbca279899ede /git-pull.sh | |
| parent | 3d4a3ffe64162b45ae7c991fc60623ecb4678cfd (diff) | |
| download | git-eb8dc05c3d364174a6b694e2850ffd6cfe32c6d3.tar.gz git-eb8dc05c3d364174a6b694e2850ffd6cfe32c6d3.tar.xz | |
pull: make pull.ff=true override merge.ff
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.
Fix this by adding the --ff switch if pull.ff=true, and add a test to
catch future regressions.
Furthermore, clarify in the documentation that pull.ff overrides
merge.ff.
Signed-off-by: Paul Tan <pyokagan@gmail.com>
Reviewed-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-pull.sh')
| -rwxr-xr-x | git-pull.sh | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/git-pull.sh b/git-pull.sh index 4d4fc77b0..2aea4fa38 100755 --- a/git-pull.sh +++ b/git-pull.sh @@ -56,6 +56,9 @@ fi # Setup default fast-forward options via `pull.ff` pull_ff=$(git config pull.ff) case "$pull_ff" in +true) + no_ff=--ff + ;; false) no_ff=--no-ff ;; |