git-annex-move(1)

📦
version 10.20261026 · 4 versions
, in alpine 3.24, arch rolling

💖 NAME 💖

git-annex-move(1) is from the General Commands Manual, bestie, and it's literally the page for moving content of files to/from another repository. ✨

🦋 SYNOPSIS 🦋

git annex move [path ...] [--from=remote|--to=remote|--to=here]

🌸 DESCRIPTION 🌸

Okay so this command moves the content of files from or to another repository. That's the whole main-character job. 💅

With no parameters, it operates on all annexed files in the current directory. You can also specify paths of files or directories to operate on. Easy.

✨ OPTIONS ✨

  • --from=remote — Move the content of files from the specified remote to the local repository.
  • --to=remote — Move the content of files from the local repository to the specified remote.
  • --to=here — Move the content of files from all reachable remotes to the local repository.
  • --from=remote1 --to=remote2 — Move the content of files that are in remote1 to remote2. Does not change what is stored in the local repository. This is implemented by first downloading the content from remote1 to the local repository (if not already present), then sending it to remote2, and then deleting the content from the local repository (if it was not present to start with).
  • --from-anywhere --to=remote — Move to the remote the files from the local repository and from all reachable remotes.
  • --force — 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. Setting this to "cpus" will run one job per CPU core. Note that when using --from with --to, twice this many jobs will run at once, evenly split between the two remotes.
  • --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.
  • --branch=ref — Operate on files in the specified branch or treeish.
  • --unused — Operate on files found by last run of git-annex unused.
  • --failed — Operate on files that have recently failed to be transferred.
  • --key=keyname — Use this option to move a specified key.
  • matching options — The git-annex-matching-options(1) can be used to control what to move.
  • --batch — 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 does not match specified matching options, 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.
  • --batch-keys — This is like --batch but the lines read from stdin are parsed as keys.
  • -z — Makes batch input be delimited by nulls instead of the usual newlines.
  • --json — Enable JSON output. This is intended to be parsed by programs that use git-annex. Each line of output is a JSON object.
  • --json-progress — Include progress objects in JSON output.
  • --json-error-messages — Messages that would normally be output to standard error are included in the JSON instead.

Also the git-annex-common-options(1) can be used.

👑 SEE ALSO 👑

🎀 AUTHOR 🎀

Joey Hess <id@joeyh.name>

That's the whole git-annex-move(1) page, bestie — the footer/source/version/date tea was just the git-annex-move(1) line, no extra date or version deets, so that's the vibe. 💖✨🫶

📦 where this page comes from