public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Newlib <newlib@sourceware.org>,
	 Sam Edge <sre.2023.newlib@under-the-mountain.co.uk>
Subject: Re: Online documentation revisions
Date: Wed, 3 Jan 2024 18:11:57 -0500	[thread overview]
Message-ID: <CAOox84tSXyG-NRVY272ZbdmCR_ezPRkGRyF7EcDQGWc77X7ekw@mail.gmail.com> (raw)
In-Reply-To: <ZSutNHuBAezMr9We@vapier>

[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]

Hi Mike,

Sorry for the late reply.  Yes, this would be accepted and I can merge any
patch you want to make to the htdocs and push any manuals you want to put
on the ftp serer.

-- Jeff J.

On Sun, Oct 15, 2023 at 5:13 AM Mike Frysinger <vapier@gentoo.org> wrote:

> On 26 Sep 2023 16:27, Sam Edge via Newlib wrote:
> > 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?
>
> it should be easy to backfill manuals for each release if we wanted.
> something like:
> https://sourceware.org/newlib/
>         # current versions
>         libc.html
>         libm.html
>         libgloss.html
>         # old releases
>         manual/
>                 4.3.0/
>                         libc.html
>                         libm.html
>                         libgloss.html
>                 4.1.0/
>                         libc.html
>                         libm.html
>                         libgloss.html
>                 ...
>
> the html pages are checked into git.  so i could send a patch if someone
> would merge it (i don't have push access to the htdocs repo).
>
> there's also pdf and such files, but those are only uploaded to the ftp
> server, and i don't have access to that either.
>
> before i write a script to do the backfill, would be nice to hear a signal
> from the newlib maintainers that this would be accepted.
> -mike
>

      reply	other threads:[~2024-01-03 23:12 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
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 [this message]

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=CAOox84tSXyG-NRVY272ZbdmCR_ezPRkGRyF7EcDQGWc77X7ekw@mail.gmail.com \
    --to=jjohnstn@redhat.com \
    --cc=newlib@sourceware.org \
    --cc=sre.2023.newlib@under-the-mountain.co.uk \
    --cc=vapier@gentoo.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).