clarify that annex.backends is used when adding new files

Even if annex.backends does not include a backend, that does not prevent
git-annex commands from acting on a file using the missing backend.

(There's really no reason at all for annex.backends to be a list.)
This commit is contained in:
Joey Hess 2017-02-24 11:53:59 -04:00
parent 8971949d60
commit 6346704a04
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
2 changed files with 4 additions and 4 deletions

View file

@ -35,8 +35,8 @@ which are known to not work on Windows. If interoperability on Windows is a
concern, avoid those. concern, avoid those.
The `annex.backends` git-config setting can be used to list the backends The `annex.backends` git-config setting can be used to list the backends
git-annex should use. The first one listed will be used by default when git-annex should use when adding new files. The first one listed will
new files are added. be used.
For finer control of what backend is used when adding different types of For finer control of what backend is used when adding different types of
files, the `.gitattributes` file can be used. The `annex.backend` files, the `.gitattributes` file can be used. The `annex.backend`

View file

@ -823,8 +823,8 @@ Here are all the supported configuration settings.
* `annex.backends` * `annex.backends`
Space-separated list of names of the key-value backends to use. Space-separated list of names of the key-value backends to use
The first listed is used to store new files by default. when adding new files to the repository.
This is overridden by annex annex.backend configuration in the This is overridden by annex annex.backend configuration in the
.gitattributes files. .gitattributes files.