summaryrefslogtreecommitdiffstats
path: root/glossary-content.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2015-06-11 12:37:48 -0700
committerJunio C Hamano <gitster@pobox.com>2015-06-11 12:37:48 -0700
commit8c5d59493937c1482fea3e1c3d494aba0abe1005 (patch)
tree075f9dcc996ccc620b362aeb22114c802af0af01 /glossary-content.txt
parent975f4dba2f3b9bdb50b16dbad38ac610850e9fc2 (diff)
downloadgit-htmldocs-8c5d59493937c1482fea3e1c3d494aba0abe1005.tar.gz
Autogenerated HTML docs for v2.4.3-413-ga5fe66
Diffstat (limited to 'glossary-content.txt')
-rw-r--r--glossary-content.txt16
1 files changed, 16 insertions, 0 deletions
diff --git a/glossary-content.txt b/glossary-content.txt
index bf383c2e8..ab18f4bac 100644
--- a/glossary-content.txt
+++ b/glossary-content.txt
@@ -469,6 +469,11 @@ The most notable example is `HEAD`.
<<def_push,push>> to describe the mapping between remote
<<def_ref,ref>> and local ref.
+[[def_remote]]remote repository::
+ A <<def_repository,repository>> which is used to track the same
+ project but resides somewhere else. To communicate with remotes,
+ see <<def_fetch,fetch>> or <<def_push,push>>.
+
[[def_remote_tracking_branch]]remote-tracking branch::
A <<def_ref,ref>> that is used to follow changes from another
<<def_repository,repository>>. It typically looks like
@@ -515,6 +520,17 @@ The most notable example is `HEAD`.
is created by giving the `--depth` option to linkgit:git-clone[1], and
its history can be later deepened with linkgit:git-fetch[1].
+[[def_submodule]]submodule::
+ A <<def_repository,repository>> that holds the history of a
+ separate project inside another repository (the latter of
+ which is called <<def_superproject, superproject>>).
+
+[[def_superproject]]superproject::
+ A <<def_repository,repository>> that references repositories
+ of other projects in its working tree as <<def_submodule,submodules>>.
+ The superproject knows about the names of (but does not hold
+ copies of) commit objects of the contained submodules.
+
[[def_symref]]symref::
Symbolic reference: instead of containing the <<def_SHA1,SHA-1>>
id itself, it is of the format 'ref: refs/some/thing' and when