From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] Re: TeX
Date: Mon, 19 Feb 2018 18:26:32 -0500 [thread overview]
Message-ID: <A6A42E873DD72DF57CAA35CDA84F3F34@5ess.inri.net> (raw)
In-Reply-To: 837D5033-E0B2-4331-B9F7-4F7862FA8D74@quintile.net
> do i need some form of entitlement to think?
This has been debated in academia for decades. To some extent,
privilege is the time and space to think.
sl
next reply other threads:[~2018-02-19 23:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 23:26 sl [this message]
2018-02-20 9:04 ` Julius Schmidt
2018-02-20 13:22 ` Ethan Grammatikidis
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 2:23 sl
2018-02-14 1:59 TeX Lyndon Nerenberg
2018-02-14 9:15 ` [9front] TeX Steve Simon
2018-02-18 6:55 ` Matthew Veety
2018-02-18 12:04 ` Steve Simon
2018-02-18 19:56 ` Sean Hinchee
2018-02-19 4:32 ` Matthew Veety
2018-02-18 14:12 ` hiro
2018-02-18 17:18 ` Steve Simon
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=A6A42E873DD72DF57CAA35CDA84F3F34@5ess.inri.net \
--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).