doc: patch-id: fix accidental literal blocks

All the final paragraphs on these three options are rendered as
literal blocks. The intent was surely to keep each of them wed to their
respective description list items. But the attempt at maintaining the
indentation level of the block causes each them to be interpreted as a
code block, since code blocks can be represented using indentation.

We need to use list continuation (+) in order to keep them wed to
their blocks.

There is also an unordered list which sandwiches two paragraphs on an
option. We don’t need to do anything about that since it attaches to the
description list item without list continuation (i.e. it is already
correct). But for consistency let’s use list continuation and an open
block on it.

Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

diff --git a/Documentation/git-patch-id.adoc b/Documentation/git-patch-id.adoc
index 1d15fa45d5126f236de4018268725c627c993fe2..45da0f27acde47f23b60af77b4a251d30ea9acba 100644 (file)
--- a/Documentation/git-patch-id.adoc
+++ b/Documentation/git-patch-id.adoc
@@ -33,27 +33,30 @@ OPTIONS
 --verbatim::
        Calculate the patch-id of the input as it is given, do not strip
        any whitespace.
-
-       This is the default if patchid.verbatim is true.
++
+This is the default if patchid.verbatim is true.
 
 --stable::
        Use a "stable" sum of hashes as the patch ID. With this option:
-        - Reordering file diffs that make up a patch does not affect the ID.
-          In particular, two patches produced by comparing the same two trees
-          with two different settings for "-O<orderfile>" result in the same
-          patch ID signature, thereby allowing the computed result to be used
-          as a key to index some meta-information about the change between
-          the two trees;
-
-        - Result is different from the value produced by git 1.9 and older
-          or produced when an "unstable" hash (see --unstable below) is
-          configured - even when used on a diff output taken without any use
-          of "-O<orderfile>", thereby making existing databases storing such
-          "unstable" or historical patch-ids unusable.
-
-        - All whitespace within the patch is ignored and does not affect the id.
-
-       This is the default if patchid.stable is set to true.
++
+--
+- Reordering file diffs that make up a patch does not affect the ID.
+  In particular, two patches produced by comparing the same two trees
+  with two different settings for "-O<orderfile>" result in the same
+  patch ID signature, thereby allowing the computed result to be used
+  as a key to index some meta-information about the change between
+  the two trees;
+
+- Result is different from the value produced by git 1.9 and older
+  or produced when an "unstable" hash (see --unstable below) is
+  configured - even when used on a diff output taken without any use
+  of "-O<orderfile>", thereby making existing databases storing such
+  "unstable" or historical patch-ids unusable.
+
+- All whitespace within the patch is ignored and does not affect the id.
+--
++
+This is the default if patchid.stable is set to true.
 
 --unstable::
        Use an "unstable" hash as the patch ID. With this option,
@@ -61,8 +64,8 @@ OPTIONS
        by git 1.9 and older and whitespace is ignored.  Users with pre-existing
        databases storing patch-ids produced by git 1.9 and older (who do not deal
        with reordered patches) may want to use this option.
-
-       This is the default.
++
+This is the default.
 
 GIT
 ---