Thread (3 messages) flat view 3 messages, 3 authors, 2016-06-15

Re: Bug in gitk search box

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:24

Paul Mackerras [off-list ref] writes:
It turns out that this problem crept in when I changed from using git
rev-list --header to git log -z --pretty=raw, and the thing that
causes it is that git rev-list puts a null character after every
commit, while git log only puts a null between commits, i.e., there
isn't a null after the last commit.

Junio, is this behaviour deliberate?
There was a recent message from Linus on the list, stating that
NUL in -z format is inter-record separator, not after-record
terminator.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help