From: Junio C Hamano <gitster@pobox.com>
To: "Julia Evans" <julia@jvns.ca>
Cc: "Julia Evans" <gitgitgadget@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] doc: checkout: rewrite detached HEAD state explanation
Date: Mon, 19 Oct 2026 14:24:24 -0700 [thread overview]
Message-ID: <xmqqcxt52xkn.fsf@gitster.g> (raw)
In-Reply-To: <9c15d34e-406d-4702-b606-da102a340e71@app.fastmail.com> (Julia Evans's message of "Mon, 19 Oct 2026 10:05:58 -0400")
"Julia Evans" <julia@jvns.ca> writes:
> Let me know if this is a helpful way for you to bring some user perspectives
> into the conversation. Like I said earlier I don't really think it's possible to
> discuss how to explain HEAD in a vacuum so maybe these quotes will help!
It surely is more helpful than "I think it is not better" that is
not backed by anything.
> Also if you could give me any ideas for how to reply in a "shorter" way than
> "I don't think this is clearer" let me know, I can't bring you quotes from user
> research to justify every single wording choice :)
IOW, "Trust me" ;-)
It is often good enough among those who have worked together for
some time, and you certainly do qualify.
> - "HEAD is a mysterious thing I never need to know about unless something has
> g-one wrong, eg. merge conflicts."
Somebody may have said so, but how does bringing it (together with
many other examples) up in _this_ discussion help us find a better
way to explain it to users?
Somebody is clueless about HEAD and does not feel the need to
understand it until they really need to. This fact alone, that they
can get going with such a sketchy understanding and make use of Git
sufficiently well may be a great thing by itself. It may support an
argument that we do not really have to explain what HEAD is to our
readers. Is that the argument you are making?
I won't comment on each and every one of them, but is your point
that many potential readers do not understand HEAD and doing fine?
Of course there are a handful of examples that they do get it, like
this one.
> - "HEAD is a reference to a commit, either directly or indirectly. A direct
> commit is just in detached state, where HEAD is looking at the commit itself.
> An indirect reference would be the case you’ve shown above, where HEAD is a
> reference to a reference."
But what did you want to illustrate again? I am little bit fuzzy on
what you wanted to achieve by dumping these at me.
Thanks.
next prev parent reply other threads:[~2026-10-19 21:24 UTC|newest]
Thread overview: 24+ 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 [this message]
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-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=xmqqcxt52xkn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--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.