From: Shawn Pearce <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 0/7] Various sp/mmap improvemnts
Date: Sun, 24 Dec 2006 00:54:27 -0500 [thread overview]
Message-ID: <20061224055427.GD7443@spearce.org> (raw)
Small improvements on top of my sp/mmap branch:
[PATCH 1/7] Rename gitfakemmap to git_mmap.
[PATCH 2/7] Switch git_mmap to use pread.
These two might apply right to master as-is and aren't
necessarily part of my sp/mmap topic.
[PATCH 3/7] Ensure packed_git.next is initia...
[PATCH 4/7] Default core.packdGitWindowSize ...
[PATCH 5/7] Don't exit successfully on EPIPE...
[PATCH 6/7] Release pack windows before repo...
[PATCH 7/7] Replace mmap with xmmap, better ...
These apply on top of my sp/mmap topic and some also assume
the 1/7,2/7 patches above to git_mmap were already applied.
1/7-5/7 were suggested by comments on the mailing list. Two I just
forgot to implement (6/7, 7/7) prior to submitting the original
series.
--
Shawn.
reply other threads:[~2006-12-24 5:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061224055427.GD7443@spearce.org \
--to=spearce@spearce.org \
--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).