individual versions versus ranges -

[Alex Haley]

Hello folks,

Can someone suggest which might be going afoul when I do the following sort of thing:

svn.exe merge -c10,11,12,13

versus

svn.exe merge -c10-13

The first example produces a merge conflict - the second does not.  I thought the two formats of -c revision numbers were identical.  Can someone describe what might be happening?

It seems to me that my scripting should just use the consolidated format - -c10-13 ...

thoughts, and thanks,

Alex Haley, Computer Scientist, 781-774-5156
Medical Information Technology, Inc.
Mailstop: F4E16W, MEDITECH Circle, Westwood, MA 02090

[Alex Haley]

footnote : so, the relevant language seems to be: (in the SVN Doc)

--change (-c) ARG

Perform the requested operation using a specific “change”. Generally speaking, this option is syntactic sugar for -r ARG-1:ARG. Some subcommands permit a comma-separated list of revision number arguments (e.g., -c ARG1,ARG2,ARG3). Alternatively, you can provide two arguments separated by a dash (as in -c ARG1-ARG2) to identify the range of revisions between ARG1 and ARG2, inclusive. Finally, if the revision argument is negated, the implied revision range is reversed: -c -45 is equivalent to -r 45:44.

Alex Haley, Computer Scientist, 781-774-5156
Medical Information Technology, Inc.
Mailstop: F4E16W, MEDITECH Circle, Westwood, MA 02090

[Stefan]

Since this applies to the command line client, you might have more luck asking this on the svn mailing list:
http://subversion.apache.org/mailing-lists.html