]> git.ipfire.org Git - thirdparty/git.git/blame - Documentation/git-archive.txt
Merge branch 'kk/maint-prefix-in-config-mak'
[thirdparty/git.git] / Documentation / git-archive.txt
CommitLineData
4df096a5
FBH
1git-archive(1)
2==============
3
4NAME
5----
29cf5e12 6git-archive - Create an archive of files from a named tree
4df096a5
FBH
7
8
9SYNOPSIS
10--------
e448ff87 11[verse]
82d97da3 12'git archive' [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
05d3951e 13 [-o | --output=<file>] [--worktree-attributes]
c005c6aa 14 [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
62b4698e 15 [<path>...]
4df096a5
FBH
16
17DESCRIPTION
18-----------
19Creates an archive of the specified format containing the tree
42b5f869
JA
20structure for the named tree, and writes it out to the standard
21output. If <prefix> is specified it is
4df096a5
FBH
22prepended to the filenames in the archive.
23
0b444cdb 24'git archive' behaves differently when given a tree ID versus when
4df096a5 25given a commit ID or tag ID. In the first case the current time is
3f7cdf32 26used as the modification time of each file in the archive. In the latter
4df096a5
FBH
27case the commit time as recorded in the referenced commit object is
28used instead. Additionally the commit ID is stored in a global
29extended pax header if the tar format is used; it can be extracted
0b444cdb 30using 'git get-tar-commit-id'. In ZIP files it is stored as a file
4df096a5
FBH
31comment.
32
33OPTIONS
34-------
35
36--format=<fmt>::
0f4b377c
DP
37 Format of the resulting archive: 'tar' or 'zip'. If this option
38 is not given, and the output file is specified, the format is
39 inferred from the filename if possible (e.g. writing to "foo.zip"
40 makes the output to be in the zip format). Otherwise the output
41 format is `tar`.
4df096a5 42
3240240f
SB
43-l::
44--list::
4df096a5
FBH
45 Show all available formats.
46
3240240f
SB
47-v::
48--verbose::
27c8f8cd
AR
49 Report progress to stderr.
50
4df096a5
FBH
51--prefix=<prefix>/::
52 Prepend <prefix>/ to each filename in the archive.
53
05d3951e 54-o <file>::
aec0c1bb
CMDV
55--output=<file>::
56 Write the archive to <file> instead of stdout.
57
ba053ea9
NTND
58--worktree-attributes::
59 Look for attributes in .gitattributes in working directory too.
60
4df096a5 61<extra>::
3f7cdf32 62 This can be any options that the archiver backend understands.
e8daf78a 63 See next section.
4df096a5
FBH
64
65--remote=<repo>::
3f7cdf32 66 Instead of making a tar archive from the local repository,
4df096a5
FBH
67 retrieve a tar archive from a remote repository.
68
c005c6aa
MB
69--exec=<git-upload-archive>::
70 Used with --remote to specify the path to the
ba020ef5 71 'git-upload-archive' on the remote side.
c005c6aa 72
4df096a5
FBH
73<tree-ish>::
74 The tree or commit to produce an archive for.
75
62b4698e 76<path>::
165ca621
RS
77 Without an optional path parameter, all files and subdirectories
78 of the current working directory are included in the archive.
79 If one or more paths are specified, only these are included.
4df096a5 80
e8daf78a
FBH
81BACKEND EXTRA OPTIONS
82---------------------
83
84zip
85~~~
86-0::
87 Store the files instead of deflating them.
88-9::
89 Highest and slowest compression level. You can specify any
90 number from 1 to 9 to adjust compression speed and ratio.
91
92
4df096a5
FBH
93CONFIGURATION
94-------------
4df096a5 95
687157c7
RS
96tar.umask::
97 This variable can be used to restrict the permission bits of
98 tar archive entries. The default is 0002, which turns off the
99 world write bit. The special value "user" indicates that the
100 archiving user's umask will be used instead. See umask(2) for
810cae53
RS
101 details. If `--remote` is used then only the configuration of
102 the remote repository takes effect.
4df096a5 103
8d1b9d23
RL
104ATTRIBUTES
105----------
106
107export-ignore::
108 Files and directories with the attribute export-ignore won't be
109 added to archive files. See linkgit:gitattributes[5] for details.
110
111export-subst::
112 If the attribute export-subst is set for a file then git will
113 expand several placeholders when adding this file to an archive.
114 See linkgit:gitattributes[5] for details.
115
9b4c8b0a
JH
116Note that attributes are by default taken from the `.gitattributes` files
117in the tree that is being archived. If you want to tweak the way the
118output is generated after the fact (e.g. you committed without adding an
119appropriate export-ignore in its `.gitattributes`), adjust the checked out
fc7642a0 120`.gitattributes` file as necessary and use `--worktree-attributes`
9b4c8b0a
JH
121option. Alternatively you can keep necessary attributes that should apply
122while archiving any tree in your `$GIT_DIR/info/attributes` file.
123
4df096a5
FBH
124EXAMPLES
125--------
126git archive --format=tar --prefix=junk/ HEAD | (cd /var/tmp/ && tar xf -)::
127
128 Create a tar archive that contains the contents of the
3f7cdf32 129 latest commit on the current branch, and extract it in the
4df096a5
FBH
130 `/var/tmp/junk` directory.
131
132git archive --format=tar --prefix=git-1.4.0/ v1.4.0 | gzip >git-1.4.0.tar.gz::
133
134 Create a compressed tarball for v1.4.0 release.
135
136git archive --format=tar --prefix=git-1.4.0/ v1.4.0{caret}\{tree\} | gzip >git-1.4.0.tar.gz::
137
138 Create a compressed tarball for v1.4.0 release, but without a
139 global extended pax header.
140
141git archive --format=zip --prefix=git-docs/ HEAD:Documentation/ > git-1.4.0-docs.zip::
142
143 Put everything in the current head's Documentation/ directory
144 into 'git-1.4.0-docs.zip', with the prefix 'git-docs/'.
145
0f4b377c
DP
146git archive -o latest.zip HEAD::
147
148 Create a Zip archive that contains the contents of the latest
149 commit on the current branch. Note that the output format is
150 inferred by the extension of the output file.
151
8d1b9d23
RL
152
153SEE ALSO
154--------
155linkgit:gitattributes[5]
156
4df096a5
FBH
157GIT
158---
9e1f0a85 159Part of the linkgit:git[1] suite