[PATCH v3 1/3] doc: config: terminate runaway lists

There are many places in git-config(1) where paragraphs that should logically come after a list are instead appended to the last item of the list. This is a well-documented quirk of AsciiDoc, and can be mitigated by enclosing the list in an open block:

	--
	* first item
	* last item
	--
	+
	New paragraph after the list.

Fix the issue accordingly.

Signed-off-by: Tuomas Ahola <taahol@utu.fi>
---

Notes (doc-diff):
    diff --git a/29bd7ed5127255713c1ac2f43b7c6f257d7b4594/home/taahol/share/man/man1/git-config.1 b/c9131b23fd1c8611fde5664fcfd4e6d5283648ad/home/taahol/share/man/man1/git-config.1
    index 326782e637..d915897ca5 100644
    --- a/29bd7ed5127255713c1ac2f43b7c6f257d7b4594/home/taahol/share/man/man1/git-config.1
    +++ b/c9131b23fd1c8611fde5664fcfd4e6d5283648ad/home/taahol/share/man/man1/git-config.1
    @@ -234,10 +234,10 @@ OPTIONS
                    sanity-check is performed to ensure that the given value is
                    canonicalize-able as an ANSI color, but it is written as-is.
    
    -               If the command is in list mode, then the --type <type> argument
    -               will apply to each listed config value. If the value does not
    -               successfully parse in that format, then it will be omitted from
    -               the list.
    +           If the command is in list mode, then the --type <type> argument
    +           will apply to each listed config value. If the value does not
    +           successfully parse in that format, then it will be omitted from the
    +           list.
    
            --bool, --int, --bool-or-int, --path, --expiry-date
                Historical options for selecting a type specifier. Prefer instead
    @@ -841,9 +841,9 @@ CONFIGURATION FILE
                    Boolean false literals are no, off, false, 0 and the empty
                    string.
    
    -               When converting a value to its canonical form using the
    -               --type=bool type specifier, git config will ensure that the
    -               output is "true" or "false" (spelled in lowercase).
    +           When converting a value to its canonical form using the --type=bool
    +           type specifier, git config will ensure that the output is "true" or
    +           "false" (spelled in lowercase).
    
            integer
                The value for many variables that specify various sizes can be
    @@ -5869,28 +5869,26 @@ CONFIGURATION FILE
                    exactly match the value advertised by the server for the
                    "token" field.
    
    -               If any of these conditions is not met for any field name listed
    -               in promisor.checkFields, the advertised remote "foo" is
    -               rejected.
    +           If any of these conditions is not met for any field name listed in
    +           promisor.checkFields, the advertised remote "foo" is rejected.
    
    -               For the "partialCloneFilter" field, this allows the client to
    -               ensure that the server’s filter matches what it expects
    -               locally, preventing inconsistencies in filtering behavior. For
    -               the "token" field, this can be used to verify that
    -               authentication credentials match expected values.
    +           For the "partialCloneFilter" field, this allows the client to
    +           ensure that the server’s filter matches what it expects locally,
    +           preventing inconsistencies in filtering behavior. For the "token"
    +           field, this can be used to verify that authentication credentials
    +           match expected values.
    
    -               Field values are compared case-sensitively.
    +           Field values are compared case-sensitively.
    
    -               The "name" and "url" fields are always checked according to the
    -               promisor.acceptFromServer policy, independently of this
    -               setting.
    +           The "name" and "url" fields are always checked according to the
    +           promisor.acceptFromServer policy, independently of this setting.
    
    -               The field names and values should be passed by the server
    -               through the "promisor-remote" capability by using the
    -               promisor.sendFields config variable. The fields are checked
    -               only if the promisor.acceptFromServer config variable is not
    -               set to "None". If set to "None", this config variable has no
    -               effect. See gitprotocol-v2(5).
    +           The field names and values should be passed by the server through
    +           the "promisor-remote" capability by using the promisor.sendFields
    +           config variable. The fields are checked only if the
    +           promisor.acceptFromServer config variable is not set to "None". If
    +           set to "None", this config variable has no effect. See gitprotocol-
    +           v2(5).
    
            promisor.storeFields
                A comma or space separated list of additional remote related field
    @@ -6630,15 +6628,15 @@ CONFIGURATION FILE
                    the top-level --git-dir command-line option, or the GIT_DIR
                    environment variable (see git(1)).
    
    -               If you do not use bare repositories in your workflow, then it
    -               may be beneficial to set safe.bareRepository to explicit in
    -               your global config. This will protect you from attacks that
    -               involve cloning a repository that contains a bare repository
    -               and running a Git command within that directory.
    +           If you do not use bare repositories in your workflow, then it may
    +           be beneficial to set safe.bareRepository to explicit in your global
    +           config. This will protect you from attacks that involve cloning a
    +           repository that contains a bare repository and running a Git
    +           command within that directory.
    
    -               This config setting is only respected in protected
    -               configuration (see the section called “SCOPES”). This prevents
    -               untrusted repositories from tampering with this value.
    +           This config setting is only respected in protected configuration
    +           (see the section called “SCOPES”). This prevents untrusted
    +           repositories from tampering with this value.
    
            safe.directory
                These config entries specify Git-tracked directories that are

 Documentation/config.adoc          | 4 +++-
 Documentation/config/promisor.adoc | 2 ++
 Documentation/config/safe.adoc     | 2 ++
 Documentation/git-config.adoc      | 2 ++
 4 files changed, 9 insertions(+), 1 deletion(-)