From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: Jason Riedy <ejr@EECS.Berkeley.EDU>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Use inttypes.h rather than stdint.h.
Date: Fri, 26 Jan 2007 07:55:06 +0100 [thread overview]
Message-ID: <45B9A5CA.1020801@fs.ei.tum.de> (raw)
In-Reply-To: <24182.1169759500@lotus.CS.Berkeley.EDU>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
Jason Riedy wrote:
> Older Solaris machines lack stdint.h but have inttypes.h.
> The standard has inttypes.h including stdint.h, so at worst
> this pollutes the namespace a bit.
my appologies for not researching enough. thanks for this correction.
cheers
simon
--
Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\
Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-01-26 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 21:11 [PATCH] Use inttypes.h rather than stdint.h Jason Riedy
2007-01-25 21:54 ` Randal L. Schwartz
2007-01-26 6:55 ` Simon 'corecode' Schubert [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45B9A5CA.1020801@fs.ei.tum.de \
--to=corecode@fs.ei.tum.de \
--cc=ejr@EECS.Berkeley.EDU \
--cc=git@vger.kernel.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 NNTP newsgroup(s).