mirror of
https://github.com/git/git.git
synced 2024-11-01 06:47:52 +01:00
7791a1d9b9
The SYNOPSIS sections of most commands that span several lines already use [verse] to retain line breaks. Most commands that don't span several lines seem not to use [verse]. In the HTML output, [verse] does not only preserve line breaks, but also makes the section indented, which causes a slight inconsistency between commands that use [verse] and those that don't. Use [verse] in all SYNOPSIS sections for consistency. Also remove the blank lines from git-fetch.txt and git-rebase.txt to align with the other man pages. In the case of git-rebase.txt, which already uses [verse], the blank line makes the [verse] not apply to the last line, so removing the blank line also makes the formatting within the document more consistent. While at it, add single quotes to 'git cvsimport' for consistency with other commands. Signed-off-by: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
82 lines
2.3 KiB
Text
82 lines
2.3 KiB
Text
git-tar-tree(1)
|
|
===============
|
|
|
|
NAME
|
|
----
|
|
git-tar-tree - Create a tar archive of the files in the named tree object
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'git tar-tree' [--remote=<repo>] <tree-ish> [ <base> ]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
THIS COMMAND IS DEPRECATED. Use 'git archive' with `--format=tar`
|
|
option instead (and move the <base> argument to `--prefix=base/`).
|
|
|
|
Creates a tar archive containing the tree structure for the named tree.
|
|
When <base> is specified it is added as a leading path to the files in the
|
|
generated tar archive.
|
|
|
|
'git tar-tree' behaves differently when given a tree ID versus when given
|
|
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.
|
|
It can be extracted using 'git get-tar-commit-id'.
|
|
|
|
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.
|
|
|
|
CONFIGURATION
|
|
-------------
|
|
|
|
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.
|
|
|
|
EXAMPLES
|
|
--------
|
|
git tar-tree HEAD junk | (cd /var/tmp/ && tar xf -)::
|
|
|
|
Create a tar archive that contains the contents of the
|
|
latest commit on the current branch, and extracts it in
|
|
`/var/tmp/junk` directory.
|
|
|
|
git tar-tree v1.4.0 git-1.4.0 | gzip >git-1.4.0.tar.gz::
|
|
|
|
Create a tarball for v1.4.0 release.
|
|
|
|
git tar-tree v1.4.0{caret}\{tree\} git-1.4.0 | gzip >git-1.4.0.tar.gz::
|
|
|
|
Create a tarball for v1.4.0 release, but without a
|
|
global extended pax header.
|
|
|
|
git tar-tree --remote=example.com:git.git v1.4.0 >git-1.4.0.tar::
|
|
|
|
Get a tarball v1.4.0 from example.com.
|
|
|
|
git tar-tree HEAD:Documentation/ git-docs > git-1.4.0-docs.tar::
|
|
|
|
Put everything in the current head's Documentation/ directory
|
|
into 'git-1.4.0-docs.tar', with the prefix 'git-docs/'.
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|