It is very typical for Git newcomers to inadvertently create merges and worst:
inadvertently pushing them. This is one of the reasons many experienced users
prefer to avoid 'git pull', and recommend newcomers to avoid it as well.
To avoid these problems and keep 'git pull' useful, it has been suggested
that 'git pull' barfs by default if the merge is non-fast-forward, which
unfortunately would break backwards compatibility.
This patch series leaves everything in place to enable this new mode, but it
only gets enabled if the user specifically configures it; pull.mode =
Later on this mode can be enabled by default (e.g. in v2.0).
To achieve that first some configurations are renamed: for example: pull.rebase
=> pull.mode = rebase, but the old ones remain functional, thus there are no
Then the new mode 'merge-ff-only' is added, but not enabled by default, and
finally, a warning is added so the users will know what to do when the new
mode is indeed enabled by default.
Felipe Contreras (5):
pull: rename pull.rename to pull.mode
pull: refactor $rebase variable into $mode
pull: add --merge option
pull: add merge-ff-only option
pull: add warning on non-ff merges
Documentation/config.txt | 24 ++++++++++--------
Documentation/git-pull.txt | 10 +++++---
branch.c | 4 +--
git-pull.sh | 63 +++++++++++++++++++++++++++++++++++++---------
t/t3200-branch.sh | 40 ++++++++++++++---------------
t/t5520-pull.sh | 62 +++++++++++++++++++++++++++++++++++++++++++++
t/t5601-clone.sh | 4 +--
7 files changed, 157 insertions(+), 50 deletions(-)
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html