Git development
 help / color / mirror / Atom feed
From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: kh/doc-trailers
Date: Fri, 21 Aug 2026 11:09:25 +0200	[thread overview]
Message-ID: <76e81149-4aff-47cf-8ae7-1e781ec2a228@app.fastmail.com> (raw)
In-Reply-To: <xmqq5x14tg5t.fsf@gitster.g>

On Fri, Aug 21, 2026, at 03:29, Junio C Hamano wrote:
> * kh/doc-trailers (2026-08-09) 11 commits
>   (merged to 'next' on 2026-08-13 at 2966f0265a)
>  + doc: interpret-trailers: document comment line treatment
>  + doc: interpret-trailers: rewrite new-trailers paragraphs
>  + 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
>  (this branch is used by kh/trailers-no-urls.)
>
>  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.

Thanks for improving the topic summary by the way. I feel like after I
added more changes on top of explaining the trailer keys format, it just
got bunched into “Also replace some terms [and a bunch of stuff]”... ;)

>
>  Graduated to 'master'.
>  cf. <0687D60D-DF6B-4547-868C-FCFC5B27ECAF@gmail.com>
>  source: <V5_CV_doc_int-tr_key_format.b26@msgid.xyz>

Kris

  reply	other threads:[~2026-08-21  9:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  1:29 What's cooking in git.git (Aug 2026, #09) Junio C Hamano
2026-08-21  9:09 ` Kristoffer Haugsbakk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-29 19:07 What's cooking in git.git (Jul 2026, #13) Junio C Hamano
2026-07-30  9:23 ` 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=76e81149-4aff-47cf-8ae7-1e781ec2a228@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox