{"thread":{"id":"39658","subject":"Re: 'git status -z' missing separators on OSX","startedAt":"2015-06-17T14:07:36Z","lastAt":"2015-06-17T19:17:04Z","messageCount":2,"participants":["Tad Hardesty","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"264020","messageId":"20150617140738.UMQU25489.txasav-vm07.suddenlink.net@[10.1.40.186]","threadId":"39658","inReplyTo":null,"subject":"Re: 'git status -z' missing separators on OSX","fromName":"Tad Hardesty","fromEmail":"tad.hardesty@suddenlink.net","sentAt":"2015-06-17T14:07:36Z","receivedAt":"2015-06-17T14:07:36Z","isPatch":false,"sender":{"key":"tad.hardesty@suddenlink.net","avatar":null},"body":"Everything looks normal using the commands you described, and it does appear to only affect status:\n\n~/test (master)$ type git\ngit is hashed (/usr/local/bin/git)\n~/test (master)$ git config --list\ncore.repositoryformatversion=0\ncore.filemode=true\ncore.bare=false\ncore.logallrefupdates=true\ncore.ignorecase=true\ncore.precomposeunicode=true\n~/test (master)$ GIT_TRACE=1 git status -z\n08:59:11.806197 git.c:348               trace: built-in: git 'status' '-z'\n~/test (master)$ git log --oneline -1 -z | hexdump -C\n00000000  35 31 35 39 30 65 30 20  49 6e 69 74 69 61 6c 20  |51590e0 Initial |\n00000010  63 6f 6d 6d 69 74 2e 00                           |commit..|\n00000018\n~/test (master)$ touch c d\n~/test (master)$ git status -z | hexdump -C\n00000000  3f 3f 20 63 3f 3f 20 64                           |?? c?? d|\n00000008\n\nThis is again with 2.4.3 from git-scm.com.\n"},{"id":"264059","messageId":"20150617191703.GC25304@peff.net","threadId":"39658","inReplyTo":"20150617140738.UMQU25489.txasav-vm07.suddenlink.net@[10.1.40.186]","subject":"Re: 'git status -z' missing separators on OSX","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2015-06-17T19:17:04Z","receivedAt":"2015-06-17T19:17:04Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Jun 17, 2015 at 09:07:36AM -0500, Tad Hardesty wrote:\n\n> Everything looks normal using the commands you described, and it does appear to only affect status:\n> \n> ~/test (master)$ type git\n> git is hashed (/usr/local/bin/git)\n> ~/test (master)$ git config --list\n> core.repositoryformatversion=0\n> core.filemode=true\n> core.bare=false\n> core.logallrefupdates=true\n> core.ignorecase=true\n> core.precomposeunicode=true\n> ~/test (master)$ GIT_TRACE=1 git status -z\n> 08:59:11.806197 git.c:348               trace: built-in: git 'status' '-z'\n> ~/test (master)$ git log --oneline -1 -z | hexdump -C\n> 00000000  35 31 35 39 30 65 30 20  49 6e 69 74 69 61 6c 20  |51590e0 Initial |\n> 00000010  63 6f 6d 6d 69 74 2e 00                           |commit..|\n> 00000018\n> ~/test (master)$ touch c d\n> ~/test (master)$ git status -z | hexdump -C\n> 00000000  3f 3f 20 63 3f 3f 20 64                           |?? c?? d|\n> 00000008\n> \n> This is again with 2.4.3 from git-scm.com.\n\nHmph. I don't really have any more ideas, then. I think my next step\nwould be to walk it through a debugger (the interesting function is\nwt_shortstatus_status, or wt_shortstatus_other).\n\n-Peff\n"}]}