From: haahr@mv.us.adobe.com (Paul Haahr)
To: richard@harlequin.co.uk
Cc: es@hawkwind.utcs.toronto.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: May I suggest we digestify the rc and es lists?
Date: Wed, 19 May 1993 12:22:10 -0400 [thread overview]
Message-ID: <9305191622.AA22903@astro.mv.us.adobe.com> (raw)
as an implementor of one of the two languages (the one that is
evolving more these days) having several rounds of correspondence
a day is very useful to me. i would hate to see the latency
increased that much.
perhaps, if someone volunteered to do it, there could be digestified
versions of the lists and people could decide to subscribe either the
digestified or normal (undigestified) version.
i'd also like, by the way, to thank Chris for maintaining the lists
as well as the es distribution. they are the only things about es
that haven't given me trouble.
paul
next reply other threads:[~1993-05-19 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-19 16:22 Paul Haahr [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-05-19 16:54 Jeff Bone x223
1993-05-19 9:21 Richard Brooksby
1993-05-19 16:20 ` Chris Siebenmann
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=9305191622.AA22903@astro.mv.us.adobe.com \
--to=haahr@mv.us.adobe.com \
--cc=es@hawkwind.utcs.toronto.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=richard@harlequin.co.uk \
/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).