From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] vhost: fix features ack
Date: Thu, 1 Apr 2010 17:53:57 +0300 [thread overview]
Message-ID: <20100401145356.GA6660@redhat.com> (raw)
In-Reply-To: <r2yf43fc5581003311238le9a3e6a6pb82403c96e37b133@mail.gmail.com>
On Wed, Mar 31, 2010 at 10:38:47PM +0300, Blue Swirl wrote:
> > Maybe it makes sense to revert the compile once patches, and discuss
> > these issues before re-commit?
>
> Maybe I'll try to remember this as your favourite problem solving
> approach if I happen to dislike the changes your patches may cause in
> the future. ;-)
My patches are usually posted on list for a week or two
before commit to the main tree. So if there's anything to dislike,
you just need to post your objections, no reason to go through
commit/revert churn.
--
MST
next prev parent reply other threads:[~2010-04-01 14:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 18:20 [Qemu-devel] [PATCH] vhost: fix features ack Michael S. Tsirkin
2010-03-31 18:26 ` [Qemu-devel] " Anthony Liguori
2010-03-31 18:38 ` Luiz Capitulino
2010-03-31 19:07 ` Michael S. Tsirkin
2010-03-31 19:24 ` Anthony Liguori
2010-03-31 19:25 ` Michael S. Tsirkin
2010-03-31 19:37 ` Anthony Liguori
2010-03-31 19:54 ` Blue Swirl
2010-03-31 19:55 ` Anthony Liguori
2010-03-31 20:06 ` Nathan Froyd
2010-03-31 19:46 ` Blue Swirl
2010-03-31 22:45 ` Aurelien Jarno
2010-04-01 2:45 ` Anthony Liguori
2010-04-01 2:46 ` Anthony Liguori
2010-04-01 15:54 ` Blue Swirl
2010-04-01 16:08 ` Anthony Liguori
2010-04-01 16:08 ` Blue Swirl
2010-03-31 19:38 ` Blue Swirl
2010-03-31 19:42 ` Anthony Liguori
2010-03-31 20:03 ` Blue Swirl
2010-04-01 12:09 ` Paul Brook
2010-04-01 14:53 ` Michael S. Tsirkin [this message]
2010-04-04 12:14 ` Michael S. Tsirkin
2010-04-13 21:58 ` [Qemu-devel] " Aurelien Jarno
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=20100401145356.GA6660@redhat.com \
--to=mst@redhat.com \
--cc=blauwirbel@gmail.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 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).