One minor annoyance with that is that .bzr.log is created with the executable bit set due to O_CREAT. As per the open(2) man page:
The effective permissions are modified by the process's umask in the usual way: The permissions of the created file are (mode & ~umask).
On my system the mask is 022. I suppose we can do a chown specifically to unset executable bit. Thoughts?
Note: This isn't tested on Windows yet as I don't have a windows system available at the moment.
« Back to merge proposal
One minor annoyance with that is that .bzr.log is created with the executable bit set due to O_CREAT. As per the open(2) man page:
The effective permissions are modified by the process's umask in the usual way: The permissions of the created file are (mode & ~umask).
On my system the mask is 022. I suppose we can do a chown specifically to unset executable bit. Thoughts?
Note: This isn't tested on Windows yet as I don't have a windows system available at the moment.