From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patch mismerge
Date: Fri, 04 Dec 2009 11:11:43 +0100 [thread overview]
Message-ID: <4B18E05F.6030800@redhat.com> (raw)
In-Reply-To: <4B18DC6D.1050100@redhat.com>
Am 04.12.2009 10:54, schrieb Kevin Wolf:
> Hi Anthony,
>
> the description of this patch made it into commit 5f370b1, but the
> content of this commit is obviously nonsense (adds only an empty line).
> It's still uint32_t in current master. Can you take the patch into your
> queue once again? It should still apply cleanly.
Sorry, looks like you already did and it's just not pushed to master yet.
Kevin
prev parent reply other threads:[~2009-12-04 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 11:15 [Qemu-devel] [PATCH] multiboot: Use signed type for negative error numbers Kevin Wolf
2009-12-04 9:54 ` [Qemu-devel] Patch mismerge (was: [PATCH] multiboot: Use signed type for negative error numbers) Kevin Wolf
2009-12-04 10:11 ` Kevin Wolf [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=4B18E05F.6030800@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.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 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).