From: Peter TB Brett <peter@peter-b.co.uk>
To: guile-devel@gnu.org
Subject: Re: Guile 2.2 TODO
Date: Sun, 01 Sep 2013 20:07:19 +0100 [thread overview]
Message-ID: <8761uk8ioo.fsf@harrington.peter-b.co.uk> (raw)
In-Reply-To: 87vc2kztv1.fsf@pobox.com
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
Hi Andy,
All of this stuff sounds great, and I can't wait for it to be available!
Can I please request an addition to your to-do list: a document that
explains what changes to libguile-using programs will be required?
Getting people from 1.8 to 2.0 is hard enough, and soon Guile will be
*two* major releases ahead of many of my users... I still need to
support people using 1.8.x.
Thanks,
Peter
--
Dr Peter Brett <peter@peter-b.co.uk>
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-09-01 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 11:03 Guile 2.2 TODO Andy Wingo
2013-09-01 19:07 ` Peter TB Brett [this message]
2013-09-02 20:01 ` Andy Wingo
2013-09-14 13:48 ` Ludovic Courtès
2013-09-17 20:16 ` Andy Wingo
2013-10-03 21:27 ` Andy Wingo
2013-10-18 9:56 ` Andy Wingo
2013-10-29 12:27 ` Ludovic Courtès
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=8761uk8ioo.fsf@harrington.peter-b.co.uk \
--to=peter@peter-b.co.uk \
--cc=guile-devel@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).