-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I think it worth posting the patch upstream. Libvirt folks would require
that such patch additionally:
- include the change in XML schema (docs/schemas/domaincommon.rng)
- include documentation (docs/
formatdomain.html.in)
- include some test (probably would be enough to include those
attributes in some existing test); and surely do not disable any
existing one...
Do you want to take care of it? I also can do this, but most likely not
earlier than October...
When the patch will be included upstream, we can easily switch to the new
libvirt version, or simply backport it to the current version. But we
want to have libvirt as close to the upstream as possible. The same goes
for Xen hypervisor BTW.
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCAAGBQJV5LheAAoJENuP0xzK19cshe0H/jvwOyeK24lXu3uQiq597L1L
WtrmTgU3OK+KjmrZ/QLuFsnXkSCGaLynKbMb//xThA5e98A9wia6Xw1sbTyjsTDe
Rs35c3x8mqcwveL1BNBr4w9lohkBn6rtgihYPhNmVsI3vSRHnwgxOqaeBLbw05Yq
QtVtKOui/P4/HAQNCWSt4BOPcQSvm7ZIniz0N0LXg3jHBvshhqz11h/n/zi5UiRQ
FOPyGRusJgQDwvZBzioLLPRgm9tUY1kP+zFVYIMDFSPP+Yu0PQ/lCnbiciBd8zSl
8pA2HQRqRAX65nPIQm/D9Ztb8Si4/plELlwn/T++aBcmZkMKr4dZwue8jRTjb6g=
=FiZw
-----END PGP SIGNATURE-----