summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-03-09 13:14:27 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-03-09 13:14:27 -0400
commit1240fae12a81d3441028e54362dff377ecf5cf2a (patch)
tree56ff68b83303e412687fa1dad0f84591211bdb0f
parent6bfe4583b9b598f91deb83d72a1e986eba3fabbf (diff)
close
-rw-r--r--doc/bugs/hash_changed.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bugs/hash_changed.mdwn b/doc/bugs/hash_changed.mdwn
index cb1c1eefe..44f2d2eba 100644
--- a/doc/bugs/hash_changed.mdwn
+++ b/doc/bugs/hash_changed.mdwn
@@ -25,3 +25,8 @@ The problem was on several disks, different manufacturer, different disk size, e
I use annex for years now, never had a problem with it. It is one of the most awesome pieces of software I've seen in the last 10 years, though I only use a really small part of it. Sometimes it bugs me a little that it consumes quite a lot of memory on large repositories, though most of the time this is not an issue for me.
+> I think this was not a bug in hashing, just a corrupted file that
+> spread to several repositories. More recent git-annex versions checksum
+> files after transfer so detect the problem.
+>
+> Since it was resolved to reporter's satisfaction, [[done]] --[[Joey]]