public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Glauber Costa <glommer@gmail.com>
Cc: Ryan Harper <ryanh@us.ibm.com>,
	Michael Goldish <mgoldish@redhat.com>,
	Lucas Meneghel Rodrigues <mrodrigu@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [RFC + PATCHES] Work to get KVM autotest upstream
Date: Wed, 13 May 2009 19:19:02 -0500	[thread overview]
Message-ID: <4A0B6376.8080606@codemonkey.ws> (raw)
In-Reply-To: <5d6222a80905131652v20fffdb9jcb8d1b7745fa1d95@mail.gmail.com>

Glauber Costa wrote:
> On Wed, May 13, 2009 at 5:21 PM, Ryan Harper <ryanh@us.ibm.com> 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



  reply	other threads:[~2009-05-14  0:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <976153117.150491242244197593.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-13 19:51 ` [RFC + PATCHES] Work to get KVM autotest upstream Michael Goldish
2009-05-13 20:21   ` Ryan Harper
2009-05-13 23:52     ` Glauber Costa
2009-05-14  0:19       ` Anthony Liguori [this message]
2009-05-14  1:19         ` Glauber Costa
     [not found] <1863742528.124741242230448044.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-13 16:23 ` Michael Goldish
2009-05-13 17:15   ` Lucas Meneghel Rodrigues
2009-05-13 13:37 Lucas Meneghel Rodrigues

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A0B6376.8080606@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=glommer@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mgoldish@redhat.com \
    --cc=mrodrigu@redhat.com \
    --cc=ryanh@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox