From: ori@eigenstate.org
To: ori@eigenstate.org, lucas.francesco93@gmail.com
Cc: 9front@9front.org
Subject: Re: [9front] zlib update
Date: Mon, 8 Jun 2020 20:12:23 -0700 [thread overview]
Message-ID: <B9AA8E35D518D510FC03C2CFFCDB5A3B@eigenstate.org> (raw)
In-Reply-To: <247D66612240058628E95EDDC861DC91@eigenstate.org>
> I don't see any changes to /sys/include/ape/zlib.h: did you forget
> to include that in the diff, or did the header stay the same?
Ignore that -- it's a dumb wrapper that stayed the same.
This looks good to me, I can just drop the manpage on my end
when I commit after baking it in a bit on my machine.
prev parent reply other threads:[~2020-06-09 3:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 22:06 Lucas Francesco
2020-05-27 22:43 ` ori
2020-06-09 2:06 ` Lucas Francesco
2020-06-09 3:10 ` ori
2020-06-09 3:12 ` ori [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=B9AA8E35D518D510FC03C2CFFCDB5A3B@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=lucas.francesco93@gmail.com \
/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).