From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: newlib@sourceware.org
Cc: Sam Edge <sre.2023.newlib@under-the-mountain.co.uk>
Subject: Re: Online documentation revisions
Date: Tue, 26 Sep 2023 11:00:52 -0600 [thread overview]
Message-ID: <3e01afb5-604b-f299-8a4c-59abbf111379@Shaw.ca> (raw)
In-Reply-To: <20e59c61-a3f1-41e1-92a6-c5683bc6832d@under-the-mountain.co.uk>
On 2023-09-26 09:27, Sam Edge wrote:
> It's my first time here so apologies if I'm being thick.
> Is there any way to see the online documentation for Newlib for a given release?
> I often get lumbered with having to use older revisions (3.0.0!) that don't come
> with source or pre-built HTML or other documentation. (Yes, STM, I'm talking to
> you!)
> Is there a way to see the state of the online docs at a given revision?
Had a similar issue wanting to see libc docs for Cygwin builds.
Check out repo at that rev, configure into out of tree build and install dirs,
then under e.g. build-3.0.0/newlib run to get into your e.g.
install-3.0.0/usr/share/{info,man} dirs:
$ make info man && make install info man
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-09-26 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 15:27 Sam Edge
2023-09-26 17:00 ` Brian Inglis [this message]
2023-09-26 17:12 ` Sam Edge
2023-09-27 8:42 ` Sam Edge
2023-09-27 22:19 ` Brian Inglis
2023-09-28 6:37 ` Sam Edge
2023-10-15 9:13 ` Mike Frysinger
2024-01-03 23:11 ` Jeff Johnston
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=3e01afb5-604b-f299-8a4c-59abbf111379@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=newlib@sourceware.org \
--cc=sre.2023.newlib@under-the-mountain.co.uk \
/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).