git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Geoffrey Knopf <gknopf@spideroak-inc.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Feature Request: Submodule Warning When Cloning Repos
Date: Fri, 17 Sep 2021 12:23:16 +0700	[thread overview]
Message-ID: <3ff1426a-73a4-731e-3b6f-269d9a900019@gmail.com> (raw)
In-Reply-To: <SA1PR17MB46101CC190E4CDDD00F2AD2C9BDC9@SA1PR17MB4610.namprd17.prod.outlook.com>

On 16/09/21 23.59, Geoffrey Knopf wrote:
> Problem:
> Easy to forget to clone submodules.
> 
> Existing Solutions:
> Always clone repos that have submodules with the "--recurse-submodules" option.
> Manually look inside the git ".submodules" file to see if there are any submodules and initialize and update them.
> 
> Request:
> When performing a clone, warn the user if there are any submodules that have not been cloned.
> Recommend that the user try the "--recurse-submodules" option next time or initialize and update the submodules.
> 

I don't think warning should be granted in this case. Maybe better as note?

 From what you wrote above, did you mean print the message when cloning 
any repo with submodules?

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2021-09-17  5:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 16:59 Feature Request: Submodule Warning When Cloning Repos Geoffrey Knopf
2021-09-17  5:23 ` Bagas Sanjaya [this message]
2021-09-17 16:26   ` [EXT] " Geoffrey Knopf

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=3ff1426a-73a4-731e-3b6f-269d9a900019@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gknopf@spideroak-inc.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).