Performance improvement for git pull rebase and autostash

|| pop stash ||| || | ||| || | success abort success success abort success Regarda, Mattias Von:Mattias Neuling

Performance improvement for git pull rebase and autostash

Hi, I have some suggestions to improve performance of 'git pull --rebase'. 1. If I have no new local commits "git pull --rebase" will do a fast forward merge. But if I have changes to local files I have to stash them also if they are not affected by the new commits from origin. I think in that

Re: Bug: Since Git 2.13.2 git rebase autostash doesn't use fast-forward (poor performance)

Could you see this as suggestion for performance improvement or should I send another e-mail for a new task? Regards, Mattias Junio C Hamano schrieb am 27.06.2017 17:02:14: > Von: Junio C Hamano > An: neul...@dakosy.de > Kopie: git@vger.kernel.org > Datum: 27.06.2017 17:02 > Betreff: Re: Bug

Bug: Since Git 2.13.2 git rebase autostash doesn't use fast-forward (poor performance)

Hi, since the latest version 2.13.2 "git pull --rebase --autostash" doesn't use a fast forward if possible. My global git config contains "pull.rebase=preserve" and "rebase.autostash=true". My working directory is clean with no changes. When I use "git pull" git doesn't use a possible fast

git pull --rebase should use fast forward merge if possible

Hi, since I have added "pull.rebase=preserve" to my global configuration I wonder why "git pull" also trys to rebase if a fast forward merge is possible. A fast forward merge would speed up every pull if your local branch contains no new commits and the remote branch is ahead. The result wou