Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
installer: offer the builtin stash/rebase as experimental options #203
As nice as the speed-ups are, the patches in question are still in flux, and they are not battle-tested at all.
Let's use the scripted commands by default, and offer the new, fast, experimental builtins as options.
This gives us the best of both worlds: users who want the raw speed improvement we got through three Google Summer of Code projects working in parallel can have that, while others who are reluctant to play guinea pig by running only well-tested code can stay on the safe side.
Plus, it gives us a chance of battle-testing those patches :-)
Note: the code added in this PR will only kick in if bundling a Git built including the latest patches of git-for-windows/git#1800.
I like the idea of exposing these options to people who might be interested in trying them out. I haven't run the code, but the code changes look reasonable to me (on inspection).
My concern is that we are adding more options to a setup that already exposes a lot of options to users. If I wasn't already familiar with the options, I am not sure how I would make an informed decision about what option I should choose based on the information presented in this dialog.
Any suggestions how to word it?