git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Submodules ref setting

From
Philip Oakley <philipoakley@iee.email>
Date
May 12, 2022, 21:18 UTC
Message-ID
<c9097f6d-3bae-a5ee-96e5-1760bb51112c@iee.email>
In-Reply-To
<F20FCD5B-7788-4D4C-8402-2C4CF447B2F5@gmail.com>
On 12/05/2022 21:01, Вадим Цветков wrote:
Show 6 quoted lines
> 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

Previous: Вадим ЦветковNext: Philippe Blain
Message 2 of 5 in “Git Submodules ref setting”
  1. Вадим ЦветковMay 12, 2022
  2. Philip OakleyMay 12, 2022
  3. Philippe BlainMay 12, 2022
  4. Philip OakleyMay 13, 2022
  5. Junio C HamanoMay 13, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.