You can use auto-props. But that is a client side feature not a server
side. I think the best practice is to use auto-props on the client and
use a pre-commit script on the server to ensure correct properties
exist. Your devs will be annoyed with the message that they will
eventually set up their autoprops.
BOb
> -----Original Message-----
> From: dieter oberkofler [mailto:doberkofler.lists_at_gmail.com]
> Sent: Monday, April 06, 2009 10:50 AM
> To: 'Andy Levy'
> Cc: users_at_subversion.tigris.org
> Subject: RE: Default server based properties
>
> Understood, but is there any way to force setting preferences instead
of
> just making sure that they are already set properly?
> Thank you,
> D
>
> > -----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&dsMessageI
d=
> 1562269
>
> To unsubscribe from this discussion, e-mail: [users-
> unsubscribe_at_subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1562296
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-06 16:56:12 CEST