diff options
author | Gordon Tetlow <gordon@FreeBSD.org> | 2023-12-01 03:41:44 +0000 |
---|---|---|
committer | Gordon Tetlow <gordon@FreeBSD.org> | 2023-12-01 03:41:44 +0000 |
commit | 3af841819564e98c70c908b2caad2f9af8039073 (patch) | |
tree | 2a8ea5662e023164e22dc0a7c9d4fdf11d3e3949 | |
parent | a847059f9ce13a81b8a0d2a46d0ad9dca6a9b335 (diff) | |
download | doc-3af8418195.tar.gz doc-3af8418195.zip |
Fix typo in the commit hash.
While we are at it, use the same hash from above for consistency.
-rw-r--r-- | documentation/content/en/articles/committers-guide/_index.adoc | 2 |
1 files changed, 1 insertions, 1 deletions
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. ==== |