* git archive --remote should generate tar.gz format indicated by -o filename
@ 2017-11-18 22:16 git-scm
0 siblings, 0 replies; only message in thread
From: git-scm @ 2017-11-18 22:16 UTC (permalink / raw)
To: git
git archive -o name.tar.gz generates a gzipped file without needing an
explicit --format switch.
However, git archive -o name.tar.gz --remote [url] generates a tar
file, which is unexpected, bandwidth-heavier, and additionally in some
cases it's not immediately obvious that this has happened.
git archive -o name.tar.gz --remote [url] --format tar.gz generates a
gzipped file, so there's obviously no limitation with e.g. git-upload-
archive.
Given the above, either git archive or git-upload-archive should apply
the same tar.gz filename heuristic and generate the expected format.
Presumably e.g. tar.xz support when using --remote would be more
problematic since, in the local case, it involves specifying an
arbitrary command.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-11-18 22:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-11-18 22:16 git archive --remote should generate tar.gz format indicated by -o filename git-scm
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 NNTP newsgroup(s).