diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2012-09-23 18:02:46 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2012-09-23 18:02:46 +0000 |
| commit | a3fa57a6a8cae10db8899424cc9cd0e036bfd058 (patch) | |
| tree | 894cb4e8967585c4d9b03eca1874e160e1400a2f | |
| parent | d4055b3dd2999a75381c4cae2ed30a7dcd32d3f2 (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_7_1724ffdf986301bf37ef7a6d16b6ea8a._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_7_1724ffdf986301bf37ef7a6d16b6ea8a._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_7_1724ffdf986301bf37ef7a6d16b6ea8a._comment new file mode 100644 index 000000000..eb26ab057 --- /dev/null +++ b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_7_1724ffdf986301bf37ef7a6d16b6ea8a._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.14.141" + subject="comment 7" + date="2012-09-23T18:02:45Z" + content=""" +If unannex makes the file a hard link to the annexed content, it will be mode 444 or so. But if the user changes the permissions and modifys it, that will corrupt the content still in the annex! + +So the current --fast behavior seems no worse than the proposed behavior. And it's not at all clear to me that this would be a better default behavior for unannex than the current behavior, which at least ensures that data left in the annex (and referred to by another annexed file) can be corrupted. +"""]] |