1git-annex-move(1) General Commands Manual git-annex-move(1)
2
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 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 Move the content of files from the specified remote to the local
21 repository.
22 --to=remote
24 Move the content of files from the local repository to the spec‐
25 ified remote.
26 --to=here
28 Move the content of files from all reachable remotes to the lo‐
29 cal repository.
30 --from=remote1 --to=remote2
32 Move the content of files that are in remote1 to remote2. Does
33 not change what is stored in the local repository.
34 This is implemented by first downloading the content from re‐
36 mote1 to the local repository (if not already present), then
37 sending it to remote2, and then deleting the content from the
38 local repository (if it was not present to start with).
39 --force
41 Override numcopies and required content checking, and always re‐
42 move files from the source repository once the destination
43 repository has a copy.
44 Note that, even without this option, you can move the content of
46 a file from one repository to another when numcopies is not sat‐
47 isfied, as long as the move does not result in there being fewer
48 copies.
49 --jobs=N -JN
51 Enables parallel transfers with up to the specified number of
52 jobs running at once. For example: -J10
53 Setting this to "cpus" will run one job per CPU core.
55 Note that when using --from with --to, twice this many jobs will
57 run at once, evenly split between the two remotes.
58 --all -A
60 Rather than specifying a filename or path to move, this option
61 can be used to move all available versions of all files.
62 This is the default behavior when running git-annex in a bare
64 repository.
65 --branch=ref
67 Operate on files in the specified branch or treeish.
68 --unused
70 Operate on files found by last run of git-annex unused.
71 --failed
73 Operate on files that have recently failed to be transferred.
74 --key=keyname
76 Use this option to move a specified key.
77 matching options
79 The git-annex-matching-options(1) can be used to control what to
80 move.
81 --batch
83 Enables batch mode, in which lines containing names of files to
84 move are read from stdin.
85 As each specified file is processed, the usual progress output
87 is displayed. If a file's content does not need to be moved, or
88 it does not match specified matching options, or it is not an
89 annexed file, a blank line is output in response instead.
90 Since the usual output while moving a file is verbose and not
92 machine-parseable, you may want to use --json in combination
93 with --batch.
94 --batch-keys
96 This is like --batch but the lines read from stdin are parsed as
97 keys.
98 -z Makes batch input be delimited by nulls instead of the usual
100 newlines.
101 --json Enable JSON output. This is intended to be parsed by programs
103 that use git-annex. Each line of output is a JSON object.
104 --json-progress
106 Include progress objects in JSON output.
107 --json-error-messages
109 Messages that would normally be output to standard error are in‐
110 cluded in the JSON instead.
111 Also the git-annex-common-options(1) can be used.
113
115 git-annex(1)
116 git-annex-get(1)
118 git-annex-copy(1)
120 git-annex-drop(1)
122
124 Joey Hess <id@joeyh.name>
125 git-annex-move(1)