Re: [PATCH 3/4] builtin/clone.c: recognize fetch.serverOption configuration

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 5, 2024, 17:50 UTC
Message-ID: <xmqq7cbq2dn0.fsf@gitster.g>
In-Reply-To: <Ztm1w_61vjEkiC4C@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

Show 11 quoted lines

> I also have to agree that "push.pushOption" would be way more sensible
> if it was configured per remote. I think it would be sensible to also
> introduce "remote.*.pushOption" in the same way and have it override the
> default value of "push.pushOption" if present. So the precedence order
> would become (from high to low):
>
>   - remote.someRemote.pushOption
>   - remote."*".pushOption
>   - push.PushOption
>
> This should be backwards compatible, too.

;-)  Sounds sensible.

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