Re: [PATCH RFC 3/3] openat2.2: document new openat2(2) syscall

2019-10-09 Thread Michael Kerrisk (man-pages)
Hello Aleksa, On 10/9/19 12:17 PM, Aleksa Sarai wrote: > On 2019-10-09, Michael Kerrisk (man-pages) wrote: >> Hello Aleksa, >> >> Thanks for this. It's a great piece of documentation work! >> >> I would prefer the path_resolution(7) piece as a separate patch. > > Thanks, and will do. > >> On 10

Re: [PATCH RFC 3/3] openat2.2: document new openat2(2) syscall

2019-10-09 Thread Aleksa Sarai
On 2019-10-09, Michael Kerrisk (man-pages) wrote: > Hello Aleksa, > > Thanks for this. It's a great piece of documentation work! > > I would prefer the path_resolution(7) piece as a separate patch. Thanks, and will do. > On 10/3/19 4:55 PM, Aleksa Sarai wrote: > > Rather than trying to merge t

Re: [PATCH RFC 3/3] openat2.2: document new openat2(2) syscall

2019-10-09 Thread Michael Kerrisk (man-pages)
Hello Aleksa, Thanks for this. It's a great piece of documentation work! I would prefer the path_resolution(7) piece as a separate patch. On 10/3/19 4:55 PM, Aleksa Sarai wrote: > Rather than trying to merge the new syscall documentation into open.2 > (which would probably result in the man-pag

[PATCH RFC 3/3] openat2.2: document new openat2(2) syscall

2019-10-03 Thread Aleksa Sarai
Rather than trying to merge the new syscall documentation into open.2 (which would probably result in the man-page being incomprehensible), instead the new syscall gets its own dedicated page with links between open(2) and openat2(2) to avoid duplicating information such as the list of O_* flags or