This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[wwwdocs] Update obvious fix commit policy


[ sent first version in html. apologies for the dup. ]

Based on the recent discussion on the obvious fix policy.

OK to commit?

Index: htdocs/svnwrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
retrieving revision 1.29
diff -u -d -u -p -r1.29 svnwrite.html
--- htdocs/svnwrite.html        24 Sep 2013 18:26:29 -0000      1.29
+++ htdocs/svnwrite.html        28 Nov 2013 12:04:40 -0000
@@ -147,10 +147,13 @@ list.</p>

 <p>The following changes can be made by everyone with SVN write access:</p>

-<p>Fixes for obvious typos in ChangeLog files, docs, web pages, comments
-and similar stuff.  Just check in the fix and copy it to
-<code>gcc-patches</code>.  We don't want to get overly anal-retentive
-about checkin policies.</p>
+<p>Obvious fixes to documentation, code and test cases can be
+committed without prior approval.  Just check in the fix and copy it
+to <code>gcc-patches</code>.  A good test to determine whether a fix
+is obvious: "will the person who objects to my work the most be able
+to find a fault with my fix?".  If the fix is later found to be
+faulty, it can always be rolled back.  We don't want to get overly
+anal-retentive about checkin policies.</p>

 <p>Similarly, no outside approval is needed to revert a patch that you
 checked in.</p>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]