From: "Carlos A. M. dos Santos" <unixmania@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] License issues
Date: Thu, 14 Aug 2008 22:53:58 -0300 [thread overview]
Message-ID: <e71790db0808141853p7ef0fc39v55018e6c5ce942dc@mail.gmail.com> (raw)
In-Reply-To: <BC50165F-2237-454E-A633-05D9DE5BB6E3@acm.org>
On Thu, Aug 14, 2008 at 11:32 AM, Simson Garfinkel <simsong@acm.org> 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?
Fabrice Bellard is the copyright holder of QEMU so is the only person
legally allowed to add license statements to those files. (Assuming
that he owns them, of course, but experience taught me never make
assumptions about copyrights and licenses.)
--
If you think things can't get worse it's probably only
because you lack sufficient imagination.
prev parent reply other threads:[~2008-08-15 1:54 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
2008-08-14 22:43 ` Simson Garfinkel
2008-08-15 1:53 ` Carlos A. M. dos Santos [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=e71790db0808141853p7ef0fc39v55018e6c5ce942dc@mail.gmail.com \
--to=unixmania@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).