From: Andreas Schwab <schwab@suse.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
axboe@kernel.dk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] Include header required for INT_MAX
Date: Mon, 12 Nov 2007 13:06:50 +0100 [thread overview]
Message-ID: <je1wav3bxh.fsf@sykes.suse.de> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711120551380.23072@localhost.localdomain> (Robert P. J. Day's message of "Mon\, 12 Nov 2007 05\:51\:54 -0500 \(EST\)")
"Robert P. J. Day" <rpjday@crashcourse.ca> writes:
> On Mon, 12 Nov 2007, Andreas Schwab wrote:
>
>> Jan Engelhardt <jengelh@computergmbh.de> writes:
>>
>> > No, because I be damn sure that some developers try compiling programs
>> > in non-linux environments (cygwin, solaris, andyourpersonaldistro, you
>> > name it) which do not have to adhere to <limits.h>. It might use
>> > <cosmiclimits.h> instead, or whatever.
>>
>> Every C compiler has <limit.h>.
>
> i'm assuming you mean <limits.h>, no?
Yes, sorry for the typo.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-11-12 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 22:52 Jan Engelhardt
2007-11-12 10:21 ` Peter Zijlstra
2007-11-12 10:46 ` Andreas Schwab
2007-11-12 10:51 ` Robert P. J. Day
2007-11-12 12:06 ` Andreas Schwab [this message]
2007-11-12 12:57 ` Vegard Nossum
2007-11-12 13:37 ` Jan Engelhardt
2007-11-12 20:50 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2007-11-10 14:55 Thomas Koeller
2007-11-10 15:56 ` Christoph Hellwig
2007-11-11 0:52 ` Thomas Koeller
2007-11-10 16:48 ` Alexander E. Patrakov
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=je1wav3bxh.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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
all inboxes | Powered by JetHome®