1git-annex-get(1) General Commands Manual git-annex-get(1)
2
6 git-annex-get - make content of annexed files available
7
9 git annex get [path ...]
10
12 Makes the content of annexed files available in this repository. This
13 will involve copying them from a remote repository, or downloading
14 them, or transferring them from some kind of key-value store.
15
17 --auto
18 Rather than getting all files, get only files that don't yet
20 have the desired number of copies, or that are preferred content
21 of the repository. See git-annex-preferred-content(1)
22 --from=remote
24 Normally git-annex will choose which remotes to get the content
25 from, preferring remotes with lower costs. Use this option to
26 specify which remote to use.
27 Any files that are not available on the remote will be silently
29 skipped.
30 --jobs=N -JN
32 Enables parallel download with up to the specified number of
33 jobs running at once. For example: -J10
34 When files can be downloaded from multiple remotes, enabling
36 parallel downloads will split the load between the remotes. For
37 example, if the files are available on remotes A and B, then one
38 file will be downloaded from A, and another file will be down‐
39 loaded from B in parallel. (Remotes with lower costs are still
40 preferred over higher cost remotes.)
41 file matching options
43 The git-annex-matching-options(1) can be used to specify files
44 to get.
45 --incomplete
47 Resume any incomplete downloads of files that were started and
48 interrupted at some point previously. Useful to pick up where
49 you left off ... when you don't quite remember where that was.
50 These incomplete files are the same ones that are listed as
52 unused temp files by git-annex-unused(1).
53 Note that the git-annex key will be displayed when downloading,
55 as git-annex does not know the associated file, and the associ‐
56 ated file may not even be in the current git working directory.
57 --all -A
59 Rather than specifying a filename or path to get, this option
60 can be used to get all available versions of all files.
61 This is the default behavior when running git-annex in a bare
63 repository.
64 --branch=ref
66 Operate on files in the specified branch or treeish.
67 --unused
69 Operate on files found by last run of git-annex unused.
70 --failed
72 Operate on files that have recently failed to be transferred.
73 Not to be confused with --incomplete which resumes only down‐
75 loads that managed to transfer part of the content of a file.
76 --key=keyname
78 Use this option to get a specified key.
79 --batch
81 Enables batch mode, in which lines containing names of files to
82 get are read from stdin.
83 As each specified file is processed, the usual progress output
85 is displayed. If the specified file's content is already
86 present, or it does not match specified matching options, or it
87 is not an annexed file, a blank line is output in response
88 instead.
89 Since the usual output while getting a file is verbose and not
91 machine-parseable, you may want to use --json in combination
92 with --batch.
93 -z Makes the --batch input be delimited by nulls instead of the
95 usual newlines.
96 --json Enable JSON output. This is intended to be parsed by programs
98 that use git-annex. Each line of output is a JSON object.
99 --json-progress
101 Include progress objects in JSON output.
102 --json-error-messages
104 Messages that would normally be output to standard error are
105 included in the json instead.
106
108 git-annex(1)
109 git-annex-drop(1)
111 git-annex-copy(1)
113 git-annex-move(1)
115
117 Joey Hess <id@joeyh.name>
118 git-annex-get(1)