From: Byron Rakitzis <byron>
To: rc
Subject: Re: first impressions rc 1.3beta
Date: Fri, 7 Feb 1992 08:57:21 -0600 [thread overview]
Message-ID: <92Feb7.085728cst.45332@archone.tamu.edu> (raw)
Re: bison. bison generates a larger file than old Berkeley yacc, my
reference point. Now, this is starting to look like useless
information, since no one seems to be running the old yacc! (NeXT
does---I'll keep using it as long as I can for ALL my rc builds). I'll
take the comment out.
Re: trip.rc and /etc/termcap. It needs a big file. What's a big file
that can be found on System V as well as Berkeley systems? (A big TEXT
file, not /*unix). And note that "passing trip.rc" does not really mean
much at this point--- as a verification suite it is hopelessly
inadequate. I just wanted to push one out the door so people could see
that I do intend to eventually follow this route.
Byron.
next reply other threads:[~1992-02-07 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-02-07 14:57 Byron Rakitzis [this message]
1992-02-07 20:23 ` Brendan Kehoe
-- strict thread matches above, loose matches on Subject: below --
1992-02-08 16:38 Byron Rakitzis
1992-02-08 15:58 malte
1992-02-08 15:44 malte
1992-02-07 13:39 malte
1992-02-07 13:53 ` Robert van Liere
1992-02-07 20:21 ` schwartz
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=92Feb7.085728cst.45332@archone.tamu.edu \
--to=rc@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).