From: fche@redhat.com (Frank Ch. Eigler)
To: Doug Evans <dje@sebabeach.org>
Cc: cgen@sourceware.org
Subject: Re: stop assuming cgen is scripted?
Date: Mon, 08 Jun 2009 14:54:00 -0000 [thread overview]
Message-ID: <y0mfxeapyhx.fsf@fche.csb> (raw)
In-Reply-To: <200906051304.n55D4xAr025352@localhost.localdomain> (Doug Evans's message of "Fri, 5 Jun 2009 06:04:59 -0700")
Doug Evans <dje@sebabeach.org> writes:
> One thing I would like to change in cgen is the assumption that it's
> scripted. It originally didn't assume it was scripted. How much
> resistance is there to removing this assumption?
Can you elaborate what this would entail in terms of code? We're
unlikely to have strong opinions in this regard; hobbit support was
only reluctantly removed because of interoperability problems with
guile, IIRC.
But I think we're all just happy to see you back actively on the
project.
- FChE
next prev parent reply other threads:[~2009-06-08 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 4:46 Doug Evans
2009-06-08 14:54 ` Frank Ch. Eigler [this message]
2009-06-09 21:29 ` 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=y0mfxeapyhx.fsf@fche.csb \
--to=fche@redhat.com \
--cc=cgen@sourceware.org \
--cc=dje@sebabeach.org \
/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).