From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] move zlib source from ghostscript to ape/lib/z and update to latest zlib
Date: Tue, 3 Mar 2020 10:08:53 +0000 [thread overview]
Message-ID: <CAFSF3XP8Hpa+0FE3e0oqDn=KmhL0+QLrjBbbTUsOgxbLxh3d5Q@mail.gmail.com> (raw)
In-Reply-To: <B89D4ECE0800262103215122680CC112@eigenstate.org>
> I think it's worth trying to change that situation, so we actually
> maintain the things we decide are worth porting.
at what cost though? i would propose creating infrastructure and
processes that make it *easier* to do, but i think many libraries are
moving too fast nowadays to track even one of them.
next prev parent reply other threads:[~2020-03-03 10:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 23:08 kokamoto
2020-03-03 0:49 ` Steve Simon
2020-03-03 1:01 ` ori
2020-03-03 10:06 ` hiro
2020-03-03 10:08 ` hiro [this message]
2020-03-03 10:12 ` hiro
2020-03-03 14:01 ` ori
2020-03-03 13:58 ` ori
-- strict thread matches above, loose matches on Subject: below --
2020-03-03 11:05 kokamoto
2020-03-03 6:36 kokamoto
2020-03-02 5:15 Lucas Francesco
2020-03-02 8:33 ` [9front] " cinap_lenrek
2020-03-02 14:41 ` ori
2020-03-05 19:17 ` cinap_lenrek
2020-03-08 23:44 ` Lucas Francesco
2020-03-16 3:28 ` ori
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='CAFSF3XP8Hpa+0FE3e0oqDn=KmhL0+QLrjBbbTUsOgxbLxh3d5Q@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.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 NNTP newsgroup(s).