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>,
Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH v4] doc: checkout: rewrite detached HEAD state explanation
Date: Fri, 16 Oct 2026 14:10:47 -0700 [thread overview]
Message-ID: <xmqqh5ile4h4.fsf@gitster.g> (raw)
In-Reply-To: <pull.2250.v4.git.1792177409868.gitgitgadget@gmail.com> (Julia Evans via GitGitGadget's message of "Fri, 16 Oct 2026 19:03:29 +0000")
"Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:
> This is a pretty quick rewrite where we didn't get any user feedback. If
> we really want to make sure it's clear to users as possible, we should
> IMO do a second stage later where we ask users which parts are unclear.
OK.
> * It's probably possible to explain HEAD better. That seems like a big
> project to me since HEAD in Git is a very tricky topic. I think it
> would be better to address in a separate patch series to have more
> time to think it through. Or if we think it's not possible to merge
> this without explaining HEAD better then I guess it shouldn't be
> merged.
I do not understand why you need to draw a "take it or leave it"
with this topic here. If you feel that the explanation of HEAD is
iffy, you know what we have here will not be the final version, and
you think we lack the capacity to reach the best possible
description with the usual review exchange, then I do not see why
you have to insist keeping what you initially have written. You can
replace it with anything that is better than your initial version
and then still record that we will further polish it later in the
proposed log message and we will be in a better place, no?
Just to leave a record, so that we have better chance remembering
the suggested improved text, here are what I think the first two
paragraphs should be replaced with.
HEAD records the state from which your current changes started.
This can be a branch (the "current branch"), or it be a commit,
(in which case HEAD is "detached").
In the detached HEAD state, you can safely build, run, and
experiment with any historical version of your codebase, without
having to worry about clobbering your branches, and you do not
have to clutter your repository with temporary branches.
Having said all that, the changes between v3 and v4 look OK to me,
so let me update the previous copy I have with this version.
next prev parent reply other threads:[~2026-10-16 21:10 UTC|newest]
Thread overview: 20+ 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-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 [this message]
2026-10-16 22:02 ` Junio C Hamano
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=xmqqh5ile4h4.fsf@gitster.g \
--to=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox