From: Joseph Myers <joseph@codesourcery.com>
To: DJ Delorie <dj@redhat.com>
Cc: Oleh Derevenko <oleh.derevenko@gmail.com>,
<adhemerval.zanella@linaro.org>, <libc-alpha@sourceware.org>
Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread
Date: Tue, 19 Jun 2018 19:26:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1806191918310.20075@digraph.polyomino.org.uk> (raw)
In-Reply-To: <xny3falozi.fsf@greed.delorie.com>
On Tue, 19 Jun 2018, DJ Delorie wrote:
> So we ask for patent licenses and copyright assignments. Because of our
And specifically, what I think is the current assignment
(/gd/gnuorg/copyright/assign.future on fencepost) says:
6. Developer hereby agrees that if he has or acquires hereafter any
proprietary interest (including, without limitation, any patent or
copyright interest) dominating the Works, the Program, the Program as
enhanced by the Works, or other enhancements to the Program, or the
use of any of those, such dominating interest will not be used to
undermine the effect of this assignment, i.e. the Foundation and the
general public will be licensed to use, in that program or programs
and their derivative works, without royalty or limitation, the subject
matter of the dominating interest. This license provision will be
binding on the assignees of, or other successors to, the dominating
interest, as well as on Developer. This license grant is
nonexclusive, royalty-free and non-cancellable.
Note that users of glibc may use glibc facilities in proprietary programs
if they follow the provisions of the LGPL (typically through dynamically
linking to glibc).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-06-19 19:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 23:35 Oleh Derevenko
2018-04-02 23:07 ` Oleh Derevenko
2018-04-03 13:41 ` Ben Hutchings
2018-04-03 20:06 ` Oleh Derevenko
[not found] ` <CAC1wWD0OwFLqUD2uXnavBzfEw=HCRn3fGW54zYfxRozxp8HsyA@mail.gmail.com>
2018-06-15 14:05 ` Oleh Derevenko
2018-06-15 14:31 ` Florian Weimer
2018-06-16 18:37 ` Oleh Derevenko
2018-06-18 13:22 ` Adhemerval Zanella
2018-06-18 19:52 ` Oleh Derevenko
2018-06-18 21:03 ` Adhemerval Zanella
2018-06-18 21:06 ` DJ Delorie
2018-06-18 22:26 ` Oleh Derevenko
2018-06-19 12:07 ` Adhemerval Zanella
2018-06-19 12:42 ` Oleh Derevenko
2018-06-19 13:09 ` Adhemerval Zanella
2018-06-19 15:36 ` Patrick McGehearty
2018-06-19 16:28 ` DJ Delorie
2018-06-19 16:52 ` Zack Weinberg
2018-06-19 19:26 ` Joseph Myers [this message]
2018-06-19 19:55 ` DJ Delorie
2018-06-19 22:39 ` Oleh Derevenko
2018-06-20 13:14 ` Carlos O'Donell
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=alpine.DEB.2.20.1806191918310.20075@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=oleh.derevenko@gmail.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).