From f08fe72e25a850f312a342ea4e2ce15de43cfcf6 Mon Sep 17 00:00:00 2001
Message-Id: <f08fe72e25a850f312a342ea4e2ce15de43cfcf6.1713406235.git.mdw@distorted.org.uk>
From: Mark Wooding <mdw@chiark.greenend.org.uk>
Date: Tue, 23 May 2017 11:19:55 +0100
Subject: [PATCH] peerdb/peers.in.5.in: Finish the example configuration
 fragment.
Organization: Straylight/Edgeware

From: Mark Wooding <mdw@distorted.org.uk>

---
 peerdb/peers.in.5.in | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/peerdb/peers.in.5.in b/peerdb/peers.in.5.in
index 9ce9561c..27992838 100644
--- a/peerdb/peers.in.5.in
+++ b/peerdb/peers.in.5.in
@@ -127,9 +127,23 @@ section (though falling back to scanning parent sections).  For
 example, given the sections
 .VS
 [parent]
-detail = in parent
+detail = in $(name)
 blurb = expand $(detail)
+
+[child]
+@inherit = parent
 .VE
+the key
+.B blurb
+takes the value
+.RB ` "expand in parent" '
+in section
+.BR parent ,
+and
+.RB ` "expand in child" '
+in section
+.BR child .
+.PP
 Apart from its effect on lookups, as just described, the
 .B @inherit
 key is entirely ignored.  In particular, it is never written to the
-- 
[mdw]