doc: fix unmatched code fences in git-stripspace

The asciidoctor renderer is more picky than classic asciidoc, and insists that the start and end of a code fence be the same size. Found with this hacky perl script: foreach my $fn (@ARGV) { open(my $fh, '<', $fn); my ($fence, $fence_lineno, $prev); while (<$fh>) { chomp; if (/^----+$/) { if ($fence_lineno) { if ($_ ne $fence) { print "$fn:$fence_lineno:mismatched fence: ", length($fence), " != ", length($_), "\n"; } $fence_lineno = undef; } # hacky check to avoid title-underlining elsif ($prev eq '' || $prev eq '+') { $fence = $_; $fence_lineno = $.; } } $prev = $_; } } Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Jeff King committed May 12, 2015 at 22:15 UTC ad3967a5a2bc8a2505ba618e59cd541775571ff8
1 file changed +3 -3
Documentation/git-stripspace.txt
+3 -3
@@ -48,7 +48,7 @@ EXAMPLES
48
49 Given the following noisy input with '$' indicating the end of a line:
50
51 ---------
51 +---------
52 |A brief introduction $
53 | $
54 |$
@@ -64,7 +64,7 @@ Given the following noisy input with '$' indicating the end of a line:
64
65 Use 'git stripspace' with no arguments to obtain:
66
67 ---------
67 +---------
68 |A brief introduction$
69 |$
70 |A new paragraph$
@@ -78,7 +78,7 @@ Use 'git stripspace' with no arguments to obtain:
78
79 Use 'git stripspace --strip-comments' to obtain:
80
81 ---------
81 +---------
82 |A brief introduction$
83 |$
84 |A new paragraph$