| Value | Meaning |
|---|---|
| GIT_PATHSPEC_DEFAULT0 | |
| GIT_PATHSPEC_IGNORE_CASE1u << 0 | GIT_PATHSPEC_IGNORE_CASE forces match to ignore case; otherwise match will use native case sensitivity of platform filesystem |
| GIT_PATHSPEC_USE_CASE1u << 1 | GIT_PATHSPEC_USE_CASE forces case sensitive match; otherwise match will use native case sensitivity of platform filesystem |
| GIT_PATHSPEC_NO_GLOB1u << 2 | GIT_PATHSPEC_NO_GLOB disables glob patterns and just uses simple string comparison for matching |
| GIT_PATHSPEC_NO_MATCH_ERROR1u << 3 | GIT_PATHSPEC_NO_MATCH_ERROR means the match functions return error code GIT_ENOTFOUND if no matches are found; otherwise no matches is still success (return 0) but git_pathspec_match_list_entrycount will indicate 0 matches. |
| GIT_PATHSPEC_FIND_FAILURES1u << 4 | GIT_PATHSPEC_FIND_FAILURES means that the git_pathspec_match_list should track which patterns matched which files so that at the end of the match we can identify patterns that did not match any files. |
| GIT_PATHSPEC_FAILURES_ONLY1u << 5 | GIT_PATHSPEC_FAILURES_ONLY means that the git_pathspec_match_list does not need to keep the actual matching filenames. Use this to just test if there were any matches at all or in combination with GIT_PATHSPEC_FIND_FAILURES to validate a pathspec. |
Options controlling how pathspec match should be executed