That would help- indeed its not a good solution for me because its just difficult to setup :P I am not getting used to it... what I am used to are visual source safe, PVCS...
Also another problem is so far I cannot find a good SCC provider for SVN as well
From: David Weintraub [mailto:email@example.com]
Sent: Sat 8/20/2005 2:47 AM
To: William Yeung
Subject: Re: Is that possible to enforce lock-modify-unlock model in a repository
I'm not sure how forcing locks on every file will improve your
situation. But, as everyone else mentioned, you can put the property
"svn:needs-lock" on every file.
I'm not sure why you say autoprops is not a good solution since it
will automatically add this property to every file you create.
Maybe you're talking about an enforcement mechanism to ensure that
this property is set? After all, a user can remove the property, or if
the user doesn't have their conf file setup correctly, the
svn:needs-lock won't be set.
I have a hook that will check properties and prevent commits if the
properties on that file aren't setup correctly. If someone removes
svn:needs-lock or creates a file without this property, they won't be
able to commit any changes unless they attach svn:needs-lock back on
Will this help?
On 8/18/05, William Yeung <firstname.lastname@example.org> wrote:
> Dear All,
> I am a newbie in subversion, while I found the facilities are great
> (especially with TortoiseSVN), I have an issue here- my team are more used
> to lock-modify-unlock mechanism, and I have bad habits on forgot to check in
> source code, so this is more suitable for us :P Is there anyway to enforce
> such policy within an repository?
> William Yeung
> IT Manager
> V-Logic Limited
> E-Mail: email@example.com
> Direct: 3102 3552
> Fax: 3101 0121
Received on Sat Aug 20 05:11:06 2005