From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Cc: Jon TURNEY <jon.turney@dronecode.org.uk>
Subject: Re: [PATCH 1/5 v3] newlib: libm: move manual into top-level build
Date: Mon, 7 Feb 2022 11:30:47 +0100 [thread overview]
Message-ID: <YgD01/82C0UTgGN1@calimero.vinschen.de> (raw)
In-Reply-To: <Yf68IlCPNBpC0c3X@vapier>
On Feb 5 13:04, Mike Frysinger wrote:
> On 05 Feb 2022 13:13, Corinna Vinschen wrote:
> > 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.
> > > ---
> >
> > Did I miss a GTG somewhere or why is this patchset already applied?
>
> sorry, i thought when you said early you were "fine with this change" (other
> than local.mk which i addressed), it meant you were fine with merging it.
Understood. I was still waiting for the result of your discussion
with jturney. Jon, anything you'd still like to discuss?
> i can pull it back out if there's something about it you didn't like.
No, it's ok, we can change or fix details in subsequent patches.
Thanks,
Corinna
prev parent reply other threads:[~2022-02-07 10:30 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 ` [PATCH 1/5 v3] newlib: libm: move manual into top-level build Corinna Vinschen
2022-02-05 18:04 ` Mike Frysinger
2022-02-07 10:30 ` 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=YgD01/82C0UTgGN1@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).