> Thanks in advance for any feedback. My understanding was that such a configuration is essentially tracking the same set of files in two different git repositories. The location of the .git is not important, I could just as easily set the working directory of any git repository to be a folder tracked by another repository. My concerns would be based primarily on the different repositories trying to act on the same files at the same time. Ignoring the sub-folder completely within the encompassing repository would avoid that, however you might have use cases that prohibit that. Out of interest, what itch are you scratching by using this model? Regards, Andrew Ardill -- 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