summaryrefslogtreecommitdiff
path: root/doc/forum/Crippled_FS__58___remove_read_perms_from_dropped_files__63___.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/Crippled_FS__58___remove_read_perms_from_dropped_files__63___.mdwn')
-rw-r--r--doc/forum/Crippled_FS__58___remove_read_perms_from_dropped_files__63___.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/Crippled_FS__58___remove_read_perms_from_dropped_files__63___.mdwn b/doc/forum/Crippled_FS__58___remove_read_perms_from_dropped_files__63___.mdwn
new file mode 100644
index 000000000..18dc2fe66
--- /dev/null
+++ b/doc/forum/Crippled_FS__58___remove_read_perms_from_dropped_files__63___.mdwn
@@ -0,0 +1,3 @@
+While experimenting with direct mode on Windows, I've got confused (and feeling momentary dread about apparent loss of data) many times when opening a file, and finding out that it in fact only contained the checksum; that is, was in the "dropped" state. As an **idea to prevent this confusion**, would it perhaps be possible to make the dropped files non-readable (permission denied) to the user somehow?
+
+(Background: I'm trying to build a version controlled development environment for a bunch of artists collaborating on large binaries, and making the process as fool-proof as possible is a priority.)