From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] patches from 9front
Date: Fri, 12 Feb 2021 09:42:40 -0800 [thread overview]
Message-ID: <1AB3C85FA8602E158A39115FEDA50BBA@eigenstate.org> (raw)
In-Reply-To: <CAJSxfmKTiZqGAisvDs+1KXVyCCDYUPQVCXNVmv9H9h4VtH7xMQ@mail.gmail.com>
Quoth Skip Tavakkolian <skip.tavakkolian@gmail.com>:
> I think the question of whether a patch is applied to the repo or
> kept as an optional patch should be: does it benefit everyone
> without breaking anything, fixes a bug, or enhances security? I
> use 9p.io as a reference for my setup. I appreciate that David
> has been judicious with the application of patches to the
> mainline.
"no" is a fine answer; my complaint is that nobody
has said it. Lufia's patch is over 2 years old.
Echoline's suggestion to port dp9ik has lead to
a valid question on what sort of review dp9ik has
had, and then silence.
What review would be needed? Who would do it?
Would 9legacy prefer to leave passwords brute
forcable by default? Any decision would be fine,
but from my reading this thread, I don't see one.
Instead, there was a long thread about some sort of
unified plan 9, without anyone mentioning what they
want to unify -- or even discussing differences.
No code was mentioned by name, and none appears to
be on the way.
(As far as I'm aware, I've already cherry picked most
relevant plan9port and 9legacy bugfixes into 9front.
Are there any that I missed?)
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc82939f1fda0e479-M6d60ab3efd4369aa75e3598c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-02-12 17:42 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 3:27 Eli Cohen
2021-02-10 3:37 ` Lucio De Re
2021-02-10 3:47 ` Eli Cohen
2021-02-10 4:14 ` Lucio De Re
2021-02-10 7:24 ` Skip Tavakkolian
2021-02-10 16:15 ` ori
2021-02-10 21:50 ` Eli Cohen
2021-02-10 22:00 ` ori
2021-02-10 22:26 ` David du Colombier
2021-02-11 5:49 ` ori
2021-02-11 7:24 ` Lucio De Re
2021-02-11 8:57 ` Jens Staal
2021-02-11 10:31 ` hiro
2021-02-11 11:57 ` Lucio De Re
2021-02-11 13:07 ` hiro
2021-02-11 17:41 ` pouya+lists.9fans
2021-02-11 8:40 ` David du Colombier
2021-02-12 1:21 ` ori
2021-02-12 2:55 ` Skip Tavakkolian
2021-02-12 17:42 ` ori [this message]
2021-02-12 17:48 ` sirjofri
2021-02-12 18:09 ` ori
2021-02-12 20:46 ` Lucio De Re
2021-02-12 23:54 ` Anthony Martin
2021-02-13 13:34 ` hiro
2021-02-13 14:05 ` Lucio De Re
2021-02-13 15:30 ` hiro
2021-02-22 18:44 ` David du Colombier
2021-02-23 4:45 ` ori
2021-03-19 14:41 ` Eli Cohen
2021-03-21 0:01 ` kokamoto
2021-03-21 8:33 ` David du Colombier
2021-03-21 9:46 ` hiro
2021-03-21 11:07 ` David du Colombier
2021-03-21 14:38 ` David du Colombier
2021-03-21 13:02 ` Ethan Gardener
2021-02-12 16:39 ` ori
2021-02-10 13:49 ` Steve Simon
2021-02-12 11:09 ` [9fans] 9pi provenance Richard Miller
2021-02-12 11:56 ` pouya+lists.9fans
2021-02-13 14:42 ` David du Colombier
2021-02-13 14:47 ` Richard Miller
2021-02-13 14:53 ` David du Colombier
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=1AB3C85FA8602E158A39115FEDA50BBA@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
/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).