neulab/tldr huggingface dataset:
git push mothership master:satellite/master dev:satellite/dev Use the source ref that matches master (e.g.  refs/heads/master) to update the ref that matches satellite/master (most probably refs/remotes/satellite/master) in the mothership repository; do the same for dev and satellite/dev.
See the section describing <refspec>...  above for a discussion of the matching semantics.
This is to emulate git fetch run on the mothership using git push that is run in the opposite direction in order to integrate the work done on satellite, and is often necessary when you can only make connection in one way (i.e. satellite can ssh into mothership but mothership cannot initiate connection to satellite because the latter is behind a firewall or does not run sshd).
After running this git push on the satellite machine, you would ssh into the mothership and run git merge there to complete the emulation of git pull that were run on mothership to pull changes made on satellite.
git push origin HEAD:master Push the current branch to the remote ref matching master in the origin repository. This form is convenient to push the current branch without thinking about its local name.
git push origin master:refs/heads/experimental Create the branch experimental in the origin repository by copying the current master branch. This form is only needed to create a new branch or tag in the remote repository when the local name and the remote name are different; otherwise, the ref name on its own will work.
git push origin :experimental Find a ref that matches experimental in the origin repository (e.g. refs/heads/experimental), and delete it.
git push origin +dev:master Update the origin repository’s master branch with the dev branch, allowing non-fast-forward updates.  This can leave unreferenced commits dangling in the origin repository.  Consider the following situation, where a fast-forward is not possible:
o---o---o---A---B  origin/master \ X---Y---Z  dev
The above command would change the origin repository to
A---B  (unnamed branch) / o---o---o---X---Y---Z  master
Commits A and B would no longer belong to a branch with a symbolic name, and so would be unreachable. As such, these commits would be removed by a git gc command on the origin repository.
The fetch and push protocols are not designed to prevent one side from stealing data from the other repository that was not intended to be shared. If you have private data that you need to protect from a malicious peer, your best option is to store it in another repository. This applies to both clients and servers. In particular, namespaces on a server are not effective for read access control; you should only grant read access to a namespace to clients that you would trust with read access to the entire repository.
The known attack vectors are as follows:
1. The victim sends "have" lines advertising the IDs of objects it has that are not explicitly intended to be shared but can be used to optimize the transfer if the peer also has them. The attacker chooses an object ID X to steal and sends a ref to X, but isn’t required to send the content of X because the victim already has it. Now the victim believes that the attacker has X, and it sends the content of X back to the attacker later. (This attack is most straightforward for a client to perform on a server, by creating a ref to X in the namespace the client has access to and then fetching it. The most likely way for a server to perform it on a client is to "merge" X into a public branch and hope that the user does additional work on this branch and pushes it back to the server without noticing the merge.)
2. As in #1, the attacker chooses an object ID X to steal. The victim sends an object Y that the attacker already has, and the attacker falsely claims to have X and not Y, so the victim sends Y as a delta against X. The delta reveals regions of X that are similar to Y to the attacker.
aapt(1)                      General Commands Manual                     aapt(1)
aapt - Android Asset Packaging Tool
aapt command [ options ] files ...
aapt l[ist] [-v] [-a] file.{zip,jar,apk} List contents of Zip-compatible archive.
aapt d[ump] [--values] WHAT file.{apk} [asset [asset ...]]
strings        Print the contents of the resource table string pool in the APK. badging        Print the label and icon for the app declared in APK. permissions    Print the permissions from the APK. resources      Print the resource table from the APK. configurations Print the configurations in the APK. xmltree        Print the compiled xmls in the given assets. xmlstrings     Print the strings of the given compiled xml assets.
aapt p[ackage] [-d] [-f] [-m] [-u] [-v] [-x] [-z] [-M AndroidManifest.xml]
[-0 extension [-0 extension ...]] [-g tolerance] [-j jarfile] [--debug-mode] [--min-sdk-version VAL] [--target-sdk-version VAL] [--app-version VAL] [--app-version-name TEXT] [--custom-package VAL] [--rename-manifest-package PACKAGE] [--rename-instrumentation-target-package PACKAGE] [--utf16] [--auto-add-overlay] [--max-res-version VAL] [-I base-package [-I base-package ...]] [-A asset-source-dir]  [-G class-list-file] [-P public- definitions-file] [-S resource-sources [-S resource-sources ...]] [-F apk-file] [-J R-file-dir] [--product product1,product2,...] [-c CONFIGS] [--preferred-configurations CONFIGS] [raw-files-dir [raw-files-dir] ...] [--output-text-symbols DIR]
Package the android resources.  It will read assets and resources that are supplied with the -M -A -S or raw-files-dir arguments.  The -J -P -F and -R options control which files are output.
aapt r[emove] [-v] file.{zip,jar,apk} file1 [file2 ...] Delete specified files from Zip-compatible archive.
aapt a[dd] [-v] file.{zip,jar,apk} file1 [file2 ...] Add specified files to Zip-compatible archive.
aapt c[runch] [-v] -S resource-sources ... -C output-folder ... Do PNG preprocessing on one or several resource folders and store the results in the output folder.
aapt s[ingleCrunch] [-v] -i input-file -o outputfile Do PNG preprocessing on a single file.
aapt v[ersion] Print program version.
The Android Asset Packaging Tool (aapt) takes your application resource files, such as the AndroidManifest.xml file and the XML files for your Activities, and compiles them. An R.java is also produced so you can reference your resources from your Java code.
A summary of options is included below.
-a     print Android-specific data (resources, manifest) when listing
-c     specify which configurations to include.  The default is all configurations.  The value of the parameter should be a comma separated list of configuration values.  Locales should be specified as either a language or language-region pair.  Some examples: en port,en port,land,en_US
If you put the special locale, zz_ZZ on the list, it will perform pseudolocalization on the default locale, modifying all of the strings so you can look for strings that missed the internationalization process.  For example: port,land,zz_ZZ
-d     one or more device assets to include, separated by commas
-f     force overwrite of existing files
-g     specify a pixel tolerance to force images to grayscale, default 0
-j     specify a jar or zip file containing classes to include
-k     junk path of file(s) added
-m     make package directories under location specified by -J
-u     update existing packages (add new, replace older, remove deleted files)
-v     verbose output
-x     create extending (non-application) resource IDs
-z     require localization of resource attributes marked with localization="suggested"
-A     additional directory in which to find raw asset files
-G     A file to output proguard options into.
-F     specify the apk file to output
-I     add an existing package to base include set
-J     specify where to output R.java resource constant definitions
-M     specify full path to AndroidManifest.xml to include in zip
-P     specify where to output public resource definitions
-S     directory in which to find resources.  Multiple directories will be scanned and the first match found (left to right) will take precedence.
-0     specifies an additional extension for which such files will not be stored compressed in the .apk.  An empty string means to not compress any files at all.
--debug-mode inserts android:debuggable="true" in to the application node of the manifest, making the application debuggable even on production devices.
--min-sdk-version inserts android:minSdkVersion in to manifest.  If the version is 7 or higher, the default encoding for resources will be in UTF-8.
--target-sdk-version inserts android:targetSdkVersion in to manifest.
--max-res-version ignores versioned resource directories above the given value.
--values when used with "dump resources" also includes resource values.
--version-code inserts android:versionCode in to manifest.
--version-name inserts android:versionName in to manifest.
--custom-package generates R.java into a different package.
--extra-packages generate R.java for libraries. Separate libraries with ':'.
--generate-dependencies generate dependency files in the same directories for R.java and resource package
--auto-add-overlay Automatically add resources that are only in overlays.
--preferred-configurations Like the -c option for filtering out unneeded configurations, but only expresses a preference.  If there is no resource available with the preferred configuration then it will not be stripped.
--rename-manifest-package Rewrite the manifest so that its package name is the package name given here.  Relative class names (for example .Foo) will be changed to absolute names with the old package so that the code does not need to change.
--rename-instrumentation-target-package Rewrite the manifest so that all of its instrumentation components target the given package.  Useful when used in conjunction with --rename-manifest-package to fix tests against a package that has been renamed.
--product Specifies which variant to choose for strings that have product variants
--utf16 changes default encoding for resources to UTF-16.  Only useful when API level is set to 7 or higher where the default encoding is UTF-8.
--non-constant-id Make the resources ID non constant. This is required to make an R java class that does not contain the final value but is used to make reusable compiled libraries that need to access resources.
--error-on-failed-insert Forces aapt to return an error if it fails to insert values into the manifest with --debug-mode, --min-sdk-version, --target-sdk- version --version-code and --version-name.  Insertion typically fails if the manifest already defines the attribute.
--output-text-symbols Generates a text file containing the resource symbols of the R class in the specified folder.
--ignore-assets Assets to be ignored.
aapt was written by The Android Open Source Project.
CLOJURE(1)                   General Commands Manual                  CLOJURE(1)
clj, clojure - runners to launch Clojure programs
clj [clj-opts] [-Aaliases] [init-opts] clojure [clj-opts] -X[aliases] my/fn? [kpath v ...] kv-map? clojure [clj-opts] -T[name|aliases] my/fn [kpath v ...] kv-map? clojure [clj-opts] -M[aliases] [init-opts] [main-opts] [args]
The clojure tool is a runner for Clojure programs.  clj is a wrapper for clojure that uses rlwrap to provide a better interactive experience. Users will typically run clj.
You can launch a Clojure REPL by running clj.
See the Deps and CLI Guide below for more complex usage.
The clj and clojure scripts can take three types of options, as shown in the synopsis.  clj-opts are used to build the java-opts and classpath. init-opts refer to Clojure code to execute.  main-opts are options to clojure.main.
clj-opts -Jopt  Pass opt through in java_opts, ex: -J-Xmx512m
-Aaliases Concatenated aliases for REPL execution, ex: -A:dev:mem
-Xaliases fn KPATH V Exec alias to invoke one or more functions that take a map, with keypath/value overrides. Function must either be supplied or be in :exec-fn argmap for alias
-Maliases Exec clojure.main, either from opts in alias or command line
-P     Prepare - download libs, cache classpath without executing
-Sdeps EDN Deps data to use as the last deps file to be merged
-Spath Compute classpath and echo to stdout only
-Scp CP Do NOT compute or cache classpath, use this one instead
-Srepro Ignore the ~/.clojure/deps.edn config file
-Sforce Force recomputation of the classpath (don't use the cache)
-Sverbose Print important path info to console
-Sdescribe Print environment and command parsing info as data
-Sthreads N Set specific number of download threads
-Strace Write a trace.edn file that traces deps expansion
--     Stop parsing dep options and pass remaining arguments to clojure.main
--version Write version to stdout and exit
-version Write version to stderr and exit
init-opts -i, --init path Load a file or resource located at path
-e, --eval string Eval exprs in string; print non-nil values
--report target Report uncaught exception to target: "file" (default), "stderr", or "none", overrides System property clojure.main.report
main-opts -m, --main ns-name Call the -main function from namespace w/args
-r, --repl Run a repl
path   Run a script from a file or resource located at path
-      Run a script from standard input
-h, -?,  --help Print this help message and exit
This script reads configuration from deps.edn files. It will check against deps.edn files in the system root location, the user configuration directory (usually ~/.clojure), and the local directory. Files in each of these locations, if they exist, are merged to form one combined configuration file. The last specified configuration file's options overwrites any earlier files (e.g. local configs take priority).
https://clojure.org/guides/deps_and_cli Deps and CLI Guide
https://clojure.org/reference/deps_and_cli Deps and CLI Reference
https://clojure.org/reference/repl_and_main REPL and Main Entrypoints
https://github.com/clojure/brew-install/blob/1.10.3/CHANGELOG.md Changelog for scripts
https://github.com/clojure/tools.deps.alpha/blob/master/CHANGELOG.md Changelog for tools.deps library
File issues at https://ask.clojure.org under category Libs / tools.deps.alpha.
clojure and clj are maintained by Alex Miller <alex.miller@cognitect.com>.  This man page was written by Elana Hashman <ehashman@debian.org>.
Copyright Â© 2018-2020 Rich Hickey, Alex Miller and contributors.
Distributed under the Eclipse Public License 1.0, the same as Clojure.
git-annex(1)                 General Commands Manual                git-annex(1)
git-annex - manage files with git, without checking their contents in
git annex command [params ...]
git-annex allows managing files with git, without checking the file contents into git. While that may seem paradoxical, it is useful when dealing with files larger than git can currently easily handle, whether due to limitations in memory, checksumming time, or disk space.
Even without file content tracking, being able to manage files with git, move files around and delete files with versioned directory trees, and use branches and distributed clones, are all very handy reasons to use git. And annexed files can co-exist in the same git repository with regularly versioned files, which is convenient for maintaining documents, Makefiles, etc that are associated with annexed files but that benefit from full revision control.
When a file is annexed, its content is moved into a key-value store, and a symlink is made that points to the content. These symlinks are checked into git and versioned like regular files. You can move them around, delete them, and so on. Pushing to another git repository will make git- annex there aware of the annexed file, and it can be used to retrieve its content from the key-value store.
# git annex get video/hackity_hack_and_kaxxt.mov get video/hackity_hack_and_kaxxt.mov (not available) I was unable to access these remotes: server Try making some of these repositories available: 5863d8c0-d9a9-11df-adb2-af51e6559a49  -- my home file server 58d84e8a-d9ae-11df-a1aa-ab9aa8c00826  -- portable USB drive ca20064c-dbb5-11df-b2fe-002170d25c55  -- backup SATA drive failed # sudo mount /media/usb # git remote add usbdrive /media/usb # git annex get video/hackity_hack_and_kaxxt.mov get video/hackity_hack_and_kaxxt.mov (from usbdrive...) ok
# git annex add iso add iso/Debian_5.0.iso ok
# git annex drop iso/Debian_4.0.iso drop iso/Debian_4.0.iso ok
# git annex move iso --to=usbdrive move iso/Debian_5.0.iso (moving to usbdrive...) ok
Display built-in help.
For help on a specific command, use git annex help command
add [path ...] Adds files to the annex.
See git-annex-add(1) for details.
get [path ...] Makes the content of annexed files available in this repository.
See git-annex-get(1) for details.
drop [path ...] Drops the content of annexed files from this repository.
See git-annex-drop(1) for details.
move [path ...] [--from=remote|--to=remote] Moves the content of files from or to another remote.
See git-annex-move(1) for details.
copy [path ...] [--from=remote|--to=remote] Copies the content of files from or to another remote.
See git-annex-copy(1) for details.
status [path ...] Similar to git status --short, displays the status of the files in the working tree.
See git-annex-status(1) for details.
unlock [path ...] Unlock annexed files for modification.
See git-annex-unlock(1) for details.
edit [path ...] This is an alias for the unlock command. May be easier to remember, if you think of this as allowing you to edit an annexed file.
lock [path ...] Use this to undo an unlock command if you don't want to modify the files, or have made modifications you want to discard.
See git-annex-lock(1) for details.
sync [remote ...] Synchronize local repository with remotes.
See git-annex-sync(1) for details.
mirror [path ...] [--to=remote|--from=remote] Mirror content of files to/from another repository.
See git-annex-mirror(1) for details.
addurl [url ...] Downloads each url to its own file, which is added to the annex.
See git-annex-addurl(1) for details.
rmurl file url Record that the file is no longer available at the url.
See git-annex-rmurl(1) for details.
import --from remote branch[:subdir] | [path ...] Add a tree of files to the repository.
See git-annex-import(1) for details.
importfeed [url ...] Imports the contents of podcast feeds into the annex.
See git-annex-importfeed(1) for details.
export treeish --to remote Export content to a remote.
See git-annex-export(1) for details.
undo [filename|directory] ... Undo last change to a file or directory.
See git-annex-undo(1) for details.
multicast Multicast file distribution.
See git-annex-multicast(1) for details.
watch  Watch for changes and autocommit.
See git-annex-watch(1) for details.
assistant Automatically sync folders between devices.
See git-annex-assistant(1) for details.
webapp Opens a web app, that allows easy setup of a git-annex repository, and control of the git-annex assistant. If the assistant is not already running, it will be started.
See git-annex-webapp(1) for details.
remotedaemon Persistant communication with remotes.
See git-annex-remotedaemon(1) for details.
init [description]
Until a repository (or one of its remotes) has been initialized, git-annex will refuse to operate on it, to avoid accidentally using it in a repository that was not intended to have an annex.
See git-annex-init(1) for details.
describe repository description Changes the description of a repository.
See git-annex-describe(1) for details.
initremote name type=value [param=value ...] Creates a new special remote, and adds it to .git/config.
See git-annex-initremote(1) for details.
enableremote name [param=value ...] Enables use of an existing special remote in the current repository.
See git-annex-enableremote(1) for details.
renameremote Renames a special remote.
See git-annex-renameremote(1) for details.
enable-tor Sets up tor hidden service.
See git-annex-enable-tor(1) for details.
numcopies [N] Configure desired number of copies.
See git-annex-numcopies(1) for details.
mincopies [N] Configure minimum number of copies.
See git-annex-mincopies(1) for details.
trust [repository ...] Records that a repository is trusted to not unexpectedly lose content. Use with care.
See git-annex-trust(1) for details.
untrust [repository ...] Records that a repository is not trusted and could lose content at any time.
See git-annex-untrust(1) for details.
semitrust [repository ...] Returns a repository to the default semi trusted state.
See git-annex-semitrust(1) for details.
group repository groupname Add a repository to a group.
See git-annex-group(1) for details.
ungroup repository groupname Removes a repository from a group.
See git-annex-ungroup(1) for details.
wanted repository [expression] Get or set preferred content expression.
See git-annex-wanted(1) for details.
groupwanted groupname [expression] Get or set groupwanted expression.
See git-annex-groupwanted(1) for details.
required repository [expression] Get or set required content expression.
See git-annex-required(1) for details.
schedule repository [expression] Get or set scheduled jobs.
See git-annex-schedule(1) for details.
config Get and set other configuration stored in git-annex branch.
See git-annex-config(1) for details.
vicfg  Opens EDITOR on a temp file containing most of the above configuration settings, as well as a few others, and when it exits, stores any changes made back to the git-annex branch.
See git-annex-vicfg(1) for details.
adjust Switches a repository to use an adjusted branch, which can automatically unlock all files, etc.
See git-annex-adjust(1) for details.
direct Switches a repository to use direct mode. (deprecated)
See git-annex-direct(1) for details.
indirect Switches a repository to use indirect mode. (deprecated)
See git-annex-indirect(1) for details.
fsck [path ...]
Checks the annex consistency, and warns about or fixes any problems found.  This is a good complement to git fsck.
See git-annex-fsck(1) for details.
expire [repository:]time ... Expires repositories that have not recently performed an activity (such as a fsck).
See git-annex-expire(1) for details.
unused Checks the annex for data that does not correspond to any files present in any tag or branch, and prints a numbered list of the data.
See git-annex-unused(1) for details.
dropunused [number|range ...] Drops the data corresponding to the numbers, as listed by the last git annex unused
See git-annex-dropunused(1) for details.
addunused [number|range ...] Adds back files for the content corresponding to the numbers or ranges, as listed by the last git annex unused.
See git-annex-addunused(1) for details.
fix [path ...] Fixes up symlinks that have become broken to again point to annexed content.
See git-annex-fix(1) for details.
merge  Automatically merge changes from remotes.
See git-annex-merge(1) for details.
upgrade Upgrades the repository.
See git-annex-upgrade(1) for details.
dead [repository ...] [--key key] Indicates that a repository or a single key has been irretrievably lost.
See git-annex-dead(1) for details.
forget Causes the git-annex branch to be rewritten, throwing away historical data about past locations of files.
See git-annex-forget(1) for details.
filter-branch Produces a filtered version of the git-annex branch.
See git-annex-filter-branch(1) for details.
repair This can repair many of the problems with git repositories that git fsck detects, but does not itself fix. It's useful if a repository has become badly damaged. One way this can happen is if a repository used by git-annex is on a removable drive that gets unplugged at the wrong time.
See git-annex-repair(1) for details.
p2p    Configure peer-2-Peer links between repositories.
See git-annex-p2p(1) for details.
find [path ...]
Outputs a list of annexed files in the specified path. With no path, finds files in the current directory and its subdirectories.
See git-annex-find(1) for details.
whereis [path ...] Displays information about where the contents of files are located.
See git-annex-whereis(1) for details.
list [path ...] Displays a table of remotes that contain the contents of the specified files. This is similar to whereis but a more compact display.
See git-annex-list(1) for details.
whereused Finds what files use or used a key.
log [path ...] Displays the location log for the specified file or files, showing each repository they were added to ("+") and removed from ("-").
See git-annex-log(1) for details.
info [directory|file|remote|uuid ...] Displays statistics and other information for the specified item, which can be a directory, or a file, or a remote, or the uuid of a repository.
When no item is specified, displays statistics and information for the repository as a whole.
See git-annex-info(1) for details.
version Shows the version of git-annex, as well as repository version information.
See git-annex-version(1) for details.
map    Generate map of repositories.
See git-annex-map(1) for details.
inprogress Access files while they're being downloaded.
See git-annex-inprogress(1) for details.
metadata [path ...]
The content of an annexed file can have any number of metadata fields attached to it to describe it. Each metadata field can in turn have any number of values.
This command can be used to set metadata, or show the currently set metadata.
See git-annex-metadata(1) for details.
view [tag ...] [field=value ...] [field=glob ...] [!tag ...] [field!=value ...] Uses metadata to build a view branch of the files in the current branch, and checks out the view branch. Only files in the current branch whose metadata matches all the specified field values and tags will be shown in the view.
See git-annex-view(1) for details.
vpop [N] Switches from the currently active view back to the previous view. Or, from the first view back to original branch.
See git-annex-vpop(1) for details.
vfilter [tag ...] [field=value ...] [!tag ...] [field!=value ...] Filters the current view to only the files that have the specified field values and tags.
See git-annex-vfilter(1) for details.
vadd [field=glob ...] [field=value ...] [tag ...] Changes the current view, adding an additional level of directories to categorize the files.
vcycle When a view involves nested subdirectories, this cycles the order.
See git-annex-vcycle(1) for details.
migrate [path ...]
Changes the specified annexed files to use a different key-value backend.
See git-annex-migrate(1) for details.
reinject src dest Moves the src file into the annex as the content of the dest file. This can be useful if you have obtained the content of a file from elsewhere and want to put it in the local annex.
See git-annex-reinject(1) for details.
unannex [path ...] Use this to undo an accidental git annex add command. It puts the file back how it was before the add.
See git-annex-unannex(1) for details.
uninit De-initialize git-annex and clean out repository.
See git-annex-uninit(1) for details.
reinit uuid|description Initialize repository, reusing old UUID.
See git-annex-reinit(1) for details.
pre-commit [path ...]
This is meant to be called from git's pre-commit hook. git annex init automatically creates a pre-commit hook using this.
See git-annex-pre-commit(1) for details.
post-receive This is meant to be called from git's post-receive hook. git annex init automatically creates a post-receive hook using this.
See git-annex-post-receive(1) for details.
lookupkey [file ...] Looks up key used for file.
See git-annex-lookupkey(1) for details.
calckey [file ...] Calculates the key that would be used to refer to a file.
See git-annex-calckey(1) for details.
contentlocation [key ..] Looks up location of annexed content for a key.
See git-annex-contentlocation(1) for details.
examinekey [key ...] Print information that can be determined purely by looking at the key.
See git-annex-examinekey(1) for details.
matchexpression Checks if a preferred content expression matches provided data.
See git-annex-matchexpression(1) for details.
fromkey [key file] Manually set up a file in the git repository to link to a specified key.
See git-annex-fromkey(1) for details.
registerurl [key url] Registers an url for a key.
See git-annex-registerurl(1) for details.
unregisterurl [key url] Unregisters an url for a key.
See git-annex-unregisterurl(1) for details.
setkey key file Moves a file into the annex as the content of a key.
See git-annex-setkey(1) for details.
dropkey [key ...] Drops annexed content for specified keys.
See git-annex-dropkey(1) for details.
transferkey key [--from=remote|--to=remote] Transfers a key from or to a remote.
See git-annex-transferkey(1) for details.
transferrer Used internally by git-annex to transfer content.
See git-annex-transferrer(1) for details.
transferkeys Used internally by old versions of the assistant.
setpresentkey key uuid [1|0] This plumbing-level command changes git-annex's records about whether the specified key's content is present in a remote with the specified uuid.
See git-annex-setpresentkey(1) for details.
readpresentkey key uuid Read records of where key is present.
See git-annex-readpresentkey(1) for details.
checkpresentkey key remote Check if key is present in remote.
See git-annex-checkpresentkey(1) for details.
rekey [file key ...] Change keys used for files.
See git-annex-rekey(1) for details.
resolvemerge Resolves a conflicted merge, by adding both conflicting versions of the file to the tree, using variants of their filename. This is done automatically when using git annex sync or git annex merge.
See git-annex-resolvemerge(1) for details.
diffdriver This can be used to make git diff use an external diff driver with annexed files.
See git-annex-diffdriver(1) for details.
smudge This command lets git-annex be used as a git filter driver, allowing annexed files in the git repository to be unlocked at all times, instead of being symlinks.
See git-annex-smudge(1) for details.
findref [ref] Lists files in a git ref. (deprecated)
See git-annex-findref(1) for details.
proxy -- git cmd [options] Bypass direct mode guard. (deprecated)
See git-annex-proxy(1) for details.
This runs git-annex's built-in test suite.
See git-annex-test(1) for details.
testremote remote This tests a remote by generating some random objects and sending them to the remote, then redownloading them, removing them from the remote, etc.
It's safe to run in an existing repository (the repository contents are not altered), although it may perform expensive data transfers.
See git-annex-testremote(1) for details.
fuzztest Generates random changes to files in the current repository, for use in testing the assistant.
See git-annex-fuzztest(1) for details.
benchmark This runs git-annex's built-in benchmarks, if it was built with benchmarking support.
See git-annex-benchmark(1) for details.
In addition to all the commands listed above, more commands can be added to git-annex by dropping commands named like "git-annex-foo" into a directory in the PATH.
Like other git commands, git-annex is configured via .git/config.  These settings, as well as relevant git config settings, are the ones git-annex uses.
(Some of these settings can also be set, across all clones of the repository, using git-annex-config. See its man page for a list.)
annex.uuid A unique UUID for this repository (automatically set).
annex.backend Name of the default key-value backend to use when adding new files to the repository.
This is overridden by annex annex.backend configuration in the .gitattributes files, and by the --backend option.
(This used to be named annex.backends, and that will still be used if set.)
annex.securehashesonly Set to true to indicate that the repository should only use cryptographically secure hashes (SHA2, SHA3) and not insecure hashes (MD5, SHA1) for content.
When this is set, the contents of files using cryptographically insecure hashes will not be allowed to be added to the repository.
Also, git-annex fsck will complain about any files present in the repository that use insecure hashes. And, git-annex import --no-content will refuse to import files from special remotes using insecure hashes.
To configure the behavior in new clones of the repository, this can be set using git-annex-config.
annex.maxextensionlength Maximum length, in bytes, of what is considered a filename extension when adding a file to a backend that preserves filename extensions. The default length is 4, which allows extensions like "jpeg". The dot before the extension is not counted part of its length. At most two extensions at the end of a filename will be preserved, e.g. .gz or .tar.gz .
annex.diskreserve Amount of disk space to reserve. Disk space is checked when transferring content to avoid running out, and additional free space can be reserved via this option, to make space for more important content (such as git commit logs). Can be specified with any commonly used units, for example, "0.5 gb", "500M", or "100 KiloBytes"
The default reserve is 1 megabyte.
annex.skipunknown Set to true to make commands like "git-annex get" silently skip over items that are listed in the command line, but are not checked into git.
Set to false to make it an error for commands like "git-annex get" to be asked to operate on files that are not checked into git.
The default is currently true, but is planned to change to false in a release in 2022.
Note that, when annex.skipunknown is false, a command like "git- annex get ."  will fail if no files in the current directory are checked into git, but a command like "git-annex get" will not fail, because the current directory is not listed, but is implicit. Commands like "git-annex get foo/" will fail if no files in the directory are checked into git, but if at least one file is, it will ignore other files that are not. This is all the same as the behavior of "git-ls files --error-unmatch".
Also note that git-annex skips files that are checked into git, but are not annexed files, this setting does not affect that.
annex.largefiles Used to configure which files are large enough to be added to the annex.  It is an expression that matches the large files, eg "include=*.mp3 or largerthan=500kb" See git- annex-matching-expression(1) for details on the syntax.
Overrides any annex.largefiles attributes in .gitattributes files.
To configure a default annex.largefiles for all clones of the repository, this can be set in git-annex-config(1).
This configures the behavior of both git-annex and git when adding files to the repository. By default, git-annex add adds all files to the annex (except dotfiles), and git add adds files to git (unless they were added to the annex previously).  When annex.largefiles is configured, both git annex add and git add will add matching large files to the annex, and the other files to git.
Other git-annex commands also honor annex.largefiles, including git annex import, git annex addurl, git annex importfeed and the assistant.
annex.dotfiles Normally, dotfiles are assumed to be files like .gitignore, whose content should always be part of the git repository, so they will not be added to the annex. Setting annex.dotfiles to true makes dotfiles be added to the annex the same as any other file.
To annex only some dotfiles, set this and configure annex.largefiles to match the ones you want. For example, to match only dotfiles ending in ".big"
git config annex.largefiles "(include=.*.big or include=*/.*.big) or (exclude=.* and exclude=*/.*)" git config annex.dotfiles true
To configure a default annex.dotfiles for all clones of the repository, this can be set in git-annex-config(1).
annex.gitaddtoannex Setting this to false will prevent git add from adding files to the annex, despite the annex.largefiles configuration.
annex.addsmallfiles Controls whether small files (not matching annex.largefiles) should be checked into git by git annex add. Defaults to true; set to false to instead make small files be skipped.
annex.addunlocked Commands like git-annex add default to adding files to the repository in locked form. This can make them add the files in unlocked form, the same as if git-annex-unlock(1) were run on the files.
This can be set to "true" to add everything unlocked, or it can be a more complicated expression that matches files by name, size, or content. See git-annex-matching-expression(1) for details.
To configure a default annex.addunlocked for all clones of the repository, this can be set in git-annex-config(1).
(Using git add always adds files in unlocked form and it is not affected by this setting.)
When a repository has core.symlinks set to false, or has an adjusted unlocked branch checked out, this setting is ignored, and files are always added to the repository in unlocked form.
annex.numcopies This is a deprecated setting. You should instead use the git annex numcopies command to configure how many copies of files are kept across all repositories, or the annex.numcopies .gitattributes setting.
This config setting is only looked at when git annex numcopies has never been configured, and when there's no annex.numcopies setting in the .gitattributes file.
Note that setting numcopies to 0 is very unsafe.
annex.genmetadata Set this to true to make git-annex automatically generate some metadata when adding files to the repository.
In particular, it stores year, month, and day metadata, from the file's modification date.
When importfeed is used, it stores additional metadata from the feed, such as the author, title, etc.
annex.used-refspec This controls which refs git-annex unused considers to be used. See REFSPEC FORMAT in git-annex-unused(1) for details.
annex.jobs Configure the number of concurrent jobs to run. Default is 1.
Only git-annex commands that support the --jobs option will use this.
Setting this to "cpus" will run one job per CPU core.
When the --batch option is used, this configuration is ignored.
annex.adjustedbranchrefresh When git-annex-adjust(1) is used to set up an adjusted branch that needs to be refreshed after getting or dropping files, this config controls how frequently the branch is refreshed.
Refreshing the branch takes some time, so doing it after every file can be too slow. (It also can generate a lot of dangling git objects.)  The default value is 0 (or false), which does not refresh the branch. Setting 1 (or true) will refresh only once, after git-annex has made other changes. Setting 2 refreshes after every file, 3 after every other file, and so on; setting 100 refreshes after every 99 files.
(If git-annex gets faster in the future, refresh rates will increase proportional to the speed improvements.)
annex.queuesize git-annex builds a queue of git commands, in order to combine similar commands for speed. By default the size of the queue is limited to 10240 commands; this can be used to change the size. If you have plenty of memory and are working with very large numbers of files, increasing the queue size can speed it up.
annex.bloomcapacity The git annex unused and git annex sync --content commands use a bloom filter to determine what files are present in eg, the work tree.  The default bloom filter is sized to handle up to 500000 files. If your repository is larger than that, you should increase this value. Larger values will make git-annex unused and git annex sync --content consume more memory; run git annex info for memory usage numbers.
annex.bloomaccuracy Adjusts the accuracy of the bloom filter used by git annex unused and git annex sync --content.  The default accuracy is 10000000 -- 1 unused file out of 10000000 will be missed by git annex unused. Increasing the accuracy will make git annex unused consume more memory; run git annex info for memory usage numbers.
annex.sshcaching By default, git-annex caches ssh connections using ssh's ControlMaster and ControlPersist settings (if built using a new enough ssh). To disable this, set to false.
annex.adviceNoSshCaching When git-annex is unable to use ssh connection caching, or has been configured not to, and concurrency is enabled, it will warn that this might result in multiple ssh processes prompting for passwords at the same time. To disable that warning, eg if you have configured ssh connection caching yourself, or have ssh agent caching passwords, set this to false.
annex.alwayscommit By default, git-annex automatically commits data to the git-annex branch after each command is run. If you have a series of commands that you want to make a single commit, you can run the commands with -c annex.alwayscommit=false. You can later commit the data by running git annex merge (or by automatic merges) or git annex sync.
annex.commitmessage When git-annex updates the git-annex branch, it usually makes up its own commit message (eg "update"), since users rarely look at or care about changes to that branch. If you do care, you can specify this setting by running commands with -c annex.commitmessage=whatever
This works well in combination with annex.alwayscommit=false, to gather up a set of changes and commit them with a message you specify.
annex.allowsign By default git-annex avoids gpg signing commits that it makes when they're not the purpose of a command, but only a side effect. That default avoids lots of gpg password prompts when commit.gpgSign is set. A command like git annex sync or git annex merge will gpg sign its commit, but a command like git annex get, that updates the git-annex branch, will not. The assistant also avoids signing commits.
Setting annex.allowsign to true lets all commits be signed, as controlled by commit.gpgSign and other git configuration.
annex.merge-annex-branches By default, git-annex branches that have been pulled from remotes are automatically merged into the local git-annex branch, so that git-annex has the most up-to-date possible knowledge.
To avoid that merging, set this to "false". This can be useful particularly when you don't have write permission to the repository.
annex.private When this is set to true, no information about the repository will be recorded in the git-annex branch.
For example, to make a repository without any mention of it ever appearing in the git-annex branch:
git init myprivate cd myprivaterepo git config annex.private true git annex init
annex.hardlink Set this to true to make file contents be hard linked between the repository and its remotes when possible, instead of a more expensive copy.
Use with caution -- This can invalidate numcopies counting, since with hard links, fewer copies of a file can exist. So, it is a good idea to mark a repository using this setting as untrusted.
When a repository is set up using git clone --shared, git-annex init will automatically set annex.hardlink and mark the repository as untrusted.
When annex.thin is also set, setting annex.hardlink has no effect.
annex.thin Set this to true to make unlocked files be a hard link to their content in the annex, rather than a second copy. This can save considerable disk space, but when a modification is made to a file, you will lose the local (and possibly only) copy of the old version. So, enable with care.
After setting (or unsetting) this, you should run git annex fix to fix up the annexed files in the work tree to be hard links (or copies).
Note that this has no effect when the filesystem does not support hard links.  And when multiple files in the work tree have the same content, only one of them gets hard linked to the annex.
annex.supportunlocked By default git-annex supports unlocked files as well as locked files, so this defaults to true. If set to false, git-annex will only support locked files. That will avoid doing the work needed to support unlocked files.
Note that setting this to false does not prevent a repository from having unlocked files added to it, and in that case the content of the files will not be accessible until they are locked.
After changing this config, you need to re-run git-annex init for it to take effect.
annex.resolvemerge Set to false to prevent merge conflicts in the checked out branch being automatically resolved by the git-annex assitant, git-annex sync, git-annex merge, and the git-annex post-receive hook.
To configure the behavior in all clones of the repository, this can be set in git-annex-config(1).
annex.synccontent Set to true to make git-annex sync default to syncing annexed content.
annex.synconlyannex Set to true to make git-annex sync default to only sincing the git-annex branch and annexed content.
annex.debug Set to true to enable debug logging by default.
annex.debugfilter Set to configure which debug messages to display (when debug message display has been enabled by annex.debug or --debug). The value is one or more module names, separated by commas.
annex.version The current version of the git-annex repository. This is maintained by git-annex and should never be manually changed.
annex.autoupgraderepository When an old git-annex repository version has become deprecated, git-annex will normally automatically upgrade the repository to the new version.
If this is set to false, git-annex won't automatically upgrade the repository. Instead it will exit with an error message. You can run git annex upgrade yourself when you are ready to upgrade the repository.
annex.crippledfilesystem Set to true if the repository is on a crippled filesystem, such as FAT, which does not support symbolic links, or hard links, or unix permissions.  This is automatically probed by "git annex init".
annex.pidlock Normally, git-annex uses fine-grained lock files to allow multiple processes to run concurrently without getting in each others' way. That works great, unless you are using git-annex on a filesystem that does not support POSIX fcntl locks. This is sometimes the case when using NFS or Lustre filesystems.
To support such situations, you can set annex.pidlock to true, and it will fall back to a single top-level pid file lock.
Although, often, you'd really be better off fixing your networked filesystem configuration to support POSIX locks.. And, some networked filesystems are so inconsistent that one node can't reliably tell when the other node is holding a pid lock. Caveat emptor.
annex.pidlocktimeout git-annex will wait up to this many seconds for the pid lock file to go away, and will then abort if it cannot continue. Default: 300
When using pid lock files, it's possible for a stale lock file to get left behind by previous run of git-annex that crashed or was interrupted.  This is mostly avoided, but can occur especially when using a network file system. This timeout prevents git-annex waiting forever in such a situation.
annex.cachecreds When "true" (the default), git-annex will cache credentials used to access special remotes in files in .git/annex/creds/ that only you can read. To disable that caching, set to "false", and credentials will only be read from the environment, or if they have been embedded in encrypted form in the git repository, will be extracted and decrypted each time git-annex needs to access the remote.
annex.secure-erase-command This can be set to a command that should be run whenever git-annex removes the content of a file from the repository.
In the command line, %file is replaced with the file that should be erased.
For example, to use the wipe command, set it to wipe -f %file.
annex.freezecontent-command, annex.thawcontent-command Usually the write permission bits are unset to protect annexed objects from being modified or deleted. The freezecontent-command is run after git-annex has removed the write bit. The thawcontent-command should undo its effect, and is run before git- annex restores the write bit.
In the command line, %path is replaced with the file or directory to operate on.
annex.tune.objecthash1, annex.tune.objecthashlower, annex.tune.branchhash1 These can be passed to git annex init to tune the repository. They cannot be safely changed in a running repository and should never be set in global git configuration.  For details, see <https://git-annex.branchable.com/tuning/>.
Remotes are configured using these settings in .git/config.
remote.<name>.annex-cost When determining which repository to transfer annexed files from or to, ones with lower costs are preferred.  The default cost is 100 for local repositories, and 200 for remote repositories.
remote.<name>.annex-cost-command If set, the command is run, and the number it outputs is used as the cost.  This allows varying the cost based on e.g., the current network.
remote.<name>.annex-start-command A command to run when git-annex begins to use the remote. This can be used to, for example, mount the directory containing the remote.
The command may be run repeatedly when multiple git-annex processes are running concurrently.
remote.<name>.annex-stop-command A command to run when git-annex is done using the remote.
The command will only be run once *all* running git-annex processes are finished using the remote.