On Tue, Oct 4, 2011 at 9:06 AM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > 3. Maybe some hero will implement > > git log -p --exclude=po/ > # or > git log -p -- :(not)po/ > > to complement "git log -p -- po/". ;-) I was pursuing the latter, but think again, maybe reuse exclude code to implement --exclude would be wiser. One of my motives for negative pathspec is to narrow/extend a narrow clone. Narrow clone itself should reuse sparse checkout for worktree part, and sparse checkout uses exclude code already. If I go with negative pathspec for narrow clone, I would need to invent another negative-path-based sparse checkout.. That does not make much sense. I believe a couple of lines in process_trees() in list-objects.c and adding struct exclude_list* to struct rev_info would be enough for --exclude, if you want to try. -- Duy -- 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