Re: Possible bug: Empty magic word list in pathspec is handled differently in short vs. long form

From the gitglossary, pathspec section:

""" In the short form, the leading colon `:` is followed by zero or more "magic signature" letters (which optionally is terminated by another colon :), and the remainder is the pattern to match against the path. """

and:

""" In the long form, the leading colon : is followed by an open parenthesis `(`, a comma-separated list of zero or more "magic words", and a close parentheses `)` , and the remainder is the pattern to match against the path. """

Note that the long form doesn't mention that a second colon has the same meaning as in the short form. In the short form, the second colon is optionally used to separate the magic signatures from the file pattern. It wouldn't be necessary in the long form, as the close parentheses acts just like that.

This way, "::" and ":():" doesn't have the same meaning, just like, for example, ":(exclude):" doesn't mean ":!" (but ":(exclude)" does).