On Saturday 29 of September 2012 01:47:10 Darrell Anderson wrote:
> > Is it sufficient?
>
> Whew! My head hurts!
>
> How do I work with this checkout branch? Does the 'checkout' command
> actually copy the files in each module to a new location/directory?
>
> My build scripts are configured to copy the sources from each GIT module to
> my build space. I would modify the scripts to look in this new checkout
> location/branch/directory to copy the sources. Or, I would write a short
> script to create tarballs from this checkout directory and then build from
> those tarballs, which my build scripts already support.
>
> Still fuzzy in my head, but hope is improving. :)
>
> Darrell
>

Checkout does not create a new directory structure, but switch your working 
tree to the desired revision. 

So your other scripts do not need to change. Using checkout you switch your 
working git tree to the desired version, then you will do tasks that you 
need - like building. And by further checkout you switch your working git 
tree to the next desired version. Everything is still in the same working 
folder.

For example - switch whole tree to v3.5.13-sru branch:

  git checkout v3.5.13-sru && git submodule update --recursive

...and switch back to current state of master branch:

  git checkout master && git submodule update --recursive

Note: In this switching may occur a little problem with modules that are not 
contained in the desired version.

Slavek
--