forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r179353 - /forrest/trunk/site-author/content/xdocs/contrib.xml
Date Wed, 01 Jun 2005 04:29:31 GMT
Author: crossley
Date: Tue May 31 21:29:29 2005
New Revision: 179353

URL: http://svn.apache.org/viewcvs?rev=179353&view=rev
Log:
Point to the ASF dev docs for version control info for committers.

Modified:
    forrest/trunk/site-author/content/xdocs/contrib.xml

Modified: forrest/trunk/site-author/content/xdocs/contrib.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/contrib.xml?rev=179353&r1=179352&r2=179353&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/contrib.xml (original)
+++ forrest/trunk/site-author/content/xdocs/contrib.xml Tue May 31 21:29:29 2005
@@ -92,7 +92,11 @@
     <title>SVN Committer with Secure Shell access</title>
       <p>After a developer has consistently provided contributions (code,
         documentation and discussion) and demonstrated committment, then the rest of the
dev community may vote to
-        grant this developer commit access to the Subversion repository. </p>
+        grant this developer commit access to the Subversion repository.
+        See the <link href="http://www.apache.org/dev/">ASF developers resources</link>
+        especially the 
+        <link href="http://www.apache.org/dev/version-control.html">Source code repositories</link>.
+      </p>
       <p>You will need secure access to the repository to be able to commit
         patches. Commits to the SVN repository must use the https: protocol.
         If you already have the codebase
@@ -101,9 +105,11 @@
       <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
+        this must be specified for every new file added. Your SVN client
+        can be 
+        <link href="http://www.apache.org/dev/version-control.html#https-svn">configured</link>
+        to automatically do this 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>



Mime
View raw message