Date: Fri, 11 May 2018 22:08:45 +0200 Subject: New upstream version 1.10.8 --- docs/libnm/html/libnm-nm-dbus-interface.html | 94 +--------------------------- 1 file changed, 2 insertions(+), 92 deletions(-) (limited to 'docs/libnm/html/libnm-nm-dbus-interface.html') diff --git a/docs/libnm/html/libnm-nm-dbus-interface.html b/docs/libnm/html/libnm-nm-dbus-interface.html index dbf59b84..575adb4e 100644 --- a/docs/libnm/html/libnm-nm-dbus-interface.html +++ b/docs/libnm/html/libnm-nm-dbus-interface.html @@ -206,10 +206,6 @@ #define -NM_DBUS_INTERFACE_CHECKPOINT - - -#define NM_DBUS_INTERFACE_SETTINGS @@ -410,10 +406,6 @@ enum -NMSettingsConnectionFlags - - -enum NMActivationStateFlags @@ -443,13 +435,11 @@ ├── NM80211ApSecurityFlags ├── NMActivationStateFlags ├── NMBluetoothCapabilities - ├── NMCheckpointCreateFlags ├── NMDeviceCapabilities ├── NMDeviceModemCapabilities ├── NMDeviceWifiCapabilities ├── NMSecretAgentCapabilities ├── NMSecretAgentGetSecretsFlags - ├── NMSettingsConnectionFlags ╰── NMSettingsUpdate2Flags @@ -707,12 +697,6 @@

NM_DBUS_INTERFACE_CHECKPOINT

#define NM_DBUS_INTERFACE_CHECKPOINT           NM_DBUS_INTERFACE ".Checkpoint"
-

NM_DBUS_INTERFACE_SETTINGS

#define NM_DBUS_INTERFACE_SETTINGS        "org.freedesktop.NetworkManager.Settings"

@@ -2877,28 +2861,10 @@ VPN plugin authentication dialogs.

- -

NM_CHECKPOINT_CREATE_FLAG_ALLOW_OVERLAPPING

- -

by default, creating - a checkpoint fails if there are already existing checkoints that - reference the same devices. With this flag, creation of such - checkpoints is allowed, however, if an older checkpoint - that references overlapping devices gets rolled back, it will - automatically destroy this checkpoint during rollback. This - allows to create several overlapping checkpoints in parallel, - and rollback to them at will. With the special case that - rolling back to an older checkpoint will invalidate all - overlapping younger checkpoints. This opts-in that the - checkpoint can be automatically destroyed by the rollback - of an older checkpoint. (Since: 1.12)

- - -

Since: 1.4 (gi flags generated since 1.12)

Since: 1.4

@@ -2948,62 +2914,6 @@ VPN plugin authentication dialogs.

enum NMSettingsConnectionFlags

Flags describing the current activation state.

Members

----- - - - - - - - - - - - - - - - - - - - - - - -

NM_SETTINGS_CONNECTION_FLAG_NONE	- an alias for numeric zero, no flags set. -
NM_SETTINGS_CONNECTION_FLAG_UNSAVED	- the connection is not saved to disk. - That either means, that the connection is in-memory only and currently - is not backed by a file. Or, that the connection is backed by a file, - but has modifications in-memory that were not persisted to disk. -
NM_SETTINGS_CONNECTION_FLAG_NM_GENERATED	- A connection is "nm-generated" if - it was generated by NetworkManger. If the connection gets modified or saved - by the user, the flag gets cleared. A nm-generated is also unsaved - and has no backing file as it is in-memory only. -
NM_SETTINGS_CONNECTION_FLAG_VOLATILE	- The connection will be deleted - when it disconnects. That is for in-memory connections (unsaved), which are - currently active but deleted on disconnect. Volatile connections are - always unsaved, but they are also no backing file on disk and are entirely - in-memory only. -

Since: 1.12

enum NMActivationStateFlags

Flags describing the current activation state.

@@ -3158,7 +3068,7 @@ VPN plugin authentication dialogs.

Since: 1.12

Since: 1.10.2

