diff options
| author |  cwg <cwg@web> | 2011-08-29 12:35:19 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-08-29 12:35:19 +0000 |
| commit | b6758746f6433a46ac14bad58f9f6e0220a42e3e (patch) | |
| tree | 4fea91be52418d8260620bcb74b1c2d19200e8d0 | |
| parent | bbba6c19bd03f2b4a4ce8a38a2423c794826b1c5 (diff) | |
| -rw-r--r-- | doc/forum/advantages_of_SHA__42___over_WORM.mdwn | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/forum/advantages_of_SHA__42___over_WORM.mdwn b/doc/forum/advantages_of_SHA__42___over_WORM.mdwn new file mode 100644 index 000000000..b959db550 --- /dev/null +++ b/doc/forum/advantages_of_SHA__42___over_WORM.mdwn @@ -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*? |