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

[PATCH v2] doc: column: fix blank lines around block delimiters

From
Kkristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
Date
Jun 1, 2025, 11:36 UTC
Message-ID
<3c6d7b154048ef0053d15b4f86cc241211ef30dc.1748777208.git.code@khaugsbakk.name>
In-Reply-To
<b493b07f88bc5562e03c249006f01091afd7b5fd.1748725662.git.code@khaugsbakk.name>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>

227c4f33a03 (doc: add a blank line around block delimiters, 2025-03-09) added blank lines around block delimiters as a defensive measure. For each block you had to mind the con- text (like the commit says):

• Top-level: just add blank lines • Block: use list continuation (+)

But list continuation was used here at the top level, which results in literal `+` in the output formats.

Acked-by: Jean-Noël Avila <jn.avila@free.fr>
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Notes (series):
    v2:
    • Finally trying the “After the list reached a consensus” step of
      SubmittingPatches
    • Add Ack
    • Use “around” consistently in subject and message
 Documentation/git-column.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-column.adoc b/Documentation/git-column.adoc
index 5a4f2b6fde9..8e0047214dc 100644
--- a/Documentation/git-column.adoc
+++ b/Documentation/git-column.adoc
@@ -50,7 +50,7 @@ EXAMPLES
 --------
 
 Format data by columns:
-+
+
 ------------
 $ seq 1 24 | git column --mode=column --padding=5
 1      4      7      10     13     16     19     22
@@ -59,7 +59,7 @@ $ seq 1 24 | git column --mode=column --padding=5
 ------------
 
 Format data by rows:
-+
+
 ------------
 $ seq 1 21 | git column --mode=row --padding=5
 1      2      3      4      5      6      7
@@ -68,7 +68,7 @@ $ seq 1 21 | git column --mode=row --padding=5
 ------------
 
 List some tags in a table with unequal column widths:
-+
+
 ------------
 $ git tag --list 'v2.4.*' --column=row,dense
 v2.4.0  v2.4.0-rc0  v2.4.0-rc1  v2.4.0-rc2  v2.4.0-rc3

Range-diff against v1:
1:  b493b07f88b ! 1:  3c6d7b15404 doc: column: fix blank lines before block delimiters
    @@ Metadata
     Author: Kristoffer Haugsbakk <code@khaugsbakk.name>
     
      ## Commit message ##
    -    doc: column: fix blank lines before block delimiters
    +    doc: column: fix blank lines around block delimiters
     
         227c4f33a03 (doc: add a blank line around block delimiters,
         2025-03-09) added blank lines around block delimiters as a
    @@ Commit message
         But list continuation was used here at the top level, which
         results in literal `+` in the output formats.
     
    +    Acked-by: Jean-Noël Avila <jn.avila@free.fr>
         Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
     
      ## Documentation/git-column.adoc ##

base-commit: 7014b55638da979331baf8dc31c4e1d697cf2d67
-- 
2.50.0.rc0.47.g3c6d7b15404.dirty
Previous: Kristoffer Haugsbakk
Message 4 of 4 in “doc: column: fix blank lines before block delimiters”
  1. doc: column: fix blank lines before block delimiterskristofferhaugsbakk@fastmail.com, May 31, 2025
  2. Jean-Noël AVILAMay 31, 2025
  3. Kristoffer HaugsbakkMay 31, 2025
  4. doc: column: fix blank lines around block delimiterskristofferhaugsbakk@fastmail.com, Jun 1, 2025

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.