From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Baruch Even <baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
Cc: KVM <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Copyright of user directory
Date: Tue, 14 Nov 2006 21:39:03 +0200 [thread overview]
Message-ID: <455A1B57.5050206@qumranet.com> (raw)
In-Reply-To: <20061114193301.GL28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>
Baruch Even wrote:
> As part of the Debian package I must know which parts of the code to
> attribute to whom and what license applies to each part. I've noticed
> that the code in the user/ directory has no copyright statement or
> license. Can someone clarify that?
>
>
/user is LGPL, I'll add the appropriate blurb.
> The management_services also has no attribution and license. What is it
> used for anyway?
>
>
Whoops, that's proprietary, I shouldn't have let that slip out.
I'll release a new tarball so you can package it.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-11-14 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 19:33 Copyright of user directory Baruch Even
[not found] ` <20061114193301.GL28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>
2006-11-14 19:39 ` Avi Kivity [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=455A1B57.5050206@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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