On 10/11/07, Joshi, Mahesh <Mahesh.Joshi@fiserv.co.in> wrote:
>
> I had installed SVN, created a repository and configure it on my machine
> successfully. Also I configured SVN on my Eclipse3.2 IDE. Now when I get the
> code from repository to some client machine. And when I started editing the
> file after the checkout the project on my local machine.
>
>
>
> My question is that if I commit a file after modification and again I try to
> edit it without checking out it should not allow me. And once a user
> checkout a file other should not edit it like in CVS.
>
> How this can be achieved.
I think you misunderstand the meaning of "checkout" as it relates to
Subversion. With Subversion, all users can edit in their working copy
at anytime, and their changes are merged with others' when committing.
Your working copy is always writable, unless you have files which have
the needs-lock property set on files, which will make them read-only
until you've claimed a lock.
Have you read the Subversion manual yet? It explains quite well the
difference between the copy-modify-merge model (default in Subversion)
and the lock-modify-unlock model (which you're apparently expecting).
http://svnbook.red-bean.com/en/1.4/svn.basic.vsn-models.html explains
that specifically, but reading the whole book is recommended.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 12 01:13:02 2007