You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by br...@apache.org on 2004/09/16 15:26:51 UTC
svn commit: rev 46176 - forrest/trunk/src/documentation/content/xdocs
Author: brondsem
Date: Thu Sep 16 06:26:50 2004
New Revision: 46176
Modified:
forrest/trunk/src/documentation/content/xdocs/contrib.xml
Log:
explain line ending issues in SVN
Modified: forrest/trunk/src/documentation/content/xdocs/contrib.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/contrib.xml (original)
+++ forrest/trunk/src/documentation/content/xdocs/contrib.xml Thu Sep 16 06:26:50 2004
@@ -98,6 +98,15 @@
checked out via the http: protocol, then the following command will
convert it.</p>
<source>svn sw https://svn.apache.org/repos/asf/forrest/trunk</source>
+ <p>Line ending issues can be a problem when committing, since developers use
+ both Linux and Windows. SVN can understand that files are text (as opposed to binary like images), but
+ this must be specified for every new file added. The commandline SVN client
+ can be <link href="http://issues.cocoondev.org/browse/FOR-124">configured to automatically do this</link>
+ for certain file extensions. To do it manually, make sure all line endings
+ are in your current OS's native format (the dos2unix and unix2dos utilities
+ may be useful) and then do a <code>svn propset svn:eol-style native myfilename.txt</code>
+ and <code>svn commit -m "fix line endings" myfilename.txt</code>
+ </p>
</section>
<section id="procedure">