From: kristofferhaugsbakk@fastmail.com
To: kristofferhaugsbakk@fastmail.com, git@vger.kernel.org
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>,
ben.knoble@gmail.com, julia@jvns.ca
Subject: [PATCH v2 resend v2] doc: git-checkout: fix placeholder markup
Date: Tue, 28 Oct 2025 19:19:19 +0100 [thread overview]
Message-ID: <v2-cb38c701537.1761675472.git.code@khaugsbakk.name> (raw)
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
The placeholder markup is underscore (_), not backtick (`) as well.
The inline-verbatim markup (backticks) handle interior formatting. This
means in this case that it applies HTML `<code>` to the underscores and
`<em>` to the placeholder.
That is the effect, anyway; we can see from the rest of 042d6f34 (doc:
git-checkout: clarify `-b` and `-B`, 2025-09-10) that this was probably
an unintended mix-up.
Acked-by: Julia Evans <julia@jvns.ca>
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Notes (series):
v2 resend:
Resend as a separate thread this time. v2 is here:
<v2-cb38c701537.1760716150.git.code@khaugsbakk.name>
v2:
Add Ack. I also considered removing “probably” from “mix-up” but
left it alone as a point-in-time note. The msg + ack makes it clear.
v1:
Since this has landed in `master` now.
Documentation/git-checkout.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-checkout.adoc b/Documentation/git-checkout.adoc
index 431185ca0ba..6f281b298ef 100644
--- a/Documentation/git-checkout.adoc
+++ b/Documentation/git-checkout.adoc
@@ -61,7 +61,7 @@ uncommitted changes.
`git checkout -B <branch> [<start-point>]`::
The same as `-b`, except that if the branch already exists it
- resets `_<branch>_` to the start point instead of failing.
+ resets _<branch>_ to the start point instead of failing.
`git checkout --detach [<branch>]`::
`git checkout [--detach] <commit>`::
@@ -155,7 +155,7 @@ of it").
`-B <new-branch>`::
The same as `-b`, except that if the branch already exists it
- resets `_<branch>_` to the start point instead of failing.
+ resets _<branch>_ to the start point instead of failing.
`-t`::
`--track[=(direct|inherit)]`::
Range-diff against v1:
1: 54bc6875cc5 ! 1: cb38c701537 doc: git-checkout: fix placeholder markup
@@ Commit message
git-checkout: clarify `-b` and `-B`, 2025-09-10) that this was probably
an unintended mix-up.
+ Acked-by: Julia Evans <julia@jvns.ca>
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
## Notes (series) ##
+ v2 resend:
+ Resend as a separate thread this time. v2 is here:
+ <v2-cb38c701537.1760716150.git.code@khaugsbakk.name>
+
+ v2:
+ Add Ack. I also considered removing “probably” from “mix-up” but
+ left it alone as a point-in-time note. The msg + ack makes it clear.
+
+ v1:
Since this has landed in `master` now.
## Documentation/git-checkout.adoc ##
base-commit: 83a9405e59e9cdfb587b19c50f0c040f346dd4ea
--
2.51.1.498.g8f0801f1c10
reply other threads:[~2025-10-28 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=v2-cb38c701537.1761675472.git.code@khaugsbakk.name \
--to=kristofferhaugsbakk@fastmail.com \
--cc=ben.knoble@gmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=julia@jvns.ca \
/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.