This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[maint] [patch] clarify ``obvious fix'' a little
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Tue, 27 Nov 2001 02:39:32 -0500
- Subject: [maint] [patch] clarify ``obvious fix'' a little
Hello,
Eli pointed out that part of the obvious fix rule was somewhat confusing
and suggested the the following. I'm going to er, check it in as
obvious (in a few days if no one complains :-).
Andrew
2001-11-27 Andrew Cagney <ac131313@redhat.com>
* MAINTAINERS: Clarify obvious fix a little
(suggesed by Eli Zaretskii).
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.123
diff -p -r1.123 MAINTAINERS
*** MAINTAINERS 2001/11/16 18:29:27 1.123
--- MAINTAINERS 2001/11/27 07:34:13
*************** All maintainers listed in this file are
*** 33,44 ****
fixes.
An "obvious fix" means that there is no possibility that anyone will
! disagree with the change. Something like bypassing an interface will
! result in instantaneous and loud complaints.
A good mental test is "will the person who hates my work the most be
able to find fault with the change" - if so, then it's not obvious and
needs to be posted first. :-)
Target/Architecture:
--- 33,47 ----
fixes.
An "obvious fix" means that there is no possibility that anyone will
! disagree with the change.
A good mental test is "will the person who hates my work the most be
able to find fault with the change" - if so, then it's not obvious and
needs to be posted first. :-)
+
+ Something like changing or bypassing an interface is _not_ an obvious
+ fix, since such a change without discussion will result in
+ instantaneous and loud complaints.
Target/Architecture: