From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions
Date: Mon, 19 Dec 2011 19:12:33 +0200 [thread overview]
Message-ID: <4EEF7081.4000907@redhat.com> (raw)
In-Reply-To: <4EEF633E.2000709@codemonkey.ws>
On 12/19/2011 06:15 PM, Anthony Liguori wrote:
>
> Pulled both of these. Thanks.
I notice the merge logs are fairly silent. You can make them more
interesting by setting the git config variable merge.log to true.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-12-19 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 13:35 [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions Avi Kivity
2011-12-15 13:35 ` [Qemu-devel] [PATCH 1/2] etraxfs_eth: drop bogus cpu_unregister_io_memory() Avi Kivity
2011-12-15 13:35 ` [Qemu-devel] [PATCH 2/2] memory: move obsolete exec.c functions to a private header Avi Kivity
2011-12-15 14:21 ` [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions Paolo Bonzini
2011-12-15 14:22 ` Avi Kivity
2011-12-15 14:26 ` Anthony Liguori
2011-12-19 15:01 ` Anthony Liguori
2011-12-19 15:06 ` Avi Kivity
2011-12-19 15:34 ` Avi Kivity
2011-12-19 16:15 ` Anthony Liguori
2011-12-19 17:12 ` Avi Kivity [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=4EEF7081.4000907@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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.