diff options
| author | Nick Clifton <nickc@redhat.com> | 2001-02-14 18:49:56 +0000 |
|---|---|---|
| committer | Nick Clifton <nickc@redhat.com> | 2001-02-14 18:49:56 +0000 |
| commit | 7ba25ce72c420a69f16b414b805bd6c497cbcaac (patch) | |
| tree | 171129902295a22cb5aa9ca69dcd4db1cabe61cd /binutils/MAINTAINERS | |
| parent | 00dbadd9691a1615c4a9789021751ad1da29b752 (diff) | |
| download | binutils-redhat-7ba25ce72c420a69f16b414b805bd6c497cbcaac.tar.gz | |
Add obvious fix rule
Diffstat (limited to 'binutils/MAINTAINERS')
| -rw-r--r-- | binutils/MAINTAINERS | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS index 427dd3acdf..ec66a38e41 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. |