Naveen Nathan <naveen@xxxxxxxxxxxxx> writes: > When --rebase-merges was introduced in 427c3bd28a the sentence > describing the difference between --rebase-merges and --preserve-merges > is a little unclear and difficult to parse. This patch improves readability > while retaining original meaning. > > ... > -The `--rebase-merges` mode is similar in spirit to the deprecated > -`--preserve-merges`, but in contrast to that option works well in interactive > -rebases: commits can be reordered, inserted and dropped at will. > +The `--rebase-merges` mode is similar in spirit to `--preserve-merges` > +(deprecated) but actually works with interactive rebases, where commits > +can be reordered, inserted and dropped at will. I think the original "to the deprecated `--preserve-merges`" is mildly easier to follow than "to `--preserve-merges` (deprecated)". The later part of the sentence with this patch does read smoother and is a definite improvement. Thanks.
