> How do you know that your repository was damaged? > Can you give instructions to reproduce the problem from scratch?
I wanted now to make a testcase but while doing so I have noticed that the repository doesn't got damaged but I got still errors (like seeing no commits anymore) because the permissions were still missing. My user uses a default umask of 077 which is propably causing this behavior if combined with sudo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347814 Title: git-gc can damage a repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1347814/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
