On Wed, 2009-05-13 at 12:23 -0400, Michael Goldish wrote: > The patches look good, but I haven't tested them yet to make sure > they leave everything at a functional state (will test them and let > you know). Thanks Michael! I will start to give more thorough test on this today, since we finally got 0.10 in shape. > I have a somewhat related question: how is KVM-Autotest development > going to proceed after the upstream merge? Currently I have > comfortable access to our repository at TLV, and on good days I push > as many as 20 patches per day. Should I submit all patches to the > Autotest mailing list after the merge, or are we going to work with > pull requests, or some other way? Will we work with git or svn? Here is my plan: For people inside our team, with access to the git tree we can just pull stuff to the git tree and on a given time basis I can pick up the patches and send them altogether to the KVM and autotest mailing list, wait for reviews and then check them. If you are already used to send all your changes to the KVM mailing list though, this would pose little or no change to you, just send an additional cc to the autotest mailing list. What do you think? > Thanks, > Michael > > ----- Original Message ----- > From: "Lucas Meneghel Rodrigues" <mrodrigu@xxxxxxxxxx> > To: kvm@xxxxxxxxxxxxxxx > Sent: Wednesday, May 13, 2009 4:37:40 PM (GMT+0200) Auto-Detected > Subject: [RFC + PATCHES] Work to get KVM autotest upstream > > These are the patches I have so far related to the work to get kvm > autotest in shape for upstream merge. Please note that once the patches > are applied, the kvm_runtest_2 directory should be placed on a fresh svn > trunk checkout to work, so there's a little bit of tweaking to get them > working. > > That said, this haven't had enough testing. I am posting them here only > if someone wants to take a look at them. > > Cheers, -- Lucas Meneghel Rodrigues Software Engineer (QE) Red Hat - Emerging Technologies -- 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
