On 27 Aug., 20:59, Tekkub <[EMAIL PROTECTED]> wrote: > The only real reason that a submodule wouldn't work well is that if a user > doesn't check out the submodule because they don't have permission, git will > see this as a change (removal) to the submodule and there's a good chance > the user would inadvertently commit that change, completely removing the > submodule for everyone.
I am thinking of a reverse setup now. Where: repository-sensitive (not available to all) repository-proper (available to all) And the "trusted" developers will work on repository-sensitive which has repository-proper as a submodule. External developers will work on repository-proper only. Deployments will happen from repository-sensitive. I'll have to look better into submodules to see how "transparent" I can make this. They add some mental overhead :-) There's a challenge in deploying if I run 2 distinct repos. Br, Morten --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
