From: "Paul G. Allen" <pgallen@randomlogic.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: OT: Virii on vger.kernel.org lists
Date: Wed, 01 Aug 2001 22:38:19 -0700 [thread overview]
Message-ID: <3B68E74B.E4A9E481@randomlogic.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108011406320.15992-100000@sol.compendium-tech.com> <Pine.GSO.4.21.0108011713080.27494-100000@weyl.math.psu.edu> <20010801235724.A23000@werewolf.able.es>
"J . A . Magallon" wrote:
>
[SNIP]
>
> That is the always repeated answer. I could get a web page at some box at the
> University, but there are many people that have not a permanent address. Going
> to the mess of using a ISP-provided web page is a pain. Instead of bzip your
> patch and send it to the list you have to go through bizarre http interfaces
> to manage your web page (tell me about a ISP that lets you telnet/ssh/ftp to your
> account).
>
> I do not see why a bzipped patch is so bad. The only person I was aware he won't
> read anything but plain text is Linus (and now some on this thread look with
> the same feeling).
>
There are a few reasons why zipped attachments, large attachments, and
even large text-only patches are bad on a mailing list such as this:
1. Not everyone uses a mail client that will support the various
attachment encodings and therefore can not get the attachment without
jumping through hoops. Why subject them to this?
2. Some mail clients pervert the standard attachment formats, such as
Outlook Express, making them undecipherable by anyone using anything
other than that very same client. Again, why subject people to that?
3. Many, many people PAY PER BYTE for their Internet connection. Adding
a large attachment, or sending a large text patch file, costs them
money. Many times they do not want it anyway and you are costing them
money by forcing them to D/L it.
4. Not everyone has a high speed connection and with the volume that a
list like this creates, it is a LARGE burden on them to wait, and wait,
and wait, for the few messages they want, and/or need, to see.
So, as with other large projects I've worked on (though none quite this
large) involving a mailing list, the best solution is to a) strip
attachments atthe mailing list server and b) provide a repository for
people to D/L patches, new kernels, etc. for public access.
PGA
--
Paul G. Allen
UNIX Admin II/Network Security
Akamai Technologies, Inc.
www.akamai.com
next prev parent reply other threads:[~2001-08-02 5:41 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-29 22:20 Test mail Mailing Server
2001-07-30 1:50 ` Test mail :: DO NOT FSKING OPEN THE ATTACHMENT God
2001-07-30 3:24 ` Michael Rothwell
2001-07-30 15:45 ` Jim Potter
2001-07-30 1:53 ` Test mail Anton Altaparmakov
2001-07-30 4:02 ` Rik van Riel
2001-07-30 6:09 ` Paul G. Allen
2001-07-30 6:28 ` Paul G. Allen
2001-07-30 7:10 ` Lew Wolfgang
2001-07-30 8:41 ` Paul G. Allen
2001-07-31 23:08 ` Dr. Kelsey Hudson
2001-07-30 9:45 ` Chris Crowther
2001-07-30 6:29 ` Alexander V. Bilichenko
2001-07-30 11:07 ` Paul Mundt
2001-07-30 11:45 ` john slee
2001-07-30 11:46 ` Alan Cox
2001-07-30 12:07 ` Paul Mundt
2001-07-30 12:15 ` Alan Cox
2001-07-30 12:23 ` Paul Mundt
2001-07-30 12:51 ` Alan Cox
2001-07-30 7:28 ` Riley Williams
2001-07-30 16:17 ` christophe barbé
2001-07-30 16:32 ` Ignacio Vazquez-Abrams
2001-07-30 17:22 ` Albert D. Cahalan
2001-07-30 17:38 ` Ignacio Vazquez-Abrams
2001-07-30 18:20 ` Justin Guyett
2001-07-30 21:14 ` Horst von Brand
2001-07-31 7:27 ` Ragnar Hojland Espinosa
[not found] ` <9k48ju$94b$1@ns1.clouddancer.com>
2001-07-30 19:21 ` Colonel
2001-07-30 17:56 ` Jim Potter
2001-07-30 18:00 ` Mike Galbraith
2001-08-01 0:18 ` Dr. Kelsey Hudson
2001-08-01 11:56 ` szonyi calin
2001-07-30 17:25 ` Jakob Østergaard
2001-07-31 12:27 ` Matti Aarnio
2001-07-31 18:02 ` Virii on vger.kernel.org lists Riley Williams
2001-07-31 18:12 ` OT: " Craig Milo Rogers
2001-07-31 19:12 ` William Scott Lockwood III
2001-07-31 21:30 ` OT: " Paul G. Allen
2001-07-31 22:17 ` Riley Williams
2001-07-31 22:31 ` Thomas Duffy
2001-07-31 22:47 ` Alan Shutko
2001-07-31 22:33 ` Craig Milo Rogers
2001-07-31 23:06 ` Riley Williams
2001-08-02 15:27 ` Alan Cox
2001-08-01 21:07 ` Dr. Kelsey Hudson
2001-08-01 21:15 ` Alexander Viro
2001-08-01 21:57 ` J . A . Magallon
2001-08-02 5:38 ` Paul G. Allen [this message]
2001-08-02 5:44 ` Miles Lane
2001-08-02 13:49 ` john slee
2001-08-02 0:27 ` Alan Cox
2001-08-01 21:20 ` Justin Guyett
2001-08-02 1:57 ` Paul G. Allen
2001-08-07 15:07 ` Dick Streefland
2001-07-31 19:01 ` Kent Borg
2001-07-31 19:18 ` William Scott Lockwood III
2001-07-31 21:27 ` Ian Stirling
2001-07-31 21:50 ` William Scott Lockwood III
2001-07-31 22:49 ` Alan Olsen
2001-07-31 22:41 ` Riley Williams
2001-07-31 22:54 ` [OT] " William Scott Lockwood III
2001-07-31 23:19 ` Riley Williams
2001-07-31 23:31 ` William Scott Lockwood III
2001-07-31 23:30 ` Riley Williams
2001-07-31 23:51 ` [OT] Virii (sic) Guest section DW
2001-08-01 4:03 ` PCMCIA IDE_CS in 2.4.7 Alan Olsen
2001-08-01 3:37 ` Keith Owens
2001-08-01 5:42 ` Alan Olsen
2001-08-02 14:18 ` Alan Cox
2001-08-02 19:07 ` Alan Olsen
2001-08-02 17:58 ` Alan Cox
2001-08-02 19:21 ` Alan Olsen
2001-08-02 20:48 ` Alan Olsen
2001-08-16 0:04 ` Paul Mackerras
2001-08-01 6:58 ` [OT] Virii (sic) Riley Williams
2001-08-01 8:13 ` [Ridiculously OT] " David Huen
2001-08-02 7:33 ` Riley Williams
2001-08-02 10:04 ` Manfred Bartz
2001-08-01 8:56 ` [OT] " Nadav Har'El
2001-08-01 9:13 ` Alessandro Suardi
2001-08-01 10:38 ` Wakko Warner
2001-08-01 10:44 ` Jean-Luc
2001-08-02 1:57 ` Johan Kullstam
2001-08-01 10:03 ` Vojtech Pavlik
2001-08-02 3:46 ` Rik van Riel
2001-07-31 22:00 ` Virii on vger.kernel.org lists Matti Aarnio
2001-07-31 22:16 ` William Scott Lockwood III
2001-08-01 10:49 ` Dominik Kubla
2001-08-01 11:04 ` Dominik Kubla
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=3B68E74B.E4A9E481@randomlogic.com \
--to=pgallen@randomlogic.com \
--cc=linux-kernel@vger.kernel.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