Jakub Narębski <jna...@gmail.com> writes: > Junio C Hamano wrote: > >> diff --git a/Documentation/glossary-content.txt >> b/Documentation/glossary-content.txt >> index f928b57..69c90d1 100644 >> --- a/Documentation/glossary-content.txt >> +++ b/Documentation/glossary-content.txt >> @@ -100,9 +100,22 @@ to point at the new commit. >> >> [[def_detached_HEAD]]detached HEAD:: >> Normally the <<def_HEAD,HEAD>> stores the name of a >> - <<def_branch,branch>>. However, git also allows you to >> <<def_checkout,check out>> >> - an arbitrary <<def_commit,commit>> that isn't necessarily the tip of any >> - particular branch. In this case HEAD is said to be "detached". >> + <<def_branch,branch>>, and commands that operate on the >> + history HEAD represents operate on the history leading to the >> + tip of the branch the HEAD points at. However, Git also >> + allows you to <<def_checkout,check out>> an arbitrary >> + <<def_commit,commit>> that isn't necessarily the tip of any >> + particular branch. The HEAD in such a state is called >> + "detached". > > Should we also add that "git branch" output shows this situation > as "(no branch)"? > > Nb. this is not documented in git-branch(1) manpage either...
Sounds good. Please make it so, perhaps for both. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
