On Mon, Apr 6, 2009 at 10:49, Dieter Oberkofler
<doberkofler.lists_at_gmail.com> wrote:
> Understood, but is there any way to force setting preferences instead of
> just making sure that they are already set properly?
You can't "force" a client to do anything. The best you can do is
distribute a well-written config file to set auto-props on newly-added
files. But there's no guarantee that your users won't override or edit
those auto-props.
>> -----Original Message-----
>> From: Andy Levy [mailto:andy.levy_at_gmail.com]
>> Sent: Monday, April 06, 2009 2:18 PM
>> To: doberkofler.lists_at_gmail.com
>> Cc: users_at_subversion.tigris.org
>> Subject: Re: Default server based properties
>>
>> On Mon, Apr 6, 2009 at 06:08, dieter oberkofler
>> <doberkofler.lists_at_gmail.com> wrote:
>> > Hi,
>> > How would I force Subversion to set some default properties for
>> > all/some files on the server side?
>> > I would for example like to have all document files (either by
>> > extension or for a directory) created with the "needs-lock"
>> property.
>> > Thank you,
>>
>> Any "forcing" you do must be via a pre-commit hook which
>> rejects any commit not conforming to your requirements.
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1562275
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-06 16:54:23 CEST