From 88c227d90a6b7b388c5c85d72802a0ca8f05ed5c Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 13 Jan 2022 22:30:39 +0100 Subject: New upstream version 1.34.0 --- docs/libnm/libnm-docs.xml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) (limited to 'docs/libnm/libnm-docs.xml') diff --git a/docs/libnm/libnm-docs.xml b/docs/libnm/libnm-docs.xml index fad95522..11a1b730 100644 --- a/docs/libnm/libnm-docs.xml +++ b/docs/libnm/libnm-docs.xml @@ -10,7 +10,7 @@ for libnm &version; The latest version of this documentation can be found on-line at - https://developer.gnome.org/libnm/stable/. + https://networkmanager.dev/docs/libnm/latest/. @@ -56,7 +56,7 @@ management service. NetworkManager supports a wide variety of network configuration scenarios, hardware devices and protocol families. Most of the functionality is exposed on a - D-Bus API, + D-Bus API, allowing other tools to use the functionality provided by NetworkManager. @@ -103,7 +103,7 @@ An alternative to use of libnm is the use of the - D-Bus API + D-Bus API, directly. This gives you larger flexibility and reduces the overhead of linking with the libnm library. This makes sense if your task is simple and you have a good D-Bus library at your disposal. Activating a particular connection profile @@ -315,6 +315,7 @@ print ("NetworkManager version " + client.get_version())]]> + @@ -326,20 +327,20 @@ print ("NetworkManager version " + client.get_version())]]> - - + + - + + - -- cgit 1.3.0-6-gf8a5