Ævar Arnfjörð Bjarmason <ava...@gmail.com> writes: > I looked into this a long while ago and remembered that rebase was > doing something like a git status for every commit that it made to > check the dirtyness. > > This could be vastly improved by having an unsafe option to git-rebase > where it just assumes that the starting state + whatever it wrote out > is the current state, i.e. it would break if someone stuck up on your > checkout during an interactive rebase and changed a file,...
You could make it a lot safer than "just assumes", and the result may become generally usable, I think. For example, you can set a "magic" bit somewhere in $GIT_DIR/rebase-i while you are in "I am doing pick/pick/pick and the user will not interfere me" mode, and clear that bit upon "rebase --continue". And you cheat only while that "magic" bit is set. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
