From: Simon Marchi <simon.marchi@ericsson.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>, <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v2] Show line numbers in output for "info var/func/type"
Date: Thu, 05 Apr 2018 19:56:00 -0000 [thread overview]
Message-ID: <5c861488-b3d3-fa48-3a68-06b0ecb9ea41@ericsson.com> (raw)
In-Reply-To: <m3muyhlljl.fsf@oc1027705133.ibm.com>
On 2018-04-05 11:28 AM, Andreas Arnez wrote:
> Just for completeness, here's the updated version of the patch. Only
> the manual update has been added; nothing else has changed. The
> documentation parts have been reviewed by Eli.
>
> OK to push?
Hi Andreas,
It's a nice improvement, and the patch LGTM. I would like to leave time for other
people to comment too if they want. Please push it in a week from now if you haven't
heard anything else.
Thanks!
Simon
next prev parent reply other threads:[~2018-04-05 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 15:28 Andreas Arnez
2018-04-05 19:56 ` Simon Marchi [this message]
2018-04-13 17:28 ` [pushed] " Andreas Arnez
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=5c861488-b3d3-fa48-3a68-06b0ecb9ea41@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=arnez@linux.vnet.ibm.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