From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 2 Aug 2001 01:50:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 2 Aug 2001 01:50:12 -0400 Received: from front1.mail.megapathdsl.net ([66.80.60.31]:20242 "EHLO front1.mail.megapathdsl.net") by vger.kernel.org with ESMTP id ; Thu, 2 Aug 2001 01:49:53 -0400 Subject: Re: OT: Virii on vger.kernel.org lists From: Miles Lane To: "Paul G. Allen" Cc: Linux Kernel In-Reply-To: <3B68E74B.E4A9E481@randomlogic.com> In-Reply-To: <20010801235724.A23000@werewolf.able.es> <3B68E74B.E4A9E481@randomlogic.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12.99 (Preview Release) Date: 01 Aug 2001 22:44:49 -0700 Message-Id: <996731092.25247.4.camel@stomata.megapathdsl.net> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 01 Aug 2001 22:38:19 -0700, Paul G. Allen wrote: > "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? One interface that provides an easy mechanism for posting attachments is Bugzilla. See http://bugzilla.gnome.org. If you open a bug report, you can add file attachments after initially creating the bug. Something similar might work very well for the LKML needs. All that is really required is a web server, some Bugzilla-like method of pointing to a file and having that get posted to the web server. Then, a unique link to the posted file can be returned that the user can then send along to LKML. Miles