From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: jsm28@cam.ac.uk
Cc: gcc@gcc.gnu.org
Subject: Re: ACATS
Date: Thu, 06 Dec 2001 15:12:00 -0000 [thread overview]
Message-ID: <10112062304.AA04387@vlsi1.ultra.nyu.edu> (raw)
The point of using the vendor branch is to have *both* the original form
(on the vendor branch) and the GCC version (on the mainline) in CVS - and
when a new version is imported onto the vendor branch, CVS should be able
to help with a lot of the work of merging onto the mainline. The CVS
experts here can probably provide step-by-step instructions for doing this
and indications of the pitfalls.
I think there's a disconnect here.
The issue is that the *format*, not the *content*, of the two branches
is fundamentally different. The ACATS cvs contains one file per test
while the GCC ACATS cvs would contain one file per *compilation unit*
and there are often multiple such per test.
next reply other threads:[~2001-12-06 23:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 15:12 Richard Kenner [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 21:14 ACATS Richard Kenner
2004-04-30 1:48 ` ACATS Zack Weinberg
2004-05-03 20:39 ` ACATS Mark Mitchell
2004-04-29 20:55 ACATS Richard Kenner
2004-04-29 19:46 ACATS Richard Kenner
2004-04-29 20:46 ` ACATS John R. Shannon
2004-04-29 13:12 ACATS John R. Shannon
2004-04-29 13:44 ` ACATS Dave Korn
2004-04-29 13:55 ` ACATS John R. Shannon
2004-04-29 14:10 ` ACATS Dave Korn
2004-04-29 17:11 ` ACATS John R. Shannon
2004-04-29 18:32 ` ACATS Dave Korn
2004-04-29 18:46 ` ACATS John R. Shannon
2001-12-06 15:08 ACATS Richard Kenner
2001-12-06 14:32 ACATS guerby
2001-12-06 15:00 ` ACATS Joseph S. Myers
2001-12-06 15:06 ` ACATS Florian Weimer
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=10112062304.AA04387@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
/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).