On Sat, Jul 07, 2007 at 08:35:35PM +0100, Johannes Schindelin wrote:
[..]
I can do these things, but they don't exactly improve readability, IMHO.
I may still need them for doing something with all_match...
You prefer
if (opt->grep_filter && !grep_buffer(opt->grep_filter,
NULL, /* we say nothing, not even filename */
commit->buffer, strlen(commit->buffer)))
return 0;
if (opt->grep_neg_filter && grep_buffer(opt->grep_neg_filter,
NULL, /* we say nothing, not even filename */
commit->buffer, strlen(commit->buffer)));
return 0;
return 1;
?
So what are the semantics of all_match without negated matches?
It doesn't seem to be documented in git-rev-list.txt.
Could you be a bit more specific?
If you're talking about the GREP_NOT thing, then AFAICS that is line based
and I want these things to be commit based. That is I want to select
commits with either a or no lines that match a given pattern and not
commits that have a line that matches some patterns and not some others.
skimo
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html