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

Re: How do I apply svn:needs-lock to an entire repository?

From: James FitzGibbon <jfitzgibbon_at_primustel.ca>
Date: 2005-07-21 12:21:22 CEST

On Jul-20-05, at 3:42 PM, Phil wrote:

> Thank you!!!!
>
> Work perfectly.
>
> Thanks again!
>
> On 7/20/05, Mark Phippard <MarkP@softlanding.com> wrote:
>
>> svn propset -R svn:needs-lock yes wc
>>

Don't forget to make yourself a pre-commit check that ensures that
the property is set on newly added files. Or, you could have a
maint. task walk the repo on a regular basis, setting the property
and doing an automated checkin. Unlike other external maint. tasks
that have the potential to require the users to constantly run 'stat -
u' followed by 'update' to track the maint. changes, the addition of
a property that doesn't really have a value shouldn't cause merge
conflicts.

I suppose if your maint. task added 'svn:needs-lock=1' and a user
added a file, committed it and then added 'svn:needs-lock=yes' you
might run into trouble, but that's more of a training issue as to
what value you want your users to use for 'svn:needs-lock'.

Regards

-- 
j.
James FitzGibbon
Systems Developer, Primus Telecommunications Canada
416.644.6111
-- 
----------------------------------------------------------------------------
This electronic message contains information from Primus Telecommunications
Canada Inc. ("PRIMUS") , which may be legally privileged and confidential.
The information is intended to be for the use of the individual(s) or entity
named above. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this information
is prohibited. If you have received this electronic message in error, please
notify us by telephone or e-mail (to the number or address above)
immediately. Any views, opinions or advice expressed in this electronic
message are not necessarily the views, opinions or advice of PRIMUS.
It is the responsibility of the recipient to ensure that
any attachments are virus free and PRIMUS bears no responsibility
for any loss or damage arising in any way from the use
thereof.The term "PRIMUS" includes its affiliates.
----------------------------------------------------------------------------
Pour la version en français de ce message, veuillez voir
 http://www.primustel.ca/fr/legal/cs.htm
----------------------------------------------------------------------------
Received on Thu Jul 21 12:22:57 2005

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.