public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/6816: Makefile.adalib needs to be updated (Gigi file name changes)
Date: Mon, 12 May 2003 23:26:00 -0000 [thread overview]
Message-ID: <20030512232600.12405.qmail@sources.redhat.com> (raw)
The following reply was made to PR ada/6816; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: dannysmith@users.sourceforge.net, gcc-gnats@gcc.gnu.org,
nobody@gcc.gnu.org, jvandyk@attglobal.net
Cc:
Subject: Re: ada/6816: Makefile.adalib needs to be updated (Gigi file name changes)
Date: Mon, 12 May 2003 16:17:31 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=6816
Hello,
gcc 3.1 is a bit old at this point. Would it be possible for the
submitter to check and see if this problem occurs with more current
sources (ie 3.3 prereleae). Thanks,
Dara
next reply other threads:[~2003-05-12 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 23:26 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 10:20 Jerry van Dijk
2003-05-13 6:39 steven
2002-10-05 17:18 bosch
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=20030512232600.12405.qmail@sources.redhat.com \
--to=dhazeghi@yahoo.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).