From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: [Qemu-devel] Re: [PATCH] hmp-commands.hx: fix badly merged client_migrate_info command
Date: Fri, 11 Mar 2011 07:33:17 +0100 [thread overview]
Message-ID: <4D79C22D.7030802@redhat.com> (raw)
In-Reply-To: <4D795CFD.8050707@codemonkey.ws>
On 03/11/11 00:21, Anthony Liguori wrote:
> 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.
I wasn't quite sure where the badness happened, it basically looked like
a bad cleanup after a git pull. Sorry if I gave the impression that the
merge at your end was to blame.
Cheers,
Jes
prev parent reply other threads:[~2011-03-11 6:33 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 ` [Qemu-devel] " Anthony Liguori
2011-03-11 6:33 ` Jes Sorensen [this message]
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=4D79C22D.7030802@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--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.