X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=Documentation%2Fglossary.txt;h=d20eb6270cd795ab61b281154a7e24070519b7fb;hb=50cfde14531a5b354bbc3a070fe39c1ee86e2915;hp=cd61aa26065ba6f3d06df7d1c00e2e81d42bce9e;hpb=59b5f52047dcc1c55122c0f3c475b4d8efa45163;p=git.git

diff --git a/Documentation/glossary.txt b/Documentation/glossary.txt
index cd61aa260..d20eb6270 100644
--- a/Documentation/glossary.txt
+++ b/Documentation/glossary.txt
@@ -259,7 +259,7 @@ refspec::
 	means "grab the master branch head from the $URL and store
 	it as my origin branch head".
 	And `git push $URL refs/heads/master:refs/heads/to-upstream`
-	means "publish my master branch head as to-upstream master head
+	means "publish my master branch head as to-upstream branch
 	at $URL".   See also gitlink:git-push[1]
 
 repository::
@@ -286,6 +286,18 @@ SCM::
 SHA1::
 	Synonym for object name.
 
+shallow repository::
+	A shallow repository has an incomplete history some of
+	whose commits have parents cauterized away (in other
+	words, git is told to pretend that these commits do not
+	have the parents, even though they are recorded in the
+	commit object).  This is sometimes useful when you are
+	interested only in the recent history of a project even
+	though the real history recorded in the upstream is
+	much larger.  A shallow repository is created by giving
+	`--depth` option to gitlink:git-clone[1], and its
+	history can be later deepened with gitlink:git-fetch[1].
+
 symref::
 	Symbolic reference: instead of containing the SHA1 id itself, it
 	is of the format 'ref: refs/some/thing' and when referenced, it