Aside from that - why does "svn update -N" not create the directory? I
understand it would not create the files within the directory but
wouldn't cerate the directory?
It also seems odd that the "svn update -N" command gives the following
info:
D Reports
Updated to revision 618.
Does D mean that it deleted the directory? That's certainly what "svn
help update" implies. But the directory is NOT deleted in the
repository!!!
Ray
________________________________
From: Ray Johnson [mailto:Rayj@ingenio.com]
Sent: Friday, June 04, 2004 2:03 PM
To: users@subversion.tigris.org
Subject: RE: Re: Help - possible bug in Subversion!
Right but after that if I do a NORMAL "svn update" and it STILL does not
show up!!!
Perhaps it's as "svn update -N" became a sticky option - with no way to
make it unsticky?!?!
Ray
________________________________
From: Toby Johnson [mailto:toby@etjohnson.us]
Sent: Friday, June 04, 2004 1:49 PM
To: users@subversion.tigris.org
Subject: Re: Help - possible bug in Subversion!
Ray Johnson wrote:
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?
Because you told it not to recurse, which means don't go into
subdirectories. I guess it's a matter of semantics whether it should
create the empty "Reports" directory -- I'd argue it shouldn't -- but
restoring any of the files in Reports would definitely be wrong.
Received on Fri Jun 4 23:08:04 2004