On Tuesday 12 January 2010, Sean Phelan wrote: > Is this comparable to SVN's externals?
I think they're similar but different, because they're each done for different reasons. http://svnbook.red-bean.com/en/1.0/ch07s03.html "once one person has made the effort to define those nested working copy checkouts, no one else has to bother—Subversion will, upon checkout of the original working copy, also checkout the external working copies." So it sounds like the intent of SVN externals is to allow binding together pieces that exist in different SVN repositories. However the intent of doing a Git "superproject" is to allow you to do a clone of only one (or more) of the submodule repositories, due to a lack of an easy way to check out only part of a tree. You can think of a "superproject" as yet another Git repository that contains other Git repositories -- i.e. another layer of "git wrapper". More importantly, doing a "clone" of the Git superproject does not auotmatically give you a clone of every submodule; that's a separate operation. It likewise changes how a 'git pull' operates -- "you have to run git submodule update after git pull if you want to update submodules, too." (see one line up from the heading at:) http://www.kernel.org/pub/software/scm/git/docs/user- manual.html#_pitfalls_with_submodules -- Chris -- Chris Knadle [email protected] _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Feb 3 - Arduino Mar 3 - Sahana & 7 Years of MHVLUG Celebration Apr 7 - Nagios
