From: Federico Benavento <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] smtp
Date: Wed, 18 May 2005 23:00:42 +0200 [thread overview]
Message-ID: <32d987d50505181400391126da@mail.gmail.com> (raw)
In-Reply-To: <32d987d505051813411bb262ef@mail.gmail.com>
> cat $home/lib/keys > /mnt/factotum/ctl
sorry, /mnt/factotum/ctl doesn´t support multiline writes.
what I have is a keys file with a bounch of echos.
--
Federico G. Benavento
next prev parent reply other threads:[~2005-05-18 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 1:47 Tim Newsham
2005-05-18 20:41 ` Federico Benavento
2005-05-18 20:56 ` andrey mirtchovski
2005-05-18 21:00 ` Federico Benavento [this message]
[not found] ` <0214c6640e3a44a97749a6198441a136@plan9.ucalgary.ca>
2005-05-18 21:51 ` Federico Benavento
-- strict thread matches above, loose matches on Subject: below --
2000-12-19 9:17 Russ Cox
2000-12-19 10:36 ` William Staniewicz
2000-12-19 5:23 anothy
2000-12-19 8:58 ` William Staniewicz
2000-12-18 17:53 William Staniewicz
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=32d987d50505181400391126da@mail.gmail.com \
--to=benavento@gmail.com \
--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).