[PATCH V4 1/2] glossary: define the term shallow clone
- From
- Stephen P. Smith <ischis2@cox.net>
- Date
- Dec 29, 2015, 18:54 UTC
- Message-ID
- <1451415275-3900-1-git-send-email-ischis2@cox.net>
- In-Reply-To
- <xmqqfuymji50.fsf@gitster.mtv.corp.google.com>
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> ---
Notes:
The review comments for the user guide update[1] suggested a change
in the definition of a shallow clone to:
- note differences between a shallow clone and a shallow repository and
- define it as a noun (which is the way the user guide update
patch uses the term)
[1] http://article.gmane.org/gmane.comp.version-control.git/283052Documentation/glossary-content.txt | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt index e225974..cafc284 100644 --- a/Documentation/glossary-content.txt +++ b/Documentation/glossary-content.txt @@ -531,6 +531,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
-- 2.7.0-rc2