interested in folks' preference for the equivalent of git submodules (including how often there is an actual *need* for this sort of thing, as opposed to just creating separate git repos and checking out the appropriate versions when a versioned build is necessary).
there's been an increasing number of pieces lately arguing that git submodules are not the perfect solution: http://somethingsinistral.net/blog/git-submodules-are-probably-not-the-answer/ http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/ https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/ so, to keep it short: * how often do people really *need* the functionality of a git submodule or submodule equivalent? * what is your opinion on git submodule, as opposed to what people are presenting as better or simpler alternatives? thanks muchly. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ Linux mailing list Linux@lists.oclug.on.ca http://oclug.on.ca/mailman/listinfo/linux
