Re: Does extending `--empty` to git-cherry-pick make sense?
- From
Brian Lyles <brianmlyles@gmail.com>
- Date
- Jan 5, 2024, 03:20 UTC
- Message-ID
- <CAHPHrSe51_y445m0Hn_SqdpwJNKLrKHKm3LzY=APG+QzBygt7w@mail.gmail.com>
- In-Reply-To
- <CABPp-BGJfvBhO_zEX8nLoa8WNsjmwvtZ2qOjmYm9iPoZg4SwPw@mail.gmail.com>
On Thu, Jan 4, 2024 at 8:28 PM Elijah Newren <newren@gmail.com> wrote:
Show 9 quoted lines
> > I was indeed focused on simply getting the multiple rebase backends to > have consistent behavior (we had like 4-5 backends at the time, > right?) and just didn't consider cherry-pick at the time. Now that > those are more consistent (though there's still work to be done on > that end too), cherry-pick and rebase really ought to share a lot more > between each other, from command line flags, to temporary control > files written, to more shared code paths. Adding an --empty flag to > cherry-pick as a step along the way makes sense.
I appreciate the insight from both of you.
It sounds like I'll be diving into some C code for the first time in over a decade, then! I'll plan to take a crack at this soon.
-Brian Lyles