From: ludo@gnu.org (Ludovic Courtès)
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-124-g5f0d295
Date: Mon, 28 Mar 2011 22:45:06 +0200 [thread overview]
Message-ID: <87tyendlf1.fsf@gnu.org> (raw)
In-Reply-To: <87sju70zlj.fsf@ossau.uklinux.net> (Neil Jerram's message of "Mon, 28 Mar 2011 21:17:12 +0100")
Hello!
Neil Jerram <neil@ossau.uklinux.net> writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hello,
>>
>> A few more thoughts...
>>
>> Andy Wingo <wingo@pobox.com> writes:
>>
>>> On Fri 25 Mar 2011 18:58, ludo@gnu.org (Ludovic Courtès) writes:
>>>
>>>> "Andy Wingo" <wingo@pobox.com> writes:
>>>>
>>>>> bdw-gc 6.8 compatibility (hopefully)
>>>>
>>>> Aarrrgh. The intent has always been to support 7.x only (bdw-gc.h has
>>>> compatibility stuff for historical reasons), which is already enough
>>>> work. ;-) The README and various responses we posted in the past are
>>>> consistent.
>>>>
>>>> WDYT?
>>>
>>> I think we've been sending mixed messages.
>>
>> Again, I don’t think so.
>
> What is the current best recommendation for libgc to use?
7.x. Best recommendation would be 7.2, which fixes several bugs, but it
hasn’t been released yet, unfortunately.
> (Note in particular that Guile doesn't build with one of the most recent
> releases, 7.2alpha4.
Really? What’s the problem with this one?
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-03-28 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Q2qM7-0003oP-Oe@vcs-noshell.in.savannah.gnu.org>
2011-03-25 17:58 ` [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-124-g5f0d295 Ludovic Courtès
2011-03-25 18:15 ` Andy Wingo
2011-03-25 18:45 ` Ludovic Courtès
2011-03-27 15:23 ` Ludovic Courtès
2011-03-28 20:17 ` Neil Jerram
2011-03-28 20:45 ` Ludovic Courtès [this message]
2011-03-28 22:06 ` Neil Jerram
2011-03-28 21:01 Mike Gran
2011-03-29 11:59 ` 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=87tyendlf1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).