On Wednesday, May 25, 2016 at 11:29:14 AM UTC-7, Konstantin Khomoutov wrote:
> On Wed, 25 May 2016 11:06:26 -0700 (PDT) 
> Derell Licht <derell...@gmail.com <javascript:>> wrote: 
> The basic idea is that submodules in Git (at least by default) work 
> like Subversion externals which specify exact revisions (!). 
> This is because the most often used pattern when working with 
> submodules is to "pin" their revisions to particular states of the 
> repository which depends on them.   This is quite logical: if you 
> depend on a library which is in flux, most of the time you want your 
> project to depend on some know-good state of that library and that's 
> why your project refers to specific commits of the submodules it uses. 
> When you check out a specific commit you get to that "detached HEAD" 
> state.  When Git checks out a submodule, the same thing happens. 
> > Further, if I view the project in SourceTree, it doesn't even let me 
> > check out 'develop', though it shows it present on origin. 
> > I am very confused by all this... 
> On this, I know nothing as I've no idea what is SourceTree. 
> Two questions: are you talking about the "develop" branch in a 
> submodule or in a main repository?  Does checking out work with plain 
> Git? 
> All in all, I think you should learn about some basics of what you 
> trying to handle.  You seem to not really have read much on submodules 
> before embarking on a complicated task of converting a complex 
> repository from a foreign SCM to Git. 
> 2. 
> https://git-scm.com/book/en/v2/Git-Tools-Submodules#working-on-a-submodule-agtpSas8C3

I created 'develop' branch in each project; main project and each submodule.

I think you are correct, I need to study submodules in more depth. Thank 
you for the links, and for your patient comments!!
I'll come back when I understand better.

I have had previous experience with Git submodules, but the projects 
already existed; this is the first time that I've actually been creating 
them and linking things together...

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/d/optout.

Reply via email to