From: Julia Evans Date: Tue, 20 Oct 2026 12:52:25 GMT Subject: Re: [PATCH] doc: checkout: rewrite detached HEAD state explanation Message-ID: <1AA9F133-4B0C-4AAC-B296-5C2543C642F2@jvns.ca> In-Reply-To: > On Oct 19, 2026, at 5:24 PM, Junio C Hamano wrote: > > "Julia Evans" 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. That’s good to hear! >> - "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? I do think that’s true yes. > 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. Mostly to give an idea of the kind of language users are using when talking about Git, to explain why saying “records” isn’t appropriate and why more generally it might not be possible for me to accept your suggested wordings for how to explain things verbatim. For example elsewhere in this thread you suggested another wording and seemed to find it hard to understand why I wouldn't replace what Marie and I had written with your suggested “better” wording. Also I have the impression that our assumptions about what Git users know and what users need are quite different, and I thought it might help illustrate why I might have a different point of view. I agree these kinds of comments can be a little unsettling to read when some of them are “wrong”. I believe that these comments are from folks who are quite a bit more knowledgeable than the average Git user. It’s my job to sort through them and figure out how to write the docs with them in mind and I’m definitely not asking you to do that :) I do need some trust though.