From: Daniel Simms <dsimms@alink.net>
Subject: missing etc?
Date: 11 Mar 1997 14:57:14 -0800 [thread overview]
Message-ID: <m3vi6yujed.fsf@yoyo.alink.net> (raw)
I think I must have overslept by weeks, I feel so lost. Or, maybe
etc-0.24 is just missing:
# ifi> get etc.tar.gz
# etc.tar.gz: No such file OR directory.
# > dir etc*
#
# -rw-r--r-- 1 larsi larsi 30656 Aug 10 1996 etc-0.20.tar.gz
# lrwxrwxrwx 1 larsi larsi 15 Sep 27 19:52 etc.tar.gz -> etc-0.24.tar.gz
# ifi>
--
Daniel Simms "A common mistake that people make when trying to design
dsimms@alink.net something completely foolproof [is] to underestimate the
(408) 720-6161 ingenuity of complete fools" -Ford Prefect
next reply other threads:[~1997-03-11 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-11 22:57 Daniel Simms [this message]
1997-03-12 5:15 ` Lars Magne Ingebrigtsen
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=m3vi6yujed.fsf@yoyo.alink.net \
--to=dsimms@alink.net \
/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).