On 7/20/20 3:50 AM, Pino Toscano wrote: > Remove the paragraph in the storage pool page that mentions > virConnectGetCapabilities, as virConnectGetCapabilities does not return > any information about pools. > > Signed-off-by: Pino Toscano <ptoscano@xxxxxxxxxx> > --- > docs/formatstoragecaps.html.in | 6 ------ > 1 file changed, 6 deletions(-) > I was asked by Pino to review to be "ok" with removal, so yeah: Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx> John If anyone cares to dredge up history back in Jan/Feb 2019 I believe it was a true statement in at least a patches I had locally, but reviews, conversations, and other adjustments to the code changed that. Been too long to recall all those details. > diff --git a/docs/formatstoragecaps.html.in b/docs/formatstoragecaps.html.in > index ee3888f44d..d8a1cacd96 100644 > --- a/docs/formatstoragecaps.html.in > +++ b/docs/formatstoragecaps.html.in > @@ -13,12 +13,6 @@ > supported, and if relevant the source format types, the required > source elements, and the target volume format types. </p> > > - <p>The Storage Pool Capabilities XML provides more information than the > - <a href="/html/libvirt-libvirt-host.html#virConnectGetCapabilities"> > - <code>virConnectGetCapabilities</code> > - </a> > - which only provides an enumerated list of supported pool types.</p> > - > <h2><a id="elements">Element and attribute overview</a></h2> > > <p>A query interface was added to the virConnect API's to retrieve the >
