From: Doug Evans <dje@transmeta.com>
To: Ben Elliston <bje@wasabisystems.com>
Cc: cgen@sources.redhat.com
Subject: Re: 1.1?
Date: Wed, 21 May 2003 04:03:00 -0000 [thread overview]
Message-ID: <16074.64131.818904.422433@casey.transmeta.com> (raw)
In-Reply-To: <87u1bpuf0w.fsf@sashimi.wasabisystems.com>
Ben Elliston writes:
> How much code do you think switching to GOOPS will shed? Presumably
> lots?
Dunno, precisely. But if we're to stay with Guile methinks
it's the right thing to do. [and I'm happy with that]
> > After that, is there anything else we'd want in a 1.1 release?
>
> Sounds good. A release has been needed for a while.
Yep. You convinced me. :-)
prev parent reply other threads:[~2003-05-21 4:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 3:16 1.1? Doug Evans
2003-05-21 3:58 ` 1.1? Ben Elliston
2003-05-21 4:03 ` Doug Evans [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=16074.64131.818904.422433@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=bje@wasabisystems.com \
--cc=cgen@sources.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).