remove incorrect documentation of annex.skipunknown behavior

git-annex get with no parameters and annex.skipunknown = false
in a directory with no files tracked by git results in the same
failure as with a "." parameter.

It may be that git ls-files --error-unmatch changed behavior? Or this
was just wrong.
This commit is contained in:
Joey Hess 2023-09-13 12:57:24 -04:00
parent 9db90bab57
commit 30a81d4644
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38

View file

@ -889,16 +889,15 @@ repository, using [[git-annex-config]]. See its man page for a list.)
to be asked to operate on files that are not checked into git. to be asked to operate on files that are not checked into git.
(This is the default in recent versions of git-annex.) (This is the default in recent versions of git-annex.)
Note that, when annex.skipunknown is false, a command like "git-annex get ." 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, ." 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 Commands like "git-annex get foo/" will fail if no files in the directory
directory is not listed, but is implicit. Commands like "git-annex get foo/" are checked into git, but if at least one file is, it will ignore other
will fail if no files in the directory are checked into git, but if files that are not. This is all the same as the behavior of "git-ls files
at least one file is, it will ignore other files that are not. This is --error-unmatch".
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 Also note that git-annex skips files that are checked into git, but are
not annexed files, this setting does not affect that. not annexed files; this setting does not affect that.
* `annex.largefiles` * `annex.largefiles`