From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: rvclayton@acm.org (r. clayton)
Cc: bug-guile@gnu.org
Subject: Re: guile-www 1.1.1 & 2.16 problems under guile 1.8.
Date: Sat, 12 May 2007 16:06:22 +0200 [thread overview]
Message-ID: <87r6pmw2zl.fsf@ambire.localdomain> (raw)
In-Reply-To: <874pmjoscg.fsf@UlanBator.myhome.westell.com> (r. clayton's message of "11 May 2007 19\:25\:51 -0400")
() rvclayton@acm.org (r. clayton)
() 11 May 2007 19:25:51 -0400
I downloaded 2.16 and 2.18 and both installed correctly.
i'm glad to hear that.
(let's hope next release maintains this property. :-)
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2007-05-12 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 1:13 guile-www 1.1.1 & 2.16 problems under guile 1.8 r. clayton
2007-05-11 7:16 ` Ludovic Courtès
2007-05-11 12:28 ` Thien-Thi Nguyen
2007-05-11 14:43 ` Ludovic Courtès
2007-05-11 15:25 ` Thien-Thi Nguyen
2007-05-11 23:25 ` r. clayton
2007-05-12 14:06 ` Thien-Thi Nguyen [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=87r6pmw2zl.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=bug-guile@gnu.org \
--cc=rvclayton@acm.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).