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

[Junio C Hamano <gitster@pobox.com>]

Julia Evans <julia@jvns.ca> writes:

>> I think the central difference is that you
>> seem to consider detached HEAD state is only about pure sightseeing
>> while it was designed to allow touching and breaking.  If the user
>> is not making any changes, of course it does not make sense to talk
>> about "your current changes" or "next commit".  But detached HEAD is
>> not limited to such a world view.
>
> We say very clearly that you can make commits while in detached HEAD 
> state so I don't think there's any danger of readers not realizing 
> that's possible.
>
>    But it's important to know that if you create new commits while in
>    detached HEAD state, those commits won't be on a branch.

Yeah, but that isn't the purpose of mentioning "next commit" etc. to
make readers realize that.  So I am not sure what you want to say
with that.

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.