From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH htdocs 4/7] refressh libc & libm manual from current git
Date: Mon, 14 Feb 2022 21:28:52 -0500 [thread overview]
Message-ID: <YgsP5C/J/0tqJIdM@vapier> (raw)
In-Reply-To: <20220215022552.11267-1-vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
---
had to compress to fit on the mailing list
libc.html | 24561 ++++++++++++++++++++++++++----------------------
libc_toc.html | 485 -
libm.html | 2764 +++---
libm_toc.html | 133 -
4 files changed, 14769 insertions(+), 13174 deletions(-)
delete mode 100644 libc_toc.html
delete mode 100644 libm_toc.html
[-- Attachment #2: 0004-refressh-libc-libm-manual-from-current-git.patch.xz --]
[-- Type: application/x-xz, Size: 179308 bytes --]
next prev parent reply other threads:[~2022-02-15 2:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 2:25 [PATCH htdocs 0/7] various website updates Mike Frysinger
2022-02-15 2:25 ` [PATCH htdocs 2/7] switch to https:// for many sites Mike Frysinger
2022-02-15 2:25 ` [PATCH htdocs 3/7] add libgloss manual from current git Mike Frysinger
2022-02-15 2:25 ` [PATCH htdocs 5/7] simplify mailing list news links Mike Frysinger
2022-02-15 2:25 ` [PATCH htdocs 6/7] update news entries for last few years Mike Frysinger
2022-02-15 2:25 ` [PATCH htdocs 7/7] update autotools faq entry to match current tree Mike Frysinger
2022-02-15 2:27 ` [PATCH htdocs 1/7] crush images Mike Frysinger
2022-02-17 6:27 ` Brian Inglis
2022-02-17 15:56 ` Brian Inglis
2022-02-15 2:28 ` Mike Frysinger [this message]
2022-02-16 10:56 ` [PATCH htdocs 0/7] various website updates Corinna Vinschen
2022-02-17 1:39 ` Mike Frysinger
2022-02-17 12:07 ` Corinna Vinschen
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=YgsP5C/J/0tqJIdM@vapier \
--to=vapier@gentoo.org \
--cc=newlib@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).