From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Andrew Burgess <andrew.burgess@embecosm.com>,
Joel Brobecker <brobecker@adacore.com>,
Tom Tromey <tom@tromey.com>, Pedro Alves <palves@redhat.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v5] Fix range end handling of inlined subroutines
Date: Wed, 30 Dec 2020 17:56:05 -0500 [thread overview]
Message-ID: <a699cd59-618c-bf28-ea84-f02961deb7d9@polymtl.ca> (raw)
In-Reply-To: <AM0PR0602MB341079D0BBC6E1AFF64C4EB2E4D70@AM0PR0602MB3410.eurprd06.prod.outlook.com>
On 2020-12-30 2:54 p.m., Bernd Edlinger wrote:
> Yes. I can do that.
>
> I quickly extracted that one line change as follows.
>
> Is it ok to push?
Yes, please push.
Simon
next prev parent reply other threads:[~2020-12-30 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 9:10 Bernd Edlinger
2020-12-30 17:17 ` Simon Marchi via Gdb-patches
2020-12-30 19:54 ` Bernd Edlinger
2020-12-30 22:56 ` Simon Marchi via Gdb-patches [this message]
2020-12-30 18:48 ` Simon Marchi via Gdb-patches
2020-12-30 20:49 ` Bernd Edlinger
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=a699cd59-618c-bf28-ea84-f02961deb7d9@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=andrew.burgess@embecosm.com \
--cc=bernd.edlinger@hotmail.de \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.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