git-annex-satisfy(1)

📦
version 10.20261026 · 2 versions
  • 10.20261026 · alpine 3.24, arch rolling, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 10.20240129 · ubuntu noble
, in alpine 3.24, arch rolling, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ git-annex-satisfy ✨

okay bestie, this is from the git-annex manual, and it's the page for git-annex-satisfy — the command that just... transfers and drops content as configured. no drama, no notes, it simply does the thing. 💅

🌸 NAME 🌸

git-annex-satisfy — transfer and drop content as configured 🫶

🦋 SYNOPSIS 🦋

git annex satisfy [remote ...]

💖 DESCRIPTION 💖

so what this does is transfer and drop content of annexed files, working toward satisfying the preferred content settings of the local repository and the remotes. it's giving "get everyone's vibes aligned" energy. ✨

it does the exact same thing as git-annex sync --content, except:

  • no pulling and pushing of git repositories 😌
  • no changing the trees that are imported to or exported from special remotes 🚫
lowkey important note: this command (just like git-annex-sync or git-annex-assist) does not work specifically toward satisfying the git-annex-numcopies setting — unless the preferred content setting of the local repository is literally written to do that, like by using eg approxlackingcopies=1. so don't come for it, it's just not its job. 💀

🎀 OPTIONS 🎀

  • [remote] — by default this command operates on all remotes, except for remotes that have remote.<name>.annex-sync set to false. if you specify the names of remotes (or remote groups), you get to control exactly which ones it operates on. main character energy, you pick the guest list. 👑
  • --content-of=path -C path — operate on only the files in the specified path. the default is to operate on all files in the working tree. you can repeat this option multiple times with different paths, so go off. 🙈
heads up: this option does not prevent exporting other files to an "exporttree=yes" remote. so like, it's not a full lockdown, okay?
  • --jobs=N -JN — enables parallel processing 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. multithreading slay. 🔥
  • --all -A — usually this command operates on annexed files in the current branch. this option makes it operate on all available versions of all annexed files (when preferred content settings allow). 🌈
note that preferred content settings that use include= or exclude= will only match the version of files currently in the work tree — not past versions of files. so, yeah, caveat. 💀

also, the git-annex-common-options(1) can be used. you know the drill. ✨

💜 SEE ALSO 💜

🌟 AUTHOR 🌟

Joey Hess <id@joeyh.name> — icon, legend, the moment. 👑

and that's the whole page, bestie 🎀 this was git-annex-satisfy(1) from the General Commands Manual, and yes the footer said git-annex-satisfy(1) again because manpages love being extra like that. go satisfy some preferred content, you got this. 💖✨

📦 where this page comes from