1git-annex-move(1) General Commands Manual git-annex-move(1)
2
3
4
6 git-annex-move - move content of files to/from another repository
7
9 git annex move [path ...] [--from=remote|--to=remote|--to=here]
10
12 Moves the content of files from or to another remote.
13
14 With no parameters, operates on all annexed files in the current direc‐
15 tory. Paths of files or directories to operate on can be specified.
16
18 --from=remote
19
20 Move the content of files from the specified remote to the local
21 repository.
22
23 --to=remote
24 Move the content of files from the local repository to the spec‐
25 ified remote.
26
27 --to=here
28 Move the content of files from all reachable remotes to the lo‐
29 cal repository.
30
31 --force
32 Override numcopies and required content checking, and always re‐
33 move files from the source repository once the destination
34 repository has a copy.
35
36 Note that, even without this option, you can move the content of
37 a file from one repository to another when numcopies is not sat‐
38 isfied, as long as the move does not result in there being fewer
39 copies.
40
41 --jobs=N -JN
42 Enables parallel transfers with up to the specified number of
43 jobs running at once. For example: -J10
44
45 Setting this to "cpus" will run one job per CPU core.
46
47 --all -A
48 Rather than specifying a filename or path to move, this option
49 can be used to move all available versions of all files.
50
51 This is the default behavior when running git-annex in a bare
52 repository.
53
54 --branch=ref
55 Operate on files in the specified branch or treeish.
56
57 --unused
58 Operate on files found by last run of git-annex unused.
59
60 --failed
61 Operate on files that have recently failed to be transferred.
62
63 --key=keyname
64 Use this option to move a specified key.
65
66 --fast When moving content to a remote, avoid a round trip to check if
67 the remote already has content. This can be faster, but might
68 skip moving content to the remote in some cases.
69
70 matching options
71 The git-annex-matching-options(1) can be used to control what to
72 move.
73
74 --batch
75 Enables batch mode, in which lines containing names of files to
76 move are read from stdin.
77
78 As each specified file is processed, the usual progress output
79 is displayed. If a file's content does not need to be moved, or
80 it does not match specified matching options, or it is not an
81 annexed file, a blank line is output in response instead.
82
83 Since the usual output while moving a file is verbose and not
84 machine-parseable, you may want to use --json in combination
85 with --batch.
86
87 --batch-keys
88 This is like --batch but the lines read from stdin are parsed as
89 keys.
90
91 -z Makes batch input be delimited by nulls instead of the usual
92 newlines.
93
94 --json Enable JSON output. This is intended to be parsed by programs
95 that use git-annex. Each line of output is a JSON object.
96
97 --json-progress
98 Include progress objects in JSON output.
99
100 --json-error-messages
101 Messages that would normally be output to standard error are in‐
102 cluded in the json instead.
103
104 Also the git-annex-common-options(1) can be used.
105
107 git-annex(1)
108
109 git-annex-get(1)
110
111 git-annex-copy(1)
112
113 git-annex-drop(1)
114
116 Joey Hess <id@joeyh.name>
117
118 git-annex-move(1)