Re: Cloned repository has file changes -> bug?

I’m not git expert but, from a user point of view, the following would make sense. When adding a file, git could check whether a different file is already in the repository with the same name (case-insensitive check). Then simply report that this may be a mistake and request to use ‘git add -f’

Re: Cloned repository has file changes -> bug?

! Filip > Op 28 jan. 2018, om 08:57 heeft Torsten Bögershausen het > volgende geschreven: > > On Sat, Jan 27, 2018 at 08:59:50PM +0100, Ævar Arnfjörð Bjarmason wrote: >> >> On Sat, Jan 27 2018, Filip Jorissen jotted: >> >>> I think our git repository is b

Cloned repository has file changes -> bug?

Dear all, I think our git repository is bugged. The reason why I say this is the following. When cloning the repository, the newly cloned repository immediately has file changes. Steps to reproduce and illustration is at the end of this email. Git checkout does not work to remove the file chang