{"thread":{"id":"64400","subject":"[PATCH v2 resend v2] doc: git-checkout: fix placeholder markup","startedAt":"2025-10-28T18:19:33Z","lastAt":"2025-10-28T18:19:33Z","messageCount":1,"participants":["kristofferhaugsbakk@fastmail.com"],"isPatch":true,"patchVersion":2,"patchTotal":null},"messages":[{"id":"529807","messageId":"v2-cb38c701537.1761675472.git.code@khaugsbakk.name","threadId":"64400","inReplyTo":null,"subject":"[PATCH v2 resend v2] doc: git-checkout: fix placeholder markup","fromName":"","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-10-28T18:19:19Z","receivedAt":"2025-10-28T18:19:33Z","isPatch":true,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"From: Kristoffer Haugsbakk <code@khaugsbakk.name>\n\nThe placeholder markup is underscore (_), not backtick (`) as well.\n\nThe inline-verbatim markup (backticks) handle interior formatting. This\nmeans in this case that it applies HTML `<code>` to the underscores and\n`<em>` to the placeholder.\n\nThat is the effect, anyway; we can see from the rest of 042d6f34 (doc:\ngit-checkout: clarify `-b` and `-B`, 2025-09-10) that this was probably\nan unintended mix-up.\n\nAcked-by: Julia Evans <julia@jvns.ca>\nSigned-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>\n---\n\nNotes (series):\n    v2 resend:\n    Resend as a separate thread this time. v2 is here:\n    <v2-cb38c701537.1760716150.git.code@khaugsbakk.name>\n    \n    v2:\n    Add Ack.  I also considered removing “probably” from “mix-up” but\n    left it alone as a point-in-time note.  The msg + ack makes it clear.\n    \n    v1:\n    Since this has landed in `master` now.\n\n Documentation/git-checkout.adoc | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-checkout.adoc b/Documentation/git-checkout.adoc\nindex 431185ca0ba..6f281b298ef 100644\n--- a/Documentation/git-checkout.adoc\n+++ b/Documentation/git-checkout.adoc\n@@ -61,7 +61,7 @@ uncommitted changes.\n `git checkout -B <branch> [<start-point>]`::\n \n \tThe same as `-b`, except that if the branch already exists it\n-\tresets `_<branch>_` to the start point instead of failing.\n+\tresets _<branch>_ to the start point instead of failing.\n \n `git checkout --detach [<branch>]`::\n `git checkout [--detach] <commit>`::\n@@ -155,7 +155,7 @@ of it\").\n \n `-B <new-branch>`::\n \tThe same as `-b`, except that if the branch already exists it\n-\tresets `_<branch>_` to the start point instead of failing.\n+\tresets _<branch>_ to the start point instead of failing.\n \n `-t`::\n `--track[=(direct|inherit)]`::\n\nRange-diff against v1:\n1:  54bc6875cc5 ! 1:  cb38c701537 doc: git-checkout: fix placeholder markup\n    @@ Commit message\n         git-checkout: clarify `-b` and `-B`, 2025-09-10) that this was probably\n         an unintended mix-up.\n     \n    +    Acked-by: Julia Evans <julia@jvns.ca>\n         Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>\n     \n     \n      ## Notes (series) ##\n    +    v2 resend:\n    +    Resend as a separate thread this time. v2 is here:\n    +    <v2-cb38c701537.1760716150.git.code@khaugsbakk.name>\n    +\n    +    v2:\n    +    Add Ack.  I also considered removing “probably” from “mix-up” but\n    +    left it alone as a point-in-time note.  The msg + ack makes it clear.\n    +\n    +    v1:\n         Since this has landed in `master` now.\n     \n      ## Documentation/git-checkout.adoc ##\n\nbase-commit: 83a9405e59e9cdfb587b19c50f0c040f346dd4ea\n-- \n2.51.1.498.g8f0801f1c10\n\n"}]}