From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: netapp!byron@netcom.com (Byron Rakitzis)
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: ^C leak
Date: Sat, 15 Aug 1992 21:32:22 -0400 [thread overview]
Message-ID: <92Aug15.213230edt.2613@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Sat, 15 Aug 92 04:07:48 EDT." <9208150807.AA18161@netapp.netapp>
I suggest not altering rc unnecessarily. Given that there are lots of
yacc implementations floating around, including a public domain one
from corbett@berkeley.edu, you might as well just tell people to use
one of those. If you ship a y.tab.[ch] with rc, it may not be
necessary to run yacc at all.
prev parent reply other threads:[~1992-08-16 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-08-15 8:07 Byron Rakitzis
1992-08-16 1:32 ` Scott Schwartz [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=92Aug15.213230edt.2613@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--cc=netapp!byron@netcom.com \
--cc=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).