From: Alex Riesen <raa.lkml@gmail.com>
To: Morten Welinder <mwelinder@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: use result of open(2) to check for presence
Date: Thu, 5 Jan 2006 19:07:15 +0100 [thread overview]
Message-ID: <20060105180715.GA6112@steel.home> (raw)
In-Reply-To: <118833cc0601050845i40f93bbajdd70e77953d07014@mail.gmail.com>
Morten Welinder, Thu, Jan 05, 2006 17:45:27 +0100:
> Config files always tend to grow, but I do agree that 4GB config files stretches
> credibility a bit.
>
> However, empty ones are not unlikely and then mmap will fail.
>
Shouldn't be a problem: the code in question does not seem to do
anything for empty files and wont even touch the result of mmap.
prev parent reply other threads:[~2006-01-05 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 11:43 use result of open(2) to check for presence Alex Riesen
2006-01-05 14:48 ` Morten Welinder
2006-01-05 15:12 ` Alex Riesen
2006-01-05 16:45 ` Morten Welinder
2006-01-05 18:07 ` Alex Riesen [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=20060105180715.GA6112@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mwelinder@gmail.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 NNTP newsgroup(s).