Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > Meaning: essentially, `rebase.useBuiltin` was defaulting to `false`, and > if a user installed Git for Windows with the experimental built-in rebase, > it was set to `true` in the system config. Oh, that changes the picture entirely. If that was what was shipped to Windows users for 2.19.X, then I'd say we should be able to trust the switch well enough. I just somehow thought that everybody in the Windows land has been using the -in-C version. >> Having said that, assuming that the switching back to scripted >> version works correctly and assuming that we want to expose this to >> end users, I think the patch text makes sense. > > Indeed. > > I would still love to see the built-in rebase to be used by default in > v2.20.0, and I am reasonably sure that the escape hatch works (because, as > I told you above, it worked in the reverse, making the built-in rebase an > opt-in in Git for Windows v2.19.1). Good. That makes things a lot simpler. Thanks.
