From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [4/5] implement "info vtable"
Date: Wed, 29 Feb 2012 18:20:00 -0000 [thread overview]
Message-ID: <83linlcxwk.fsf@gnu.org> (raw)
In-Reply-To: <87mx82prmd.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: Tue, 28 Feb 2012 14:36:42 -0700
>
> This one needs a doc review, and of course commentary on the naming and
> output.
The documentation parts are fine, thanks.
next prev parent reply other threads:[~2012-02-29 18:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 21:48 Tom Tromey
2012-02-29 18:20 ` Eli Zaretskii [this message]
2012-03-01 14:52 ` Pedro Alves
2012-03-01 17:36 ` Tom Tromey
2012-03-01 20:18 ` Pedro Alves
2012-03-15 15:43 ` Tom Tromey
2012-03-16 8:10 ` Crash regression [Re: [4/5] implement "info vtable"] Jan Kratochvil
2012-03-19 18:13 ` Tom Tromey
2012-07-19 9:34 ` [4/5] implement "info vtable" Andreas Schwab
2012-07-19 17:01 ` Tom Tromey
2012-07-20 8:33 ` Andreas Schwab
2012-07-20 14:24 ` Tom Tromey
2012-07-20 14:29 ` Andreas Schwab
2012-07-20 16:23 ` Tom Tromey
2012-07-20 17:34 ` Andreas Schwab
2012-07-20 17:48 ` Tom Tromey
2012-07-20 18:08 ` 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=83linlcxwk.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