From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: SCM_DEBUG reveals possible goops bugs
Date: Sun, 10 May 2009 21:44:18 +0200 [thread overview]
Message-ID: <87zldkspyl.fsf@gnu.org> (raw)
In-Reply-To: 1241410479.21077.2255.camel@localhost.localdomain
Hi Mike,
Mike Gran <spk121@yahoo.com> writes:
> Here are some things I've noticed. I don't know what to make of them,
> but, I wanted to jot them down before I forgot them.
I suggest that you file them in the bug tracker so we *really* don't
forget them. :-)
Thanks,
Ludo'.
prev parent reply other threads:[~2009-05-10 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 4:14 SCM_DEBUG reveals possible goops bugs Mike Gran
2009-05-10 19:44 ` Ludovic Courtès [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=87zldkspyl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).