public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com>
To: Arnaud Charlet <charlet@ACT-Europe.FR>
Cc: Jan Hubicka <hubicka@ucw.cz>,
	Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
	Laurent GUERBY <laurent@guerby.net>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Ada mainline
Date: Thu, 09 Sep 2004 14:03:00 -0000	[thread overview]
Message-ID: <1094737644.10163.247.camel@localhost.localdomain> (raw)
In-Reply-To: <20040909151348.A3539@dublin.act-europe.fr>

On Thu, 2004-09-09 at 09:13, Arnaud Charlet wrote:

> Generally speaking, if simple changes (even if not complete or perfect)
> fixing such Ada breakages could be put in place rapidly, that would
> be a big help.
> 
Why should we?  You folks like to do mega dumps of your local trees,
instead of following the usual patch posting and committing procedures. 
That's probably the single most frustrating aspect I find regarding Ada
in the FSF tree.


Diego.

  parent reply	other threads:[~2004-09-09 13:47 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 12:06 Richard Kenner
2004-09-09 12:54 ` Arnaud Charlet
2004-09-09 13:13   ` Jan Hubicka
2004-09-09 13:36     ` Arnaud Charlet
2004-09-09 13:43       ` Jan Hubicka
2004-09-09 13:47       ` Paolo Bonzini
2004-09-09 13:48         ` Paolo Bonzini
2004-09-09 13:50         ` Arnaud Charlet
2004-09-09 14:05           ` Arnaud Charlet
2004-09-09 14:03       ` Diego Novillo [this message]
2004-09-09 14:51         ` Arnaud Charlet
2004-09-09 18:50           ` Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
2004-09-10 12:34 Richard Kenner
2004-09-10 14:50 ` Gabriel Dos Reis
2004-09-10  1:59 Richard Kenner
2004-09-10  8:45 ` Robert Dewar
2004-09-10  9:50 ` Joseph S. Myers
2004-09-10 15:40 ` James A. Morrison
2004-09-09 22:37 D. Starner
2004-09-09 22:53 ` Robert Dewar
2004-09-10  0:38   ` Florian Weimer
2004-09-10 15:02 ` Paul Koning
2004-09-10 17:40   ` Matt Austern
2004-09-09 19:22 Richard Kenner
2004-09-09 21:00 ` Daniel Berlin
2004-09-09 21:18   ` Robert Dewar
2004-09-09 21:22     ` Diego Novillo
2004-09-09 21:39       ` Joseph S. Myers
2004-09-09 21:52       ` Robert Dewar
2004-09-09 22:15         ` Richard Henderson
2004-09-09 22:38         ` Diego Novillo
2004-09-09 23:00           ` Robert Dewar
2004-09-09 22:41         ` Gabriel Dos Reis
2004-09-09 23:06           ` Robert Dewar
     [not found]         ` <4140D9D6.504@bellsouth.net>
2004-09-09 22:57           ` Robert Dewar
2004-09-09 23:11             ` Robert Dewar
2004-09-09 23:14             ` Richard Henderson
2004-09-09 23:19               ` Robert Dewar
2004-09-10 11:27                 ` Laurent GUERBY
2004-09-09 21:54       ` Robert Dewar
2004-09-09 23:31         ` Kaveh R. Ghazi
2004-09-10 15:55           ` Manfred Hollstein
2004-09-09 21:29     ` Daniel Berlin
2004-09-09 21:57       ` Robert Dewar
2004-09-09 22:32         ` Diego Novillo
2004-09-09 11:37 Laurent GUERBY
2004-09-09 11:51 ` Giovanni Bajo

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=1094737644.10163.247.camel@localhost.localdomain \
    --to=dnovillo@redhat.com \
    --cc=charlet@ACT-Europe.FR \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=laurent@guerby.net \
    /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).