On Friday, April 26, 2013 4:52:41 AM UTC+2, Dale Worley wrote:

> OK, how to I set up a submodule? 
> As far as I can tell from "Version Control with Git", I should be able 
> to: 
> 1. Write .gitmodules with the appropriate configuration values.  In my 
> case: 
> [submodule "T9"] 
>         path = T9 
>         url = /home/worley/T9 
> 2. Execute "git submodule init" to copy these config values into 
> .git/config, thus making the submodule known to Git. 
> 3. Execute "git submodule update" to cause Git to set up the directory 
> ./T9; in this situation, by cloning /home/worley/T9 into it. 
> However, the "git submodule" commands do nothing and produce no error 
> messages.  (Which is crappy coding!)  So I'm not doing the right 
> thing, and have no guidance as to where I'm making a mistake. 
I get the same behavior here. However, when using the approach described 
in http://git-scm.com/book/en/Git-Tools-Submodules - with *git submodule 
add ...*, it works.

Reading in the docs about what the init and update commands do, I was also 
a bit suprised that it didn't work.. But reading further up, it says:

"When adding a new submodule to the tree, the add subcommand is to be used. 
However, when pulling a tree containing submodules, these will not be 
checked out by
       default; the init and update subcommands will maintain submodules 
checked out and at appropriate revision in your working tree."

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to