v6: * rebased on top of origin/bw/pathspec-cleanup, resolving conflicts. (Additionally needs merging with origin/sb/submodule-embed-gitdir to have 6f94351b0, test-lib-functions.sh: teach test_commit -C <dir>) * reworded comments and commit message * do not reuse the strip_submodule_slash_expensive function, but have a dedicated die_inside_submodule_path function. v5: * was just resending the latest patch, which turns out to be in conflict with origin/bw/pathspec-cleanup v4: > It MIGHT be a handy hack when writing a test, but let's stop doing > that insanity. No sane project does that in real life, doesn't it? > Create a subdirectory, make it a repository, have a commit there and > bind that as our own submodule. That would be a more normal way to > start your own superproject and its submodule pair if they originate > together at the same place. This comes as an extra patch before the actual fix. The actual fixing patch was reworded borrowing some words from Jeff. As this makes use of "test_commit -C", it goes on top of sb/submodule-embed-gitdir v3: more defensive and with tests. Stefan Beller (2): submodule tests: don't use itself as a submodule pathspec: give better message for submodule related pathspec error pathspec.c | 31 ++++++++++++++++++++++--------- t/lib-submodule-update.sh | 2 ++ t/t6134-pathspec-in-submodule.sh | 33 +++++++++++++++++++++++++++++++++ t/t7001-mv.sh | 5 +++-- t/t7507-commit-verbose.sh | 4 +++- t/t7800-difftool.sh | 4 +++- t/test-lib-functions.sh | 16 ++++++++++++++++ 7 files changed, 82 insertions(+), 13 deletions(-) create mode 100755 t/t6134-pathspec-in-submodule.sh -- 2.11.0.31.g919a8d0.dirty
