qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 3/5] qapi: Extract qapi/block-core.json definitions
Date: Thu, 05 Jun 2014 10:42:56 -0600	[thread overview]
Message-ID: <53909E10.9020300@redhat.com> (raw)
In-Reply-To: <1401968733-10998-4-git-send-email-benoit.canet@irqsave.net>

[-- Attachment #1: Type: text/plain, Size: 4342 bytes --]

On 06/05/2014 05:45 AM, Benoît Canet wrote:
> Signed-off-by: Benoit Canet <benoit@irqsave.net
> ---
>  qapi-schema.json     | 1428 +-------------------------------------------------
>  qapi/block-core.json | 1406 +++++++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 1417 insertions(+), 1417 deletions(-)

Intra-diff for reference.  It mostly shows that the tweaks you made got
git a bit confused; since 'git diff --patience' shows a smaller diffstat of:
 qapi-schema.json     | 1406
--------------------------------------------------
 qapi/block-core.json | 1406
++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 1406 insertions(+), 1406 deletions(-)

and therefore your larger stat on qapi-schema.json was due to 'git diff'
picking some lines as deletions and reinsertions instead of context to a
larger chunk of moved text.  Since I was able to apply the patch and run
the patience algorithm, I'm confident your code motion was clean.

Reviewed-by: Eric Blake <eblake@redhat.com>

$ diff -u <(sed -n 's/^-//p'  patch3) \
	  <(sed -n 's/^\+//p' patch3)
--- /dev/fd/63	2014-06-05 10:33:52.056307499 -0600
+++ /dev/fd/62	2014-06-05 10:33:52.057307497 -0600
@@ -1,5 +1,18 @@
---
--- a/qapi-schema.json
+++ b/qapi-schema.json
+# Since: 0.14.0
+# Notes: This command only exists as a stop-gap.  Its use is highly
+#        discouraged.  The semantics of this command are not guaranteed.
+#        Known limitations:
+#        o This command is stateless, this means that commands that depend
+#          on state information (such as getfd) might not work
+#       o Commands that prompt the user for data (eg. 'cont' when the
block
+#         device is encrypted) don't currently work
+{ 'command': 'human-monitor-command',
+  'data': {'command-line': 'str', '*cpu-index': 'int'},
+  'returns': 'str' }
+++ b/qapi/block-core.json
+
+##
 # @SnapshotInfo
 #
 # @id: unique snapshot id
@@ -674,24 +687,6 @@
   'data': 'BlockdevSnapshot' }

 ##
-# Since: 0.14.0
-#
-# Notes: This command only exists as a stop-gap.  Its use is highly
-#        discouraged.  The semantics of this command are not guaranteed.
-#
-#        Known limitations:
-#
-#        o This command is stateless, this means that commands that depend
-#          on state information (such as getfd) might not work
-#
-#       o Commands that prompt the user for data (eg. 'cont' when the
block
-#         device is encrypted) don't currently work
-##
-{ 'command': 'human-monitor-command',
-  'data': {'command-line': 'str', '*cpu-index': 'int'},
-  'returns': 'str' }
-
-##
 # @block-commit
 #
 # Live commit of data from overlay image nodes into backing nodes - i.e.,
@@ -793,21 +788,28 @@
 #
 # @buf-size: #optional maximum amount of data in flight from source to
 #            target (since 1.4).
+#
 # @on-source-error: #optional the action to take on an error on the
source,
 #                   default 'report'.  'stop' and 'enospc' can only be
used
 #                   if the block device supports io-status (see
BlockInfo).
+#
 # @on-target-error: #optional the action to take on an error on the
target,
 #                   default 'report' (no limitations, since this
applies to
 #                   a different block device than @device).
+#
 # Returns: nothing on success
 #          If @device is not a valid block device, DeviceNotFound
+#
 # Since 1.3
+##
 { 'command': 'drive-mirror',
   'data': { 'device': 'str', 'target': 'str', '*format': 'str',
             'sync': 'MirrorSyncMode', '*mode': 'NewImageMode',
             '*speed': 'int', '*granularity': 'uint32',
             '*buf-size': 'int', '*on-source-error': 'BlockdevOnError',
             '*on-target-error': 'BlockdevOnError' } }
+
+##
 # @block_set_io_throttle:
 #
 # Change I/O throttle limits for a block drive.
@@ -1013,8 +1015,6 @@
 { 'command': 'block-job-complete', 'data': { 'device': 'str' } }

 ##
-
-##
 # @BlockdevDiscardOptions
 #
 # Determines how to handle discard requests.
@@ -1417,5 +1417,3 @@
 ##
 { 'command': 'blockdev-add', 'data': { 'options': 'BlockdevOptions' } }

--- a/qapi/block-core.json
-- 


-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2014-06-05 16:43 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 [this message]
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 ` [Qemu-devel] [PATCH v2 5/5] qapi: Set QAPI descriptions files under the GPL V2 license Benoît Canet
2014-06-05 16:52   ` 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=53909E10.9020300@redhat.com \
    --to=eblake@redhat.com \
    --cc=benoit.canet@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).