From: George Burgess IV <george.burgess.iv@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Joseph Myers <joseph@codesourcery.com>, libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH] Refactoring FORTIFY
Date: Mon, 06 Nov 2017 19:12:00 -0000 [thread overview]
Message-ID: <CAKh6zBEz4kE-WHbp3O8anezU8oBDLeUj1aZALHjix5LLAiHX-w@mail.gmail.com> (raw)
In-Reply-To: <1B58D4F8-1CE9-4621-A6B7-DC95D1EF284F@linaro.org>
Ping :)
> I think we are good regarding it
Glad to hear it!
On Thu, Oct 5, 2017 at 1:06 PM, Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
> Thanks for the follow up, I think we are good regarding it.
>
>> Il giorno 05 ott 2017, alle ore 12:48, Joseph Myers <joseph@codesourcery.com> ha scritto:
>>
>>> On Thu, 5 Oct 2017, Adhemerval Zanella wrote:
>>>
>>> I am not sure if Google has an assignment that cover submission of all
>>> its engineers. Also, I am not well versed in the requirements for the
>>> FSF copyright assignment, the only point I have is the GLIBC wiki entry [1].
>>>
>>> Joseph, is the wiki updated with latest guidelines and and does Google
>>> current CLA already cover George work?
>>
>> There is a Google assignment dated 2007-03-15 for all GNU projects.
>>
>> I presume that the Google-internal version of
>> https://opensource.google.com/docs/patching/ mentions the FSF assignment
>> and deals with any Google-specific contribution requirements.
>>
>> --
>> Joseph S. Myers
>> joseph@codesourcery.com
next prev parent reply other threads:[~2017-11-06 19:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 6:27 George Burgess IV
2017-10-02 20:12 ` George Burgess IV
2017-10-03 19:34 ` Adhemerval Zanella
2017-10-03 20:54 ` George Burgess IV
2017-10-05 13:43 ` Adhemerval Zanella
2017-10-05 15:48 ` Joseph Myers
2017-10-05 20:06 ` Adhemerval Zanella
2017-11-06 19:12 ` George Burgess IV [this message]
2017-11-20 20:03 ` Adhemerval Zanella
2017-12-05 4:53 ` George Burgess IV
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=CAKh6zBEz4kE-WHbp3O8anezU8oBDLeUj1aZALHjix5LLAiHX-w@mail.gmail.com \
--to=george.burgess.iv@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).