On Aug 15, 2006, at 14:54, Rob Wilkerson wrote:
>>> The file you reference is in *my* home directory. Presumably, then,
>>> setting autoprops in that file will only affect commits made by me.
>>> Is there a way to set those autoprops "globally"?
>>
>> Yes, it only affects your commits. No, you cannot set it globally.
>> What you can do is install a pre-commit hook which verifies incoming
>> commits and rejects any that do not meet your autoprops definitions.
>> The error message you print could direct people to a Subversion
>> config file that's already set up correctly, for example on a web
>> page somewhere. You'd have to write this script though.
>
> Ryan, your message left me wondering whether I really understand the
> use of svn:keywords or, perhaps, the autoprops setting. I don't
> necessarily want to force developers to include any or all keywords,
> but I want Subversion to always updated files if the keywords are
> present. I thought that, in order to do the latter, I had to
> explicitly tell svn to recognize certain keywords. Is my
> understanding correct or am I horribly misguided?
Oh. Well if you don't want to require certain keywords on all files
of a certain type, then you can skip the hook script.
The point of autoprops is also to cause certain properties (for
example, keywords) to be applied automatically to all files matching
a given regular expression (for example, all *.c files). So if you
don't want keywords automatically on all files of a certain type, but
rather on only specific files, then you can skip the autoprops too.
You can just set the svn:keywords property on the files where you
want it, and any Subversion client will expand those keywords on
checkout. (Keyword expansion happens client-side after checkout or
update, not server-side.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 15 15:18:35 2006