blender/.gitmodules

[submodule "release/scripts/addons"]
	path = release/scripts/addons
	url = ../blender-addons.git
	ignore = all
	branch = master
[submodule "release/scripts/addons_contrib"]
	path = release/scripts/addons_contrib
	url = ../blender-addons-contrib.git
	ignore = all
	branch = master
[submodule "release/datafiles/locale"]
	path = release/datafiles/locale
	url = ../blender-translations.git
	ignore = all
	branch = master
[submodule "source/tools"]
	path = source/tools
	url = ../blender-dev-tools.git
	ignore = all
	branch = master
Initialize git submodules for addons, locales and scons Uses relative paths to repositories, so this is expected to work fine for any protocol we support (git, ssh and http). Uses ignore=all for all the submodules, so updating them to latest remote hash does not tags blender repository as changes. But it is still possible to make changes to submodules and commit them from their path. 2013-11-15 06:19:08 +00:00			`[submodule "release/scripts/addons"]`
			`path = release/scripts/addons`
			`url = ../blender-addons.git`
			`ignore = all`
Point all submodules to master branch This way it should be safe to use `git submodule update --remote`. 2017-04-03 12:54:51 +00:00			`branch = master`
Initialize git submodules for addons, locales and scons Uses relative paths to repositories, so this is expected to work fine for any protocol we support (git, ssh and http). Uses ignore=all for all the submodules, so updating them to latest remote hash does not tags blender repository as changes. But it is still possible to make changes to submodules and commit them from their path. 2013-11-15 06:19:08 +00:00			`[submodule "release/scripts/addons_contrib"]`
			`path = release/scripts/addons_contrib`
			`url = ../blender-addons-contrib.git`
			`ignore = all`
Point all submodules to master branch This way it should be safe to use `git submodule update --remote`. 2017-04-03 12:54:51 +00:00			`branch = master`
Initialize git submodules for addons, locales and scons Uses relative paths to repositories, so this is expected to work fine for any protocol we support (git, ssh and http). Uses ignore=all for all the submodules, so updating them to latest remote hash does not tags blender repository as changes. But it is still possible to make changes to submodules and commit them from their path. 2013-11-15 06:19:08 +00:00			`[submodule "release/datafiles/locale"]`
			`path = release/datafiles/locale`
			`url = ../blender-translations.git`
			`ignore = all`
Point all submodules to master branch This way it should be safe to use `git submodule update --remote`. 2017-04-03 12:54:51 +00:00			`branch = master`
Add developer tools submodule This is intended for utilities to help with development, which aren't needed for building. See https://wiki.blender.org/index.php/Dev:Doc/Tools/Blender_Tools_Repo for details 2016-07-14 15:26:40 +00:00			`[submodule "source/tools"]`
			`path = source/tools`
			`url = ../blender-dev-tools.git`
			`ignore = all`
Point all submodules to master branch This way it should be safe to use `git submodule update --remote`. 2017-04-03 12:54:51 +00:00			`branch = master`