From: Joe Buck <Joe.Buck@synopsys.COM>
To: Tom Tromey <tromey@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>,
Mark Mitchell <mark@codesourcery.com>,
Alex Perez <aperez@student.santarosa.edu>,
gcc@gcc.gnu.org, Zack Weinberg <zack@codesourcery.com>
Subject: Re: Objective-C bugs and GCC releases
Date: Tue, 25 Jan 2005 20:07:00 -0000 [thread overview]
Message-ID: <20050125194554.GA20230@synopsys.com> (raw)
In-Reply-To: <m33bwpz4ld.fsf@localhost.localdomain>
On Tue, Jan 25, 2005 at 12:33:18PM -0700, Tom Tromey wrote:
> One potential problem I see with the current approach is that a
> non-release-critical language can be screwed by changes outside its
> purview. For gcj we've occasionally had bugs (cf PR 19505) which
> occur in the gcc core. In theory, something like this could be
> introduced the day before a release, and we'd end up shipping a broken
> gcj. No amount of manpower can solve this.
We are not robots here; I know that Mark will use good judgment even if
not required to do so by what we have written down. Should something like
that arise (a change goes in the last day that breaks Java, say), Mark can
still hold things up until the change is backed out or repaired. However,
that can only happen if such things are caught quickly.
next prev parent reply other threads:[~2005-01-25 19:45 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 23:08 Gregory John Casamento
2005-01-24 23:09 ` Daniel Berlin
2005-01-24 23:43 ` Dale Johannesen
2005-01-25 0:10 ` Richard Henderson
2005-01-25 2:15 ` Mark Mitchell
2005-01-25 2:56 ` Alex Perez
2005-01-25 3:24 ` Daniel Berlin
2005-01-25 3:26 ` Daniel Berlin
2005-01-25 4:19 ` Zack Weinberg
2005-01-25 7:01 ` Mark Mitchell
2005-01-25 7:32 ` make header flag Lucaz _
2005-01-26 20:08 ` James E Wilson
2005-01-25 14:47 ` Objective-C bugs and GCC releases Adrian Robert
2005-01-25 15:04 ` Robert Dewar
2005-01-25 15:36 ` Adrian Robert
2005-01-25 15:41 ` Robert Dewar
2005-01-25 16:05 ` Richard Earnshaw
2005-01-25 16:36 ` Helge Hess
2005-01-25 17:02 ` Steven Bosscher
[not found] ` <0A7059BA-6EF8-11D9-ACCF-000D93C1A604@opengroupware.org>
2005-01-25 18:02 ` Steven Bosscher
2005-01-25 18:18 ` Helge Hess
2005-01-25 18:30 ` Joe Buck
2005-01-26 1:32 ` Nicola Pero
2005-01-26 1:38 ` Steven Bosscher
2005-01-26 1:54 ` Nicola Pero
2005-01-26 2:34 ` Gabriel Dos Reis
2005-01-26 2:38 ` Mike Stump
2005-01-26 6:47 ` Nicola Pero
2005-01-26 3:28 ` Mark Mitchell
2005-01-26 8:44 ` Daniel Berlin
2005-01-25 19:19 ` Daniel Berlin
2005-01-25 19:15 ` Daniel Berlin
2005-01-25 20:04 ` Anthony Juckel
2005-01-26 0:29 ` Mike Stump
2005-01-25 15:16 ` Mark Mitchell
2005-01-25 16:02 ` Adrian Robert
2005-01-25 16:18 ` Daniel Jacobowitz
2005-01-25 16:24 ` Andrew Pinski
2005-01-25 20:00 ` Tom Tromey
2005-01-25 20:07 ` Joe Buck [this message]
2005-01-25 20:42 ` Tom Tromey
2005-01-25 17:59 ` Joe Buck
2005-01-25 15:35 ` Gabriel Dos Reis
2005-01-25 19:05 ` Stefan Strasser
2005-01-25 17:54 ` Joe Buck
2005-01-25 19:11 ` Daniel Berlin
2005-01-25 17:24 ` Joe Buck
2005-01-25 14:22 ` Patrick McFarland
2005-01-25 15:12 ` Mark Mitchell
2005-01-25 23:33 ` Patrick McFarland
2005-01-25 23:40 ` Joe Buck
2005-01-26 0:06 ` Steven Bosscher
[not found] <41F6D6EB.20801@adacore.com>
2005-01-26 1:17 ` Gregory John Casamento
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=20050125194554.GA20230@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=aperez@student.santarosa.edu \
--cc=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=tromey@redhat.com \
--cc=zack@codesourcery.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).