On Thu, Sep 22, 2016 at 07:33:11PM +0000, Anatoly Borodin wrote:
> Hi Stefan,
> this section was added to the manual in the commit
> cddb42d2c58a9de9b2b5ef68817778e7afaace3e by "Jonathan Nieder"
> <jrnie...@gmail.com> 6 years ago. Maybe he remembers better?
Just to make it clear, this section explicitly talks about 'bugs' with
preserve-merges and interactive rebase. Without the --preserve-merges
option, those operations works as expected.
The reason, as that section explains, is that it's not possible to store
the merge structure in the flat todo list. I assume this means git
internally remembers where the merge commit was, and then restores it
Changing the order, or dropping commits might then give unexpected