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

Re: How can I get files locked as default

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-03-20 20:48:46 CET

On Mar 20, 2007, at 09:20, Miller, Eric wrote:

>>> I want to use SVN for many configuration-files in excel-format. We
>>> want to have that every time only one person is allowed to make
>>> changes on it. How cab I set the files locked as default, so that
>>> SVN allowed me only to read it, if somebody is making changes on it?
>>
>> Hi. You can configure the client to automatically add the svn:needs-
>> lock property to files with a certain extension (like .xls). The
>> feautre is called auto-props (automatic properties) and is described
>> in further detail in the book at http://svnbook.org as is locking.
>> The file you want to edit is ~/.subversion/config (on Unix-like
>> machines, anyway; on Windows the file is elsewhere).
>>
>> Since this is a client-side setting, it is up to each user to
>> configure their system this way. To ensure that they do, you can
>> write a pre-commit hook which would reject the commit of any .xls
>> file which did not have the svn:needs-lock property.
>
> You can also specify --config-dir and point to a common config file.
>
> You can just write a simple wrapper or alias around the svn client to
> always use that config file.

Ok, but writing an appropriate pre-commit hook is still a good idea,
to catch those who have forgotten to use this wrapper. (Perhaps
someone just reinstalled their machine and forgot to install the
wrapper.)

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 20 20:49:19 2007

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.