git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: why '--init' in git-submodule update

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
Nov 5, 2012, 21:30 UTC
Message-ID
<20121105213004.GA2797@book.hvoigt.net>
In-Reply-To
<CAC9WiBgpHWFGW-z5fnQR_EWnfGJUw+G3b7C6tYMGuVu1S-kP9A@mail.gmail.com>
Hi,
On Mon, Nov 05, 2012 at 05:30:51PM +0100, Francis Moreau wrote:
> I'm wondering why the --init option from git-submodule-update is not
> at least the defaut. Or even wilder, why this option exists at all and
> git-submodule-update always behave like --init was always passed.

That was a design decision. People may not be interested in all submodules but just a subset they are working with. E.g. think of a large media directory as a submodule the developers might not be interested in having it around all the time because only the designers are heavily working with it.

So the rationale is that you should ask for a certain submodule to be initialized to get it. If there is demand for it we could of course think about offering a config option in .gitmodules to allow enabling it by default for some submodules.

Cheers Heiko
Previous: Francis MoreauNext: Francis Moreau
Message 2 of 3 in “why '--init' in git-submodule update”
  1. Francis MoreauNov 5, 2012
  2. Heiko VoigtNov 5, 2012
  3. Francis MoreauNov 7, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.