Re: Handling multiple revision ranges in a single merge operation

On 03/04/2007 2.06, Daniel Rall wrote:

> I'd like to extend the svn_client_merge_peg3() API to accept a list of
> revision ranges to merge. As this API already been rewritten
> internally to handle this to support Merge Tracking, we'd only be
> exposing functionality that 'merge' is already offerring.
>
> A couple of questions:
>
> - Should 'svn merge -rN URL [WC_PATH]' also support this?
> Example: svn merge -r3,5-7,10 $URL

Wouldn't it better to use -c for this? -rN:M already has a meaning of svn
merge, so adding -rN,M and -rN-M to it looks like a bit of a confusion.

When you say -r3,5-7,10 (like svnmerge.py), you're naming changesets, which is
what it's done in SVN with -c.

-- 
Giovanni Bajo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org