From: Patrick Steinhardt <ps@pks.im>
To: kristofferhaugsbakk@fastmail.com
Cc: git@vger.kernel.org, Kristoffer Haugsbakk <code@khaugsbakk.name>,
Pushkar Singh <pushkarkumarsingh1970@gmail.com>
Subject: Re: [PATCH v2 0/6] doc: patch-id: six small improvements
Date: Fri, 9 Jan 2026 15:55:05 +0100 [thread overview]
Message-ID: <aWEWydo-P5m0D5xR@pks.im> (raw)
In-Reply-To: <V2_CV_doc_patch-id_3.1b2@msgid.xyz>
On Fri, Jan 09, 2026 at 03:25:56PM +0100, kristofferhaugsbakk@fastmail.com wrote:
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> Topic name: kh/doc-patch-id-3
>
> Topic summary: Improvements to git-patch-id(1). Fix git-diff-tree(1)
> mention, Fix '--verbatim' documentation, and four other small
> improvements.
>
> This is the third patch series for git-patch-id(1). This one only has
> small improvements.
>
> • Patch series 1:
> • Topic: kh/doc-patch-id-markup-fix
> • https://lore.kernel.org/git/v2-e5ad12cc3b3.1759178715.git.code@khaugsbakk.name/
> • Patch series 2:
> • Topic: kh/doc-patch-id-1
> • https://lore.kernel.org/git/v2-38645ea253c.1760369708.git.code@khaugsbakk.name/
>
> § Changtes in v2
>
> Fix markup in commit message.
This version looks good to me based on the range-diff, thanks!
Patrick
prev parent reply other threads:[~2026-01-09 14:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 6:28 [PATCH 0/6] doc: patch-id: six small improvements kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 1/6] doc: patch-id: don’t use semicolon between bullet points kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 2/6] doc: patch-id: capitalize Git version kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 3/6] patch-id: use “patch ID” throughout kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 4/6] doc: patch-id: use definite article for the result kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 5/6] doc: patch-id: spell out the git-diff-tree(1) form kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 6/6] doc: patch-id: --verbatim locks in --stable kristofferhaugsbakk
2026-01-08 18:15 ` Pushkar Singh
2026-01-08 18:18 ` Kristoffer Haugsbakk
2026-01-08 18:26 ` Kristoffer Haugsbakk
2026-01-09 11:38 ` [PATCH 0/6] doc: patch-id: six small improvements Patrick Steinhardt
2026-01-09 11:45 ` Kristoffer Haugsbakk
2026-01-09 14:25 ` [PATCH v2 " kristofferhaugsbakk
2026-01-09 14:25 ` [PATCH v2 1/6] doc: patch-id: don’t use semicolon between bullet points kristofferhaugsbakk
2026-01-09 14:25 ` [PATCH v2 2/6] doc: patch-id: capitalize Git version kristofferhaugsbakk
2026-01-09 14:25 ` [PATCH v2 3/6] patch-id: use “patch ID” throughout kristofferhaugsbakk
2026-01-09 14:26 ` [PATCH v2 4/6] doc: patch-id: use definite article for the result kristofferhaugsbakk
2026-01-09 14:26 ` [PATCH v2 5/6] doc: patch-id: spell out the git-diff-tree(1) form kristofferhaugsbakk
2026-01-09 14:26 ` [PATCH v2 6/6] doc: patch-id: --verbatim locks in --stable kristofferhaugsbakk
2026-01-09 14:55 ` Patrick Steinhardt [this message]
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=aWEWydo-P5m0D5xR@pks.im \
--to=ps@pks.im \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=pushkarkumarsingh1970@gmail.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.