From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: GNU Guile 2.0.0 released
Date: Wed, 16 Feb 2011 20:41:52 +0100 [thread overview]
Message-ID: <m3bp2b4vi7.fsf@unquote.localdomain> (raw)
In-Reply-To: <87lj1f52cp.fsf@netris.org> (Mark H. Weaver's message of "Wed, 16 Feb 2011 12:13:58 -0500")
On Wed 16 Feb 2011 18:13, Mark H Weaver <mhw@netris.org> writes:
> Looks like we all forgot to look at the README though:
>
>> !!! This is not a Guile release; it is a source tree retrieved via
>> Git or as a nightly snapshot at some random time after the
>> Guile 1.8 release. If this were a Guile release, you would not see
>> this message. !!! [fixme: zonk on release]
>>
>> This is a 1.9 development version of Guile, Project GNU's extension
> [...]
>> The next stable release will likely be version 2.0.0.
Heh, indeed.... But if that's the worst blunder, then we're probably
doing good. Knock on wood!
Peace,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-02-16 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 10:29 GNU Guile 2.0.0 released Ludovic Courtès
2011-02-16 17:13 ` Mark H Weaver
2011-02-16 19:41 ` Andy Wingo [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=m3bp2b4vi7.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mhw@netris.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).