From: Neil Jerram <neil@ossau.uklinux.net>
To: Julian Graham <joolean@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: trace examples broken in master
Date: Wed, 23 Sep 2009 21:19:25 +0100 [thread overview]
Message-ID: <87y6o5ifci.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <2bc5f8210909221834vb2a71sf45c0c22cd7258be@mail.gmail.com> (Julian Graham's message of "Tue, 22 Sep 2009 21:34:37 -0400")
Julian Graham <joolean@gmail.com> writes:
> Argh, yes, that was it. Thanks! I'll clean up my environment.
Phew. Otherwise I was out of ideas...
Neil
prev parent reply other threads:[~2009-09-23 20:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 19:22 trace examples broken in master Julian Graham
2009-07-14 8:07 ` Neil Jerram
2009-07-23 21:42 ` Andy Wingo
2009-08-14 17:00 ` Neil Jerram
2009-08-14 17:21 ` Julian Graham
2009-08-30 10:07 ` Neil Jerram
2009-08-30 15:10 ` Julian Graham
2009-09-01 22:16 ` Neil Jerram
2009-09-15 21:54 ` Neil Jerram
2009-09-16 0:55 ` Neil Jerram
2009-09-22 14:28 ` Julian Graham
2009-09-22 19:57 ` Neil Jerram
2009-09-23 1:34 ` Julian Graham
2009-09-23 20:19 ` Neil Jerram [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=87y6o5ifci.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=joolean@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).