mirror of
https://github.com/git/git
synced 2024-10-31 00:45:12 +00:00
5d2fc9135a
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>
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
|