https://bugs.documentfoundation.org/show_bug.cgi?id=125401
Miklos Vajna <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #2 from Miklos Vajna <[email protected]> ---
I'm not sure what to fix here. My understanding is that ~all software has this
best practice, that if you overwrite a large file, then first you write to a
tmp file next to the final target, and once you're done, you delete the
original and move the tmp file to the final destination.
Sure, if really wanted we can keep this for Windows only where we have
ReplaceFileW(), but I would rather close this as wontfix.
References:
- https://lwn.net/Articles/682721/ "the standard POSIX atomic-overwrite trick
(write to temporary file in same directory, rename over the top)"
- GLib's g_file_set_contents() does the same
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
