From: Ximin Luo <infinity0@pwned.gg>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2] Generate reproducible output independently of the build-path
Date: Wed, 03 May 2017 15:53:00 -0000 [thread overview]
Message-ID: <34c14f10-3318-3451-b7e4-59f27c35439d@pwned.gg> (raw)
In-Reply-To: <alpine.DEB.2.20.1704211725370.8453@digraph.polyomino.org.uk>
Joseph Myers:
> On Tue, 11 Apr 2017, Ximin Luo wrote:
>
>> Copyright disclaimer
>> ====================
>>
>> I dedicate these patches to the public domain by waiving all of my rights to
>> the work worldwide under copyright law, including all related and neighboring
>> rights, to the extent allowed by law.
>>
>> See https://creativecommons.org/publicdomain/zero/1.0/legalcode for full text.
>>
>> Please let me know if the above is insufficient and I will be happy to sign any
>> relevant forms.
>
> I believe the FSF wants its own disclaimer forms signed as evidence code
> is in the public domain. The process for getting disclaimer forms is to
> complete
> https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-disclaim.changes
> and then you should be sent a disclaimer form for disclaiming the
> particular set of changes you have completed (if you then make further
> significant changes afterwards, the disclaimer form would then need
> completing for them as well).
>
I've now done this, and the copyright clerk at the FSF has told me that this is complete on their side as well.
Did any of you get a chance to look at the patch yet?
X
--
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
next prev parent reply other threads:[~2017-05-03 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 11:35 Ximin Luo
2017-04-11 11:35 ` [PATCH 2/3] Use BUILD_PATH_PREFIX_MAP envvar to transform __FILE__ Ximin Luo
2017-04-11 11:35 ` [PATCH 3/3] When remapping paths, only match whole path components Ximin Luo
2017-04-11 11:35 ` [PATCH 1/3] Use BUILD_PATH_PREFIX_MAP envvar for debug-prefix-map Ximin Luo
2017-04-18 14:57 ` [PATCH v2] Generate reproducible output independently of the build-path Ximin Luo
2017-04-21 18:28 ` Joseph Myers
2017-05-03 15:53 ` Ximin Luo [this message]
2017-06-07 16:15 ` Ximin Luo
2017-06-29 10:46 ` [Ping ^3][PATCH " Ximin Luo
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=34c14f10-3318-3451-b7e4-59f27c35439d@pwned.gg \
--to=infinity0@pwned.gg \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).