link:git-send-email-script.html[git-send-email]::
Send patch e-mails out of "format-patch --mbox" output.
+link:git-get-tar-commit-id.html[git-get-tar-commit-id]::
+ Extract commit ID from an archive created using git-tar-tree.
Commands not yet documented
---------------------------
link:git-checkout-script.html[git-checkout-script]::
git-checkout-script.
-link:git-clone-dumb-http.html[git-clone-dumb-http]::
- git-clone-dumb-http.
-
link:git-daemon.html[git-daemon]::
git-daemon.
link:git-format-patch-script.html[git-format-patch-script]::
git-format-patch-script.
-link:git-get-tar-commit-id.html[git-get-tar-commit-id]::
- git-get-tar-commit-id.
-
link:git-request-pull-script.html[git-request-pull-script]::
git-request-pull-script.
File/Directory Structure
------------------------
-The git-core manipulates the following areas in the directory:
-
- .git/ The base (overridden with $GIT_DIR)
- objects/ The object base (overridden with $GIT_OBJECT_DIRECTORY)
- ??/ 'First 2 chars of object' directories.
- pack/ Packed archives.
- refs/ Directories containing symbolic names for objects
- (each file contains the hex SHA1 + newline)
- heads/ Commits which are heads of various sorts
- tags/ Tags, by the tag name (or some local renaming of it)
- */ Any other subdirectory of refs/ can be used to store
- files similar to what are under refs/heads/.
- HEAD Symlink to refs/heads/<current-branch-name>
+Please see link:repository-layout.html[repository layout] document.
Higher level SCMs may provide and manage additional information in the
GIT_DIR.
+
Terminology
-----------
Please see link:glossary.html[glossary] document.