From: Phil Muldoon <pmuldoon@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [commit/doco] Fix unmatched @end table in gdb.texinfo.
Date: Tue, 29 Jun 2010 20:04:00 -0000 [thread overview]
Message-ID: <4C2A519F.4010805@redhat.com> (raw)
In-Reply-To: <83d3v9bv1p.fsf@gnu.org>
On 29/06/10 18:36, Eli Zaretskii wrote:
>> From: Joel Brobecker <brobecker@adacore.com>
>> Cc: pmuldoon@redhat.com, Joel Brobecker <brobecker@adacore.com>
>> Date: Mon, 28 Jun 2010 21:35:49 -0700
>>
>> --- a/gdb/doc/gdb.texinfo
>> +++ b/gdb/doc/gdb.texinfo
>> @@ -21118,6 +21118,7 @@ does not use that identifier.
>>
>> A @code{gdb.InferiorThread} object has the following methods:
>>
>> +@table @code
>> @defmethod InferiorThread switch
>> This changes @value{GDBN}'s currently selected thread to the one represented
>> by this object.
>
> Yes, this is the right fix. Thanks.
Apologies. I pruned the thread.newest_thread documentation one line too much
I'm not sure how I missed the make info results there.
Cheers,
Phil
prev parent reply other threads:[~2010-06-29 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 4:36 Joel Brobecker
2010-06-29 17:36 ` Eli Zaretskii
2010-06-29 20:04 ` Phil Muldoon [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=4C2A519F.4010805@redhat.com \
--to=pmuldoon@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.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