From: Conrad Meyer <cem@freebsd.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [OB PATCH] Improve remote attach round-trips without btrace
Date: Tue, 20 Aug 2019 16:17:00 -0000 [thread overview]
Message-ID: <CAG6CVpUHqZw_xPWHOt9ZcMnGYG=z2DNJG+7ZaPOntE10vK5gDg@mail.gmail.com> (raw)
In-Reply-To: <2f92062b-68a7-ecd6-1218-33784bb364eb@redhat.com>
On Tue, Aug 20, 2019 at 7:28 AM Pedro Alves <palves@redhat.com> wrote:
>
> On 8/19/19 8:18 PM, Conrad Meyer wrote:
>
> > Please find the 'git format-patch' formatted patch attached to this
> > email, and please let me know if you have any follow-up questions. I
> > have already sent a copyright disclaimer form email for this change to
> > assign@gnu.
>
> Thanks, this looks good.
>
> I don't see your assignment/disclaimer in fencepost yet, but given that
> change is small, that should not be a problem, so I went ahead and
> merged it.
Thanks, Pedro!
Best,
Conrad
prev parent reply other threads:[~2019-08-20 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 19:18 Conrad Meyer
2019-08-20 14:28 ` Pedro Alves
2019-08-20 16:17 ` Conrad Meyer [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='CAG6CVpUHqZw_xPWHOt9ZcMnGYG=z2DNJG+7ZaPOntE10vK5gDg@mail.gmail.com' \
--to=cem@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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