diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-02-24 11:53:59 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-02-24 11:53:59 -0400 |
| commit | 1da3d6d7d6e44e2e4cc2930f6db4c37af20dd718 (patch) | |
| tree | 3eae10ae93a1b45b9aaef355cb692423211a8740 | |
| parent | 9ca99b8312678f171414a4c33e2f283ee60d23a5 (diff) | |
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.)
| -rw-r--r-- | doc/backends.mdwn | 4 | ||||
| -rw-r--r-- | doc/git-annex.mdwn | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/backends.mdwn b/doc/backends.mdwn index 710255dcf..d26cadce5 100644 --- a/doc/backends.mdwn +++ b/doc/backends.mdwn @@ -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` diff --git a/doc/git-annex.mdwn b/doc/git-annex.mdwn index 525900d92..1c905766d 100644 --- a/doc/git-annex.mdwn +++ b/doc/git-annex.mdwn @@ -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. |