Mark Stosberg writes:
>
> > All of the major VCSes claim to support cherry-picking, and
> > by their designers' lights I see no reason to think they don't do it
> > well.
>
> As far as I'm aware, git can only cherry-pick specific patches
> easily.
Although the cherrypick command works one patch at a time, git can
cherrypick certain connected components of a DAG easily, with rebase.
I can't recall wanting anything else.
> With Darcs, I can easily say (throughout the command set):
>
> "please deal only with patches that included RT#1234" in the name.
>
> With git, it seems the equivalent is to use a notably more complex
> workflow involving a branch named "rt-1234".
It's not more complex, merely more tedious, and therefore easily
automatable. I use it all the time for collecting typo fixes and
other things that naturally will apply to multiple branches. It's
less spontaneous, but equally effective.
> Correct me if I'm wrong, but git has no reasonable way to pull all the
> patches that match a given regex for the patch name.
That's meaningless in git. The human-understandable names for patches
are based on DAG-traversal ("grandparent of the head of the 'master'
branch"), not on arbitrary text strings.
> it certainly appears that git is missing so me interesting features
> which darcs has.
Sure. And vice versa.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
