From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/3] python: Add Inferior.progspace property
Date: Thu, 13 Sep 2018 14:20:00 -0000 [thread overview]
Message-ID: <834letlbsa.fsf@gnu.org> (raw)
In-Reply-To: <e90e05f13adc7a86c71b673e084aa115@polymtl.ca> (message from Simon Marchi on Thu, 13 Sep 2018 09:50:32 -0400)
> Date: Thu, 13 Sep 2018 09:50:32 -0400
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
>
> > This brace should be deleted.
>
> The brace belongs there (it is the end of the @code), if I remove it I
> get a makeinfo error.
Sorry, you are right. That was a long day.
next prev parent reply other threads:[~2018-09-13 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 2:36 Simon Marchi
2018-09-13 2:37 ` [PATCH v2 3/3] python: Fix erroneous doc about gdb.objfiles() Simon Marchi
2018-09-13 13:49 ` Eli Zaretskii
2018-09-13 2:37 ` [PATCH v2 2/3] python: Add Progspace.objfiles method Simon Marchi
2018-09-13 13:49 ` Eli Zaretskii
2018-09-13 13:46 ` [PATCH v2 1/3] python: Add Inferior.progspace property Eli Zaretskii
2018-09-13 13:50 ` Simon Marchi
2018-09-13 14:20 ` Eli Zaretskii [this message]
2018-09-13 19:45 ` Simon Marchi
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=834letlbsa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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