Re: [PATCH v2] sequencer: advise if skipping cherry-picked commit

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 12, 2021, 19:13 UTC
Message-ID: <xmqqtuju328n.fsf@gitster.g>
In-Reply-To: <c185a396-c498-b2ef-1c86-cec7d5751f3d@gmail.com>

Philippe Blain <levraiphilippeblain@gmail.com> writes:

> Since your proposed changes are in sequencer.c, this will only affect
> the default "merge" rebase backend, and not the older 'apply' backend. I think
> it might be worth mentioning this in the commit message.

It shouldn't be too hard to teach "format-patch --cherry-pick" to report when commits are actually dropped. There isn't necessarily a need to give help to users what to do to apply the same change twice, but even for those who _know_ how to do so, they need to know if commits are dropped in the first place. And such a notice is useful for any user of the --cherry-pick feature of format-patch, not just as an implementation detail of "git rebase".