From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: kpcyrd <kpcyrd@archlinux.org>
Cc: rb-general@lists.reproducible-builds.org,
arch-dev-public@lists.archlinux.org, git@vger.kernel.org,
gitster@pobox.com, l.s.r@web.de
Subject: Re: git 2.38.0: Change in `git archive` output
Date: Mon, 17 Oct 2022 15:14:06 -0400 [thread overview]
Message-ID: <20221017191406.uimmmmr6c6eiy56t@meerkat.local> (raw)
In-Reply-To: <20b14207-a6f2-033f-3419-271662bffba9@archlinux.org>
On Sun, Oct 16, 2022 at 11:57:40PM +0200, kpcyrd wrote:
> 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
prev parent reply other threads:[~2022-10-17 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 21:57 git 2.38.0: Change in `git archive` output kpcyrd
2022-10-16 23:21 ` brian m. carlson
2022-10-17 0:02 ` Jeff King
2022-10-17 0:51 ` brian m. carlson
2022-10-17 17:03 ` Jeff King
2022-10-17 19:14 ` Konstantin Ryabitsev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221017191406.uimmmmr6c6eiy56t@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=arch-dev-public@lists.archlinux.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kpcyrd@archlinux.org \
--cc=l.s.r@web.de \
--cc=rb-general@lists.reproducible-builds.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).