You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Julian Foad <ju...@btopenworld.com> on 2005/04/27 13:21:14 UTC

svn update non_existent_file (issue #2269) [was: svn updated non_existent_file]

S.Ramaswamy S wrote:
> 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

See issue #2269, "svn rm|status|update fileThatDoesNotExist doesn't warn, 
returns 0 exit code", <http://subversion.tigris.org/issues/show_bug.cgi?id=2269>.

> 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.

You need to check that the file is neither in the working copy nor in the 
reppository.  The issue #2269 doesn't make that clear.

> Not sure if opening
> ra_session to check for the existence of multiple update paths is
> a good idea.

Not sure what you mean by "existence of multiple update paths", but you need to 
check whether the item is in the repository somehow at some point during the 
operation.

- Julian

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