glossary: update description of head and ref
Reword them to avoid sounding as if loose refs are the only ones in the world. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Jun 23, 2011 at 09:47 UTC
deaef1e94734a61407c73637e0e9718f914c3a62
1 file changed
+5
-4
Documentation/glossary-content.txt
+5
-4
@@ -161,8 +161,8 @@ to point at the new commit.
161
162
[[def_head]]head::
163
A <<def_ref,named reference>> to the <<def_commit,commit>> at the tip of a
164
- <<def_branch,branch>>. Heads are stored in
165
- `$GIT_DIR/refs/heads/`, except when using packed refs. (See
164
+ <<def_branch,branch>>. Heads are stored in a file in
165
+ `$GIT_DIR/refs/heads/` directory, except when using packed refs. (See
166
linkgit:git-pack-refs[1].)
167
168
[[def_HEAD]]HEAD::
@@ -350,8 +350,9 @@ including Documentation/chapter_1/figure_1.jpg.
350
351
[[def_ref]]ref::
352
A 40-byte hex representation of a <<def_SHA1,SHA1>> or a name that
353
- denotes a particular <<def_object,object>>. These may be stored in
354
- `$GIT_DIR/refs/`.
353
+ denotes a particular <<def_object,object>>. They may be stored in
354
+ a file under `$GIT_DIR/refs/` directory, or
355
+ in the `$GIT_DIR/packed-refs` file.
356
357
[[def_reflog]]reflog::
358
A reflog shows the local "history" of a ref. In other words,