From: meillo@marmaro.de (markus schnalke)
Subject: [TUHS] Questions about the history of cut(1)
Date: Mon, 18 May 2015 16:04:38 +0200 [thread overview]
Message-ID: <1YuLeo-1Qx-00@marmaro.de> (raw)
In-Reply-To: <201505181036.t4IAagZS031943@coolidge.cs.dartmouth.edu>
[2015-05-18 06:36] Doug McIlroy <doug at cs.dartmouth.edu>
>
> I believe cut/paste originated in PWB Unix, but I can't recall who
> wrote it.
Thanks for your reply.
I checked the PWB code of bostic and spencer ...
http://minnie.tuhs.org/Archive/PDP-11/Distributions/usdl/
http://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1
... but couldn't find any signs of cut or paste there.
meillo
next prev parent reply other threads:[~2015-05-18 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 10:36 Doug McIlroy
2015-05-18 11:49 ` John Cowan
2015-05-18 14:04 ` markus schnalke [this message]
2015-05-18 15:01 ` Andy Kosela
2015-05-18 15:20 ` Clem Cole
2015-05-18 15:06 ` Clem Cole
2015-05-31 18:06 ` markus schnalke
2015-05-31 22:18 ` Mary Ann Horton
2015-06-01 14:14 ` Clem Cole
2015-06-02 17:31 ` markus schnalke
2015-05-18 15:13 ` random832
-- strict thread matches above, loose matches on Subject: below --
2015-05-17 18:00 markus schnalke
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=1YuLeo-1Qx-00@marmaro.de \
--to=meillo@marmaro.de \
/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).