From c25b1c7063278a803c707c80bfc9006d96654a9e Mon Sep 17 00:00:00 2001
From: Umang Jain <umang@endlessm.com>
Date: Wed, 12 Dec 2018 13:35:26 +0530
Subject: [PATCH] man/ostree.repo-config: Update min-free-space-* docs

Docs should reflect the changes done in PR:
https://github.com/ostreedev/ostree/pull/1779

Closes: #1786
Approved by: jlebon
---
 man/ostree.repo-config.xml | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/man/ostree.repo-config.xml b/man/ostree.repo-config.xml
index acaa3be5..618b524b 100644
--- a/man/ostree.repo-config.xml
+++ b/man/ostree.repo-config.xml
@@ -138,7 +138,11 @@ Boston, MA 02111-1307, USA.
           </para>
           <para>
             If <varname>min-free-space-size</varname> is set to a non-zero
-            value, <varname>min-free-space-percent</varname> is ignored.
+            value, <varname>min-free-space-percent</varname> is ignored. Note
+            that, <varname>min-free-space-percent</varname> is not enforced on
+            metadata objects. It is assumed that metadata objects are relatively
+            small in size compared to content objects and thus kept outside the
+            scope of this option.
           </para>
         </listitem>
       </varlistentry>
@@ -156,7 +160,10 @@ Boston, MA 02111-1307, USA.
           <para>
             If this option is set to a non-zero value, and
             <varname>min-free-space-percent</varname> is also set, this option
-            takes priority.
+            takes priority. Note that, <varname>min-free-space-size</varname> is
+            not enforced on metadata objects. It is assumed that metadata objects
+            are relatively small in size compared to content objects and thus kept
+            outside the scope of this option.
           </para>
         </listitem>
       </varlistentry>