qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] LICENSE: clarify licensing
Date: Tue, 20 Nov 2012 00:00:51 +0400 (MSK)	[thread overview]
Message-ID: <alpine.LNX.2.00.1211200000290.6102@linmac> (raw)
In-Reply-To: <87obitcr10.fsf@codemonkey.ws>

On Mon, 19 Nov 2012, Anthony Liguori wrote:

> malc <av1474@comtv.ru> writes:
> 
> > On Mon, 19 Nov 2012, Peter Maydell wrote:
> >
> >> On 19 November 2012 18:21, malc <av1474@comtv.ru> wrote:
> >> > On Mon, 19 Nov 2012, Anthony Liguori wrote:
> >> >> +5) Files without explicit licenses fall under the GPL v2.
> >> >
> >> > I have issue with this, files without licenses are just that files
> >> > without licenses.
> >> 
> >> If we believe this (and it seems a logical thing to believe)
> >> then QEMU's not distributable until we rewrite or remove or track
> >> down all authors for all the files without licenses...
> >
> > Yes.
> 
> That's ridiculous.
> 
> There has always been a LICENSE file with a catch-all clause going back
> to at least 2005.
> 
> If a file doesn't have an explicit LICENSE, it falls under the catch all
> clause.
> 

Wishful thinking.

-- 
mailto:av1474@comtv.ru

  reply	other threads:[~2012-11-19 20:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 16:40 [Qemu-devel] [PATCH] LICENSE: clarify licensing Anthony Liguori
2012-11-19 18:14 ` Paolo Bonzini
2012-11-19 18:21 ` malc
2012-11-19 18:34   ` Peter Maydell
2012-11-19 18:34     ` malc
2012-11-19 19:08       ` Stefan Weil
2012-11-19 19:30         ` malc
2012-11-19 19:48       ` Anthony Liguori
2012-11-19 20:00         ` malc [this message]
2012-11-20 10:39           ` 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=alpine.LNX.2.00.1211200000290.6102@linmac \
    --to=av1474@comtv.ru \
    --cc=anthony@codemonkey.ws \
    --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).