From: Bruno Haible <bruno@clisp.org>
To: Eric Blake <eblake@redhat.com>
Cc: bug-gnulib@gnu.org
Subject: Re: put appropriate license notices in source files
Date: Fri, 04 Jun 2021 23:02:36 +0200 [thread overview]
Message-ID: <2629110.UVmybNBK2l@omega> (raw)
In-Reply-To: <20210604202552.52xlrdzdwpebnrdi@redhat.com>
Eric Blake wrote:
> Speaking of tools, should we include SPDX tags alongside the full text
> of all our licenses, as that is yet another thing that aids
> license-checking tools?
If there is a GNU policy on this, I would follow it.
Personally I think there is little point to it. SPDX arose in the Linux kernel,
where there is (or has traditionally been at some time) a sloppy attitude
regarding copyright and license headers.
In GNU, the systematic use of a license header in most files alleviates the
problem to a large extent.
Bruno
next prev parent reply other threads:[~2021-06-04 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 20:03 put appropriate license notices in source files Bruno Haible
2021-06-04 20:25 ` Eric Blake
2021-06-04 20:36 ` Paul Eggert
2021-06-04 21:02 ` Bruno Haible [this message]
2021-06-07 10:13 ` Simon Josefsson via Gnulib discussion list
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2629110.UVmybNBK2l@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eblake@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).