Skip to content

Commit 5d3c566

Browse files
committed
mingw: change core.fsyncObjectFiles = 1 by default
From the documentation of said setting: This boolean will enable fsync() when writing object files. This is a total waste of time and effort on a filesystem that orders data writes properly, but can be useful for filesystems that do not use journalling (traditional UNIX filesystems) or that only journal metadata and not file contents (OS X’s HFS+, or Linux ext3 with "data=writeback"). The most common file system on Windows (NTFS) does not guarantee that order, therefore a sudden loss of power (or any other event causing an unclean shutdown) would cause corrupt files (i.e. files filled with NULs). Therefore we need to change the default. Note that the documentation makes it sound as if this causes really bad performance. In reality, writing loose objects is something that is done only rarely, and only a handful of files at a time. Signed-off-by: Johannes Schindelin <[email protected]>
1 parent 4653d14 commit 5d3c566

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

compat/mingw.c

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2920,6 +2920,7 @@ int wmain(int argc, const wchar_t **wargv)
29202920

29212921
maybe_redirect_std_handles();
29222922
adjust_symlink_flags();
2923+
fsync_object_files = 1;
29232924

29242925
/* determine size of argv and environ conversion buffer */
29252926
maxlen = wcslen(wargv[0]);

0 commit comments

Comments
 (0)