From: Brian Lyles Date: Sat, 10 Feb 2024 07:43:56 GMT Subject: [PATCH v2 8/8] cherry-pick: add `--empty` for more robust redundant commit handling Message-ID: <20240210074859.552497-9-brianmlyles@gmail.com> In-Reply-To: <20240119060721.3734775-2-brianmlyles@gmail.com> As with git-rebase(1) and git-am(1), git-cherry-pick(1) can result in a commit being made redundant if the content from the picked commit is already present in the target history. However, git-cherry-pick(1) does not have the same options available that git-rebase(1) and git-am(1) have. There are three things that can be done with these redundant commits: drop them, keep them, or have the cherry-pick stop and wait for the user to take an action. git-rebase(1) has the `--empty` option added in commit e98c4269c8 (rebase (interactive-backend): fix handling of commits that become empty, 2020-02-15), which handles all three of these scenarios. Similarly, git-am(1) got its own `--empty` in 7c096b8d61 (am: support --empty=