This is the mail archive of the
mailing list for the glibc project.
Re: The direction of malloc?
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: Florian Weimer <fweimer at redhat dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, GNU C Library <libc-alpha at sourceware dot org>, Andreas Jaeger <aj at suse dot com>, Andreas Schwab <schwab at suse dot de>, OndÅej BÃlka <neleai at seznam dot cz>, Siddhesh Poyarekar <siddhesh at redhat dot com>, Pavel Simerda <psimerda at redhat dot com>
- Date: Mon, 16 Dec 2013 13:53:46 -0800 (PST)
- Subject: Re: The direction of malloc?
- Authentication-results: sourceware.org; auth=none
- References: <52A6A0DA dot 1080109 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1312101639060 dot 15324 at digraph dot polyomino dot org dot uk> <52AAE179 dot 9060802 at redhat dot com> <52AB9D04 dot 3020600 at redhat dot com>
> In the past did we just ask the FSF for permission to use the
> bind code? How hard was that process?
"The past" was a very long time ago and the process was not formalized at
all. It was simply decided and approved by RMS that UCB as a copyright
holder with the canonical BSD terms was a sufficiently known quantity that
we'd use their code without assignment or disclaimer. Later that was
extended to the ISC, DEC, and IBM copyrights in BIND code. The decision
about Sun's copyright on the sunrpc code was similar.
You can consult FSF legal folks if you want, but it's likely that the first
line of people answering those queries now don't understand the history and
the big exceptions to the usual assignment rules. You might need to
involve RMS to make sure it's clear, and there is no particular guarantee
that he will respond entirely consistently with his past decisions.
Frankly, I think any new code from the same projects (e.g. BIND) and the
same copyright holders with similarly permissive license terms is fine for
us to take without new legal consulation.