From: Bruno Haible <bruno@clisp.org>
To: libc-alpha@sourceware.org
Subject: published documentation
Date: Sun, 20 Mar 2022 15:40:49 +0100 [thread overview]
Message-ID: <3188887.clyjiGRsXx@omega> (raw)
Glibc 2.35 has been released more than a month ago [1][2],
but the published documentation [3] is still the one of version 2.34.
[1] https://mail.gnu.org/archive/html/info-gnu/2022-02/msg00002.html
[2] https://ftp.gnu.org/gnu/glibc/
[3] https://www.gnu.org/software/libc/manual/
next reply other threads:[~2022-03-20 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 14:40 Bruno Haible [this message]
2022-03-20 20:04 ` Paul Eggert
2022-03-20 21:08 ` Bruno Haible
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=3188887.clyjiGRsXx@omega \
--to=bruno@clisp.org \
--cc=libc-alpha@sourceware.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).