On 5/26/20 2:37 PM, Aleksandar Markovic wrote:
+mips ``fulong2e`` machine (since 5.1) +''''''''''''''''''''''''''''''''''''' + +This machine has been renamed ``fuloong2e``. +
Libvirt doesn't have any special handling for this machine so this shouldn't impact us.
Well, Peter,
I was also wondering libvirt listed as a recipient, and I think it creates unneeded noise in your group, but Philippe uses some his system for automatic picking of recipients, and libivrt somehow appears there during that process. Philippe, either correct that detail in this particular component of your workflow, or change entirely your system for recipient choice - the current workflow creates incredible amount of noise, wasting time of many people.
This happened before in case of deprecating an ancient mips machine, that absolutely doesn't have anything to do with linvirt.
See commit b02c9bc35a0: MAINTAINERS: New section "Incompatible changes", copy libvir-list Libvirt developers would like to be copied on patches to qemu-doc appendix "Deprecated features". Do them the favor. Signed-off-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Thomas Huth <thuth@redhat.com> Reviewed-by: Cornelia Huck <cohuck@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> What says Peter is as a libvirt maintainer he is fine with this deprecation, as it doesn't have side effect on libvirt. Similarly with the previous "ancient mips machine".
In some large companies, there where some analysis on how much is the cost of sending an e-mail to all people in the company, in terms of wasting time on reading or just seeing such email. The result was: such single e-mail costs the company $2000 - in wasted time of its employees.
Aleksanadar