--
YHkKTK8zeAeUY7KZJCk
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> > The ability to cherry pick patches is also a real benefit.
> 
> Is it, really?  I'm not trying to be combative, I'm just wondering  
> how often that comes up.

I like the ability to develop a patchset as an object -- 'here, does
this set work?' -- and discuss. I like the orientation of discussing
changes rather than states.

I cherry-pick a lot -- it also lets me take my production copy -- which
has a couple site-specific changes to version-controlled files still --
and make a hotfix and push back to the repo from that without getting my
changes mixed in.

It suits my workflow.

The other thing to note is that you can use two SCMs at once. I quite
often push to a darcs repo that is also a SVN checkout. Once I get the
patchset to a state I like, I can commit a huge chunk all at once, and
use the darcs changelog to make a good commit entry.

I'm trying git with one project. So far, so good. It's also a really
good tool. And mightily fast.

Aria

--
YHkKTK8zeAeUY7KZJCk
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBF9r70tP09exA3hooRAvHXAKDOx4t+acFxg5TGQKW3k+WetUE2yQCdEi6Z
yNHgHqpVdnVSXbepjDgxWTA5K
-----END PGP SIGNATURE-----

--
YHkKTK8zeAeUY7KZJCk--