qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, "Benoît Canet" <benoit.canet@irqsave.net>,
	"Benoit Canet" <benoit@irqsave.net>,
	lcapitulino@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v2 5/5] qapi: Set QAPI descriptions files under the GPL V2 license
Date: Thu,  5 Jun 2014 13:45:33 +0200	[thread overview]
Message-ID: <1401968733-10998-6-git-send-email-benoit.canet@irqsave.net> (raw)
In-Reply-To: <1401968733-10998-1-git-send-email-benoit.canet@irqsave.net>

Signed-off-by: Benoit Canet <benoit@irqsave.net>
---
 qapi-schema.json     | 4 ++++
 qapi/block-core.json | 4 ++++
 qapi/block.json      | 4 ++++
 qapi/common.json     | 4 ++++
 4 files changed, 16 insertions(+)

diff --git a/qapi-schema.json b/qapi-schema.json
index 14b498b..870d3f6 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -1,5 +1,9 @@
 # -*- Mode: Python -*-
 #
+# This file is part of the QEMU project.
+#
+# This file is licensed under the GPL V2.
+#
 # QAPI Schema
 
 # QAPI common definitions
diff --git a/qapi/block-core.json b/qapi/block-core.json
index 7215e48..33bd93f 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -1,5 +1,9 @@
 # -*- Mode: Python -*-
 #
+# This file is part of the QEMU project.
+#
+# This file is licensed under the GPL V2.
+#
 # QAPI block core definitions (vm unrelated)
 
 # QAPI common definitions
diff --git a/qapi/block.json b/qapi/block.json
index 61c463a..b5cf325 100644
--- a/qapi/block.json
+++ b/qapi/block.json
@@ -1,5 +1,9 @@
 # -*- Mode: Python -*-
 #
+# This file is part of the QEMU project.
+#
+# This file is licensed under the GPL V2.
+#
 # QAPI block definitions (vm related)
 
 # QAPI block core definitions
diff --git a/qapi/common.json b/qapi/common.json
index 4e9a21f..6d8a308 100644
--- a/qapi/common.json
+++ b/qapi/common.json
@@ -1,5 +1,9 @@
 # -*- Mode: Python -*-
 #
+# This file is part of the QEMU project.
+#
+# This file is licensed under the GPL V2.
+#
 # QAPI common definitions
 
 ##
-- 
1.9.1

  parent reply	other threads:[~2014-06-05 11:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 11:45 [Qemu-devel] [PATCH v2 0/5] Extract QAPI block commands Benoît Canet
2014-06-05 11:45 ` [Qemu-devel] [PATCH v2 1/5] qapi: Extract qapi/common.json definitions Benoît Canet
2014-06-05 15:16   ` Eric Blake
2014-06-05 11:45 ` [Qemu-devel] [PATCH v2 2/5] qapi: create two block related json modules Benoît Canet
2014-06-05 16:20   ` Eric Blake
2014-06-05 11:45 ` [Qemu-devel] [PATCH v2 3/5] qapi: Extract qapi/block-core.json definitions Benoît Canet
2014-06-05 16:42   ` Eric Blake
2014-06-05 11:45 ` [Qemu-devel] [PATCH v2 4/5] qapi: Extract qapi/block.json definitions Benoît Canet
2014-06-05 16:45   ` Eric Blake
2014-06-05 11:45 ` Benoît Canet [this message]
2014-06-05 16:52   ` [Qemu-devel] [PATCH v2 5/5] qapi: Set QAPI descriptions files under the GPL V2 license Eric Blake
2014-06-05 16:53 ` [Qemu-devel] [PATCH v2 0/5] Extract QAPI block commands Eric Blake
2014-06-06 15:26   ` Benoît Canet
2014-06-06 14:28 ` Stefan Hajnoczi
2014-06-06 14:33   ` Benoît Canet

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=1401968733-10998-6-git-send-email-benoit.canet@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=benoit@irqsave.net \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).