From: Vincent Lefevre <vincent@vinc17.net>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Alejandro Colomar <alx@kernel.org>,
"Andries E. Brouwer" <aeb@cwi.nl>,
linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
libc-alpha@sourceware.org
Subject: Re: man-pages-6.14 released
Date: Fri, 27 Jun 2025 02:20:11 +0200 [thread overview]
Message-ID: <20250627002011.GA431181@qaa.vinc17.org> (raw)
In-Reply-To: <42dad79f-e0f2-4731-ac14-0189f5d278a0@redhat.com>
On 2025-06-26 19:01:24 -0400, Carlos O'Donell wrote:
> On 6/26/25 5:04 PM, Alejandro Colomar wrote:
> > The thing is, as someone else mentioned, removals happen also implicitly
This was me, there:
https://lore.kernel.org/linux-man/u2ogua4573d2xm2p2oiuna67kydkr3e26pt6lixeidezdw34dg@nvn64na3cptt/T/#me71349fc15520d5c183311dfaf85667903c07d9d
> > by moving text from one page to another and not copying copyright
> > notices, so how much does it matter an intentional rewrite of the
> > copyright notices into a different form (but which keeps their
> > copyright, as part of the AUTHORS file), compared to an unintentional
> > removal of copyright by moving the text (these do actually remove
> > copyright, so these are the problematic ones).
>
> Both are legally mistakes.
Mistakes, yes (as long as copyright notices are per-file).
But legally? Why?
I've always heard that a copyright notice was optional and only
informative (so, in particular, there are no requirements to have
per-file copyright notices instead of a single one for the work).
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2025-06-27 0:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 23:15 Alejandro Colomar
2025-05-09 11:26 ` Andries E. Brouwer
2025-05-09 12:02 ` Alejandro Colomar
2025-05-09 12:14 ` Andries E. Brouwer
2025-05-09 12:28 ` Alejandro Colomar
2025-05-09 12:48 ` Vincent Lefevre
2025-05-09 12:57 ` Alejandro Colomar
2025-05-09 13:11 ` Vincent Lefevre
2025-06-26 20:41 ` Carlos O'Donell
2025-06-26 21:04 ` Alejandro Colomar
2025-06-26 23:01 ` Carlos O'Donell
2025-06-26 23:14 ` Alejandro Colomar
2025-06-27 0:08 ` Andries E. Brouwer
2025-06-27 0:45 ` Alejandro Colomar
2026-02-08 22:04 ` Alejandro Colomar
2025-06-27 0:20 ` Vincent Lefevre [this message]
2025-06-27 4:23 ` Alejandro Colomar
2025-06-27 7:49 ` Vincent Lefevre
2025-06-27 13:09 ` Alejandro Colomar
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=20250627002011.GA431181@qaa.vinc17.org \
--to=vincent@vinc17.net \
--cc=aeb@cwi.nl \
--cc=alx@kernel.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.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
all inboxes | Powered by JetHome®