Alban Gruin <alban.gruin@xxxxxxxxx> writes: > To prevent mistakes when editing a branch, rebase features a knob, > rebase.missingCommitsCheck, to warn the user if a commit was dropped. > Unfortunately, this check is only effective for the initial edit, which > means that if you edit the todo list at a later point of the rebase and > drop a commit, no warnings or errors would be issued. > ... > rebase-interactive.c | 57 ++++++++++++++++++++---- > rebase-interactive.h | 2 + > sequencer.c | 53 ++++++---------------- > sequencer.h | 1 - > t/t3404-rebase-interactive.sh | 83 +++++++++++++++++++++++++++++++++++ > 5 files changed, 147 insertions(+), 49 deletions(-) This passes the self-test when tested by itself, but when merged near the tip of 'pu', it breaks t3404.116, it seems.
