From: Pedro Alves <palves@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc v3][5/6] Make "info proc" command generic
Date: Tue, 17 Jan 2012 20:10:00 -0000 [thread overview]
Message-ID: <4F15D564.1010602@redhat.com> (raw)
In-Reply-To: <201201171948.q0HJm3sS025563@d03av02.boulder.ibm.com>
Again, only a tiny nit.
On 01/17/2012 07:48 PM, Ulrich Weigand wrote:
> + /* Show information about process PTID. */
> + void (*to_info_proc) (struct target_ops *, char *, enum info_proc_what);
> +
> +/* Show information about process PTID. */
> +
> +void target_info_proc (char *, enum info_proc_what);
The comments should no longer refer to PTID, I think.
--
Pedro Alves
next prev parent reply other threads:[~2012-01-17 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 19:50 Ulrich Weigand
2012-01-17 20:10 ` Pedro Alves [this message]
2012-01-17 20:28 ` Ulrich Weigand
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=4F15D564.1010602@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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