Name |
Last commit
|
Last update |
---|---|---|
.. | ||
add.c | ||
escape.c | ||
init.c | ||
inject_option.c | ||
lookup.c | ||
modify.c | ||
nosubs.c | ||
open.c | ||
repository_init.c | ||
status.c | ||
submodule_helpers.c | ||
submodule_helpers.h | ||
update.c |
The test submodule::add::homemade_clone unfortunately doesn't test what's expected, but does instead clone the submodule to a directory that is outside of the parent repository. Fixing this by cloning to the correct location isn't possible, though, as `git_submodule_add_setup` will have pre-created a ".git" file already, which will cause `git_clone` to error out. As it's not possible to perform the clone without fiddling around with the repo's layout, let's just remove this test as that is in fact what the new `git_submodule_clone` function is for.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
add.c | Loading commit data... | |
escape.c | Loading commit data... | |
init.c | Loading commit data... | |
inject_option.c | Loading commit data... | |
lookup.c | Loading commit data... | |
modify.c | Loading commit data... | |
nosubs.c | Loading commit data... | |
open.c | Loading commit data... | |
repository_init.c | Loading commit data... | |
status.c | Loading commit data... | |
submodule_helpers.c | Loading commit data... | |
submodule_helpers.h | Loading commit data... | |
update.c | Loading commit data... |