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

Re: Per repository settings in the Subversion Configuration File

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: Thu, 11 Mar 2010 22:54:40 +0100


On 11 March 2010 22:04, Todd <toddyboy82577_at_gmail.com> wrote:
> In our company we have users that work in a single repository and
> users that work in numerous repositories.  Some of the repositories
> are configured to require all files to have the needs-lock property
> set, while other repos have zero constraints.
> For the users working in a single repo with the needs-lock required,
> we can setup the Subversion configuration file to add the properties
> automatically and everything works well. For the users working in
> multiple repos that scenario doesn't work so well because they don't
> want to be adding the needs-lock property to files if it is not
> required.
> Is there a way customize the Subversion Configuration file to set
> properties on a repo by repo case?  If this functionality is not
> available, what alternative solutions to you suggest?

You can use the tsvn:autoprops properties. When set on a folder it
will act similar to the svn:autoprops, but only for files added in the

.       ___
.  @@  // \\      "De Chelonian Mobile"
. (_,\/ \_/ \     TortoiseSVN
.   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
.   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-11 22:55:48 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.