From: Tom Tromey <tromey@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [MI tracepoints 9/9] documentation
Date: Wed, 24 Mar 2010 21:32:00 -0000 [thread overview]
Message-ID: <m3r5n9h0di.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201003161656.07287.vladimir@codesourcery.com> (Vladimir Prus's message of "Tue, 16 Mar 2010 16:56:07 +0300")
>>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
Volodya> Thanks for review -- I have applied other comments pretty much as
Volodya> written. Here's the revised patch that I plan to commit after the
Volodya> code patches are in.
Volodya> @item frame
Volodya> The information about the frame corresponding to the found trace
Volodya> -frame. This field is present only if a trace frame was found.
Volodya> -See @xref{GDB/MI Frame Information} for description of this field.
Volodya> +frame. This field is present only if a trace frame was found.
Volodya> +@xref{GDB/MI Frame Information} for description of this field.
This introduced a warning from makeinfo:
makeinfo -I ../../../src/gdb/doc/../../readline/doc -I ../../../src/gdb/doc/../mi -I ../../../src/gdb/doc \
-o gdb.info ../../../src/gdb/doc/gdb.texinfo
../../../src/gdb/doc/gdb.texinfo:26053: warning: `.' or `,' must follow @xref, not `f'.
Tom
next prev parent reply other threads:[~2010-03-24 21:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 9:04 Vladimir Prus
2010-03-14 18:25 ` Eli Zaretskii
2010-03-16 13:56 ` Vladimir Prus
2010-03-24 21:32 ` Tom Tromey [this message]
2010-03-24 21:41 ` Vladimir Prus
2010-03-24 21:43 ` Tom Tromey
2010-03-25 4:06 ` Eli Zaretskii
2010-03-25 17:30 ` Vladimir Prus
2010-03-25 17:36 ` Vladimir Prus
2010-03-25 18:12 ` Stan Shebs
2010-03-25 19:33 ` Eli Zaretskii
2010-03-26 8:08 ` Vladimir Prus
2010-03-26 8:50 ` Eli Zaretskii
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=m3r5n9h0di.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).