From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: Ping: canonicalize type names on input / output
Date: Mon, 30 Mar 2009 21:16:00 -0000 [thread overview]
Message-ID: <u7i26lovb.fsf@gnu.org> (raw)
In-Reply-To: <m3vdpqlte5.fsf@fleche.redhat.com>
> Cc: gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 30 Mar 2009 13:09:38 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> >> http://sourceware.org/ml/gdb-patches/2007-10/msg00510.html
> >> I didn't see any response to the content of this patch.
>
> Eli> Hey, that's unfair! I did respond.
>
> What I meant by 'content' was the bulk of the patch.
> You replied concerning the NEWS entry.
That's what was in my responsibility, and that's what Daniel asked me
to do.
prev parent reply other threads:[~2009-03-30 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 18:59 Tom Tromey
2009-03-30 19:03 ` Daniel Jacobowitz
2009-03-30 21:25 ` Tom Tromey
2009-03-31 13:37 ` Eli Zaretskii
2009-03-31 20:32 ` Tom Tromey
2009-03-30 19:08 ` Eli Zaretskii
2009-03-30 19:15 ` Tom Tromey
2009-03-30 21:16 ` 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=u7i26lovb.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