public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andries E. Brouwer" <aeb@cwi.nl>
To: Alejandro Colomar <alx@kernel.org>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
	"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:08:11 +0200	[thread overview]
Message-ID: <20250627000811.GB1598947@if> (raw)
In-Reply-To: <u2ogua4573d2xm2p2oiuna67kydkr3e26pt6lixeidezdw34dg@nvn64na3cptt>

On Fri, Jun 27, 2025 at 01:14:46AM +0200, Alejandro Colomar wrote:

> On Thu, Jun 26, 2025 at 07:01:24PM -0400, Carlos O'Donell wrote:

> > you need permission from the authors.
> > 
> > I disagree that man-pages should go forward with the current changes.
> > 
> > May you please restore the copyright notices and cut a new release?
> 
> Hmmm, it'll take some time.  I need to stop and compare the both lists,
> which are rather long.  I don't promise it will happen soon, but I'll
> keep it in a TODO list.  I'll also try to do it at least after
> September, when I'll be meeting Michael in person, where I'll ask him
> about his copyright notices (which represent a huge percentage of the
> copyright notice lines).  That will reduce the work significantly.
> So, it might happen around the end of this year.
> 
> Once I start doing that, I'll do another round of asking the remaining
> people about their copyright notices.  Hopefully, there'l l be few of
> them.


I think you are too sloppy.

Do you not recall the SCO saga?
There a big legal conflict arose over copyright ownership.
Something is still visible on https://en.wikipedia.org/wiki/SCO–Linux_disputes
Maybe this ancient matter has still not been completely settled.

Copyright is a legal matter, not something where convenience plays a role.
In principle you need permission of everyone involved, and not only that,
but you must be able to prove in court that everyone did give this permission.
So one needs written permission.
(And in what jurisdiction? Copyright details differ between countries.)
Some original copyright holders are no longer alive, and the rights
have been inherited.
Life is much easier if you regard those copyright sentences as fossils
carried over from earlier to later versions. And leave them verbatim.

Andries

  reply	other threads:[~2025-06-27  0:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 23:15 man-pages-6.14 released 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 [this message]
2025-06-27  0:45                 ` Alejandro Colomar
2026-02-08 22:04               ` Alejandro Colomar
2025-06-27  0:20             ` Vincent Lefevre
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=20250627000811.GB1598947@if \
    --to=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