summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStephen P. Smith <ischis2@cox.net>2015-12-29 18:54:35 (GMT)
committerJunio C Hamano <gitster@pobox.com>2015-12-29 19:18:36 (GMT)
commitbac58749bb2cd04720a4d5a1f58ebc428869f9a2 (patch)
treead2d92d53ecbe81132fd118e6d1cf3b9ecb70aba
parent1de2e442af45acf52ad45f9ac86d4c19f6475590 (diff)
downloadgit-bac58749bb2cd04720a4d5a1f58ebc428869f9a2.zip
git-bac58749bb2cd04720a4d5a1f58ebc428869f9a2.tar.gz
git-bac58749bb2cd04720a4d5a1f58ebc428869f9a2.tar.bz2
glossary: define the term shallow clone
There are several places in the documentation that the term shallow clone is used. Defining the term enables its use elsewhere with a known definition. Signed-off-by: Stephen P. Smith <ischis2@cox.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/glossary-content.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
index 4e0b971..c408d72 100644
--- a/Documentation/glossary-content.txt
+++ b/Documentation/glossary-content.txt
@@ -504,6 +504,11 @@ The most notable example is `HEAD`.
"Secure Hash Algorithm 1"; a cryptographic hash function.
In the context of Git used as a synonym for <<def_object_name,object name>>.
+[[def_shallow_clone]]shallow clone::
+ Mostly a synonym to <<def_shallow_repository,shallow repository>>
+ but the phrase makes it more explicit that it was created by
+ running `git clone --depth=...` command.
+
[[def_shallow_repository]]shallow repository::
A shallow <<def_repository,repository>> has an incomplete
history some of whose <<def_commit,commits>> have <<def_parent,parents>> cauterized away (in other