From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH v2] newlib: update build system generation documentation
Date: Fri, 25 Feb 2022 14:47:08 +0100 [thread overview]
Message-ID: <Yhjd3N+7XufCuQMQ@calimero.vinschen.de> (raw)
In-Reply-To: <20220225041034.21195-1-vapier@gentoo.org>
On Feb 24 23:10, Mike Frysinger wrote:
> Replace all of the individual autotool steps with a single autoreconf.
> This simplifies the documentation greatly, and in the current system,
> only takes ~10 seconds to regenerate everything.
>
> Update the developer documentation to cover all the major components
> of the current build system. Hopefully this is a fairly complete road
> map to everything. I tried to include everything that I wish I knew
> when I started hacking on this :P.
> ---
> newlib/HOWTO | 169 ++++++++++++++++++++++++++++++++++++++++++++++++++
> newlib/NEWS | 1 +
> newlib/README | 91 ++++++---------------------
> 3 files changed, 189 insertions(+), 72 deletions(-)
GTG
Thx,
Corinna
prev parent reply other threads:[~2022-02-25 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 5:52 [PATCH/RFC] " Mike Frysinger
2022-02-23 9:21 ` Corinna Vinschen
2022-02-24 3:20 ` Mike Frysinger
2022-02-24 9:22 ` Corinna Vinschen
2022-02-25 4:10 ` [PATCH v2] " Mike Frysinger
2022-02-25 13:47 ` 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=Yhjd3N+7XufCuQMQ@calimero.vinschen.de \
--to=vinschen@redhat.com \
--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).