-- cgit 1.3.0-6-gf8a5 From 04bc9e1cd3544445d883ad29ea108c1645c8e7b7 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Mon, 4 Jun 2018 00:07:45 +0200 Subject: New upstream version 1.11.4 --- docs/libnm/html/libnm-nm-dbus-interface.html | 98 ++++++++++++++++++++++++++-- 1 file changed, 94 insertions(+), 4 deletions(-) (limited to 'docs/libnm/html/libnm-nm-dbus-interface.html') diff --git a/docs/libnm/html/libnm-nm-dbus-interface.html b/docs/libnm/html/libnm-nm-dbus-interface.html index 575adb4e..03257ef2 100644 --- a/docs/libnm/html/libnm-nm-dbus-interface.html +++ b/docs/libnm/html/libnm-nm-dbus-interface.html @@ -8,7 +8,7 @@ - + @@ -206,6 +206,10 @@ #define +NM_DBUS_INTERFACE_CHECKPOINT + + +#define NM_DBUS_INTERFACE_SETTINGS @@ -406,6 +410,10 @@ enum +NMSettingsConnectionFlags + + +enum NMActivationStateFlags @@ -435,11 +443,13 @@ ├── NM80211ApSecurityFlags ├── NMActivationStateFlags ├── NMBluetoothCapabilities + ├── NMCheckpointCreateFlags ├── NMDeviceCapabilities ├── NMDeviceModemCapabilities ├── NMDeviceWifiCapabilities ├── NMSecretAgentCapabilities ├── NMSecretAgentGetSecretsFlags + ├── NMSettingsConnectionFlags ╰── NMSettingsUpdate2Flags @@ -697,6 +707,12 @@

NM_DBUS_INTERFACE_CHECKPOINT

#define NM_DBUS_INTERFACE_CHECKPOINT           NM_DBUS_INTERFACE ".Checkpoint"
+

NM_DBUS_INTERFACE_SETTINGS

#define NM_DBUS_INTERFACE_SETTINGS        "org.freedesktop.NetworkManager.Settings"

@@ -2861,10 +2877,28 @@ VPN plugin authentication dialogs.

+ +

NM_CHECKPOINT_CREATE_FLAG_ALLOW_OVERLAPPING

+ +

by default, creating + a checkpoint fails if there are already existing checkoints that + reference the same devices. With this flag, creation of such + checkpoints is allowed, however, if an older checkpoint + that references overlapping devices gets rolled back, it will + automatically destroy this checkpoint during rollback. This + allows to create several overlapping checkpoints in parallel, + and rollback to them at will. With the special case that + rolling back to an older checkpoint will invalidate all + overlapping younger checkpoints. This opts-in that the + checkpoint can be automatically destroyed by the rollback + of an older checkpoint. (Since: 1.12)

+ + +

Since: 1.4

Since: 1.4 (gi flags generated since 1.12)

@@ -2914,6 +2948,62 @@ VPN plugin authentication dialogs.

enum NMSettingsConnectionFlags

Flags describing the current activation state.

Members

+++++ + + + + + + + + + + + + + + + + + + + + + + +

NM_SETTINGS_CONNECTION_FLAG_NONE	+ an alias for numeric zero, no flags set. +
NM_SETTINGS_CONNECTION_FLAG_UNSAVED	+ the connection is not saved to disk. + That either means, that the connection is in-memory only and currently + is not backed by a file. Or, that the connection is backed by a file, + but has modifications in-memory that were not persisted to disk. +
NM_SETTINGS_CONNECTION_FLAG_NM_GENERATED	+ A connection is "nm-generated" if + it was generated by NetworkManger. If the connection gets modified or saved + by the user, the flag gets cleared. A nm-generated is also unsaved + and has no backing file as it is in-memory only. +
NM_SETTINGS_CONNECTION_FLAG_VOLATILE	+ The connection will be deleted + when it disconnects. That is for in-memory connections (unsaved), which are + currently active but deleted on disconnect. Volatile connections are + always unsaved, but they are also no backing file on disk and are entirely + in-memory only. +

Since: 1.12

enum NMActivationStateFlags

Flags describing the current activation state.

@@ -3068,11 +3158,11 @@ VPN plugin authentication dialogs.

Since: 1.10.2

Since: 1.12

Generated by GTK-Doc V1.28 \ No newline at end of file -- cgit 1.3.0-6-gf8a5