summaryrefslogtreecommitdiff
path: root/dir.h
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2015-03-24 14:12:10 -0700
committerJunio C Hamano <gitster@pobox.com>2015-03-24 14:12:10 -0700
commit777c55a61615837d4391facd75cf334b96635801 (patch)
tree5c5a3afc4249a24acbb6ea76cb72e53057ce6954 /dir.h
parent282616c72d1d08a77ca4fe1186cb708c38408d87 (diff)
downloadgit-777c55a61615837d4391facd75cf334b96635801.tar.gz
report_path_error(): move to dir.cjc/report-path-error-to-dir
The expected call sequence is for the caller to use match_pathspec() repeatedly on a set of pathspecs, accumulating the "hits" in a separate array, and then call this function to diagnose a pathspec that never matched anything, as that can indicate a typo from the command line, e.g. "git commit Maekfile". Many builtin commands use this function from builtin/ls-files.c, which is not a very healthy arrangement. ls-files might have been the first command to feel the need for such a helper, but the need is shared by everybody who uses the "match and then report" pattern. Move it to dir.c where match_pathspec() is defined. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'dir.h')
-rw-r--r--dir.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/dir.h b/dir.h
index 55e53456af..ed336add79 100644
--- a/dir.h
+++ b/dir.h
@@ -135,6 +135,7 @@ extern char *common_prefix(const struct pathspec *pathspec);
extern int match_pathspec(const struct pathspec *pathspec,
const char *name, int namelen,
int prefix, char *seen, int is_dir);
+extern int report_path_error(const char *ps_matched, const struct pathspec *pathspec, const char *prefix);
extern int within_depth(const char *name, int namelen, int depth, int max_depth);
extern int fill_directory(struct dir_struct *dir, const struct pathspec *pathspec);