Sorry for re-posting the question but I though I should explain the issue better and to fix the subject line. sub When you are cloning repository containing submodules, and you are using the --merge flag to "git submodule update" the first time, then the submodule instance in question will assume you want to delete all files present in the module. Please look at attachment for a testcase and how the result might look like. Unless this is not the intended behavior, then I would suggest changing --merge (and possible --rebase) to not assume a non-existent repository to be a empty one. The man pages says "Merge the commit recorded in the superproject into the current branch of the submodule", but we have no current branch of the submodule. I would be happy for any reply, and sorry again for the repost. /Carl FÃrstenberg
Attachment:
submodule_merge_test.sh
Description: Bourne shell script
Attachment:
test_output
Description: Binary data