[PATCH 0/2] doc: interpret-trailers: explain key format
- From
- kristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
- Date
- Mar 30, 2026, 21:11 UTC
- Message-ID
- <CV_doc_int-tr_key_format.533@msgid.xyz>
- In-Reply-To
- <CA+i-1C1DM0CHoFJ0A5CchQg=qDVLi_SSiZqcd0dxsay-Y94WTQ@mail.gmail.com>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Topic name: doc-int-tr-2-key-format
Topic summary: Explain the format of trailer keys (alphanum and hyphens). This is important to keep in mind so that metadata is not lost to simple syntax errors.
To facilitate this there is a first commit/patch to reorient the introduction towards discussing “key-value pairs”, since that makes it easier to follow up with an explanation of the *key* format.
§ Cc
Linus Arver as the author of the example that this change touches.
[1/2] doc: interpret-trailers: stop fixating on RFC 822 [2/2] doc: interpret-trailers: explain key format
Documentation/git-interpret-trailers.adoc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
base-commit: 5361983c075154725be47b65cca9a2421789e410
-- 2.53.0.32.gf6228eaf9cc