From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-124-g5f0d295
Date: Fri, 25 Mar 2011 19:45:39 +0100 [thread overview]
Message-ID: <874o6rdooc.fsf@gnu.org> (raw)
In-Reply-To: <m3hbarf4mz.fsf@unquote.localdomain> (Andy Wingo's message of "Fri, 25 Mar 2011 19:15:32 +0100")
Hi,
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?
[...]
> In short, it doesn't much matter to me :) We can program to the 7.x
> interfaces, and if people want to use old buggy software, then we tell
> them to upgrade. But if it keeps working, no problem, right?
Well, I think it’s an additional burden on us. GC bugs are hard to test
and debug as you know ;-), so if we add more variability, then we may
get stuck in a GC debugging loop.
Not to mention that 6.8 is slower.
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-03-25 18: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 [this message]
2011-03-27 15:23 ` Ludovic Courtès
2011-03-28 20:17 ` Neil Jerram
2011-03-28 20:45 ` Ludovic Courtès
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=874o6rdooc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).