All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jes.Sorensen@redhat.com
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: [Qemu-devel] Re: [PATCH] hmp-commands.hx: fix badly merged client_migrate_info command
Date: Thu, 10 Mar 2011 17:21:33 -0600	[thread overview]
Message-ID: <4D795CFD.8050707@codemonkey.ws> (raw)
In-Reply-To: <1299686074-25719-1-git-send-email-Jes.Sorensen@redhat.com>

On 03/09/2011 09:54 AM, Jes.Sorensen@redhat.com wrote:
> From: Jes Sorensen<Jes.Sorensen@redhat.com>
>
> client_migrate_info was merged badly,

It wasn't merged badly, it was implemented badly.  The initial 
description confused me because it sounded like a bad merge conflict 
resolution but it just was wrong from the start.

>   placing it between the command
> and the documentation for another command. In addition it did not
> respect the general rule of hmp-commands.hx, of having command
> definition before the documentation.
>
> Signed-off-by: Jes Sorensen<Jes.Sorensen@redhat.com>

Applied.  Thanks.

Regards,

Anthony Liguori

> ---
>   hmp-commands.hx |   32 ++++++++++++++++----------------
>   1 files changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/hmp-commands.hx b/hmp-commands.hx
> index 372bef4..834e6a8 100644
> --- a/hmp-commands.hx
> +++ b/hmp-commands.hx
> @@ -821,16 +821,12 @@ Set maximum tolerated downtime (in seconds) for migration.
>   ETEXI
>
>       {
> -        .name       = "snapshot_blkdev",
> -        .args_type  = "device:B,snapshot_file:s?,format:s?",
> -        .params     = "device [new-image-file] [format]",
> -        .help       = "initiates a live snapshot\n\t\t\t"
> -                      "of device. If a new image file is specified, the\n\t\t\t"
> -                      "new image file will become the new root image.\n\t\t\t"
> -                      "If format is specified, the snapshot file will\n\t\t\t"
> -                      "be created in that format. Otherwise the\n\t\t\t"
> -                      "snapshot will be internal! (currently unsupported)",
> -        .mhandler.cmd_new = do_snapshot_blkdev,
> +        .name       = "client_migrate_info",
> +        .args_type  = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
> +        .params     = "protocol hostname port tls-port cert-subject",
> +        .help       = "send migration info to spice/vnc client",
> +        .user_print = monitor_user_noop,
> +        .mhandler.cmd_new = client_migrate_info,
>       },
>
>   STEXI
> @@ -842,12 +838,16 @@ new parameters (if specified) once the vm migration finished successfully.
>   ETEXI
>
>       {
> -        .name       = "client_migrate_info",
> -        .args_type  = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
> -        .params     = "protocol hostname port tls-port cert-subject",
> -        .help       = "send migration info to spice/vnc client",
> -        .user_print = monitor_user_noop,
> -        .mhandler.cmd_new = client_migrate_info,
> +        .name       = "snapshot_blkdev",
> +        .args_type  = "device:B,snapshot_file:s?,format:s?",
> +        .params     = "device [new-image-file] [format]",
> +        .help       = "initiates a live snapshot\n\t\t\t"
> +                      "of device. If a new image file is specified, the\n\t\t\t"
> +                      "new image file will become the new root image.\n\t\t\t"
> +                      "If format is specified, the snapshot file will\n\t\t\t"
> +                      "be created in that format. Otherwise the\n\t\t\t"
> +                      "snapshot will be internal! (currently unsupported)",
> +        .mhandler.cmd_new = do_snapshot_blkdev,
>       },
>
>   STEXI

  reply	other threads:[~2011-03-10 23:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 15:54 [Qemu-devel] [PATCH] hmp-commands.hx: fix badly merged client_migrate_info command Jes.Sorensen
2011-03-10 23:21 ` Anthony Liguori [this message]
2011-03-11  6:33   ` [Qemu-devel] " Jes Sorensen

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=4D795CFD.8050707@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=Jes.Sorensen@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.