From: Eli Zaretskii <eliz@gnu.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch][doc] Fix PR python/15613 (make gdb.GdbError formatting consistent with other exceptions
Date: Wed, 18 Sep 2013 20:37:00 -0000 [thread overview]
Message-ID: <83r4cln9x3.fsf@gnu.org> (raw)
In-Reply-To: <523A06E2.1010602@redhat.com>
> Date: Wed, 18 Sep 2013 21:02:42 +0100
> From: Phil Muldoon <pmuldoon@redhat.com>
>
> This patch addresses PR 15613. This makes the formatting of
> gdb.GdbError more consistent with other exception types documented.
>
> OK?
OK for the documentation part.
Thanks.
prev parent reply other threads:[~2013-09-18 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 20:02 Phil Muldoon
2013-09-18 20:37 ` 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=83r4cln9x3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.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