This post originated from an RSS feed registered with Ruby Buzz
by Edward Spencer.
Original Post: Git clone vs Git submodule
Feed Title: Ed's Elite blog
Feed URL: http://feeds2.feedburner.com/EdSpencer
Feed Description: Ruby on Rails development, Git issues and ExtJS/JavaScript
Having recently made the switch from svn to git, I wanted to achieve what svn externals did (and what Piston did better). Turns out this is pretty simple, for example to get rails on edge:
cd your_git_dir git submodule add git://github.com/rails/rails.git vendor/rails
What submodule does is to check out the submodules as their own repositories, so they are tracked independently of the repository you made them submodules of. The submodules you have are tracked in the .gitmodules file, which might look something like this:
Note especially that you need to remove the \\'s and replace all \'s with /'s. If you don't git will give a fail message like:
fatal: bad config file line 2 in .gitmodules No submodule mapping found in .gitmodules for path 'vendor/plugins/attachment_fu'
I don't know why it's doing that, maybe it's something I'm doing wrong but you'll need to tidy it up to make it look more like the first example in order for it to work properly.
One final thing to be aware of is that when you clone onto a new machine you'll need to run the following commands:
git submodule init git submodule update
This will initialise the submodules that are referenced in the .gitmodules file, then pull them down. By default cloning doesn't seem to do that.
Previous Topic
