From 5d9e3721ad196595acd064e0d3ce66edc2613e51 Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Wed, 11 Jan 2023 13:39:59 +0100
Subject: New upstream version 1.40.10

---
 docs/api/dbus-org.freedesktop.NetworkManager.Device.xml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

(limited to 'docs/api/dbus-org.freedesktop.NetworkManager.Device.xml')

diff --git a/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml b/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml
index 0d73ca72..c8ccbd52 100644
--- a/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml
+++ b/docs/api/dbus-org.freedesktop.NetworkManager.Device.xml
@@ -100,6 +100,9 @@ that the user made these changes intentionally outside of NetworkManager).
 Reapply can make the applied-connection different from the
 settings-connection, just like updating the settings-connection can make
 them different.
+</para><para>
+Since 1.42, 1.40.10, "preserve-external-ip" flag (0x1) is supported to not
+remove externally added IP addresses and routes on the device during reapply.
 </para>
 <variablelist role="params">
 <varlistentry>
@@ -117,7 +120,7 @@ If non-zero, the current version id of the applied-connection must match. The cu
 <varlistentry>
   <term><literal>IN u <parameter>flags</parameter></literal>:</term>
   <listitem><para>
-Flags which would modify the behavior of the Reapply call. There are no flags defined currently and the users should use the value of 0.
+Flags which would modify the behavior of the Reapply call. Invalid flags are rejected.
 </para></listitem>
 </varlistentry>
 </variablelist>
-- 
cgit 1.3.0-6-gf8a5