From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] duplicate code segments
Date: Fri, 27 Apr 2001 07:55:26 +0100 [thread overview]
Message-ID: <20010427065824.DA996199C1@mail.cse.psu.edu> (raw)
dup(1) doesn't seem to have been included in the distribution, though it's in the index, but
i ported Dick Grune's `sim' program ages ago, and it might be
as useful.
it must be old:
..!mcvax!vu44!dick
dick@vu44.UUCP
they don't make addresses like that anymore. good old pathalias; i'd forgotten all about that.
anyway, it's on my web page http://www.caldo.demon.co.uk/plan9/soft/
next reply other threads:[~2001-04-27 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-27 6:55 forsyth [this message]
2001-04-27 13:48 ` Boyd Roberts
2001-04-27 16:33 ` Latchesar Ionkov
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=20010427065824.DA996199C1@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.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).