Re: [PATCH v3 9/9] user-manual: Use -o latest.tar.gz to create a gzipped tarball
On Sun, Feb 17, 2013 at 06:58:58PM -0800, Junio C Hamano wrote: It is easy for me to deal with conflicts in this particular case, but in general it would have been more straightforward to manage if these more localized phrasing fixes came earlier and a larger file-wide cosmetic change was done after all the others have settled. Ok. I'll shift the backtick fix to the back of the stack for v4. -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy signature.asc Description: OpenPGP digital signature
[PATCH v3 9/9] user-manual: Use -o latest.tar.gz to create a gzipped tarball
From: W. Trevor King wk...@tremily.us 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 wk...@tremily.us --- Documentation/user-manual.txt | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 3381c22..af6c09d 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -931,11 +931,20 @@ 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 -o latest.tar.gz --prefix=project/ HEAD - -will use HEAD to produce a tar archive in which each filename is -preceded by `project/`. +will use HEAD to produce a gzipped tar archive in which each filename +is preceded by `project/`. The output file format is inferred from +the output file extension if possible, see linkgit:git-archive[1] for +details. + +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 -- 1.8.1.336.g94702dd -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v3 9/9] user-manual: Use -o latest.tar.gz to create a gzipped tarball
W. Trevor King wk...@tremily.us writes: From: W. Trevor King wk...@tremily.us 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 wk...@tremily.us --- This looks like a good 'maint' material that can be applied straight away there if the patch did not depend on 5/9 to cause needless conflicts. It is easy for me to deal with conflicts in this particular case, but in general it would have been more straightforward to manage if these more localized phrasing fixes came earlier and a larger file-wide cosmetic change was done after all the others have settled. diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 3381c22..af6c09d 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -931,11 +931,20 @@ 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 -o latest.tar.gz --prefix=project/ HEAD - -will use HEAD to produce a tar archive in which each filename is -preceded by `project/`. +will use HEAD to produce a gzipped tar archive in which each filename +is preceded by `project/`. The output file format is inferred from +the output file extension if possible, see linkgit:git-archive[1] for +details. + +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 -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
