Clemens Buchacher <drizzd@xxxxxx> writes: > I think we could at least add an option to disable globbing. Then we can > also disable the above check conditioned on that. If we allowed globbing > pattern for following renames wouldn't that result in following the first > file (or last in history) to match the pattern, which is potentially > confusing? Yeah, I agree that would be a reasonable thing to do. In places we read paths from the index or from the work tree and add them as pathspec elements---you would want to mark them as non-globbing, too. Which probably means that "is it Ok to glob this" setting has to be per pathspec array elements. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html