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 --all -A
43 Rather than specifying a filename or path to move, this option
44 can be used to move all available versions of all files.
45
46 This is the default behavior when running git-annex in a bare
47 repository.
48
49 --branch=ref
50 Operate on files in the specified branch or treeish.
51
52 --unused
53 Operate on files found by last run of git-annex unused.
54
55 --failed
56 Operate on files that have recently failed to be transferred.
57
58 --key=keyname
59 Use this option to move a specified key.
60
61 --fast When moving content to a remote, avoid a round trip to check if
62 the remote already has content. This can be faster, but might
63 skip moving content to the remote in some cases.
64
65 file matching options
66 The git-annex-matching-options(1) can be used to specify files
67 to move.
68
69 --batch
70 Enables batch mode, in which lines containing names of files to
71 move are read from stdin.
72
73 As each specified file is processed, the usual progress output
74 is displayed. If a file's content does not need to be moved, or
75 it does not match specified matching options, or it is not an
76 annexed file, a blank line is output in response instead.
77
78 Since the usual output while moving a file is verbose and not
79 machine-parseable, you may want to use --json in combination
80 with --batch.
81
82 -z Makes the --batch input be delimited by nulls instead of the
83 usual newlines.
84
85 --json Enable JSON output. This is intended to be parsed by programs
86 that use git-annex. Each line of output is a JSON object.
87
88 --json-progress
89 Include progress objects in JSON output.
90
91 --json-error-messages
92 Messages that would normally be output to standard error are
93 included in the json instead.
94
96 git-annex(1)
97
98 git-annex-get(1)
99
100 git-annex-copy(1)
101
102 git-annex-drop(1)
103
105 Joey Hess <id@joeyh.name>
106
107 git-annex-move(1)