On 4/11/06, JIRAT SRISAWAT <JIRATSR@set.or.th> wrote:
>
>
> Hi,
> Can we set every new create file in subversion to be read only and need to
> lock before edit by default?
> I would like to do the same things as VSS that we can not edit any file that
> we didn't lock it.
>
> now I can do only set svn:need-lock recursive to my working folder everytime
> I add new file...
> can we do it by default ?
Ryan gave you the answer for "how" - but I'm going to ask "why?"
There are definitely legitimate reasons for locking a file. However,
Subversion's working model is quite different from VSS's (and
discourages exclusive locks, unlike VSS which depends upon them), and
IMHO it's better to work *with* that model than to attempt to force
SVN to act like VSS. Having used both VSS and SVN, SVN's copy/merge
model is far easier to work with, especially with multiple developers
working in the same groups of files. It's just a matter of
understanding the right way to work. The Book (Ryan gave a link)
explains quite well.
In summary...before setting a global policy of requiring locks on all
files, ask yourself if you're doing it because that's what VSS did, or
because your *entire project* actually requires it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 12 16:10:49 2006