| commit | d9a4bb3385329c391096fce51fa0dedce838fc8b | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Fri, 15 Dec 2023 20:32:41 +0000 (15 12:32 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 15 Dec 2023 22:08:21 +0000 (15 14:08 -0800) | ||
| tree | e3f1634ac5bb8c7ea64710eee286b56fb093c7be | treesnapshot (tar.gz zip) |
| parent | 564d0252ca632e0264ed670534a51d18a689ef5d | commitdiff |
git.txt: HEAD is not that special
The introductory text in "git help git" that describes HEAD called
it "a special ref". It is special compared to the more regular refs
like refs/heads/master and refs/tags/v1.0.0, but not that special,
unlike truly special ones like FETCH_HEAD.
Rewrite a few sentences to also introduce the distinction between a
regular ref that contain the object name and a symbolic ref that
contain the name of another ref. Update the description of HEAD
that point at the current branch to use the more correct term, a
"symbolic ref".
This was found as part of auditing the documentation and in-code
comments for uses of "special ref" that refer merely a "pseudo ref".
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The introductory text in "git help git" that describes HEAD called
it "a special ref". It is special compared to the more regular refs
like refs/heads/master and refs/tags/v1.0.0, but not that special,
unlike truly special ones like FETCH_HEAD.
Rewrite a few sentences to also introduce the distinction between a
regular ref that contain the object name and a symbolic ref that
contain the name of another ref. Update the description of HEAD
that point at the current branch to use the more correct term, a
"symbolic ref".
This was found as part of auditing the documentation and in-code
comments for uses of "special ref" that refer merely a "pseudo ref".
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git.txt | diffblobblamehistory |