Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
Pushing to a directory directly.
What did you expect to happen? (Expected behavior)
Good behavior
What happened instead? (Actual behavior)
Disk errors. After pushing to a directory (my origin field is C:\Work
for example) the git repository will be corrupted.
Moreover causing disk errors not only in the target git bare repository.
I've loosed some other files.
Cannot be reproduced exactly. However I have decided to report this
problem.
I've experienced this problem for several years.
What's different between what you expected and what actually happened?
Described.
Anything else you want to add:
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.31.1.windows.1
cpu: x86_64
built from commit: c5f0be26a7e3846e3b6268d1c6c4800d838c6bbb
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 19044
compiler info: gnuc: 10.2
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe
[Enabled Hooks]
