From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: "Zhang, Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] 0/10 Splitting kvm structure (V3)
Date: Tue, 20 Nov 2007 13:21:55 -0600 [thread overview]
Message-ID: <1195586515.21816.10.camel@basalt> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC9A1058-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Wed, 2007-11-21 at 00:32 +0800, Zhang, Xiantao wrote:
> Hi Avi,
> I rebased the series of patches for splitting kvm structure. For
> more readability, I split them into small ones.
You still seem to be ignoring my comments on these patches. I spent some
time to respin your original patch, and now you've broken it into 10,
still lacking those changes. At least part of this is based on the
latency of Sourceforge mailing lists, but it's becoming frustrating.
Also, you are still sending very whitespace-mangled emails. I see that
you are also sending patches as attachments, but I really wish you could
figure out a way to solve this problem. If you use a standard mailing
script, the mails will also be threaded correctly for ease of reading.
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2007-11-20 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 16:32 [PATCH] 0/10 Splitting kvm structure (V3) Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDC9A1058-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-20 19:21 ` Hollis Blanchard [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=1195586515.21816.10.camel@basalt \
--to=hollisb-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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