This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A few suggestions for bugzilla mail to gcc-bugs
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Daniel Berlin <dberlin at dberlin dot org>
- Cc: Segher Boessenkool <segher at koffie dot nl>, gcc <gcc at gcc dot gnu dot org>
- Date: Fri, 23 May 2003 22:23:56 -0400
- Subject: Re: A few suggestions for bugzilla mail to gcc-bugs
- References: <3ECEBD9C.2020303@koffie.nl> <Pine.LNX.4.53.0305232201400.22503@dberlin.org>
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