From: Hilco Wijbenga Date: Tue, 28 Jun 2011 01:28:18 GMT Subject: Re: Submodule URL Message-ID: In-Reply-To: <201106272258.p5RMwOxK028539@no.baka.org> On 27 June 2011 15:58, Seth Robertson wrote: > In message , Hilco Wijbenga writes: > >    As I was creating a script to support a question about submodules I >    ran into something that I don't understand. I've attached a simple >    script that fails to execute properly. I don't understand why. > > Perhaps you should consider gitslave as an alternative to > git-submodule, depending on your development workflow it may be better > (or worse). FYI, yes, somebody read the entire tutorial and learnt something. ;-) > gitslave (http://gitslave.sf.net) is useful when you control and > develop on the subprojects at more of less the same time as the > superproject, and furthermore when you typically want to tag, branch, > push, pull, etc all repositories at the same time. :-) Perfect! That's seems to be *exactly* what I need. How hard is it to turn an umbrella project with content and quite a few submodules (only 1 level deep) into a gitslave repo? > git-submodule is better when you do not control the subprojects or > more specifically wish to fix the subproject at a specific revision > even as the subproject changes > > However, more directly to your question, we see that using absolute > pathnames (not file: URLs) works.  See > https://git.wiki.kernel.org/index.php/GitSubmoduleTutorial > > If this works for you and file:// does not, I'd say it was a bug in > git. Well, it seems like a bug to me then. Still, maybe I made a mistake in my script. I hope somebody else can chime in too.