From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, msysgit@googlegroups.com,
Johannes Sixt <j6t@kdbg.org>
Subject: [PATCH 0/5] Various fixes for Windows
Date: Thu, 20 May 2010 20:57:50 +0200 [thread overview]
Message-ID: <cover.1274380838.git.j6t@kdbg.org> (raw)
Here are some unrelated patches that I had accumulated over the past
weeks that improve the git experience on Windows.
The first three are maint-worthy and have been cooked long enough.
IMO it is safe to put them on maint directly.
Erik Faye-Lund (1):
mingw: use _commit to implement fsync
Ian McLean (1):
Fix "Out of memory? mmap failed" for files larger than 4GB on Windows
Johannes Sixt (1):
Recent MinGW has a C99 implementation of snprintf functions
René Scharfe (1):
Fix checkout of large files to network shares on Windows XP
bert Dvornik (1):
start_command: close cmd->err descriptor when fork/spawn fails
Makefile | 1 -
compat/mingw.c | 17 +++++++++++++++++
compat/mingw.h | 5 ++++-
compat/win32mmap.c | 6 +++---
run-command.c | 2 ++
t/t5516-fetch-push.sh | 2 +-
t/t5705-clone-2gb.sh | 12 +++++++++---
7 files changed, 36 insertions(+), 9 deletions(-)
next reply other threads:[~2010-05-20 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 18:57 Johannes Sixt [this message]
2010-05-20 18:57 ` [PATCH 1/5 maint] Fix "Out of memory? mmap failed" for files larger than 4GB on Windows Johannes Sixt
2010-05-20 18:57 ` [PATCH 2/5 maint] start_command: close cmd->err descriptor when fork/spawn fails Johannes Sixt
2010-05-20 18:57 ` [PATCH 3/5 maint] Fix checkout of large files to network shares on Windows XP Johannes Sixt
2010-05-20 18:57 ` [PATCH 4/5] mingw: use _commit to implement fsync Johannes Sixt
2010-05-20 18:57 ` [PATCH 5/5] Recent MinGW has a C99 implementation of snprintf functions Johannes Sixt
2010-05-20 23:13 ` [PATCH 0/5] Various fixes for Windows Junio C Hamano
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=cover.1274380838.git.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=msysgit@googlegroups.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).