From: "Michal Suchánek" <email@example.com> To: Mateusz Loskot <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Suggestion: git clone should warn if repository has submodules Date: Tue, 6 Aug 2019 17:58:47 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CABUeae9JhQ+JcNzYRMr40T2FTCJChYEz_riUr6Q1O5YO0uEDng@mail.gmail.com> On Tue, 6 Aug 2019 17:54:20 +0200 Mateusz Loskot <email@example.com> wrote: > On Tue, 6 Aug 2019 at 16:04, Jason Sewall <firstname.lastname@example.org> 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 README.md 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. Thanks Michal
prev parent 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 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: 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Suggestion: git clone should warn if repository has submodules' \ /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
Code repositories for project(s) associated with this 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).