Running svn update on a path that does not exist in
the working copy, results in a "At revision N" message,
which is kind of misleading, even though the "U path"
portion of the message does not appear. For instance, if
you have a working copy that is not updated and run svn up
with an invalid path argument, you get the "At revision HEAD"
message, even though the working copy has not been updated to
the HEAD revision. I applied the patch that follows to correct
the problem. But that seems to break a feature of svn update -
it acts like svn checkout if the path argument matches a path
that exists only in the repository. Not sure if opening
ra_session to check for the existence of multiple update paths is
a good idea.
Ramaswamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 24 19:20:45 2005