Andy Parkins <andyparkins <at> gmail.com> writes: > > Hello, > > I've done this by hand as a proof of concept I suspect it would need loads of > work in git-svn to do it properly. However, I thought I'd mention as part of > my "success with submodules" reports. > > ... > Now we want that clone to be even more strongly linked to the parent - to the > extent that they share the same refs, etc: > > $ cd libswscale > $ rm -rf .git/refs .git/logs .git/info description config > $ ln -s ../../.git/refs .git/refs > $ ln -s ../../.git/logs .git/logs > $ ln -s ../../.git/info .git/info > $ ln -s ../../.git/config .git/config > $ ln -s ../../.git/description .git/description > > ... > Andy I don't know if it's a good idea to follow-up on such an old entry... but I used your trick, Andy, and it works pretty well. With one exception: I am using Git on Windows and there is no symlinks on this OS. That means that you need to basically "recreate" the symlinks everytime you want to update the submodules. Not very handy but acceptable as they are not updated very often. I have to check the list if there has been some new ways to achieve this. But I'm clearly in the case of svn:externals not tighten to a particular revision, which seems the difficult case for Git. Cheers, Michel -- 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