From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] License issues
Date: Thu, 14 Aug 2008 09:47:05 -0500 [thread overview]
Message-ID: <48A44569.3050901@codemonkey.ws> (raw)
In-Reply-To: <BC50165F-2237-454E-A633-05D9DE5BB6E3@acm.org>
Simson Garfinkel wrote:
> Greetings. Yesterday I posted a query regarding the license of some of
> the .h files.
>
> Basically, all of the image layer files area clearly licensed to have
> no restrictions, but some of the necessary .h files are missing that
> license.
>
> Who is responsible for maintaining the license of the .h files?
Whoever originally committed the code. If you look at the LICENSE file,
I think the safe thing to assume is that if a file doesn't have an
explicit license associated with it, it is licensed under the GPL.
Regards,
Anthony Liguori
> Regards,
>
>
> Simson Garfinkel
>
>
>
next prev parent reply other threads:[~2008-08-14 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 14:32 [Qemu-devel] License issues Simson Garfinkel
2008-08-14 14:47 ` Anthony Liguori [this message]
2008-08-14 22:43 ` Simson Garfinkel
2008-08-15 1:53 ` Carlos A. M. dos Santos
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=48A44569.3050901@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).