From: Wilko Meyer <w@wmeyer.eu>
To: help-guix@gnu.org
Subject: documentation on copyright headers?
Date: Thu, 16 Nov 2023 15:39:47 +0100 [thread overview]
Message-ID: <87o7ftkapb.fsf@wmeyer.eu> (raw)
Hi Guix,
The "The Perfect Set-Up" chapter of guixes manual describes how to set
up copyright.el to support the process of inserting/updating ones
copyright header; however it doesn't answer:
- why a copyright header has to be inserted
- if a copyright header has to be inserted for all files that are
subject to changes (is there a treshold? can it be left out for minor
changes to files etc.?) of a sent patch.
I'm not too knowledgable in copyright law to answer these things myself
and would guess, that explaining this briefly could be useful in guixes
documentation on contributions.
--
Kind regards,
Wilko Meyer
w@wmeyer.eu
next reply other threads:[~2023-11-16 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 14:39 Wilko Meyer [this message]
2023-11-16 17:01 ` documentation on copyright headers? 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
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=87o7ftkapb.fsf@wmeyer.eu \
--to=w@wmeyer.eu \
--cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).