From d95c075ae432aa9a9db7f8ffd9e438393763944c Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 5 Mar 2014 18:02:08 +0000 Subject: [PATCH] Added a comment --- ...comment_5_b426c4569b7a788fbf963f787590e051._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment diff --git a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment new file mode 100644 index 0000000000..c50d75476a --- /dev/null +++ b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.146" + subject="comment 5" + date="2014-03-05T18:02:08Z" + content=""" +Well, the easy way, assuming that you don't need the extension in the key at all, is to run `git annex migrate --backend=SHA512 *.cam` in both repositories. + +You can also play tricks with `git annex rekey`. I don't know if I'd recommend doing so. +"""]]