[PATCH 2/5] git.txt: de-emphasize the implementation detail of a ref
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 23, 2011, 16:52 UTC
- Message-ID
- <1308847958-3429-3-git-send-email-gitster@pobox.com>
- In-Reply-To
- <1308847958-3429-1-git-send-email-gitster@pobox.com>
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> --- Documentation/git.txt | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt index 8c0bfdf..7fc6b88 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].
-- 1.7.6.rc3