From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Thoughts about using inttypes.h
Date: Mon, 17 Feb 2003 12:42:51 -0600 [thread overview]
Message-ID: <87smumu4t0.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <xy71y27nlzq.fsf@nada.kth.se> (Mikael Djurfeldt's message of "Mon, 17 Feb 2003 13:13:29 +0100")
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
>> Anyone opposed?
>
> I'm not. It sounds excellent.
OK. I'll wait a bit longer for any other counter arguments, but if
there are none, I'll go ahead.
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-02-17 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 22:29 Thoughts about using inttypes.h Rob Browning
2003-02-17 12:13 ` Mikael Djurfeldt
2003-02-17 18:42 ` Rob Browning [this message]
2003-02-17 21:34 ` Mikael Djurfeldt
2003-02-18 17:26 ` Marius Vollmer
2003-02-18 17:34 ` Rob Browning
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=87smumu4t0.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).