On Mon, Dec 16, 2019 at 09:50:33AM +0000, Mikael Simonsson wrote: > I will try to recreate the problem with a new repository. > > So far I think I've narrowed it down to a bug introduced in git 2.20.0. > > Not buggy: > [...] If you can build Git from source, you might try using "git bisect" to find the exact commit where the problem starts. > The buggy versions all try to delete fileX when running "git commit fileA": > > % git commit fileA > > # Please enter the commit message for your changes. Lines starting > # with '#' will be ignored, and an empty message aborts the commit. > # > # On branch master > # Your branch is up to date with 'origin/master'. > # > # Changes to be committed: > # deleted: fileX > # modified: fileA > # > # Changes not staged for commit: Is there anything about "fileX" and "fileA"'s names that might be relevant? E.g., might they case-fold to the same name or something? -Peff
