diff options
author | Jeff King <peff@peff.net> | 2012-10-29 04:12:12 -0400 |
---|---|---|
committer | Jeff King <peff@peff.net> | 2012-10-29 04:12:12 -0400 |
commit | fdb4d27158e4f8e19ac3b11b896bff92038afbfa (patch) | |
tree | f402de20fbac8f24b516426ed5eaf9c537515885 /run-command.c | |
parent | d21240fafafdea4fb4cab27c0e9b58ebad7d6172 (diff) | |
parent | 4b7c286ec74c7bb88e9e7ac2d283d86f64b6b0ea (diff) | |
download | git-fdb4d27158e4f8e19ac3b11b896bff92038afbfa.tar.gz |
Merge branch 'jl/submodule-add-by-name'
If you remove a submodule, in order to keep the repository so that
"git checkout" to an older commit in the superproject history can
resurrect the submodule, the real repository will stay in $GIT_DIR
of the superproject. A later "git submodule add $path" to add a
different submodule at the same path will fail. Diagnose this case
a bit better, and if the user really wants to add an unrelated
submodule at the same path, give the "--name" option to give it a
place in $GIT_DIR of the superproject that does not conflict with
the original submodule.
* jl/submodule-add-by-name:
submodule add: Fail when .git/modules/<name> already exists unless forced
Teach "git submodule add" the --name option
Diffstat (limited to 'run-command.c')
0 files changed, 0 insertions, 0 deletions