From: Kevin Ryde <user42@zip.com.au>
To: guile-devel@gnu.org
Subject: Re: Heads up: Releasing 1.8.2
Date: Thu, 16 Aug 2007 09:08:42 +1000 [thread overview]
Message-ID: <87bqd8xuo5.fsf@zip.com.au> (raw)
In-Reply-To: <66e540fe0706250542gfaf6effif30c55b81d1db5e3@mail.gmail.com> (Mikael Djurfeldt's message of "Mon, 25 Jun 2007 14:42:10 +0200")
"Mikael Djurfeldt" <mikael@djurfeldt.com> writes:
>
> Isn't the original and only purpose of Guile's provide/require to be
> part of support for slib?
It wasn't a clone of what's in emacs was it? And/or a way to have
built-time optional bits present or not in the guile core, like threads?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2007-08-15 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 15:43 Heads up: Releasing 1.8.2 Ludovic Courtès
2007-06-24 22:31 ` Greg Troxel
2007-06-25 8:11 ` Ludovic Courtès
2007-06-25 12:42 ` Mikael Djurfeldt
2007-06-26 12:19 ` Greg Troxel
2007-06-26 15:34 ` Mikael Djurfeldt
2007-08-15 23:08 ` Kevin Ryde [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
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=87bqd8xuo5.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).