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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 13, 2026, 17:23 UTC
Message-ID
<xmqq33t4fxx7.fsf@gitster.g>
In-Reply-To
<36e73720-287f-47a5-bd3f-dc53629ac968@jvns.ca>
Julia Evans <julia@jvns.ca> writes:
Show 14 quoted lines
>> The mention of "your current work" (started at the HEAD) and "next
>> commit" is to lay groundwork to explain what happens when they make
>> that commit, and how it is different when they are on detached HEAD,
>> in contrast to when they are on a branch.  After all, what we were
>> discusssing is an improved explanation on detached HEAD, and your
>> commits not affecting any of your branch *is* the most important
>> aspect of what detached HEAD gives you
>
> I read this a few times and it's hard for me to tell what the issue 
> being raised is.
>
> Are you saying that we're not explaining all the details from "`HEAD` 
> can store either a branch or commit ID" to "if you create new commits 
> while in detached HEAD state, those commits won't be on a branch"?

No. I do not expect an introductory document to tell *all* the things that needs to be known about a topic. That is an encyclopedia, not a technical manual.

The fact that you would not clobber any branches when you make a temporary commit on a detached HEAD, however, is the most important consequence of HEAD *not* recording what branch we are on that has real *impact* to the end-users. They can leave their temporary work behind without explicit removal by just checking out a branch, which also means they have to be careful about losing *if* they care about what they did during this temporary state.

I view it as a disservice to deliberately avoid talking about it.
Previous: Julia EvansNext: Julia Evans
Message 37 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.