From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-74999-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 23007 invoked by alias); 24 May 2003 02:24:39 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 22811 invoked from network); 24 May 2003 02:24:31 -0000
Received: from unknown (HELO crack.them.org) (146.82.138.56)
  by sources.redhat.com with SMTP; 24 May 2003 02:24:31 -0000
Received: from nevyn.them.org ([66.93.61.169] ident=mail)
	by crack.them.org with asmtp (Exim 3.12 #1 (Debian))
	id 19JOi2-0005Tm-00; Fri, 23 May 2003 21:24:34 -0500
Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian))
	id 19JOhQ-0001wP-00; Fri, 23 May 2003 22:23:56 -0400
Date: Sat, 24 May 2003 02:56:00 -0000
From: Daniel Jacobowitz <drow@mvista.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Segher Boessenkool <segher@koffie.nl>, gcc <gcc@gcc.gnu.org>
Subject: Re: A few suggestions for bugzilla mail to gcc-bugs
Message-ID: <20030524022356.GA7386@nevyn.them.org>
Mail-Followup-To: Daniel Berlin <dberlin@dberlin.org>,
	Segher Boessenkool <segher@koffie.nl>, gcc <gcc@gcc.gnu.org>
References: <3ECEBD9C.2020303@koffie.nl> <Pine.LNX.4.53.0305232201400.22503@dberlin.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.53.0305232201400.22503@dberlin.org>
User-Agent: Mutt/1.5.1i
X-SW-Source: 2003-05/txt/msg02170.txt.bz2

On Fri, May 23, 2003 at 10:02:36PM -0400, Daniel Berlin wrote:
> 
> 
> On Sat, 24 May 2003, Segher Boessenkool wrote:
> 
> > Hi,
> >
> > A few suggestions for the mail to gcc-bugs, taking this recent
> > message as an example:
> >
> >  > PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
> >
> > Can't this be automated?
> Actually, it can't, AFAIK.

Well, there's already a Reply-To: header set...

> >  > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10942
> >
> > Maybe show the short URL here?
> Sure, i guess.
> 
> 
> >
> >  > ------- Additional Comments From edmar@motorola.com  2003-05-22 17:30 -------
> >  > Created an attachment (id=4054)
> >  >  --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=4054&action=view)
> >  > Preprocessed file that caused the ICE
> >
> > Although I really like not getting any useless 500kB+ emails
> > through gcc-bugs anymore, if an attachment is short, can it
> > be sent in the actual email please?
> 
> Define short.

Let's just pick a reasonable limit - how about 20K?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer