aboutsummaryrefslogtreecommitdiff
path: root/binutils/MAINTAINERS
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2001-02-14 18:49:56 +0000
committerNick Clifton <nickc@redhat.com>2001-02-14 18:49:56 +0000
commita9f1078629b87bb73266591e78a090b7b8c2ad99 (patch)
tree8aa398d686c3ea3a534cb0e809f3551754f90297 /binutils/MAINTAINERS
parentfc24370e47de795c93e5be9bcc1bcebf739a0b67 (diff)
downloadgdb-a9f1078629b87bb73266591e78a090b7b8c2ad99.zip
gdb-a9f1078629b87bb73266591e78a090b7b8c2ad99.tar.gz
gdb-a9f1078629b87bb73266591e78a090b7b8c2ad99.tar.bz2
Add obvious fix rule
Diffstat (limited to 'binutils/MAINTAINERS')
-rw-r--r--binutils/MAINTAINERS11
1 files changed, 11 insertions, 0 deletions
diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS
index 427dd3a..ec66a38 100644
--- 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.