Well, excluding developers and testers, few people use libvirt directly by APIs. Since libvirt is also a library, it is worthwhile to mention updates on public APIs in release notes even it is supposed for internal implementation.
On Fri, Nov 8, 2019 at 5:47 PM Jiri Denemark <jdene...@redhat.com> wrote: > On Fri, Nov 08, 2019 at 15:00:22 +0800, Han Han wrote: > > Signed-off-by: Han Han <h...@redhat.com> > > --- > > docs/news.xml | 10 ++++++++++ > > 1 file changed, 10 insertions(+) > > > > diff --git a/docs/news.xml b/docs/news.xml > > index 571a1b6ea4..c37d0d22ef 100644 > > --- a/docs/news.xml > > +++ b/docs/news.xml > > @@ -199,6 +199,16 @@ > > backend. It requires qemu over <code>4.1</code>. > > </description> > > </change> > > + <change> > > + <summary> > > + Introduce virConnectSetIdentity API > > + </summary> > > + <description> > > + For splited libvirt daemons, this API can be used to forward > uid, gid > > + and selinux info from <code>virproxyd</code> to > > + <code>virtqemud</code>. > > + </description> > > + </change> > > </section> > > <section title="Improvements"> > > <change> > > This API is not really supposed to be used by users. It's an internal > implementation detail and should not be mentioned in news. > > Jirka > -- Best regards, ----------------------------------- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list