From: Andy Wingo <wingo@pobox.com>
To: rixed@happyleptic.org
Cc: guile-user@gnu.org
Subject: Re: Now that SCM type is a union...
Date: Thu, 15 Sep 2011 12:54:15 -0700 [thread overview]
Message-ID: <87hb4da8ew.fsf@pobox.com> (raw)
In-Reply-To: <20110812124436.GA2223@ccellier.rd.securactive.lan> (rixed@happyleptic.org's message of "Fri, 12 Aug 2011 14:44:36 +0200")
On Fri 12 Aug 2011 05:44, rixed@happyleptic.org writes:
> Between stable-2.0 and master a patch changed the C representation
> of the SCM type so that it is now a union.
As a result of this constant-expression issue, I have reverted those
patches. Now `master' uses the same SCM representation as 2.0.
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-09-15 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 12:44 Now that SCM type is a union rixed
2011-08-13 5:26 ` Ken Raeburn
2011-08-13 10:40 ` rixed
2011-08-13 12:23 ` Andy Wingo
2011-08-13 22:00 ` Ken Raeburn
2011-08-14 20:10 ` Andy Wingo
2011-08-15 2:04 ` Ken Raeburn
2011-08-15 2:21 ` Ken Raeburn
2011-09-15 19:54 ` Andy Wingo [this message]
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=87hb4da8ew.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=rixed@happyleptic.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).