public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
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
Date: Sat, 24 May 2003 02:56:00 -0000	[thread overview]
Message-ID: <20030524022356.GA7386@nevyn.them.org> (raw)
In-Reply-To: <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

  reply	other threads:[~2003-05-24  2:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24  2:02 Segher Boessenkool
2003-05-24  2:14 ` Daniel Berlin
2003-05-24  2:56   ` Daniel Jacobowitz [this message]
2003-05-24  3:05     ` Daniel Berlin
2003-05-24  3:09       ` DJ Delorie
2003-05-24  3:57         ` Daniel Berlin
2003-05-24 15:15       ` Daniel Jacobowitz
2003-06-02 20:02         ` Andreas Schwab
2003-06-02 21:34           ` Daniel Berlin
2003-06-02 21:38             ` Daniel Jacobowitz
2003-06-02 21:54               ` Daniel Berlin
2003-06-02 22:03                 ` Daniel Jacobowitz
2003-05-24  3:42     ` Segher Boessenkool
2003-05-24  9:52   ` Joseph S. Myers
2003-05-24 15:46     ` Daniel Berlin
2003-05-24 20:17       ` Joseph S. Myers

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=20030524022356.GA7386@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=segher@koffie.nl \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).