From: Jeff King <peff@peff.net>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Elliot Chandler <worldpeacehaven@gmail.com>,
Lutz Roeder <lutz.noreply@gmail.com>,
git@vger.kernel.org
Subject: Re: Git on macOS shows committed files as untracked
Date: Fri, 14 Jul 2017 09:28:47 -0400 [thread overview]
Message-ID: <20170714132846.dww7y5ae4fexejnc@sigill.intra.peff.net> (raw)
In-Reply-To: <8b5fc22c-4d65-d34a-a84c-c913f454c771@web.de>
On Fri, Jul 14, 2017 at 02:35:52PM +0200, Torsten Bögershausen wrote:
> (Please no top-posting)
> On 14/07/17 11:45, Elliot Chandler wrote:
> > For what it's worth, the file looks normal in Gentoo GNU/Linux (name
> > appears "ḋἲ╓εﮯ𒑏○╓Ӳ" and it seems to work like any other directory).
> >
> Thanks for testing -
> Normal and Normal ;-)
> For me the 6th code point does look strange
> The "box" with 04142F:
> Code point 4142F is unassigned and is outside any currently defined block range.
Are you sure? I get u+1244f. I don't have a glyph for it in my font, but
at least it's a real unicode codepoint (cuneiform 1).
> So this is not valid Unicode, so we have a problem here under MacOS -
> not much Git can do about it.
I do still suspect this is the root of the problem. There's something
about the string that HFS+ doesn't want to store, and there's nothing we
can do to fix that.
-Peff
next prev parent reply other threads:[~2017-07-14 13:28 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 ` Git on macOS shows committed files as untracked Lutz Roeder
2017-07-14 8:41 ` 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 [this message]
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=20170714132846.dww7y5ae4fexejnc@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=lutz.noreply@gmail.com \
--cc=tboegi@web.de \
--cc=worldpeacehaven@gmail.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).