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

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 12, 2008, 06:27 UTC
Message-ID: <7v7iify2wm.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <47885B2C.8020809@gmail.com>

Mark Levedahl <mlevedahl@gmail.com> writes:

Show 8 quoted lines

> Junio C Hamano wrote:
>> Mark Levedahl <mlevedahl@gmail.com> writes:
>>
>>   It's that simple.  Isn't it?
>>
> Yes, until you hit submodules whose state you are managing from a
> super project. Then it gets hard because the machinery brings origin
> into play.

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.

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