In
http://www.apache.org/dev/version-control.html
the ASF suggests:
Committers will need to properly configure their svn client. One
particular issue is OS-specific line-endings for text files. When you
add a new text file, especially when applying patches from Bugzilla,
first ensure that the line-endings are appropriate for your system, then
do ...
svn add test.txt
svn propset svn:eol-style native test.txt
Your svn client can be configured to do that automatically for some
common file types. Add the list to your ~/.subversion/config file.
The last line links to:
http://www.apache.org/dev/svn-eol-style.txt
I used this and up to now had no problems with new files in connectors.
But: when I check out the TC6 files, I get a funny mix of line ending
types. So I think at the moment htey are not very consistent in the
repository. I remember Filip also having some trouble.
Maybe we need to set everything to native, checkout, convert those that
have the wrong endings and commit?
Rainer
Mladen Turk wrote:
Remy Maucherat wrote:
[EMAIL PROTECTED] wrote:
Author: mturk
Date: Tue Jul 18 08:38:14 2006
New Revision: 423119
URL: http://svn.apache.org/viewvc?rev=423119&view=rev
Log:
Add svn:eol-style:native.
We'll probably need to do that for the entire repository.
-1. This will screw up diffs, which will create much bigger problems.
???
Are you sure?
I think that the current situation is screwing the diffs.
All .txt files should have svn:eol-style:native
All .sh files should have svn:eol-style:native;svn:executable
etc...
Anyhow see:
http://svnbook.red-bean.com/en/1.0/ch07s02.html#svn-ch-7-sect-2.3.5
--
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
