diff mbox series

[wwwdocs] svnwrite.html - reduce references to SVN

Message ID alpine.LSU.2.21.1812311326310.15084@anthias.pfeifer.com
State New
Headers show
Series [wwwdocs] svnwrite.html - reduce references to SVN | expand

Commit Message

Gerald Pfeifer Jan. 12, 2019, 4:27 p.m. UTC 
When migrating from CVS to SVN I already reduced direct references
to CVS/SVN, and expecting a migration to GIT in this decade let me
take the opportunity to generalize/simplify things a bit further.

Committed.

(Perhaps we should also start refering to the more general term
"commit" vs "check in"?)

Gerald
diff mbox series

Patch

Index: svnwrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
retrieving revision 1.42
diff -u -r1.42 svnwrite.html
--- svnwrite.html	30 Sep 2018 14:38:47 -0000	1.42
+++ svnwrite.html	12 Jan 2019 16:23:09 -0000
@@ -142,7 +142,7 @@ 
 
 <h3>Free for all</h3>
 
-<p>The following changes can be made by everyone with SVN write access:</p>
+<p>The following changes can be made by everyone with write access:</p>
 
 <p>Obvious fixes can be committed without prior approval.  Just check
 in the fix and copy it to <code>gcc-patches</code>.  A good test to
@@ -207,13 +207,12 @@ 
 when performing checkins to avoid accidental checkins of local
 code.</p>
 
-<p>We prefer that each SVN checkin be of a complete, single logical
+<p>We prefer that each checkin be of a complete, single logical
 change, which may affect multiple files.  The log message for that
 checkin should be the complete ChangeLog entry for the change.  This
 makes it easier to correlate changes across files, and minimizes the
 time the repository is inconsistent.  If you have several unrelated
-changes, you should check them in with separate SVN commit
-commands.</p>
+changes, you should check them in separately.</p>
 
 <ol>
 <li>Sync your sources with the master repository via "<code>svn