From: Markus Armbruster <armbru@redhat.com>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [QUESTION] What is the best license option for new files introduced in QEMU?
Date: Tue, 26 Nov 2019 10:29:13 +0100 [thread overview]
Message-ID: <87lfs39eae.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAL1e-=gmaimCBh5NBBYFp6Z1ci4ZheQtXpyjU9Uexqi4zSHh2A@mail.gmail.com> (Aleksandar Markovic's message of "Mon, 25 Nov 2019 18:49:51 +0100")
Aleksandar Markovic <aleksandar.m.mail@gmail.com> writes:
> 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:
The situation is confusing. It's a mess of our own making.
> * GPL 2.0
> * GPL 2.0 (or later at your option)
> * GPL 2.1
> * GPL 2.1 (or later at your option)
>
> or something else. (The rest od wording of license preamble is clear
> to me.) Please somebody explsin snd clarify.
Let's not add to the mess: GPLv2+ unless you have a compelling reason to
deviate, spelled out in your commit message.
In my opinion, accepting GPLv2-only contributions was a mistake.
prev parent reply other threads:[~2019-11-26 9:50 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
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 [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=87lfs39eae.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=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 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.