Re: git log -z doesn't separate commits with NULs

On Fri, Feb 24, 2012 at 01:14:05PM -0800, Junio C Hamano wrote:

quoted

True. That is also a slightly dangerous thing to do, though, because you
are omitting full patches in the middle that touch the same paths as the
patches you include....
... So
perhaps we are better off to refer the user to git-log(1), say that
commit limiting options in general would work, but be careful with
sending a partial result.

You seem to have spelled out everything I originally wrote in my reply
that I later deleted before sending it out, and I think the reason that
brought you to the three-line conclusion is the same one that made me I
delete them ;-).

OK, good. :)

Nikolaj, have you followed all of this? Do you want to try to improve
your patch in this direction?

-Peff