Hi
Consider the following usecase: I have the master branch where I have a
submodule A. I create a branch where I rename the submodule to be in the
directory B. After doing all of this, everything looks good.
Now, I switch back to master. The first oddity is, that it fails to
remove the folder B because there are still files in there:
bschindler@metis ~/Projects/submodule_test (testbranch) $ git checkout
master
warning: unable to rmdir other_submodule: Directory not empty
Switched to branch 'master'
Git submodule deinit on B fails because the submodule is not known to
git anymore (after all, the folder B exists only in the other branch). I
can easily just remove the folder B from disk and initialize the
submodule A again, so all seems good.
However, what is not good is that the submodule b is still known in
.git/config. This is in particular a problem for us, because I know a
number of tools which use git config to retrieve the submodule list. Is
it therefore a bug that upon branch switch, the submodule gets
deregistered, but its entry in .git/config remains?
thanks a lot
Benjamin Schindler
P.s. I did not subscribe to the mailing list, please add me at least do
CC. Thanks
