From: Junio C Hamano <gitster@pobox.com>
To: "Julia Evans via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
"D. Ben Knoble" <ben.knoble@gmail.com>,
Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH v5] doc: checkout: rewrite detached HEAD state explanation
Date: Wed, 11 Nov 2026 20:08:09 -0800 [thread overview]
Message-ID: <xmqqmrrelmja.fsf@gitster.g> (raw)
In-Reply-To: <xmqqqzgrklkh.fsf@gitster.g> (Junio C. Hamano's message of "Wed, 11 Nov 2026 15:14:22 -0800")
Junio C Hamano <gitster@pobox.com> writes:
>
>> diff --git a/advice.c b/advice.c
>> index 401d047391..8d2c1ff1ee 100644
>> --- a/advice.c
>> +++ b/advice.c
>> @@ -291,6 +291,7 @@ void detach_advice(const char *new_name)
>> "\n"
>> " git switch -\n"
>> "\n"
>> + "Run `git help detached-head` to learn more.\n"
>
> Shouldn't we be using a normal single quote instead of backtick?
>
> Existing references to command in this file has the command without
> quotes, on its own line "\tgit merge --no-ff\n", or uses a normal
> single quote as in "... use 'git add/rm <file>'".
>
> People's terminals do not grok markdown anyway ;-)
One more thing.
This change needs to update t/t2020-checkout-detach.sh because the
new output is not expected there (yet).
next prev parent reply other threads:[~2026-11-12 4:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 14:52 [PATCH] doc: checkout: rewrite detached HEAD state explanation Julia Evans via GitGitGadget
2026-10-07 16:43 ` Junio C Hamano
2026-10-13 12:54 ` Julia Evans
2026-10-19 14:05 ` Julia Evans
2026-10-19 21:24 ` Junio C Hamano
2026-10-20 12:52 ` Julia Evans
2026-10-20 13:06 ` Julia Evans
2026-10-07 19:02 ` Kristoffer Haugsbakk
2026-10-13 11:48 ` Julia Evans
2026-10-13 12:20 ` Kristoffer Haugsbakk
2026-10-13 12:27 ` Julia Evans
2026-10-13 12:42 ` Julia Evans
2026-10-13 13:01 ` [PATCH v2] " Julia Evans via GitGitGadget
2026-10-14 18:52 ` Junio C Hamano
2026-10-14 21:10 ` Julia Evans
2026-10-15 20:58 ` [PATCH v3] " Julia Evans via GitGitGadget
2026-10-15 22:39 ` Junio C Hamano
2026-10-16 14:55 ` Julia Evans
2026-10-16 17:03 ` Junio C Hamano
2026-10-16 18:35 ` Julia Evans
2026-10-16 19:05 ` Junio C Hamano
2026-10-16 19:03 ` [PATCH v4] " Julia Evans via GitGitGadget
2026-10-16 21:10 ` Junio C Hamano
2026-11-07 20:06 ` D. Ben Knoble
2026-11-08 4:25 ` Junio C Hamano
2026-11-09 21:48 ` Julia Evans
2026-11-10 6:46 ` Junio C Hamano
2026-11-10 13:13 ` Julia Evans
2026-11-11 21:45 ` Julia Evans
2026-11-12 1:58 ` Ben Knoble
2026-11-12 15:40 ` Junio C Hamano
2026-11-12 16:37 ` Julia Evans
2026-11-12 19:25 ` Junio C Hamano
2026-11-12 22:45 ` Julia Evans
2026-10-16 22:02 ` Junio C Hamano
2026-11-11 21:34 ` [PATCH v5] " Julia Evans via GitGitGadget
2026-11-11 23:14 ` Junio C Hamano
2026-11-12 0:01 ` Julia Evans
2026-11-12 4:08 ` Junio C Hamano [this message]
2026-11-12 22:47 ` [PATCH v6] " Julia Evans via GitGitGadget
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=xmqqmrrelmja.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=julia@jvns.ca \
--cc=kristofferhaugsbakk@fastmail.com \
/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.