I'm just a regular lil user, new and all, but well... I don't understand
what you expect to happen at all.
A non-recursive update sort of, by definition, doesn't go into any
subdirectories, doesn't it? 'Reports' is a subdirectory. Sure, maybe it
should/might re-create the directory, but that directory would have no
files in it. Is that the expected behavior?
--Stephen
_____
From: Ray Johnson [mailto:Rayj@ingenio.com]
Sent: Friday, June 04, 2004 1:43 PM
To: users@subversion.tigris.org
Subject: Help - possible bug in Subversion!
We have a case where a directory that we know is in the
repository doesn't come over when doing an "svn update" not matter what
we try. We have been able to reproduce how subversion gets into this
state. Here is what we did:
Starting in an existing working directory:
c:> rmdir Reports ;# Where Reports is a directory
under version control and did exist in the working directory
c:> svn update -N ;# Do a non-recursive update.
D Reports
Updated to revision 618.
This does not recreate the Reports directory. Why not?
Doing an "svn update" or "svn status" in the working directory
shows we are up to date, and no changes on our side.
However, the Reports directory still does not exist in our
working dierectory but is in the repository!
This has something to do with the "svn update -N". We have
never seen this happen with a normal "svn update" (even tested it on
directories in a different working directory). At this point I'm
starting to think there is a bug in that command.
Is this a known bug? Am I missing something? Help!
Ray
Received on Fri Jun 4 22:49:04 2004