From: Dave Wolfe <dwolfe@risc.sps.mot.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: List limits (was new irq.c)
Date: Fri, 15 Jan 1999 14:24:46 -0600 [thread overview]
Message-ID: <19990115142446.A13988@risc.sps.mot.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990115104436.9566I-100000@persephone.cs.nmt.edu>; from Cort Dougan on Fri, Jan 15, 1999 at 10:45:11AM -0700
[ Cort Dougan writes: ]
>
> Damn list won't let me send the file itself (too large)
Actually it's the damn listmaster. :-) But it's your (meaning all of
you) list and my policies are there to try to protect your mailboxes
from the list. Given the number of subscribers that complain to me that
they can't handle the volume of mail and the number of bounces from
mailboxes exceeding quotas, I believe some sort of message size limit is
desirable. Currently that limit is 40,000 bytes for the entire message.
Is that too small?
Message size really doesn't address the larger issue of mailing files
to a mail list. Do all the 1100 or so recipients of linuxppc-dev and
linuxppc-dev-digest *really* want to receive every file/mega-patch
potentially mailed to the list? Although all may want to know what's
going on (or they wouldn't be subscribed), I suspect very few are eager
to receive every file to build into their system, but every one of them
pays for those few to receive the files if they're mailed, nonetheless.
On the other hand, it's no stretch to claim that a development list
exists to help exchange experimental code and bug fixes, but can't that
be done more reliably by posting URLs where files can be retrieved via
ftp?
I administer these lists to try to contribute to something I feel is
important, so I'm open to (reasonable) suggestions. If you wish to
express an opinion, I encourage you to respond to me directly since this
has little to do with Linux development, but use your judgement if you
think your response merits discussion. Now where did I put my asbestos
underwear...?
--
Dave Wolfe
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
prev parent reply other threads:[~1999-01-15 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-15 12:49 anyone used kgdb lately? Frederick Heitkamp
1999-01-15 17:45 ` new irq.c Cort Dougan
1999-01-15 20:24 ` Dave Wolfe [this message]
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=19990115142446.A13988@risc.sps.mot.com \
--to=dwolfe@risc.sps.mot.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).