Re: [RFC] Rebasing merges: a jorney to the ultimate solution(RoadClear)
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 30, 2018, 10:38 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1803301235560.5026@qfpub.tvgsbejvaqbjf.bet>
- In-Reply-To
- <87zi2r5swc.fsf@javad.com>
Hi,
On Thu, 29 Mar 2018, Sergey Organov wrote:
Show 11 quoted lines
> Jacob Keller <jacob.keller@gmail.com> writes: > > > I care about the general compatibility of the rebase todo list > > regardless of which options you enabled on the command line to > > generate it. > > It's a good thing in general, yes. However, I recall I was told by the > author that --recreate-merges was introduced exactly to break backward > compatibility of the todo list. If so, could we please agree to stop > using backward compatibility as an objection in the discussion of this > particular feature?
That is a serious misrepresentation of what I said.
If I had changed --preserve-merges to the new format, *that* would have broken backwards-compatibility.
So the entire reason of introducing --recreate-merges was to *not have to break backwards-compatibility*.
I definitely did not say the *exact opposite*.
Hopefully this clarifies your confusion, Johannes