Thread (32 messages) 32 messages, 3 authors, 11h ago

Re: [PATCH v2 1/5] SubmittingPatches: encourage trailer use for substantial help

From: Kristoffer Haugsbakk <hidden>
Date: 2026-06-18 12:21:50

On Wed, Jun 17, 2026, at 23:41, Junio C Hamano wrote:
kristofferhaugsbakk@fastmail.com writes:
quoted
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 176567738d4..0b12badf86d 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -443,8 +443,16 @@ identifying, and not misleading.
 The goal of this policy is to allow us to have sufficient information to contact
 you if questions arise about your contribution.

+=== Commit trailers
 [[commit-trailers]]
-If you like, you can put extra trailers at the end:
I think majority of AsciiDoc files in this project places [[anchor]]
before the "=== title" of a section.  For example, here is how the
patch flow section begins in SubmittingPatches:

    [[patch-flow]]
    === A typical life cycle of a patch series

    To help us understand the reason behind various guidelines given later
    in the document, first let's understand how the life cycle of a
    typical patch series for this project goes.

I do not offhand know which way is kosher, but we should be
consistent either way.
Your suspicion is correct. Skimming this I cannot seem to find any
examples where the anchor goes after the title.

    git grep --extended-regexp -C1 '^\[\[' -- 'Documentation/*adoc'

I’ll fix it.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help