Let "git submodule add" fail when .git/modules/<name> already exists
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Teach "git submodule add" the --name optionDocumentation/ Documentation/ git-submodule.sh +1 more | +76 | 0 replies | |
| 2/2 | submodule add: Fail when .git/modules/<name> already existsgit-submodule.sh t/ t/ | +21 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Let "git submodule add" fail when .git/modules/<name> already exists
Am 26.09.2012 22:56, schrieb Jens Lehmann:
Quoted 27 lines
Am 26.09.2012 06:18, schrieb Jonathan Johnson:
Quoted 7 lines
To reproduce
1) add a git submodule in a specific location (we'll say it's at
./submodule/location)
2) go through the normal steps of removing a submodule, as listed here - https://git.wiki.kernel.org/index.php/GitSubmoduleTutorial
3) Now the submodule is completely removed and there is no reference to it in .gitmodules or .git/config
4) Re-add a different repository at the same location (./submodule/location)Quoted 7 lines
Expected - The new submodule repository will be set up at ./submodule/location and have the new repository as its origin
What Actually Happens - The new submodule uses the existing
$gitdir(old repository) as the actual backing repository to the submodule, but the new repository is reflected in .gitmodules and .git/config.So to recap, the result is that
git remote show originin the submodule shows a different origin than is in .gitmodules and .git/configOne simple step to remedy this would be to add the deletion of the backing repository from the .git/modules directory, but again, I think an actual command to take care of all of these steps is in order anyways. Not sure you want to encourage people poking around in the .git directory.
Unfortunately just throwing away the old repository under .git/modules, whether manually or by a git command, is no real solution here: it would make it impossible to go back to a commit which records the old submodule and check that out again.
The reason for this issue is that the submodule path is used as its name by "git submodule add". While we could check this type of conflict locally, we can't really avoid it due to the distributed nature of git (somebody else could add a different repo under the same path - and thus the same name - in another clone of the repo).
Quoted 6 lines
The only long term solution I can think of is to use some kind of UUID for the name, so that the names of newly added submodules won't have a chance to clash anymore. For the short term aborting "git submodule add" when a submodule of that name already exists in .git/modules of the superproject together with the ability to provide a custom name might at least solve the local clashes.
This two patch series implements the short term solution described above.
Using some kind of UUID can easily be added in a subsequent patch, we just have to replace 'sm_name="$sm_path"' with 'sm_name=$(<generate uuid>)' in line 348 of git-submodule.sh. I think it'll be the best solution to just use a random UUID for that, as doing anything clever (like using the SHA1 of the url to avoid copies of the same remote repo) might lead to subtle breakages (e.g. because it assumes the url stays unique forever, which it sometimes won't). But maybe the short term solution is sufficient as most of the time people won't produce submodule name conflicts (and names derived from paths are much more readable that UUIDs). Thoughts?
Jens Lehmann (2):
Teach "git submodule add" the --name option submodule add: Fail when .git/modules/<name> already exists
Documentation/git-submodule.txt | 7 ++++- Documentation/gitmodules.txt | 4 ++- git-submodule.sh | 35 ++++++++++++++++------- t/t7400-submodule-basic.sh | 63 +++++++++++++++++++++++++++++++++++++++++ t/t7406-submodule-update.sh | 2 +- 5 files changed, 97 insertions(+), 14 deletions(-)
Signature · 1 line
1.7.12.1.430.g4fd6dc4