mirror/git
1
0
Fork 0
mirror of https://github.com/git/git.git synced 2024-10-21 01:08:11 +02:00
Code

glossary: fix and clarify the definition of 'ref'

Browse Source 
Signed-off-by: Richard Hansen <rhansen@bbn.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Richard Hansen 2013-09-04 15:04:34 -04:00 committed by Junio C Hamano
parent abdb54a1d2
commit 4b6acde543
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
Documentation/glossary-content.txt
View File

@ -395,10 +395,20 @@ should not be combined with other pathspec.
to the result.
[[def_ref]]ref::
A 40-byte hex representation of a <<def_SHA1,SHA-1>> or a name that
denotes a particular <<def_object,object>>. They may be stored in
a file under `$GIT_DIR/refs/` directory, or
in the `$GIT_DIR/packed-refs` file.
A name that begins with `refs/` (e.g. `refs/heads/master`)
that points to an <<def_object_name,object name>> or another
ref (the latter is called a <<def_symref,symbolic ref>>).
For convenience, a ref can sometimes be abbreviated when used
as an argument to a Git command; see linkgit:gitrevisions[7]
for details.
Refs are stored in the <<def_repository,repository>>.
+
The ref namespace is hierarchical.
Different subhierarchies are used for different purposes (e.g. the
`refs/heads/` hierarchy is used to represent local branches).
+
There are a few special-purpose refs that do not begin with `refs/`.
The most notable example is `HEAD`.
[[def_reflog]]reflog::
A reflog shows the local "history" of a ref. In other words,