diff options
| author |  Jens Lehmann <Jens.Lehmann@web.de> | 2012-09-30 23:01:29 +0200 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2012-09-30 16:53:57 -0700 |
| commit | 4b7c286ec74c7bb88e9e7ac2d283d86f64b6b0ea (patch) | |
| tree | 6825a9ffe4b1467939ea77c1b513dd368abdfd8a /test-ctype.c | |
| parent | Teach "git submodule add" the --name option (diff) | |
| download | tgif-4b7c286ec74c7bb88e9e7ac2d283d86f64b6b0ea.tar.xz | |
submodule add: Fail when .git/modules/<name> already exists unless forced
When adding a new submodule it can happen that .git/modules/<name> already
contains a submodule repo, e.g. when a submodule is removed from the work
tree and another submodule is added at the same path. But then the work
tree of the submodule will be populated using the existing repository and
not the one the user provided, which results in an incorrect work tree. On
the other hand the user might reactivate a submodule removed earlier, then
reusing that .git directory is the Right Thing to do.
As git can't decide what is the case, error out and tell the user she
should use either use a different name for the submodule with the "--name"
option or can reuse the .git directory for the newly added submodule by
providing the --force option (which only makes sense when the upstream
matches, so the error message lists all remotes of .git/modules/<name>).
In one test in t7406 the --force option had to be added to "git submodule
add", as that test re-adds a formerly removed submodule.
Reported-by: Jonathan Johnson <me@jondavidjohn.com>
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'test-ctype.c')
0 files changed, 0 insertions, 0 deletions