Daniel John Debrunner wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
myrnap wrote:
Kathey Marsden wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Can you ensure that for any text files you added, the svn property svn:eol-style is set to native. Do an 'svn help propset' for details.
The property must be set on a machine that is running the same os as the one you committed (added) the files from.
Without this step, patches will cause problems across windows/linux.
Is there a way to make this the default for all files added to our repository?
From my google searching I saw that you can make it the default byediting a config file and enabling auto-props...You can specify the extension and the default eol-style you want. Maybe that's an idea.
Just to clear, svn:eol-style native should be the default for *text* files, not all files in the repository.
When I looked at it first, I saw that you can set up defaults but it wasn't clear to me if it would apply just to the Derby files or to the complete svn repository at Apache. Obviously if it is the latter then it's a decision that needs to be made elsewhere.
Dan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBrhOWIv0S4qsbfuQRArupAKCGdgmcQ9ztopxAtO93nKSwTPAhdACdGr/6 ST2DjCr5u4cdc+u/nDwOmqw= =Ned2 -----END PGP SIGNATURE-----
It looks like:
[EMAIL PROTECTED] NetworkServer]$ ls bin readme.html
[EMAIL PROTECTED] NetworkServer]$ svn -R propset svn:eol-style native *.* property 'svn:eol-style' set (recursively) on 'readme.html'
This shows up in the diff after changes to eol-style are set:
Property changes on: readme.html
___________________________________________________________________
Name: svn:eol-style + native
I'm a bit uncertain abou the -R, I guessed it would do a recursive path traversal, but it doesn't. Manual time again.
scott
scott
