Re: [RFC] cherry-pick using multiple parents to implement -x
- From
Paolo Bonzini <bonzini@gnu.org>
- Date
- Sep 8, 2008, 15:04 UTC
- Message-ID
- <48C53F13.10608@gnu.org>
- In-Reply-To
- <20080908143807.GB10252@spearce.org>
Show 5 quoted lines
> Sorry for wandering into a thread in the middle. But we've already > been down this road before, and decided the additional header wasn't > worth it from cherry-pick. What's changed? The fact that gitk > wants to hyperlink this? Why can't it just regex out a string of > hex digits longer than 6 and see if there is a commit that matches?
The main difference is that git-cherry too often does not work right now (I have a local patch so that it more-or-less works with my GNU ChangeLogs, but it does not improve the situation if rerere kicks in).
(Of course git cherry could also regex out a string of hex digits longer than 6 and see if there is a commit that matches).
Paolo