From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Klaus Schilling <schilling.klaus@web.de>
Cc: guile-user@gnu.org
Subject: Re: Guile 1.4.1.111 available
Date: Thu, 27 Sep 2007 15:06:08 +0200 [thread overview]
Message-ID: <87y7esmf5r.fsf@ambire.localdomain> (raw)
In-Reply-To: <20070927.124154.59469146.schilling.klaus@web.de> (Klaus Schilling's message of "Thu\, 27 Sep 2007 12\:41\:54 +0200 \(CEST\)")
() Klaus Schilling <schilling.klaus@web.de>
() Thu, 27 Sep 2007 12:41:54 +0200 (CEST)
What's the reason for continuing 1.4
while 1.8.* is already released?
one reason is that i can experiment w/o too much fear
of bothering users (-: since there seem to be so few).
[cc trimmed.]
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-09-27 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 8:59 Guile 1.4.1.111 available Thien-Thi Nguyen
2007-09-27 10:41 ` Klaus Schilling
2007-09-27 13:06 ` Thien-Thi Nguyen [this message]
2007-09-28 7:44 ` William Xu
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=87y7esmf5r.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=schilling.klaus@web.de \
/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).