Re: Considering teaching plumbing to users harmful
- From
Kevin Ballard <kevin@sb.org>
- Date
- Jul 17, 2008, 20:12 UTC
- Message-ID
- <38486DD8-B4D8-4AAC-9B5F-0A8035D894DD@sb.org>
- In-Reply-To
- <m3k5fks2et.fsf@localhost.localdomain>
On Jul 17, 2008, at 1:04 PM, Jakub Narebski wrote:
Show 16 quoted lines
>> 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@sb.org http://www.tildesoft.com