From: Daniel Troger <random_n0body@icloud.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Philippe Blain <levraiphilippeblain@gmail.com>,
"Randall S. Becker" <rsbecker@nexbridge.com>,
git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: git-bugreport-2021-01-06-1209.txt (git can't deal with special characters)
Date: Fri, 8 Jan 2021 20:56:08 +0100 [thread overview]
Message-ID: <7B64BC13-CB54-43CE-8C01-D45E25591E2A@icloud.com> (raw)
> That did the trick, the test case is now reproducible here.
> It seems as if there could be a patch in a couple of days, but no promises.
That's great news, thank you all very much!
I was already afraid at first it was some weird macOS filesystem bug only happening on high sierra and earlier which was never going to be fixed.
In the meantime I have managed to add "both directories" to git (with git add paulbr*). It's funny, now one directory shows up twice when viewing my repo on gitlab.
And this is the message I get when cloning:
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'[...]/paulbrunngård-springyard/main.ts'
'[...]/paulbrunngård-springyard/main.ts'
What will happen with the two folders in the git repo after the patch?
next reply other threads:[~2021-01-08 19:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 19:56 Daniel Troger [this message]
2021-01-09 17:23 ` git-bugreport-2021-01-06-1209.txt (git can't deal with special characters) Torsten Bögershausen
2021-01-13 14:57 ` Daniel Troger
2021-01-16 17:24 ` Torsten Bögershausen
-- strict thread matches above, loose matches on Subject: below --
2021-01-06 11:35 Daniel Troger
2021-01-06 14:21 ` Torsten Bögershausen
2021-01-06 16:49 ` Daniel Troger
2021-01-06 21:47 ` Torsten Bögershausen
2021-01-06 22:21 ` Daniel Troger
2021-01-06 23:07 ` Randall S. Becker
2021-01-07 14:34 ` Philippe Blain
2021-01-07 15:49 ` Torsten Bögershausen
2021-01-07 16:21 ` Philippe Blain
2021-01-08 19:07 ` Torsten Bögershausen
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=7B64BC13-CB54-43CE-8C01-D45E25591E2A@icloud.com \
--to=random_n0body@icloud.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=levraiphilippeblain@gmail.com \
--cc=rsbecker@nexbridge.com \
--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).