From: Nick Clifton Date: Wed, 14 Feb 2001 18:49:56 +0000 (+0000) Subject: Add obvious fix rule X-Git-Tag: jimb_gnu_v3_branchpoint~182 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a9f1078629b87bb73266591e78a090b7b8c2ad99;p=platform%2Fupstream%2Fbinutils.git Add obvious fix rule --- diff --git a/binutils/ChangeLog b/binutils/ChangeLog index ae1bb58..00e8e72 100644 --- a/binutils/ChangeLog +++ b/binutils/ChangeLog @@ -1,3 +1,7 @@ +2001-02-14 Nick Clifton + + * MAINTAINERS: Add "Obvious Fix" rule. + 2001-02-11 Michael Sokolov * unwind-ia64.c: Don't use ANSI C preprocessor stringisation and string 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.