Re: "git rebase" behavior change in 2.26.0
- From
Elijah Newren <newren@gmail.com>
- Date
- Mar 27, 2020, 20:59 UTC
- Message-ID
- <CABPp-BGKeUeMCaOt2b6j1kqgbeTDJxYjRxAPdM+=JB6V1r4EpA@mail.gmail.com>
- In-Reply-To
- <CABPp-BHihQjMc9qugVtVTZVduRxLYUAhf18R5c=3Lb5bcRzjAw@mail.gmail.com>
On Fri, Mar 27, 2020 at 11:34 AM Elijah Newren <newren@gmail.com> wrote:
> > On Fri, Mar 27, 2020 at 11:01 AM Norbert Kiesel <nkiesel@gmail.com> wrote: > >
...
> What's in your .git/config, and in your $HOME/.gitconfig? (Or maybe > just the output of 'git config --list'?) > What hooks do you have setup in .git/hooks/?
After some off-thread discussion due to concerns with sharing his configuration globally...
Ahah, so I can duplicate when using both pull.rebase=true and rebase.autosquash=true. rebase.autosquash in the rebase code sets allow_preemptive_ff to 0, meaning it disables rebase from fast-forwarding. That would have been fine if we only ran a rebase, but we ran both a merge and a rebase and thus updated ORIG_HEAD *twice*. So, the "extra" bug I found upthread (pull runs both merge and rebase for a fast-forward) isn't an extra bug but is *the* bug in question. It's been with us for a few years as Jeff pointed out, but just was uncovered due to the other recent 2.26 changes. Patch incoming soon.