|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2
On Fri, Jan 29, 2010 at 01:22:50AM -0800, Daniel Stodden wrote:
> On Fri, 2010-01-29 at 03:52 -0500, Keir Fraser wrote:
> > On 29/01/2010 08:45, "Daniel Stodden" <daniel.stodden@xxxxxxxxxx> 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.
>
> To avoid confusion: By inline I meant the content-disposition. The
> visual results would combine the best of both. But I suspect the results
> somwhat depend on the mailer in use.
>
> It's completely up to you. I don't charge for python cycles. :)
>
> So far I got
>
> [alias]
> email-xen = email --attach --inline --to 'Xen
> <xen-devel@xxxxxxxxxxxxxxxxxxx>'
> email-xapi = email --review --inline --to 'Xen API
> <xen-api@xxxxxxxxxxxxxxxxxxx>'
>
> Maybe Pasi knows a decent corner on the wiki where this stuff can
> converge to gatekeeper preferences.
>
There's a note about submitting patches in:
http://wiki.xensource.com/xenwiki/XenFaq
I can add this stuff there.
So those aliases should go to .hgrc ?
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [PATCH 1 of 4] blktap2: Sort out tapdisk IPC init, (continued)
- [Xen-devel] [PATCH 1 of 4] blktap2: Sort out tapdisk IPC init, Daniel Stodden
- [Xen-devel] [PATCH 2 of 4] blktap2: Sort out tapdisk AIO init, Daniel Stodden
- [Xen-devel] [PATCH 3 of 4] blktap2: Separate tapdisk raw I/O into different backends, Daniel Stodden
- [Xen-devel] [PATCH 4 of 4] blktap2: Prefer AIO eventfd support on kernels >= 2.6.22, Daniel Stodden
- [Xen-devel] Re: [PATCH 0 of 4] aio event fd support to blktap2, Daniel Stodden
- Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2, Keir Fraser
- Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2, Daniel Stodden
- Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2, Daniel Stodden
- Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2, Keir Fraser
- Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2, Daniel Stodden
- Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2,
Pasi Kärkkäinen <=
- Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2, Daniel Stodden
Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2, Ian Campbell
|
|
|
|
|