From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: request reversion regarding scm_i_* removal
Date: Thu, 04 Sep 2008 21:31:25 +0200 [thread overview]
Message-ID: <87myinoghe.fsf@gnu.org> (raw)
In-Reply-To: 87od3agv4m.fsf@gnu.org
Hi,
ludo@gnu.org (Ludovic Courtès) writes:
> After discussion with Andy on IRC and looking for uses for `scm_i_' in
> Google's codesearch, I've become convinced that we'd better not make
> this change in 1.8 so that we don't break existing code. That means
> reverting these commits:
>
> bc566d672f0d21f1567b83ddd732e4089983a2a8 Fix `SCM_INTERNAL' with GCC 4.3.
> f0c64044d311ac31f491f959daf1b3a2163ee883 Add `SCM_INTERNAL' macro, use it.
>
> If nobody complains, I'll revert them in 1.8 by the end of the next
> week.
Done!
Ludo'.
prev parent reply other threads:[~2008-09-04 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:11 request reversion regarding scm_i_* removal Andy Wingo
2008-08-11 8:10 ` Ludovic Courtès
2008-08-18 18:36 ` Andy Wingo
2008-08-21 11:52 ` Ludovic Courtès
2008-08-30 19:28 ` Ludovic Courtès
2008-08-30 21:17 ` Neil Jerram
2008-08-31 10:24 ` Ludovic Courtès
2008-09-04 19:31 ` Ludovic Courtès [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=87myinoghe.fsf@gnu.org \
--to=ludo@gnu.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).