From: Nala Ginrut <nalaginrut@gmail.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: Preparing for 2.0.6
Date: Fri, 29 Jun 2012 10:38:23 +0800 [thread overview]
Message-ID: <CAPjoZofQOFmA-QkNA1C6mX+7D8XUph+kdpqty8UCmKzd6r11BQ@mail.gmail.com> (raw)
In-Reply-To: <CA+U71=PrUtHRwFwwX-qfnLQ31iE1LfipmnYi_Qn9FXEzMB0P7g@mail.gmail.com>
@Noah: Could you apply the patch to fix ecmascript?
http://lists.gnu.org/archive/html/guile-devel/2012-05/msg00001.html
@Andy: How about these patches:
http://lists.gnu.org/archive/html/guile-devel/2012-02/msg00196.html
http://lists.gnu.org/archive/html/guile-devel/2012-02/msg00165.html
On Fri, Jun 29, 2012 at 9:09 AM, Noah Lavine <noah.b.lavine@gmail.com> wrote:
> I think bug 10623 is fixed in stable-2.0, but I don't know how to
> close it in the tracker.
>
> Thanks,
> Noah
>
> On Thu, Jun 28, 2012 at 4:05 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Hello!
>>
>> Still hesitant between writing a native code back-end for IA64 and
>> making Guile multiboot-compliant? Hesitate no more!
>>
>> Time has come for 2.0.6, so let’s squash bugs!
>>
>> One thing I’d like to get in by then is the SRFI-9 “functional record
>> setters”. Mark: what’s your take on this?
>>
>> Optionally, integrating SRFI-64 would be great.
>>
>> Other than that, fixing as many bugs as we can.
>>
>> Any other ideas?
>>
>> Andy: would you like to take care of NEWS? :-)
>>
>> I’ll be mostly away from July 9th for some time, so I could push the
>> tarball by then, or otherwise during the GHM.
>>
>> Thanks,
>> Ludo’.
>>
>>
>
next prev parent reply other threads:[~2012-06-29 2:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 20:05 Preparing for 2.0.6 Ludovic Courtès
2012-06-28 20:27 ` Ian Price
2012-06-28 21:35 ` Andy Wingo
2012-06-29 1:09 ` Noah Lavine
2012-06-29 2:38 ` Nala Ginrut [this message]
2012-06-29 2:49 ` Noah Lavine
2012-06-29 2:55 ` Nala Ginrut
2012-06-29 9:57 ` Ludovic Courtès
2012-07-02 1:44 ` Nala Ginrut
2012-07-02 19:16 ` Ludovic Courtès
2012-07-03 2:43 ` Nala Ginrut
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=CAPjoZofQOFmA-QkNA1C6mX+7D8XUph+kdpqty8UCmKzd6r11BQ@mail.gmail.com \
--to=nalaginrut@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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).