SVN Update Usage

I have come across something that I'm not sure is a bug, or misuse.
I have a local working copy called Proj1/. Someone commits a new
directory Proj1/files and adds some files to the new directory to the
repository. I see the changes with `svn status -u`, there are a ton
of changes, but I just want to pull down the Proj1/files. `cd Proj1 ;
svn update files` doesn't work "files not under version control"
error. I then tried a svn co https://hostname/path/Proj1/files while
in my local Proj1 folder. This yields another error message: Working
copy 'files' not locked. The files directory is created without a
checkout of files... cd files ; svn update works afterwards, but then
breaks in the parents Proj1/ directory with the the lock error message
again on an `svn update files.

In CVS I could update a directory that didn't exist locally by cvs up
-dP files. Anybody have a clue what is going on here?

Regards,
Ryan Phillips

-- 
... the heat come 'round and busted me for smiling on a cloudy day.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org