From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [QUESTION] What is the best license option for new files introduced in QEMU?
Date: Mon, 25 Nov 2019 20:25:59 +0100 [thread overview]
Message-ID: <CAL1e-=i-u5eR7Fk_Muobbe0-Viim0iPceHoEGtJWCq7L1o9teA@mail.gmail.com> (raw)
In-Reply-To: <CAL1e-=gmaimCBh5NBBYFp6Z1ci4ZheQtXpyjU9Uexqi4zSHh2A@mail.gmail.com>
On Mon, Nov 25, 2019 at 6:49 PM Aleksandar Markovic
<aleksandar.m.mail@gmail.com> wrote:
>
> I read LICENSE file, but I read also recent contributions, and it is
> not clear to me what version of GPL is best/recommended for new file
> just being introduced to QEMU:
>
> * GPL 2.0
> * GPL 2.0 (or later at your option)
> * GPL 2.1
> * GPL 2.1 (or later at your option)
>
Thomas pointed to me that I mixed up GPL and LGPL - which is true.
Still, the question remains with these options:
* GPL 2.0
* GPL 2.0 + wording "or later (at your option)"
* LGPL 2.1
* LGPL 2.1 + wording "or later (at your option)"
The context of my question is that I am reviewing a series that came
with files with different license preambles (or without it at all), and I
want to advice the submitters on the best option.
Sincerely,
Aleksandar
> or something else. (The rest od wording of license preamble is clear
> to me.) Please somebody explsin snd clarify.
>
> Thanks,
> Aleksandar
next prev parent reply other threads:[~2019-11-25 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 17:49 [QUESTION] What is the best license option for new files introduced in QEMU? Aleksandar Markovic
2019-11-25 19:25 ` Aleksandar Markovic [this message]
2019-11-25 21:27 ` Eric Blake
2019-11-25 23:59 ` Aleksandar Markovic
2019-11-26 7:05 ` Thomas Huth
2019-11-26 9:29 ` Markus Armbruster
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='CAL1e-=i-u5eR7Fk_Muobbe0-Viim0iPceHoEGtJWCq7L1o9teA@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--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).