Re: [PATCH v2 14/45] Guard against new pathspec magic in pathspec matching code
From: Eric Sunshine <hidden>
Date: 2016-06-15 22:56:28
On Wed, Mar 20, 2013 at 8:16 AM, Nguyễn Thái Ngọc Duy [off-list ref] wrote:
quoted hunk ↗ jump to hunk
diff --git a/Documentation/technical/api-setup.txt b/Documentation/technical/api-setup.txt index 59a947e..f62528e 100644 --- a/Documentation/technical/api-setup.txt +++ b/Documentation/technical/api-setup.txt@@ -28,3 +28,22 @@ parse_pathspec(). This function takes several arguments: - prefix and args come from cmd_* functions get_pathspec() is obsolete and should never be used in new code. + +parse_pathspec() helps catch unsupported features and reject it
s/reject it/reject them/
+politely. At a lower level, different pathspec-related functions may +not support the same set of features. Such pathspec-sensitive +functions are guarded with GUARD_PATHSPEC(), which will die in an +unfriendly way when an unsupported feature is requested.