From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: Bug Reports for 1.6 Release Candidates
Date: Sun, 17 Mar 2002 00:22:05 -0800 [thread overview]
Message-ID: <E16mVvZ-0003zb-00@giblet> (raw)
In-Reply-To: 87u1rfdhcd.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us
From: Evan Prodromou <evan@glug.org>
Date: Sat, 16 Mar 2002 21:05:22 -0600
http://evan.prodromou.san-francisco.ca.us/BUGS2html.scm
cool. output for guile-core and guile-core-1.6 should be appearing
shortly under "details" heading under: http://www.glug.org/snap/ .
perhaps guile-core-1.4 will get a BUGS file in the near future.
(a link to the (slightly modified) source is forthcoming.)
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-17 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 18:50 Bug Reports for 1.6 Release Candidates Evan Prodromou
2002-03-17 3:05 ` Evan Prodromou
2002-03-17 8:22 ` Thien-Thi Nguyen [this message]
2002-03-17 16:46 ` Evan Prodromou
2002-03-18 3:46 ` Rob Browning
2002-03-18 3:59 ` Evan Prodromou
2002-03-18 14:17 ` Rob Browning
2002-04-03 3:39 ` Thien-Thi Nguyen
2002-04-03 4:18 ` Rob Browning
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=E16mVvZ-0003zb-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@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).