On Sun, Feb 26, 2012 at 1:54 PM, Brian Troutwine <br...@troutwine.us> wrote: > I'm a big fan of using read-only submodules, usually to the upstream > project but sometimes to my own fork. The use of submodules makes > getting changes in from upstream trivial
I agree that github is where it's at. On of the things I liked looking at chef (if I can mention competing systems :) was their integrated module system does a little git dance to (allegedly) make this all happen, I should probably look and see what they are actually doing in there. One of my concerns with submodule is the need to treat them differently from other subtrees. Having a small team working on the configuration system would everyone need to remember (or remember to check) which modules were local and which were from the forge? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
