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

Re: svn:needs-lock

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-12-22 14:01:54 CET

On 12/22/06, LievenCardoen <Lieven.Cardoen@indiegroup.be> wrote:
> Hello,
> Is it possible to set the property svn:needs-lock on the server side. It
> should always be set, on any file that is added to the version control (of
> every project)?

Not directly. You can install a pre-commit hook to inform the user
that they can't commit any files without this attribute and reject the
commit, but that's about it. Before you ask about having the hook set
the attribute, don't. Modifying an in-progress transaction is a very
bad idea.

But ask yourself why you're setting this requirement. Subversion is
built primarily on a copy-modify-merge model, instead of the
lock-modify-unlock model other systems use. This model is being
abandoned by many of those vendors because it's inefficient and
inconvenient. Requiring this lock on binaries which can't be
diffed/merged easily is one thing, but doing it unilaterally is just
going to make things more cumbersome, especially for plain text files.

Plus, locks can be stolen by any user. They're really only
informational, they can't "force" anything.

To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Dec 22 14:02:09 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.