Re: [PATCH 2/2] Honor GIT_DEFAULT_HASH for empty clones without remote algo

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 26, 2023, 21:18 UTC
Message-ID: <xmqqjzxyqr4t.fsf@gitster.g>
In-Reply-To: <20230426205324.326501-3-sandals@crustytoothpaste.net>

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> However, up until 8b214c2e9d ("clone: propagate object-format when
> cloning from void", 2023-04-05), we honored GIT_DEFAULT_HASH in this
> case, so let's continue to do that.

Let's not. Once we identified the bug of mistakenly honoring a wrong variable, let's fix it and keep it fixed.

The local optimization, if necessary, can be taught to peek the source repository and propagating the object format selection to the destination repository.

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