2005-05-10 21:32:30 +00:00
|
|
|
git-tar-tree(1)
|
|
|
|
|
===============
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
2007-01-18 23:53:37 +00:00
|
|
|
git-tar-tree - Create a tar archive of the files in the named tree object
|
2005-05-10 21:32:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
2011-07-02 02:38:26 +00:00
|
|
|
[verse]
|
2008-06-30 06:09:04 +00:00
|
|
|
'git tar-tree' [--remote=<repo>] <tree-ish> [ <base> ]
|
2005-05-10 21:32:30 +00:00
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
2010-01-09 23:33:00 +00:00
|
|
|
THIS COMMAND IS DEPRECATED. Use 'git archive' with `--format=tar`
|
2007-04-18 23:51:21 +00:00
|
|
|
option instead (and move the <base> argument to `--prefix=base/`).
|
2006-09-24 21:42:01 +00:00
|
|
|
|
2005-05-10 21:32:30 +00:00
|
|
|
Creates a tar archive containing the tree structure for the named tree.
|
2005-08-05 15:05:02 +00:00
|
|
|
When <base> is specified it is added as a leading path to the files in the
|
2005-05-10 21:32:30 +00:00
|
|
|
generated tar archive.
|
|
|
|
|
|
2010-01-09 23:33:00 +00:00
|
|
|
'git tar-tree' behaves differently when given a tree ID versus when given
|
2005-06-02 18:50:42 +00:00
|
|
|
a commit ID or tag ID. In the first case the current time is used as
|
|
|
|
|
modification time of each file in the archive. In the latter case the
|
|
|
|
|
commit time as recorded in the referenced commit object is used instead.
|
|
|
|
|
Additionally the commit ID is stored in a global extended pax header.
|
2010-01-09 23:33:00 +00:00
|
|
|
It can be extracted using 'git get-tar-commit-id'.
|
2005-06-02 18:50:42 +00:00
|
|
|
|
2006-06-07 18:15:10 +00:00
|
|
|
OPTIONS
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
|
<tree-ish>::
|
|
|
|
|
The tree or commit to produce tar archive for. If it is
|
|
|
|
|
the object name of a commit object.
|
|
|
|
|
|
|
|
|
|
<base>::
|
|
|
|
|
Leading path to the files in the resulting tar archive.
|
|
|
|
|
|
|
|
|
|
--remote=<repo>::
|
|
|
|
|
Instead of making a tar archive from local repository,
|
|
|
|
|
retrieve a tar archive from a remote repository.
|
|
|
|
|
|
2006-07-20 09:30:44 +00:00
|
|
|
CONFIGURATION
|
|
|
|
|
-------------
|
|
|
|
|
|
2007-08-21 18:01:16 +00:00
|
|
|
tar.umask::
|
|
|
|
|
This variable can be used to restrict the permission bits of
|
|
|
|
|
tar archive entries. The default is 0002, which turns off the
|
|
|
|
|
world write bit. The special value "user" indicates that the
|
|
|
|
|
archiving user's umask will be used instead. See umask(2) for
|
|
|
|
|
details.
|
2006-07-20 09:30:44 +00:00
|
|
|
|
|
|
|
|
EXAMPLES
|
2006-06-07 18:15:10 +00:00
|
|
|
--------
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git tar-tree HEAD junk | (cd /var/tmp/ && tar xf -)`::
|
2006-06-07 18:15:10 +00:00
|
|
|
|
|
|
|
|
Create a tar archive that contains the contents of the
|
|
|
|
|
latest commit on the current branch, and extracts it in
|
|
|
|
|
`/var/tmp/junk` directory.
|
|
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git tar-tree v1.4.0 git-1.4.0 | gzip >git-1.4.0.tar.gz`::
|
2006-06-07 18:15:10 +00:00
|
|
|
|
2006-06-18 10:57:59 +00:00
|
|
|
Create a tarball for v1.4.0 release.
|
2006-06-07 18:15:10 +00:00
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git tar-tree v1.4.0{caret}\{tree\} git-1.4.0 | gzip >git-1.4.0.tar.gz`::
|
2006-06-07 18:15:10 +00:00
|
|
|
|
2006-06-18 10:57:59 +00:00
|
|
|
Create a tarball for v1.4.0 release, but without a
|
|
|
|
|
global extended pax header.
|
|
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git tar-tree --remote=example.com:git.git v1.4.0 >git-1.4.0.tar`::
|
2006-06-18 10:57:59 +00:00
|
|
|
|
|
|
|
|
Get a tarball v1.4.0 from example.com.
|
2005-05-10 21:32:30 +00:00
|
|
|
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-04 02:13:29 +00:00
|
|
|
`git tar-tree HEAD:Documentation/ git-docs > git-1.4.0-docs.tar`::
|
2006-07-31 00:26:27 +00:00
|
|
|
|
|
|
|
|
Put everything in the current head's Documentation/ directory
|
|
|
|
|
into 'git-1.4.0-docs.tar', with the prefix 'git-docs/'.
|
|
|
|
|
|
2005-05-10 21:32:30 +00:00
|
|
|
GIT
|
|
|
|
|
---
|
2008-06-06 07:07:32 +00:00
|
|
|
Part of the linkgit:git[1] suite
|
