Re: When does svn co -N make sense?

[The example situation is that there are projects a, b, and c
under /trunk/ of the repository, and the user does not want to
check everything out at the same time.]

What would look natural to me but is *not* the way svn seem to
work now is:

 laptop$ svn ls http://server/svn/trunk/
 a/
 b/
 c/
 laptop$ svn co -N http://server/svn/trunk/ .
 laptop$ ls -aF
 . ../ .svn/
 laptop$ svn update a
 laptop$ ls -aF
 ./ ../ .svn/ a/
 laptop$ svn update c
 laptop$ ls -aF
 ./ ../ .svn/ a/ c/
 laptop$ svn st
 ! b

Specifically, since the working copy checked out with -N does
not seem to know that it has a, b, c directotires as its
children, "svn update a" does not update from trunk/a, nor "svn
st" does not say b is missing.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 3 08:42:54 2003