From: Alejandro Colomar <alx+linux-man@kernel.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Alejandro Colomar <alx@kernel.org>,
Xavier Leroy <Xavier.Leroy@inria.fr>,
linux-man <linux-man@vger.kernel.org>,
Michal Schorm <mschorm@redhat.com>
Subject: Re: Two copyright notices missing in 6.20?
Date: Fri, 20 Nov 2026 01:34:45 +0100 [thread overview]
Message-ID: <av-UBJhM_77OtKJA@devuan> (raw)
In-Reply-To: <e2835e4f-3cb4-4b39-9a1d-a6b222e8bbb4@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
Hi Carlos,
> Date: 2026-11-09 16:42:39-0500
> From: Carlos O'Donell <carlos@redhat.com>
>
> On 11/5/26 6:06 PM, Alejandro Colomar wrote:
> > Actually, I've looked at memcpy(3), and the text I thought might have
> > come from glibc is not present in the glibc manual, so I guess it's
> > from this project only. The text from glibc might have been replaced
> > entirely over time.
>
> Agreed.
>
> > Now we have a Ship of Theseus problem here. The page doesn't seem to
> > contain any copyrighted text, but are we allowed to just drop that
> > license notice? Any suggestions about memcpy(3)?
> I think at this point the interface is so well understood and the text
> sufficiently simple that we can keep memcpy.3 as-is for 6.20+.
>
> However, signbit.3 clearly says "Based on glibc infopages, copyright Free Software Foundation"
>
> Likewise "heavily based on glibc infopages, copyright Free Software Foundation"
>
> Both of these should be rewritten from scratch IMO if we're going to ship
> something that is legally permissible without being GFDL.
>
> I can't write these since I'm involved in reviewing artih.texi updates
> for glibc.
>
> I think anyone else could probably write them.
I've rewritten the pages.
Have a lovely night!
Alex
>
> --
> Cheers,
> Carlos.
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-11-20 0:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 16:24 Two copyright notices missing in 6.20? Carlos O'Donell
2026-11-02 23:13 ` Alejandro Colomar
2026-11-03 7:10 ` Michal Schorm
2026-11-03 11:57 ` Alejandro Colomar
2026-11-03 14:55 ` Carlos O'Donell
2026-11-03 15:28 ` Alejandro Colomar
2026-11-03 18:02 ` Carlos O'Donell
2026-11-03 18:52 ` GPL/GFDL incompatibility (was: Two copyright notices missing in 6.20?) G. Branden Robinson
2026-11-05 23:06 ` Two copyright notices missing in 6.20? Alejandro Colomar
2026-11-09 21:42 ` Carlos O'Donell
2026-11-20 0:34 ` Alejandro Colomar [this message]
2026-11-03 16:54 ` copyright year ranges and "collapse" (was: Two copyright notices missing in 6.20?) G. Branden Robinson
2026-11-03 17:55 ` copyright year ranges and "collapse" Carlos O'Donell
2026-11-03 18:39 ` G. Branden Robinson
2026-11-03 21:40 ` Carlos O'Donell
2026-11-12 20:48 ` G. Branden Robinson
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=av-UBJhM_77OtKJA@devuan \
--to=alx+linux-man@kernel.org \
--cc=Xavier.Leroy@inria.fr \
--cc=alx@kernel.org \
--cc=carlos@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=mschorm@redhat.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