Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.0.2 → 2.1.3 no changes
- 2.0.1 06/25/14
- 22.214.171.124 → 2.0.0 no changes
- 126.96.36.199 01/13/14
- 188.8.131.52 → 184.108.40.206 no changes
- 1.8.5 11/27/13
- 220.127.116.11 → 18.104.22.168 no changes
- 22.214.171.124 04/07/13
- 126.96.36.199 → 188.8.131.52 no changes
- 1.8.1 12/31/12
- 184.108.40.206 → 220.127.116.11 no changes
- 18.104.22.168 05/11/12
- 22.214.171.124 no changes
- 1.7.10 04/06/12
- 126.96.36.199 → 188.8.131.52 no changes
- 1.7.5 04/24/11
gitmodules - defining submodule properties
.gitmodules file, located in the top-level directory of a Git
working tree, is a text file with a syntax matching the requirements
The file contains one subsection per submodule, and the subsection value is the name of the submodule. The name is set to the path where the submodule has been added unless it was customized with the --name option of git submodule add. Each submodule section also contains the following required keys:
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.
Defines a URL from which the submodule repository can be cloned. This may be either an absolute URL ready to be passed to git-clone or (if it begins with ./ or ../) a location relative to the superproject’s origin repository.
In addition, there are a number of optional keys:
Defines what to do when the submodule is updated by the superproject. If checkout (the default), the new commit specified in the superproject will be checked out in the submodule on a detached HEAD. If rebase, the current branch of the submodule will be rebased onto the commit specified in the superproject. If merge, the commit specified in the superproject will be merged into the current branch in the submodule. If none, the submodule with name
$namewill not be updated by default.
This config option is overridden if 'git submodule update' is given the '--merge', '--rebase' or '--checkout' options.
A remote branch name for tracking updates in the upstream submodule. If the option is not specified, it defaults to master. See the
--remotedocumentation in git-submodule for details.
This option can be used to control recursive fetching of this submodule. If this option is also present in the submodules entry in .git/config of the superproject, the setting there will override the one found in .gitmodules. Both settings can be overridden on the command line by using the "--[no-]recurse-submodules" option to "git fetch" and "git pull".
Defines under what circumstances "git status" and the diff family show a submodule as modified. When set to "all", it will never be considered modified, "dirty" will ignore all changes to the submodules work tree and takes only differences between the HEAD of the submodule and the commit recorded in the superproject into account. "untracked" will additionally let submodules with modified tracked files in their work tree show up. Using "none" (the default when this option is not set) also shows submodules that have untracked files in their work tree as changed. If this option is also present in the submodules entry in .git/config of the superproject, the setting there will override the one found in .gitmodules. Both settings can be overridden on the command line by using the "--ignore-submodule" option. The git submodule commands are not affected by this setting.
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,
libbar. These are expected to
be checked out in the paths include/foo and include/bar, and for both
submodules a URL is specified which can be used for cloning the submodules.
Part of the git suite