From: Renzo Davoli <renzo@cs.unibo.it>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: utimensat(2) and faccessat(2): man pages do not mention AT_EMPTY_PATH flag
Date: Mon, 1 Jan 2024 16:48:37 +0100 [thread overview]
Message-ID: <ZZLe1Zg60z2Y0ON_@cs.unibo.it> (raw)
In-Reply-To: <ZZKled8QpdxwC90B@debian>
Hi Alex,
great. thank you.
I wish you have a happy new year to you, too.
renzo
On Mon, Jan 01, 2024 at 12:43:53PM +0100, Alejandro Colomar wrote:
> [CCing again linux-man@]
>
> Dear Renzo,
>
> On Sat, Dec 09, 2023 at 05:37:21PM +0100, Renzo Davoli wrote:
> > Dear Alex,
> >
> > On Sat, Dec 09, 2023 at 01:00:08PM +0100, Alejandro Colomar wrote:
> > > On Wed, Dec 06, 2023 at 12:04:07PM +0100, Renzo Davoli wrote:
> > > > utimensat and faccessat support the flag AT_EMPTY_PATH since Linux 5.8 but
> > > > this option is still missing in the man pages.
> > > Thanks for reporting that. Would you mind preparing a patch updating
> > > the page? If you need any help, just ask for it.
> >
> > No problem. It is here attached. Let me know if it's okay.
>
> Normally, you should send a patch with a commit message (as formatted by
> git-format-patch(1)). However, I've written something based on your
> original mail, so you don't need to do it. I also signed it with your
> name.
>
> Patch applied here:
> <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=26cdb3ebb2f6bd5a0c947bcf46e35b7c07759632>
>
> Thanks!
>
> Have a lovely year,
> Alex
prev parent reply other threads:[~2024-01-01 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 11:04 utimensat(2) and faccessat(2): man pages do not mention AT_EMPTY_PATH flag Renzo Davoli
2023-12-09 12:00 ` Alejandro Colomar
2023-12-09 16:38 ` Renzo Davoli
2023-12-09 21:36 ` Alejandro Colomar
2023-12-10 8:07 ` Renzo Davoli
[not found] ` <ZXSXwZMWbojebpH1@cs.unibo.it>
2024-01-01 11:43 ` Alejandro Colomar
2024-01-01 15:48 ` Renzo Davoli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZZLe1Zg60z2Y0ON_@cs.unibo.it \
--to=renzo@cs.unibo.it \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).