From: Tom Tromey <tom@tromey.com>
To: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
Cc: Lancelot SIX <lsix@lancelotsix.com>
Subject: Re: [PATCH] [PR cli/1729] doc: Fix show remote interrupt-sequence.
Date: Wed, 17 Feb 2021 10:55:50 -0700 [thread overview]
Message-ID: <87v9aq60k9.fsf@tromey.com> (raw)
In-Reply-To: <20210214092108.12996-1-lsix@lancelotsix.com> (Lancelot SIX via Gdb-patches's message of "Sun, 14 Feb 2021 09:21:08 +0000")
>>>>> "Lancelot" == Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org> writes:
Lancelot> Add the missing 'remote' word.
Lancelot> gdb/doc/ChangeLog
Lancelot> PR cli/1729
Lancelot> * gdb.texinfo (Remote Configuration): Fix show remote
Lancelot> interrupt-sequence.
Thanks. This patch would qualify under the "obvious" rule.
I took a look and there's another related instance a bit further down:
@item show interrupt-on-connect
I wonder if you'd mind fixing this up as well before checking it in?
thanks,
Tom
next prev parent reply other threads:[~2021-02-17 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 9:21 Lancelot SIX via Gdb-patches
2021-02-17 17:55 ` Tom Tromey [this message]
2021-02-17 19:28 ` Eli Zaretskii via Gdb-patches
2021-02-17 23:23 ` [PATCH] [PR cli/17290] doc: Fix show remote interrupt-* Lancelot SIX via Gdb-patches
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=87v9aq60k9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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