From 429ab4ed02e2ef0887e92942987e5702022c8a7f Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Sun, 22 Sep 2013 08:54:30 +0200 Subject: libsmbconf:registry: clarify the appearance of "includes" in forbidden_names Signed-off-by: Michael Adam Reviewed-by: Andrew Bartlett --- source3/lib/smbconf/smbconf_reg.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'source3/lib') diff --git a/source3/lib/smbconf/smbconf_reg.c b/source3/lib/smbconf/smbconf_reg.c index 9bdcbfd903..84294ab663 100644 --- 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; -- cgit