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