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.)
I think that would be a great idea. If someone can tell me how to do that on Windows..
Note that even if you opened such a file, and made a change, and then saved it, this would at the worst result in a new commit being made. Other repositories that have a copy of the file would not lose their copy, at least not immediately (
git annex dropunused
might eventually remove it). So, to recover from such a mistake, it suffices to rungit annex undo $file
.