From: Jason Sewall <email@example.com> To: firstname.lastname@example.org Subject: Suggestion: git clone should warn if repository has submodules Date: Tue, 6 Aug 2019 10:03:57 -0400 [thread overview] Message-ID: <CADqa0D5wVWk2wa-raeVmCEhCqYznpba4TeUW_7UQOA0huR-RAg@mail.gmail.com> (raw) 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. I can see why --recursive isn't the default for git clone; you don't want to just blindly follow whatever urls are in .gitmodules without the user being aware of the possibility. That said, folks that are not familiar with submodules (which seems to be most of the people I work with!) wind up confused by this and don't know how to fix it. While the burden is on the user and should remain so, it seems like having git print out a message after cloning to the effect of "there are submodules that are not populated, maybe you should look at them" would go a long way to eliminating confusion for newer users. Yes, I have put some documentation in my project that users should fetch the submodules, but if possible, I'd like lower the number of times I have to suggest that people RTFM. Alternatively, is it preferable that I have my build system look at the submodules and inform the user more helpfully? I'm curious to know what, if any, is the recommended procedure. Cheers, Jason
next reply other threads:[~2019-08-06 14:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-06 14:03 Jason Sewall [this message] 2019-08-06 15:54 ` Mateusz Loskot 2019-08-06 15:58 ` Michal Suchánek
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=CADqa0D5wVWk2wa-raeVmCEhCqYznpba4TeUW_7UQOA0huR-RAg@mail.gmail.com \ --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).