Junio C Hamano <gitster@xxxxxxxxx> writes:
> True. So instead of letting the machine match commits on the both
> sides up, the end-user who is rebasing will find matches (or near
> matches) and manually handle them. It would be a good idea to
> describe the pros and cons for the option (which I think has already
> been written fairly clearly in the proposed patch).
Sorry, strike the part in (parentheses) out. I was looking at the
description in an earlier version with --skip-cherry-pick-detection,
which had a good explanation on "if such detection is not done,
then..." but with the latest one seems to have lost the description
altogether. Minimally something like this from the earlier round
should probably be resurrected.
... these duplicates will be re-applied, which will likely
result in no new changes (as they are already in upstream) and
drop them from the resulting history.
Thanks.
