From: Steffen Prohaska <prohaska@zib.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, peff@peff.net, pclouds@gmail.com,
john@keeping.me.uk, schacon@gmail.com,
Steffen Prohaska <prohaska@zib.de>
Subject: [PATCH v5 0/4] Stream fd to clean filter; GIT_MMAP_LIMIT, GIT_ALLOC_LIMIT with git_parse_ulong()
Date: Sun, 24 Aug 2014 18:07:42 +0200 [thread overview]
Message-ID: <1408896466-23149-1-git-send-email-prohaska@zib.de> (raw)
Changes since v4: use git_parse_ulong() to parse env vars.
Steffen Prohaska (4):
convert: Refactor would_convert_to_git() to single arg 'path'
Change GIT_ALLOC_LIMIT check to use git_parse_ulong()
Introduce GIT_MMAP_LIMIT to allow testing expected mmap size
convert: Stream from fd to required clean filter instead of mmap
convert.c | 60 +++++++++++++++++++++++++++++++++++++++++++++------
convert.h | 10 ++++++---
sha1_file.c | 50 +++++++++++++++++++++++++++++++++++++++---
t/t0021-conversion.sh | 24 ++++++++++++++++-----
t/t1050-large.sh | 2 +-
wrapper.c | 16 ++++++++------
6 files changed, 138 insertions(+), 24 deletions(-)
--
2.1.0.8.gd3b6067
next reply other threads:[~2014-08-24 16:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 16:07 Steffen Prohaska [this message]
2014-08-24 16:07 ` [PATCH v5 1/4] convert: Refactor would_convert_to_git() to single arg 'path' Steffen Prohaska
2014-08-25 22:55 ` Junio C Hamano
2014-08-24 16:07 ` [PATCH v5 2/4] Change GIT_ALLOC_LIMIT check to use git_parse_ulong() Steffen Prohaska
2014-08-25 11:38 ` Jeff King
2014-08-25 15:06 ` Steffen Prohaska
2014-08-25 15:12 ` Jeff King
2014-08-24 16:07 ` [PATCH v5 3/4] Introduce GIT_MMAP_LIMIT to allow testing expected mmap size Steffen Prohaska
2014-08-24 16:07 ` [PATCH v5 4/4] convert: Stream from fd to required clean filter instead of mmap Steffen Prohaska
2014-08-25 12:43 ` Jeff King
2014-08-25 16:55 ` Steffen Prohaska
2014-08-25 18:35 ` Junio C Hamano
2014-08-26 18:00 ` Jeff King
2014-08-26 19:32 ` Junio C Hamano
2014-08-26 17:54 ` Jeff King
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=1408896466-23149-1-git-send-email-prohaska@zib.de \
--to=prohaska@zib.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=schacon@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).