From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: When is 1.8 going to be released
Date: Fri, 12 Sep 2003 18:06:52 +0200 [thread overview]
Message-ID: <87ekymq9cz.fsf@zagadka.ping.de> (raw)
In-Reply-To: <16159.55969.896460.534700@localhost.localdomain> (Han-Wen Nienhuys's message of "Thu, 24 Jul 2003 15:09:53 +0200")
Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
> 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?
Mostly Rob and myself. I'm not aware of Cygwin patches (which is
enterily my fault). Please mail them to me and I'll have a look.
>> - 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?
I can't answer this yet; maybe it is that simple.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-09-12 16:06 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
2003-08-23 17:32 ` Rob Browning
2003-08-27 23:53 ` Kevin Ryde
2003-09-12 16:06 ` Marius Vollmer [this message]
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=87ekymq9cz.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--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).