Frawley, Sarah sarah.frawley at intel.com writes:
Correct when I referred to 10+ layers I meant nested repositories
which make up a large hierarchy. Some
repositories are repeated across the hierarchy. We check-out
submodules to tag versions (as opposed
to master branch). If we need to
On Wed, May 27, 2015 at 01:20:11PM +, Frawley, Sarah wrote:
Thanks Heiko for getting back to me.
Correct when I referred to 10+ layers I meant nested repositories
which make up a large hierarchy. Some repositories are repeated
across the hierarchy. We check-out submodules to tag
Heiko Voigt hvoigt at hvoigt.net writes:
What exactly is the feature of using a tag instead of a commit id like
it
is currently the default? A tag should be nailed to a commit anyway or
does it change in your situation? In that case I would say it is a
branch.
Cheers Heiko
:12 PM
To: Frawley, Sarah
Cc: git@vger.kernel.org
Subject: Re: FW: Query on git submodules
On Wed, May 27, 2015 at 01:20:11PM +, Frawley, Sarah wrote:
Thanks Heiko for getting back to me.
Correct when I referred to 10+ layers I meant nested repositories
which make up a large hierarchy
On Tue, Jun 02, 2015 at 09:45:39AM +, Mattias Vannergård wrote:
I am planning on using submodules in a way, where I can specify a
configuration of repos with tags, and rebuild the submodule tree, when
selecting a configuration on the top level.
But, yet I have found no easy way to
Thanks Heiko for getting back to me.
Correct when I referred to 10+ layers I meant nested repositories which make up
a large hierarchy. Some repositories are repeated across the hierarchy. We
check-out submodules to tag versions (as opposed to master branch). If we need
to roll out a
6 matches
Mail list logo
