git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug in gitk search box

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 26, 2007, 02:54 UTC
Message-ID
<7vtzrrc1sb.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<18087.60033.676105.538784@cargo.ozlabs.ibm.com>
Paul Mackerras <paulus@samba.org> writes:
Show 7 quoted lines
> 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.

Previous: Paul MackerrasNext: Paul Mackerras
Message 3 of 6 in “Bug in gitk search box”
  1. Brian DowningJul 25, 2007
  2. Paul MackerrasJul 26, 2007
  3. Junio C HamanoJul 26, 2007
  4. Paul MackerrasJul 26, 2007
  5. Junio C HamanoJul 26, 2007
  6. Marco CostalbaJul 26, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.