From: Ben Elliston <bje@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: Implementation Language
Date: Sun, 06 Aug 2000 15:27:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0008070826300.14710-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <20000806175233.C8142@redhat.com>
Right, though continuing to keep generated files cached in CVS at
least limits the pain to active developers instead of everyone.
True.
> btw, I'm playing with Rscheme a lot these days. [...]
Looks nice, but them nonstandard extensions sure look addictive.
Can someone provide some references to Rscheme on the Web?
Ben
next prev parent reply other threads:[~2000-08-06 15:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-29 9:26 Doug Evans
2000-07-31 18:31 ` Frank Ch. Eigler
2000-08-01 1:00 ` Ben Elliston
2000-08-02 17:10 ` Frank Ch. Eigler
2000-08-03 0:03 ` Ben Elliston
2000-08-03 7:07 ` matthew green
2000-08-03 9:31 ` Doug Evans
2000-08-03 9:49 ` Doug Evans
2000-08-03 16:23 ` Ben Elliston
2000-08-03 18:31 ` Doug Evans
2000-08-03 16:22 ` Ben Elliston
2000-08-05 10:16 ` Doug Evans
2000-08-06 14:52 ` Frank Ch. Eigler
2000-08-06 15:27 ` Ben Elliston [this message]
2000-08-07 14:01 ` Doug Evans
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=Pine.LNX.4.21.0008070826300.14710-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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).