From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Use -Wall -Wextra
Date: Thu, 04 Jan 2007 04:09:00 -0000 [thread overview]
Message-ID: <usler1lhp.fsf@gnu.org> (raw)
In-Reply-To: <20070103191225.GH17935@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 3 Jan 2007 14:12:25 -0500)
> Date: Wed, 3 Jan 2007 14:12:25 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> Here's what I have just tested on x86_64-pc-linux-gnu. This is a much
> more conservative patch than my previous one. It may still break other
> targets, especially native ones, with -Werror; I'll be happy to help
> fix any breakage if the fixes aren't apparent.
>
> OK to commit?
Yes, thanks.
next prev parent reply other threads:[~2007-01-04 4:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 19:55 Daniel Jacobowitz
2006-12-29 12:13 ` Eli Zaretskii
2006-12-29 13:58 ` Daniel Jacobowitz
2006-12-29 20:44 ` Eli Zaretskii
2006-12-29 21:02 ` Daniel Jacobowitz
2006-12-30 15:32 ` Eli Zaretskii
2006-12-30 16:00 ` Daniel Jacobowitz
2006-12-30 16:55 ` Eli Zaretskii
2007-01-03 19:12 ` Daniel Jacobowitz
2007-01-03 20:38 ` Mark Kettenis
2007-01-04 4:09 ` Eli Zaretskii [this message]
2007-01-04 19:42 ` Daniel Jacobowitz
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=usler1lhp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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