From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Guile 1.6.7 has been released.
Date: Wed, 22 Dec 2004 18:41:26 +0000 [thread overview]
Message-ID: <41C9BFD6.9050907@ossau.uklinux.net> (raw)
In-Reply-To: <87ekhjtsn1.fsf@trouble.defaultvalue.org>
Rob Browning wrote:
> We are pleased to announce the availability of a new Guile release.
> This is the next maintenance release for the 1.6 stable series.
>
> You can find it here:
>
> ftp://ftp.gnu.org/gnu/guile/guile-1.6.7.tar.gz.
>
Vaguely related to this ... what is required to push one of the recent
Guile versions into Debian testing (which is currently at 1.6.4)? I'm
personally interested in 1.6.5 or better.
Thanks,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-12-22 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 18:26 Guile 1.6.7 has been released Rob Browning
2004-12-22 18:41 ` Neil Jerram [this message]
2004-12-22 20:14 ` Rob Browning
2004-12-23 1:20 ` Neil Jerram
2004-12-23 3:14 ` Rob Browning
2004-12-24 22:39 ` Neil Jerram
2004-12-25 22:37 ` 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=41C9BFD6.9050907@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).