Add obvious fix rule

diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index ae1bb587d6f2a9f0c027b8a6d3fd9c258e904273..00e8e723d5d9269dfb28513b4e11e78a7e2452f6 100644 (file)
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,7 @@
+2001-02-14  Nick Clifton  <nickc@redhat.com>
+
+       * MAINTAINERS: Add "Obvious Fix" rule.
+
 2001-02-11  Michael Sokolov  <msokolov@ivan.Harhan.ORG>
 
        * unwind-ia64.c: Don't use ANSI C preprocessor stringisation and string

diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS
index 427dd3acdf7cce4fb0fa64ea4fa616de0d4600e3..ec66a38e4142f98fc6e53e63fa1635d3dac09e8b 100644 (file)
--- a/binutils/MAINTAINERS
+++ b/binutils/MAINTAINERS
@@ -76,3 +76,14 @@ one of the above lists (blanket write or maintainers).
 [It's a huge list, folks.  You know who you are.  If you have the
  *ability* to do binutils checkins, you're in this group.  Just remember
  to get approval before checking anything in.]
+
+              -------------  Obvious Fixes -------------
+
+Fixes for obvious mistakes do not need approval, and can be checked in
+right away, but the patch should still be sent to the binutils list.
+The definition of obvious is a bit hazy, and if you are not sure, then
+you should seek approval first.  Obvious fixes include fixes for
+spelling mistakes, blatantly incorrect code (where the correct code is
+also blatantly obvious), and so on.  Obvious fixes should always be
+small, the larger they are, the more likely it is that they contain
+some un-obvious side effect or consequence.