Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: simark@simark.ca, gdb-patches@sourceware.org
Subject: Re: [PATCH 7/7] Allow setting a parameter to raise gdb.GdbError
Date: Mon, 24 Sep 2018 12:39:00 -0000	[thread overview]
Message-ID: <83efdjax2m.fsf@gnu.org> (raw)
In-Reply-To: <8736tzp514.fsf@tromey.com> (message from Tom Tromey on Mon, 24	Sep 2018 04:24:07 -0600)

> From: Tom Tromey <tom@tromey.com>
> Cc: Simon Marchi <simark@simark.ca>,  tom@tromey.com,  gdb-patches@sourceware.org
> Date: Mon, 24 Sep 2018 04:24:07 -0600
> 
> FWIW I made the requested change before pushing:

Thanks.

> >> >> +If this method raises @code{gdb.GdbError} (@pxref{Exception
> 
> >> > "raises the 'gdb.GdbError' exception", I presume?
> 
> However I wonder if it should read "a" rather the "the".

My gut feeling is "the", but your English is more native than mine, so
I'll defer to your opinion.


      reply	other threads:[~2018-09-24 12:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-15  7:25 [PATCH 0/7] some small python fixes (one including a doc patch) Tom Tromey
2018-09-15  7:25 ` [PATCH 5/7] Check for negative argument in Type.template_argument Tom Tromey
2018-09-15  7:25 ` [PATCH 6/7] Consolidate gdb.GdbError handling Tom Tromey
2018-09-15  7:25 ` [PATCH 3/7] Allow conversion of pointers to Python int Tom Tromey
2018-09-15  7:25 ` [PATCH 4/7] Report Python errors coming from gdb.post_event Tom Tromey
2018-09-15  7:25 ` [PATCH 2/7] Preserve sign when converting gdb.Value to Python int Tom Tromey
2018-09-15  7:25 ` [PATCH 1/7] Allow more Python scalar conversions Tom Tromey
2018-09-24  2:06   ` Simon Marchi
2018-09-24  4:58     ` Tom Tromey
2018-09-15  7:25 ` [PATCH 7/7] Allow setting a parameter to raise gdb.GdbError Tom Tromey
2018-09-15  9:16   ` Eli Zaretskii
2018-09-24  2:39     ` Simon Marchi
2018-09-24  4:58       ` Tom Tromey
2018-09-24  5:14         ` Tom Tromey
2018-09-24  7:10       ` Eli Zaretskii
2018-09-24 10:24         ` Tom Tromey
2018-09-24 12:39           ` Eli Zaretskii [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=83efdjax2m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --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