On Fri, Nov 27, 2015 at 08:16:46PM +0300, Roman Kagan wrote:
On Thu, Nov 26, 2015 at 06:29:45PM -0600, Jeff Nelson wrote:
On Thu, Nov 26, 2015 at 08:12:41PM +0300, Roman Kagan wrote:
Do I get it right that the way virtio-win is packaged for Fedora and RHEL is driven by the scripts at
https://github.com/crobinso/virtio-win-pkg-scripts
and I should be submitting patches or pull requests to it?
Yes, that's what I use to package the drivers for RHEL.
Or should the layout be determined only by the build machinery at
https://github.com/YanVugenfirer/kvm-guest-drivers-windows
and I should be direct my submissions that way?
I don't know, but if you work strictly with virtio-win-pkg-scripts it shouldn't matter.
Thanks a lot, I'll look into it early next week.
I guess there's no mailing list, so I'll have to do pull requests on github, right?
I guess for general discussion, the virt-tools mailing list is the right one, but use pull requests on github for patches I suppose. https://www.redhat.com/mailman/listinfo/virt-tools-list Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top