From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [Xen-Devel] Enabling IRQ Crossbar (Secondary
 Interrupt Controller) Support
Date: Thu, 30 Jul 2015 11:57:46 +0100
Message-ID: <1438253866.11600.291.camel@citrix.com>
References: <55AD817E.6020300@ti.com> <55AE13C1.1060507@citrix.com>
	<55AE520B.90604@ti.com> <1437491565.8383.59.camel@citrix.com>
	<55B93962.2060408@ti.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <55B93962.2060408@ti.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Brandon Perez <a0225893@ti.com>, Julien Grall <julien.grall@citrix.com>, xen-devel@lists.xen.org
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2015-07-29 at 16:36 -0400, Brandon Perez wrote:
> On 07/21/2015 11:12 AM, Ian Campbell wrote:
> > On Tue, 2015-07-21 at 10:07 -0400, Brandon Perez wrote:
> > > 
> > >       I'm not sure that these patches are quite ready yet to be put
> > > into
> > > the Xen repo.
> > 
> > That's ok, but even for an RFC (Request For Comments) please post them
> > one patch per email in the manner of git send-email. You can use -
> > -subject-prefix='PATCH RFC' to tag them as such.
> > 
> > Thanks,
> > Ian.
> > 
> 
> All,
> 
>      Apologies for the delay, I've been pretty busy the last week. Also, 
> sorry for the confusion with sending the patches, this is my first time 
> working with an open-source dev group.
> 
>      I've sent the patches, one per email, via git.

Thanks. For next time please can you send a batch of related patches all
with the same git send-email invocation such that they arrive as a set of
threaded mails (i.e. with a References header on the previous). That keeps
the related patches together in peoples in box, and also labels them 1/N,
2/N etc so we know which order they are applicable in.

Invoking send-email with --dry-run will print out all the headers it would
send, so you can check it will do as expected.

http://wiki.xen.org/wiki/Submitting_Xen_Patches#Git_send-email talks about
this stuff a bit.

Thanks,

Ian.