From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] fqa: request for requests
Date: Fri, 15 Jan 2021 21:18:44 +0100 [thread overview]
Message-ID: <CAFSF3XMnQQv1TQdUXgMh4o2CqM=HLjLbpkDXx2g9LtJun6X2=Q@mail.gmail.com> (raw)
In-Reply-To: <CAPZaUOfR_+6CFaBx-5Sai7tjgM==a8-bmiGMDan6hbq1huvi+w@mail.gmail.com>
> More on forgetting you are in the wrong namespace
try mycroftiv's grio, it will help color your namespaces.
can't come up with any other responses for your requests, sorry :D
On 1/15/21, William Gunnells <thinktankworkspaces@gmail.com> wrote:
> The satire wasn't so bad. But you can't please everyone. Maybe an
> additional section for dummies like myself. Like being more productive
> inside plan9. I remember reading on some plan9 website about goals of
> accomplishing certain things such as CPU/Auth, Mail, users, to
> eventual decentralize and or grid. Maybe more on Plan9 as a Desktop. I
> spend a lot of time ssh to a linux to do something and not enough time
> IN plan9. I guess it's hard to make the jump and this would be beyond
> scope of FQA but would be helpful nonetheless. It's asking too much.
> Perhaps I just want more youtube video's of plan9 users actually using
> it and being productive beyond how to use install, Acme or draw. More
> on forgetting you are in the wrong namespace, screwing up credentials,
> constant issues with TLS problems or expire, or your forgot mount use
> something. Or if you are cpu into another system copy to this
> directory to grab the data and maybe compile locally.
>
>
> On Fri, Jan 15, 2021 at 12:16 AM Stanley Lieber <sl@stanleylieber.com>
> wrote:
>>
>> okay, let's self-police. it is not my intention to clog this mailing list
>> with meta discussion, but it has been brought to my attention (again) that
>> people are unhappy.
>>
>> what in the fqa offends you and should be removed?
>>
>> please feel free to respond publicly or privately.
>>
>> sl
>
next prev parent reply other threads:[~2021-01-15 20:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 7:47 Stanley Lieber
2021-01-15 8:52 ` Rodrigo G. López
2021-01-15 9:28 ` Daniel Morandini
2021-01-15 9:50 ` roy niang
2021-01-15 10:32 ` hiro
2021-01-15 11:18 ` roy niang
2021-01-15 10:49 ` Daniel Morandini
2021-01-15 10:56 ` hiro
2021-01-15 12:17 ` Thaddeus Woskowiak
2021-01-15 13:19 ` hiro
2021-01-15 15:39 ` Thaddeus Woskowiak
2021-01-15 15:35 ` Stanley Lieber
2021-01-15 11:33 ` Sigrid Solveig Haflínudóttir
2021-01-15 13:37 ` Juan Cuzmar
2021-01-15 16:13 ` rgl
2021-01-15 15:38 ` Calvin Morrison
2021-01-15 18:33 ` Stuart Morrow
2021-01-15 19:25 ` William Gunnells
2021-01-15 20:18 ` hiro [this message]
2021-01-16 0:41 ` qwx
2021-01-16 2:50 ` sl
2021-01-15 20:41 ` [9front] " Anthony Martin
2021-01-15 22:18 ` William Gunnells
2021-01-15 22:45 ` Sigrid Solveig Haflínudóttir
2021-01-16 2:49 ` sl
2021-01-15 22:57 ` Eli Cohen
2021-01-16 2:42 ` sl
2021-01-17 1:06 ` Anthony Martin
2021-01-17 13:23 ` hiro
2021-01-17 19:11 ` Eckard Brauer
2021-01-17 22:00 ` hiro
2021-01-18 9:24 ` Eckard Brauer
2021-01-18 10:36 ` Rodrigo G. López
2021-01-18 10:56 ` hiro
2021-01-18 12:57 ` Eckard Brauer
2021-01-18 2:57 ` sl
2021-01-16 10:05 ` [9front] " Kemal
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='CAFSF3XMnQQv1TQdUXgMh4o2CqM=HLjLbpkDXx2g9LtJun6X2=Q@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).