I'm not tottally sure about it, but AFAIK
git submodule update
fetches the latest commit of the "master" branch, and then checks it out,
leaving the submodule directory in a detached state. You can, however,
check out a specific branch or tag (see the git-checkout manual on that). I
hope this answer suites you, otherwise you must wait for a more advanced
On Mar 4, 2013 10:41 PM, "FlashBurn" <rail.shafigu...@gmail.com> wrote:
> I'm not very clear on submodules. I did look at the Online git book,
> http://git-scm.com/book/ch6-6.html, but I'm still somewhat confused. From
> this chapter I understood that if I want one project to include another, I
> use submodules. But here is where I'm clear. Say I have the following
> directory structure
> myproject (regular git project)
> |-some other project 1 (as a git submodule)
> |-some other project 2 (as a git submodule)
> 1) Say both project1 and project2 are being developed. However when I
> clone or pull myproject I don't want the latest version of project 1 and
> project 2. I want them at the state when I created them as submodules. Do I
> need to git add myproject/project1 myproject/project2 ?
> 2) What do I need to do I do want the latest revisions of project1 and
> project2 when myproject is clonded or pulled?
> Any help is appreciated.
> 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.
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
For more options, visit https://groups.google.com/groups/opt_out.