From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org, gtrees-devel@vychodil.inf.upol.cz
Subject: Re: scm_gc_malloc not in stable branch
Date: Fri, 29 Nov 2002 21:49:57 -0800 [thread overview]
Message-ID: <E18I0Vp-0000Dw-00@giblet> (raw)
In-Reply-To: <20021129234342.00ffb7da.david@altosw.be> (message from David Pirotte on Fri, 29 Nov 2002 23:43:42 -0500)
From: David Pirotte <david@altosw.be>
Date: Fri, 29 Nov 2002 23:43:42 -0500
so, should I talk to the gtree developers or is it a
guile problem? am I missing something here?
|
v
you are missing the high probability that you and the
gtrees developers share the trait of being programmers,
and the consequence of understanding that fully. when
you find it you will ask better questions but perhaps
by then you won't need to.
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-11-30 5:49 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 [this message]
2002-11-30 13:35 ` 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=E18I0Vp-0000Dw-00@giblet \
--to=ttn@giblet.glug.org \
--cc=gtrees-devel@vychodil.inf.upol.cz \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).