From: Simon Tournier <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Wilko Meyer <w@wmeyer.eu>, help-guix@gnu.org
Subject: Re: documentation on copyright headers?
Date: Thu, 11 Jan 2024 18:29:28 +0100 [thread overview]
Message-ID: <87y1cvzslj.fsf@gmail.com> (raw)
In-Reply-To: <871qc3yufq.fsf@gmail.com>
Hi,
On Sun, 03 Dec 2023 at 14:09, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> I think it should be avoided as well, the long list of copyrights are
> already a bit messy to maintain across trees :-).
In addition to the current mess, we also keep Copyright header even if
the code holding such Copyright had been removed since. Legally
speaking, I think – although I am not totally sure – the copyright
applies to the current source code and not to the history of additions.
> info '(maintain) Legally Significant' offers as advice that changes of
> 15 lines or less or not legally significant for copyright.
For the interested reader, it comes from the package ’gnu-standards’,
also online:
https://www.gnu.org/prep/maintain/html_node/Legally-Significant.html#Legally-Significant
Cheers,
simon
next prev parent reply other threads:[~2024-01-12 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 14:39 documentation on copyright headers? Wilko Meyer
2023-11-16 17:01 ` Felix Lechner via
2023-11-17 9:54 ` pelzflorian (Florian Pelz)
2023-12-01 14:48 ` Simon Tournier
2023-12-02 9:37 ` pelzflorian (Florian Pelz)
2023-12-03 19:09 ` Maxim Cournoyer
2024-01-11 17:29 ` Simon Tournier [this message]
2024-01-14 0:55 ` Wilko Meyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1cvzslj.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=w@wmeyer.eu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).