From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Re: When is 1.8 going to be released
Date: Thu, 24 Jul 2003 15:09:53 +0200 [thread overview]
Message-ID: <16159.55969.896460.534700@localhost.localdomain> (raw)
In-Reply-To: <87n0f6ohar.fsf@zagadka.ping.de>
mvo@zagadka.de writes:
> > Just wondering what time-frame you had in mind for releasing 1.8,
>
> I myself don't have any time-frame yet and I don't feel like we need
> to hurry. But that's just me. I'm certainly looking forward to 1.8,
> it's going to have some very good things in it.
On 2nd thought, I also do not have a particular hurry. However, Jan is
getting annoyed at having to patch GUILE to get it compiling on
cygwin. Who is working on the 1.6 branch maintenance?
> - Implement scm replacements for all of GH
>
> This includes designing the replacement first and writing
> documentation, both tutorial style and reference style.
I don't quite get this. Where is the exact problem here?
What's wrong with replacing gh_ with scm_ (or scm_c_ ) in the .c and
.h files?
> - Make 1.8 backwards compatible again with 1.6.
>
> This should be nearly done, but needs more testing.
>
> I want to work on these items when I have finished my thesis, which
> hopefully happens in the next three to four weeks. Knock on wood...
OK, hang in there, you'll survive.
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-07-24 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 20:24 When is 1.8 going to be released Han-Wen Nienhuys
2003-07-22 12:51 ` Marius Vollmer
2003-07-24 13:09 ` Han-Wen Nienhuys [this message]
2003-08-23 17:32 ` Rob Browning
2003-08-27 23:53 ` Kevin Ryde
2003-09-12 16:06 ` Marius Vollmer
2003-07-30 23:07 ` Kevin Ryde
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16159.55969.896460.534700@localhost.localdomain \
--to=hanwen@cs.uu.nl \
--cc=guile-devel@gnu.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).