Okay, it seems submodules really were the answer. I split my app into a standalone public subtree and a development subtree that will use the public source as a submodule (haven't actually done that yet, though). These will be excluded from the parent git repository, but I guess that is fine since the parent is used mainly for archiving and the remote repository serves as the code archive. -- View this message in context: http://git.661346.n2.nabble.com/Sharing-nested-subparts-of-large-repository-tp7403743p7439149.html Sent from the git mailing list archive at Nabble.com. -- 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