From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [RFC + PATCHES] Work to get KVM autotest upstream Date: Wed, 13 May 2009 19:19:02 -0500 Message-ID: <4A0B6376.8080606@codemonkey.ws> References: <976153117.150491242244197593.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> <1855560932.150641242244290232.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> <20090513202149.GY3233@us.ibm.com> <5d6222a80905131652v20fffdb9jcb8d1b7745fa1d95@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Ryan Harper , Michael Goldish , Lucas Meneghel Rodrigues , kvm@vger.kernel.org To: Glauber Costa Return-path: Received: from mail-gx0-f166.google.com ([209.85.217.166]:38347 "EHLO mail-gx0-f166.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752138AbZENATG (ORCPT ); Wed, 13 May 2009 20:19:06 -0400 Received: by gxk10 with SMTP id 10so1866514gxk.13 for ; Wed, 13 May 2009 17:19:05 -0700 (PDT) In-Reply-To: <5d6222a80905131652v20fffdb9jcb8d1b7745fa1d95@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: Glauber Costa wrote: > On Wed, May 13, 2009 at 5:21 PM, Ryan Harper wrote: > >> I'd definitely like to see patches to the list before committing; we do >> the same for kvm, qemu etc, not sure why kvm-autotest should be any >> different. On the other hand, it's not currently being done that way >> and I'm not losing any sleep over it; it's easy enough to git log and >> and email the list if you break something or think something should be >> done differently. >> >> >> > > If you have, or can have, a publicly visible git tree with your changes, you > can generate pull requests from time to time. Then the job of the maintainer > will be only to sanitize your tree, make sure it is in overall good shape, and > merge it to the main stream. > The advantage to posting non-trivial patches (beyond review) is that it helps people learn about how things are being developed and makes it easier to for others to get involved. It forces a lot of the design discussions to happen on the mailing list. Regards, Anthony Liguori