From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: pushed: [RFA/commit+doco] GDB/MI: Document support for -exec-run --start in -list-features
Date: Sat, 28 Dec 2013 03:10:00 -0000 [thread overview]
Message-ID: <20131228030957.GA4532@adacore.com> (raw)
In-Reply-To: <837gav8s79.fsf@gnu.org>
> > > > gdb/doc/ChangeLog:
> > > >
> > > > * gdb.texinfo (GDB/MI Support Commands): Add @findex entries
> > > > for each @item in the table describing the list of features.
> > > > Add empty line between each @item.
> > > >
> > > > OK to commit?
> > >
> > > It is OK, but the same effect for a much smaller effort would be
> > > achieved by replacing @table with @ftable. Thgen each @item
> > > automatically gets inserted into the function index.
> >
> > I didn't know that, thanks! Here is a new patch...
>
> Obviously correct, thanks.
Thank you, Eli. The patch has been pushed!
--
Joel
next prev parent reply other threads:[~2013-12-28 3:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 6:21 Joel Brobecker
2013-12-03 7:22 ` Eli Zaretskii
2013-12-03 10:18 ` Joel Brobecker
2013-12-10 12:03 ` Joel Brobecker
2013-12-10 17:39 ` Eli Zaretskii
2013-12-12 16:02 ` pushed: Add @cindex for section documenting the -list-features GDB/MI command. (was: "[RFA/commit+doco] GDB/MI: Document support for -exec-run --start in -list-features") Joel Brobecker
2013-12-12 16:35 ` Eli Zaretskii
2013-12-13 6:10 ` [RFA/commit+doco] GDB/MI: Document support for -exec-run --start in -list-features Joel Brobecker
2013-12-13 15:51 ` Joel Brobecker
2013-12-13 19:36 ` Eli Zaretskii
2013-12-23 1:01 ` Joel Brobecker
2013-12-23 1:40 ` Joel Brobecker
2013-12-23 3:49 ` Eli Zaretskii
2013-12-23 4:28 ` Joel Brobecker
2013-12-23 16:10 ` Eli Zaretskii
2013-12-28 3:10 ` Joel Brobecker [this message]
2013-12-10 11:14 ` pushed: " Joel Brobecker
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=20131228030957.GA4532@adacore.com \
--to=brobecker@adacore.com \
--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