From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] another dusty upas question
Date: Fri, 2 May 2008 13:35:21 -0400 [thread overview]
Message-ID: <7fbfeef848768eb40e6dbf82a7713992@quanstro.net> (raw)
In-Reply-To: <20080502173332.7497C1E8C3A@holo.morphisms.net>
> ah, so the nedmail rf command invokes marshal -F.
> i would be inclined to change -F to take the name
> of the file, so that nedmail can be the sole arbiter of
> what goes where.
don't forget acme mail.
touching the poison upas is a thankless deal,
but at least one makes no progress. and the
scars are cool.
- erik
next prev parent reply other threads:[~2008-05-02 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 13:29 erik quanstrom
2008-05-02 14:05 ` Russ Cox
2008-05-02 14:10 ` erik quanstrom
2008-05-02 14:23 ` Russ Cox
2008-05-02 15:22 ` erik quanstrom
2008-05-02 16:45 ` Russ Cox
2008-05-02 16:59 ` erik quanstrom
2008-05-02 17:30 ` Russ Cox
2008-05-02 17:35 ` erik quanstrom [this message]
2008-05-02 17:47 ` Russ Cox
2008-05-02 19:31 ` erik quanstrom
2008-05-02 21:43 ` Russ Cox
2008-05-02 21:50 ` erik quanstrom
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=7fbfeef848768eb40e6dbf82a7713992@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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).