All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil via <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Files without license statement
Date: Sun, 25 Feb 2024 17:55:26 +0100	[thread overview]
Message-ID: <e2ab2851-3f0b-4f26-8099-4350cfea8b06@weilnetz.de> (raw)
In-Reply-To: <20210223095931.16908-1-alex.bennee@linaro.org>

Hi Paolo,

I just noticed that scripts/fix-multiline-comments.sh has a copyright 
statement, but no license statement. Should that be fixed?

It looks like there exist more files with the same problem (if it is a 
problem), for example docs/devel/loads-stores.rst (written by Peter).

LICENSE says that "Source files with no licensing information are 
released under the GNU General Public License [...]". Does that include 
shell and Python scripts, documentation and other files which might not 
be regarded as "source files"? Or should that be updated to "Any files 
with no licensing information [...]" which would also include files 
which have neither a copyright nor a license statement?

Kind regards
Stefan W.


      parent reply	other threads:[~2024-02-25 16:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23  9:59 [PATCH] docs: move CODING_STYLE into the developer documentation Alex Bennée
2021-02-23 11:05 ` Claudio Fontana
2021-02-24 11:01   ` Alex Bennée
2021-02-23 11:07 ` Peter Maydell
2021-02-23 11:29   ` Philippe Mathieu-Daudé
2021-02-23 11:33     ` Philippe Mathieu-Daudé
2021-02-23 13:37       ` Alex Bennée
2021-02-24 12:15         ` Stefan Hajnoczi
2021-02-24 12:19           ` Daniel P. Berrangé
2021-02-24 15:25             ` Stefan Hajnoczi
2021-02-24 15:33               ` Daniel P. Berrangé
2021-03-01 16:13                 ` Stefan Hajnoczi
2021-02-23 12:03   ` Alex Bennée
2024-02-25 16:55 ` Stefan Weil via [this message]

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=e2ab2851-3f0b-4f26-8099-4350cfea8b06@weilnetz.de \
    --to=qemu-devel@nongnu.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=sw@weilnetz.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.