From: Marius Vollmer <mvo@zagadka.de>
Cc: Christopher Cramer <crayc@pyro.net>, guile-devel@gnu.org
Subject: Re: future thread interface
Date: 27 Jul 2003 18:51:30 +0200 [thread overview]
Message-ID: <873cgrrjzh.fsf@zagadka.ping.de> (raw)
In-Reply-To: <xy7he61b2le.fsf@nada.kth.se>
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
> I posted an analysis of the thread situation on this list before
> Christmas. I think you agreed with the conclusions.
Yes, I see now that I'm not being very consistent. Unfortunately, I
don't have the, ahem, 'mental capacity' right now to do this topic
justice, so I'll better shut up for now. Christopher, please listen
to Mikael about what is going to happen with the threads.
--
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
prev parent reply other threads:[~2003-07-27 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 6:32 future thread interface Christopher Cramer
2003-07-01 10:27 ` Marius Vollmer
2003-07-01 18:57 ` Christopher Cramer
2003-07-05 12:05 ` Mikael Djurfeldt
2003-07-27 16:51 ` Marius Vollmer [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=873cgrrjzh.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=crayc@pyro.net \
--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).