From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39798) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b83DP-0007g9-24 for qemu-devel@nongnu.org; Wed, 01 Jun 2016 06:17:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b83DH-0007Aw-Sk for qemu-devel@nongnu.org; Wed, 01 Jun 2016 06:17:29 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50076) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b83DH-0007Ap-O6 for qemu-devel@nongnu.org; Wed, 01 Jun 2016 06:17:23 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 3B0BD63147 for ; Wed, 1 Jun 2016 10:17:23 +0000 (UTC) From: "Daniel P. Berrange" Date: Wed, 1 Jun 2016 11:17:13 +0100 Message-Id: <1464776234-9910-2-git-send-email-berrange@redhat.com> In-Reply-To: <1464776234-9910-1-git-send-email-berrange@redhat.com> References: <1464776234-9910-1-git-send-email-berrange@redhat.com> Subject: [Qemu-devel] [PATCH 1/2] migration: fix typos in qapi-schema from latest migration additions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Amit Shah , Juan Quintela , Eric Blake , "Daniel P. Berrange" Recent migration QAPI enhancements had a few spelling mistakes and also incorrect version number in a few places. Signed-off-by: Daniel P. Berrange --- qapi-schema.json | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/qapi-schema.json b/qapi-schema.json index 8483bdf..5c7b87c 100644 --- a/qapi-schema.json +++ b/qapi-schema.json @@ -486,7 +486,7 @@ # # @error-desc: #optional the human readable error description string, when # @status is 'failed'. Clients should not attempt to parse the -# error strings. (Since 2.6) +# error strings. (Since 2.7) # # Since: 0.14.0 ## @@ -631,7 +631,7 @@ # migration URI does not already include a hostname. For # example if using fd: or exec: based migration, the # hostname must be provided so that the server's x509 -# certificate identity canbe validated. (Since 2.7) +# certificate identity can be validated. (Since 2.7) # # Since: 2.4 ## @@ -672,7 +672,7 @@ # migration URI does not already include a hostname. For # example if using fd: or exec: based migration, the # hostname must be provided so that the server's x509 -# certificate identity canbe validated. (Since 2.7) +# certificate identity can be validated. (Since 2.7) # # Since: 2.4 ## @@ -708,14 +708,14 @@ # be for a 'client' endpoint, while for the incoming side the # credentials must be for a 'server' endpoint. Setting this # will enable TLS for all migrations. The default is unset, -# resulting in unsecured migration at the QEMU level. (Since 2.6) +# resulting in unsecured migration at the QEMU level. (Since 2.7) # # @tls-hostname: hostname of the target host for the migration. This is # required when using x509 based TLS credentials and the # migration URI does not already include a hostname. For # example if using fd: or exec: based migration, the # hostname must be provided so that the server's x509 -# certificate identity canbe validated. (Since 2.6) +# certificate identity can be validated. (Since 2.7) # # Since: 2.4 ## -- 2.5.5