Re: Does extending `--empty` to git-cherry-pick make sense?
From: Taylor Blau <hidden>
Date: 2024-01-04 19:33:49
From: Taylor Blau <hidden>
Date: 2024-01-04 19:33:49
[+cc Elijah] On Thu, Jan 04, 2024 at 12:57:18AM -0600, Brian Lyles wrote:
Is there any real barrier to exposing that option to git-cherry-pick as well? Was this an oversight, or intentionally left out? The corresponding commit message doesn't seem to indicate any specific reason for limiting it to git-rebase.
I am not nearly as familiar with this code as Elijah is, but this certainly appears possible by setting the `drop_redundant_commits` and `keep_redundant_commits` flags in the replay_opts struct. I don't see any fundamental reason why cherry-pick shouldn't have the same functionality. Thanks, Taylor