From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-trivial@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/1] Add -incoming help text
Date: Mon, 1 Jun 2015 10:29:32 +0100 [thread overview]
Message-ID: <20150601092931.GE2314@work-vm> (raw)
In-Reply-To: <87pp5flvka.fsf@blackfin.pond.sub.org>
* Markus Armbruster (armbru@redhat.com) wrote:
> Michael Tokarev <mjt@tls.msk.ru> writes:
>
> > 29.05.2015 21:52, Dr. David Alan Gilbert (git) wrote:
> >> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >>
> >> The help/man text for
> >>
> >> -incoming defer
> >>
> >> didn't make it through the merge of the code that implemented it.
> >>
> >> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> >> ---
> >> qemu-options.hx | 6 +++++-
> >> 1 file changed, 5 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/qemu-options.hx b/qemu-options.hx
> >> index dad49cf..3085412 100644
> >> --- a/qemu-options.hx
> >> +++ b/qemu-options.hx
> >> @@ -3238,7 +3238,9 @@ DEF("incoming", HAS_ARG, QEMU_OPTION_incoming, \
> >> "-incoming fd:fd\n" \
> >> "-incoming exec:cmdline\n" \
> >> " accept incoming migration on given file descriptor\n" \
> >> - " or from given external command\n",
> >> + " or from given external command\n" \
> >> + "-incoming defer\n" \
> >> + " wait for the URI to be specified via migrate_incoming\n",
> >> QEMU_ARCH_ALL)
> >> STEXI
> >> @item -incoming tcp:[@var{host}]:@var{port}[,to=@var{maxport}][,ipv4][,ipv6]
> >> @@ -3254,6 +3256,8 @@ Accept incoming migration from a given filedescriptor.
> >>
> >> @item -incoming exec:@var{cmdline}
> >> Accept incoming migration as an output from specified external command.
> >> +@item -incoming defer
> >> +Wait for the URI to be specified via migrate_incoming.
> >
> > I wonder what's the reason of mentioning it twice with
> > such a short and _identical_ text each time...
>
> Because that's the way our documentation works.
>
> The first hunk patches the fourth argument of DEF(), which goes into
> -help.
>
> The second hunk patches STEXI..ETEXI, which goes via qemu-options.texi
> into qemu.1 and qemu-doc.{dvi,info,html,pdf}.
>
> > Maybe
> > it's a good idea to reword the second message a bit.
> > Because actually it is not clear what does the whole
> > thing mean, what qemu will do when starting? Will it
> > accept other commands?
>
> You're right in that .texi allows more verbose explanations than -help.
>
> David's text looks okay to me as is. Perhaps your questions inspire
> further improvements.
How about changing the second part to.
+@item -incoming defer
+Wait for the URI to be specified via migrate_incoming. The monitor can
+be used to change settings (such as migration parameters) prior to issuing
+the migrate_incoming to allow the migration to begin.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-06-01 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 18:52 [Qemu-devel] [PATCH 1/1] Add -incoming help text Dr. David Alan Gilbert (git)
2015-05-30 14:15 ` Michael Tokarev
2015-06-01 7:47 ` Markus Armbruster
2015-06-01 9:29 ` Dr. David Alan Gilbert [this message]
2015-06-01 11:11 ` Markus Armbruster
2015-06-02 5:29 ` Michael Tokarev
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=20150601092931.GE2314@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=quintela@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).