From: kristofferhaugsbakk@fastmail.com Date: Thu, 08 Jan 2026 06:28:16 GMT Subject: [PATCH 2/6] doc: patch-id: capitalize Git version Message-ID: In-Reply-To: From: Kristoffer Haugsbakk Git versions are always capitalized. Signed-off-by: Kristoffer Haugsbakk --- Documentation/git-patch-id.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-patch-id.adoc b/Documentation/git-patch-id.adoc index bac37db09d4..82992e35fc1 100644 --- a/Documentation/git-patch-id.adoc +++ b/Documentation/git-patch-id.adoc @@ -47,7 +47,7 @@ This is the default if `patchid.verbatim` is `true`. as a key to index some meta-information about the change between the two trees. -- Result is different from the value produced by git 1.9 and older +- Result is different from the value produced by Git 1.9 and older or produced when an "unstable" hash (see `--unstable` below) is configured - even when used on a diff output taken without any use of `-O`, thereby making existing databases storing such @@ -61,8 +61,8 @@ This is the default if `patchid.stable` is set to `true`. `--unstable`:: Use an "unstable" hash as the patch ID. With this option, the result produced is compatible with the patch-id value produced - by git 1.9 and older and whitespace is ignored. Users with pre-existing - databases storing patch-ids produced by git 1.9 and older (who do not deal + by Git 1.9 and older and whitespace is ignored. Users with pre-existing + databases storing patch-ids produced by Git 1.9 and older (who do not deal with reordered patches) may want to use this option. + This is the default. -- 2.52.0.421.gc32ead4fc78