On Wed, Dec 13, 2017 at 7:57 AM, Matthijs Kooijman wrote:
>
>> I think the inconsistency in the handling of umask on *BSD systems is
>> a bug. Please open an issue for that at https://golang.org/issue.
> Ok: https://github.com/golang/go/issues/23120
>
>> We've discussed in the past how much to do
Hi Ian,
> I think the inconsistency in the handling of umask on *BSD systems is
> a bug. Please open an issue for that at https://golang.org/issue.
Ok: https://github.com/golang/go/issues/23120
> We've discussed in the past how much to document umask in the os
> package. After all, umask is a s
On Wed, Dec 13, 2017 at 5:46 AM, wrote:
>
> I just ran into some inconsistencies wrt permissions and `os.Mkdir()`, at
> least on Linux. I'm not sure what part of this is actual bugs that need to
> be fixed and what is a documentation bug, but let me state what I've found.
>
> The documentation fo
Hi,
I just ran into some inconsistencies wrt permissions and `os.Mkdir()`, at
least on Linux. I'm not sure what part of this is actual bugs that need to
be fixed and what is a documentation bug, but let me state what I've found.
The documentation for Mkdir says: "Mkdir creates a new directory w