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

Re: Setting bugtraq properties to all projects in a repository

From: Manuel Ferrero <mferrero_at_reer.it>
Date: Tue, 04 Dec 2012 09:57:25 +0100

Andy Levy ha wrote:

> You can configure automatic property setting on each client (auto-props
> in your config file, and tsvn:autoprops on your folders but only used by
> Tortoise, see
> http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-propertypage.html),
> and you can configure a pre-commit hook script to reject any commit
> where new items lack the property or existing items have the property
> removed, but you can't control client configuration via the server.

So basically you're saying that those properties shall be set by the
client and then committed to the server.

The thing that I don't understand is why I cannot set the property on
the server side.
If I understood correctly, all the properties are linked to the
directory, so once I set a new property and I commit the directory
everybody that checks out that directory will see that property on it,
right? So how come that I have to set the property on one client and I
can't do that directly on the server?

-- 
Regards,
Manuel Ferrero
R&D department
Reer SpA	
Tel.  +39 011 2482215
Fax. +39 011 859867
L'utilizzo non autorizzato del presente messaggio e' vietato e potrebbe costituire reato.
Se il presente messaggio non e' a Lei indirizzato, il suo contenuto non deve essere considerato
come trasmesso o autorizzato dalla Reer SpA; in tale caso Le saremmo grati se, via e-mail,
ce ne comunicasse l'errata ricezione.
The unauthorized use of this e-mail is prohibited and could constitute an offence.
If you are not the intended recipient of this message its contents shall be understood as neither
given nor endorsed by Reer SpA. Please notify Reer SpA by e-mail immediately in that case.
Received on 2012-12-04 09:59:03 CET

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.