It appears that "locking" the file makes it so that other users are
unable to edit the file. I was looking more for a way to essentially
"sync" your copy of the repository so you can build, etc. but when you
want you actually edit a file, you can explicitly checkout the file for
editing. This does not mean that other people can't do the same, it just
prevents a user from accidentally modifying some portion of the source
because they have not explicitly checked out that file for editing. This
sounds like more of a client-side feature in that the client can get a
copy of the repository but make all the files read-only and changes to
those files will only be commited if the file is checked out for
editing. Does that help explain the issue any clearer?
Thanks,
Patrick
Patrick Burleson wrote:
>On Apr 1, 2005 2:03 PM, Patrick Hanna <patrick.hanna@openwave.com> wrote:
>
>
>>Is there a method for obtaining a module that creates a read-only copy
>>of the module? This way, if a developer wants to edit the file, they can
>>then specifically checkout the file for editing. This will prevent
>>accidental editing of files that a developer may not need to edit. Thanks,
>>
>>Patrick
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>For additional commands, e-mail: users-help@subversion.tigris.org
>>
>>
>>
>>
>
>I think you are going to want to wait until Subversion 1.2, which will
>include locking of files, which is essentially what you want.
>
>Patrick
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 2 17:12:09 2005