git‐annex‐move − move content of files to/from another

git annex move [path ...]

Moves the content of files from or to another remote.


     Move the content of files from the specified remote to
     the local repository.

     Move the content of files from the local repository to
     the specified remote.

     Move the content of files from all reachable remotes to
     the local repository.

     Override numcopies and required content checking, and
     always remove files from the source repository once the
     destination repository has a copy.

     Note that, even without this option, you can move the
     content of a file from one repository to another when
     numcopies is not satisfied, as long as the move does
     not result in there being fewer copies.

−−jobs=N −JN
     Enables parallel transfers with up to the specified
     number of jobs running at once. For example: −J10

−−all −A
     Rather than specifying a filename or path to move, this
     option can be used to move all available versions of
     all files.

     This is the default behavior when running git‐annex in
     a bare repository.


     Operate on files in the specified branch or treeish.

     Operate on files found by last run of git‐annex unused.

     Operate on files that have recently failed to be

     Use this option to move a specified key.

     When moving content to a remote, avoid a round trip to
     check if the remote already has content. This can be
     faster, but might skip moving content to the remote in
     some cases.

file matching options
     The git‐annex−matching−options(1) can be used to
     specify files to move.

     Enables batch mode, in which lines containing names of
     files to move are read from stdin.

     As each specified file is processed, the usual progress
     output is displayed. If a file’s content does not need
     to be moved or it is not an annexed file, a blank line
     is output in response instead.

     Since the usual output while moving a file is verbose
     and not machine−parseable, you may want to use −−json
     in combination with −−batch.

     Enable JSON output. This is intended to be parsed by
     programs that use git‐annex. Each line of output is a
     JSON object.

     Include progress objects in JSON output.


     Messages that would normally be output to standard
     error are included in the json instead.





Joey Hess <>