From: Chet Ramey <chet.ramey@case.edu>
To: Joseph Holsten <joseph@josephholsten.com>,
Steve Nickolas <usotsuki@buric.co>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Early BSD license thread
Date: Wed, 21 Sep 2022 19:53:32 -0400 [thread overview]
Message-ID: <0c826dab-52c9-493b-724c-981676926093@case.edu> (raw)
In-Reply-To: <AD97AF1B-D57C-47B5-A085-DB08EFC7B9C6@josephholsten.com>
On 9/21/22 6:44 PM, Joseph Holsten wrote:
> I’ve thought of this example many times when the 9fans minimalists talk
> about empty-file `true` impls.
>
> Which of course would lead to the 3.8k reported issues of
> https://github.com/kelseyhightower/nocode
> <https://github.com/kelseyhightower/nocode>
My favorites are the ones that ask to add a scripting language to the
project.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2022-09-21 23:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 10:10 [TUHS] " Warner Losh
2022-09-21 12:36 ` [TUHS] " Rob Pike
2022-09-21 13:33 ` Marc Donner
2022-09-21 13:46 ` Warner Losh
2022-09-21 14:50 ` Rich Salz
2022-09-21 14:58 ` Warner Losh
2022-09-21 15:06 ` Miod Vallat
2022-09-21 14:57 ` [TUHS] Fwd: " Clem Cole
2022-09-21 15:09 ` [TUHS] " Larry McVoy
2022-09-21 15:25 ` Warner Losh
2022-09-21 22:06 ` [TUHS] " Bakul Shah
2022-09-21 22:20 ` Warner Losh
2022-09-21 21:14 ` [TUHS] Re: Fwd: " Theodore Ts'o
2022-09-21 21:46 ` Clem Cole
2022-09-21 21:49 ` [TUHS] " Phil Budne
2022-09-21 22:07 ` Rich Salz
2022-09-21 22:24 ` Warner Losh
2022-09-21 22:09 ` Dan Cross
2022-09-21 22:19 ` Steve Nickolas
2022-09-21 22:44 ` Joseph Holsten
2022-09-21 23:53 ` Chet Ramey [this message]
2022-09-22 0:32 ` Rob Pike
2022-09-22 7:08 ` [TUHS] " Andy Kosela
2022-09-22 17:44 ` [TUHS] " Dan Cross
2022-09-22 18:44 ` Bakul Shah
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=0c826dab-52c9-493b-724c-981676926093@case.edu \
--to=chet.ramey@case.edu \
--cc=joseph@josephholsten.com \
--cc=tuhs@tuhs.org \
--cc=usotsuki@buric.co \
/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).