WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2

To: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0 of 4] aio event fd support to blktap2
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Fri, 29 Jan 2010 12:06:34 +0200
Cc: Xen <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Fri, 29 Jan 2010 02:06:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1264756970.3295.41.camel@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C7885260.80A4%keir.fraser@xxxxxxxxxxxxx> <1264756970.3295.41.camel@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
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