Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>, eliz@gnu.org
Cc: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [PR cli/17290] doc: Fix show remote interrupt-*.
Date: Wed, 17 Feb 2021 23:23:26 +0000	[thread overview]
Message-ID: <YC2lbpMznhICAFzS@Plymouth> (raw)
In-Reply-To: <87v9aq60k9.fsf@tromey.com>

Le Wed, Feb 17, 2021 at 10:55:50AM -0700, Tom Tromey a écrit :
> >>>>> "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

I just pushed the following patch.

Lancelot.

---

commit 22e6d16f9b9caff5b4bbb27727441c21480af9ad
Author: Lancelot SIX <lsix@lancelotsix.com>
Date:   Sat Feb 13 23:38:28 2021 +0000

    [PR cli/17290] gdb/doc: Fix show remote interrupt-*.
    
    Add the missing 'remote' in:
      - @item show remote interrupt-sequence
      - @item show remote interrupt-on-connect

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index bc5a2ea0d93..7f324dedade 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,9 @@
+2021-02-17  Lancelot Six  <lsix@lancelotsix.com>
+
+	PR cli/17290
+	* gdb.texinfo (Remote Configuration): Fix show remote
+	interrupt-sequence and show remote interrupt-on-connect.
+
 2021-02-11  Andrew Burgess  <andrew.burgess@embecosm.com>
 
 	* gdb.texinfo (Files): Update documentation for 'maint info
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 0b1deba9667..90f0c7683f6 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -22905,7 +22905,7 @@ is high level of serial line for some certain time.
 Linux kernel prefers @samp{BREAK-g}, a.k.a Magic SysRq g.
 It is @code{BREAK} signal followed by character @code{g}.
 
-@item show interrupt-sequence
+@item show remote interrupt-sequence
 Show which of @samp{Ctrl-C}, @code{BREAK} or @code{BREAK-g}
 is sent by @value{GDBN} to interrupt the remote program.
 @code{BREAK-g} is BREAK signal followed by @code{g} and
@@ -22918,7 +22918,7 @@ Specify whether interrupt-sequence is sent to remote target when
 Linux kernel.  Linux kernel expects @code{BREAK} followed by @code{g}
 which is known as Magic SysRq g in order to connect @value{GDBN}.
 
-@item show interrupt-on-connect
+@item show remote interrupt-on-connect
 Show whether interrupt-sequence is sent
 to remote target when @value{GDBN} connects to it.
 


      parent reply	other threads:[~2021-02-17 23:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14  9:21 [PATCH] [PR cli/1729] doc: Fix show remote interrupt-sequence Lancelot SIX via Gdb-patches
2021-02-17 17:55 ` Tom Tromey
2021-02-17 19:28   ` Eli Zaretskii via Gdb-patches
2021-02-17 23:23   ` Lancelot SIX via Gdb-patches [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=YC2lbpMznhICAFzS@Plymouth \
    --to=gdb-patches@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=lsix@lancelotsix.com \
    --cc=tom@tromey.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