[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN Update Usage

From: Bruce Elrick <bruce_at_elrick.ca>
Date: 2004-03-25 01:03:28 CET

I could be wrong here, but I think the creation of the files subdir is a
change on the parent dir Proj1, so you have to update Proj1 at least to
the rev where the files subdir was created. If that means pulling in
changes to other files in Proj1 or other subdirs of Proj1, you're out of

But I am by no means an expert...

Ryan Phillips wrote:

> 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

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 25 01:04:44 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.