From: Greg Troxel <gdt@ir.bbn.com>
Subject: Re: more machine support NetBSD - including x86-64
Date: 30 Nov 2004 08:57:23 -0500 [thread overview]
Message-ID: <rmiekibzbgc.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87zn104ay4.fsf@zip.com.au>
> Perhaps only the __ versions should be tested.
Maybe, but the plain ones do no harm and might be wanted for older
systems. I added the __'s.
Sure, that's fine to leave the un__ versions - if there is an issue
its with namespace pollution and defining them, not checking them
anyway. Thanks for applying this part of the patch.
(Someone else will need to review the rest of what you posted.)
OK. I don't fully grasp the details myself (no x86_64 hw).
--
Greg Troxel <gdt@ir.bbn.com>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-11-30 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 1:34 more machine support NetBSD - including x86-64 Greg Troxel
2004-11-27 19:51 ` Kevin Ryde
2004-11-29 18:33 ` Greg Troxel
2004-11-29 21:11 ` Kevin Ryde
2004-11-30 13:57 ` Greg Troxel [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=rmiekibzbgc.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.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).