Re: Stability of git-archive, breaking (?) the Github universe, and a... | git

Stability of git-archive, breaking (?) the Github universe, and a possible solution · Eli Schwartz <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Ævar Arnfjörð Bjarmason <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Eli Schwartz <hidden> · 2023-01-31
[PATCH 0/9] git archive: use gzip again by default, document output stabilty · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
[PATCH 1/9] archive & tar config docs: de-duplicate configuration section · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
[PATCH 2/9] git config docs: document "tar.<format>.{command,remote}" · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
[PATCH 3/9] archiver API: make the "flags" in "struct archiver" an enum · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
[PATCH 4/9] archive: omit the shell for built-in "command" filters · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
[PATCH 5/9] archive-tar.c: move internal gzip implementation to a function · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
[PATCH 6/9] archive: use "gzip -cn" for stability, not "git archive gzip" · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
[PATCH 7/9] test-lib.sh: add a lazy GZIP prerequisite · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
[PATCH 8/9] archive tests: test for "gzip -cn" and "git archive gzip" stability · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
[PATCH 9/9] git archive docs: document output non-stability · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
Re: [PATCH 9/9] git archive docs: document output non-stability · brian m. carlson <hidden> · 2023-02-02
Re: [PATCH 9/9] git archive docs: document output non-stability · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
Re: [PATCH 0/9] git archive: use gzip again by default, document output stabilty · Phillip Wood <hidden> · 2023-02-02
Re: [PATCH 0/9] git archive: use gzip again by default, document output stabilty · Raymond E. Pasco <hidden> · 2023-02-02
[PATCH] archive: document output stability concerns · Raymond E. Pasco <hidden> · 2023-02-03
Re: [PATCH 0/9] git archive: use gzip again by default, document output stabilty · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-03
Re: [PATCH 0/9] git archive: use gzip again by default, document output stabilty · Phillip Wood <hidden> · 2023-02-06
Re: [PATCH 0/9] git archive: use gzip again by default, document output stabilty · "Theodore Ts'o" <tytso@mit.edu> · 2023-02-03
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · brian m. carlson <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Ævar Arnfjörð Bjarmason <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Konstantin Ryabitsev <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · brian m. carlson <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · demerphq <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Michal Suchánek <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · demerphq <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · demerphq <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · "Theodore Ts'o" <tytso@mit.edu> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Joey Hess <hidden> · 2023-02-02
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · "Theodore Ts'o" <tytso@mit.edu> · 2023-02-03
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-03
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Raymond E. Pasco <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · brian m. carlson <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-02
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Eli Schwartz <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Konstantin Ryabitsev <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Eli Schwartz <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Konstantin Ryabitsev <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Michal Suchánek <hidden> · 2023-01-31
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · brian m. carlson <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · Ævar Arnfjörð Bjarmason <hidden> · 2023-02-01
Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution · brian m. carlson <hidden> · 2023-02-01

Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution

From: Michal Suchánek <hidden>
Date: 2023-02-01 12:21:58

On Wed, Feb 01, 2023 at 12:34:06PM +0100, demerphq wrote:

On Wed, 1 Feb 2023 at 11:26, Ævar Arnfjörð Bjarmason [off-list ref] wrote:

quoted

That would be going above & beyond what's needed IMO, but still a lot
easier than the daunting task of writing a specification that exactly
described GNU gzip's current behavior, to the point where you could
clean-room implement it and be guaranteed byte-for-byte compatibility.

Why does it have to be gzip? It is not that hard to come up with a

historical reasons?

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help