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:
parent
9db90bab57
commit
30a81d4644
1 changed files with 7 additions and 8 deletions
|
@ -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.
|
||||
(This is the default in recent versions of git-annex.)
|
||||
|
||||
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,
|
||||
but a command like "git-annex get" will not fail, because the current
|
||||
directory is not listed, but is implicit. Commands like "git-annex get foo/"
|
||||
will fail if no files in the directory are checked into git, but if
|
||||
at least one file is, it will ignore other files that are not. This is
|
||||
all the same as the behavior of "git-ls files --error-unmatch".
|
||||
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.
|
||||
Commands like "git-annex get foo/" will fail if no files in the directory
|
||||
are checked into git, but if at least one file is, it will ignore other
|
||||
files that are not. This is 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
|
||||
not annexed files, this setting does not affect that.
|
||||
not annexed files; this setting does not affect that.
|
||||
|
||||
* `annex.largefiles`
|
||||
|
||||
|
|
Loading…
Reference in a new issue