From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: and my ship fades off into the nite
Date: Wed, 16 Mar 2022 23:15:55 -0400 [thread overview]
Message-ID: <YjKn62oOQ9cHYLDU@vapier> (raw)
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
just a heads up that i've largely "completed" the work that i intend to on the
libgloss & newlib build systems. hopefully people find it better off than when
i started. i'll still be around, so if i introduced a regression, i'm happy to
take a look. if people have questions, hopefully the documentation updates i
merged will cover it, or i can explain things as needed. but other than the
few minor patches i've already posted, i don't have anything else scheduled.
i'm off to find another project to procrastinate on instead.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-03-17 3:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 3:15 Mike Frysinger [this message]
2022-03-17 6:32 ` Sebastian Huber
2022-03-17 9:51 ` Corinna Vinschen
2022-03-17 13:28 ` Joel Sherrill
2022-03-17 18:15 ` Jeff Johnston
2022-03-23 10:08 ` Sebastian Huber
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=YjKn62oOQ9cHYLDU@vapier \
--to=vapier@gentoo.org \
--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).