From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 46220@debbugs.gnu.org
Subject: bug#46220: Fwd: Some non-standard O_* flags are missing
Date: Sun, 02 May 2021 16:05:19 +0200 [thread overview]
Message-ID: <87o8dt5izk.fsf@gnu.org> (raw)
In-Reply-To: <4eca22f89b0e02b71962d035de638095e2a72ed2.camel@telenet.be> (Maxime Devos's message of "Tue, 09 Mar 2021 20:03:27 +0100")
Hi Maxime,
Maxime Devos <maximedevos@telenet.be> skribis:
> From d769a75962c64804f354a0133494491626b8b2dc Mon Sep 17 00:00:00 2001
> From: Maxime Devos <maximedevos@telenet.be>
> Date: Tue, 2 Mar 2021 18:03:22 +0100
> Subject: [PATCH] Define `O_NOFOLLOW' and various other flags when supported.
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> * libguile/filesys.c (scm_init_filesys): Define ‘O_IGNORE_CTTY’,
> ‘O_NOLINK’, ‘O_NOFOLLOW’, ‘O_PATH’, ‘O_TMPFILE’, ‘O_SHLOCK’,
> ‘O_EXLOCK’, ‘O_ASYNC’, ‘O_NOATIME’, ‘O_DIRECTORY’, ‘O_CLOEXEC’
> and ‘O_DIRECT’ when available.
> ---
> libguile/filesys.c | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
The patch LGTM. I’ll apply it later today if there are no objections.
Thanks!
Ludo’.
next prev parent reply other threads:[~2021-05-02 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eee99a01c43dec23cd119f71b9a9758c7986aceb.camel@telenet.be>
2021-01-31 21:30 ` bug#46220: Fwd: Some non-standard O_* flags are missing Maxime Devos
2021-01-31 21:31 ` bug#46220: Acknowledgement (Fwd: Some non-standard O_* flags are missing) GNU bug Tracking System
2021-03-09 19:03 ` bug#46220: Fwd: Some non-standard O_* flags are missing Maxime Devos
2021-05-02 14:05 ` Ludovic Courtès [this message]
2021-05-08 10:05 ` Ludovic Courtès
2021-05-08 10:06 ` bug#46220: closed (Re: bug#46220: Fwd: Some non-standard O_* flags are missing) GNU bug Tracking System
2021-03-02 18:30 ` bug#46220: Some non-standard O_* flags are missing Maxime Devos
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8dt5izk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=46220@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).