From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Troubles with Objcode and Storing JIT Pointers
Date: Sat, 17 Jul 2010 13:36:52 +0200 [thread overview]
Message-ID: <m38w5a49wr.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTikOP9z1FeTj_i8HJgCpp7ylrj_noZKQ7hv-yhic@mail.gmail.com> (Noah Lavine's message of "Sat, 3 Jul 2010 14:28:50 -0400")
On Sat 03 Jul 2010 20:28, Noah Lavine <noah.b.lavine@gmail.com> writes:
> I just sent two patches which start to implement this to
> guile-sources@gnu.org. (The first patch is actually a small
> documentation change, which I made only so I could rewrite it with
> updated documentation in the second patch.)
Would you mind resending to guile-devel? It's better to discuss here :)
Re-post the rationale too, please.
Thanks!
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2010-07-17 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 18:19 Troubles with Objcode and Storing JIT Pointers Noah Lavine
2010-06-21 20:19 ` Andy Wingo
2010-06-21 22:23 ` Noah Lavine
2010-06-22 19:03 ` Andy Wingo
2010-07-03 18:28 ` Noah Lavine
2010-07-04 17:43 ` Noah Lavine
2010-07-17 11:36 ` Andy Wingo [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=m38w5a49wr.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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).