From: Neil Jerram <neil@ossau.uklinux.net>
To: Antoine Mathys <antoine_mathys@yahoo.fr>
Cc: guile-user@gnu.org
Subject: Re: threading issue in 1.8.3
Date: Fri, 01 Feb 2008 22:54:12 +0000 [thread overview]
Message-ID: <87ir18guej.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87bq72ubib.fsf@ossau.uklinux.net> (Neil Jerram's message of "Wed, 30 Jan 2008 23:41:48 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> Anyway, code in ~/.guile should expect (current-module) to be sane, so
> the necessary fix is still to make sure that (current-module) always
> returns a module (so long as the module system has booted). My
> proposed patch for this is attached.
Thanks for testing; this patch is in CVS now.
Neil
next prev parent reply other threads:[~2008-02-01 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 14:11 threading issue in 1.8.3 Antoine Mathys
2008-01-19 0:16 ` Neil Jerram
2008-01-30 23:41 ` Neil Jerram
2008-02-01 22:54 ` Neil Jerram [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-31 1:11 Antoine Mathys
2008-02-01 21:01 ` Neil Jerram
2008-01-31 1:44 Antoine Mathys
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=87ir18guej.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=antoine_mathys@yahoo.fr \
--cc=guile-user@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).