From: Andrew Cagney <ac131313@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [maint] [patch] clarify ``obvious fix'' a little
Date: Wed, 14 Nov 2001 10:37:00 -0000 [thread overview]
Message-ID: <3C034334.8030403@cygnus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 205 bytes --]
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
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1375 bytes --]
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:
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <ac131313@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [maint] [patch] clarify ``obvious fix'' a little
Date: Mon, 26 Nov 2001 23:39:00 -0000 [thread overview]
Message-ID: <3C034334.8030403@cygnus.com> (raw)
Message-ID: <20011126233900.7EmBSNEINkrXpS0-8V5sDasPy4j5Je-NWupVD2yveus@z> (raw)
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
From eliz@is.elta.co.il Mon Nov 26 23:40:00 2001
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: 5.1 -> 5.1.0_0000-00-00-cvs
Date: Mon, 26 Nov 2001 23:40:00 -0000
Message-id: <Pine.SUN.3.91.1011127093950.20335I-100000@is>
References: <3C033756.8050605@cygnus.com>
X-SW-Source: 2001-11/msg00489.html
Content-length: 192
On Tue, 27 Nov 2001, Andrew Cagney wrote:
> I've bumped the 5.1 branch version.in again. This will (hopefully) kick
> start the branches snapshot process.
Are we going to release v5.1.1?
next reply other threads:[~2001-11-27 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 10:37 Andrew Cagney [this message]
2001-11-26 23:39 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C034334.8030403@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox