From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] If NO_MMAP is defined, fake mmap() and munmap()
Date: Sat, 8 Oct 2005 01:57:35 +0200 [thread overview]
Message-ID: <20051007235735.GB14827@steel.home> (raw)
In-Reply-To: <7vwtkoyjs9.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano, Sat, Oct 08, 2005 01:44:22 +0200:
> > Since some platforms do not support mmap() at all, and others do only just
> > so, this patch introduces the option to fake mmap() and munmap() by
> > malloc()ing and read()ing explicitely.
>
> I guess I can just drop Alex Riesen patch and any other recent
> patches that try to work around mmap(). Happy!
>
Me too. I was just about to make a read_cache read the whole index in
(absolutely the same as Johannes, but not that elegant).
The platform(s) deserve such a treatment :)
prev parent reply other threads:[~2005-10-07 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 22:55 [PATCH] If NO_MMAP is defined, fake mmap() and munmap() Johannes Schindelin
2005-10-07 23:44 ` Junio C Hamano
2005-10-07 23:57 ` 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=20051007235735.GB14827@steel.home \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).