[PATCH 0/2] de-confuse git cherry-pick --author behavior

From: Jeff King <peff@peff.net>
Date: Jul 9, 2018, 19:46 UTC
Message-ID: <20180709194636.GB9852@sigill.intra.peff.net>
In-Reply-To: <20180709191607.GA9852@sigill.intra.peff.net>

On Mon, Jul 09, 2018 at 03:16:07PM -0400, Jeff King wrote:

Show 5 quoted lines

> I agree that having something similar to commit's "--author" (or even
> just "--reset-author") would be useful. When I've had to do this before,
> I usually just cherry-pick and then follow-up with "commit --amend
> --author" (or use "rebase -i" if there are several commits). You can
> also do "cherry-pick -n $commit" followed by "commit -c $commit".

I'll leave adding any options there as an exercise if somebody is interested. This series just focuses on the inconsistent error behavior you found.

  [1/2]: sequencer: handle empty-set cases consistently
  [2/2]: sequencer: don't say BUG on bogus input

 sequencer.c                     | 8 +++++---
 t/t3510-cherry-pick-sequence.sh | 7 ++++++-
 2 files changed, 11 insertions(+), 4 deletions(-)

-Peff