From: Julian Graham <joolean@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: TODO for 2.0
Date: Mon, 19 Apr 2010 08:11:26 -0400 [thread overview]
Message-ID: <m2g2bc5f8211004190511p5af88a92m369bef6367709c8e@mail.gmail.com> (raw)
In-Reply-To: <m3ochfbyb7.fsf@pobox.com>
Hi Andy,
> I'll add this to my list, then. Is there no smaller test case than
> compiling the entire wrapper module? Does this problem occur with
> smaller libraries as well? I would love to have a simple test case that
> I can run on master. I'll spelunk on your branch, though, if that's
> necessary.
Thanks! I've been trying to create a more discrete test case -- no
luck as yet, but I'll let you know if I come up with one.
Regards,
Julian
next prev parent reply other threads:[~2010-04-19 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 11:59 TODO for 2.0 Andy Wingo
2010-04-17 18:30 ` Mike Gran
2010-04-18 15:57 ` Julian Graham
2010-04-19 9:12 ` Andy Wingo
2010-04-19 12:11 ` Julian Graham [this message]
2010-04-18 20:53 ` Ludovic Courtès
2010-04-19 9:33 ` Andy Wingo
2010-04-19 17:09 ` Ken Raeburn
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=m2g2bc5f8211004190511p5af88a92m369bef6367709c8e@mail.gmail.com \
--to=joolean@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).