parse_pathspec: add special flag for max_depth feature
match_pathspec_depth() and tree_entry_interesting() check max_depth
field in order to support "git grep --max-depth". The feature
activation is tied to "recursive" field, which led to some unwanted
activation, e.g. 5c8eeb8 (diff-index: enable recursive pathspec
matching in unpack_trees - 2012-01-15).
This patch decouples the activation from "recursive" field, puts it in
"magic" field instead. This makes sure that only "git grep" can
activate this feature. And because parse_pathspec knows when the
feature is not used, it does not need to sort pathspec (required for
max_depth to work correctly). A small win for non-grep cases.
Even though a new magic flag is introduced, no magic syntax is. The
magic can be only enabled by parse_pathspec() caller. We might someday
want to support ":(maxdepth:10)src." It all depends on actual use
cases.
max_depth feature cannot be enabled via init_pathspec() anymore. But
that's ok because init_pathspec() is on its way to /dev/null.
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
committed by
Junio C Hamano
parent
0fdc2ae512
commit
6330a17199
@ -267,6 +267,9 @@ void parse_pathspec(struct pathspec *pathspec,
|
||||
|
||||
memset(pathspec, 0, sizeof(*pathspec));
|
||||
|
||||
if (flags & PATHSPEC_MAXDEPTH_VALID)
|
||||
pathspec->magic |= PATHSPEC_MAXDEPTH;
|
||||
|
||||
/* No arguments, no prefix -> no pathspec */
|
||||
if (!entry && !prefix)
|
||||
return;
|
||||
@ -322,8 +325,9 @@ void parse_pathspec(struct pathspec *pathspec,
|
||||
pathspec->magic |= item[i].magic;
|
||||
}
|
||||
|
||||
qsort(pathspec->items, pathspec->nr,
|
||||
sizeof(struct pathspec_item), pathspec_item_cmp);
|
||||
if (pathspec->magic & PATHSPEC_MAXDEPTH)
|
||||
qsort(pathspec->items, pathspec->nr,
|
||||
sizeof(struct pathspec_item), pathspec_item_cmp);
|
||||
}
|
||||
|
||||
/*
|
||||
|
||||
Reference in New Issue
Block a user