From: Daniel Jacobowitz <drow@mvista.com>
To: fnf@intrinsity.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix several operator precedence bugs
Date: Thu, 06 Feb 2003 04:56:00 -0000 [thread overview]
Message-ID: <20030206045643.GA5543@nevyn.them.org> (raw)
In-Reply-To: <200302051716.h15HGANM001905@fred.ninemoons.com>
On Wed, Feb 05, 2003 at 10:16:10AM -0700, Fred Fish wrote:
> 2003-02-05 Fred Fish <fnf@intrinsity.com>
>
> * remote-e7000.c (e7000_drain_command): Fix precedence problem with
> '=' and '!='.
> * rdi-share/ardi.c (wait_for_debug_message): Fix precedence problem
> with '&' and '=='.
> (angel_RDI_info): Ditto.
> * infttrace.c (threads_continue_all_but_one): Fix precedence problem
> with '&' and '!='.
> (threads_continue_all_with_signals): Ditto.
Thanks. Fred, could you commit these obvious fixes (and update the
copyright years in the touched files)?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-02-06 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 17:16 Fred Fish
2003-02-06 4:56 ` Daniel Jacobowitz [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=20030206045643.GA5543@nevyn.them.org \
--to=drow@mvista.com \
--cc=fnf@intrinsity.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