From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Re: [Patch] APE changes (2019 Lufia patches)
Date: Sun, 28 Feb 2021 19:41:51 -0800 [thread overview]
Message-ID: <CB3454E7C04DB86ECA0CF57E0DE179AD@eigenstate.org> (raw)
In-Reply-To: <5591aeb1a24fac8a3e472085c5be336c.squirrel@mx.sdf.org>
Quoth bsdsm@sdf.org:
>
> Sorry for the delay. Attached are the changes, minus architecture
> specific code, with interests separated as previously discussed.
>
> Please allow me a moment to address my intentions. My goals are more
> human than software related. I began working on a port of Lufia's
> changes not long after the pull requests. I stopped for some of the
> reasons already discussed: git9, libressl isn't desired, etc. I
> decided to put something together only after finding out that those
> original patches are still in limbo after two years through 9fans. My
> intention being that if even a single line presented was thought
> worthy of import then I could reach out to Lufia and say, 'hey check
> this out, and maybe your next patch can come straight to 9front.'
>
> Perhaps my goals were misguided. It is not my intention to denigrate
> anyone, 9fan or otherwise.
>
> As a final note I agree with the comments made previously about
> nitpicking the changes. Please nitpick everything. I just wanted to
> make my intentions clearer.
>
Thanks for posting -- I'll start looking
over it in the next while; if I don't post
an initial response in 2 weeks, please feel
free to ping.
next prev parent reply other threads:[~2021-03-01 3:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 2:48 [9front] " bsdsm
2021-02-22 4:14 ` ori
2021-02-22 5:20 ` Jens Staal
2021-02-25 2:15 ` ori
2021-02-25 2:21 ` ori
2021-02-25 16:37 ` Aaron
2021-02-25 18:06 ` ori
2021-02-26 10:28 ` cinap_lenrek
2021-02-26 15:38 ` Lucas Francesco
2021-02-26 19:23 ` [9front] " bsdsm
2021-03-01 3:41 ` ori [this message]
2021-03-15 3:20 ` ori
2021-03-15 3:36 ` 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=CB3454E7C04DB86ECA0CF57E0DE179AD@eigenstate.org \
--to=ori@eigenstate.org \
--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).