public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Robert Dewar <dewar@gnat.com>
Cc: Zack Weinberg <zack@codesourcery.com>,
	Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
	gcc@gcc.gnu.org
Subject: Re: Reenabling Ada by default
Date: Thu, 09 Sep 2004 22:10:00 -0000	[thread overview]
Message-ID: <m3pt4vqeue.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <4140AC5F.4020608@gnat.com>

Robert Dewar <dewar@gnat.com> writes:

[...]

| The internal review process very often involves proprietary customer
| information, so generally this kind of opening up is not possible.
| Remember that the great majority of bugs that are being fixed by
| AdaCore are from customers with proprietary code.

This is a very slippery slope for the GCC project.  Imagine all GCC
developers start checking things in, with non public review process, on
the basis that that would involves proprietary customers nd
proprietary codes!  

Form experience and the cases I know of, huge efforts are made to
identify freely accessible data that could be the base of patch
reviews or testcases or benchmarcks.  After that, the rest of the
review process is made public on GCC list.

-- Gaby

  parent reply	other threads:[~2004-09-09 22:06 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 19:01 Richard Kenner
2004-09-09 19:17 ` Zack Weinberg
2004-09-09 19:22   ` Robert Dewar
2004-09-09 19:40     ` Zack Weinberg
2004-09-09 19:41       ` Robert Dewar
2004-09-09 19:56     ` Diego Novillo
2004-09-09 20:04     ` Andrew Haley
2004-09-09 22:10     ` Gabriel Dos Reis [this message]
2004-09-09 19:40 ` Kaveh R. Ghazi
2004-09-09 20:37 Richard Kenner
2004-09-09 20:56 ` Robert Dewar
2004-09-09 20:57   ` Florian Weimer
2004-09-09 21:04     ` Robert Dewar
2004-09-12  2:46     ` Per Bothner
2004-09-12 12:29       ` Andrew Haley
2004-09-12 14:15       ` Florian Weimer
2004-09-12 14:41         ` Robert Dewar
2004-09-12 17:48         ` Tom Tromey
2004-09-12 23:39         ` Per Bothner
2004-09-09 21:19   ` Eric Christopher
2004-09-09 21:45     ` Robert Dewar
2004-09-09 22:25       ` Gabriel Dos Reis
2004-09-10  0:29       ` Giovanni Bajo
2004-09-09 21:26 ` Duncan Sands
2004-09-09 21:57   ` Robert Dewar
2004-09-10  3:50     ` Kaveh R. Ghazi
2004-09-09 22:50 ` James A. Morrison
2004-09-09 22:54   ` Joseph S. Myers
2004-09-09 23:08   ` Robert Dewar
2004-09-09 23:29     ` Daniel Jacobowitz
2004-09-10 16:17     ` James A. Morrison
2004-09-09 23:07 ` Richard Henderson
2004-09-09 23:23 ` Kaveh R. Ghazi
2004-09-09 21:36 Richard Kenner
2004-09-09 22:06 ` Duncan Sands
2004-09-09 22:12 Wolfgang Bangerth
2004-09-09 22:17 Richard Kenner
2004-09-10  1:52 Richard Kenner
2004-09-10  2:18 ` Paul Brook
2004-09-10  5:08 ` Richard Henderson
2004-09-10  2:18 Richard Kenner
2004-09-10  5:19 ` Phil Edwards
2004-09-10  3:12 Richard Kenner
2004-09-10  4:38 Richard Kenner
2004-09-10  4:55 ` Kaveh R. Ghazi
2004-09-10  5:39 Richard Kenner
2004-09-10  6:14 ` Phil Edwards
2004-09-10 11:58 Richard Kenner
2004-09-10 14:11 ` Gabriel Dos Reis
2004-09-10 17:55 Richard Kenner
2004-09-10 22:07 ` Phil Edwards

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=m3pt4vqeue.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --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).