A deprecation is inherantly a warning, not an error, so adding an error
with this name makes no conceptual sense.

Features in drivers may come & go at any time and we've always use the
VIR_ERR_NO_SUPPORT to indicate when a hypervisor driver does not support
a particular API.

Changed in v2:

 - Don't remove the driver API entry point entirely - leave it set
   to NULL, so we can document version number range.

Daniel P. Berrangé (4):
  qemu: delete methods which are no longer supported
  docs: update QEMU driver docs to replace deprecated with deleted
  Revert "news: Mention VIR_ERR_DEPRECATED in improvements"
  Revert "error: Add VIR_ERR_DEPRECATED error code"

 docs/drvqemu.html.in        |  2 +-
 docs/hvsupport.pl           | 25 +++++++++++++++----------
 docs/libvirt.css            |  4 ++--
 docs/news.xml               | 10 ----------
 include/libvirt/virterror.h |  1 -
 src/qemu/qemu_driver.c      | 33 ++-------------------------------
 src/util/virerror.c         |  4 ----
 7 files changed, 20 insertions(+), 59 deletions(-)

-- 
2.21.0

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list