git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/3] config.txt: perform some minor reformatting

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 14, 2024, 01:58 UTC
Message-ID
<xmqqedcd1sm5.fsf@gitster.g>
In-Reply-To
<d50c0f22c41ec36b574e1ff67e68485d9a6f2a84.1710258538.git.dsimic@manjaro.org>
Dragan Simic <dsimic@manjaro.org> writes:
> Reformat a few lines a bit, to utilize the available horizontal space better.
> There are no changes to the actual contents of the documentation.

I was a bit surprised to see such a "preliminary clean-up" step to come before the main change, not after, but separating this from the change to the next paragraph, which is the main change in this series, is nevertheless a very good idea.

Show 27 quoted lines
>
> Signed-off-by: Dragan Simic <dsimic@manjaro.org>
> ---
>  Documentation/config.txt | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index 4480bb44203b..2fc4a52d8d76 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -58,11 +58,11 @@ compared case sensitively. These subsection names follow the same
>  restrictions as section names.
>  
>  All the other lines (and the remainder of the line after the section
> -header) are recognized as setting variables, in the form
> -'name = value' (or just 'name', which is a short-hand to say that
> -the variable is the boolean "true").
> -The variable names are case-insensitive, allow only alphanumeric characters
> -and `-`, and must start with an alphabetic character.
> +header) are recognized as setting variables, in the form 'name = value'
> +(or just 'name', which is a short-hand to say that the variable is the
> +boolean "true").  The variable names are case-insensitive, allow only
> +alphanumeric characters and `-`, and must start with an alphabetic
> +character.
>  
>  A line that defines a value can be continued to the next line by
>  ending it with a `\`; the backslash and the end-of-line are stripped.
Previous: Dragan SimicNext: Dragan Simic
Message 3 of 14 in “Improve the documentation and test coverage for whitespace and comments”
  1. 0/3 Improve the documentation and test coverage for whitespace and commentsDragan Simic, Mar 12, 2024
  2. 2/3 config.txt: perform some minor reformattingDragan Simic, Mar 12, 2024
  3. Junio C HamanoMar 14, 2024
  4. Dragan SimicMar 14, 2024
  5. Junio C HamanoMar 14, 2024
  6. Dragan SimicMar 14, 2024
  7. 1/3 config.txt: describe whitespace characters further and more accuratelyDragan Simic, Mar 12, 2024
  8. Junio C HamanoMar 14, 2024
  9. Dragan SimicMar 14, 2024
  10. Junio C HamanoMar 14, 2024
  11. Dragan SimicMar 14, 2024
  12. 3/3 t1300: add tests for internal whitespace and inline commentsDragan Simic, Mar 12, 2024
  13. Junio C HamanoMar 14, 2024
  14. Dragan SimicMar 14, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.