From 78ce8fc01c351c94e957242299812869185d6687 Mon Sep 17 00:00:00 2001 From: Kalle Date: Thu, 31 Mar 2016 21:22:22 +0000 Subject: [PATCH] Added a comment: Had what I believe to be the same issue --- ...ment_3_b2a029fc9f4765633ef5393fe091016e._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/direct_cripple_mode_crippled_my_other_non-crippled_repos/comment_3_b2a029fc9f4765633ef5393fe091016e._comment diff --git a/doc/bugs/direct_cripple_mode_crippled_my_other_non-crippled_repos/comment_3_b2a029fc9f4765633ef5393fe091016e._comment b/doc/bugs/direct_cripple_mode_crippled_my_other_non-crippled_repos/comment_3_b2a029fc9f4765633ef5393fe091016e._comment new file mode 100644 index 0000000000..36555e30dd --- /dev/null +++ b/doc/bugs/direct_cripple_mode_crippled_my_other_non-crippled_repos/comment_3_b2a029fc9f4765633ef5393fe091016e._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="Kalle" + subject="Had what I believe to be the same issue" + date="2016-03-31T21:22:21Z" + content=""" +[[Podcast_filename_encoding_breaks_Android_client/]] + +The problem for me was that the podcatcher setup would automatically download new dangerous files and wipe all repos... My workaround in the end was to use ``--template`` to create date only filenames for podcasts. A solution I still use but it's rather inconvenient as more descriptive filenames are useful. + +This is quite a dangerous bug as all you need is a direct mode repo and an unusual filename for your whole annex cluster to empty itself. It can be saved by git surgery but unless being very careful you just end up syncing the bad filename back from a repo or another. + + +"""]]