This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Copyright header for changes to imported code (Re: [PATCH v4] Makebindresvport() function to multithread-safe)
- From: Pedro Alves <palves at redhat dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Cc: "Carlos O'Donell" <carlos at systemhalted dot org>, Roland McGrath <roland at hack dot frob dot com>, Peng Haitao <penght at cn dot fujitsu dot com>, Andreas Jaeger <aj at suse dot com>, Paul Eggert <eggert at cs dot ucla dot edu>
- Date: Thu, 22 Nov 2012 16:22:50 +0000
- Subject: Copyright header for changes to imported code (Re: [PATCH v4] Makebindresvport() function to multithread-safe)
- References: <1348823725-18793-1-git-send-email-penght@cn.fujitsu.com> <CAE2sS1hJLkePJXMw8wCXQ48einUnvjPSbjX11LMzCVvT3i3zZg@mail.gmail.com> <20120928162304.53D062C0C5@topped-with-meat.com> <5065D265.7050909@redhat.com> <20120928164226.0A4AE2C0BF@topped-with-meat.com> <5065DAC5.1000504@redhat.com> <5065E053.4050201@systemhalted.org>
Hi there,
On 9/28/2012 1:13 PM, Pedro Alves wrote:
> I've had this doubt before, so I sent the question towards the FSF
> copyright clerk.
I got a response back from the FSF (gnu.org #773481):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hi Pedro,
1) It is certainly the case that you should add a copyright line for the
FSF when nontrivial changes are made. This is what reflects reality,
and it has always been the stated practice to follow, though I gather
libc did not bother to do so. It is explicitly discussed at the end of
the Copyright Notices section you cited,
http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Pedro Alves