From: stanley lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] rc: unix bits removed
Date: Wed, 18 May 2016 10:48:01 -0400 [thread overview]
Message-ID: <BA6925CB-1F89-4EC5-8D77-FB6D908A0323@stanleylieber.com> (raw)
In-Reply-To: <94636e3ee2c682498480e9333693a7b7@felloff.net>
>> It's likely I'm not qualified for the job in the first place.
>
> just DO IT.
Two problems:
1. I don't know what I'm doing
2. These days, I have less than zero time.
They've made it so we can't have personal computing devices or Internet at work AT ALL, and when I'm at home I'm completely occupied with family stuff.
Eventually, I will try to do it.
sl
next prev parent reply other threads:[~2016-05-18 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 1:31 stanley lieber
2016-05-17 1:55 ` [9front] " cinap_lenrek
2016-05-18 0:42 ` stanley lieber
2016-05-18 6:45 ` cinap_lenrek
2016-05-18 14:48 ` stanley lieber [this message]
2016-05-18 15:21 ` hiro
2016-05-18 15:34 ` cinap_lenrek
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=BA6925CB-1F89-4EC5-8D77-FB6D908A0323@stanleylieber.com \
--to=sl@stanleylieber.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).