From: Paul Eggert <eggert@cs.ucla.edu>
To: libc-alpha@sourceware.org
Subject: Re: Update to glibc copyright assignment policy
Date: Thu, 29 Jul 2021 12:02:37 -0700 [thread overview]
Message-ID: <1172b18f-8157-e6b8-ac6a-59cc31e63896@cs.ucla.edu> (raw)
In-Reply-To: <874kcd2ob4.fsf@oldenburg.str.redhat.com>
On 7/29/21 7:21 AM, Florian Weimer via Libc-alpha wrote:
> I'm worried that this obligation means that we cannot use glibc-specific
> facilities in code shared with gnulib.
We'll just have to take those problems as they come. I'm not
particularly worried about it. If it's an important facility that's
portable, we can simply rewrite it for Gnulib and then share back as needed.
The main obstacles for sharing will likely continue to be technical, not
political/legal.
prev parent reply other threads:[~2021-07-29 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 19:50 Update to glibc copyright assignment policy Carlos O'Donell via Libc-alpha
2021-07-29 10:25 ` Siddhesh Poyarekar
2021-07-29 13:58 ` Carlos O'Donell via Libc-alpha
2021-07-29 14:07 ` Siddhesh Poyarekar
2021-07-29 14:21 ` Florian Weimer via Libc-alpha
2021-07-29 19:02 ` Paul Eggert [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1172b18f-8157-e6b8-ac6a-59cc31e63896@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--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).