Nathan Hartman
2018-09-02 21:10:41 UTC
Has there been a recent change to how wildcards (the asterisk '*') is
treated under Windows?
I am using command line client 1.10.2 r1835932 as installed with
TortoiseSVN 1.10.1, Build 28295 - 64 Bit , 2018/07/15 12:14:12, on
Windows 10 Home 1803 build 17134.254.
I've encountered weirdness with wildcards several times today, so I
just tried in a clean freshly checked-out copy:
E:\workspace\processor>svn rm *.hconfig
svn: E200005: Use --force to override this restriction (local modifications
may be lost)
svn: E200005: 'E:\workspace\processor\a' is not under version control
There is no file or directory named 'a' here; however many files in
this directory have names that begin with the letter 'a'.
Furthermore, when working in the command line earlier today, it
appeared that the names printed in the error messages were truncated
versions of filenames. In this case the filename was truncated to
just one character but I think I saw more characters in other
filenames earlier (not 100% sure on this point).
Other (possibly useful) information: There are no files whose names
differ only in case. The filenames do not contain spaces (nor do any
of the paths, whether in the repo or my working copy). There are no
properties set on this directory or any of its files. Also, I tried
similar operations on freshly checked out copies of other areas of
the repo and the same phenomenon is manifesting. I don't recall ever
seeing this before.
Thoughts?
treated under Windows?
I am using command line client 1.10.2 r1835932 as installed with
TortoiseSVN 1.10.1, Build 28295 - 64 Bit , 2018/07/15 12:14:12, on
Windows 10 Home 1803 build 17134.254.
I've encountered weirdness with wildcards several times today, so I
just tried in a clean freshly checked-out copy:
E:\workspace\processor>svn rm *.hconfig
svn: E200005: Use --force to override this restriction (local modifications
may be lost)
svn: E200005: 'E:\workspace\processor\a' is not under version control
There is no file or directory named 'a' here; however many files in
this directory have names that begin with the letter 'a'.
Furthermore, when working in the command line earlier today, it
appeared that the names printed in the error messages were truncated
versions of filenames. In this case the filename was truncated to
just one character but I think I saw more characters in other
filenames earlier (not 100% sure on this point).
Other (possibly useful) information: There are no files whose names
differ only in case. The filenames do not contain spaces (nor do any
of the paths, whether in the repo or my working copy). There are no
properties set on this directory or any of its files. Also, I tried
similar operations on freshly checked out copies of other areas of
the repo and the same phenomenon is manifesting. I don't recall ever
seeing this before.
Thoughts?