Skip to content

Commit 0abcfbf

Browse files
committed
git.txt: de-emphasize the implementation detail of a ref
It is an unimportant implementation detail that branches and tags are stored somewhere under $GIT_DIR/refs directory, or the name of the commit that will become the parent of the next commit is stored in $GIT_DIR/HEAD. What is more important is that branches live in refs/heads and tags live in refs/tags hierarchy in the ref namespace, and HEAD means the tip of the current branch. Signed-off-by: Junio C Hamano <[email protected]>
1 parent a0a7e9e commit 0abcfbf

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

Documentation/git.txt

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -510,16 +510,15 @@ Any git command accepting any <object> can also use the following
510510
symbolic notation:
511511

512512
HEAD::
513-
indicates the head of the current branch (i.e. the
514-
contents of `$GIT_DIR/HEAD`).
513+
indicates the head of the current branch.
515514

516515
<tag>::
517516
a valid tag 'name'
518-
(i.e. the contents of `$GIT_DIR/refs/tags/<tag>`).
517+
(i.e. a `refs/tags/<tag>` reference).
519518

520519
<head>::
521520
a valid head 'name'
522-
(i.e. the contents of `$GIT_DIR/refs/heads/<head>`).
521+
(i.e. a `refs/heads/<head>` reference).
523522

524523
For a more complete list of ways to spell object names, see
525524
"SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].

0 commit comments

Comments
 (0)