[PATCH 2 of 2] rebase: add --cherrypick to cherrypick single revisions

Matt Mackall mpm at selenic.com
Tue Jan 12 23:34:51 CST 2010


On Tue, 2010-01-12 at 10:07 +0100, Dan Villiom Podlaski Christiansen
wrote:
> On 12 Jan 2010, at 09:09, Stefano Tortarolo wrote:
> 
> > 2010/1/11 Matt Mackall <mpm at selenic.com>
> > 
> >> Note that all of this is less about selecting which changesets to work
> >> on ('cherrypicking') and focusing more on what we do with them ('adapt
> >> or port or transplant them from one branch to another').
> > 
> > Yes, you're right obviously. It's just that for non-English speakers this
> > might be not so intuitive.
> > However, I like 'adapt'.
> 
> I was wondering, how related to the functionality of ‘transplant’ is
> the proposed command? If it's a superset of it and could be made
> backwards compatible, wouldn't it be worthwhile to simply replace
> ‘transplant’ with the new command?

Transplant can work between independent repos (even unrelated ones!) and
apply various filters to changes, which rebase/'adapt' can't.

-- 
http://selenic.com : development and support for Mercurial and Linux




More information about the Mercurial-devel mailing list