public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: [PATCH 0/5] Various improvements to newlib manpages build
Date: Wed, 4 May 2022 20:37:58 -0400	[thread overview]
Message-ID: <CAOox84vaFGZJkvvfObu_+z1dLt81d+R6j6nHK=yiEG8dwDJsWg@mail.gmail.com> (raw)
In-Reply-To: <20220502125518.19808-1-jon.turney@dronecode.org.uk>

Thanks Jon.  Patches merged.

-- Jeff J.

On Mon, May 2, 2022 at 8:55 AM Jon Turney <jon.turney@dronecode.org.uk>
wrote:

> Jon Turney (5):
>   Simplify rules for creating man pages
>   Add build avoidance for 'make man'
>   Silence xsltproc when writing manpages
>   Fix warning about duplicate id in docbook XML
>   Generate manpages for functions in chapter sys.tex
>
>  newlib/Makefile.am                 |  3 +++
>  newlib/doc/chapter-texi2docbook.py |  2 +-
>  newlib/libc/Makefile.inc           | 17 ++++++++---------
>  newlib/libc/libc.in.xml            |  4 +++-
>  newlib/libm/Makefile.inc           | 17 ++++++++---------
>  5 files changed, 23 insertions(+), 20 deletions(-)
>
> --
> 2.36.0
>
>

      parent reply	other threads:[~2022-05-05  0:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 12:55 Jon Turney
2022-05-02 12:55 ` [PATCH 1/5] Simplify rules for creating man pages Jon Turney
2022-05-08 19:42   ` Mike Frysinger
2022-05-02 12:55 ` [PATCH 2/5] Add build avoidance for 'make man' Jon Turney
2022-05-02 12:55 ` [PATCH 3/5] Silence xsltproc when writing manpages Jon Turney
2022-05-02 12:55 ` [PATCH 4/5] Fix warning about duplicate id in docbook XML Jon Turney
2022-05-02 12:55 ` [PATCH 5/5] Generate manpages for functions in chapter sys.tex Jon Turney
2022-05-05  0:37 ` 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='CAOox84vaFGZJkvvfObu_+z1dLt81d+R6j6nHK=yiEG8dwDJsWg@mail.gmail.com' \
    --to=jjohnstn@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).