public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: rth@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: Reenabling Ada by default
Date: Fri, 10 Sep 2004 01:52:00 -0000	[thread overview]
Message-ID: <10409100119.AA16565@vlsi1.ultra.nyu.edu> (raw)

    The internet is a large enough place that I expect at least copies
    of gcc and its mail archives to exist until the global apocalypse.
    I do not expect the same to be true for any given corporation.

Sure, but I don't understand what data you are talking about losing.
There are three potential types of data:

(1) patches
(2) test cases
(3) discussions of patches

Patches are available via either CVS or the gcc-patches list whether they
are batched or not.

We've spoken about test cases before.

#3 is the trickier one.  But what's important to realize is that for the vast
majority of patches, there's no data of that kind anywhere.  Most of the
patches you do are in the same category: the only "discussion" is within your
own skull.

For the small fraction where that's not the case, there is usually an
additional difficulty in publicizing that discussion that hasn't been
addressed here yet and it's not just a resource issue.

A discussion of a bug will, by its nature, refer to the customer test case,
which cannot be made public.  Sure, it's possible to "sanitize" that test
case, but usually not until the bug has been understood, which is *after*
those discussions.  Even when it can be sanitized earlier, requiring it be
done before the discussions take place in order to allow them to occur in
public will put an additional item on the critical path for the customer to
have their bug fixed.  That's a serious problem.

So can you be a little more specific about what data you are concerned about
being preserved?

    The policy of the gcc community is that patch discussion, approval,
    and application happens in a particular manner.  

Sure, but that "manner" is significantly different when somebody with
maintainer privilege on a part of the compiler is doing the patch, as would
be the case with all ACT folks patching the front end, vs. somebody who
doesn't have such a privilege.  And what Arno is doing is really not all
that much different than that procedure: basically all that's happening is
that he's acting as a surrogate for the other people.

             reply	other threads:[~2004-09-10  1:16 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  1:52 Richard Kenner [this message]
2004-09-10  2:18 ` Paul Brook
2004-09-10  5:08 ` Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
2004-09-10 17:55 Richard Kenner
2004-09-10 22:07 ` Phil Edwards
2004-09-10 11:58 Richard Kenner
2004-09-10 14:11 ` Gabriel Dos Reis
2004-09-10  5:39 Richard Kenner
2004-09-10  6:14 ` Phil Edwards
2004-09-10  4:38 Richard Kenner
2004-09-10  4:55 ` Kaveh R. Ghazi
2004-09-10  3:12 Richard Kenner
2004-09-10  2:18 Richard Kenner
2004-09-10  5:19 ` Phil Edwards
2004-09-09 22:17 Richard Kenner
2004-09-09 22:12 Wolfgang Bangerth
2004-09-09 21:36 Richard Kenner
2004-09-09 22:06 ` Duncan Sands
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 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
2004-09-09 19:40 ` Kaveh R. Ghazi

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=10409100119.AA16565@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.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).