'svn co' (checkout) creates a new working copy of the repository
I assume you already have and are working within your working copy. You
don't want to create a working copy embedded inside your existing
working copy. Subversion (and you) will get confused and not be able to
update all the files properly when you least expect. If you do already
have and are working within a working copy, then you want to do this
instead:
'svn update -r rev url'
else, if you just want the file independent of the whole repository,
then
'svn export -r rev url'
this will get you a copy of the file(s) without any of the .svn
versioning
> -----Original Message-----
> From: alexus [mailto:alexus_at_gmail.com]
> Sent: Tuesday, April 14, 2009 12:46 PM
> To: users_at_subversion.tigris.org
> Subject: svn co $file without svn update .
>
> Hi
>
> I'm trying to do targeting rollout, and i have a directory
> that contains hundreds files and subdirectories, and I need
> to download only one file from svn to top directory and when
> I try svn co -r rev url I get
>
> svn: Working copy 'XXX' not locked
>
> my "workaround" was to do svn update . and then roll back
> files to state there were before i do svn update, but is
> there a better way to do it?
>
>
> --
> http://alexus.org/
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&
> dsMessageId=1715266
>
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe_at_subversion.tigris.org].
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1715892
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-14 22:44:33 CEST