mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
zardoz 2014-08-16 13:58:28 +00:00 • committed by admin
parent c5267cb543
commit d8a50f49ed
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_3_bda1e0d3569a6becf374d0e820219469._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="zardoz"
ip="78.48.163.229"
subject="comment 3"
date="2014-08-16T13:58:28Z"
content="""
One scenario where the above guarantee would be violated is when one
moves a new file of identical size, basename, and mtime, into a path
where a key-colliding file has been kept before. Still, I’d consider
this a scenario one could reasonably control for (especially in the
archive usecase); plus, even without manual control such a
move-induced collision would be much more unlikely than a collision of
basenames only.
"""]]