[taler-docs] branch master updated: -generate taler-auditor-sync man page

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new b231c3d  -generate taler-auditor-sync man page
b231c3d is described below

commit b231c3dcc34c1d7997bfb8c00acb217738342fca
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sun Aug 8 22:32:20 2021 +0200

    -generate taler-auditor-sync man page
---
 conf.py                   | 2 ++
 manpages/taler.conf.5.rst | 6 +++++-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/conf.py b/conf.py
index cd59bf0..f7aa52e 100644
--- a/conf.py
+++ b/conf.py
@@ -280,6 +280,8 @@ man_pages = [
      1),
     ("manpages/taler-auditor-dbinit.1", "taler-auditor-dbinit",
      "setup auditor database", "GNU Taler contributors", 1),
+    ("manpages/taler-auditor-sync.1", "taler-auditor-sync",
+     "tool to safely synchronize auditor database", "GNU Taler contributors", 
1),
     ("manpages/taler-auditor-httpd.1", "taler-auditor-httpd",
      "HTTP server providing a RESTful API to access a Taler auditor",
      "GNU Taler contributors", 1),
diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst
index fb20d58..ee67358 100644
--- a/manpages/taler.conf.5.rst
+++ b/manpages/taler.conf.5.rst
@@ -52,7 +52,11 @@ overrides these defaults.
 A configuration file may include another, by using the ``@INLINE@`` directive,
 for example, in ``main.conf``, you could write ``@INLINE@ sub.conf`` to
 include the entirety of ``sub.conf`` at that point in ``main.conf``.
-.. TODO: Document ‘taler-config -V’ in light of ‘@INLINE@’ in taler-config(1).
+
+Be extra careful when using ``taler-config -V VALUE`` to change configuration
+values: it will destroy all uses of ``@INLINE@`` and furthermore remove all
+comments from the configuration file!
+
 
 GLOBAL OPTIONS
 --------------

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.