Christian Couder <christian.couder@xxxxxxxxx> writes: > In the commit message it might be nice if there were some explanations > about why `test_path_is_missing PATH` should be used instead of `! > test_path_is_file PATH` or `test ! -f PATH` or `! test -f PATH`. Meaning "the original used '! test -f foo' but what it meant was that it did not want to see 'foo' on the filesystem, regardless of its type, so it should have been '!test -e foo' to begin with"? I guess it does not hurt, as the original would have passed by mistake if these paths were on the filesystem as directories, but the new code would behave differently, and even if it is a "bugfix", it still is a behaviour change that may be worth explaining. > The diff part of the patch looks good to me. Thanks!
