git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Heiko Voigt <hvoigt@hvoigt.net>
To: "Mattias Vannergård" <mattias.vannergard@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: FW: Query on git submodules
Date: Tue, 2 Jun 2015 13:17:21 +0200	[thread overview]
Message-ID: <20150602111720.GB7442@book.hvoigt.net> (raw)
In-Reply-To: <loom.20150602T113612-540@post.gmane.org>

On Tue, Jun 02, 2015 at 09:45:39AM +0000, 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 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

  reply	other threads:[~2015-06-02 11:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C328B7D13677A4EAF715D0755A6D7EE25C56C89@irsmsx110.ger.corp.intel.com>
2015-05-22 13:46 ` Query on git submodules Frawley, Sarah
2015-05-26 17:01   ` Heiko Voigt
2015-05-27 13:20     ` FW: " Frawley, Sarah
2015-06-02  9:45       ` Mattias Vannergård
2015-06-02 11:17         ` Heiko Voigt [this message]
2015-06-02 11:27           ` Mattias Vannergård
2015-06-02 11:12       ` Heiko Voigt
2015-06-02 14:22         ` Frawley, Sarah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150602111720.GB7442@book.hvoigt.net \
    --to=hvoigt@hvoigt.net \
    --cc=git@vger.kernel.org \
    --cc=mattias.vannergard@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).