From: Pedro Alves <pedro@palves.net>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: document MI -remove-inferior command
Date: Wed, 15 Feb 2023 15:33:03 +0000 [thread overview]
Message-ID: <d4a54b6b-d61e-b932-925d-c9760c4b4dc1@palves.net> (raw)
In-Reply-To: <49a2305e22e03e195dd157421cd97e0aaf9c3d37.1676461926.git.aburgess@redhat.com>
Hi!
On 2023-02-15 11:52 a.m., Andrew Burgess via Gdb-patches wrote:
>
> +@subheading The @code{-remove-inferior} Command
> +@findex -remove-inferior
Sorry for the extra trouble, but please put the @findex before the @subheading, as per:
https://inbox.sourceware.org/gdb-patches/83zg9hec14.fsf@gnu.org/T/#m9adb943b330c10be31774a0009767b0236cbd1f9
Pedro Alves
next prev parent reply other threads:[~2023-02-15 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 11:52 Andrew Burgess
2023-02-15 13:55 ` Eli Zaretskii
2023-02-15 15:33 ` Pedro Alves [this message]
2023-02-16 8:44 ` Andrew Burgess
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=d4a54b6b-d61e-b932-925d-c9760c4b4dc1@palves.net \
--to=pedro@palves.net \
--cc=aburgess@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).