From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-user@gnu.org, gtrees-devel@vychodil.inf.upol.cz
Subject: Re: scm_gc_malloc not in stable branch
Date: 30 Nov 2002 14:35:44 +0100 [thread overview]
Message-ID: <87bs47b2of.fsf@zagadka.ping.de> (raw)
In-Reply-To: <20021129234342.00ffb7da.david@altosw.be>
David Pirotte <david@altosw.be> writes:
> so, should I talk to the gtree developers or is it a guile problem? am
> I missing something here?
You should talk to th gtree developers. They might have made the
decision to only support the unstable Guile series (which is a
perfectly fine decision) and then you have to unstable Guile yourself.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-11-30 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-30 4:43 scm_gc_malloc not in stable branch David Pirotte
2002-11-30 5:49 ` Thien-Thi Nguyen
2002-11-30 13:35 ` 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=87bs47b2of.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=gtrees-devel@vychodil.inf.upol.cz \
--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).