Update upstream source from tag 'upstream/1.20.0'

Update to upstream version '1.20.0'
with Debian dir 832bc2b5ac5f253004165f6354c938efbe172206

1 files changed, 8 insertions, 1 deletions

diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Settings.Connection.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Settings.Connection.html
index 030af0d6..7226560d 100644
--- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Settings.Connection.html
+++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Settings.Connection.html
@@ -216,7 +216,8 @@ Update2 (IN  a{sa{sv}} settings,
           "0x4" (in-memory-detached),
           "0x8" (in-memory-only),
           "0x10" (volatile),
-          "0x20" (block-autoconnect).
+          "0x20" (block-autoconnect),
+          "0x40" (no-reapply).
           Unknown flags cause the call to fail.
         <em class="parameter"><code>args</code></em>: optional arguments dictionary, for extensibility. Currently no
           arguments are accepted. Specifying unknown keys causes the call
@@ -229,6 +230,12 @@ Update2 (IN  a{sa{sv}} settings,
         the change is only made in memory (without touching an eventual
         profile on disk). If neither 0x1 nor 0x2 is set, the change is made
         in memory only, if the connection is already in memory only.
+        The flags 0x4 (in-memory-detached) and 0x8 (in-memory-only) are like
+        "in-memory", but behave slightly different when migrating the profile
+        from disk to in-memory.
+        The flag 0x20 (block-autoconnect) blocks auto-connect on the updated
+        profile, and 0x40 (no-reapply) prevents "connection.zone" and "connection.metered"
+        properties to take effect on currently active devices.
         Secrets may be part of the update request, and will be either stored in persistent
         storage or sent to a Secret Agent for storage, depending on the flags
         associated with each secret.