public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@redhat.com>
To: joel.sherrill@OARcorp.com
Cc: gcc@gcc.gnu.org, guerby@acm.org
Subject: Re: 3.1 branch Ada cross report
Date: Thu, 02 May 2002 08:23:00 -0000	[thread overview]
Message-ID: <xwuit66fua1.fsf@tonopah.toronto.redhat.com> (raw)
In-Reply-To: <3CD11FF7.D5697ED8@OARcorp.com>

It is approved for the CVS mainline.  I can do that.  Richard Kenner has
already said it looked OK with him too, so this should be OK for the Ada folks.

You might want to check with ACT to make sure it gets into their tree.  They
have a history of losing patches that are checked into the FSF tree but not
into the ACT tree.  They apparently don't understand that the FSF tree is the
master source tree.

I believe explicit approval from Mark Mitchell is necessary to check it into
the 3.1 release branch.

Jim

  reply	other threads:[~2002-05-02 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30 10:46 Joel Sherrill
2002-05-01 14:09 ` Jim Wilson
2002-05-02  4:15   ` Joel Sherrill
2002-05-02  8:23     ` Jim Wilson [this message]
2002-05-01 14:39 Richard Kenner
2002-05-02  8:49 Richard Kenner

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=xwuit66fua1.fsf@tonopah.toronto.redhat.com \
    --to=wilson@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=guerby@acm.org \
    --cc=joel.sherrill@OARcorp.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).