merge option needs to be able to handle multiple change sets?

If I do some merges I can do as follows:

svn merge -c15 repo/branch
svn merge -c20 repo/branch
svn merge -c35 repo/branch
svn merge -c17 repo/branch

But it is not possible to dry run these:

svn merge -c15,20,35,17 repo/branch

does not work. This seems intentional, but its something really needed in
order to calculate weather executing a merge gives G or C files. Come to
that it would be very useful to be able to actually do as one command. In
fact I think there ought to be a command to read an arbitrary changeset list
from a file when doing either wet or dry run merges.

There is also no way that I know of to synthesize the dry run result from a
number of dry runs, the order of the merge can be important and not allowing
multiples takes order out of the equation.

But it seems like the omission of multiple changesets is so obvious that it
MUST be intentional, or is it just that I missed some vital option or that
the help is not up to date. What is even odder is that the pre 1.5
svnmerge.py tool, explicitly DID allow this type of thing. Ive not used the
svnmerge.py tool, and my understanding is that it is discouraged with 1.5
because 1.5 is supposed to provide better inbuilt facilities.

So, can someone tell me what the outlook for this is. A clearly needed
facility intentionally not implemented? Will it and can it be?

-- 
View this message in context: http://www.nabble.com/merge-option-needs-to-be-able-to-handle-multiple-change-sets--tp18607129p18607129.html
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org