diff options
| author | Michael Biebl <biebl@debian.org> | 2022-01-13 22:34:27 +0100 |
|---|---|---|
| committer | Michael Biebl <biebl@debian.org> | 2022-01-13 22:34:27 +0100 |
| commit | dd97d276b5d70c3397a4e59c978ca5228f06ba44 (patch) | |
| tree | 5fb3f5e0f5da28e39d3261d50561349a512ba297 /docs/libnm/libnm-docs.xml | |
| parent | 3e2f6719468f8d957ae3cb112f3cb75b9c82d6a7 (diff) | |
| parent | 88c227d90a6b7b388c5c85d72802a0ca8f05ed5c (diff) | |
Update upstream source from tag 'upstream/1.34.0'
Update to upstream version '1.34.0' with Debian dir b598c27ee9cef517760bc745aa6a3bb7d9fb2ecb
Diffstat (limited to 'docs/libnm/libnm-docs.xml')
| -rw-r--r-- | docs/libnm/libnm-docs.xml | 15 |
1 files changed, 8 insertions, 7 deletions
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 @@ <releaseinfo> for libnm &version; The latest version of this documentation can be found on-line at - <ulink url="https://developer.gnome.org/libnm/stable/">https://developer.gnome.org/libnm/stable/</ulink>. + <ulink url="https://networkmanager.dev/docs/libnm/latest/">https://networkmanager.dev/docs/libnm/latest/</ulink>. </releaseinfo> <copyright> @@ -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 - <ulink url="https://developer.gnome.org/NetworkManager/stable/spec.html">D-Bus API</ulink>, + <ulink url="https://networkmanager.dev/docs/api/latest/spec.html">D-Bus API</ulink>, allowing other tools to use the functionality provided by NetworkManager. </para> <para> @@ -103,7 +103,7 @@ </para> <para> An alternative to use of libnm is the use of the - <ulink url="https://developer.gnome.org/NetworkManager/stable/spec.html">D-Bus API</ulink> + <ulink url="https://networkmanager.dev/docs/api/latest/spec.html">D-Bus API</ulink>, 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())]]></programlisting></in <xi:include href="xml/nm-setting-8021x.xml"/> <xi:include href="xml/nm-setting-adsl.xml"/> <xi:include href="xml/nm-setting-bluetooth.xml"/> + <xi:include href="xml/nm-setting-bond-port.xml"/> <xi:include href="xml/nm-setting-bond.xml"/> <xi:include href="xml/nm-setting-bridge-port.xml"/> <xi:include href="xml/nm-setting-bridge.xml"/> @@ -326,20 +327,20 @@ print ("NetworkManager version " + client.get_version())]]></programlisting></in <xi:include href="xml/nm-setting-gsm.xml"/> <xi:include href="xml/nm-setting-hostname.xml"/> <xi:include href="xml/nm-setting-infiniband.xml"/> - <xi:include href="xml/nm-setting-ip4-config.xml"/> - <xi:include href="xml/nm-setting-ip6-config.xml"/> <xi:include href="xml/nm-setting-ip-config.xml"/> <xi:include href="xml/nm-setting-ip-tunnel.xml"/> + <xi:include href="xml/nm-setting-ip4-config.xml"/> + <xi:include href="xml/nm-setting-ip6-config.xml"/> <xi:include href="xml/nm-setting-macsec.xml"/> <xi:include href="xml/nm-setting-macvlan.xml"/> <xi:include href="xml/nm-setting-match.xml"/> <xi:include href="xml/nm-setting-olpc-mesh.xml"/> <xi:include href="xml/nm-setting-ovs-bridge.xml"/> - <xi:include href="xml/nm-setting-ovs-interface.xml"/> <xi:include href="xml/nm-setting-ovs-dpdk.xml"/> + <xi:include href="xml/nm-setting-ovs-external-ids.xml"/> + <xi:include href="xml/nm-setting-ovs-interface.xml"/> <xi:include href="xml/nm-setting-ovs-patch.xml"/> <xi:include href="xml/nm-setting-ovs-port.xml"/> - <xi:include href="xml/nm-setting-ovs-external-ids.xml"/> <xi:include href="xml/nm-setting-ppp.xml"/> <xi:include href="xml/nm-setting-pppoe.xml"/> <xi:include href="xml/nm-setting-proxy.xml"/> |