This commit is contained in:
parent
bbba6c19bd
commit
b6758746f6
1 changed files with 6 additions and 0 deletions
6
doc/forum/advantages_of_SHA__42___over_WORM.mdwn
Normal file
6
doc/forum/advantages_of_SHA__42___over_WORM.mdwn
Normal file
|
@ -0,0 +1,6 @@
|
|||
Thanks for creating git-annex.
|
||||
|
||||
I am confused about the advantages of the SHA* backends over WORM. The "backends" page in this wiki says that with WORM files "can be moved around, but should never be added to or changed". But I don't see any difference to SHA* files as long as the premise of WORM that "any file with the same basename, size, and modification time has the same content" is true.
|
||||
|
||||
Using "git annex unlock", WORM files can be modified in the same way as SHA* files.
|
||||
If the storage I use is dependable (i.e. I don't need SHA checksums for detection of corruption), and I don't need to optimize for the case that the modification date of a file is changed but the contents stay the same, is there actually any advantage in using SHA*?
|
Loading…
Reference in a new issue