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 <gitster@pobox.com>
Junio C Hamano committed
Jun 23, 2011 at 09:35 UTC
0abcfbff4ddaf08e5aa2524f28a7035095b6d0c9
1 file changed
+3
-4
Documentation/git.txt
+3
-4
@@ -510,16 +510,15 @@ Any git command accepting any <object> can also use the following
510
symbolic notation:
511
512
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.
514
515
<tag>::
516
a valid tag 'name'
518
- (i.e. the contents of `$GIT_DIR/refs/tags/<tag>`).
517
+ (i.e. a `refs/tags/<tag>` reference).
518
519
<head>::
520
a valid head 'name'
522
- (i.e. the contents of `$GIT_DIR/refs/heads/<head>`).
521
+ (i.e. a `refs/heads/<head>` reference).
522
523
For a more complete list of ways to spell object names, see
524
"SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].