From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30037 invoked by alias); 23 Nov 2012 21:08:42 -0000 Received: (qmail 30029 invoked by uid 22791); 23 Nov 2012 21:08:41 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from virtual.bogons.net (HELO virtual.bogons.net) (193.178.223.136) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Nov 2012 21:08:35 +0000 Received: from jifvik.dyndns.org (jifvik.dyndns.org [85.158.45.40]) by virtual.bogons.net (8.10.2+Sun/8.11.2) with ESMTP id qANL8YE23597; Fri, 23 Nov 2012 21:08:34 GMT Received: from shurg.barn.ecoscentric.com (unknown [87.127.120.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jifvik.dyndns.org (Postfix) with ESMTP id 494D13FE1; Fri, 23 Nov 2012 21:08:33 +0000 (GMT) Message-ID: <50AFE5D0.6090205@jifvik.org> Date: Fri, 23 Nov 2012 21:19:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Lightning/1.0b3pre Thunderbird/3.1.16 MIME-Version: 1.0 To: Diego Novillo Cc: overseers@gcc.gnu.org Subject: Re: Could we start accepting rich-text postings on the gcc lists? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2012-q4/txt/msg00078.txt.bz2 On 23/11/12 19:53, Diego Novillo wrote: > In this day and age of rich-text capable mailers, restricting postings > to be text-only seems quaint and antiquated. Are there any hard > requirements that force us to only accept plain text messages? IMHO, there are some good reasons not to allow them now, some technical, some more political. There was a thread on this back in March too. Here were some of my responses, for what it's worth: http://sourceware.org/ml/overseers/2012-q1/msg00070.html http://sourceware.org/ml/overseers/2012-q1/msg00088.html Some of those could be resolved after the hardware upgrade (although I don't know the current status on that), where the current proposal involves a switch to Mailman. But that wouldn't solve all the issues. Maybe something can be done to deal with these, but it may be that that would involve so many compromises that keeping things as plain text only might still be "least worst". Jifl -- --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine