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

Re: server-side auto-set svn-prop: need-lock

From: Paul R <paul.r.ml_at_gmail.com>
Date: Thu, 07 Aug 2008 20:57:19 +0200

Hi Kevin,

On Thu, 7 Aug 2008 13:45:36 -0500, kmradke_at_rockwellcollins.com said:
kevin> I don't recommend it (even though I wrote it), but you can
kevin> install a server side hook that adds the missing needs-lock
kevin> property as a new commit if it is missing. (Or you can run the
kevin> script periodically to do the same, but for multiple files at
kevin> a time.)

kevin> The biggest problem is user confusion, since as soon as they
kevin> checkin a file with the missing properties, their version is
kevin> obsolete. They wouldn't expect this and have no way to know
kevin> this unless they do an update right after they do the commit.

Is this the only reason why you don't recommand it ? I was starting to
set up such a solution.

kevin> In any case, it can be found here:

kevin> http://svn.collab.net/repos/svn/trunk/contrib/server-side/add-needs-lock.py

kevin> It requires the python subversion bindings, and needs direct
kevin> access to the repository. It operates directly on the
kevin> repository, so no intermediate working copy is needed on the
kevin> Subversion server.

Sounds good, thank you very much for this tip, that's the way I'm
going through now, as it seems to be the best option in my case.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-07 20:57:53 CEST

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.