git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v4] doc: checkout: rewrite detached HEAD state explanation

From
Julia Evans <julia@jvns.ca>
Date
Nov 12, 2026, 16:37 UTC
Message-ID
<931a94e4-feab-49a9-b5c6-479f0d7f8b75@jvns.ca>
In-Reply-To
<xmqq5wy2kqhl.fsf@gitster.g>
On 2026-11-12 10:40 a.m., Junio C Hamano wrote:
Show 24 quoted lines
> Julia Evans <julia@jvns.ca> writes:
>
>> Yeah I agree the "it's the parent of the next commit" would be
>> distracting unless there's a specific reason we need to include it.
>>
>> I agree "the state from which your current changes started" isn't right
>> but I think if we reinterpret it as "the current commit you have checked
>> out" (which I think has the same or a very similar meaning) then it'll
>> seem familiar to folks and might even help.
>> ...
>> because I couldn't think of a reason why someone would clobber an
>> existing branch to check out an old version of their code.
> When I find something interesting in a topic, which may be an old
> commit from the point of view of 'seen', I would detach HEAD at the
> tip of the branch to take a look at its contents, because what I am
> going to do next would very often involve modifying the working tree
> files to experiment.  Even a topic that is documentation only, like
> the je/doc-detached-head topic, can have a cascading effect that
> ends up breaking tests, for example, and I'd be futzing with the
> sources and tests to figure out what the best fix would be.  Even
> though I am not going to make any permanent commits out of these
> efforts, being able to make temporary commits to mark a resumable
> state is handy, and when my spelunking gets longer, I do make such
> commits.
Thanks, this is helpful, it makes sense now why this would be useful to you as the Git maintainer with what I've learned about your workflow.
Show 5 quoted lines
> I guess it requires a developer's mindset and imagination to
> appreciate why detached HEAD is useful while spelunking.  We often
> phrase the act of visiting random commits (often older ones) as
> "sight-seeing", but in reality, even when you are mostly looking,
> you do want to futz with things you see there.
I'm not sure what you mean by "it requires a developer's mindset", in my time working as a developer using Git I never ran into a case where I would have needed to clobber a branch in this way :)
It's important to remember that different Git users can have very different workflows (especially among developers, I think!) and that one person's workflow may not generalize well to other developers.
This is something I pay a lot of attention to in my own work: some parts of my own personal workflow are a bit unusual and I keep a mental catalog of those things to avoid giving them as advice.
> It is in a developer's heart ;-).
>
> Hope this clarifies.
Previous: Junio C HamanoNext: Junio C Hamano
Message 32 of 53 in “doc: checkout: rewrite detached HEAD state explanation”
  1. doc: checkout: rewrite detached HEAD state explanationJulia Evans via GitGitGadget, Oct 7, 2026
  2. Junio C HamanoOct 7, 2026
  3. Julia EvansOct 13, 2026
  4. Julia EvansOct 19, 2026
  5. Junio C HamanoOct 19, 2026
  6. Julia EvansOct 20, 2026
  7. Julia EvansOct 20, 2026
  8. Kristoffer HaugsbakkOct 7, 2026
  9. Julia EvansOct 13, 2026
  10. Kristoffer HaugsbakkOct 13, 2026
  11. Julia EvansOct 13, 2026
  12. Julia EvansOct 13, 2026
  13. doc: checkout: rewrite detached HEAD state explanationJulia Evans via GitGitGadget, Oct 13, 2026
  14. Junio C HamanoOct 14, 2026
  15. Julia EvansOct 14, 2026
  16. doc: checkout: rewrite detached HEAD state explanationJulia Evans via GitGitGadget, Oct 15, 2026
  17. Junio C HamanoOct 15, 2026
  18. Julia EvansOct 16, 2026
  19. Junio C HamanoOct 16, 2026
  20. Julia EvansOct 16, 2026
  21. Junio C HamanoOct 16, 2026
  22. doc: checkout: rewrite detached HEAD state explanationJulia Evans via GitGitGadget, Oct 16, 2026
  23. Junio C HamanoOct 16, 2026
  24. D. Ben KnobleNov 7, 2026
  25. Junio C HamanoNov 8, 2026
  26. Julia EvansNov 9, 2026
  27. Junio C HamanoNov 10, 2026
  28. Julia EvansNov 10, 2026
  29. Julia EvansNov 11, 2026
  30. Ben KnobleNov 12, 2026
  31. Junio C HamanoNov 12, 2026
  32. Julia EvansNov 12, 2026
  33. Junio C HamanoNov 12, 2026
  34. Julia EvansNov 12, 2026
  35. Junio C HamanoNov 13, 2026
  36. Julia EvansNov 13, 2026
  37. Junio C HamanoNov 13, 2026
  38. Julia EvansNov 13, 2026
  39. Julia EvansNov 13, 2026
  40. Junio C HamanoNov 14, 2026
  41. Julia EvansNov 14, 2026
  42. Julia EvansNov 13, 2026
  43. Junio C HamanoNov 13, 2026
  44. Julia EvansNov 13, 2026
  45. Junio C HamanoNov 14, 2026
  46. Junio C HamanoOct 16, 2026
  47. doc: checkout: rewrite detached HEAD state explanationJulia Evans via GitGitGadget, Nov 11, 2026
  48. Junio C HamanoNov 11, 2026
  49. Julia EvansNov 12, 2026
  50. Junio C HamanoNov 12, 2026
  51. doc: checkout: rewrite detached HEAD state explanationJulia Evans via GitGitGadget, Nov 12, 2026
  52. doc: add new detached HEAD state guideJulia Evans via GitGitGadget, Nov 16, 2026
  53. Junio C HamanoNov 16, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.