From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: George Burgess IV <george.burgess.iv@gmail.com>,
libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH] Refactoring FORTIFY
Date: Thu, 05 Oct 2017 20:06:00 -0000 [thread overview]
Message-ID: <1B58D4F8-1CE9-4621-A6B7-DC95D1EF284F@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1710051541510.25551@digraph.polyomino.org.uk>
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-10-05 20:06 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 [this message]
2017-11-06 19:12 ` George Burgess IV
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=1B58D4F8-1CE9-4621-A6B7-DC95D1EF284F@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=george.burgess.iv@gmail.com \
--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).