@matheusbsbs / matheus-bagliano / commits / 12bd7e78ee
Fork 0

Documentation(glossary): minor formatting clean-ups.

Signed-off-by: Junio C Hamano <junkio@cox.net>

Junio C Hamano committed Dec 7, 2005 at 16:16 UTC 12bd7e78ee138e3ceefa5442db224c8288204b64
2 files changed +6 -7
Documentation/glossary.txt
+6 -6
@@ -20,7 +20,7 @@ hash::
20
21 object database::
22 Stores a set of "objects", and an individial object is identified
23 - by its object name. The object usually live in $GIT_DIR/objects/.
23 + by its object name. The objects usually live in `$GIT_DIR/objects/`.
24
25 blob object::
26 Untyped object, e.g. the contents of a file.
@@ -109,15 +109,15 @@ head::
109 branch::
110 A non-cyclical graph of revisions, i.e. the complete history of
111 a particular revision, which is called the branch head. The
112 - branch heads are stored in $GIT_DIR/refs/heads/.
112 + branch heads are stored in `$GIT_DIR/refs/heads/`.
113
114 ref::
115 A 40-byte hex representation of a SHA1 pointing to a particular
116 - object. These may be stored in $GIT_DIR/refs/.
116 + object. These may be stored in `$GIT_DIR/refs/`.
117
118 head ref::
119 A ref pointing to a head. Often, this is abbreviated to "head".
120 - Head refs are stored in $GIT_DIR/refs/heads/.
120 + Head refs are stored in `$GIT_DIR/refs/heads/`.
121
122 tree-ish::
123 A ref pointing to either a commit object, a tree object, or a
@@ -125,7 +125,7 @@ tree-ish::
125
126 ent::
127 Favorite synonym to "tree-ish" by some total geeks. See
128 - http://en.wikipedia.org/wiki/Ent_(Middle-earth) for an in-depth
128 + `http://en.wikipedia.org/wiki/Ent_(Middle-earth)` for an in-depth
129 explanation.
130
131 tag object::
@@ -137,7 +137,7 @@ tag object::
137 tag::
138 A ref pointing to a tag or commit object. In contrast to a head,
139 a tag is not changed by a commit. Tags (not tag objects) are
140 - stored in $GIT_DIR/refs/tags/. A git tag has nothing to do with
140 + stored in `$GIT_DIR/refs/tags/`. A git tag has nothing to do with
141 a Lisp tag (which is called object type in git's context).
142 A tag is most typically used to mark a particular point in the
143 commit ancestry chain.
Documentation/sort_glossary.pl
-1
@@ -42,7 +42,6 @@ sub no_spaces ($) {
42
43 print 'GIT Glossary
44 ============
45 -Aug 2005
45
46 This list is sorted alphabetically:
47