From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: meson.build files are missing copyright/license headers
Date: Mon, 24 Aug 2020 22:29:41 +0400 [thread overview]
Message-ID: <CAJ+F1CL1Hp-g8gNMpdGgk2d0KCzJfBde9f_mX8TLtewe3-B48g@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_0R9mQNFnyzdpR65YRHoDs0uPKWxmCOQUojbpAM-jP8A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
Hi
On Mon, Aug 24, 2020 at 1:44 PM Peter Maydell <peter.maydell@linaro.org>
wrote:
> It looks like the new meson.build files are missing the usual
> copyright-and-license header comment. Could somebody add them,
> please?
>
> scripts/ninjatool.py does have a copyright line but is missing
> the license statement.
>
>
Afaik, most makefiles didn't have any, so it falls under the default GPL2+
LICENSE rule.
If it's a matter of prepending
# SPDX-License-Identifier: GPL-2.0-or-later
On each meson.build file, I can prepare a patch. If you expect something
different, it's time to tell.
thanks
--
Marc-André Lureau
[-- Attachment #2: Type: text/html, Size: 1134 bytes --]
next prev parent reply other threads:[~2020-08-24 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 9:43 meson.build files are missing copyright/license headers Peter Maydell
2020-08-24 18:29 ` Marc-André Lureau [this message]
2020-08-24 18:46 ` Peter Maydell
2020-08-25 5:57 ` Thomas Huth
2020-08-25 9:53 ` Peter Maydell
2020-08-25 13:58 ` Thomas Huth
2020-08-25 14:04 ` Peter Maydell
2020-08-25 14:15 ` Daniel P. Berrangé
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=CAJ+F1CL1Hp-g8gNMpdGgk2d0KCzJfBde9f_mX8TLtewe3-B48g@mail.gmail.com \
--to=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).