summaryrefslogtreecommitdiff
path: root/Documentation/glossary.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2007-01-17 10:53:31 -0800
committerJunio C Hamano <junkio@cox.net>2007-01-17 10:53:31 -0800
commit428ddc5de64684ad37d20c563544f17993a4d58d (patch)
treebe5f9bb689c412109e8568fe4a254a3c6eb0659d /Documentation/glossary.txt
parentdf59afe3eb121e89195e246105dd53de0ec396ab (diff)
downloadgit-428ddc5de64684ad37d20c563544f17993a4d58d.tar.gz
Documentation: describe shallow repository
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/glossary.txt')
-rw-r--r--Documentation/glossary.txt12
1 files changed, 12 insertions, 0 deletions
diff --git a/Documentation/glossary.txt b/Documentation/glossary.txt
index bc917bbac3..d20eb6270c 100644
--- a/Documentation/glossary.txt
+++ b/Documentation/glossary.txt
@@ -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