Thomas Wolf
4e745c57f7
FastIgnoreRule: include bad pattern in log message
When a .gitignore pattern cannot be parsed include the pattern in the log message. Just reporting "not closed bracket" isn't helpful if the user doesn't know in which pattern the problem occurred. Even better would be to include the full path of the .gitignore file that contained the offending pattern. This is not implemented in this change; it may need new API and needs more thought. Bug: 571143 Change-Id: Id5b16d9cf550544ba3ad409a02041946fa8516ab Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch> |
il y a 3 ans | |
---|---|---|
.. | ||
internal | Merge branch 'stable-5.6' | il y a 4 ans |
FastIgnoreRule.java | FastIgnoreRule: include bad pattern in log message | il y a 3 ans |
IMatcher.java | Make the IMatcher public API | il y a 4 ans |
IgnoreNode.java | [spotbugs] Silence NP_BOOLEAN_RETURN_NULL in IgnoreNode#checkIgnored | il y a 3 ans |
package-info.java | Add Javadoc description for packages | il y a 11 ans |