git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Tad Hardesty <tad.hardesty@suddenlink.net>
Cc: git@vger.kernel.org, Tad Hardesty <tad@platymuus.com>
Subject: Re: 'git status -z' missing separators on OSX
Date: Wed, 17 Jun 2015 15:17:04 -0400	[thread overview]
Message-ID: <20150617191703.GC25304@peff.net> (raw)
In-Reply-To: <20150617140738.UMQU25489.txasav-vm07.suddenlink.net@[10.1.40.186]>

On Wed, Jun 17, 2015 at 09:07:36AM -0500, Tad Hardesty wrote:

> Everything looks normal using the commands you described, and it does appear to only affect status:
> 
> ~/test (master)$ type git
> git is hashed (/usr/local/bin/git)
> ~/test (master)$ git config --list
> core.repositoryformatversion=0
> core.filemode=true
> core.bare=false
> core.logallrefupdates=true
> core.ignorecase=true
> core.precomposeunicode=true
> ~/test (master)$ GIT_TRACE=1 git status -z
> 08:59:11.806197 git.c:348               trace: built-in: git 'status' '-z'
> ~/test (master)$ git log --oneline -1 -z | hexdump -C
> 00000000  35 31 35 39 30 65 30 20  49 6e 69 74 69 61 6c 20  |51590e0 Initial |
> 00000010  63 6f 6d 6d 69 74 2e 00                           |commit..|
> 00000018
> ~/test (master)$ touch c d
> ~/test (master)$ git status -z | hexdump -C
> 00000000  3f 3f 20 63 3f 3f 20 64                           |?? c?? d|
> 00000008
> 
> This is again with 2.4.3 from git-scm.com.

Hmph. I don't really have any more ideas, then. I think my next step
would be to walk it through a debugger (the interesting function is
wt_shortstatus_status, or wt_shortstatus_other).

-Peff

  reply	other threads:[~2015-06-17 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 14:07 'git status -z' missing separators on OSX Tad Hardesty
2015-06-17 19:17 ` Jeff King [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-16 23:21 Tad Hardesty
2015-06-17  3:32 ` Jeff King
2015-06-17 21:32   ` Eric Sunshine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150617191703.GC25304@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=tad.hardesty@suddenlink.net \
    --cc=tad@platymuus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).