New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
builtin/pull.c: use config value of autostash #1179
Conversation
There is an issue in commit c5e7035: |
c5e7035
to
ecd7177
Compare
There is an issue in commit ecd7177: |
ecd7177
to
fd8964d
Compare
There is an issue in commit fd8964d: |
fd8964d
to
a720f1b
Compare
There is an issue in commit a720f1b: |
It looks like you manually entered the sign off - If this was generated by another tool let me know. |
a720f1b
to
ba3496a
Compare
There is an issue in commit ba3496a: |
ba3496a
to
c231881
Compare
There is an issue in commit c231881: |
c231881
to
a305b73
Compare
There is an issue in commit a305b73: |
/preview |
There is an issue in commit a305b73: |
a305b73
to
b459152
Compare
There is an issue in commit b459152: |
b459152
to
5c0b8da
Compare
There is an issue in commit 5c0b8da: |
5c0b8da
to
6e23e98
Compare
There is an issue in commit 6e23e98: |
6e23e98
to
46c4f45
Compare
There is an issue in commit 46c4f45: |
46c4f45
to
7139aeb
Compare
There is an issue in commit 7139aeb: |
7139aeb
to
15eb361
Compare
There is an issue in commit 15eb361: |
Try letting git do it: btw, you have a capital 'O' in 'off'. GitHub seems to be more forgiving on the case. |
15eb361
to
ac12a6d
Compare
On a git pull --rebase, if fast forward is possible we run merge. However, merge will not honor rebase.autostash if it is configured. This has the unfortunate result of $ git config rebase.autostash true $ git pull --rebase to ignore the rebase.autostash value. Allow run_merge() to honor rebase.autostash by passing in config_autostash if --autostash or --no-autostash flags are not explicitly set. Reported-by: "Tilman Vogel" <tilman.vogel@web.de> Co-authored-by: "Junio C Hamano" <gitster@pobox.com> Signed-off-by: "John Cai" <johncai86@gmail.com>
ac12a6d
to
58c8592
Compare
This PR could be closed as this bug was fixed in 7a9ae6d |
A bug in pull.c causes merge and rebase functions to ignore
rebase.autostash if it is only set in the config.
There are a couple of different scenarios that we need to be mindful of:
$ git pull --autostash
merge/rebase should get --autostashed passed through
$ git config rebase.autostash true
$ git pull --rebase
merge/rebase should get --autostash from config
$ git pull --no-autostash
--no-autostash should be passed into merge/rebase
$ git config rebase.autostash true
$ git pull
--autostash should not be passed into merge but not rebase
This change adjusts variable names to make it more clear which autostash
setting it is modifying, and ensures --autostash is passed into the
merge/rebase where appropriate.
cc: René Scharfe l.s.r@web.de
cc: Philippe Blain levraiphilippeblain@gmail.com
cc: Tilman Vogel tilman.vogel@web.de