I noticed that when using the Git Extensions on Windows to init
a bare repository that it does
git init --bare --shared=all
I've read the manual for the --shared
options. It seems a convenience to set folder permissions but the descriptions are very UNIX-y (e.g. umask
).
My remote repositories are going to be shared, but they're on a remote UNC share under Windows Authentication.
So, in my situation, is there any need for this --shared
option, for instance if I was initialising a repo from the command prompt?
Except from the permissions (that indeed might not work in windows), using the --shared
flag also sets the receive.denyNonFastForwards
config in shared repositories. Of course you could also set that manually if you want to...
Try running git init --bare --shared=all
from a git-bash
shell, and see if you get any reports regarding permissions.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With