From: Pedro Alves <palves@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH, testsuite] Add cc-with-dwz.exp add cc-with-dwz-m.exp
Date: Thu, 11 Apr 2019 15:59:00 -0000 [thread overview]
Message-ID: <a4fe24dd-c45c-7963-38c9-b604e50820ba@redhat.com> (raw)
In-Reply-To: <7f934a85-e7c0-a8e5-7107-485a72bc891d@suse.de>
On 4/11/19 10:35 AM, Tom de Vries wrote:
> On 10-04-19 14:11, Pedro Alves wrote:
>> Sorry for being dense, but I was completely confused by this
>> description for a bit.
> No problem, my bad, it's one of those things were I spent some time
> investigating what's going whilst not having a clue, and after I find
> out what's wrong it seems so obvious I fail to mention it in the
> submission...
Yeah, an easy trap to fall into. We have a note about that in the
contribution checklist. :-)
> Updated patch OK for trunk?
Yes. The new description looks beautifully clear, thanks!
Thanks,
Pedro Alves
prev parent reply other threads:[~2019-04-11 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 9:40 Tom de Vries
[not found] ` <e4e152bc-75c8-4c6b-7620-8add873d0ff1@redhat.com>
[not found] ` <7f934a85-e7c0-a8e5-7107-485a72bc891d@suse.de>
2019-04-11 15:59 ` Pedro Alves [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=a4fe24dd-c45c-7963-38c9-b604e50820ba@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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