Opened 16 years ago
Last modified 14 years ago
#1020 closed task (fixed)
Please add svn property 'svn:eol-style native' to _all_ text files
Reported by: | Dietmar Winkler | Owned by: | Dietmar Winkler |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Version: | ||
Keywords: | Cc: | Dietmar Winkler, |
Description
It would be nice if all text files would get the svn property svn:eol-style native set.
Currently I'm checking file out with a linux machine and when I check in changes the CRLF will be transformed to LF unnecessarily. Setting svn:eol-style native will adjust the line endings natively to your OS with which you checkout.
You can do this globally quite easy by editing $HOME/.subversion/config and then run this python script:
http://subversion.tigris.org/tools_contrib.html#svn_apply_autoprops_py
This should also be done for all the other repos.
Change History (6)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Well in that case simply add in .subversion/config
*.h = svn:eol-style=native *.c = svn:eol-style=native *.whathaveyou = svn:eol-style=native compiler/*.mo = svn:eol-style=LF
and use the python script to apply the changes and check before the commit.
comment:3 by , 16 years ago
OK. I'll see if I can I do this with TortoiseSVN
and if not I'll boot my Ubuntu virtual machine
and give it a try from there.
Cheers,
Adrian Pop/
comment:4 by , 16 years ago
This was resolved in r3732
Commit message:
Formal clean up of all code files:
- applied svn:eol-style native to all files except Compiler/*.mo --> LF
- unified the eol-style of ALL files (this was necessary in order to set the svn properties
- unification was done by a script which also removed all trailing whitespaces (except for all files in testsuite as white spaces are necessary to successful compare the results, could be improved maybe)
- make clean all test --> sucess on Ubuntu Linux 8.10, proably a good idea to run it for the other platforms as well.
- FYI: script to remove trailing white spaces: http://is.gd/5A6B
comment:5 by , 14 years ago
Closing this as it was previously resolved (we now have a make target that sets the svn properties as we can't force all our users to use a customized subversion config-file). The eol-style used is LF instead of native though. The important thing is that the svn server normalizes all line endings on commit.
comment:6 by , 14 years ago
I wasn't aware that you can force a certain line-ending on the server side. Is that done by post-commit hooks?
Hi,
We cannot do that for Compiler/*.mo files as the debugger expects them with
LF style endings. Otherwise the execution pointer is way off.
For all other files is fine.
Cheers,
Adrian Pop/