At 3/13/2006 10:09 AM, Ryan Schmidt wrote:
>On Mar 13, 2006, at 16:46, Matt England wrote:
>
>>Does there exist a way to manage this mechanism (svn:eol-style
>>property, or anything else) such that "ASCII standarizations" will
>>be made regardless of client-side settings?
>>
>>In other words, is this a client-side setting or a server-side
>>setting? Or is this question pertinent?
>
>The settings are client-side. Server-side, you have hooks. So the
>complete solution is to set up auto-props in the clients' config
>files, and install a pre-commit hook which prevents people from
>committing things which do not have the correct properties on the
>files, possibly referring in the error message to a web page where
>the user could download a properly-configured config file.
Ok, good.
A few questions about this:
Do I understand correctly that the above procedure requires one and only
one manual, client-side setting to 'enable-auto-props = yes' (not sure of
the exact syntax) in the client-side .subversion config file?
Also, the svn book says:
"
enable-auto-props
This instructs Subversion to automatically set properties on newly added or
imported files. The default value is no, so set this to yes to enable
Auto-props. The auto-props section of this file specifies which properties
are to be set on which files.
"
What happens for *existing* files in the repo? Do they inherit this
"auto-props" setting (or is this auto-props setting not a per-file
thing)? In other words, will the svn:eol-style setting work on existing
files in my repo?
I'm still feeling my way through this process, so my apologies if I'm
asking ignorant questions.
-Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 13 20:55:05 2006