summaryrefslogtreecommitdiff
path: root/run-command.c
diff options
context:
space:
mode:
authorTyler Brazier <tyler@tylerbrazier.com>2017-06-01 04:18:36 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-06-01 05:09:39 (GMT)
commitf15e7cf5cc95cbfd0d05c260f75631781e290edc (patch)
tree1dc654940aba622254fd24906c89060c9e44d4d6 /run-command.c
parentb06d3643105c8758ed019125a4399cb7efdcce2c (diff)
downloadgit-f15e7cf5cc95cbfd0d05c260f75631781e290edc.zip
git-f15e7cf5cc95cbfd0d05c260f75631781e290edc.tar.gz
git-f15e7cf5cc95cbfd0d05c260f75631781e290edc.tar.bz2
pull: ff --rebase --autostash works in dirty repo
When `git pull --rebase --autostash` in a dirty repository resulted in a fast-forward, nothing was being autostashed and the pull failed. This was due to a shortcut to avoid running rebase when we can fast-forward, but autostash is ignored on that codepath. Now we will only take the shortcut if autostash is not in effect. Based on a few tests against the git.git repo, the shortcut does not seem to give us significant performance benefits, on Linux at least. Regardless, it is more important to be correct than to be fast. Signed-off-by: Tyler Brazier <tyler@tylerbrazier.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'run-command.c')
0 files changed, 0 insertions, 0 deletions