diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-05-10 17:15:27 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-05-10 17:15:27 -0400 |
| commit | 62042866a105885f978540749cbb5de0815fc28a (patch) | |
| tree | 520781d651eb41979642d0b10a793e86d9f5d33a | |
| parent | b439a47af9046d4cd3380a6d9d253651109b80fa (diff) | |
close; done in v6 mode
| -rw-r--r-- | doc/todo/use_inode_cache_in_unlocked_files.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/todo/use_inode_cache_in_unlocked_files.mdwn b/doc/todo/use_inode_cache_in_unlocked_files.mdwn index adf2bc3dd..572d80ec6 100644 --- a/doc/todo/use_inode_cache_in_unlocked_files.mdwn +++ b/doc/todo/use_inode_cache_in_unlocked_files.mdwn @@ -21,3 +21,13 @@ direct mode, the worst that can happen in this case is probably that a modified file doesn't get added and committed. But, using the inode cache for unlocked files would result in any such modified versions being thrown away when the file is added, which is much more data lossy.. + +> This bug was regarding v5 unlock/lock. In v6 mode, locking a +> file doesn't need to rechecksum it; the key is pulled out of the +> associated files database, and the inode cache is used to detect if the +> unlocked file has been modified and so avoid data loss. +> +> So, this is [[done]] but only for v6 mode. I don't think I want to +> backport it to v5 mode though; it fell out naturally as a consequence of +> v6 mode, but to support it in v5 mode would be a lot more work. +> --[[Joey]] |