Re: FW: Query on git submodules

From: Heiko Voigt <hvoigt@hvoigt.net>
Date: Jun 2, 2015, 11:17 UTC
Message-ID: <20150602111720.GB7442@book.hvoigt.net>
In-Reply-To: <loom.20150602T113612-540@post.gmane.org>

On Tue, Jun 02, 2015 at 09:45:39AM +0000, Mattias Vannergård wrote:

Show 21 quoted lines

> 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 select the tag in a subrepo. I 
> would like the .gitmodules to accept tag instead of branch. I think 
> there is very little difference between specifying a branch or a tag, 
> but it is more convenient to have the release version as a tag.
> 
> So, if a product A, consist of subcomponents a1, a2 and a3, the version 
> v1.1 of product A will have a configuration saying: a1, tag=v0.4; a2, 
> tag=v1.0; a3, tag=v2.0
> 
> Subcomponent can be both a pre-built binary or a shared/common source 
> base, or a complete 3rd party repository.
> 
> Is this comparable to your situation?
> 
> I am currently working on editing the git-submodules to add -t (as in 
> tag). I need to find an easy way to switch between tracking a branch and 
> locking to tag, though.

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