Hi Christophe, I understand clearly the process. I was just asking if there are some other requirements I should be aware of juts to save time.
BTW. Splitting the developments into several patchs (by features) will introduce a dependency between them; they will have to be reviewed and applied in a specific order. Does it mean that the new set of patch must be submitted one after one ? In case a patch needs to be revised, all other patchs (on the same source code) may need to be regenerated, right ? Thanks, Yves. -----Message d'origine----- De : Christophe Fergeau [mailto:[email protected]] Envoyé : mercredi 1 octobre 2014 10:20 À : Yves Vinter Cc : Eric Blake; [email protected] Objet : Re: [libvirt] [PATCH] New features implemented in hyperv libvirt driver Hi Yves, On Wed, Oct 01, 2014 at 06:59:52AM +0000, Yves Vinter wrote: > No answer ? If you split the patch in several smaller chunks as Eric requested and send them to the mailing list for review, the next steps will be that people on this list will review pour patch, potentially make comments about how the code could be made better, or point out some bugs, ... If there are such comments, you'll have to address them, and potentially send revised versions of the patches. If there are no review comments, they will be committed in the upstream repository. I don't know if this is the kind of answer you were waiting for? Christophe -- libvir-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/libvir-list
