From: "Berek" <berek@usa.net>
To: "Ben Elliston" <bje@redhat.com>, "Syd Polk" <spolk@redhat.com>
Cc: <sourcenav@sources.redhat.com>
Subject: RE: SN 5.0 and Beta
Date: Fri, 29 Dec 2000 17:07:00 -0000 [thread overview]
Message-ID: <NDBBJEBJPMNFKBGLKCNFGEBKEPAA.berek@usa.net> (raw)
In-Reply-To: <Pine.LNX.4.31.0012301008590.31445-100000@moshpit.cygnus.com>
I've got a great test suite, but it belongs to my employers :( ...and they
won't let me provide it to the red hat crew.
> -----Original Message-----
> From: Ben Elliston [ mailto:bje@redhat.com ]
> Sent: Friday, December 29, 2000 18:10
> To: Syd Polk
> Cc: berek@usa.net; sourcenav@sources.redhat.com
> Subject: Re: SN 5.0 and Beta
>
>
> spolk wrote:
>
> Alas, there are not that many fixes to C++ parsing in 5.0. Most of it
> is GUI cleanup.
>
> IMHO, what would fix the C++ parser to the greatest extent in the shortest
> possible time is to implement a testsuite. I wish I had time to do it.
>
> Ben
>
>
prev parent reply other threads:[~2000-12-29 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 19:41 Berek
2000-12-29 10:39 ` Syd Polk
2000-12-29 15:09 ` Ben Elliston
2000-12-29 17:07 ` Berek [this message]
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=NDBBJEBJPMNFKBGLKCNFGEBKEPAA.berek@usa.net \
--to=berek@usa.net \
--cc=bje@redhat.com \
--cc=sourcenav@sources.redhat.com \
--cc=spolk@redhat.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).