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?
If it's a client-side setting, then it's not nearly as useful to me. This
goes back to the general issue I have with subversion where I can't manage
the properties of clients from a single point (namely the server), which
would be much more powerful, in my opinion. Is there any move afoot for
future subversion changes to support a single-point-of-client control?
-Matt
At 3/12/2006 07:04 PM, Tony Morris wrote:
>I am by no means an expert, but I have used the svn:eol-style property.
>You can set it to apply to commits of specific file types in the Subversion
>config file as an 'auto-prop'.
>
>Tony Morris
>http://tmorris.net/
>
>
>-----Original Message-----
>From: Matt England [mailto:mengland@mengland.net]
>Sent: Monday, March 13, 2006 10:52 AM
>To: SVN Users email list
>Cc: mengland@mengland.net
>Subject: Standardize on ASCII type: dos2unix pre-commit hook?
>
>The various repos I administer finds users putting different text/ASCII
>types (dos and unix, maybe some old mac) in the text-file content. This
>screws up the diff comparisons, merges, and other things.
>
>I'd like to auto-force a standard unix text across certain repos (if not
>all of them). My current thinking is to run a dos2unix/mac2unix pre-commit
>hook. Is this a good/best way to go?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 13 17:05:24 2006