Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Administration
Server Admin
Plumbing Commands
- 1.8.2.2 → 1.8.2.3 no changes
-
1.8.2.1
04/07/13
- 1.8.1.1 → 1.8.1.6 no changes
-
1.8.1
12/31/12
- 1.7.10.3 → 1.8.0.3 no changes
-
1.7.10.2
05/11/12
- 1.7.10.1 no changes
-
1.7.10
04/06/12
- 1.7.5.1 → 1.7.9.7 no changes
-
1.7.5
04/24/11
- 1.7.4.1 → 1.7.4.5 no changes
-
1.7.4
01/31/11
- 1.7.3.1 → 1.7.3.5 no changes
-
1.7.3
09/18/10
- 1.7.1.3 → 1.7.2.5 no changes
-
1.7.1.2
07/27/10
- 1.6.4.1 → 1.7.1.1 no changes
-
1.6.4
07/29/09
- 1.6.0.3 → 1.6.3.4 no changes
-
1.6.0.2
09/12/08
gitmodules(5) Manual Page
NAME
gitmodules - defining submodule properties
SYNOPSIS
$GIT_WORK_DIR/.gitmodules
DESCRIPTION
The .gitmodules file, located in the top-level directory of a git working tree, is a text file with a syntax matching the requirements of git-config(1).
The file contains one subsection per submodule, and the subsection value is the name of the submodule. Each submodule section also contains the following required keys:
- submodule.<name>.path
Defines the path, relative to the top-level directory of the git working tree, where the submodule is expected to be checked out. The path name must not end with a /. All submodule paths must be unique within the .gitmodules file.
- submodule.<name>.url
Defines an url from where the submodule repository can be cloned.
EXAMPLES
Consider the following .gitmodules file:
[submodule "libfoo"] path = include/foo url = git://foo.com/git/lib.git
[submodule "libbar"] path = include/bar url = git://bar.com/git/lib.git
This defines two submodules, libfoo and libbar. These are expected to be checked out in the paths include/foo and include/bar, and for both submodules an url is specified which can be used for cloning the submodules.
SEE ALSO
DOCUMENTATION
Documentation by Lars Hjemli <hjemli@gmail.com>
GIT
Part of the git(1) suite