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

Re: SVN Query

From: Jeremy Pereira <jeremyp_at_jeremyp.net>
Date: 2007-10-12 10:57:20 CEST

On 12 Oct 2007, at 07:01, Joshi, Mahesh wrote:

>
>
>
> Hello,
>
> First of all thanks for your reply.
>
> When I checkout the code from SVN repository from the server I get all
> the code in writable mode. But using CVS when we get the code, it
> is in
> read-only mode and if one needs to modify the code, CVS does not allow
> it unless the user checkouts the file, whereas in SVN any user can

cvs checkout means the same thing as svn checkout. I think you mean
that the user has to cvs edit the file to make it read/write. The
same behaviour can be achieved with subversion by setting svn:needs-
lock property on the files.

> modify the code without locking it. So I want to force the user to
> checkout the file(s) before it can be edited by the user.
>
> How this can be achieved in SVN?
>
>
> -----Original Message-----
> From: Andy Levy [mailto:andy.levy@gmail.com]
> Sent: Friday, October 12, 2007 4:38 AM
> To: Joshi, Mahesh
> Cc: users@subversion.tigris.org
> Subject: Re: SVN Query
>
> 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. >
>>
>> 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 11:10:28 2007

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.