The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: itz@very.loosely.org (Ian Zimmerman)
Subject: Running V8 ... [ really basic tools ]
Date: Mon, 16 Oct 2017 18:15:54 -0700	[thread overview]
Message-ID: <20171017011554.76ffxpcotcxlxeeo@matica.foolinux.mooo.com> (raw)
In-Reply-To: <201710161928.v9GJSB8Y028111@darkstar.fourwinds.com>

On 2017-10-16 12:28, Jon Steinhart wrote:

> I didn't prohibit people from creating their own tools and shortcuts.
> I prevented them from using existing utility names for their tools and
> shortcuts.  That meant that when they asked someone else in the group
> to take a look at a problem that that person could actually do so
> instead of causing damage.

I see - I have misunderstood you.  No problem with this policy.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
Do obvious transformation on domain to reply privately _only_ on Usenet.


  reply	other threads:[~2017-10-17  1:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 11:58 [TUHS} Running V8 Doug McIlroy
2017-10-16 15:41 ` Don Hopkins
2017-10-17 11:47   ` Tony Finch
2017-10-17 14:30     ` Larry McVoy
2017-10-17 14:50     ` Don Hopkins
2017-10-16 16:28 ` Clem Cole
2017-10-16 16:39   ` [TUHS} Running V8 ... [ really basic tools ] Jon Steinhart
2017-10-16 19:16     ` Ian Zimmerman
2017-10-16 19:28       ` Jon Steinhart
2017-10-17  1:15         ` Ian Zimmerman [this message]
2017-10-17  4:20           ` UNIX version 2*pi Don Hopkins
2017-10-17  6:08             ` Dave Horsfall
2017-10-17 18:23               ` Ron Natalie
2017-10-18  2:46                 ` Dave Horsfall
2017-10-18 10:15                   ` Ron Natalie
2017-10-16 16:38 ` [TUHS} Running V8 Will Senn

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=20171017011554.76ffxpcotcxlxeeo@matica.foolinux.mooo.com \
    --to=itz@very.loosely.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).