SZEDER Gábor <szeder.dev@xxxxxxxxx> writes: > ... However, once > rebase stops for the 'edit' instruction the user can do just about > anything, so I'm not sure how rebase could figure out when to copy the > note and when not. True. > This doesn't happen when inserting a 'break' instruction between > picking the "second" and "third" commits, and then adding new commits. Meaning the original note for the second one is carried to the rewritten second, and the one for the third is carried to the rewritten third? That would be a reasonable outcome. > Alas, the 'break' instruction is not even a year old, and I have been > using 'edit' for this purpose for over a decade now... so > re-training my fingers will be hard :) Probably a section in the tutorial and/or the example section of the "git rebase -i" documentation should encourage use of "break" when inserting a brand-new commit in the middle. Thanks.
