Jakub Narebski wrote: > First, I assume there that you do not allow for the same file to > belong to different repositories. Well, no, I cant see why a file cannot belong to both repositories. I'm sure it would be easier if a file did belong to a unique repository, but given that GIT operates at a content layer (from what I've read anyway), I cant see why it couldnt belong to more than one. > you can try either submodules > (git-submodule), or subtree (subtree merge, or third-party git-subtree > helper). I had a quick look at submodule - I dont think it helps me anyway, since I want the flexibility for files to belong to many sub-directories - not all under 1 sub directory hierarchy. > Third, if the above isn't what you want, then you can manually > intermingle working directories of different git repositories > (probably requiring decouplig of bare git repository (git-dir) > from working area (work-tree)). Ahh, now this sounds like it might be what I want to do - I think I'll explore this. I can see that it would provide file level autonomy only, but as a starting point I think it will help heaps... I'll work on it as time permits and come up with some scripts to provide what I am after (need to learn more on the workings of GIT first - everyday I learn a new feature :) Thanks for your idea... ...deon -- 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