mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Michal Suchánek" <>
To: Mateusz Loskot <>
Subject: Re: Suggestion: git clone should warn if repository has submodules
Date: Tue, 6 Aug 2019 17:58:47 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 6 Aug 2019 17:54:20 +0200
Mateusz Loskot <> wrote:

> On Tue, 6 Aug 2019 at 16:04, Jason Sewall <> wrote:
> >
> > Submodules are great, and I used them at work. The problem is, people
> > wind up cloning my repos without --recursive and then nothing works
> > for them, because  the submodules weren't populated and those
> > ultimately are needed to build my code.  
> What you need is a simple document for your team that outlines the common
> Git workflow or in root directory of your repositories with
> fat heading:
> ## Clone
> ```
> git clone --recursive ...
> ```
> A team in another company may require non-recursive clones by default
> and warnings from git may be quite annoying. Given the fact there is not
> one but may valid "my way"-s available, acceptable and supported by Git,
> I think, babysitting behaviour is not quite aligned with its philosophy, is it?

It has warnings that you can disable globally or per-repository in
configuration to fit your workflow.



      reply	other threads:[~2019-08-06 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 14:03 Suggestion: git clone should warn if repository has submodules Jason Sewall
2019-08-06 15:54 ` Mateusz Loskot
2019-08-06 15:58   ` Michal Suchánek [this message]

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:

  List information:

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

  git send-email \ \ \ \ \

* 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

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).