From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: kh/doc-trailers
Date: Thu, 30 Jul 2026 11:23:33 +0200 [thread overview]
Message-ID: <2d1d5f4c-2f5a-4bf2-af82-fa215db96ff2@app.fastmail.com> (raw)
In-Reply-To: <xmqqzez9obr0.fsf@gitster.g>
On Wed, Jul 29, 2026, at 21:07, Junio C Hamano wrote:
> * kh/doc-trailers (2026-06-10) 10 commits
> - doc: interpret-trailers: document comment line treatment
> - doc: interpret-trailers: commit to “trailer block” term
> - doc: interpret-trailers: join new-trailers again
> - doc: interpret-trailers: add key format example
> - doc: interpret-trailers: explain key format
> - doc: interpret-trailers: explain the format after the intro
> - doc: interpret-trailers: not just for commit messages
> - doc: interpret-trailers: use “metadata” in Name as well
> - doc: interpret-trailers: replace “lines” with “metadata”
> - doc: interpret-trailers: stop fixating on RFC 822
>
> Documentation for 'git interpret-trailers' has been updated to explain
> the format of trailer keys (alphanumeric characters and hyphens),
> replace outdated terminology, define key terms upfront, and document
> how comment lines in the input are treated.
>
> Will discard.
> cf. <xmqq1pedthkv.fsf@gitster.g>
> source: <V3_CV_doc_int-tr_key_format.8a3@msgid.xyz>
I’ve posted the next version now.
<V4_CV_doc_int-tr_key_format.ae2@msgid.xyz>
next prev parent reply other threads:[~2026-07-30 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 19:07 What's cooking in git.git (Jul 2026, #13) Junio C Hamano
2026-07-30 9:23 ` Kristoffer Haugsbakk [this message]
2026-07-30 10:00 ` kh/doc-replay-config Kristoffer Haugsbakk
-- strict thread matches above, loose matches on Subject: below --
2026-08-21 1:29 What's cooking in git.git (Aug 2026, #09) Junio C Hamano
2026-08-21 9:09 ` kh/doc-trailers Kristoffer Haugsbakk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d1d5f4c-2f5a-4bf2-af82-fa215db96ff2@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.