public inbox for newlib-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org> To: newlib-cvs@sourceware.org Subject: [newlib-cygwin] newlib: use https:// URIs in more places Date: Thu, 17 Feb 2022 05:49:44 +0000 (GMT) [thread overview] Message-ID: <20220217054944.38CA23858D20@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=bf9f6a0984c0eefd3f4d218cd7260030c5f689a2 commit bf9f6a0984c0eefd3f4d218cd7260030c5f689a2 Author: Mike Frysinger <vapier@gentoo.org> Date: Thu Feb 17 00:48:58 2022 -0500 newlib: use https:// URIs in more places Diff: --- newlib/HOWTO | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/newlib/HOWTO b/newlib/HOWTO index 3a214edf4..668766096 100644 --- a/newlib/HOWTO +++ b/newlib/HOWTO @@ -38,7 +38,7 @@ and TeX (or `texi2roff') to typeset the printed version. While Newlib contains a copy of the texinfo package (texinfo.tex), the manual for it is not included. The latest one may be found at -http://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html +https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html (which could be for a newer version of texinfo.tex than is included in Newlib). @@ -79,12 +79,12 @@ purpose of Linux-based open standards for embedded development. In brief, the intent is to define multiple levels for API functions that allows the user to size the library appropriately for their application--at least in terms of the predefined lists. For full details, refer to the EL/IX home -page at http://sourceware.org/elix/. The likely best way to tell how to +page at https://sourceware.org/elix/. The likely best way to tell how to classify any new functions in terms of needing an ELIX level qualification is to ask Jeff Johnston. To see how it works and try classification on your own, refer to the API specification on the web site, -http://sourceware.org/elix/api/current/api.pdf. +https://sourceware.org/elix/api/current/api.pdf (Unfortunately, it is not complete with respect to either the C99 or POSIX standards, so particular C and POSIX functions may or may not be found.)
reply other threads:[~2022-02-17 5:49 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220217054944.38CA23858D20@sourceware.org \ --to=vapier@sourceware.org \ --cc=newlib-cvs@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: linkBe 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).