From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-devel@gnu.org
Subject: Re: User perception on backward compatibility
Date: Thu, 21 Jan 2010 13:42:47 +0100 [thread overview]
Message-ID: <87eiljiq7s.fsf@ambire.localdomain> (raw)
In-Reply-To: <87y6jrzq10.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 21 Jan 2010 11:54:51 +0100")
() ludo@gnu.org (Ludovic Courtès)
() Thu, 21 Jan 2010 11:54:51 +0100
I think the next big task will be to list and try to reduce
incompatibilities compared to 1.8.
Yes, please.
At the moment, i would ask you to look at the guile-user message
w/ subject "(define ((f a) b) ...)".
thi
next prev parent reply other threads:[~2010-01-21 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 10:54 User perception on backward compatibility Ludovic Courtès
2010-01-21 12:42 ` Thien-Thi Nguyen [this message]
2010-01-21 14:27 ` Ludovic Courtès
2010-01-21 20:14 ` Neil Jerram
2010-01-21 15:09 ` Mike Gran
2010-01-21 16:04 ` Ludovic Courtès
2010-01-21 16:57 ` Sergey Poznyakoff
2010-01-22 14:26 ` Peter Brett
[not found] <cmu-lmtpd-30631-1264093887-1@mail-imap1.uio.no>
2010-01-21 17:36 ` Kjetil S. Matheussen
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=87eiljiq7s.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--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).