Libguestfs - Mar 2022 - [p2v PATCH] virt-p2v.pod: fix typo in paragraph about virt-v2v log capture

Commit 9b057cc1ac5f ("p2v: Don't display debugging messages in the run
dialog.", 2016-06-18) contained the following hunk:
> @@ -749,8 +749,9 @@ file (see above), which in turn references the NBD
listening port(s)
>  of the data connection(s).
>
>  Output from the virt-v2v command (messages, debugging etc) is saved
> -both in the log file on the conversion server, and sent over the
> -control connection to be displayed in the graphical UI.
> +both in the log file on the conversion server.  Only informational
> +messages are sent back over the control connection to be displayed in
> +the graphical UI.
>
>  =head1 SEE ALSO
>
The word "both" no longer makes sense; remove it.

Fixes: 9b057cc1ac5f56d5f93b33c705d153b7ce01e628
Signed-off-by: Laszlo Ersek <lersek at redhat.com>
---
 virt-p2v.pod | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/virt-p2v.pod b/virt-p2v.pod
index 758021134958..5f4aa5763524 100644
--- a/virt-p2v.pod
+++ b/virt-p2v.pod
@@ -720,10 +720,10 @@ virt-v2v command.  The virt-v2v command references the
F<physical.xml>
 file (see above), which in turn references the NBD listening port(s)
 of the data connection(s).
 
-Output from the virt-v2v command (messages, debugging etc) is saved
-both in the log file on the conversion server.  Only informational
-messages are sent back over the control connection to be displayed in
-the graphical UI.
+Output from the virt-v2v command (messages, debugging etc) is saved in
+the log file on the conversion server.  Only informational messages are
+sent back over the control connection to be displayed in the graphical
+UI.
 
 =head1 SEE ALSO
 
-- 
2.19.1.3.g30247aa5d201

On Sat, Mar 19, 2022 at 08:08:12AM +0100, Laszlo Ersek
wrote:
> Commit 9b057cc1ac5f ("p2v: Don't display debugging messages in the
run
> dialog.", 2016-06-18) contained the following hunk:
> 
> > @@ -749,8 +749,9 @@ file (see above), which in turn references the NBD
listening port(s)
> >  of the data connection(s).
> >
> >  Output from the virt-v2v command (messages, debugging etc) is saved
> > -both in the log file on the conversion server, and sent over the
> > -control connection to be displayed in the graphical UI.
> > +both in the log file on the conversion server.  Only informational
> > +messages are sent back over the control connection to be displayed in
> > +the graphical UI.
> >
> >  =head1 SEE ALSO
> >
> 
> The word "both" no longer makes sense; remove it.
> 
> Fixes: 9b057cc1ac5f56d5f93b33c705d153b7ce01e628
> Signed-off-by: Laszlo Ersek <lersek at redhat.com>
> ---
>  virt-p2v.pod | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/virt-p2v.pod b/virt-p2v.pod
> index 758021134958..5f4aa5763524 100644
> --- a/virt-p2v.pod
> +++ b/virt-p2v.pod
> @@ -720,10 +720,10 @@ virt-v2v command.  The virt-v2v command references
the F<physical.xml>
>  file (see above), which in turn references the NBD listening port(s)
>  of the data connection(s).
>  
> -Output from the virt-v2v command (messages, debugging etc) is saved
> -both in the log file on the conversion server.  Only informational
> -messages are sent back over the control connection to be displayed in
> -the graphical UI.
> +Output from the virt-v2v command (messages, debugging etc) is saved in
> +the log file on the conversion server.  Only informational messages are
> +sent back over the control connection to be displayed in the graphical
> +UI.
ACK - you may as well just push tiny docs fixes like these.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW