mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

rework subcommand invocation logic

Browse source
This commit is contained in:
Joey Hess 2010-11-01 14:49:05 -04:00
parent 4da551827f
commit 59e49ae083
3 changed files with 85 additions and 63 deletions
Download patch file Download diff file Expand all files Collapse all files

14
doc/git-annex.mdwn
View file

@ -159,8 +159,7 @@ Many git-annex subcommands will stage changes for later `git commit` by you.
* --backend=name
Specify the default key-value backend to use, adding it to the front
of the list normally configured by `annex.backends`.
Specifies the key-value backend to use when adding a file.
* --key=name
@ -186,7 +185,7 @@ Here are all the supported configuration settings.
repositories (default: 1)
* `annex.backends` -- space-separated list of names of
the key-value backends to use. The first listed is used to store
new files. (default: "WORM SHA1 URL")
new files by default. (default: "WORM SHA1 URL")
* `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
@ -204,6 +203,15 @@ Here are all the supported configuration settings.
* `annex.scp-options` and `annex.ssh-options` -- Default scp and ssh
options to use if a remote does not have specific options.
The backend used when adding a new file to the annex can be configured
on a per-file-type basis via the `.gitattributes` file. In the file,
the `git-annex-backend` attribute can be set to the name of the backend to
use. For example, this here's how to use the WORM backend by default,
but the SHA1 backend for ogg files:
* git-annex-backend=WORM
*.ogg git-annex-backend=SHA1
# FILES
These files are used, in your git repository: