Re: [PATCH 0/9] git archive: use gzip again by default, document output stabilty

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 2, 2023, 16:25 UTC
Message-ID: <xmqq5yckvxtb.fsf@gitster.g>
In-Reply-To: <cover-0.9-00000000000-20230202T093212Z-avarab@gmail.com>

Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:

> As the disruption of changing the default isn't worth it, let's use
> gzip(1) again by default, and only fall back on the new "git archive
> gzip" if it isn't available.

It perhaps is OK, and lets us answer "ugh, the compressed output of 'git archive' is unstable again" with "we didn't change anything, perhaps you changed your gzip(1)?" when they fix bugs or improve compression or whatever. Of course that is not an overall win for the end users, but in the short term until gzip gets such a change, we would presumably get the "same" output as before.

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