Hi Ryan,
I initially asked for a fully recursive checkout, I'm certain of that.
At some point an svn update -N may have been run, but most of the time
It would have been simply 'svn update'.
But now that you bring it up - if one DOES get a workspace which has
been checked out non-recursively, is there any way to force svn to check
out/update the rest of the directories recursively?
Cheers,
John
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2008a_at_ryandesign.com]
Sent: Tuesday, February 12, 2008 11:54 AM
To: John Mcgrath
Cc: John Peacock; users_at_subversion.tigris.org
Subject: Re: svnupdate - some directories not being updated
On Feb 12, 2008, at 10:47, John Mcgrath wrote:
> After I noticed this issue, I did try go to the webserver's workspace
> and do the manual update. Typing svn update does not produce any
> error,
> it just returns 'At revision <latest>'. So it appears, as far as it's
> concerned, everything is updated. I ran an svn cleanup, and then tried
> again, but it made no difference. The only way I could get it to
> populate this new directory was to do the svn update <dir_name>.
How was the working copy on the server initially created? The
behavior you describe sounds correct if you initially asked for a non-
recursive checkout, e.g. via "svn checkout -N" or "svn checkout --non-
recursive".
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-12 23:23:28 CET