git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git 2.38.0: Change in `git archive` output

From
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date
Oct 17, 2022, 19:14 UTC
Message-ID
<20221017191406.uimmmmr6c6eiy56t@meerkat.local>
In-Reply-To
<20b14207-a6f2-033f-3419-271662bffba9@archlinux.org>
On Sun, Oct 16, 2022 at 11:57:40PM +0200, kpcyrd wrote:
Show 6 quoted lines
> I don't know if there's some kind of gzip standard that could be used to
> align the git internal gzip implementation with gnu gzip.
> 
> I'm not saying this is necessarily a bug or regression but it makes it
> harder to reproduce github tar balls from a git repository. Just sharing
> what I've debugged. :)

I've previously complained about the output of .tar format changing, but I think it's too much to expect the *compressed* output to remain the same. In environments where CPU time is more expensive than bandwidth, it's entirely normal to expect the administrator to arbitrarily adjust compression levels without any warning, or, on the contrary, pre-generate and cache zopfli-compressed archives.

-K
Previous: Jeff King
Message 6 of 6 in “git 2.38.0: Change in `git archive` output”
  1. kpcyrdOct 16, 2022
  2. brian m. carlsonOct 16, 2022
  3. Jeff KingOct 17, 2022
  4. brian m. carlsonOct 17, 2022
  5. Jeff KingOct 17, 2022
  6. Konstantin RyabitsevOct 17, 2022

Read the whole thread, see it on lore, or plain text.

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