libsmbconf:registry: clarify the appearance of "includes" in forbidden_names

Signed-off-by: Michael Adam <obnox@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>

diff --git a/source3/lib/smbconf/smbconf_reg.c b/source3/lib/smbconf/smbconf_reg.c
index 9bdcbfd9037fa41671ebe1df978ad60cb2ca74d5..84294ab663e30d83b5a1670c2ced73bad69a5e98 100644 (file)
--- a/source3/lib/smbconf/smbconf_reg.c
+++ b/source3/lib/smbconf/smbconf_reg.c
@@ -62,7 +62,13 @@ bool smbconf_reg_parameter_is_valid(const char *param_name)
                "lock dir",
                "config backend",
                "include",
-               "includes", /* this has a special meaning internally */
+               /*
+                * "includes" has a special meaning internally.
+                * It is currently not necessary to list it here since it is
+                * not a valid parameter. But for clarity and safety, we keep
+                * it for now.
+                */
+               INCLUDES_VALNAME,
                NULL
        };
        const char **forbidden = NULL;