git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: "Вадим Цветков" <vadim.tsvetkov80@gmail.com>, git@vger.kernel.org
Subject: Re: Git Submodules ref setting
Date: Thu, 12 May 2022 22:18:55 +0100	[thread overview]
Message-ID: <c9097f6d-3bae-a5ee-96e5-1760bb51112c@iee.email> (raw)
In-Reply-To: <F20FCD5B-7788-4D4C-8402-2C4CF447B2F5@gmail.com>

On 12/05/2022 21:01, Вадим Цветков wrote:
> Hello,
>
> I've started a small project which involves several git repositories, which depends on each other.
> For dealing with these repos I wanted to use git submodules as a simple package manager.
> However, it seems impossible to lock a submodule to particular ref, only to a branch.
> I would like to ask if this is deliberate design choice?

This may be a confusion about how some large projects use sub-modules 
and are now able to follow the developments within a sub-module branch.

The original sub-module mechanism is still available where the 
sub-module is locked at a specific commit object id's hash i.e. a 
specific 'library' version of that sub-module (in that context assumed 
to be rarely changing).
> And if it's not, may I contribute this feature?
--
Philip

  reply	other threads:[~2022-05-12 21:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 20:01 Git Submodules ref setting Вадим Цветков
2022-05-12 21:18 ` Philip Oakley [this message]
2022-05-12 22:42 ` Philippe Blain
2022-05-13  8:46   ` Philip Oakley
2022-05-13 15:22   ` Junio C Hamano

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=c9097f6d-3bae-a5ee-96e5-1760bb51112c@iee.email \
    --to=philipoakley@iee.email \
    --cc=git@vger.kernel.org \
    --cc=vadim.tsvetkov80@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).