From: Lutz Roeder <lutz.noreply@gmail.com>
To: peff@peff.net, git@vger.kernel.org, tboegi@web.de
Subject: Re: Git on macOS shows committed files as untracked
Date: Thu, 13 Jul 2017 21:51:21 -0700 [thread overview]
Message-ID: <CANmutwAJd3qUbNmPv5WpD4zr=rt=Zt3sJ3Ackuasu=pOCRz-5g@mail.gmail.com> (raw)
In-Reply-To: <CANmutwCSGgLxESPmTJZXkid6P1N6HwwOTaz=7QHOsSPrrHQ4EQ@mail.gmail.com>
Using precomposeunicode still reproduces the issue:
Repro steps:
1. Download https://www.dropbox.com/s/0q5pbpqpckwzj7b/gitstatusrepro.zip?dl=0
2. unzip gitstatusrepro.zip && cd gitstatusrepro
3. git reset --hard
4. git -c core.precomposeunicode=true status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
"d\314\207\316\271\314\223\314\200\342\225\223\316\265\357\256\257\360\222\221\217\342\227\213\342\225\223\320\243\314\213/"
nothing added to commit but untracked files present (use "git add" to track)
> From: Torsten Bögershausen <tboegi@web.de>
>
> Thanks for the fast analyzes -
> in short:
> what does
> git -c core.precomposeunicode=true status
> say ?
>
>
> The easiest thing may be to set
> git config --global core.precomposeunicode true
next parent reply other threads:[~2017-07-14 4:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANmutwCSGgLxESPmTJZXkid6P1N6HwwOTaz=7QHOsSPrrHQ4EQ@mail.gmail.com>
2017-07-14 4:51 ` Lutz Roeder [this message]
2017-07-14 8:41 ` Git on macOS shows committed files as untracked Torsten Bögershausen
2017-07-14 9:46 ` Elliot Chandler
[not found] ` <CAHVrscDg8bc-CYm6dSJFgdPSv1vJ0=AC0s3y26CHctKkYAvJyA@mail.gmail.com>
2017-07-14 12:35 ` Torsten Bögershausen
2017-07-14 13:28 ` Jeff King
2017-07-14 13:29 ` Andreas Schwab
2017-07-12 22:21 roeder.git
2017-07-12 23:15 ` Jeff King
2017-07-13 8:42 ` Torsten Bögershausen
2017-07-13 19:35 ` Junio C Hamano
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='CANmutwAJd3qUbNmPv5WpD4zr=rt=Zt3sJ3Ackuasu=pOCRz-5g@mail.gmail.com' \
--to=lutz.noreply@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=tboegi@web.de \
/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).