Hi, I'm interested in working as a student for git in the GSOC program this year. I'm running a lot of web projects with heavy use of git submodules (each project has around 40 submodules) and therefore I'm very interested in enchant the git submodule experience. I'm asking for your oppinions and idées for my planned todolist for this summer (if I get accepted of course). == Preventing false "pointers" == It's far too easy to push a gitrepo pointing to a submodule version that is not existing on the server. Prevent this by checking for available submodule versions before acceptingt the push. == Threat every module alike == When failing fetching a submodule, continue fetching the next one instead of dying. There's no need to prevent fetching a submodule beginning at 'z' just because a failing in fetching a submodule beginning at 'a'. The submodules should not be alphabetically dependant as they are now. == Make submodule changes globally visible == Give git-log submodule support. A git log of showing a new version of a module should (if choosen by --submodules or alike) also list the changes to that submodule since the last version of the submodule was commited. == Move submodules into core == This last bit is excellent described in the link below. So, what do you all think? Is it too much? Too little? Is the quests relevant to git? See also https://git.wiki.kernel.org/index.php/SoC2011Ideas#Git_Submodules_Enhancements -- Med vänliga hälsningar Fredrik Gustafsson tel: 0733-608274 e-post: iveqy@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html