From: cgd@broadcom.com
To: "Andrew Cagney" <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [MIPS sim PATCH] Remove SIGNEXTEND.
Date: Tue, 05 Mar 2002 11:21:00 -0000 [thread overview]
Message-ID: <yov5sn7estvm.fsf@broadcom.com> (raw)
In-Reply-To: "Andrew Cagney"'s message of "Tue, 05 Mar 2002 14:18:34 -0500"
At Tue, 05 Mar 2002 14:18:34 -0500, Andrew Cagney wrote:
> Even if it is technically a problem for me, that isn't a reason to not
> pull the macro. I don't think it is reasonable for me to hold up a
> cleanup like this because it breaks some un-released code.
My thought was something more like:
If you've got code that needs it, there's probably a chance that that
code would be pushed back eventually... and so why delete it only to
add it back N months from now.
(Looking at some of my changes it might be hard to believe, but i
prefer to avoid tweaking code back and forth. 8-)
> Yes feel free to commit it.
OK, thanks.
chris
prev parent reply other threads:[~2002-03-05 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 11:09 cgd
2002-03-05 11:18 ` Andrew Cagney
2002-03-05 11:21 ` cgd [this message]
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=yov5sn7estvm.fsf@broadcom.com \
--to=cgd@broadcom.com \
--cc=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