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

[Xen-devel] Re: [PATCH 00 of 10] blkfront pvops updates, v2

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 00 of 10] blkfront pvops updates, v2
From: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Date: Fri, 30 Apr 2010 15:31:48 -0700
Cc: Xen <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Fri, 30 Apr 2010 15:32:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BDB56AD.3030502@xxxxxxxx>
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: <patchbomb.1272664874@xxxxxxxxxxxxxxxxxxxxxxx> <4BDB56AD.3030502@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2010-04-30 at 18:16 -0400, Jeremy Fitzhardinge wrote:
> On 04/30/2010 03:01 PM, Daniel Stodden wrote:
> >  * Found the switch [again] for HG to strip those headers -- cheers.
> >   
> 
> The ideal for me is if you have a git tree I can pull from, 

There's still hope to get one. Didn't happen yet. Ian?

> but failing
> that, the most useful format for mailed patches is something that "git
> am" can accept.  It looks like it will take the attachments OK, but it
> cats the mail body onto the attachment, so it ends up with the commit
> comment twice.  If you have a non-mangling mailer, it's probably easiest
> if you just include the full commit comment+patch in the mail body (it's
> easier to comment on the patches in mail that way too).

Okay, whatever works.

> > Oh beautiful. This apparently strips the first comment line together
> > with the patch header. Looks buggy.
> >
> > F*! 
> >
> > Sorry. Fix/resend?
> >   
> 
> Did it lose something other than the subject?  

No.

> git am picked it up from
> the email Subject: line, so it didn't matter it was missing from the
> patch comment itself.

Good.

Thanks,
Daniel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel