From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Yu Zhiguo <yuzg@cn.fujitsu.com>
Subject: Re: [PATCH] xencommons: modprobe xenfs if it not be loaded
Date: Mon, 21 Jun 2010 21:33:31 +0100 [thread overview]
Message-ID: <C8458B2B.2D4F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C1FC7D8.3080101@goop.org>
On 21/06/2010 21:13, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
>> Should I leave tools patches unapplied for a week, perhaps?
>
> You mean the policy is that if a patch is not interesting enough to draw
> comment, you'll accept it by default after a week? What about waiting
> until there are either positive or negative comments, and suggesting the
> poster ping if the patch is uncommented on after a day or two?
Well, possibly. I think that will leave a lot of patches unapplied. Perhaps
that is for the best, of course.
-- Keir
next prev parent reply other threads:[~2010-06-21 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 7:39 [PATCH] xencommons: modprobe xenfs if it not be loaded Yu Zhiguo
2010-06-19 8:10 ` Yu Zhiguo
2010-06-21 9:46 ` Jeremy Fitzhardinge
2010-06-21 14:05 ` Ian Jackson
2010-06-21 14:45 ` Jeremy Fitzhardinge
2010-06-21 16:31 ` Ian Jackson
2010-06-21 17:29 ` Keir Fraser
2010-06-21 17:28 ` Keir Fraser
2010-06-21 20:13 ` Jeremy Fitzhardinge
2010-06-21 20:33 ` Keir Fraser [this message]
2010-06-22 1:18 ` [PATCH] xencommons: mount xenfs directly if xenfs " Yu Zhiguo
2010-06-22 13:47 ` Ian Jackson
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=C8458B2B.2D4F%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
--cc=yuzg@cn.fujitsu.com \
/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).