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

clarify that annex.backends is used when adding new files

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

4
doc/backends.mdwn
View file

@ -35,8 +35,8 @@ which are known to not work on Windows. If interoperability on Windows is a
concern, avoid those.
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
new files are added.
git-annex should use when adding new files. The first one listed will
be used.
For finer control of what backend is used when adding different types of
files, the `.gitattributes` file can be used. The `annex.backend`

4
doc/git-annex.mdwn
View file

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