From: help-debbugs@gnu.org (GNU bug Tracking System)
To: bug-guile@gnu.org
Subject: bug#46220: Acknowledgement (Fwd: Some non-standard O_* flags are missing)
Date: Sun, 31 Jan 2021 21:31:01 +0000 [thread overview]
Message-ID: <handler.46220.B.161212864326485.ack@debbugs.gnu.org> (raw)
In-Reply-To: 308932c261a6f953a498606fb45cb35e08988af5.camel@telenet.be
Thank you for filing a new bug report with debbugs.gnu.org.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
bug-guile@gnu.org
If you wish to submit further information on this problem, please
send it to 46220@debbugs.gnu.org.
Please do not send mail to help-debbugs@gnu.org unless you wish
to report a problem with the Bug-tracking system.
--
46220: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=46220
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
next prev parent reply other threads:[~2021-01-31 21:31 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 ` GNU bug Tracking System [this message]
2021-03-09 19:03 ` Maxime Devos
2021-05-02 14:05 ` Ludovic Courtès
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=handler.46220.B.161212864326485.ack@debbugs.gnu.org \
--to=help-debbugs@gnu.org \
--cc=46220@debbugs.gnu.org \
--cc=bug-guile@gnu.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).