From: Corinna Vinschen <vinschen@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: newlib@sourceware.org
Subject: Re: [PATCH 1/5 v3] newlib: libm: move manual into top-level build
Date: Sat, 5 Feb 2022 13:13:43 +0100 [thread overview]
Message-ID: <Yf5p90lU9mqlO0gy@calimero.vinschen.de> (raw)
In-Reply-To: <20220201062107.19266-1-vapier@gentoo.org>
On Feb 1 01:21, Mike Frysinger wrote:
> This doesn't migrate all the docs, just the libm's manual (pdf/info).
> This is to show the basic form of migrating the chew files.
> ---
> v3: fix .stamp handling with tex generation
>
> newlib/Makefile.am | 9 +
> newlib/Makefile.in | 443 ++++++++++++++++++++++++++++---
> newlib/doc/local.mk | 11 +
> newlib/libm/Makefile.am | 27 +-
> newlib/libm/Makefile.in | 398 +++------------------------
> newlib/libm/Makefile.inc | 28 ++
> newlib/libm/common/Makefile.am | 14 +-
> newlib/libm/common/Makefile.in | 22 +-
> newlib/libm/common/Makefile.inc | 10 +
> newlib/libm/complex/Makefile.am | 12 +-
> newlib/libm/complex/Makefile.in | 18 +-
> newlib/libm/complex/Makefile.inc | 8 +
> newlib/libm/fenv/Makefile.am | 11 +-
> newlib/libm/fenv/Makefile.in | 15 +-
> newlib/libm/fenv/Makefile.inc | 7 +
> newlib/libm/math/Makefile.am | 15 +-
> newlib/libm/math/Makefile.in | 23 +-
> newlib/libm/math/Makefile.inc | 11 +
> newlib/libm/mathfp/Makefile.am | 35 +--
> newlib/libm/mathfp/Makefile.in | 42 +--
> newlib/libm/mathfp/Makefile.inc | 31 +++
> 21 files changed, 634 insertions(+), 556 deletions(-)
> create mode 100644 newlib/libm/Makefile.inc
> create mode 100644 newlib/libm/common/Makefile.inc
> create mode 100644 newlib/libm/complex/Makefile.inc
> create mode 100644 newlib/libm/fenv/Makefile.inc
> create mode 100644 newlib/libm/math/Makefile.inc
> create mode 100644 newlib/libm/mathfp/Makefile.inc
Did I miss a GTG somewhere or why is this patchset already applied?
Corinna
next prev parent reply other threads:[~2022-02-05 12:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 4:32 [PATCH 0/5] migrate documentation into top-level Mike Frysinger
2022-01-22 4:32 ` [PATCH 1/5] newlib: libm: move manual into top-level build Mike Frysinger
2022-01-22 4:32 ` [PATCH 2/5] newlib: libc: include all chapters all the time in the manual Mike Frysinger
2022-01-22 4:32 ` [PATCH 3/5] newlib: libc: move manual into top-level build Mike Frysinger
2022-01-24 14:30 ` Corinna Vinschen
2022-01-22 4:32 ` [PATCH 4/5] newlib: move man page generation " Mike Frysinger
2022-01-22 4:32 ` [PATCH 5/5] newlib: drop shared documentation rules Mike Frysinger
2022-01-28 7:58 ` [PATCH 1/5 v2] newlib: libm: move manual into top-level build Mike Frysinger
2022-01-28 7:58 ` [PATCH 2/5 v2] newlib: libc: include all chapters all the time in the manual Mike Frysinger
2022-01-28 7:58 ` [PATCH 3/5 v2] newlib: libc: move manual into top-level build Mike Frysinger
2022-01-28 7:58 ` [PATCH 4/5 v2] newlib: move man page generation " Mike Frysinger
2022-01-28 7:58 ` [PATCH 5/5 v2] newlib: drop shared documentation rules Mike Frysinger
2022-01-31 14:58 ` [PATCH 1/5 v2] newlib: libm: move manual into top-level build Jon Turney
2022-02-01 3:40 ` Mike Frysinger
2022-02-01 14:37 ` Jon Turney
2022-02-01 6:21 ` [PATCH 1/5 v3] " Mike Frysinger
2022-02-01 6:21 ` [PATCH 2/5 v3] newlib: libc: include all chapters all the time in the manual Mike Frysinger
2022-02-01 6:21 ` [PATCH 3/5 v3] newlib: libc: move manual into top-level build Mike Frysinger
2022-02-01 6:21 ` [PATCH 4/5 v3] newlib: move man page generation " Mike Frysinger
2022-02-01 14:37 ` Jon Turney
2022-02-01 23:12 ` Mike Frysinger
2022-02-01 6:21 ` [PATCH 5/5 v3] newlib: drop shared documentation rules Mike Frysinger
2022-02-05 12:13 ` Corinna Vinschen [this message]
2022-02-05 18:04 ` [PATCH 1/5 v3] newlib: libm: move manual into top-level build Mike Frysinger
2022-02-07 10:30 ` 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=Yf5p90lU9mqlO0gy@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.org \
--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).