From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-5.0 required=3.0 tests=AWL,BAYES_00,BODY_8BITS, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id BA8481F4D8 for ; Thu, 12 May 2022 21:19:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1358686AbiELVTI (ORCPT ); Thu, 12 May 2022 17:19:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41736 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1358690AbiELVTA (ORCPT ); Thu, 12 May 2022 17:19:00 -0400 Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 80B5A142817 for ; Thu, 12 May 2022 14:18:58 -0700 (PDT) Received: from host217-43-165-125.range217-43.btcentralplus.com ([217.43.165.125] helo=[192.168.1.168]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1npGD2-0007Pq-Eo; Thu, 12 May 2022 22:18:56 +0100 Message-ID: Date: Thu, 12 May 2022 22:18:55 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: Git Submodules ref setting Content-Language: en-US To: =?UTF-8?B?0JLQsNC00LjQvCDQptCy0LXRgtC60L7Qsg==?= , git@vger.kernel.org References: From: Philip Oakley In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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