Give it a chance. I think you will like it.
I am a relatively new Subversion user, but a long-time ClearCase and RCS
user. ClearCase makes all files read-only unless they have been
checked-out -- which ClearCase treats separately from obtaining an
"exclusive lock". While you can do any of the above with Subversion,
the default is that everything in the working copy is checked out. I
find this much more pragmatic than any of the more restrictive options.
In one case, however, the more restrictive approach helps prevent an
accidentally-modified file (e.g., with a temporary debug logging
statement) from being committed as a part of a group of files. This is
easily managed by the discipline of looking at the list of changed
files before committing them.
If you want the more restrictive approaches, you can export files from
Subversion without checking them out, and you can obtain an exclusive
lock on files.
--Wayne Cannon
Andy Levy wrote:
> 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
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 12 17:40:41 2007