xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Daniel Stodden <daniel.stodden@citrix.com>
Cc: Xen <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 4] aio event fd support to blktap2
Date: Fri, 29 Jan 2010 08:52:48 +0000	[thread overview]
Message-ID: <C7885260.80A4%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1264754755.3295.18.camel@ramone.somacoma.net>

On 29/01/2010 08:45, "Daniel Stodden" <daniel.stodden@citrix.com> wrote:

> On Fri, 2010-01-29 at 03:29 -0500, Daniel Stodden wrote:
>> On Fri, 2010-01-29 at 03:09 -0500, Keir Fraser wrote:
>>> Echo the changeset comment and sign-off into the email body would be better,
>>> but your re-send is fine as far as I'm concerned. I should be able to apply
>>> the attachments no problem.
>> 
>> Patchbomb as of hg 1.3.1 doesn't seem to do this.
> 
> Ah, it does.
> 
> So --inline implies --attach,
> but is still different from --inline *and* --attach.
> 
> Sorry for the noise.

By the way, attaching and inlining a whole patch is also acceptable. Some
people like inline patches, so that they can easily review and comment. I
like attachments because they JustWork when I'm trying to apply big bundles
of patches.

For smaller patches, inline only can be okay. For some reason, I find that
inline large patches rarely apply for me. It's really weird, given I only
fetchmail and munpack the emails, and yet I have a suspicion the mangling
does happen at my end.

 -- Keir

  reply	other threads:[~2010-01-29  8:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 22:37 [PATCH 0 of 4] aio event fd support to blktap2 Daniel Stodden
2010-01-28 22:37 ` [PATCH 1 of 4] blktap2: Sort out tapdisk IPC init Daniel Stodden
2010-01-28 22:37 ` [PATCH 2 of 4] blktap2: Sort out tapdisk AIO init Daniel Stodden
2010-01-28 22:37 ` [PATCH 3 of 4] blktap2: Separate tapdisk raw I/O into different backends Daniel Stodden
2010-01-28 22:37 ` [PATCH 4 of 4] blktap2: Prefer AIO eventfd support on kernels >= 2.6.22 Daniel Stodden
2010-01-29  6:55 ` [PATCH 0 of 4] aio event fd support to blktap2 Keir Fraser
2010-01-29  7:44   ` Daniel Stodden
2010-01-29  7:44     ` [PATCH 1 of 4] blktap2: Sort out tapdisk IPC init Daniel Stodden
2010-01-29  7:44     ` [PATCH 2 of 4] blktap2: Sort out tapdisk AIO init Daniel Stodden
2010-01-29  7:44     ` [PATCH 3 of 4] blktap2: Separate tapdisk raw I/O into different backends Daniel Stodden
2010-01-29  7:44     ` [PATCH 4 of 4] blktap2: Prefer AIO eventfd support on kernels >= 2.6.22 Daniel Stodden
2010-01-29  7:55     ` [PATCH 0 of 4] aio event fd support to blktap2 Daniel Stodden
2010-01-29  8:09     ` Keir Fraser
2010-01-29  8:29       ` Daniel Stodden
2010-01-29  8:45         ` Daniel Stodden
2010-01-29  8:52           ` Keir Fraser [this message]
2010-01-29  9:22             ` Daniel Stodden
2010-01-29 10:06               ` Pasi Kärkkäinen
2010-01-29 10:27                 ` Daniel Stodden
2010-01-29 10:34 ` Ian Campbell
2010-01-29 10:52   ` Daniel Stodden
2010-02-02 22:53 ` David P. Quigley
2010-02-02 23:10   ` Daniel Stodden
2010-02-02 23:08     ` David P. Quigley
2010-02-02 23:23     ` David P. Quigley
2010-02-02 23:57       ` Daniel Stodden
2010-02-03  0:37         ` David P. Quigley
     [not found]           ` <1265219911.14885.1940.camel@agari.van.xensource.com>
     [not found]             ` <1265224548.19768.3.camel@moss-terrapins.epoch.ncsc.mil>
2010-02-03 19:41               ` Daniel Stodden
2010-02-03 19:47                 ` Daniel Stodden
2010-02-03 19:41                   ` David P. Quigley
2010-02-03 20:02                     ` Daniel Stodden
2010-02-03 20:12                       ` David P. Quigley

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=C7885260.80A4%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=daniel.stodden@citrix.com \
    --cc=xen-devel@lists.xensource.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).