From: Junio C Hamano Date: Sun, 10 Feb 2013 22:27:08 GMT Subject: Re: [PATCH v2 15/15] user-manual: Use --format=tar.gz to create a gzipped tarball Message-ID: <7va9rbst37.fsf@alter.siamese.dyndns.org> In-Reply-To: <92a02e35df3dab70928e56e6790417243beea2af.1360508415.git.wking@tremily.us> "W. Trevor King" writes: > From: "W. Trevor King" > > This functionality was introduced by 0e804e09 (archive: provide > builtin .tar.gz filter, 2011-07-21) for v1.7.7. > > Signed-off-by: W. Trevor King > --- This is a "meh" at least to me. Unless it uses something like git archive -o latest.tar.gz --prefix=project/ HEAD it is not all that interesting. > Documentation/user-manual.txt | 9 ++++++++- > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt > index 8024758..c04ea51 100644 > --- a/Documentation/user-manual.txt > +++ b/Documentation/user-manual.txt > @@ -931,12 +931,19 @@ The linkgit:git-archive[1] command can create a tar or zip archive from > any version of a project; for example: > > ------------------------------------------------- > -$ git archive --format=tar --prefix=project/ HEAD | gzip >latest.tar.gz > +$ git archive --format=tar.gz --prefix=project/ HEAD >latest.tar.gz > ------------------------------------------------- > > will use HEAD to produce a tar archive in which each filename is > preceded by `project/`. > > +Versions of Git older than 1.7.7 don't know about the 'tar.gz' format, > +you'll need to use gzip explicitly: > + > +------------------------------------------------- > +$ git archive --format=tar --prefix=project/ HEAD | gzip >latest.tar.gz > +------------------------------------------------- > + > If you're releasing a new version of a software project, you may want > to simultaneously make a changelog to include in the release > announcement.