On Jul 17, 2008, at 1:04 PM, Jakub Narebski wrote:
Granted, particularly concerning the external property. OTOH, it
makes
the equivalent of git submodules rather cheap (and I actually still
have
no idea how git submodules properly work and what implications they
have).
Git submodules are roughly equivalent to svn:externals with peg
revisions; I mean here that they refer not to some branch in some
external repository, but to specific revision. This is the only sane
design, as it assures that when checking out some historical revision,
the state that is checked out will be the same for everybody.
Please take into account however that submodules are quite new
feature, and while underlying engine is solid, interface (UI) needs
some polishing (and use cases).
There is one facet of submodules that annoys me, because it prevents
me from using them as a replacement for svn:externals. Namely, the
submodule refers to a specific repository, but not a path within that
repository. I work with svn repos that use svn:externals to peg
revisions (as is appropriate) but they all refer to various paths
within the other repositories, and the only way I can deal with that
is to throw symlinks everywhere.
-Kevin Ballard
--
Kevin Ballard
http://kevin.sb.org
kevin@xxxxxx
http://www.tildesoft.com
--
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
