On Fri, Mar 29, 2013 at 10:35:17AM -0700, Junio C Hamano wrote: > This may be just the matter of naming. > > It smelled wrong to me only because the "fnmatch" in the helper > fnmatch_icase_mem() told me that it should forever use fnmatch > semantics. After reading its (only) two callsites, they are both > "the caller has transformed the inputs to this lowest level pathname > vs pattern matching function in order to reduce the cost of > matching, and now it is time to exercise the matcher". The only > thing they care about is that they are calling "the lowest level > pathname vs pattern matching function." > > If we pronounce "fnmatch_icase_mem()" as "match_path_with_pattern()" > or something in the original series, the problem may go away ;-) Yes, since there are only the two new added callers, if they both want to switch to wildmatch, then it is fine for the helper function to switch. The danger is if some other caller wants to start using it; I added it with the name I did figuring that other spots might want to use it eventually. But if all of fnmatch is going to go away in favor of wildmatch eventually, then that helper is not all that useful (or it would be even more useful as "wildmatch_mem" or similar). > Does any caller pass FNM_* bits to a callchain that reach the new *_mem() > function? The series only adds two callers, and they provide constant flags; match_basename passes no flags, and should be OK. match_pathname uses FNM_PATHNAME, and would need to be converted to use WM_PATHNAME as part of the conflict resolution. -Peff -- 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