git/builtin
Elijah Newren fbae70ddc6 pull: avoid running both merge and rebase
When opt_rebase is true, we still first check if we can fast-forward.
If the branch is fast-forwardable, then we can avoid the rebase and just
use merge to do the fast-forward logic.  However, when commit a6d7eb2c7a
("pull: optionally rebase submodules (remote submodule changes only)",
2017-06-23) added the ability to rebase submodules it accidentally
caused us to run BOTH a merge and a rebase.  Add a flag to avoid doing
both.

This was found when a user had both pull.rebase and rebase.autosquash
set to true.  In such a case, the running of both merge and rebase would
cause ORIG_HEAD to be updated twice (and match HEAD at the end instead
of the commit before the rebase started), against expectation.

Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-03-27 15:54:54 -07:00
..
2019-10-15 13:47:59 +09:00
2019-10-11 14:24:48 +09:00
2019-09-18 11:50:09 -07:00
2019-12-06 16:31:39 +01:00
2019-01-29 12:47:54 -08:00
2019-10-15 13:48:02 +09:00
2019-04-25 16:41:12 +09:00
2019-10-15 13:48:02 +09:00
2018-10-19 13:34:02 +09:00
2019-09-18 11:50:09 -07:00
2019-09-30 13:19:32 +09:00
2019-10-07 11:32:53 +09:00
2019-05-13 14:22:54 +09:00
2019-10-15 13:48:03 +09:00
2019-10-11 14:24:46 +09:00
2019-10-11 14:24:46 +09:00
2019-07-19 11:30:21 -07:00
2019-10-11 14:24:48 +09:00
2019-12-06 16:31:39 +01:00
2019-06-19 08:19:21 -07:00
2019-10-11 14:24:48 +09:00