> >
> > 1. After you get used to it, keeping track of revision
> boundries when
> > merging isn't *that* bad. 2. It seems that svnmerge.py works fairly
> > well, though we've just experimented with it so far so.
> There may be
> > issues we don't know about. 3. Finally, merge tracking
> supposedly is
> > coming in 1.5.
>
> True, svnmerge.py adds much of the needed functionality. It
> doesn't allow you to cherry pick a portion of a change set
> yet, but I'm looking forward to 1.5. No complaining here,
> just stating the facts so Steve is informed.
I haven't used cherry-picking functionality yet, but according to
http://www.orcaware.com/svn/wiki/Svnmerge.py, cherry picking is
supported.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 27 19:59:44 2007