From 17ba622451d51bbe7b0000bab0172894b8e60ae8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A1n=20Tomko?= <jtomko@redhat.com>
Date: Mon, 15 Jun 2015 14:08:05 +0200
Subject: [PATCH] man: clarify usage of virsh blockcopy with --xml

The --xml option is mandatory if an XML description is used.
Otherwise the third parameter is treated as the destination.

https://bugzilla.redhat.com/show_bug.cgi?id=1206406#c3
---
 tools/virsh.pod | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/virsh.pod b/tools/virsh.pod
index 9b57c8cbf3..154922e3b2 100644
--- a/tools/virsh.pod
+++ b/tools/virsh.pod
@@ -989,12 +989,12 @@ unlimited. The hypervisor can choose whether to reject the value or
 convert it to the maximum value allowed.
 
 =item B<blockcopy> I<domain> I<path> { I<dest> [I<format>] [I<--blockdev>]
-| I<xml> } [I<--shallow>] [I<--reuse-external>] [I<bandwidth>]
+| I<--xml> B<file> } [I<--shallow>] [I<--reuse-external>] [I<bandwidth>]
 [I<--wait> [I<--async>] [I<--verbose>]] [{I<--pivot> | I<--finish>}]
 [I<--timeout> B<seconds>] [I<granularity>] [I<buf-size>]
 
 Copy a disk backing image chain to a destination.  Either I<dest> as
-the destination file name, or I<xml> as the name of an XML file containing
+the destination file name, or I<--xml> with the name of an XML file containing
 a top-level <disk> element describing the destination, must be present.
 Additionally, if I<dest> is given, I<format> should be specified to declare
 the format of the destination (if I<format> is omitted, then libvirt
-- 
GitLab