Subject: [PATCH] Documentation/config.txt: a variable can be defined on the section header line Signed-off-by: Nanako Shiraishi <nanako3@xxxxxxxxxxx> --- Quoting Junio C Hamano <gitster@xxxxxxxxx>: > Nanako Shiraishi <nanako3@xxxxxxxxxxx> writes: > >> Isn't this a syntax error? >> >> Documentation/config.txt says this. > > Even if it were, I think it would be nice to allow it. I'll have to > re-read Alex's patch, but I thought it was sane. Perhaps we can update > the documentation, mildly hinting that it is allowed without encouraging > it too strongly, as I think it is a good style to have these on separate > lines. How about this small update to the documentation, then? Documentation/config.txt | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index 6857d2f..c6f09f8 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -49,7 +49,8 @@ There is also a case insensitive alternative `[section.subsection]` syntax. In this syntax, subsection names follow the same restrictions as for section names. -All the other lines are recognized as setting variables, in the form +All the other lines (and the remainder of the line after the section +header) are recognized as setting variables, in the form 'name = value'. If there is no equal sign on the line, the entire line is taken as 'name' and the variable is recognized as boolean "true". The variable names are case-insensitive and only alphanumeric -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html