[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: Andy Levy <andy.levy_at_gmail.com>
Date: Thu, 11 Mar 2010 20:12:36 -0500

On Thu, Mar 11, 2010 at 16:54, Jean-Marc van Leerdam
<j.m.van.leerdam_at_gmail.com> wrote:
> Hi,
> 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
> folder(tree).

Keep in mind that this property will only be honored by TSVN; if you
have a mixed user base (I personally use as many as 3 clients with the
same WC - command-line, TSVN & Subclipse), you can't rely upon it.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-12 02:13:58 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.