Anatoly Borodin <anatoly.borodin@xxxxxxxxx> wrote: > PS There are also some pieces of "what should work" in these tests: > > t/t3409-rebase-preserve-merges.sh* > t/t3410-rebase-preserve-dropped-merges.sh* > t/t3411-rebase-preserve-around-merges.sh* > t/t3414-rebase-preserve-onto.sh* Thanks, this is interesting; I'm having trouble understanding the tests though. Some of them use rebase -p -i, but I don't understand why they use -i, or why that even works in a test (i.e. why it doesn't open an editor). In one test I saw "GIT_EDITOR=: git rebase -i -p", which I guess means "use the initially given todo sheet unchanged". I don't see any tests that do an interactive rebase and actually change the todo list. -- Stefan Haller Berlin, Germany http://www.haller-berlin.de/