From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <mvo@zagadka.ping.de>,
Guile Mailing List <guile-user@gnu.org>
Subject: Re: problem becouse scm_tc7_contin is not defined
Date: Mon, 16 Sep 2002 00:00:32 -0500 [thread overview]
Message-ID: <87admir0jz.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0209151942420.9390-100000@ariel.lan.telltronics.org> (Steve Tell's message of "Sun, 15 Sep 2002 20:04:29 -0400 (EDT)")
Steve Tell <tell@telltronics.org> writes:
> _Are_ there any scwm developers any more?
I believe Pieter is working on working on the update scwm to 1.6.0.
> Or am I looking in the wrong place? I was thinking of abandoning scwm
> myself, perhaps I don't have to if work is continuing and there is a
> new version that at least works with guile-1.4?
If he keeps up, sounds like 1.6.0 will be the next supported version.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-09-16 5:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020910103210.30704.32477.Mailman@monty-python.gnu.org>
2002-09-10 11:57 ` problem becouse scm_tc7_contin is not defined P Pareit
2002-09-10 19:04 ` Marius Vollmer
2002-09-11 10:01 ` P Pareit
2002-09-11 18:16 ` Marius Vollmer
2002-09-16 0:04 ` Steve Tell
2002-09-16 5:00 ` Rob Browning [this message]
2002-09-16 19:57 ` Marius Vollmer
2002-09-20 1:55 ` 1.4 vs. 1.5.x vs 1.6 snarfingdefined Steve Tell
2002-09-09 9:18 problem becouse scm_tc7_contin is not defined P Pareit
2002-09-09 18:08 ` Marius Vollmer
2002-09-09 18:10 ` Marius Vollmer
2002-09-09 18:43 ` Marius Vollmer
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=87admir0jz.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-user@gnu.org \
--cc=mvo@zagadka.ping.de \
/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).