From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <guerby@acm.org>
Cc: <gcc@gcc.gnu.org>
Subject: Re: ACATS legal status cleared by FSF
Date: Wed, 05 Dec 2001 16:21:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0112060010460.28350-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <200112052305.fB5N5D700531@ulmo.localdomain>
On Thu, 6 Dec 2001 guerby@acm.org wrote:
> [4] What should be the top directory in the gcc tree for the ACATS
> test suite? gcc/gcc/testsuite/ada/acats or a top level directory or
That seems plausible - presumably "runtest --tool ada" will be used in
"make check" to run both those and other Ada tests?
> [8] I propose to commit directly with the patch applied, I'll of course
> commit and maintain a list of tests that were modified and why, any
> objection?
It is arguable that perhaps the CVS vendor branch mechanism should be used
- import the unmodified sources on the vendor branch with GCC's modified
version on the mainline. This should make it easy to use CVS to see what
the differences from unmodified ACATS are. I don't know whether whatever
tests it is deliberately decided to drop rather than include in the GCC
testsuite should also go on the vendor branch, or whether it should just
be documented which are dropped.
> The upstream ACATS is maintained using CVS, web documents and
> interface from <http://www.ada-auth.org/>. There's a very low volume
> public mailing list.
We ought to have a link to this from the Ada section of readings.html.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2001-12-06 0:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 15:13 guerby
2001-12-05 16:21 ` Joseph S. Myers [this message]
2001-12-05 18:00 ` Jerry van Dijk
2001-12-06 3:36 ` Geoff Keating
2001-12-06 9:34 ` Geert Bosch
2001-12-06 11:48 ` Zack Weinberg
2001-12-06 14:24 ` Geert Bosch
2001-12-06 14:32 ` Joseph S. Myers
2001-12-06 15:10 ` Zack Weinberg
2001-12-06 15:41 ` Geert Bosch
2001-12-06 18:22 ` Zack Weinberg
2001-12-05 15:28 Richard Kenner
2001-12-05 15:41 ` guerby
2001-12-05 23:36 dewar
2001-12-06 15:01 Richard Kenner
2001-12-06 15:40 Richard Kenner
2001-12-06 17:38 dewar
2001-12-06 19:09 dewar
2001-12-07 3:18 Richard Kenner
2001-12-07 17:59 dewar
2001-12-07 18:50 mike stump
2001-12-07 18:57 dewar
2001-12-07 19:12 dewar
2001-12-09 13:02 ` Zack Weinberg
2001-12-09 14:52 ` guerby
2001-12-09 19:47 ` Geert Bosch
2001-12-09 14:00 dewar
2001-12-09 15:06 dewar
2001-12-09 15:55 ` Joseph S. Myers
2001-12-09 19:03 dewar
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=Pine.LNX.4.33.0112060010460.28350-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.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).