From: Chris Siebenmann <cks>
To: rc
Subject: Re: Differences between Duff's rc and Byron's
Date: Wed, 26 May 1993 16:32:10 -0400 [thread overview]
Message-ID: <93May26.163314edt.2237@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: haahr's message of Wed, 26 May 93 13:58:36 -0400. <9305261758.AA03677@astro.mv.us.adobe.com>
(an addendum: it fails in a somewhat old version of Duff's rc. It may be
different in current ones; someone with access to a Plan 9 system will
have to be the one to check.)
- cks
next prev parent reply other threads:[~1993-05-26 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-26 17:58 Paul Haahr
1993-05-26 20:31 ` Chris Siebenmann
1993-05-26 20:32 ` Chris Siebenmann [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-05-27 6:48 Paul Haahr
1993-05-27 5:02 Alan Watson
1993-05-26 17:38 Tom Culliton x2278
1993-05-26 17:06 Paul Haahr
1993-05-26 16:53 Paul Haahr
1993-05-26 17:55 ` Chris Siebenmann
1993-05-29 12:34 ` John Mackin
1993-05-25 23:32 Alan Watson
1993-05-25 22:42 Tom Culliton x2278
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=93May26.163314edt.2237@hawkwind.utcs.toronto.edu \
--to=rc@hawkwind.utcs.toronto.edu \
/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).