From: Glauber Costa <gcosta@redhat.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, akpm@linux-foundation.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/3 - resend] kvmclock reboot
Date: Tue, 18 Mar 2008 07:55:39 -0300 [thread overview]
Message-ID: <47DF9FAB.6030604@redhat.com> (raw)
In-Reply-To: <47DF9ED3.2070302@qumranet.com>
Avi Kivity wrote:
> Glauber Costa wrote:
>> Avi,
>>
>> Hope this series is okay now.
>>
>> Thanks for the testing
>>
>>
>>
>
> Applied, thanks.
>
> [Once a patchset has been applied and pushed (as seen on kvm-commits), I
> prefer incremental patches]
>
But I think this is a very good case of an exception, since the applied
patches would break bisect. I prefer to hear "damn glommer!" because of
that than "damn glommer!!" because of a broken bisect.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-18 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 10:30 [PATCH 0/3 - resend] kvmclock reboot Glauber Costa
2008-03-18 10:30 ` [PATCH 1/3] [PATCH] allow machine_crash_shutdown to be replaced Glauber Costa
2008-03-18 10:30 ` [PATCH 2/3] [PATCH] make native_machine_shutdown non-static Glauber Costa
2008-03-18 10:30 ` [PATCH 3/3] [PATCH] disable clock before rebooting Glauber Costa
2008-03-18 10:52 ` [PATCH 0/3 - resend] kvmclock reboot Avi Kivity
2008-03-18 10:55 ` Glauber Costa [this message]
2008-03-18 11:00 ` Avi Kivity
2008-03-18 11:02 ` Glauber Costa
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=47DF9FAB.6030604@redhat.com \
--to=gcosta@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=virtualization@lists.linux-foundation.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