Re: Collisions while cloning (was: Re: renormalize histroy with smudge/clean-filter, again)
- From
Torsten Bögershausen <tboegi@web.de>
- Date
- Feb 13, 2025, 16:40 UTC
- Message-ID
- <20250213164035.GA24612@tb-raspi4>
- In-Reply-To
- <20250213113614.GS30202@raven.inka.de>
On Thu, Feb 13, 2025 at 12:36:14PM +0100, Josef Wolf wrote:
Show 25 quoted lines
> Hi folks, > > while investigating/recovering my problems with renormalizing with > clean/smudge filtering, I stumbled on collisions while creating a fresh clone > of the repo from the server: > > $ LANG= git clone ssh://gitrepos@my.server/repo > smart-home-ets5hashes-removed > Cloning into 'smart-home-ets5hashes-removed'... > remote: Enumerating objects: 7499, done. > remote: Counting objects: 100% (7499/7499), done. > remote: Compressing objects: 100% (3263/3263), done. > remote: Total 7499 (delta 3955), reused 7109 (delta 3594), pack-reused 0 > Receiving objects: 100% (7499/7499), 140.12 MiB | 10.54 MiB/s, done. > Resolving deltas: 100% (3955/3955), done. > Updating files: 100% (1423/1423), done. > 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: > > 'Projects/P-0113/B.ets5hash' > [more files deleted] > > This is on linux, so the FS is _not_ case-insensitive. >
That sounds fishy (tm) Does 'git ls-files' give any hints ?