On 8/13/06, Andreas Guther <Andreas.Guther@markettools.com> wrote:
> Hi,
>
> I am unlucky in finding information on how to turn on per default the
> svn:keywords properties.
>
> So far all I can find and do is to either set the svn:keywords
> properties on a per file basis or recursively. I rather would like to
> tell the svn server to set the keywords per default and turn it off
> manually where needed.
>
> We have a standard header for our source files with different SVN
> keywords. But very often developers forget to turn set the properties
> for a new file. From time to time we then set the keywords recursively
> on the source tree but that results in a forced change/commit of all
> files.
>
> Is there a way to set the svn:keywords per default on the SVN server
> (implicit) rather than on a manual basis (explicit)?
Currently this is stricly client-based; you need to set the properties
at the client end and check it in. Two things you can do:
#1 - Distribute an auto-props configuration to all developers and ask
them to roll it into their Subversion client config
#2 - Write a pre-commit hook to deny adding/committing any files that
don't have the desired properties set appropriately
#1 can be hard to enforce, since everyone can edit their own
subversion client config. I've faced exactly this; I have a pretty
thorough auto-props config for what I'm working on, but the other
person working on the project hasn't set his own up to match (though I
have told him what my config is). As a result, I run
svn_apply_autoprops.py against my WC about once a week to catch up
with any new files he's added without the properties we want. #2 is
the more draconian approach and could really tick people off.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 13 20:09:48 2006