Re: [PATCH] Teach remote machinery about remotes.default config variable

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 12, 2008, 18:46 UTC
Message-ID: <7vwsqeubj8.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <4788BFA8.2030508@gmail.com>

Mark Levedahl <mlevedahl@gmail.com> writes:

Show 10 quoted lines

> Junio C Hamano wrote:
>> Sorry, I may be missing something.
>>
>> Even if you have a submodule, you can go there and that will be
>> a valid freestanding repository.  You can always be explicit,
>> bypassing any behaviour that defaults to 'origin' to avoid
>> ambiguity.
>>
> "git-submodule update" *requires* that origin is defined in all
> sub-modules. There is no way to avoid this behavior.

Ahh.

Does that suggest the new configuration thing is only about the "submodule update" command, not "remotes.default" that affects how the non-submodule merge and fetch works?

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