git-annex-put(1)

📦 version 10.20261026, in alpine 3.24, arch rolling

💖 git-annex-put — sending ur files to other repos, no cap 💖

okay so this is the git-annex-put(1) page from the General Commands Manual, and we're gonna make it make sense bestie 🫶

✨ NAME ✨

git-annex-put — send content of files to other repositories 🚀

✨ SYNOPSIS ✨

git annex put [path ...]

✨ DESCRIPTION ✨

So basically: this sends the content of ur annexed files off to remotes. By default, files get sent to all remotes — with one little exception, which is certain special remotes that have to be populated using git-annex export instead. iykyk 💅

If you give it no parameters at all, it operates on all annexed files in the current directory. You can specify paths of files or directories to operate on if you wanna be specific about it. 🎀

🌸 OPTIONS 🌸

  • --wanted, -w — sends files only to remotes that actually want them. like a vibe check for remotes 💅 see git-annex-preferred-content(1)
  • --auto — only sends files to remotes that want them, or when there aren't yet the desired number of copies. lowkey the chill option ✨
  • --fast — only sends files to remotes with the lowest annex-cost value configured. speedrun strats 🔥
  • --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. iconic multi-tasking behavior 👑

  • --all, -A — instead of specifying a filename or path to send, this option can be used to send all available versions of all files. the "do everything" button fr fr

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 the last run of git-annex unused. the leftovers arc 😭
  • --failed — operate on files that have recently failed to be transferred. second-chance era 💖
  • --key=keyname — use this option to send a specified key. just one specific little guy 🔑
  • matching options — the git-annex-matching-options(1) can be used to specify what to send. filter away bestie 🦋
  • --batch — enables batch mode, where lines containing names of files to send are read from stdin. conveyor belt energy 🎀

As each specified file is processed, the usual progress output is displayed. If a file's content does not need to be sent, or it does not match specified matching options, or it is not an annexed file, a blank line is output in response instead. (not me getting a blank line back 🙈)

Since the usual output while sending a file is verbose and not machine-parseable, you may want to use --json in combination with --batch. pro tip from the manpage itself, periodt 💅

  • --batch-keys — this is like --batch but the lines read from stdin are parsed as keys. same energy, different input 🔑
  • -z — makes batch input be delimited by nulls instead of the usual newlines. null bytes on main 🧚
  • --json — enable JSON output. This is intended to be parsed by programs that use git-annex. Each line of output is a JSON object. machine-readable slay 🤖✨
  • --json-progress — include progress objects in JSON output. so you can watch the progress in JSON 📊
  • --json-error-messages — messages that would normally be output to standard error are included in the JSON instead. errors but make them JSON 💀
  • Also the git-annex-common-options(1) can be used. the usual suspects 🌈

🦋 SEE ALSO 🦋

👑 AUTHOR 👑

Joey Hess <id@joeyh.name> — actual legend, no cap 💜

okay that's the whole page bestie!! this one's git-annex-put(1) straight outta the General Commands Manual — same page, same title, all the same facts, just with the vibes upgraded 💅✨ go send some files, you got this 🫶💖

📦 where this page comes from