git: 3af8418195 - main - Fix typo in the commit hash.

From: Gordon Tetlow <>
Date: Fri, 01 Dec 2023 03:42:22 UTC
The branch main has been updated by gordon:


commit 3af841819564e98c70c908b2caad2f9af8039073
Author:     Gordon Tetlow <>
AuthorDate: 2023-12-01 03:41:44 +0000
Commit:     Gordon Tetlow <>
CommitDate: 2023-12-01 03:41:44 +0000

    Fix typo in the commit hash.
    While we are at it, use the same hash from above for consistency.
 documentation/content/en/articles/committers-guide/_index.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
index 667e635bd2..6caa7d6bf4 100644
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -609,7 +609,7 @@ a8163e165c5b (upstream/main) HEAD@{1}: checkout: moving from b6fb97efb682994f59b
 shows me moving the working tree to the `main` branch (a816...) and then updating from upstream (to 5ef0...).
-In this case, bad would be HEAD (or 5rf0bd68) and good would be a8163e165.
+In this case, bad would be HEAD (or 5ef0bd68b515) and good would be a8163e165c5b.
 As you can see from the output, HEAD@{1} also often works, but isn't foolproof if you have done other things to your Git tree after updating, but before you discover the need to bisect.