public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: jason@cygnus.com (Jason Merrill)
Cc: robertl@dgii.com, egcs@cygnus.com, law@cygnus.com
Subject: Re: egcs-1.1.1 issues
Date: Tue, 22 Sep 1998 11:27:00 -0000	[thread overview]
Message-ID: <199809221621.JAA06218@atrus.synopsys.com> (raw)
In-Reply-To: <u9ww6wx2uf.fsf@yorick.cygnus.com>

[ fast fixincludes ]
Jason writes:
> My inclination would be to just turn it on now.  There's no need to handle
> this so delicately, if it's expected to work.

Yes, the only way you get bugs out is to have people bang on it.  Why
not just make it the default in the next snapshot?  Then tell people to
try it, and if it fails, mail in a report of what went wrong and then
rebuild with it turned off to find other bugs.



  reply	other threads:[~1998-09-22 11:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-15 23:51 Jeffrey A Law
1998-09-16  9:44 ` Bruce Korb
1998-09-16 22:55   ` Jeffrey A Law
1998-09-17  9:59     ` Theodore Papadopoulo
1998-09-17 18:37       ` Jeffrey A Law
1998-09-21  7:32     ` Bruce Korb
1998-09-21 14:55       ` Robert Lipe
1998-09-21 19:37         ` Bruce Korb
1998-09-21 22:52         ` Jeffrey A Law
     [not found]     ` <19980921132907.J27681.cygnus.egcs@dgii.com>
1998-09-21 20:14       ` Jason Merrill
1998-09-22 11:27         ` Joe Buck [this message]
1998-09-27 16:28           ` Jeffrey A Law
1998-09-16 21:52 ` egcs-1.1.1 issues; Fortran Toon Moene
1998-09-17 11:42   ` Craig Burley
1998-09-18  6:59     ` Dave Love
1998-10-02  1:40   ` Jeffrey A Law
1998-10-02 17:44     ` David Edelsohn
1998-10-08  6:14     ` Dave Love
1998-10-09 10:40       ` Craig Burley
1998-09-16 21:52 ` egcs-1.1.1 issues Laurent Bonnaud
1998-09-17  9:59 ` Gary Thomas
1998-09-17 13:55 ` Gerald Pfeifer
     [not found] <8560.909819597@hurl.cygnus.com>
1998-10-31  9:57 ` H.J. Lu

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=199809221621.JAA06218@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=egcs@cygnus.com \
    --cc=jason@cygnus.com \
    --cc=law@cygnus.com \
    --cc=robertl@dgii.com \
    /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).