From 0018d1f3cf71d680d7b6bceda55a5717244d8b26 Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Tue, 16 Aug 2022 18:24:19 +0200
Subject: New upstream version 1.39.90

---
 docs/api/html/settings-hostname.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'docs/api/html/settings-hostname.html')

diff --git a/docs/api/html/settings-hostname.html b/docs/api/html/settings-hostname.html
index 52e0d5fe..d6110465 100644
--- a/docs/api/html/settings-hostname.html
+++ b/docs/api/html/settings-hostname.html
@@ -29,7 +29,7 @@
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
 <h2>hostname</h2>
-<p>hostname — Hostname settings</p>
+<p>hostname —  Hostname settings</p>
 </td>
 <td class="gallery_image" valign="top" align="right"></td>
 </tr></table></div>
@@ -57,25 +57,25 @@
 <td><pre class="screen">from-dhcp</pre></td>
 <td><pre class="screen">NMTernary (int32)</pre></td>
 <td><pre class="screen"></pre></td>
-<td>Whether the system hostname can be determined from DHCP on this connection. When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</td>
+<td> </td>
 </tr>
 <tr>
 <td><pre class="screen">from-dns-lookup</pre></td>
 <td><pre class="screen">NMTernary (int32)</pre></td>
 <td><pre class="screen"></pre></td>
-<td>Whether the system hostname can be determined from reverse DNS lookup of addresses on this device. When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_TRUE (1).</td>
+<td> </td>
 </tr>
 <tr>
 <td><pre class="screen">only-from-default</pre></td>
 <td><pre class="screen">NMTernary (int32)</pre></td>
 <td><pre class="screen"></pre></td>
-<td>If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6). If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route. When set to NM_TERNARY_DEFAULT (-1), the value from global configuration is used. If the property doesn't have a value in the global configuration, NetworkManager assumes the value to be NM_TERNARY_FALSE (0).</td>
+<td> </td>
 </tr>
 <tr>
 <td><pre class="screen">priority</pre></td>
 <td><pre class="screen">int32</pre></td>
 <td><pre class="screen">0</pre></td>
-<td>The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority. If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100. Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.</td>
+<td> </td>
 </tr>
 </tbody>
 </table></div>
-- 
cgit 1.3.0-6-gf8a5