From 955042a0bf491d1b2f48967999a01992056a397c Mon Sep 17 00:00:00 2001 From: atrent Date: Sat, 30 Nov 2019 20:37:00 +0000 Subject: [PATCH] Added a comment: no collisions --- ...2_f0325cefa5cd53a5a897046606137cef._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/internals/comment_12_f0325cefa5cd53a5a897046606137cef._comment diff --git a/doc/internals/comment_12_f0325cefa5cd53a5a897046606137cef._comment b/doc/internals/comment_12_f0325cefa5cd53a5a897046606137cef._comment new file mode 100644 index 0000000000..fe35b66fa2 --- /dev/null +++ b/doc/internals/comment_12_f0325cefa5cd53a5a897046606137cef._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="atrent" + avatar="http://cdn.libravatar.org/avatar/6069dfebff03997460874771defa0fa4" + subject="no collisions" + date="2019-11-30T20:37:00Z" + content=""" +I can confirm that these are not collisions: these identical files are the same photos with different names, shame on Dropbox syncing from my smartphone. I was actually hoping to dedupe through git-annex ;-) + +Some more questions/suggestions/conversation-starters: + +* I suppose I can dedup them with rdfind (i.e., hardlinking identical files), do you foresee any side effects? + +* may I change the hash function of git-annex to something not depending on filenames? (I suppose so, I'll have a look at the docs) + +* if I can change the hash function can I regenerate the whole annex without re-creating it? (again I'll have a look at docs) + +Thanks +"""]]