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-ppc-devel

Re: [XenPPC][Patch 1/3] xen patches for xm save/restore

To: geyi <kudva@xxxxxxxxxxxxxx>
Subject: Re: [XenPPC][Patch 1/3] xen patches for xm save/restore
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Thu, 02 Nov 2006 13:01:21 -0600
Cc: xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 02 Nov 2006 13:45:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <454A219B.8030203@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <454A219B.8030203@xxxxxxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Yi, a few general comments about submitting patches:

     1. As I told you before, do not use Thunderbird. It corrupts the
        whitespace so your patches do not apply. 
     2. You should include a "patch 0" with a description of what this
        patchset accomplishes. The description should also indicate if
        you believe the patches are ready to be applied, or if you're
        just sending them out to get comments from other developers.
        Tools like "hg email" (part of the "MQ" Mercurial extension)
        will do this for you automatically. 
     3. Each patch should contain a single logical change. For example,
        adding support for "getshadowlist" should be a single patch,
        with no unrelated changes in it. 
     4. Each patch should apply, build, and accomplish something useful
        depending only on the patches before it. In this case, patches 1
        and 2 won't even build, because XEN_DOMCTL_getshadowlist isn't
        defined until patch 3. As maintainer, I should be able to accept
        only patch 1, or only patches 1 and 2, or patches 1, 2, and 3. 
     5. You must include a Signed-off-by line with each patch. See
        http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_dco.html 
for the explanation.

-- 
Hollis Blanchard
IBM Linux Technology Center


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

<Prev in Thread] Current Thread [Next in Thread>