From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] awk
Date: Mon, 11 Jun 2001 14:27:56 +0200 [thread overview]
Message-ID: <0ba901c0f271$f1f1dd40$e8b7c6d4@SOMA> (raw)
In-Reply-To: <200106111013.MAA14426@boris.cd.chalmers.se>
i even persuaded it to 'parse' mime as one company's 'rat squad'
[les boeuf-carrotes] had to round up the odd scapegoat [tête de
turc].
next prev parent reply other threads:[~2001-06-11 12:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 10:13 Laura Creighton
2001-06-11 12:27 ` Boyd Roberts [this message]
2001-06-18 9:12 ` Rick O'shay
-- strict thread matches above, loose matches on Subject: below --
2003-09-13 0:40 boyd
2002-11-07 9:56 okamoto
2002-11-07 6:46 Kenji Arisawa
2002-11-20 14:49 ` Kenji Arisawa
2000-03-14 10:06 Arnold
2000-03-13 6:25 Bengt
2000-03-13 1:21 Vladimir
2000-03-12 23:29 bobf
2000-03-12 22:50 Scott
2000-03-12 21:50 Vladimir
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='0ba901c0f271$f1f1dd40$e8b7c6d4@SOMA' \
--to=boyd@fr.inter.net \
--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).