From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix compilation failure in parse_escape
Date: Wed, 15 Apr 2009 20:42:00 -0000 [thread overview]
Message-ID: <83eivtlkdg.fsf@gnu.org> (raw)
In-Reply-To: <m3ocuxg201.fsf@fleche.redhat.com>
> Cc: gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Wed, 15 Apr 2009 13:17:50 -0600
>
> Eli> 2009-04-15 Eli Zaretskii <eliz@gnu.org>
> Eli> * utils.c (parse_escape): Initialize target_char to pacify GCC.
>
> Any value (not just -2) is ok here because it will always be overwritten.
> Add a comment explaining that the initialization is to avoid a
> warning -- we do this in other places. Ok with that.
Committed, thanks.
prev parent reply other threads:[~2009-04-15 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 18:48 Eli Zaretskii
2009-04-15 19:18 ` Tom Tromey
2009-04-15 20:42 ` Eli Zaretskii [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=83eivtlkdg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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