From: Richard Brooksby <richard@harlequin.co.uk>
To: rc@hawkwind.utcs.toronto.edu, es@hawkwind.utcs.toronto.edu
Subject: May I suggest we digestify the rc and es lists?
Date: Wed, 19 May 1993 05:21:29 -0400 [thread overview]
Message-ID: <20399.9305190921@morris.harlqn.co.uk> (raw)
Much as I enjoy corresponding about rc and es I am finding that my
mailbox, which is already overloaded, is becoming even more so. I am
even considering unsubscribing (to es at least) simply because I do
not have the time.
May I suggest that the rc and es lists are made into digests at the
distribution site? I would much prefer to receive a daily message
containing correspondence, even though it would slow down the reaction
time somewhat. (Actually, in my experience, slowing down the reaction
time often improves the content of a list.)
Is this technically feasible? Do others agree that this would be a
good thing?
Please consider this carefully. I beleive I have something to
contribute; it would be a shame if I didn't have the chance.
---
Richard Brooksby <richard@harlequin.co.uk>
ML Project / Symbolic Processing Division / Harlequin
+44 223 872522
next reply other threads:[~1993-05-19 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-19 9:21 Richard Brooksby [this message]
1993-05-19 16:20 ` Chris Siebenmann
1993-05-19 16:22 Paul Haahr
1993-05-19 16:54 Jeff Bone x223
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=20399.9305190921@morris.harlqn.co.uk \
--to=richard@harlequin.co.uk \
--cc=es@hawkwind.utcs.toronto.edu \
--cc=rc@hawkwind.utcs.toronto.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).