From: Pedro Alves <palves@redhat.com>
To: Yunlian Jiang <yunlian@google.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbserver: support Unix domain sockets
Date: Mon, 14 Mar 2016 15:02:00 -0000 [thread overview]
Message-ID: <56E6D291.805@redhat.com> (raw)
In-Reply-To: <56E1B066.2080509@redhat.com>
On 03/10/2016 05:35 PM, Pedro Alves wrote:
> This is larger than what we can accept without a copyright
> assignment with the FSF -- I looked at the records and
> couldn't find one. Let me know if you'd like to get that started.
Sorry, I notice now that I got confused here -- you're already covered
by Google's blanket copyright assignment.
Thanks,
Pedro Alves
prev parent reply other threads:[~2016-03-14 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 0:05 Yunlian Jiang
2016-03-10 17:35 ` Pedro Alves
2016-03-14 15:02 ` 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=56E6D291.805@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yunlian@google.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