On Wed, May 13, 2009 at 9:19 PM, Anthony Liguori <anthony@xxxxxxxxxxxxx> wrote: > Glauber Costa wrote: >> >> On Wed, May 13, 2009 at 5:21 PM, Ryan Harper <ryanh@xxxxxxxxxx> 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. > +5 Note that I'm not against it in any means. I'm all for post for mailing lists. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
