summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2011-06-23 09:35:10 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-06-23 15:38:18 -0700
commit0abcfbff4ddaf08e5aa2524f28a7035095b6d0c9 (patch)
treef6f058ebae8dd61ad8b1f66fbc8ca2cca9e24599 /Documentation
parentcheck-ref-format doc: de-emphasize the implementation detail of a ref (diff)
downloadtgif-0abcfbff4ddaf08e5aa2524f28a7035095b6d0c9.tar.xz
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>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git.txt7
1 files changed, 3 insertions, 4 deletions
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 8c0bfdf5a0..7fc6b88b96 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -510,16 +510,15 @@ Any git command accepting any <object> can also use the following
symbolic notation:
HEAD::
- indicates the head of the current branch (i.e. the
- contents of `$GIT_DIR/HEAD`).
+ indicates the head of the current branch.
<tag>::
a valid tag 'name'
- (i.e. the contents of `$GIT_DIR/refs/tags/<tag>`).
+ (i.e. a `refs/tags/<tag>` reference).
<head>::
a valid head 'name'
- (i.e. the contents of `$GIT_DIR/refs/heads/<head>`).
+ (i.e. a `refs/heads/<head>` reference).
For a more complete list of ways to spell object names, see
"SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].