I've been using git for a couple of months to get used to the system. Basic stuff - a few larger project repositories in unique directories, commits, pushes to a remote repository. Mostly as a kind of backup system. However, my ultimate goal is to share part of one large project currently being managed with git with my developers. I want them to have access to source code and test data, but not my manuscripts, correspondence, whatever. I also want to make a portion of what I will give my developers available as open source, e.g., on github, but not all of it. Just the stable, non-developmental parts. NOT the our development stuff and not the parts being used for private contracts. Submodules seem promising, but the examples are not quite what I am looking for, as far as I can tell. They talk about isolating submodules that depend on a larger project. I want to make available the larger project while keeping nested submodules (so to speak) private. Would someone point me in the right direction to achieve my goals? TIA -- View this message in context: http://git.661346.n2.nabble.com/Sharing-nested-subparts-of-large-repository-tp7403743p7403743.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