summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-04-28 20:47:36 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-04-28 20:47:36 -0400
commit6e95521b85263d9b734fa3f77030a96f850b1e1e (patch)
tree545a44efcd60dc06a9c2c0d0e69a93ce756d0296
parent8fcac59852e28c36c4512d5ee0a32ed76774aa2d (diff)
tweak
-rw-r--r--doc/bugs/Error_while_adding_a_file___34__createSymbolicLink:_already_exists__34__.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/bugs/Error_while_adding_a_file___34__createSymbolicLink:_already_exists__34__.mdwn b/doc/bugs/Error_while_adding_a_file___34__createSymbolicLink:_already_exists__34__.mdwn
index e94312774..21293af54 100644
--- a/doc/bugs/Error_while_adding_a_file___34__createSymbolicLink:_already_exists__34__.mdwn
+++ b/doc/bugs/Error_while_adding_a_file___34__createSymbolicLink:_already_exists__34__.mdwn
@@ -38,8 +38,8 @@ I think the right behavior here is to annex file2 just fine, as if they weren't
-- Asheesh.
> The same thing happens anytime the key for a file collides with a key
-> already in the annex, AFAICS. Including when the files have the same
-> content but are not hard links.
+> already in the annex, AFAICS. (Including when the files have the same
+> content but are not hard links... unless you're using WORM backend.)
>
> I've fixed this bug. The first file in wins. See commit for some
> interesting discussion about why it should not check for hash collisions