From: Corinna Vinschen <vinschen@redhat.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: newlib@sourceware.org
Subject: Re: [PATCH 0/4] fenv doc fixes
Date: Tue, 13 Aug 2019 07:51:00 -0000 [thread overview]
Message-ID: <20190813075150.GS11632@calimero.vinschen.de> (raw)
In-Reply-To: <20190812183037.55230-1-jon.turney@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
On Aug 12 19:30, Jon Turney wrote:
> Jon Turney (4):
> fenv: fe_dfl_env.c doesn't contain any documentation
> fenv: Fix mangled makedoc markup
> fenv: Fix typo-ed variable name in documentation
> fenv: Update makedocbookpy for eae68bfc
>
> newlib/doc/makedocbook.py | 4 +++-
> newlib/libm/fenv/Makefile.am | 2 +-
> newlib/libm/fenv/Makefile.in | 2 +-
> newlib/libm/fenv/fegetexceptflag.c | 2 +-
> newlib/libm/fenv/feraiseexcept.c | 2 +-
> newlib/libm/fenv/fesetenv.c | 4 ++--
> newlib/libm/fenv/fesetexceptflag.c | 4 ++--
> newlib/libm/fenv/feupdateenv.c | 6 +++---
> 8 files changed, 14 insertions(+), 12 deletions(-)
>
> --
> 2.21.0
LGTM, please push.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-13 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 18:30 Jon Turney
2019-08-12 18:30 ` [PATCH 2/4] fenv: Fix mangled makedoc markup Jon Turney
2019-08-12 18:31 ` [PATCH 3/4] fenv: Fix typo-ed variable name in documentation Jon Turney
2019-08-12 18:31 ` [PATCH 1/4] fenv: fe_dfl_env.c doesn't contain any documentation Jon Turney
2019-08-12 18:31 ` [PATCH 4/4] fenv: Update makedocbookpy for eae68bfc Jon Turney
2019-08-12 18:45 ` [PATCH 0/4] fenv doc fixes Joel Sherrill
2019-08-13 7:51 ` Corinna Vinschen [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=20190813075150.GS11632@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=jon.turney@dronecode.org.uk \
--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).