From: Carlo Wood <carlo@runaway.xs4all.nl>
To: burley@gnu.org (Craig Burley)
Cc: egcs@cygnus.com (egcs@cygnus.com)
Subject: Re: egcs testsuite & dejagnu : A special case?
Date: Thu, 02 Jul 1998 11:02:00 -0000 [thread overview]
Message-ID: <199807021422.QAA19572@jolan.ppro> (raw)
In-Reply-To: <199807011209.IAA15248@melange.gnu.org>
| Would this be worth trying to put into 1.1? (Isn't the freeze date
| for that coming up, like, this week?) If so, I'll try and do the
| work tout-de-suite myself unless someone (anyone :) with more
| scripting knowledge steps forward. Otherwise, I'll just leave it
| on my list and get to it when it percolates to the top (should
| be within a couple of months or so, though the fact that I'd find
| it personally useful might speed things up).
|
| tq vm, (burley)
Would you mind giving an exact description of the gcc invokation
etc that you have in mind, and what it will exactly accomplish?
I am not worried about the patch itself; however it is still unclear
what the `user interface' will become. I am thinking about a short
alinea that describes the syntax and a few example locations of the
involved files.
Carlo Wood <carlo@runaway.xs4all.nl>
next prev parent reply other threads:[~1998-07-02 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-01 0:54 Mike Stump
1998-07-01 7:26 ` Craig Burley
1998-07-01 20:20 ` Jeffrey A Law
1998-07-02 11:02 ` Carlo Wood [this message]
1998-07-03 0:12 ` Craig Burley
1998-07-03 0:50 ` Carlo Wood
1998-07-03 8:38 ` Craig Burley
1998-07-03 9:35 ` Carlo Wood
[not found] <199807031310.PAA24690@jolan.ppro>
1998-07-03 15:29 ` Craig Burley
-- strict thread matches above, loose matches on Subject: below --
1998-06-29 22:34 Mike Stump
1998-06-30 15:15 ` Craig Burley
1998-06-30 14:46 ` Jeffrey A Law
1998-06-25 18:53 Carlo Wood
1998-06-26 2:49 ` Manfred Hollstein
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=199807021422.QAA19572@jolan.ppro \
--to=carlo@runaway.xs4all.nl \
--cc=burley@gnu.org \
--cc=egcs@cygnus.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).