From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Should we fix warnings from GCC 2.xx?
Date: Thu, 12 Sep 2002 11:50:00 -0000 [thread overview]
Message-ID: <20020912185054.GA1105@gnat.com> (raw)
In-Reply-To: <3D80B892.4050203@ges.redhat.com>
> Regardless, I don't see how it can hurt. Removes the dangling `else'
> problem.
Ok, thanks for the clarification. I will check-in this patch shortly
and send the associated [PATCH] email as a confirmation. There is also
the exact same error in exec.c that I will fix.
--
Joel
next prev parent reply other threads:[~2002-09-12 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 16:43 Joel Brobecker
2002-09-12 8:53 ` Andrew Cagney
2002-09-12 11:50 ` Joel Brobecker [this message]
2002-09-19 4:12 ` Eli Zaretskii
2002-09-19 4:31 ` Andreas Schwab
2002-09-19 4:49 ` Eli Zaretskii
2002-09-19 5:03 ` Andreas Schwab
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=20020912185054.GA1105@gnat.com \
--to=brobecker@gnat.com \
--cc=ac131313@ges.redhat.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