public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: reword a sentence
Date: Mon, 10 May 2021 10:11:24 +0100	[thread overview]
Message-ID: <20210510091124.GP6612@embecosm.com> (raw)
In-Reply-To: <83v97r7sqc.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2021-05-09 19:54:35 +0300]:

> > From: Andrew Burgess <andrew.burgess@embecosm.com>
> > Date: Sun,  9 May 2021 17:29:18 +0100
> > 
> > gdb/doc/ChangeLog:
> > 
> > 	* python.texinfo (Breakpoints In Python): Reword sentence.
> > ---
> >  gdb/doc/ChangeLog   | 4 ++++
> >  gdb/doc/python.texi | 2 +-
> >  2 files changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
> > index 453ddfec03f..4865634537d 100644
> > --- a/gdb/doc/python.texi
> > +++ b/gdb/doc/python.texi
> > @@ -5500,7 +5500,7 @@
> >  Hardware assisted access watchpoint.
> >  @end vtable
> >  
> > -The available watchpoint types represented by constants are defined in the
> > +The available watchpoint types are represented by constants defined in the
> >  @code{gdb} module:
> >  
> >  @vtable @code
> > -- 
> > 2.25.4
> 
> Thanks, this is OK.

Thanks for the review.  I realised the same mistake was present in the
guile.texi file too so I extended the patch to cover that file too.

Thanks,
Andrew

  reply	other threads:[~2021-05-10  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-09 16:29 Andrew Burgess
2021-05-09 16:54 ` Eli Zaretskii
2021-05-10  9:11   ` Andrew Burgess [this message]
2021-05-10 13:38     ` 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=20210510091124.GP6612@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=eliz@gnu.org \
    --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).