MatCat.OpenSource/8sa1-binutils-gdb
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Add obvious fix rule

Browse Source
This commit is contained in:
Nick Clifton 2001-02-14 18:49:56 +00:00
parent fc24370e47
commit a9f1078629
2 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
binutils/ChangeLog
View File

@ -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> 2001-02-11 Michael Sokolov <msokolov@ivan.Harhan.ORG>
* unwind-ia64.c: Don't use ANSI C preprocessor stringisation and string * unwind-ia64.c: Don't use ANSI C preprocessor stringisation and string

11
binutils/MAINTAINERS
View File

@ -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 [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 *ability* to do binutils checkins, you're in this group. Just remember
to get approval before checking anything in.] 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.