From 1f6cfecc972b121fa42ea80383183bbaccc2195a Mon Sep 17 00:00:00 2001
From: Joey Hess <joey@kitenet.net>
Date: Thu, 29 May 2014 15:23:05 -0400
Subject: remove old closed bugs and todo items to speed up wiki updates and
 reduce size

Remove closed bugs and todos that were least edited before 2014.

Command line used:

for f in $(grep -l '\[\[done\]\]' *.mdwn); do if [ -z $(git log --since=2014 --pretty=oneline "$f") ]; then git rm  $f; git rm -rf $(echo "$f" | sed 's/.mdwn$//'); fi; done
---
 ....0.1_references_on_remote_assistant_access.mdwn |   20 -
 doc/bugs/3.20121112:_build_error_in_assistant.mdwn |  432 ---
 ...ent_1_b42f40ffd83321ab5cc0ef24ced15e98._comment |    8 -
 ...ent_2_b1d2aa10ea84c5c370b3e76507fc8761._comment |  476 ---
 ...ent_3_b38e40d36bba95b16afbce68e7f25a80._comment |    8 -
 .../3.20121112_build_fails_on_Ubuntu_12.04.mdwn    |   97 -
 ...ent_1_ce2efd2196e7682f4cdbabdb0616d449._comment |    8 -
 ...ent_2_2a6faf662ebb85a8f1c89adcdfb9adb6._comment |   10 -
 ...ent_3_37f34baa34068def1adf794d0942e462._comment |    8 -
 ...ent_4_2f8a859fef9edc8eb93bf1cc74296702._comment |    8 -
 ...ror___39__not_in_scope_getAddBoxComR__39__.mdwn |   33 -
 ...on__44___because_testpack_won__39__t_build.mdwn |   57 -
 ...ent_1_b7140e2bf1ea9c73ecc9e214095968e7._comment |    8 -
 ...ent_2_6be87b2fb2ed828e7b4bf785729e910e._comment |    9 -
 doc/bugs/4.20130601_xmpp_sync_error.mdwn           |  125 -
 ...ent_1_5b50d97e44cbd5b31ff24537ec3f8603._comment |   14 -
 doc/bugs/400_mode_leakage.mdwn                     |   25 -
 ...r_repository_on_USB_drive_causes_sync_loop.mdwn |   22 -
 ...ent_1_81839a6de7450734ee75b51e47a0898e._comment |   10 -
 ...ent_2_907ce31a31df94984c2bd7aaafe5b10b._comment |    8 -
 ...ent_3_d8a86ae0ae5fa1f91e0b40b8b2ba0406._comment |   10 -
 ...ent_4_1f08fd5dd4f5d8723c2b5391cc3b60f9._comment |   22 -
 ...a_bare_repository_next_to_the_existing_one.mdwn |   21 -
 ...ent_1_cb781d34889d583663e855c4074f8e0e._comment |   16 -
 ...ent_2_c0c87957d7c7a09664e60571a2ca0e8c._comment |   12 -
 ...ing_box.com_remote_on_Android_fails_for_me.mdwn |   20 -
 ...ent_1_0303ce880415d7e043533551c2b24694._comment |   10 -
 doc/bugs/Adding_git_ssh_remote_fails.mdwn          |   32 -
 ...ent_1_05c0bd9ac7c6f0045217fd72fc1f0a1b._comment |   10 -
 ...ent_2_df05456cafdd89e8ceea830199f42d45._comment |   10 -
 ...ng_second_remote_repository_over_ssh_fails.mdwn |   41 -
 ...ent_1_308d5f517bf00c8edc53db438de52355._comment |   14 -
 ...ve_in_webapp_gives_internal_server_error__.mdwn |   69 -
 doc/bugs/Addurl_with_quvi_not_working.mdwn         |   74 -
 ...ng_to_a_specific_directory_on_a_USB_remote.mdwn |   30 -
 ...ent_1_13ecedfbb34c3564af3a790b8bf0f591._comment |   25 -
 ...ils_with___34__Internal_Server_Error__34__.mdwn |   22 -
 ...ent_1_91787407727f7ed833d5970d3226d0cb._comment |    8 -
 ...ent_2_f4c52fe33e9c4c107c2469fabb0c6826._comment |   10 -
 ...ent_3_20c1f9399321dd85cb584b8845140b1d._comment |    8 -
 ...ent_4_d92c30061e087878a2462b5a2e495346._comment |   12 -
 ..._34___in_the_Dashboard_seems_to_do_nothing.mdwn |   24 -
 ...ent_1_a9b03d4f4760fea2754a4dc93547f0a3._comment |   10 -
 ...ent_2_015e859a16b1ce4c0c7601df0594d555._comment |   10 -
 ..._when_submitting_jabber_user_and_password..mdwn |   20 -
 ...ent_1_c973032e0b780bd3b26bf1f744f04082._comment |   22 -
 ...ent_2_9ef5c13a7a28e9098a837d42e5c4c964._comment |   10 -
 ...ent_3_0c8087dfbcd8811913e7b3b6376cab90._comment |   12 -
 ...ent_4_8ad9047dd136e3b438fb9a6d50ecb04c._comment |    8 -
 ...ent_5_5f478c24065fc9a50a1cff3148b83bec._comment |   20 -
 ...-annex_does_not_support_XMPP_pairing__34__.mdwn |   26 -
 ...ent_1_c034bb84e58b2dda1038ba205ec78c56._comment |  273 --
 ...ent_2_99a754f41d59fdd401ba6d169945e7c9._comment |    8 -
 .../Android_app_permission_denial_on_startup.mdwn  |   18 -
 ...nt_10_dc06737997c8883ef0a12dbecd9ac30f._comment |    8 -
 ...nt_11_b444cd6717658116533745c51481dd3d._comment |    8 -
 ...nt_12_66181f34ed7496d1f6601b39e5ae3c65._comment |   13 -
 ...ent_1_ddf5761bf14de30ac97030ad338601ae._comment |   14 -
 ...ent_2_8b9fafa73ebf5f803c7da9531cfb5b34._comment |   10 -
 ...ent_3_58501bb043b4c5836d7472ffd6baa72c._comment |   23 -
 ...ent_4_d3a04dc7bbc1816cccc8d85c73ffb689._comment |    8 -
 ...ent_5_eeabbc0cc434ed84c36a3f4e03fcef36._comment |   10 -
 ...ent_6_4203b496bee1bdd424466ed63b5d31cf._comment |   10 -
 ...ent_7_74373eb2cc46b76659e3c463d6682d15._comment |   10 -
 ...ent_8_0923d2a09df01d152ec4784c92689c96._comment |    8 -
 ...ent_9_b60928e54a5b620899cf29820b9b8e70._comment |   10 -
 doc/bugs/Android_daily_build_missing_webapp.mdwn   |   23 -
 ...version_apparently_unable_to_run_sha256sum.mdwn |   27 -
 ...ent_1_51316a0a0d80cf8f9ee37b2eca64323d._comment |   12 -
 ...ent_2_14341ee188b1248f68164b1d9aa4c929._comment |   11 -
 ...ent_3_8624567ebc3af967fb59bad5a3fb6659._comment |  367 --
 ...ent_4_84aed89077d339f5471f113a1bcc4306._comment |   12 -
 ...ent_5_e1e6707042e52a1f07276c27af651339._comment |   10 -
 ...ent_6_f28f65901c46d9543797f698b0eedb63._comment |    8 -
 ...nnex_thinks_file_exists_afer_being_dropped.mdwn |   27 -
 ...ent_1_1d100441fd1ef529eb854b350fece9ee._comment |   29 -
 ...ent_2_166c459c2b27859cf457e17da685fe75._comment |   14 -
 ...ent_3_9d985b6e7973bfaaf8b4f5349d8c13ee._comment |    8 -
 ...ent_4_3e084cff454b95c7170c0225a53f0c30._comment |   11 -
 ...ed_files_into_git_until_daily_sanity_check.mdwn |  106 -
 ...__t_actually_sync_file_contents_by_default.mdwn |   16 -
 ...ent_1_8577fdaa4d49e6241c4372b159694c9c._comment |   12 -
 ...ent_2_027521e48283c68b39315bb8213f6e45._comment |   10 -
 ...ent_3_fd8f6938596aace60b04fb35c4069e37._comment |   10 -
 ...ent_4_ca908021ab5a2a50fd0d4a7e8d12498f._comment |    9 -
 ...ent_5_73532556cfc354ad5f37a3f3a048fb32._comment |   12 -
 ...ent_6_ced397b9e6119a0798a282ee07e885df._comment |   61 -
 ...ent_7_8acb66850e5db8337cf3f2b2dd236ccc._comment |   10 -
 ...ent_8_7eb530851ae6fa1a69813725c4e8fcec._comment |   59 -
 ...ent_9_c7d51a26e1febc3894d02546940d64e5._comment |   19 -
 ...es_it_has_just_transferred_elsewhere_again.mdwn |   26 -
 ...oop_and_eats_up_all_of_RAM_after_X_restart.mdwn |   24 -
 ...ssistant_lost_dbus_connection_spamming_log.mdwn |   88 -
 ...nt_10_b47d543e06a1a243211a2fa0cb5d09a3._comment |   13 -
 ...nt_11_399c1e4455dce105df95414fe3ff939d._comment |    8 -
 ...nt_12_1cfdd76e751ee3726bd80359cfc85c47._comment |    8 -
 ...nt_13_37aa5274874242861dc128efa1d29486._comment |   12 -
 ...ent_1_27fc71cadcbe6d5f146ffdb72b64689a._comment |   12 -
 ...ent_2_0fb01ff463e7da6df2864186dc28f8e4._comment |   12 -
 ...ent_3_10fa5082909f5e568623cf6d901d5161._comment |   11 -
 ...ent_4_f4e0fa25b7f466228622a6da02b157e7._comment |   24 -
 ...ent_5_6b9b87bfb8b94171b3dba51919fd1ceb._comment |   10 -
 ...ent_6_51f35f069c95a5ea7bd4dbab47b5702b._comment |   10 -
 ...ent_7_691661d902acbf9c11d713541d5d39e4._comment |    8 -
 ...ent_8_ef559feb7b350f2014055680d087c2bc._comment |   10 -
 ...ent_9_278b41aaa73a214b2b38881242a29b17._comment |   12 -
 ...in_some_cases__44___although_used_remotely.mdwn |   29 -
 ...hen_adding__47__creating_repo_on_ArchLinux.mdwn |   75 -
 ...nt_10_ec4a7388ea7106a953f599b664b37f1d._comment |    8 -
 ...ent_1_6a60c23850a5e2a7bba355e1317abc69._comment |   13 -
 ...ent_2_90b6ed232b2917b9fe041532284e1212._comment |   10 -
 ...ent_3_5a89d79395d96c43d7d8a6fd9dc275f1._comment |  248 --
 ...ent_4_cdd26c71875428dbe3c100944a443d3f._comment |    9 -
 ...ent_5_76242f5d6c815acd5bd58213bd8bb0fe._comment |   10 -
 ...ent_6_10852171c0207ca61ea6df1082107353._comment |    8 -
 ...ent_7_73e8a5696709f8154e63693ba5e569c3._comment |   10 -
 ...ent_8_392fc344e5833b0eb665fcd38f956b7a._comment |    8 -
 ...ent_9_9f0fc19a7fcaf7a5827e59e1495cf8c9._comment |    8 -
 ...Assistant_uses_obsolete_GDU_volume_monitor.mdwn |   28 -
 ...nt_10_0e1db417a5815ea903c1f7ccd07308c4._comment |    8 -
 ...ent_1_28b0cfcba8902c9c16dbe6c4b07984c4._comment |   10 -
 ...ent_2_952b3f78da756ff5f89235db94bec67f._comment |   53 -
 ...ent_3_d86aba42d014c4b4f708dcb5fe86e055._comment |   10 -
 ...ent_4_9aaf296ef53da317d6dc6728705d5c56._comment |   16 -
 ...ent_5_0d5f8a05a1505660f7ff1bc4ac6ff271._comment |    8 -
 ...ent_6_3dfdfd49597c85575cb689adb70d2de6._comment |    8 -
 ...ent_7_943a446c60ed9d7d4f240ba7f00fe925._comment |    8 -
 ...ent_8_9563859850fb40b1cc2c20c516c12960._comment |   16 -
 ...ent_9_cf6221c585ee3dbf039bdaea71842d9b._comment |    9 -
 ...Auto_update_not_updating_to_newest_version.mdwn |   72 -
 ...ent_1_6f75569dc960ea5bc4d334b2b321ebf8._comment |   12 -
 ...ent_2_4f26cce07a9f37c79b166111db499ce1._comment |   11 -
 ...ent_3_585bfcaa655b0e838f9b66a241d5ffc2._comment | 2163 -----------
 ...ent_4_2705fbfd74652ab097ac48ec687517c7._comment |    8 -
 ...ent_5_ab1ee005dbd54e560ea6e3c716cc8f1b._comment |   70 -
 ...ent_6_8019fa061d74365ea72e32780d288eb4._comment |    8 -
 ...pgrades_should_be_cryptographically_signed.mdwn |    8 -
 ...ent_1_37ed871c82879a31c2d8cfc7d9736548._comment |   10 -
 ...ckup_repository_doesn__39__t_get_all_files.mdwn |   40 -
 ...ent_1_a486dc0f741e08d5bcf2fd1a6ecbdf05._comment |   12 -
 ...ch_on_Android___39__git_annex_webapp__39__.mdwn |   35 -
 ...ent_1_173393b0b3d2d8c622c0d8a2eaace421._comment |    8 -
 ...s_needs___39__hxt__39___added_-_3.20121127.mdwn |   36 -
 ...biguous_occurrence___96__callCommand__39__.mdwn |   74 -
 ...ent_1_3127b3c448888fdf70096f24c7cbfd3c._comment |   50 -
 doc/bugs/Build_error_on_Linux.mdwn                 |   29 -
 doc/bugs/Build_error_on_Mac_OSX_10.6.mdwn          |   11 -
 ...uld_not_find_module___96__Text.Blaze__39__.mdwn |  105 -
 ...not_find_module___96__Data.XML.Types__39__.mdwn |   82 -
 ...type_constructor_or_class___96__Html__39__.mdwn |  189 -
 ...r___126____47__bin_breaks_the_desktop_link.mdwn |   15 -
 ...ent_1_c0f0a2878070ed86900815c6b6a5fa5e._comment |    8 -
 ...ent_2_53f2de3d3993821d8502fd08a0fcce12._comment |    8 -
 doc/bugs/Building_on_OpenBSD.mdwn                  |   40 -
 ...ent_1_bec4a7253e851567cd47b96ceead5d91._comment |   10 -
 ...ent_2_4a37935080b86643ecda717fe17f8f87._comment |   18 -
 ...ent_3_2df229eb965189e2f7ea6dcd66cf68ca._comment |   24 -
 ...ent_4_d141c0bac92bdfbc8b95d532d032174c._comment |    8 -
 ...ent_5_8aba96ef58eb6954f1d15029e0dda9ed._comment |   10 -
 ...ent_6_82e6744e246fe5caa72081d4e921b168._comment |   11 -
 doc/bugs/Cabal_cannot_solve_dependencies.mdwn      |   36 -
 ...ent_1_1d41ac79867226dcb71f1c7b38da062d._comment |   21 -
 ...ent_2_50e72633a4462f6f6eb33d57b137fdcc._comment |   48 -
 ...ent_3_886f2d1f7c47a3973b8dc7d7c412289a._comment |   10 -
 doc/bugs/Cabal_dependency_monadIO_missing.mdwn     |   17 -
 ...ent_1_14be660aa57fadec0d81b32a8b52c66f._comment |   75 -
 ...ent_2_4f4d8e1e00a2a4f7e8a8ab082e16adac._comment |    8 -
 ...don__39__t_always_use__annex-rsync-options.mdwn |   35 -
 ...___34__git-annex_get__34___with_3.20111203.mdwn |   27 -
 ...__39__t_rename___34__here__34___repository.mdwn |   32 -
 .../Can__39__t_set_repositories_directory.mdwn     |   15 -
 ...ent_1_beb5d5b66a8d0fab12be44a7d877e9b0._comment |    8 -
 ...ent_2_366aa798a5e55350d32b63b31c19112b._comment |   19 -
 ...ent_3_812554d58ad9274a50b2a33d5f4d2ec3._comment |   10 -
 ...ent_4_bec5f147441ad18c97845b44c90c728b._comment |   28 -
 ...__39__t_set_up_rsync.net_repo_on_OS_X_10.9.mdwn |   26 -
 ...ent_1_91a961cfa5dd4d6f0e4abfbbcfb81e92._comment |   35 -
 ...ent_2_0b5266e31fe7014bd11ea164f8e4744e._comment |   12 -
 doc/bugs/Can__39__t_start_it_on_Debian_Wheezy.mdwn |   26 -
 ...o_rsync_remote_with_encryption__61__shared.mdwn |   54 -
 ...ent_1_ca7ec2041bbec330476fb040b1e66a92._comment |    8 -
 ...ent_2_c476847665a5320214721497d8fad15b._comment |    8 -
 .../Cannot_build_the_latest_with_GHC_7.6.1.mdwn    |   18 -
 ...ent_1_b25859c159d62f2e92b92f505535131b._comment |   14 -
 ...ent_2_4c9eab9120718457fdc1ae9051e44bca._comment |   16 -
 ...ent_3_61aec9801e1f76db4a286536ffacc3ed._comment |   12 -
 ...ent_4_6381ff0ea419831d9bbed27511cad1e9._comment |   16 -
 doc/bugs/Cannot_copy_to_a_git-annex_remote.mdwn    |   14 -
 ...nt_10_258a376cff4c62bc4be919322bb1bd88._comment |   10 -
 ...nt_10_d9b830a1fdea8760cb7da1d36b3cd34d._comment |   12 -
 ...ent_1_09d76e5f9480b9a35644a8f08790cd97._comment |   10 -
 ...ent_2_7b586c705a937d09a1b44bd6af2d4686._comment |    8 -
 ...ent_3_07dbd8f64982f1921077e23f468122cf._comment |   25 -
 ...ent_4_926fd494f0b27103a99083cd5d0702d5._comment |    8 -
 ...ent_5_80444a509cc340f5eb3cd08b193fd389._comment |   10 -
 ...ent_6_4c6b99cd67b4aa742da5101fb1b379f7._comment |    8 -
 ...ent_8_f45cdd2b6acc5f458b67539fced0e529._comment |   12 -
 ...ent_9_5a455dd14fb9d3ff408bb3f81e366c38._comment |   10 -
 ...__47__foo_not___126____47__bar__47____34__.mdwn |   29 -
 ...ent_1_6f7b5c164ff64f00b8814b2ee334709f._comment |   13 -
 ...ent_2_807ef1250237bf4426e3a24c1f9ba357._comment |   10 -
 doc/bugs/Check_for_minimum_Git_version.mdwn        |   41 -
 doc/bugs/Committer_crashed.mdwn                    |   32 -
 .../Compile_needs_more_than_1.5gb_of_memory.mdwn   |   16 -
 ...ent_1_0806b5132c55d7a5a17fbdad7e3f2291._comment |   16 -
 ...te_failure_trying_to_unannex_a_large_annex.mdwn |   56 -
 ...ent_1_1c202695ab7fe62cdc8770e1fb428d0c._comment |   10 -
 doc/bugs/Conflicting_archive_descriptions.mdwn     |   16 -
 ...ontrolPath_too_long_for_Unix_domain_socket.mdwn |   53 -
 ...ent_1_60f58e205604eebe668b1e05dcfbf9a7._comment |   24 -
 ...ent_2_9c0c65389a3b4e7e81b8de96d430a3f1._comment |    8 -
 doc/bugs/Could_not_find_module_Data.Default.mdwn   |   33 -
 doc/bugs/Could_not_resolve_dependencies.mdwn       |   40 -
 .../Crash_trying_to_sync_with_a_repo_over_ssh.mdwn |   43 -
 ...ent_1_9705f295ad8101f3f0ede18e590b56ef._comment |    8 -
 ...ent_2_0d751d81ac618f8d7e3f1dd20c830542._comment |    8 -
 doc/bugs/Crash_when_adding_jabber_account_.mdwn    |   32 -
 ...ent_1_2dc61ebcfa8919fb839656999c155c52._comment |   10 -
 ...ent_2_e49af3b8a937d82eda1509b6f67b21d4._comment |    8 -
 ...ent_3_e59f8813bf1a7c4e3c8c120fe82348b9._comment |   10 -
 ...ent_4_716ac138cb69eecd0fb586699b4aeb2a._comment |    8 -
 ...ent_5_9bfd8df548d5866599dfc69fb3aaf94a._comment |    8 -
 doc/bugs/Creating_a_box.com_repository_fails.mdwn  |   41 -
 ...ent_1_c0b4855b65cb7052daf6538c2ad73e99._comment |   11 -
 ...ent_2_b05a1e7b37989c698353cc6b3fd02d7c._comment |   12 -
 ...ent_3_6c3610fb95676592f17f36e4e1b09bd8._comment |    8 -
 ...ent_4_c9895712e72854e4b5ff7a58e82ae374._comment |   17 -
 ...ent_5_93981afe8162f64ebb9d8c2c6a7ef91e._comment |    8 -
 ...ent_6_752b5725b4596721438098d38af8fb66._comment |    8 -
 ...ent_7_73f71386f8eafbb65f4cc9769021710f._comment |   13 -
 ...ent_8_109e37051beb729834e05997c023b849._comment |    8 -
 ...y_with_an_invalid_name_throws_an_exception.mdwn |   18 -
 doc/bugs/DS__95__Store_not_gitignored.mdwn         |   26 -
 ...ent_1_b93ac0ea3be82c361ceb4352e742ba39._comment |    8 -
 ...ent_2_4136e1f4aba7aa7562dafcf6a213e10c._comment |   58 -
 doc/bugs/Detection_assumes_that_shell_is_bash.mdwn |   24 -
 ...ficult_to_troubleshoot_XMPP_login_failures.mdwn |   11 -
 ...ent_1_4205bccf515169031e4a9ed8e905262c._comment |   10 -
 ...mode_keeps_re-checksuming_duplicated_files.mdwn |   25 -
 ...ent_1_cb10385a4f046bfe676720ded3409379._comment |   14 -
 ...ent_2_4bcf1a897181e40c9c8969d597a844f0._comment |    8 -
 ...ent_3_6a6d22d218f036c9977072973ed99aa8._comment |   11 -
 ...ent_4_eaa7ffb3a1d9ffd6d89de301bd2cd5b2._comment |   11 -
 ..._repositories_end_up_with_unstaged_changes.mdwn |   46 -
 ...ent_1_300a2b246182be3079db20a7e3322261._comment |    8 -
 ..._between_git_annex_add_and_git_annex_watch.mdwn |   33 -
 doc/bugs/Displayed_copy_speed_is_wrong.mdwn        |    8 -
 ...ent_1_74de3091e8bfd7acd6795e61f39f07c6._comment |    8 -
 ...ent_2_8b240de1d5ae9229fa2d77d1cc15a552._comment |    8 -
 ...l_folder_suddenly_appear_in_sub-sub-folder.mdwn | 3747 --------------------
 ...ent_1_ae4a13ff121d27f78904eee9bf5e716b._comment |   20 -
 ...ent_2_32e360cd7b100ddb9a526e7833fc55e1._comment |   15 -
 ...ent_3_650dc9ede4e16ef668d96840f63dad47._comment |   12 -
 ...ent_4_721cf184fb5a5244ec5c15de3302ebf7._comment |   33 -
 ...e__44___versions_3.20120315_and_3.20120430.mdwn |   79 -
 ...ository:___34__internal_server_error__34__.mdwn |   28 -
 ...ent_1_9be1b577fa4d5fe9754845073fdf5d32._comment |   10 -
 ...ent_2_0da0d68b646f2b38be6ecf7c0fe13743._comment |    8 -
 ...ent_3_09c56f5574931f2ebe903069f0731160._comment |   16 -
 ...ent_4_0c127396e682ca6ced43aec7deeb0335._comment |   12 -
 ...ent_5_6bc3eadefde4750eec67a55de6651b2d._comment |   13 -
 ...ent_6_263ab9c1483438b1717c8061ac81a2fa._comment |    9 -
 ...ent_7_eccc10990dff37584f8e60cd481a7140._comment |   26 -
 ...ent_8_f897d20cbe5e0f3f58ce1a0bacad3d71._comment |    8 -
 ...dropping___34__hGetLine:_end_of_file__34__.mdwn |   31 -
 ...nt_10_8742f7ac27b5f4ad6261d04a174a691c._comment |   10 -
 ...nt_11_b8e720340000537de6713c49b7733b2f._comment |   21 -
 ...ent_1_489fa3a717519cd5d8b4c1a9d143d8c6._comment |    8 -
 ...ent_2_b0796d3b1913e1b6f7b34d75a591be42._comment |   16 -
 ...ent_3_d8ca17ccaa5ee48d590736af8e77d88a._comment |    8 -
 ...ent_4_aa7a690aaf75d21f52051a31d7fce70e._comment |    8 -
 ...ent_5_dc235dc2d024b7f340721bb578630e00._comment |   10 -
 ...ent_6_5d1e6ea5b5725c773acc6e288add812c._comment |    8 -
 ...ent_7_6389b4f03ebc916358bc6674398d70c4._comment |   14 -
 ...ent_8_bcacc9fb3751042968118ebe33802e27._comment |   10 -
 ...ent_9_6d4c9f0e133ebd94fc11346df446402e._comment |   16 -
 ...ing_annexed_file_to_a_.gitignored_location.mdwn |   21 -
 ...ent_1_b524e70156e8bc1219d5c6741974ad99._comment |   18 -
 ...ent_2_ff7349c396d1249204d621e71f6a7a52._comment |   10 -
 ...ent_4_4bc7d4c51faea3fdafc977cb66b7f73a._comment |   26 -
 ...__createSymbolicLink:_already_exists__34__.mdwn |   46 -
 ...ry_new_file_gets_symlinked_to_a_git_object.mdwn |   78 -
 ...ent_1_d4e7ed56b16494a95e6c904c746cc91f._comment |    8 -
 ...ent_2_656b2a2cc44e9102c86bdd57045549d5._comment |   10 -
 ...tory___40__calling_nonexistant_shell__41__.mdwn |   28 -
 ...ent_1_fb8a379ed7f4b88bd55245ce5b18042c._comment |    8 -
 ..._create_remote_repo_if_no_global_email_set.mdwn |   55 -
 ..._to_make_git_annex_add_not_ignore_dotfiles.mdwn |   14 -
 ...ent_1_c258016dd545b0426e75a7c0132154d8._comment |    8 -
 ...ent_2_c506f609390f8bf46433b67fc2a9ddf8._comment |    8 -
 .../Feature_request:___34__quvi__34___flag.mdwn    |   14 -
 ...ent_1_908c38024fd252328566034608c2dec3._comment |   12 -
 ...ent_2_4b6822fe91aa865f2ac1297a3daa3fca._comment |    8 -
 ...ent_3_c72ef77e76b1c99b5e0c78d0742080e7._comment |    8 -
 ...ent_4_6092695d6afb1608447afe6f86e6fb83._comment |    8 -
 doc/bugs/Finding_an_Unused_file.mdwn               |  152 -
 ..._or_xdg-open_on_linux__47__bsd__63____41__.mdwn |   26 -
 ...th_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn |   62 -
 doc/bugs/GPG_can__39__t_handle_some_files.mdwn     |   23 -
 ...ent_1_4388c971e991dbc0326e69c49994df1e._comment |    8 -
 doc/bugs/GPG_problem_on_Mac.mdwn                   |   34 -
 ...ent_1_9ccfa12e7a9569a7ae9a3b819917c275._comment |    9 -
 ...ent_2_a5e07131e2bc1a646c8439fc2506128b._comment |   29 -
 ...ent_3_388238360f2423f84881e904443efb86._comment |   12 -
 .../Git_annex_add_fails_on_read-only_files.mdwn    |   49 -
 ...ent_1_d31018e8bf31d729ee9fee43a0a07934._comment |   10 -
 ...ent_2_e38e7048749f890169cd0be602be6ee7._comment |   10 -
 ...annex_add_on_vfat__47__sdcard__47__android.mdwn |  280 --
 ...ent_1_2fc435d1c741f9fc422401f682e7c8b7._comment |   17 -
 ...ent_2_b73fb99a75aef912f8286626c5bde66d._comment |   14 -
 ...ent_3_b7115f2c658439ff59a029f500697fc1._comment |   57 -
 ...ent_4_67de7a56ddb06fc0e31cc011d281c633._comment |    8 -
 ...ent_5_58fdb2a00f1737746cdbc804f831a0e7._comment |    8 -
 doc/bugs/Hanging_on_install_on_Mountain_lion.mdwn  |   26 -
 ...nt_10_f57ff027b19ca16e2ecf1fc6aee9ef4a._comment |   10 -
 ...nt_11_2ff78d2090d0fd3418ab50b27c6028ce._comment |    8 -
 ...ent_1_523d3c0c71f80536850a001b90fd0e9e._comment |    8 -
 ...ent_2_6c360c64093b016c2150206dc3ad1709._comment |   10 -
 ...ent_3_7b77fd9b7dc236c345f2f6149c8138ee._comment |   18 -
 ...ent_5_08289596445d7588e43d35490fbfe5f4._comment |    8 -
 ...ent_5_2a336fe7b8aed07cbdaa868bd34078f9._comment |    8 -
 ...ent_6_ea7a40c3b6748738421aed00a6f7ca10._comment |   10 -
 ...ent_7_00962da9288976f8a48d0cbc08e1d9e2._comment |   15 -
 ...ent_8_5d53d23e529f33f6e7deb10643831613._comment |   11 -
 ...ent_9_f00c8761e3184975b6645c0c3e241365._comment |   10 -
 ...on_creating_repository_when_using_--listen.mdwn |   49 -
 ...ent_1_8cbe786de8cf8b407418149b9c811aab._comment |   14 -
 ...ent_2_dc128eeddeaaf3f84e71aca0fb7d341f._comment |    8 -
 ...ard_push_without_using_the_assistant__63__.mdwn |  295 --
 ...ent_1_0ddcbe0ccecdec1012964dfa436a3eee._comment |   19 -
 ...ent_2_5765b849bcf045ead9f007bd50b2cfbd._comment |   20 -
 ..._the_case_of_adding_an_existing_repository.mdwn |   28 -
 ..._symlink_path_in_simple_submodule_use_case.mdwn |   72 -
 ...ent_1_73b4dc5f90c8ba5634caee35cd31af1a._comment |   14 -
 ...ent_2_e84b93062c82453f18308a82ee270585._comment |   16 -
 .../Incorrect_version_on_64_Standalone_Build.mdwn  |   11 -
 ...ent_1_1964e4cad33a9f98b2eedbf095e899ff._comment |   12 -
 .../Install_of_git-annex-3.20121112_fails.mdwn     |   20 -
 ...ent_1_80fc80151d4390bd8a4332f30723962e._comment |    8 -
 ...ent_2_2613320a41a74dc757a3277c8c328bd0._comment |   62 -
 ...ent_3_c364764d0c56e8dc3cac276905d99841._comment |   10 -
 ...ent_4_f1057340dfa978071d3bbc9e2af1e612._comment |   19 -
 ...ent_5_9007b1a3abd647945604968db19cb841._comment |    8 -
 ...ent_6_0bb3ac5375f29ce9d3d0be93879267e3._comment |   11 -
 ...ent_7_ae4443b8cd069080d1f77fca16aa8b04._comment |   10 -
 ...x.com_repo_after_deleted_an_encrypted_one..mdwn |   28 -
 ...rnal_server_error_adding_USB_drive_on_OS_X.mdwn |   25 -
 ...ent_1_b2ef077d87a9da624f20649c21401b5b._comment |   17 -
 ...ent_2_ef849e25b0264808bff800d9d3836119._comment |   10 -
 ...ent_3_ae3cbd0eb69cbeb9b349e0060d056d43._comment |   18 -
 ...ent_4_0ff2897805928b14829b7b369a3aed91._comment |   16 -
 ...ent_5_414a45573aeb5201f4d80433955669d5._comment |   12 -
 ...e_can_cause_all_following_switches_to_fail.mdwn |   50 -
 ...put_broken_with___34__git_annex_sync__34__.mdwn |   21 -
 ...ent_1_380a49b3c132f9f529729a1cb5a69621._comment |    8 -
 ...ent_2_282f5f89fb4a46e1fad0980e0b2994a0._comment |    8 -
 ...ent_3_7ff98958146b7f6396226bdd878ec86e._comment |   10 -
 ...ent_4_f9e460a09e7e5f53c16c20ded2649201._comment |    8 -
 ...pp_not_supported_on_Debian_Wheezy_backport.mdwn |   12 -
 ...tant_daemon_leaves_ssh_mux_sessions_behind.mdwn |   38 -
 ...ent_1_17879b98a5e79ace03b543064751e46e._comment |    8 -
 ...ent_2_2dc877e281750004b16619ea7b931160._comment |    8 -
 ...ons_result_in_stale_symlinks_and_data_loss.mdwn |   57 -
 ...nt_10_52364dc5b1b43b51748453d1896e35c6._comment |    8 -
 ...nt_11_99b4db1841f8630a9c5efd08910e87a3._comment |  104 -
 ...ent_1_fbb410a54bb0bd82d0953ef58a88600e._comment |   24 -
 ...ent_2_8007c9ba42a951a4426255ec3c37d961._comment |   13 -
 ...ent_3_73ecd4cb8ee58a8dfe7cab0e893dbe5b._comment |    8 -
 ...ent_4_e8a10886a564f35414c30a04335d9d32._comment |    8 -
 ...ent_5_6a318edfe45c80343d017dc7b4837acb._comment |    8 -
 ...ent_6_f7a1d9f9d40aff531d873a95d2196edd._comment |    8 -
 ...ent_7_1724ffdf986301bf37ef7a6d16b6ea8a._comment |   10 -
 ...ent_8_5470e2f50e6506139ecb1b342371c509._comment |   10 -
 ...ent_9_e53148a9efa061a825f668a9492182f7._comment |   10 -
 ...wo_versions_didn__39__t_show_up_on_hackage.mdwn |   11 -
 ...ent_1_74b56dea2100450e322e726bb55bb310._comment |    8 -
 doc/bugs/Local_files_not_found.mdwn                |   50 -
 ...ent_1_5e1fcc0597594fa493ffa28aa32e1df8._comment |   12 -
 ...Local_pairing_fails:_received_PairMsg_loop.mdwn |   39 -
 ...ent_1_b8c485bafd98be8c21595597af361255._comment |    8 -
 ...ent_2_bc63489334f44a423645021415ffe196._comment |   10 -
 ...ent_3_6345b174d04b6613c2c55a6ec9e50c21._comment |   16 -
 ...ent_4_f39ec6c3d5a016b3c5260162c0b42177._comment |   12 -
 ...ent_5_ca0c5ef6e6a6d2c4b64430ac68370b6a._comment |    8 -
 doc/bugs/Log_rotation_loses_large_logs.mdwn        |   69 -
 doc/bugs/Lost_S3_Remote.mdwn                       |   59 -
 ...ent_1_6e80e6db6671581d471fc9a54181c04c._comment |   10 -
 ...ent_2_c99c65882a3924f4890e500f9492b442._comment |    8 -
 ...ent_3_1e434d5a20a692cd9dc7f6f8f20f30dd._comment |    8 -
 ...xist___40__No_such_file_or_directory__41__.mdwn |   37 -
 ...ent_1_6e50d721c624ad82e94c8e5e93b38783._comment |   13 -
 ...ent_2_07a22d9e9010a04ae0088ebfd4bbf4df._comment |   11 -
 ...ent_3_0b64e2dada87cd79fa584e86a00529ea._comment |    8 -
 doc/bugs/Makefile_is_missing_dependancies.mdwn     |   47 -
 ...ent_1_5a3da5f79c8563c7a450aa29728abe7c._comment |   47 -
 ...ent_2_416f12dbd0c2b841fac8164645b81df5._comment |    8 -
 ...ent_3_c38b6f4abc9b9ad413c3b83ca04386c3._comment |   25 -
 ...ent_4_cc13873175edf191047282700315beee._comment |   30 -
 ...ent_5_0a1c52e2c96d19b9c3eb7e99b8c2434f._comment |   59 -
 ...ent_6_24119fc5d5963ce9dd669f7dcf006859._comment |   10 -
 ...ent_7_96fd4725df4b54e670077a18d3ac4943._comment |   12 -
 ...ent_8_a3555e3286cdc2bfeb9cde0ff727ba74._comment |    8 -
 doc/bugs/Manual_mode_weirdness.mdwn                |   37 -
 ...ent_1_f8ab3bac9e9a6768e5fd5a052f0d920f._comment |    8 -
 ...ent_2_e810daa488fad32ca8bdaae620051da8._comment |    8 -
 doc/bugs/Matching_oddity_in_SafeCommand.hs.mdwn    |   28 -
 ...ent_1_1a51630c0791547a7e0b68eea5d81e4c._comment |    8 -
 ...t_6cecc26206c4a539999b04664136c6f785211a41.mdwn |   35 -
 ...weirdness_with_the_assistant_branch_on_OSX.mdwn |   15 -
 ...ent_1_377525e70640751e1ead445aeed15efa._comment |    8 -
 ...nt_git-annex_will_not_build_on_OpenIndiana.mdwn |   36 -
 ...ent_1_f3c336ecfee51e074ea3a9fc95301de5._comment |    8 -
 ...ent_2_102c0e998934e84deca92fd1c90145fa._comment |    8 -
 ...ent_3_1449dd796ce9f2209f085d4b017a5f33._comment |   19 -
 ...ent_4_c4aa8a4379b2c056ca9b7afcff412bbc._comment |   10 -
 ...ent_5_6ca4dd2ad51182edf7198f38b336b9b6._comment |    8 -
 ...me_scheme_does_not_follow_git__39__s_rules.mdwn |   31 -
 ...lly_install_c2hs_-_3.20121127_and_previous.mdwn |   37 -
 doc/bugs/No_progress_bars_with_S3.mdwn             |   26 -
 ...ent_1_33a601201a9fdd2357f1c03e32fa6b9c._comment |    8 -
 ...ent_2_52361805ced99c22d663b3b1e8a5b221._comment |    8 -
 ...ent_3_5903c1c40c4562f4fbaccd1640fedb18._comment |    8 -
 ...ent_4_80799c33e513384894b390fe34ab312a._comment |    8 -
 doc/bugs/No_version_information_from_cli.mdwn      |   18 -
 ...sarily_large_and_not_inherently_compressed.mdwn |   68 -
 ...OSX_alias_permissions_and_versions_problem.mdwn |   37 -
 ...ent_1_4fabe32e7e626e6ca23aa0b6f449c4c6._comment |   14 -
 ...ent_2_064d60fcc8366a70958540bc145e611a._comment |   11 -
 ...ent_3_6c72d4f40ea0a9566a1185901beff5ba._comment |   14 -
 ...ent_4_8a11f404bb72a1aeb2290744cce2d00d._comment |   12 -
 ...ent_5_30888607199d6a48b76d0c48f5aa4f64._comment |    8 -
 doc/bugs/OSX_build_broken.mdwn                     |   13 -
 ...ent_1_0b570aa6c58effeace2a989184c9c601._comment |   10 -
 ...app_error:__LSOpenURLsWithRole__40____41__.mdwn |   26 -
 ...ent_1_0dfa839f1ba689b23f811787515b8cff._comment |    8 -
 ...ent_2_612b947eb5474f6d792a833e33105665._comment |    8 -
 ...ent_3_549b8bcae6f1f8b21932b734e32fbdd1._comment |    8 -
 ...ent_4_23078dfea127fa3ef20696eb10ce964c._comment |   10 -
 ...ent_5_7da5ef8325b8787bbf1c6e2c17b1142e._comment |    8 -
 doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp.mdwn  |   31 -
 ...ent_1_2653fe701a1bb20254f3d6b90f10a43b._comment |   18 -
 ...ent_2_d9ce701d077e40f39b142ce2cc570a3b._comment |    8 -
 ...ent_3_14964ab68253dc1a8903d14a821b8b40._comment |   10 -
 ...ent_4_4a579e9a13305ab4157f4b3eba46b92d._comment |   16 -
 ...ent_5_2a710960dc3a177ce62ef92f8546c496._comment |   12 -
 ...ent_6_a4ad73530cd0f6621bcc6394d5f39af7._comment |   41 -
 ...rver_Error_when_push.default___61___simple.mdwn |   67 -
 ...ent_1_971224d2c0c0ce8d4530b1991508f849._comment |   12 -
 ...ent_2_6866f96277dbe83a8aadcdeb426b6750._comment |    8 -
 ...ent_3_eaed9b5532e30e401f50193a72b98310._comment |   13 -
 ...ent_4_1fab407f3823ce8cec87f5df55e49f8c._comment |    8 -
 ...emote__44___but_believes_it_has_succeeded..mdwn |  180 -
 ...__wget_is_not_used__44___even_if_available.mdwn |   67 -
 doc/bugs/Partial_direct__47__indirect_repo.mdwn    |   24 -
 ...ent_1_42344fce051d759f95215c985e9d1135._comment |   12 -
 ...ent_2_8ba64f2750d0ef4adf595674c723bc65._comment |    8 -
 ...ent_3_bd4985864b7dcd70a609ca7bc2617e4a._comment |    8 -
 ...tus___39__typechange__39___and_direct_mode.mdwn |   32 -
 ...ent_1_84cb8c651584ec2887f6e1b7dc107190._comment |    8 -
 ...ommand_now_asks_for_a_commit_message__34__.mdwn |   18 -
 doc/bugs/Problem_when_dropping_unused_files.mdwn   |   21 -
 ...nt_10_d4f6bfe8e04560fc661a47b09ed8a5f4._comment |    8 -
 ...ent_1_e1a99bd3eb8b3186653b52a52b1836de._comment |   10 -
 ...ent_2_dec3e5ffe5cfdc439f418ee00d7d9810._comment |    8 -
 ...ent_3_d106a87101db52f957da84d90dafcdbb._comment |   12 -
 ...ent_4_f28ed0635612693e437e64d872af5c37._comment |    8 -
 ...ent_5_f0237075653768c84deb702442645f28._comment |    8 -
 ...ent_6_b509006e1590480a104627369bc910f2._comment |    8 -
 ...ent_7_fe261c074211ccb94bbcb32cfd8ee654._comment |   14 -
 ...ent_8_bc8e4dc7e0d6577ba5fcc98f56627b1f._comment |    8 -
 ...ent_9_e9a22aa2ebcde5f6595b49dba9375761._comment |   14 -
 doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn   |   52 -
 doc/bugs/Problems_building_on_Mac_OS_X.mdwn        |   62 -
 ...ent_1_1c199b826fdd84b5184b1466ad03a9a4._comment |    8 -
 doc/bugs/Problems_running_make_on_osx.mdwn         |   49 -
 ...nt_10_94e4ac430140042a2d0fb5a16d86b4e5._comment |    8 -
 ...nt_11_56f1143fa191361d63b441741699e17f._comment |    8 -
 ...nt_12_ec5131624d0d2285d3b6880e47033f97._comment |    8 -
 ...nt_13_88ed095a448096bf8a69015a04e64df1._comment |   16 -
 ...nt_14_89a960b6706ed703b390a81a8bc4e311._comment |    8 -
 ...nt_15_6b8867b8e48bf807c955779c9f8f0909._comment |   71 -
 ...nt_16_5c2dd6002aadaab30841b77a5f5aed34._comment |    8 -
 ...nt_17_62fccb04b0e4b695312f7a3f32fb96ee._comment |   43 -
 ...nt_18_64fab50d95de619eb2e8f08f90237de1._comment |   24 -
 ...nt_19_4253988ed178054c8b6400beeed68a29._comment |   11 -
 ...ent_1_34120e82331ace01a6a4960862d38f2d._comment |   17 -
 ...nt_20_7db27d1a22666c831848bc6c06d66a84._comment |   10 -
 ...ent_2_cc53d1681d576186dbc868dd9801d551._comment |    8 -
 ...ent_3_68f0f8ae953589ae26d57310b40c878d._comment |   57 -
 ...ent_4_c52be386f79f14c8570a8f1397c68581._comment |   12 -
 ...ent_5_7f1330a1e541b0f3e2192e596d7f7bee._comment |  107 -
 ...ent_6_0c46f5165ceb5a7b9ea9689c33b3a4f8._comment |    9 -
 ...ent_7_237a137cce58a28abcc736cbf2c420b0._comment |   22 -
 ...ent_8_efafa203addf8fa79e33e21a87fb5a2b._comment |    8 -
 ...ent_9_cc283b485b3c95ba7eebc8f0c96969b3._comment |   66 -
 doc/bugs/Problems_with_syncing_gnucash.mdwn        |  568 ---
 ...ent_1_ca195af3ba4a286eb5ab687634192fa4._comment |    8 -
 ...ent_2_754fb430381ad88e6248ecb902b32118._comment |   20 -
 ...ent_4_25881998c6f149c70b1358f37b7c66ba._comment |   20 -
 doc/bugs/Provide_64-bit_standalone_build.mdwn      |    6 -
 ...ent_1_1850bb3eb464f1d3c122cfeb4ccaf265._comment |   15 -
 .../Remote_repo_and_set_operation_with_find.mdwn   |    6 -
 ..._both_sides_have_written_to_the_repository.mdwn |   70 -
 ...ent_1_92211091daf9827a4ec7e5b5a6769d59._comment |    8 -
 ...ent_2_f0fa97a9eba1c624f6f8720ba8a160b7._comment |    8 -
 ...ent_3_e3d677ea4170c07cd31efe6dc85fa5f3._comment |    8 -
 doc/bugs/Repository_deletion_error.mdwn            |   46 -
 ...ent_1_31673d0300986b6098d1af2cc4b180c6._comment |   10 -
 ...ository_in_manual_mode_does_not_hold_files.mdwn |  305 --
 ...ent_1_86e8a4e546610e8e265806eb245d8aba._comment |    8 -
 ...ent_2_17d5775a38b67ba4f0e73f6b89cff2d0._comment |    8 -
 ...leak_somewhere_in_the___39__get__39___code.mdwn |   24 -
 ...ent_1_66b21720cd1b2a4f66ef24252d3e6305._comment |    8 -
 ...ent_2_18c9f55c5af1f4f690a7727df71ab561._comment |    8 -
 ...te_asks_for_ssh_key_password_for_each_file.mdwn |   30 -
 ...ent_1_fd95e0bb61e80a72b4ac1304ef6c2e77._comment |   16 -
 ...es_the_same_key_for_encryption_and_hashing.mdwn |   10 -
 ...ent_1_dc5ae7af499203cfd903e866595b8fea._comment |   18 -
 ...ent_2_c62daf5b3bfcd2f684262c96ef6628c1._comment |   12 -
 ...ent_3_e1f39c4af5bdb0daabf000da80858cd9._comment |   10 -
 ...ent_4_bb6b814ab961818d514f6553455d2bf3._comment |    8 -
 ...ent_5_5bb128f6d2ca4b5e4d881fae297fa1f8._comment |    8 -
 ...ent_6_63fb74da342751fc35e1850409c506f6._comment |    8 -
 ...40__SSH_too_old_on_OS_X_10.6.8__63____41__.mdwn |   27 -
 ...ent_1_0c57a2196d35eb1ecfb0c51273bba05c._comment |   10 -
 ...egfaults_on_Fedora_18_with_SELinux_enabled.mdwn |   65 -
 ...ent_1_f708d87aa65cd38c20087859d3ab2dc7._comment |   12 -
 ...ent_2_fb7188db031147992f3c906783ebbee0._comment |   59 -
 ..._39__s_for_Remotes_be_case_sensitive__63__.mdwn |   46 -
 ...ent_1_00b52dba3bc30516e06c44cbfd3a05a2._comment |   17 -
 ...ent_2_8f5fa659c2ab91b1757bac31cd3b15eb._comment |   10 -
 ...ent_3_ccf9623d60c58d036d8bf24757e50de3._comment |   10 -
 ...Should_ignore_.thumbnails__47___on_android.mdwn |   28 -
 ...__-c__34___instead_applies_it_to_all_files.mdwn |   75 -
 ...ent_1_2fe6d735bc075275a6b8890fac48ee58._comment |   18 -
 doc/bugs/Stale_lock_files_on_Android.mdwn          |   44 -
 ...ct_stomps_on___39__regular__39___git_files.mdwn |   27 -
 ...ent_1_0d2cb3b8509cd0eba50aafa14afefc02._comment |   63 -
 ...rect_mode_to_direct_mode_breaks_duplicates.mdwn |   30 -
 ..._server_is_not_honoring_--listen_parameter.mdwn |   24 -
 ...ent_1_4dd773372979dd95538bfba6516a11eb._comment |    9 -
 ...eates_broken_links_instead_of_proper_files.mdwn |   51 -
 ...ent_1_a2bedb2e77451b02fc66fc9ef5c4405c._comment |   11 -
 doc/bugs/Test_failure_on_debian_dropunused.mdwn    |   31 -
 doc/bugs/The_assistant_hangs_forever.mdwn          |   46 -
 ...ent_1_b0291e32860e0da0b66837d14ed5aab6._comment |    8 -
 ...ent_2_a2950cf91b8a4e4f2951f5522ef0e9c4._comment |   18 -
 ...ent_3_db95f78519d5ffbad793906028730dab._comment |   12 -
 ...ent_4_28b13fd3165b38a2fbc9e1a461c38921._comment |   22 -
 ...ent_5_81a79c8840ff26307a9c6edad5b850f9._comment |    9 -
 ...ent_6_b739719b14705f4d7e1d412b3cab090c._comment |   17 -
 ...ent_7_2b300d960697c5b967c1f109dfd6dfbf._comment |   16 -
 ...ent_8_8623220d08b1a72ed8b669a2d9cc0f75._comment |   15 -
 ...ssword_login___40__nearly__41___impossible.mdwn |   29 -
 ...nt_10_8305becdc6e70abdaf17e42f263173fc._comment |   12 -
 ...nt_11_d75896a6e204d1abdda04923aa668d04._comment |    8 -
 ...nt_12_a36a4a64a04c01c2db467b09300e6ebd._comment |    8 -
 ...nt_13_c9d6631c304acb289e485fb901e1f274._comment |   35 -
 ...nt_14_10282c4352075c8d148b8674973b7b16._comment |   22 -
 ...nt_15_ceb68da01d9e2fe9a70fab6244116da0._comment |   15 -
 ...nt_16_cca4abde86a8be5e2919c4738f5bdd0c._comment |   18 -
 ...nt_17_2fa5d7d9110c91b0a3a833cb3d9f53fd._comment |   10 -
 ...nt_18_bf21d28142e4c304aa0bc740955ddea0._comment |   10 -
 ...nt_19_45537758fa937f16fc82120bf8b234e8._comment |    8 -
 ...ent_1_a38497772834a4b12137390b461ce70b._comment |   12 -
 ...nt_20_b685050ee6fbb1a685e33f9656a10e84._comment |    8 -
 ...ent_3_17bc0220c20553c848875475c5fd4ae6._comment |   12 -
 ...ent_4_76472bc58bb790f773c46ec2c39fcf88._comment |   11 -
 ...ent_4_dcd9286e314779c25764484beff40561._comment |   10 -
 ...ent_5_2146eec77b87b615100d0d003e8dce75._comment |   15 -
 ...ent_6_2bd6f4e04903ee251d43d0a97bd40b6e._comment |    8 -
 ...ent_7_7db8ed002eb6313b07f09bd1a34019e3._comment |   10 -
 ...ent_8_1bcb2a238006044bc78849e56cb21a01._comment |    9 -
 ...ent_9_26c6937cf78e7141e0e3b20f25ed8f7a._comment |    8 -
 ...p_doesn__39__t_allow_deleting_repositories.mdwn |   33 -
 ...ent_1_1b80f9cfedd25e34997fa07e08d15012._comment |    8 -
 ...ent_2_53499da1185c56d8fd25f86ba41d96ce._comment |   11 -
 ...ent_3_3e07b8386d2c7afce2a78d24b9c260b9._comment |   14 -
 doc/bugs/Too_many_open_files.mdwn                  |   59 -
 ...ent_1_d5d509b9b431d2ea6000ebc0aed62857._comment |    8 -
 doc/bugs/Too_much_system_load_on_startup.mdwn      |   24 -
 ...ent_1_4470cddc0965062588acff1bc77285e9._comment |    8 -
 doc/bugs/TransferScanner_crash_on_Android.mdwn     |   28 -
 ...ent_1_6c3584ade1ee6cccddddeaa8e1697945._comment |   20 -
 ...ent_2_06574e05149a677d666a722061586658._comment |   10 -
 ...ent_3_54ae097d30bb7a49fe151f38c9bac033._comment |    8 -
 .../Trouble_initializing_git_annex_on_NFS.mdwn     |   16 -
 ...ent_1_e26952373150d63b8a5d3643a2762de1._comment |   10 -
 ...ent_2_f80b10ed395738e50e345fc22c708ae5._comment |   10 -
 ...ent_3_f99e0f05950fc2fc80fdecd35e17012c._comment |    8 -
 ...ent_4_e42146d2dcc4052266dd61d204aeb551._comment |    8 -
 doc/bugs/True_backup_support.mdwn                  |    7 -
 ...ent_1_50aa0bc1e2502622585682cb703e0b85._comment |   10 -
 ...ent_2_d6030c6c49b227e022f05d590746d4ca._comment |    8 -
 doc/bugs/USB_drive_not_syncing.mdwn                |  519 ---
 ...ent_1_de76bd6b9f8eb2489d4854a4c8ddd308._comment |   15 -
 doc/bugs/Unable_to_copy_from_Android.mdwn          |  148 -
 ...ent_1_3bb70c44b6b8d451687591fcab5c1506._comment |    8 -
 doc/bugs/Unable_to_import_feed.mdwn                |   27 -
 ...ent_1_16230fbbb996e165b84787ed4d5f72ea._comment |   45 -
 doc/bugs/Unable_to_switch_back_to_direct_mode.mdwn |   55 -
 ...ent_1_4585b251f011a153c62f377c324cf963._comment |   24 -
 ...ent_2_5848ebbab38d1244347f7e7351b3a30d._comment |   10 -
 ...ent_3_1c5c7b0c7bc336e00f43e257b87a6208._comment |    8 -
 ...ent_4_b0bfd68998bc3e11d8e089646b8292a6._comment |   12 -
 ...nable_to_sync_a_second_machine_through_Box.mdwn |   46 -
 ...ent_1_cb43a2bc976e3eb1cfc3ee9d4d34e78e._comment |   22 -
 ...ent_2_3375e9bfab3fed271413bd9bb5fa0121._comment |   30 -
 ...ent_3_c4420e1a3db321b4135b1626d3582adb._comment |   12 -
 ...ent_4_f4b2c88bb5938dacdd04dfe9a68560de._comment |   18 -
 ...ent_5_6dcc95ffb3fc7bbbedd6be5df0111c85._comment |    8 -
 ...able_to_use_remotes_with_space_in_the_path.mdwn |   35 -
 doc/bugs/Unfortunate_interaction_with_Calibre.mdwn |   24 -
 ...ent_1_7cb5561f11dfc7726a537ddde2477489._comment |    8 -
 ...ent_2_b8ae4bc589c787dacc08ab2ee5491d6e._comment |    8 -
 ...ent_3_977c5f6b82f9e18cdd81d57005bb8b89._comment |    8 -
 ...ent_4_ff7d2e9a39dfe12b975d04650ac57cc4._comment |    8 -
 ...ent_5_fc4d5301797589e92cc9a24697b2155d._comment |   15 -
 doc/bugs/Unknown_command___39__list__39__.mdwn     |   15 -
 ...ent_1_c625d03d1ed2019141ac9202f933466d._comment |    8 -
 ...ent_2_800e1b6417768bdadda311ebfb5df637._comment |    8 -
 ...ent_3_35dfc75ce9efffff139f8929dc311e29._comment |   10 -
 doc/bugs/Unknown_remote_type_webdav.mdwn           |    8 -
 doc/bugs/Unnecessary_remote_transfers.mdwn         |   27 -
 ...nt_10_b778fbb1386f0f51bf057ffacd590ebb._comment |   12 -
 ...nt_11_55430eac842d0a192dc7f41d7730e4d5._comment |   10 -
 ...ent_1_00c18e07678dc513a02d974fe059df73._comment |   12 -
 ...ent_2_2e9992dbfceabd6df535a2770626de16._comment |   35 -
 ...ent_3_a98f3091a6a658919f0562cf396439c2._comment |    8 -
 ...ent_4_417c1e8e27ee1a1f9ebf9160560605c5._comment |   96 -
 ...ent_5_eb5a2717a1f0c7bb761d2a7866b23def._comment |    8 -
 ...ent_6_89f756db1f3f2e60a3bd1f35f55fee43._comment |   40 -
 ...ent_7_5aaf8766a7ba05c4f92715e5d5175a8f._comment |   13 -
 ...ent_8_e856b350632cc865d16d1995a6cdf065._comment |   14 -
 ...ent_9_64f831545b34b78452952cf49b5f5b05._comment |   25 -
 ...emote_tracking_branches_into_account__63__.mdwn |   18 -
 ...ent_1_8fe44da0581d9b8c6ab5fe6aea8d83d1._comment |    8 -
 ...pendency_on_certificate___62____61___1.3.3.mdwn |   64 -
 ...t_repository_on_the_server_don__39__t_work.mdwn |   49 -
 ...ent_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment |   12 -
 ...ent_2_bca95245b457631d08b47591da6163ad._comment |    9 -
 ...ent_3_f54bb003096752dae0442660267a1e37._comment |   11 -
 ...ent_4_38bb916ed5b90b92ffa91a452ff052a9._comment |   10 -
 ...ent_5_5b6ef464ab1ad061f27122db40191e26._comment |    8 -
 ...ent_6_3727bda5082cb1f2b1f746f9f80ced7d._comment |    8 -
 ...ent_7_a7139f19f0b73c024cd9218eb01e6104._comment |    8 -
 ...ent_8_35c949aca52de83af4881a9da6340185._comment |    8 -
 ...ent_9_9100031689eaa460791191d9bfb746d8._comment |    8 -
 ...Using_Github_as_remote_throws_proxy_errors.mdwn |   27 -
 ...ent_1_10616b17c3fb8286fdc64c841023f8a1._comment |    9 -
 ...ent_2_8a72887d33e492a041f8246d93d0c778._comment |    8 -
 doc/bugs/Using_a_revoked_GPG_key.mdwn              |   34 -
 ...ent_1_7bb01d081282e5b02b7720b2953fe5be._comment |    8 -
 ...ent_2_9c0c40360f0058a4bd346c1362e302b6._comment |    8 -
 ...ent_3_8f69f58107246595f5603f35c4aa7395._comment |    8 -
 ...ent_4_78b3c52ba85edfa6ee6e273bec3bea5c._comment |   13 -
 ...ent_5_a85ccf2f09ebe87147f8761b81a02326._comment |    8 -
 ...ent_6_8b89eb5e6386acd0a922310c04f863ac._comment |   12 -
 ...ent_7_20dc5a7ce7cb6ca97ccdfb923c3b24bb._comment |   10 -
 ...ent_8_9dc921dc6077f828454a4444088b9a43._comment |   15 -
 ...ent_9_f50c802d78041fd1522f0e7599ce6a45._comment |   42 -
 doc/bugs/WEBDAV_443.mdwn                           |  307 --
 ...nt_10_9ee2c5ed44295455af890caee7b06f1a._comment |   18 -
 ...nt_11_863a7d315212c9a8ab8f6fafa5d1b7f5._comment |    8 -
 ...nt_12_c17a4e23011e0a917dbe0ecf7e9f0cb5._comment |    8 -
 ...nt_13_3414416ff455d2fd1a7c7e7c4554b54d._comment |   11 -
 ...nt_14_e1da141eefb0445c217e5f5c119356da._comment |    8 -
 ...nt_15_41c3134bcc222b97bf183559723713d9._comment |   27 -
 ...nt_16_89621b526065b5bef753ce75db1af7b5._comment |   14 -
 ...nt_17_131a1b65c8008cf9f02c93d4fb75720b._comment |   10 -
 ...nt_18_b4f894a0b9ebb84ab73f6ffcf0778090._comment |   29 -
 ...ent_1_c6572ca1eaaf89b01c0ed99a4058412f._comment |   10 -
 ...ent_2_a357969cde382a91e13920ee1e9f711c._comment |    8 -
 ...ent_3_213815d6b827d467c60f3e8af925813b._comment |   14 -
 ...ent_4_b775be4b722fc7124d9fbe2d5d01cc9f._comment |   22 -
 ...ent_5_c4ea745da437e56b2426d1c2c00dfcec._comment |   17 -
 ...ent_6_ef05c0ae88fee9c626922c6064ffdf1e._comment |    8 -
 ...ent_7_eecabe8d5ed564cb540450770ca7d0b6._comment |    8 -
 ...ent_8_7f77ba8ebd90186d3b3949ae529ba393._comment |   12 -
 ...ent_9_87ebdc92b48d672964fb3f248c53600f._comment |    9 -
 .../WORM:_Handle_long_filenames_correctly.mdwn     |    4 -
 ...ent_1_77aa9cafbe20367a41377f3edccc9ddb._comment |   10 -
 ...ent_2_fe735d728878d889ccd34ec12b3a7dea._comment |    8 -
 ...ent_3_2bf0f02d27190578e8f4a32ddb195a0a._comment |   10 -
 ...ent_4_8f7ba9372463863dda5aae13205861bf._comment |    8 -
 ...06c4a539999b04664136c6f785211a41_segfaults.mdwn |   31 -
 ...nt_10_6c872dff4fcc63c16bf69d1e96891c89._comment |    8 -
 ...ent_1_5cad24007f819e4be193123dab0d511a._comment |   10 -
 ...ent_2_d449bf656a59d424833f9ab5a7fb4e82._comment |    8 -
 ...ent_3_ffb1ce41477ad60840abd7a89a133067._comment |    8 -
 ...ent_4_cebbc138c6861c086bb7937b54f5adbc._comment |    8 -
 ...ent_5_5e27737a5bb0e9e46c98708700318e67._comment |    8 -
 ...ent_6_1f92da712232d050e085a4f39063d7a6._comment |   21 -
 ...ent_7_4153dc8029c545f8e86584a38bd536fb._comment |   15 -
 ...ent_8_f85b6eb5bfd28ffc6973fb4ab0fe4337._comment |    8 -
 ...ent_9_c747c488461c98cd285b51d3afc2c3eb._comment |   10 -
 .../Watcher_crashed:_addWatch:_does_not_exist.mdwn |   25 -
 ...ent_1_24f511a8103727894c6e96798a559870._comment |   10 -
 ...ent_2_e14eddbc09cadbf1e4dbbb0c07e0e5b0._comment |   10 -
 ...ent_3_513fae4d379008f954a307be8df34976._comment |   13 -
 ...ent_4_172eaeb3bb8b502379695aba35f96120._comment |   12 -
 ...ent_5_8adb9de82cc8581422734acc66dd094c._comment |   11 -
 ...ent_6_02f0beef1188bfa336bf4220eb5c6286._comment |   13 -
 doc/bugs/WebDAV_HandshakeFailed_.mdwn              |    7 -
 ...ent_1_40499110ea43bc99ad9dd9f642da434c._comment |   15 -
 ...ent_2_506712e8cc5b47b9bd69edf67ae54da7._comment |   10 -
 ...ent_3_5641481d9e9ed2b711b1516f1abc5c30._comment |    8 -
 ...ent_4_1d609de93fa66ce9dc802e67b5922243._comment |    8 -
 ...ent_5_62761882d30c1b02930c938cb8e30ed4._comment |   10 -
 ...ent_6_acda8fae848ec486ce2a0b3dff3bd0a5._comment |    8 -
 ...ent_7_6c51b6c7dd477d8911dd9a7a5c41ea2e._comment |    8 -
 ...ent_8_e834f791d3000669fab25732a7c72ab3._comment |   13 -
 ...d_behaviour_of_direct_and_indirect_annexes.mdwn |   57 -
 ...ent_1_56474a69c2f174d83be9137d3c045a47._comment |   33 -
 ...es__44___git_annex_uses_9x_times_diskspace.mdwn |   49 -
 .../comment_0._comment                             |   34 -
 ...nt_10_037a6dd6e15ef5f789a1f364f7507b53._comment |   45 -
 ...nt_11_614e4110188fc6474e7da50fc4281e13._comment |   10 -
 ...nt_12_dcb74fb91e1c2f0db4efd68c8bcbc96c._comment |   20 -
 ...nt_14_38671ba8d302f4d32460d1478abd2111._comment |   45 -
 ...nt_14_483244b1ed5744308022465f45c091fd._comment |   14 -
 ...ent_1_d2c63723fa4bf828873770a42ffaab20._comment |    8 -
 ...ent_3_52f0db73dc38c3e3a73f6c7a420bf016._comment |    8 -
 ...ent_4_93596b4d5a48ffcf4bc11ba9c83cf7ca._comment |    9 -
 ...ent_5_de94e80dde6d12485140bb079d74d775._comment |   14 -
 ...ent_6_5f34c3d449247b4bce4665b3ea4d054c._comment |   25 -
 ...ent_7_b43ae8aec23ba3acaf70edc0de058710._comment |   17 -
 ...ent_8_13b8e0a62f6b6d02960687e206a8b016._comment |   15 -
 ...ent_9_818b94a74b01a210d1106dd35bc932d8._comment |   10 -
 ...dows_and_Linux_in_direct_mode_confuses_git.mdwn |  384 --
 ...ent_1_155e0c4d3aa41eebfe27533ab70a91d3._comment |   68 -
 ...With_S3__44___GPG_ask_for_a_new_passphrase.mdwn |   21 -
 ...ent_1_a4fc30bf7d39cae337286e9e815e6cba._comment |   13 -
 ...ent_2_e5d42b623017acedf6a3890ce15680a3._comment |   12 -
 ...ent_3_e5150b65b514896e14b9ad3d951963f7._comment |   10 -
 ...ent_4_47c2fc167b0c396edc40468fb7c7bfee._comment |    8 -
 ...h_a___34__Network_unreachable__34___error..mdwn |   42 -
 ...ent_1_6d821af99ab3c83a5b0f52d3713ab8e2._comment |   10 -
 ...ent_2_206b6c8cce8350fc088f01c42fc4715b._comment |    8 -
 ...ent_3_ed36f503f88611382b50687608b9b7e7._comment |   10 -
 ...n_operating_in_a_symlink__39__ed_directory.mdwn |   27 -
 ...__deletes_all_files_with_identical_content.mdwn |   49 -
 ...ent_1_2eb20b65582fa7f271b1d0bb5560d08c._comment |   10 -
 ...ent_2_b14e1d31dd6a8fb930fcc0bec798e194._comment |   19 -
 ...ent_3_1892bcfbe3c462aa74552a241d65cad9._comment |    8 -
 ...ent_4_dfa0e31996eaa14e2945c1d11670c4d9._comment |   15 -
 ...ent_5_e2a9336cf1080c158765d4adfe72f26b._comment |    9 -
 .../__34__git_annex_watch__34___adds_map.dot.mdwn  |   23 -
 ...s_a_commit_even_with_autocommit__61__false.mdwn |   22 -
 doc/bugs/__34__make_test__34___fails_silently.mdwn |    4 -
 ...ent_1_f868e34f41d828d4571968d1ab07820a._comment |   16 -
 ...ent_2_fb9e8e2716b0dea15b0d4807ae7cd114._comment |    8 -
 ..._write_a_repository_there__39___on_Windows.mdwn |   32 -
 ...ing_repo_on_other_drive_than_C:_on_Windows.mdwn |   36 -
 ...ent_1_ea3b2c0e3bdfb50ac0dce10ba1b6339f._comment |   24 -
 ...rts_pulling_in___39__archive__39___content.mdwn |   24 -
 ...ent_1_56f9cd5cc2e089b32cb076dc2e2a8ca5._comment |   22 -
 ...ent_2_21c0f7f328cb51080fbd97e086c47a30._comment |   37 -
 ...ent_3_3287b2f25f3b5ae4c27f4748694563ee._comment |    8 -
 ...ent_4_e515eca68a70d40c522805d7e0d7c0e6._comment |   24 -
 ...ent_5_b27f4c103dda050b6e9cf03ea3157abc._comment |   10 -
 ...ent_6_2cc7083dab944705bf91fc00319b75e6._comment |    9 -
 ...ent_7_1175f9be789d4c1907f0be98e435bd2f._comment |   10 -
 ...ent_8_78e6164ef67a9560a3a9ead1f7a72473._comment |   15 -
 ...ent_9_1d578fd13022dcd6382b415a7f6e097a._comment |    8 -
 ..._quickcheck_that_satisfies___62____61__2.1.mdwn |   40 -
 ...3___pause_syncing_with_specific_repository.mdwn |    8 -
 ...start_it_easily_with_the_terminal_app_menu.mdwn |   23 -
 ...ent_1_9bb53c45d685b368c7ba1758885f2874._comment |   12 -
 ...ent_2_251311a04f1a610e54ebe8e9b92de72e._comment |   13 -
 ...ent_3_83ac87a01639776a6e519af226bd84d5._comment |    8 -
 ...ix__96___run_on_non-annexed_files_is_no-op.mdwn |   15 -
 ...ent_1_9b671e583eec5adf870dccd1e97b5dbc._comment |    8 -
 ...ent_2_d11744202213d6f897f4234bc4c70c18._comment |    9 -
 ...ent_3_a729deb465ff44f5a9b87c963cd6235a._comment |   15 -
 ...ent_4_3f735503df9a08472d42fabd219c2ec5._comment |   31 -
 ...ent_5_2c61eabbba7fd2a52ba02d59a0a76a42._comment |    8 -
 ...s_not_work_on_other_git_annex_repositories.mdwn |  115 -
 ...ent_1_94ccd548c084286163eeb2af1ddc18e3._comment |    8 -
 ...ent_2_befde3ef3d2b171ebb691915ff3af172._comment |    8 -
 ...__96__git_annex_sync__96___ignores_remotes.mdwn |  106 -
 ...ent_1_39421e6935233cd8f45949ebdef369fe._comment |    9 -
 ...ent_2_53fb15d6fbf96d43564ff7c866239d18._comment |    8 -
 ...ument_to___34__git_annex_dropunused__34___.mdwn |   21 -
 doc/bugs/add_script-friendly_output_options.mdwn   |   19 -
 ...adding_an_rsync.net_repo_give_an_gpg_error.mdwn |   22 -
 ...ent_1_f55cfc133be72ac10cae93c877c487df._comment |   21 -
 ...ent_2_24dd024ac4b21a82a781343b8fe3891e._comment |   11 -
 ...ed_with_--file_doesn__39__t_actually_relax.mdwn |   26 -
 doc/bugs/addurl_fails_on_the_internet_archive.mdwn |   65 -
 ...ent_1_e227aa25eea0b41f1176037a601c5844._comment |   10 -
 ...ent_2_6d4fd58f0caa1f75ee2dd3f0a909cd91._comment |    8 -
 ...t_work_with_spaces_in_filenames_and_--fast.mdwn |   29 -
 ...ent_1_eea9477ea1157cb88c8a07d8da5f0dba._comment |   10 -
 ...allows_repository_with_the_same_name_twice.mdwn |   24 -
 ...ent_1_ba7801403e7138684704a3471c8bc4a6._comment |   12 -
 ...ent_2_8c19a4ddedbe7ddb8bdcf84acac68cc8._comment |   14 -
 doc/bugs/amd64_i386_standalone:_no_SKEIN.mdwn      |   41 -
 ...ent_1_fcf7e1089b25993378df7574ccee8062._comment |    8 -
 ...tandalone:_ld-linux-x86-64.so.2:_not_found.mdwn |   21 -
 ...ent_1_5e40f32caf9c1177a5f7b9883cdcc6dd._comment |    8 -
 ...:_high_CPU_usage__44___unclear_how_to_quit.mdwn |   28 -
 ...nt_10_1d841ff0b0ffd814efed2449dc1f35f3._comment |   10 -
 ...nt_10_cd101e0af45d8f463011fb0d04b3b822._comment |    9 -
 ...nt_11_8595041cfe703d9bea49e792732dc15f._comment |    8 -
 ...ent_1_8e7bc6965ea967a8d43240791a30c5bc._comment |    9 -
 ...ent_2_891c1073f908b204651899d41599f944._comment |    8 -
 ...ent_3_de02b8f1b5928fa1a7078c4aa2124bea._comment |   11 -
 ...ent_6_506acc4275a81ed9e9b08e8a40fcf96a._comment |    9 -
 ...ent_7_d38d6f40db4c9437764c7b2ddf36b5a9._comment |   10 -
 ...ent_8_9bb23e9cbc77ecca4b1209b0f66bc2b0._comment |    8 -
 ...ent_9_d1ce7fc251db076da61eed5bb9d71b9a._comment |    9 -
 ...ent_9_feb71c1022ff65d82e66a3958a41dfb2._comment |    8 -
 doc/bugs/android_cannot_get_from_5.20131221.mdwn   |   41 -
 ...ent_1_f8eeb67e58bf2a4658dcc32a9f275f19._comment |    8 -
 ...ent_2_eba841b1978c70a4c20a8d96c9f71172._comment |   36 -
 ...ent_3_4ba8208822c7f66e23037564b3501391._comment |    8 -
 ...annex-rsync-options_shell-split_carelessly.mdwn |   18 -
 ...ent_1_2636e0d224317f2e6db94658d8a094c4._comment |   23 -
 ...copies_not_overriden_by_--numcopies_option.mdwn |   16 -
 doc/bugs/annex_add_in_annex.mdwn                   |    6 -
 ...ils:___34__No_such_file_or_directory__34__.mdwn |   68 -
 ...ent_1_e44ae9c19796efc8eda5432d3bf1e5a3._comment |   18 -
 doc/bugs/annex_get_over_SSH_is_very_slow.mdwn      |   33 -
 .../annex_seems_to_ignore_core.bare_setting.mdwn   |   45 -
 ...ent_1_beb674205f06310f6a9060bea35fa3fe._comment |   11 -
 ...ent_2_bc5a4be517409f8da2f36299dc4cbbde._comment |    8 -
 doc/bugs/another_build_error_in_assistant.mdwn     |   79 -
 doc/bugs/archiving_git_repositories.mdwn           |    5 -
 ...ent_1_51f546a571303118446a9e0b3e6482c9._comment |   10 -
 ...___-___34__too_many_open_files__34___error.mdwn |   32 -
 ...ent_1_9904c30a4c24a699d71e90ce5e9b89cf._comment |    8 -
 .../assistant_always_assumes_port_22__63__.mdwn    |   39 -
 ...nt_does_not_list_remote___39__origin__39__.mdwn |   26 -
 ...ent_1_ffa008240c61b50396aa92f467731db6._comment |   12 -
 ...ent_2_a53f80090bc2a0f32b8d8307cb24b563._comment |    8 -
 ...nt_does_not_warn_on_files_it_failed_to_add.mdwn |   46 -
 ...ent_1_13b2f93b7d09c8fd6c22829a0dc6428b._comment |   10 -
 ...ent_2_94e46bc0044b8a91a9fd51058825aa8f._comment |   60 -
 ...ent_3_10a38bdbf31dd4071e4bc4ac746d9c56._comment |   11 -
 ...ent_4_b8fdf502c7e80aece5a9544a2078c85c._comment |   36 -
 ...ent_5_a2ff7668f2a0d549b362d7de97fac8a1._comment |   10 -
 ...ent_6_60d72f34a6cfd1c081f74aa610f4305a._comment |   33 -
 ...ent_7_53a73e662c9356b759fbfa1e5a3bd927._comment |   14 -
 ...ent_8_10b65168b6a54d960427966d7e3d05f5._comment |   19 -
 ...ent_9_b640e8fa6aafb041d66bbf8857a8fa3d._comment |   44 -
 ...ection__59___falling_back_to_polling__34__.mdwn |   48 -
 ...ent_1_a3dccf1db287ea5c1ac1763518d5d9f9._comment |    9 -
 ...ent_2_cb85fb3ba0152671568c23d6b95f3b7a._comment |   14 -
 ...ent_3_5d87371fa86ddbbcd31dfc932ab6080f._comment |    9 -
 ...s_to_sync_in_preferred_content_mode_manual.mdwn |   24 -
 ...ent_1_37acb3afafb1b4c4da7c778130cf3035._comment |    8 -
 ...ent_2_9d58887ee0184663852bde83b8d497c7._comment |   10 -
 ...ent_3_b70881c8026e30fd3ddc051bd01a888b._comment |    8 -
 ...ent_4_43f756e2e6ff985c8e050da0e369d486._comment |   25 -
 ...ent_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment |   25 -
 ...__34___group__44___tries_to_transfer_files.mdwn |   56 -
 ...ent_1_e3f545d9adc27a4e7340bf16177c4fe0._comment |   12 -
 ...ent_2_1403076dbc47733607f0c8b2856e2381._comment |   37 -
 ...ent_3_af83717bfb260bea6d52ff71c6b34743._comment |    8 -
 ...ent_4_b4f811611d14e7392009c539fa6b8574._comment |    8 -
 ....1_not_::1_which_breaks_IPv6_enabled_hosts.mdwn |   30 -
 ...ent_1_91a62a2ce14a1027d2ac8b8e88df5f0c._comment |   12 -
 ...ent_2_4982cd373eaaeee180be03c6e9fda7b1._comment |   10 -
 ...ent_3_85d264e311acaa91dac0597ee8deda82._comment |    8 -
 ...ndows_adding_remote_containing_linux_paths.mdwn |   23 -
 doc/bugs/authentication_to_rsync.net_fails.mdwn    |   30 -
 ...ent_1_9db65f89415c8d825f268afb75244998._comment |   10 -
 ...ckend_version_upgrade_leaves_repo_unusable.mdwn |   72 -
 .../bad_comment_in_ssh_public_key_ssh-rsa.mdwn     |   22 -
 ...ent_1_15cce6e6f455e83f4362a38c561bc973._comment |   17 -
 ...ent_2_e9e1f38880a32610b3fbce475bffc3e4._comment |   12 -
 ...ent_3_51da7f5881f65422328d341e5ab0d250._comment |   33 -
 ...ent_4_ba384314c1e47ec4b72e1843e0500df9._comment |   10 -
 doc/bugs/bare_git_repos.mdwn                       |   29 -
 ...4___and_constraints_issues_with_3.20121112.mdwn |   45 -
 .../bug_system_updates_when___34__done__34__.mdwn  |   24 -
 doc/bugs/build_is_broken_at_commit_cc0e5b7.mdwn    |   13 -
 ..._with_latest_release_0.20110522-1-gde817ba.mdwn |   14 -
 doc/bugs/build_problem_on_OSX.mdwn                 |   18 -
 doc/bugs/building_on_lenny.mdwn                    |   80 -
 ...nitremote_failed_with_localhost_+_username.mdwn |   49 -
 ...ent_1_0e669c3039b089fa8a815d3ec11465d2._comment |   20 -
 ...nd_module___96__Data.AssocList__39____34__.mdwn |   23 -
 ...ent_1_0da9fd67c3cc01b316f95a1df4eb62ae._comment |    8 -
 .../cabal_configure_is_broken_on_OSX_builds.mdwn   |   14 -
 .../cabal_install_fails_to_install_manpage.mdwn    |   43 -
 ...2.04_fails_with_complaint_about_regex-base.mdwn |   34 -
 ...lised___40__non-git-annex__41___repository.mdwn |  208 --
 ...ent_1_dd202a7764d9df998868d595a86ffb21._comment |   30 -
 ...ent_2_ca065c82ac8e3215b581660f3e44f459._comment |   51 -
 ...ent_3_927a01f9961c71bedb42c519a31b5fe5._comment |   14 -
 ..._39__t_annex_get_from_annex_in_direct_mode.mdwn |   23 -
 ...ent_1_20c31a844d8351a99cf69e05d2836e0e._comment |   19 -
 ...ent_2_f26e0f763f9027d9dfc08cd840ced153._comment |   10 -
 ..._t_drop_unused_files_that_never_were_added.mdwn |   86 -
 ...istant_from_the_command_line_anymore__63__.mdwn |   31 -
 ...ssistant_with___34__host:port__34___syntax.mdwn |   30 -
 ...ent_1_397eb359c3f8ef30460a9556b6f55848._comment |   14 -
 ..._add_file__44___get___34__user_error__34__.mdwn |   32 -
 ...ent_1_14aa717c1befcbbf526f25ca2f0af825._comment |   14 -
 ...ent_2_7f7ac59e7f3dce9d7a7d0c3379c2edcf._comment |   18 -
 ...ent_3_5ebf03120b12edb3fbb8954546e7603e._comment |    8 -
 ...ent_4_1ba6d2614778949520b47896fd98b598._comment |    8 -
 ...ent_5_4a6e55861a63b350a02edb888b4da99b._comment |   21 -
 doc/bugs/cannot_connect_to_xmpp_server.mdwn        |   32 -
 ...nt_10_5072de8fcca9fe70bc235ea8c8ee2877._comment |    8 -
 ...nt_11_dabd74bba1f38b326a2d0c86d3027cd9._comment |   17 -
 ...nt_12_0245b426cc0ab64f8c167b8806b03f5d._comment |   10 -
 ...ent_1_307df11b5bcf289d7999e1e7f7c461c9._comment |   10 -
 ...ent_2_f24378cf30a7d32594da90749fabec3c._comment |   12 -
 ...ent_3_4b07093be844ac62b611cee1dfde5aa7._comment |    8 -
 ...ent_4_fe1ed152a485c4aebfa9b9f300101835._comment |    8 -
 ...ent_5_2d311f520aee04287df6bddfd8535734._comment |   28 -
 ...ent_6_d9f916f012184738446c5996ee9d2270._comment |   13 -
 ...ent_7_0b5f9350e2367301241c7668a15815ef._comment |    8 -
 ...ent_8_f00b6ae154004e405f0bd23b7359962e._comment |    8 -
 ...ent_9_41b86468013da15f46be29da520afa10._comment |    8 -
 doc/bugs/cannot_determine_uuid_for_origin.mdwn     |  135 -
 doc/bugs/case_sensitivity_on_FAT.mdwn              |   49 -
 doc/bugs/check_for_curl_in_configure.hs.mdwn       |   92 -
 .../clicking_back_in_the_web_browser_crashes.mdwn  |   23 -
 ...ent_1_c962218657a28494ff837a471d71b43f._comment |    8 -
 ...ent_2_643b2c99ecfe851c576a023ce4385dbb._comment |   10 -
 ...ent_3_6e85c50439da81212f4239c74947b75e._comment |   12 -
 ...hable.git-annex.assistant.plist_is_invalid.mdwn |   15 -
 ...eaks_on_OSX_as_mntent.h_doesn__39__t_exist.mdwn |    8 -
 ...m_and_builds_a_broken_git-annex_executable.mdwn |   57 -
 ...should_detect_uuidgen_instead_of_just_uuid.mdwn |    6 -
 doc/bugs/conflicting_haskell_packages.mdwn         |   17 -
 ...ent_1_e552a6cc6d7d1882e14130edfc2d6b3b._comment |   24 -
 doc/bugs/conq:_invalid_command_syntax.mdwn         |   30 -
 ...ent_1_f33b83025ce974e496f83f248275a66a._comment |   10 -
 ...ent_2_195106ca8dedad5f4d755f625e38e8af._comment |    9 -
 ...ent_3_55af43e2f43a4c373f7a0a33678d0b1c._comment |   15 -
 doc/bugs/copy_doesn__39__t_scale.mdwn              |   38 -
 ...ent_1_7c12499c9ac28a9883c029f8c659eb57._comment |   10 -
 ...ent_2_f85d8023cdbc203bb439644cf7245d4e._comment |   15 -
 ...ent_3_4592765c3d77bb5664b8d16867e9d79c._comment |   11 -
 ...opy_fast_confusing_with_broken_locationlog.mdwn |    6 -
 ...nt_10_435f87d54052f264096a8f23e99eae06._comment |    8 -
 ...nt_11_9be0aef403a002c1706d17deee45763c._comment |   24 -
 ...nt_12_26d60661196f63fd01ee4fbb6e2340e7._comment |   11 -
 ...nt_13_ead55b915d3b92a62549b2957ad211c8._comment |   35 -
 ...nt_14_191de89d3988083d9cf001799818ff4a._comment |   10 -
 ...nt_15_b3e3b338ccfa0a32510c78ba1b1bb617._comment |    8 -
 ...nt_16_04a9f4468c3246c8eff3dbe21dd90101._comment |    8 -
 ...ent_1_6a41bf7e2db83db3a01722b516fb6886._comment |   18 -
 ...ent_2_9f5f1dbffb2dd24f4fcf8c2027bf0384._comment |    8 -
 ...ent_3_b596b5cfd3377e58dbbb5d509d026b90._comment |   14 -
 ...ent_4_d7112c315fb016a8a399e24e9b6461d8._comment |   12 -
 ...ent_5_4ea29a6f8152eddf806c536de33ef162._comment |   14 -
 ...ent_6_0d85f114a103bd6532a3b3b24466012e._comment |    8 -
 ...ent_7_d38d5bee6d360b0ea852f39e3a7b1bc6._comment |   12 -
 ...ent_8_29c3de4bf5fbd990b230c443c0303cbe._comment |   10 -
 ...ent_9_2cee4f6bd6db7518fd61453c595162c6._comment |    8 -
 ...copy_to_webdav_sometimes_doesn__39__t_work.mdwn |   74 -
 ...ent_1_77629f620b28ac62364de44b41fa539d._comment |    8 -
 doc/bugs/cross_platform_permissions_woes.mdwn      |   36 -
 ...ent_1_7f01104de38a6a319a8f36aa1dc8b4b3._comment |   14 -
 ...ent_2_0a34e11b466fad287325425e76487fa1._comment |   73 -
 ...ent_3_278f91b4bc4c32717ab1c39c2abf9305._comment |    8 -
 ...ent_4_eb6a271cb63c71341469c9ff89dc0eb9._comment |    9 -
 doc/bugs/cyclic_drop.mdwn                          |  104 -
 ...conflicting_directory-file_of_direct_repos.mdwn |  199 --
 ...ent_1_294c33af08649256908a97894f93c05d._comment |   10 -
 ...ent_2_02a2b69adbb04b557146e713b70b34d2._comment |   14 -
 ...ent_3_d296ef26fc90f4e3166bba6d2de0a1ee._comment |    8 -
 ...ent_4_33ba2c890c962a71ae9fadc417359f8e._comment |    8 -
 ...ent_5_39eb0bb96fd271bd0de4a3a40814ae1b._comment |   11 -
 ...ent_6_d80c4b631bdf58901a06f29a2c5682e2._comment |    8 -
 ...annex_add__34___on_android_in_direct_mode_.mdwn |   19 -
 ...ent_1_eb6db7f6a156a065e2724c2de5fc4366._comment |   10 -
 ...ent_2_59a96cade9e4881767562a139fc7fb4b._comment |   40 -
 ...ent_3_bf9d2562d66f0f6a9478ac178606cf4e._comment |   12 -
 ...ent_4_ad0dbdc448fff2e126ffec9aac6d7463._comment |   23 -
 ...ent_5_e828585e56b10710598143483ce362b6._comment |   12 -
 ..._repository_with___60__SCREECH__62___files.mdwn |   73 -
 ...ent_1_523b80ad81ad49bddfb8855d12d5561d._comment |   10 -
 doc/bugs/direct_mode_renames.mdwn                  |   15 -
 ...ent_1_f18c335e0d6f4259d2470935ef391cb8._comment |    8 -
 .../direct_mode_sync_should_avoid_git_commit.mdwn  |    5 -
 ...ent_1_d286800081f019651cd40355b7d5518a._comment |   27 -
 ...ent_2_4e23201d1d1d549f72eec75987601a73._comment |   13 -
 ...ption_+_chunk_size___61___lost_files__63__.mdwn |   51 -
 ...ent_1_69dfbf566c75396cdaaf5ad70f1a94a8._comment |   19 -
 ...ent_2_8d09cc0e06548c4ebde7956edd1b5d85._comment |    8 -
 doc/bugs/dotdot_problem.mdwn                       |    4 -
 ...drop_fails_to_see_copies_that_whereis_sees.mdwn |   69 -
 ...ent_1_f5a9d99d90daf5eba4773d361fa1807a._comment |   14 -
 ...ent_2_040aa454cd8acd2857ef36884465576f._comment |   16 -
 ...ent_3_f5d8faab325ee26800ecad5aba49b54b._comment |   10 -
 ...-adding_from_web_remotes_doesn__39__t_work.mdwn |  139 -
 ...sn__39__t_handle_double_spaces_in_filename.mdwn |   87 -
 ...punused_doesn__39__t_work_in_my_case__63__.mdwn |   70 -
 ...enableremote_broken_with_direct_mode__63__.mdwn |   41 -
 ...ent_1_a2e61f5de7a28498de0c2d5e3d51eab4._comment |    8 -
 doc/bugs/encrypted_S3_stalls.mdwn                  |    9 -
 ..._gpg_keyid_still_uses_symmetric_encryption.mdwn |   46 -
 ...ent_1_2f4ec4b7b92a0f0a0c4c0758da4a05a5._comment |   13 -
 ...ent_2_7c0aeae6b1b2b0338735b0231c5db7d4._comment |   16 -
 doc/bugs/encryption_key_is_surprising.mdwn         |   24 -
 ...ent_1_5b172830ac31d51a1687bc8b1db489f9._comment |   10 -
 ...ent_2_5b7e6bb36c3333dfd71808e8b4544746._comment |    8 -
 ...ent_4_8ec86b8c35bce15337a143e275961cd5._comment |    8 -
 ...ent_4_c5e49b3a0eceabe6d14f5226d7ba4c7a._comment |    8 -
 ...ent_5_cd7cbf0c0ee9cafec344dfbf1acd9590._comment |    8 -
 ...ent_6_01381524114d885961704acc3f172536._comment |    8 -
 ...ent_7_c1eb59e1c5f583dcef7cea17623a2435._comment |    8 -
 ..._building_git-annex_3.20120624_using_cabal.mdwn |  159 -
 doc/bugs/error_propigation.mdwn                    |    3 -
 ...ing_repositories_with_non-ASCII_characters.mdwn |   62 -
 ...ent_1_38cc2d2ed907649df085de8ad83cb9dd._comment |   14 -
 .../error_with_file_names_starting_with_dash.mdwn  |   15 -
 doc/bugs/fails_to_handle_lot_of_files.mdwn         |  445 ---
 ...ent_1_09d8e4e66d8273fab611bd29e82dc7fc._comment |    8 -
 ...ent_2_fd2ec05f4b5a7a6ae6bd9f5dbc3156de._comment |    8 -
 ..._Out_of_memory__63___mmap_failed:_No_error.mdwn |   31 -
 ...ent_1_3bc14a8b093ebb2c0571f5a554ef8cf3._comment |   12 -
 doc/bugs/fatal:_empty_ident_name.mdwn              |   51 -
 ...ent_1_ceae87308fb75a1f79c7c8d63ec47226._comment |    8 -
 ...ent_2_68832ee3e0e7244ce62bccabe2e52630._comment |   25 -
 ...ent_3_ed31ad316747343d7730e4c2d7dacd24._comment |   10 -
 ...ent_4_b812d6f30e8a866bce7260a9ee3218e3._comment |   13 -
 ...lative_filenames_containing___39__..__39__.mdwn |   52 -
 ...ent_1_8a4045634bffc29c8147056096b7089d._comment |   13 -
 ...ent_2_a1539aaec74074b4667ac27cfcfcccd6._comment |   16 -
 ...ent_3_d252f39ddb9c9c14784c85a8b850a4ec._comment |   10 -
 ...ent_4_eb07c84dc0b15b68c99d0ef4144f82f5._comment |   10 -
 doc/bugs/feature_request:_addhash.mdwn             |   29 -
 ...ent_1_064e963adb6834813380fd836bb58566._comment |    8 -
 ...ent_2_7b712786c580dd1ca24479664c31eed6._comment |    8 -
 ...cess__47__locking_issues_with_the_assitant.mdwn |   54 -
 ...nt_10_fadf06f5ab34e36ab130536ec55afc8e._comment |   12 -
 ...nt_11_4a337f7b1140c45e5dd660b40202f696._comment |   10 -
 ...ent_1_05e1398e78218ced9c2da6a2510949e8._comment |   21 -
 ...ent_2_9226f0adf091154c0d8a08b340b71869._comment |    8 -
 ...ent_3_44d3e2096b7d45a1062222bee83a346d._comment |    8 -
 ...ent_4_f2e1d188b7b2d2daf0d832c59a68583e._comment |    8 -
 ...ent_5_998fe58994ecf855310e4b8e6cce9e18._comment |    8 -
 ...ent_6_4ce243cb0ea8ff810a4949a5320e4afc._comment |   13 -
 ...ent_7_c713f6316d889c8fc52326f21375c1c4._comment |    8 -
 ...ent_8_6dd23bab7983b8b1f938dd4f21a16f5a._comment |    8 -
 ...ent_9_961c8f968eff0b39a85b607ee3f7630d._comment |   16 -
 doc/bugs/file_modification_times.mdwn              |   13 -
 ...__47__.ssh__47__config___40__windows__41__.mdwn |   20 -
 ...ent_1_a04b71f4f81c477d18f14d8dfe8b378f._comment |    8 -
 ...ent_2_0dbc908984b4b5bcc1283db807e058cb._comment |   10 -
 ...ent_3_ff6cd2bb007d41284a09e470e060c32d._comment |    8 -
 ..._40__relates_to_the_new_inotify_flag__41__.mdwn |   36 -
 doc/bugs/free_space_checking.mdwn                  |   21 -
 ...ent_1_a868e805be43c5a7c19c41f1af8e41e6._comment |   10 -
 ...ent_2_8a65f6d3dcf5baa3f7f2dbe1346e2615._comment |    8 -
 ...ent_3_0fc6ff79a357b1619d13018ccacc7c10._comment |    8 -
 ...47__fix_the_permissions_of_.git__47__annex.mdwn |    8 -
 ...m_when_less_copies_than_required_are_found.mdwn |   57 -
 doc/bugs/fsck_output.mdwn                          |   46 -
 ...ld_double-check_when_a_content-check_fails.mdwn |    3 -
 ...ent_1_03af24b70adbcd9f4b94d009f6b71d0a._comment |   13 -
 ...ent_2_41214a7d18c66b694645248d6ebeadbf._comment |   25 -
 ...ent_3_e7ddd77ea35994f2051f840e9b4c7e0c._comment |   11 -
 ...ent_4_36a70d5a378983a76fcdbb7fba044044._comment |   32 -
 ...ent_5_899c4afbc988d81984c5c3397285bb01._comment |   12 -
 ...ent_6_dbff51d00c5645eb1832aa4644889c5e._comment |   10 -
 ...nks_file_content_is_bad_when_it_isn__39__t.mdwn |   35 -
 ...ent_1_cafb58eca97a0a66110ac39b169d8de3._comment |    8 -
 ...initremote_pushes_git-annex_but_not_master.mdwn |   19 -
 .../get_failed__44___but_remote_has_the_file.mdwn  |   40 -
 ...ent_1_55c8b73ce05dfca11a393bb296b99b9a._comment |   10 -
 ...ent_2_474c67a421dca4c245e7bfe495d3f6d3._comment |   18 -
 ...ent_3_845e8a23d63fb0b071c63ee736697d26._comment |   20 -
 ...ent_4_7dec21cb67e7f4dbdb49da97f2443e8f._comment |   35 -
 ...7____47___web_remotes_if_the_file_is_empty.mdwn |   26 -
 .../get_from_bup-remote_with_pubkey_failing.mdwn   |   93 -
 ...__static__41__:_strange_closure_type_30799.mdwn |   75 -
 ...ent_1_1c19e716069911f17bbebd196d9e4b61._comment |   10 -
 ...ent_2_a4d66f29d257044e548313e014ca3dc3._comment |   66 -
 ...ent_3_f5f1081eb18143383b2fb1f57d8640f5._comment |   38 -
 ...ent_4_b1f818b85c3540591c48e7ba8560d070._comment |   10 -
 ...ent_5_67406dd8d9bd4944202353508468c907._comment |   13 -
 ...40__unrecognized_option___96__--uuid__39__.mdwn |   53 -
 ...ent_1_13510e954e36484e196e7395a3a9bf1f._comment |   10 -
 ...ent_2_7edc478a76983a3b3c68d01f24dce613._comment |    9 -
 ...__39__t_honour_Rsync__39__s_bwlimit_option.mdwn |   37 -
 ...ent_1_8cda861c11ef2fff3442e5a0df741939._comment |   12 -
 ...ent_2_15e06f6db9a14a8217dea25e24ddc23a._comment |   12 -
 ...ent_3_d36045e2b466882108c5bf09580755fa._comment |    8 -
 doc/bugs/git-annex:_Argument_list_too_long.mdwn    |   40 -
 ...ent_1_3f83ea525436b2379ab29a0f860c4669._comment |    8 -
 ...ent_2_b417c94169378ef7d0d278ebae517fa1._comment |    8 -
 ...ent_3_fa925cca216cb810ad80482b19fc6053._comment |    8 -
 ...ent_4_8bd2996107b2d272c32810658e07e715._comment |    8 -
 ...ent_5_378de7d7503a64611eab62f2f5cffef3._comment |   15 -
 ...ent_6_a94e17151348d02999442dd1219babfb._comment |   10 -
 ...:_Cannot_decode_byte___39____92__xfc__39__.mdwn |   34 -
 ...ent_1_f1a7352b04f395e06e0094c1f51b6fff._comment |   12 -
 ...ent_2_c1890067079cd99667f31cbb4d2e4545._comment |    8 -
 ...ent_3_213c96085c60c8e52cd803df07240158._comment |   13 -
 doc/bugs/git-annex:_Not_in_a_git_repository._.mdwn |   22 -
 ...ent_1_e10363a912953a646b87c824d1c6e5d4._comment |   10 -
 ...ent_2_9e96063a664b2be8a36d7940e7632d3f._comment |    8 -
 ...ent_3_8c9bd76b0e1200723ec13fbef943a2cc._comment |   10 -
 ...ent_4_8c49979b8a815f0d6f9de39ee9a88730._comment |    8 -
 ...to_write_file:_TlsNotSupported:_user_error.mdwn |   35 -
 ...ent_1_2c54c57f456e4570666fd7a5731dcd27._comment |   11 -
 ...ent_2_c9a9f070b2eaff9f68f603ca1defec81._comment |    8 -
 ...ent_3_62ff37a8429cfb3577d4250c701811d0._comment |    8 -
 doc/bugs/git-annex:_status:_1_failed.mdwn          |   25 -
 ...nt_10_7cd9de88e55633fc75460f4fe0400f09._comment |    8 -
 ...nt_11_504a944aab34155046f2fd82c2878f3e._comment |   18 -
 ...ent_1_c235cc83c75474e6393e08d2d94b119d._comment |   10 -
 ...ent_2_932f6aaa712298a47868002872e16310._comment |   10 -
 ...ent_3_4bf55320439de152a65e2f21d4a0604b._comment |   14 -
 ...ent_4_cb2cfb798c6171f77eb7c4c4061c0f0c._comment |    8 -
 ...ent_5_05c84dde377298adfd3fc20749b3108f._comment |   10 -
 ...ent_6_bb5141e29c665bc0bb82611ea27d4be8._comment |   11 -
 ...ent_7_5fd39168c9e1bf43909ee0ab3c75c40c._comment |   35 -
 ...ent_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment |    8 -
 ...ent_9_573377d444aee0895b231082bc6839a4._comment |    8 -
 .../git-annex_3.20130216.1_tests_are_broken.mdwn   |   43 -
 ...py_files_with___39__:__39___in_their_names.mdwn |   38 -
 ...-annex_add_hangs_indefinitely_on_all_files.mdwn |   32 -
 ...ent_1_f787155da9a4d92c41546c35f3bd6a08._comment |   12 -
 ...ent_2_66ad95d98c12b4b26e06e3fe28f0ed01._comment |   10 -
 .../git-annex_add_should_repack_as_it_goes.mdwn    |   32 -
 ...ent_1_dbcaa0be4cd764128fb7263a95f73a32._comment |   22 -
 ...ent_2_6a27551c4fb7f62ed9f627134c755d01._comment |   14 -
 ...ent_3_ff8b589fbcf25c98abd1c58830074650._comment |    8 -
 doc/bugs/git-annex_branch_corruption.mdwn          |   95 -
 doc/bugs/git-annex_branch_push_race.mdwn           |   45 -
 ...n_repositories_with_a_partial_set_of_files.mdwn |   29 -
 ...it-annex_directory_hashing_problems_on_osx.mdwn |  100 -
 ...nt_10_f3594de3ba2ab17771a4b116031511bb._comment |    8 -
 ...nt_11_97de7252bf5d2a4f1381f4b2b4e24ef8._comment |   13 -
 ...nt_12_f1c53c3058a587185e7a78d84987539d._comment |    8 -
 ...nt_13_4f56aea35effe5c10ef37d7ad7adb48c._comment |    8 -
 ...nt_14_cc2a53c31332fe4b828ef1e72c2a4d49._comment |   10 -
 ...nt_15_37f1d669c1fa53ee371f781c7bb820ae._comment |   17 -
 ...nt_16_8a4ab1af59098f4950726cf53636c2b3._comment |   22 -
 ...nt_17_515d5c5fbf5bd0c188a4f1e936d913e2._comment |    9 -
 ...nt_18_db64c91dd1322a0ab168190686db494f._comment |   14 -
 ...nt_19_ff555c271637af065203ca99c9eeaf89._comment |    8 -
 ...ent_1_9a7b09de132097100c1a68ea7b846727._comment |    8 -
 ...nt_20_7e328b970169fffb8bce373d1522743b._comment |   19 -
 ...nt_21_98f632652b0db9131b0173d3572f4d62._comment |   10 -
 ...nt_22_52d41afd7fd0b71a4c8e84ab1b4df5bd._comment |    8 -
 ...nt_23_c2cd8a69c37539c0511bae02016180ca._comment |    8 -
 ...ent_2_174952fc3e3be12912e5fcfe78f2dd13._comment |  185 -
 ...ent_3_a18ada7ac74c63be5753fdb2fe68dae5._comment |   18 -
 ...ent_4_039e945617a6c1852c96974a402db29c._comment |    8 -
 ...ent_5_eacd0b18475c05ab9feed8cf7290b79a._comment |   37 -
 ...ent_6_e55117cb628dc532e468519252571474._comment |   14 -
 ...ent_7_0f4f471102e394ebb01da40e4d0fd9f6._comment |   68 -
 ...ent_8_68e2d6ccdb9622b879e4bc7005804623._comment |   12 -
 ...ent_9_45b11ddd200261115b653c7a14d28aa9._comment |    8 -
 ...ist_files_containing_ISO8859-15_characters.mdwn |   48 -
 ...ent_1_b84e831298c03b12471fb75da597e365._comment |    8 -
 doc/bugs/git-annex_dropunused_has_no_effect.mdwn   |   12 -
 ...ent_1_66b581eb7111a9e98c6406ec75b899cf._comment |   12 -
 ...ent_2_11c46cd2087511c3d22b7ce7c149b3e9._comment |   16 -
 ...ent_3_b1c3d8c6ec4b20727aaa9c4b746531b0._comment |   10 -
 ...ent_4_f05a9a3760858c5ee5c98dd8ab059c28._comment |    8 -
 ...it-annex_fails_to_initialize_under_Windows.mdwn |  215 --
 ...ent_1_082277b9b906a2cc0fcace6790f5cfad._comment |   10 -
 ...ent_2_b9a3a0104bc56f9110fc58c9df140f12._comment |   34 -
 ...ent_3_7aeeccd6c4bd97224980a2752e0f8ba8._comment |   14 -
 ...ent_4_12b6ed59c8b7ded6b6b9150b32e58ce4._comment |   17 -
 ...ent_5_f975059733fca678e93b791b2a250535._comment |   13 -
 ...ent_6_66cfbb5ce75d322f68b4c41f11bb15ae._comment |   59 -
 ...ent_7_9195b2373b0c5298ebbe309414d26ee4._comment |   10 -
 ...ent_8_bf3f1e801bee930673907d9a8eb4c147._comment |    8 -
 .../git-annex_fix_not_noticing_file_renames.mdwn   |   36 -
 ...ent_1_4edd95200d59ec5a5426167b8da8e3f9._comment |   24 -
 ...ent_2_a9a44debefb3bdd4b8ed2d1cf53f2338._comment |    8 -
 ...ent_3_0efb11f35b872b75a3fbc4ebb71ac827._comment |   10 -
 ...it-annex_get:_requested_key_is_not_present.mdwn |   41 -
 ...ent_1_d4baa6607a61d0e6a7cea1325a5ddf95._comment |   26 -
 ...ent_2_b49725488c3db5e00ede7b65ed9d62fa._comment |  110 -
 ...ent_3_c17a7138579b93c6f14e3444c11664ac._comment |    8 -
 ..._with_git_when_staging__47__commiting_logs.mdwn |   34 -
 ...it-annex_immediately_re-gets_dropped_files.mdwn |   27 -
 ...ent_1_09e616a4866e726a48be4febe6375cc8._comment |    8 -
 ...nex_incorrectly_parses_bare_IPv6_addresses.mdwn |   59 -
 ...sing_rsync_remotes_with_encryption_enabled.mdwn |  103 -
 ...d_filesystem_can_still_failed_due_to_case_.mdwn |   32 -
 ...ent_1_850695231926dfe94f11342d3af7f63c._comment |   54 -
 ...ent_2_c2a2f801a3e18ad597ff0acf2f104557._comment |   22 -
 ...annex_quit_unexpectedly___40__macosx__41__.mdwn |  358 --
 ...ent_1_97abb8442329d19c9687002f43afac74._comment |   23 -
 ...ent_2_3405f3cd699860ee239cf23ade19e92c._comment |   10 -
 ...git-annex_sync_broken_on_squeeze_backports.mdwn |   20 -
 ...nks_files_are_in_repositories_they_are_not.mdwn |   29 -
 ...ent_1_6722fd627ec4add9f2b16546bd8ef341._comment |    8 -
 ...ent_2_508e475f764e1cb453b756eb50bc3a15._comment |   34 -
 ...ent_3_1656ba18c519a262c57ef626a3449e77._comment |   12 -
 ...ent_4_347dc3b6e5bc6c4195ec09d54bc1398e._comment |   24 -
 ...ent_5_a9c93bfc3278ef8b1117eac2af859bc3._comment |   12 -
 ...ent_6_804dd62beef64f7d4e203bdb28cbe660._comment |   11 -
 ...ent_7_4ef107d70647780eb5347cae6f467fed._comment |   12 -
 .../git-repair_real_world_failure_example.mdwn     |   11 -
 doc/bugs/git_annex_add_..._adds_too_much.mdwn      |   25 -
 ...x_add_eats_files_when_filename_is_too_long.mdwn |   14 -
 ...ent_1_9650284913bec2a00cf551b90ab5d8ff._comment |   21 -
 ...ent_2_c6c8d2a1f444d85c582bc5396b08e148._comment |    8 -
 ...ent_3_5776864d78d56849001dd12e3adb9cbe._comment |    8 -
 ...ent_4_371ec7b4ae73280ede31edfe90b42a95._comment |    9 -
 ...ent_5_4fb04f646de591640f8504c0caf61acd._comment |   12 -
 ...ent_6_b4055409fe48da95bb3101c0242ef0bc._comment |    8 -
 ...it_annex_add_error_with_Andrew_File_System.mdwn |   28 -
 ...ent_1_bc783e551fc0e8da87bc95bff5b8f73a._comment |    8 -
 ...ent_2_faefcf69bd61c47566131cb31b78cc19._comment |   10 -
 ...ent_3_d5014c8b78437b9fddbb1e83d3679081._comment |   10 -
 doc/bugs/git_annex_add_memory_leak.mdwn            |   39 -
 ...t_annex_add_removes_file_with_no_data_left.mdwn |  103 -
 ...nt_10_9cc749a6efd4359a99316036f5bc867f._comment |   12 -
 ...nt_11_1fed5be9db29866e4dc3d3bb12907bf3._comment |    8 -
 ...nt_12_06d517ac4ef8def4629a40d7c3549bac._comment |    8 -
 ...ent_1_8f081aeba7065d143a453dc128543f59._comment |   18 -
 ...ent_2_54a4b10723fd8a80dd486377ff15ce0d._comment |   10 -
 ...ent_3_f1964e4e07991a251c2795da0361a4e2._comment |   28 -
 ...ent_4_73c38d843c30f00f6fd8883db8e55f62._comment |   10 -
 ...ent_5_7ede5ee312f3abdf78979c0d52a7871a._comment |   12 -
 ...ent_6_e37cf18708f09619442c3a9532d12ed9._comment |   13 -
 ...ent_7_a744ef7dd3a224a911ebb24858bc2fd6._comment |    8 -
 ...ent_8_f97141b255073b90120895148220c2d7._comment |   10 -
 ...ent_9_dd2be11dfd190129d491f5f891e7cd1a._comment |   10 -
 .../git_annex_assistant_--autostart_failed.mdwn    |   39 -
 ...ent_1_746545273b53849c42ff6272324e5155._comment |   10 -
 ...ent_2_5bdf6f94da12e551ae12e7f550a84d62._comment |    8 -
 ...ent_3_bfd646f69946a5fe926b270cf94f87cb._comment |    8 -
 ...git_annex_content_fails_with_a_parse_error.mdwn |   32 -
 ...ent_1_2b60b6ae0115de13ecf837b34dadcd1d._comment |    8 -
 ..._-f_REMOTE_._doesn__39__t_work_as_expected.mdwn |   18 -
 ...py_trying_to_connect_to_remotes_uninvolved.mdwn |   27 -
 ...ent_1_f1330935a07460c9c8bc82ee8d4709c5._comment |   12 -
 .../git_annex_describe_can_break_uuid.log.mdwn     |   46 -
 ...ent_2_9ead36f13cbde6c822b231441de636ae._comment |    8 -
 doc/bugs/git_annex_does_nothing_useful.mdwn        |   67 -
 ...nt_10_457354dc0018333002dc5049935c0feb._comment |    8 -
 ...nt_11_8a6d244165dd238ddf9dd629795de2f6._comment |   10 -
 ...nt_12_30d06bc0f1c37d988a1a31962b57533c._comment |   18 -
 ...ent_1_fc4f51ddcbc69631e2835b86c3489c8e._comment |    7 -
 ...ent_2_9bb1647e6c59f1ed7b13b81ecc33f920._comment |   13 -
 ...ent_3_d434f5c614a27b75d73530b5b918b851._comment |   14 -
 ...ent_4_998e33219d29ea41b0b2a5d2955a9862._comment |   46 -
 ...ent_5_c72e2571e5b8c06bbfa2276a7ad1e8a6._comment |   16 -
 ...ent_6_bc8b42432ba25de8f972c192bc3cdff6._comment |   44 -
 ...ent_7_e7469a4c5e45078ade775f5cbdd17cfc._comment |   67 -
 ...ent_8_bc9e6fd284440a59ffe4e4ed1f73f7d7._comment |   30 -
 ...ent_9_38a2dbeee3750d79ca9a943a02fceb29._comment |   17 -
 doc/bugs/git_annex_fork_bombs_on_gpg_file.mdwn     |   25 -
 ...nt_10_6e29b60cd77f3288e33ad270f95f410e._comment |    8 -
 ...nt_11_ad13e3221ae06086e86800316912d951._comment |   12 -
 ...nt_12_41746b731eae7f280bb668c776022bcb._comment |    8 -
 ...nt_13_56ca8590110abffeed6d826c54ca1136._comment |   10 -
 ...ent_1_73ae438a37e4c5f56fe291448e1c64dd._comment |   13 -
 ...ent_2_aa237adebe7674b8cdb9a967bb5f96a8._comment |    8 -
 ...ent_3_ab403d7abbbbabd498b954b0b9742755._comment |   12 -
 ...ent_4_a35d04440b1220faf9088107c3f17762._comment |   10 -
 ...ent_5_8345331b9b313769ba401da2ffd89332._comment |   10 -
 ...ent_6_7eb535ca38b3e84d44d0f8cbf5e61b8b._comment |   18 -
 ...ent_7_a3aa4231a82917c56cbdf52b65db7133._comment |   21 -
 ...ent_8_178fd4e4d6abbca192fcd6d592615fca._comment |   12 -
 ...ent_9_7d80f131f43312bb061df2be7fa956ef._comment |   10 -
 ...sck_in_direct_mode_does_not_checksum_files.mdwn |   18 -
 ...ent_1_a6cde4aa495512344fa7f50e10749c68._comment |    8 -
 ...ent_2_4ac3b87ec0bc0514c4eff9f5a75b9f5d._comment |   26 -
 ...ent_3_d18b1fdc866edf2786d2c6b7ec55119f._comment |   11 -
 ...ent_4_31e4fcbf63c11cc374a849daf3ce1dbc._comment |    8 -
 .../git_annex_fsck_is_a_no-op_in_bare_repos.mdwn   |   21 -
 ...ent_1_fc59fbd1cdf8ca97b0a4471d9914aaa1._comment |    8 -
 ...ent_2_273a45e6977d40d39e0d9ab924a83240._comment |    9 -
 ...hoke_when_remote_is_an_ssh_url_with_a_port.mdwn |   13 -
 ...sed_about_remotes_with_dots_in_their_names.mdwn |   34 -
 ...ort_destroys_a_fellow_git_annex_repository.mdwn |  130 -
 doc/bugs/git_annex_importfeed_fails.mdwn           |   64 -
 ...t_annex_indirect_can_fail_catastrophically.mdwn |   78 -
 ...ent_1_0b085e7e8c8e364f479574bc00c7c394._comment |   21 -
 .../git_annex_info_listings_can_be_confusing.mdwn  |   33 -
 ...mote_needs_some___34__error_checking__34__.mdwn |   65 -
 .../git_annex_initremote_walks_.git-annex.mdwn     |   19 -
 doc/bugs/git_annex_lock_dangerous.mdwn             |   19 -
 ...migrate_leaves_old_backend_versions_around.mdwn |   19 -
 ...ent_1_f3e418144e5a5a9b3eda459546fc2bb0._comment |    8 -
 ...ould_use___39__git_add_-f__39___internally.mdwn |   11 -
 ...ent_1_7683bf02cf9e97830fb4690314501568._comment |    8 -
 ..._sync_content_without_--content_flag__41__.mdwn |   32 -
 ...ent_1_a797542acb1f0c51dd4c75e4566558f0._comment |   10 -
 doc/bugs/git_annex_test_under_windows_8.1.mdwn     |   67 -
 ...nnex_uninit_loses_content_when_interrupted.mdwn |   33 -
 ...ent_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment |    8 -
 ...ent_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment |   12 -
 ...emoves_files_not_previously_added_to_annex.mdwn |   32 -
 ...ent_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment |   10 -
 ...ent_2_3aa125635609fce41ab0c98cefb81f98._comment |    9 -
 ...d_aborts_due_to_filename_encoding_problems.mdwn |   15 -
 ...ent_1_8ba4fdb9f2d3bd44db5e910526cb9124._comment |    8 -
 ...ent_2_2a4a2b3e287a0444a1c8e8d98768a206._comment |    8 -
 ...ent_3_dacfdb8322045fc4ceefc9128bf7c505._comment |   17 -
 ...ent_4_7889a3ff5ce80c6322448aa674df8525._comment |   10 -
 ...ent_5_6d28c2537ce24eeb3496ca349823defd._comment |   19 -
 ...ent_6_4bf14ecef622988e80976c0fb55c24b9._comment |   10 -
 ...ent_7_d2e5382fe0f38fb9dd9ee69901c68151._comment |    8 -
 ...ent_8_b282757537cda863d3dc6d0bbfd6b656._comment |    8 -
 ...emote_branches_which_makes_it_inconsistent.mdwn |  106 -
 ...ent_1_a636ffe55b11c46a0afcc0b9a3a88cd4._comment |   10 -
 ...ent_2_5e1ad57420efd16ae09c9e5cad55b5f2._comment |   13 -
 ...nex_unused_seems_to_check_for_current_path.mdwn |   39 -
 ..._upgrade_output_is_inconsistent_and_spammy.mdwn |   15 -
 ...ent_1_3a01c81efba321b0e46d1bc0426ad8d1._comment |   10 -
 ...ex_version_should_without_being_in_a_repo_.mdwn |    7 -
 ...ent_1_e7b26eeb1a765fd83280ef907c0deef2._comment |    8 -
 doc/bugs/git_annex_webapp_runs_on_wine.mdwn        |   47 -
 ...ent_1_c71dfa42780c0fc78f88ce054e5f3ee3._comment |   16 -
 ...ent_2_f28441b18b0be90c1e58348455ce09d9._comment |   23 -
 ...nnex_won__39__t_copy_files_to_my_usb_drive.mdwn |   60 -
 ...ent_1_7707017fbf3d92ee21d600fe0aefce4f._comment |   10 -
 ...ent_2_f3392ec3ca7392823cbad2cc9b77f54e._comment |    9 -
 ...ent_3_b3d016a487b12748fe2c4d14300eb158._comment |   20 -
 ...ent_4_61f600511a3172f0707e5809fc444d0c._comment |    9 -
 ...ent_5_8cf029ac7bf3c19dcb0b613eed3b52ac._comment |   10 -
 ...ent_6_e40d88eba7d8aec1530ce1d32d1c85f2._comment |   11 -
 ...ent_7_b101fab9e690d1b335a1a29abab68d6c._comment |   10 -
 ...ent_8_b30d32086314a7e357f3dd6608828ee5._comment |    9 -
 ...it_annix_breaks_git_commit_after_uninstall.mdwn |   42 -
 ...ent_1_c8b1bab40d3bb2468a5bba7b116e854e._comment |    8 -
 ...ent_2_4173770375fca51dcaf9b974296d041a._comment |    8 -
 ...s___40__child_of_git-annex_assistant__41__.mdwn |   34 -
 ...ent_1_5e3f4b63db5cd32b63fb3e6a78f9b093._comment |   10 -
 doc/bugs/git_repo_fails_to_checkout.mdwn           |   39 -
 ...ent_1_d92e7e3b41382501a08f6a66c673b1fd._comment |    8 -
 ...sion_in_prebuilt_linux_tarball_is_outdated.mdwn |   11 -
 ...ent_1_2a5a07498df9d38531d4570f7b463b9a._comment |    8 -
 doc/bugs/gix-annex_help_is_homicidal.mdwn          |   23 -
 doc/bugs/gpg_bundled_with_OSX_build_fails.mdwn     |   25 -
 ...ent_1_ec911f920db6c354ba998ffbb5886606._comment |   10 -
 ...ent_2_bf2a3ab1bbe258bd501ec4b776882adf._comment |   12 -
 ...ent_3_c0142427400323c00bd8294415ae32c5._comment |   15 -
 ...ent_4_b56db4b5afc276f88a2b980e22fda8a0._comment |   10 -
 ...ent_5_a4eda81e5f927c463593bc48fbe84077._comment |   12 -
 ...ent_6_2f0b9331d16a208883bac586258a7b50._comment |    8 -
 ...ent_7_c05c484a6134f93796cff08de0f63e80._comment |   16 -
 ...ent_8_f2cb5467ebe80cf67e1155b771b73978._comment |    8 -
 ...ent_9_27bbda7e31f55b29e1473555ee17e613._comment |    8 -
 doc/bugs/gpg_error_on_android.mdwn                 |   39 -
 ...ent_1_870583fd1b7a33b688b9a228077d1333._comment |  629 ----
 ...ent_2_9ce5511a109bde50d8cf87bad0268b4a._comment |   26 -
 ...ent_3_b345e80f38d38f82cfcfce3102138fb8._comment |   46 -
 ...ent_4_032f42235b7f26854e725041ca33384b._comment |   10 -
 ...ting_a_new_remote_repository_via_assistant.mdwn |   55 -
 ...ent_1_7b409701c650b55b3472accd70555f16._comment |    8 -
 ...ent_2_40b00f7258512677516ec5036b89090f._comment |   14 -
 doc/bugs/gpg_hangs_on_glacier_remote_creation.mdwn |   78 -
 ...ent_1_41ca74a4e4aaf4f6b012a92677037651._comment |   14 -
 ...ent_2_dd11fd25c8bb1f2d7e1292c07abf553e._comment |  591 ---
 ...ent_3_543d8a13756c1355a5752867bdcbefd3._comment |   20 -
 ...ent_4_6441cf25e6bd62c96d7e766da9bdd7fb._comment |   25 -
 ...ent_5_72e152294e36bc5f2d78e8e2ebed6a23._comment |    8 -
 ...ent_6_890e85df05903795e01efbd7879f9c87._comment |    8 -
 ...ent_7_042047f9fcc45abbfa47c3973d79f08e._comment |   10 -
 doc/bugs/gpg_needs_--use-agent.mdwn                |   53 -
 doc/bugs/gsha256sum_crashes.mdwn                   |   92 -
 ...ent_1_8597d8ee29232494b1795526b6a0d8d1._comment |   81 -
 ...ent_2_e410fc1998fbc7db8c13081f76acf7fc._comment |   12 -
 ...ent_3_f796dd49097425148b785bb7b6213df6._comment |   10 -
 ...ent_4_1c46b4ad0c981c6105ffb8531223f0b1._comment |   10 -
 ...ent_5_3fa106ed7fb30226ee7c48b66edb963c._comment |   16 -
 ...ent_6_276b181b2aeb1512e0468b88598e0a84._comment |   12 -
 ...ent_7_c2898422ceb9e103d8acdde866b7a211._comment |   34 -
 doc/bugs/hGetContents:_user_error.mdwn             |   38 -
 ...ent_1_30178f151f8c60d2ff856ca543dc506c._comment |   10 -
 ...ent_2_f74eeed4a007058a22183fd678ecd6c6._comment |    8 -
 ...ent_3_515e562228a89a13d6d857a874f4a468._comment |    8 -
 ...ent_4_8c6ed5e459c5c66b77db446c6317114c._comment |    8 -
 ...ent_5_f80bce48c3f96b0cd6892af43ee88a96._comment |    8 -
 ...ent_6_69dc09e4ae726856dafbeec34170671c._comment |    8 -
 ...ent_7_3f66b03f773341fad94ec16b4f55edaa._comment |   32 -
 ...ent_8_a697e2d36abfc999e65c9f587c0de56e._comment |   10 -
 ...ent_9_da7c5905a64bb6779970f9394155e629._comment |   10 -
 ..._OSX___40__or_this_a_general_problem__41__.mdwn |  113 -
 ..._with_rysnc_installed__44___not_recognized.mdwn |   19 -
 ...ent_1_3ff000eb3efde41426c7b086ae627dcf._comment |   12 -
 ...ent_2_34e592ab057df2df54e13d3f5cae64f0._comment |   14 -
 ...ent_3_05ffbae13d8f9b08315f40bb9b206f46._comment |   21 -
 ...ent_4_99d1f151263ca3433dd4afa8a928b1fe._comment |   30 -
 ...ent_5_6ef1a377b0b4d3efeffdf9693d0b496b._comment |   12 -
 ...ent_6_d9e36828ad55f3181a1c650010f23d6b._comment |   14 -
 doc/bugs/immediately_drops_files.mdwn              |  224 --
 ...ent_1_9ef6e694ef8a8eee7a42f88554475db7._comment |   10 -
 ...ent_2_76e4f8b73ab60b2540dd2a3e5379791d._comment |    8 -
 ...ent_3_788db083f5ba2e5589c3b952203ec954._comment |   21 -
 ...ent_4_425b79865eb77d69d0b7a71a14639f81._comment |   10 -
 ...ent_5_7c9f660b6bcec31827a44a650e9d4622._comment |   10 -
 .../importfeed_fails__44___bad_feed_content.mdwn   |   36 -
 ...ing_the_option_--lazy_for_specific_podcast.mdwn |   77 -
 ...ent_1_4ccfabbaf75e139b32f6fa6f7bc6a7fe._comment |    8 -
 ...tfeed_should_allow_pubdate_in_the_template.mdwn |    5 -
 ...ed_uses___34____95__foo__34___as_extension.mdwn |   17 -
 ...ernal_server_error:_unknown_UUID_on_webapp.mdwn |  147 -
 ...l_server_error_creating_repo_on_ssh_server.mdwn |   26 -
 ...ent_1_4a2c9338d5c779496049d78e29cf5cbd._comment |    8 -
 ..._when_choosing_encrypted_rsync_repo_option.mdwn |   28 -
 ...ent_1_14a2f775f43a86129ce3649a06f8ba0b._comment |    8 -
 ...ent_2_7b277320fcffd8d03e0d3d31398eb571._comment |   16 -
 ...ent_3_ba9dd8f2cc46640383d4339a3661571f._comment |   16 -
 ...ent_4_274ae39d55545bde0be931d7a6c42c94._comment |   12 -
 ...ent_5_242291d46acc61bdfc112e3316de528b._comment |   10 -
 ...ent_6_76b936263e82ca6c415a16ed57e770b4._comment |    8 -
 ...ent_7_9ccd3749fd9f32b0906c0b9428cc514f._comment |   10 -
 ...ent_8_4e8982668b5044b2286d55c90adb9da3._comment |    8 -
 ...ent_9_aaf0ee250972d737a2ca57de5b5f1c0a._comment |   12 -
 .../interrupting_migration_causes_problems.mdwn    |   52 -
 doc/bugs/javascript_functions_qouting_issue.mdwn   |   44 -
 .../journal_commit_error_when_using_annex.mdwn     |   21 -
 ...ent_1_38f60ca3503ea1530c4bd2cde5c9182f._comment |   10 -
 ...ent_2_6de455a67f37d9ee0a307a78123781bf._comment |   10 -
 doc/bugs/json_is_broken_for_status.mdwn            |   34 -
 ...ssistant_causes_resource_starvation_on_OSX.mdwn |   30 -
 ...ent_1_91c911c29fd126ddc365c561591f627e._comment |   10 -
 ...ent_2_c316aead931a6a2377a4515bbb34ac5b._comment |    8 -
 ...__47__committer_thread_loops_occassionally.mdwn |   53 -
 ...ent_1_f8d1720aa26c719609720acf0772606e._comment |   11 -
 ...ent_2_0527569ea2924721d19dadcf4fe0ec5a._comment |    8 -
 ...ent_3_5b67ff08a897ea3d2266ccc910ab4278._comment |    8 -
 doc/bugs/mac_os_x_10.7_DMG_out_of_date.mdwn        |   16 -
 doc/bugs/make_SHA512E_the_default.mdwn             |   29 -
 .../making_annex-merge_try_a_fast-forward.mdwn     |   35 -
 ...map_not_respecting_annex_ssh_options__63__.mdwn |   38 -
 ...ent_1_c63a1ed5909d53f116f06e60aba74dc6._comment |   10 -
 ...rives_seem_to_die_when_using_the_ARM_build.mdwn |   38 -
 ...ent_1_0527581ea60d28bb28504fa2a355ed87._comment |   10 -
 ...ent_2_926a87b60e20d286d49639c8dad13a1a._comment |    8 -
 ...ent_3_c509fba1a9adacfd26a2bd12b4aea988._comment |    8 -
 .../minor_bug:_errors_are_not_verbose_enough.mdwn  |   26 -
 ...missing_dependency_in_git-annex-3.20130216.mdwn |   29 -
 doc/bugs/missing_kde__47__gnome_menu_item..mdwn    |   29 -
 ....0.1_is_not_in_Haskell_Platform_2012.4.0.0.mdwn |   12 -
 ...ent_1_2c4b3757bb8de563edca65aeabcbbc5a._comment |   29 -
 ...ounted_repo_results_in_errors_on_drop_move.mdwn |   59 -
 ...orming_upgrades_or_setting_upgrade_options.mdwn |   35 -
 ...ble_to_have_annex_on_a_separate_filesystem.mdwn |   32 -
 ...old_data_isn__39__t_unused_after_migration.mdwn |   66 -
 doc/bugs/on--git-dir_and_--work-tree_options.mdwn  |   31 -
 doc/bugs/one_test_fail_on_osx.mdwn                 |   30 -
 doc/bugs/ordering.mdwn                             |   12 -
 doc/bugs/pages_of_packfile_errors.mdwn             |   32 -
 ...ent_1_eb2989112b38bb27ce8f691dd5d318e5._comment |   10 -
 ...ent_2_69fba53035ebea213ae1c11be5326690._comment |    8 -
 ...ent_3_73b9f574e8ce36d5e0d0f6c6a89006b7._comment |   39 -
 doc/bugs/pasting_into_annex_on_OSX.mdwn            |   28 -
 ...ent_1_4eab52bb6eda92e39bdaa8eee8f31a7f._comment |    8 -
 ...ent_2_f1b58adfec179b75c1fc2bf578a3b5c4._comment |    8 -
 ...ent_3_270aa7680c3b899a92ce6543eaba666a._comment |   17 -
 ...ent_4_ec11a80d5b0f78c7a927f8aa71a6c57a._comment |    8 -
 ...ent_5_1928bd25e5e6874a3b83c2f2adc776f5._comment |    7 -
 ...ent_6_0fe288f54b781a0c51395cb32f0e2f9d._comment |    8 -
 doc/bugs/problem_to_addurl_--file_with_ftp.mdwn    |   67 -
 ...ent_1_2bf44f1653069fb2ed0b124cf8581a48._comment |    8 -
 ...ent_2_c85266a9359a9f45e632f31c016a45dc._comment |    8 -
 ...ent_3_5bba62e1dd4118bcf7e1c990c7009239._comment |   22 -
 doc/bugs/problems_with_utf8_names.mdwn             |   81 -
 ...nt_10_c53c309771caa41accab5523cc6998dd._comment |   10 -
 ...ent_1_3c7e3f021c2c94277eecf9c8af6cec5f._comment |   17 -
 ...ent_2_bad4c4c5f54358d1bc0ab2adc713782a._comment |   10 -
 ...ent_3_4f936a5d3f9c7df64c8a87e62b7fbfdc._comment |    8 -
 ...ent_4_93bee35f5fa7744834994bc7a253a6f9._comment |   10 -
 ...ent_5_519cda534c7aea7f5ad5acd3f76e21fa._comment |   11 -
 ...ent_6_52e0bfff2b177b6f92e226b25d2f3ff1._comment |    8 -
 ...ent_7_0cc588f787d6eecfa19a8f6cee4b07b5._comment |    8 -
 ...ent_8_ff5c6da9eadfee20c18c86b648a62c47._comment |   10 -
 ...ent_9_f358e617799e5a4e3afc6536d419eb08._comment |   10 -
 .../quvi_0.9.5_does_not_work_with_git-annex.mdwn   |   87 -
 ...ent_1_d0d2bcd97ef5c9bce8a57c4184a176e0._comment |   10 -
 ...ent_2_ff9661198257b8c5e2e8ca3d85a7471c._comment |    8 -
 ...d_leave_file_in_place_on_checksum_mismatch.mdwn |   15 -
 ...vable_device_configurator_chokes_on_spaces.mdwn |   18 -
 ...sion_denied__44___after_direct_mode_switch.mdwn |   81 -
 ...ent_1_14cec6448831c67794b62926a03b2fc5._comment |   13 -
 ...ent_2_93af8f48a01b6e2d011bd6f60499ccd2._comment |   23 -
 ...ent_3_f8fba1955e62360061613e5898b3d74e._comment |   16 -
 ...ent_4_abffe1fb3b3e684b126e4768089dc5f4._comment |    8 -
 ...ent_5_bccc53d2d6f659f21965042a057358f5._comment |    8 -
 ...ent_6_ac8b3b042b882680f0eb0d53ade1ce15._comment |   14 -
 ...ex_get_the_file__39__s_content_from_remote.mdwn |   27 -
 ...ent_1_d6aad1831674586fe4cdf61dd2a4bbb9._comment |   15 -
 ...ent_2_8591e174c1a8cddfae9371407a58ff1c._comment |   10 -
 ...pair_fails_when_home_on_seperate_partition.mdwn |   60 -
 doc/bugs/restart_daemon_required.mdwn              |   22 -
 ...ent_1_f79ac16cc9f1e3b08cd121bf5efb29c3._comment |    8 -
 ...ent_2_50c1b268a3cc4514681059eabca674e3._comment |    8 -
 ...ent_3_1716e0f3c7c44dc77ebf7f00fdd8f9e3._comment |  310 --
 ...ent_4_3ce776786eca83fcb8ff94c8f6ff3eb9._comment |   15 -
 doc/bugs/rsync_remote_shows_no_progress.mdwn       |   15 -
 ...ent_1_a7f5d646a924c462b987561cf6fc4318._comment |    8 -
 doc/bugs/scp_interrupt_to_background.mdwn          |    2 -
 ...version_without_having_to_be_in_a_git_repo.mdwn |   11 -
 doc/bugs/smarter_flood_filling.mdwn                |   31 -
 doc/bugs/softlink_mtime.mdwn                       |   57 -
 .../ssh-askpass_locks_me_out_of_x_console.mdwn     |   27 -
 ...ent_1_1def05a57e25b6765b881f22bc6d82a2._comment |   10 -
 ...ent_2_cd4869faf350c81deb1de6fa25f32876._comment |   10 -
 ...ent_3_87c980feb28a05d12a259fb2b3091cdf._comment |    8 -
 ...ent_4_33a367dbeb5c7bf8692a414f20d8de69._comment |   10 -
 .../ssh_connection_caching_broken_on_NTFS.mdwn     |   66 -
 ...ent_1_54e7e12514f4c109fd57a4eb744b731a._comment |   14 -
 ...t_linux_build_as_of_Mar_6th___39__14__41__.mdwn |   10 -
 ...ent_1_462c377dca2484e5598a0b71d91ab64a._comment |    8 -
 ...data___40__git-annex-shell_not_found__41__.mdwn |   50 -
 ...ent_1_6203563196a70b8356102a48927e4ccd._comment |   44 -
 ...ent_2_cee9428c651e6574f93effed31d83fb9._comment |   10 -
 ...ent_3_9d8f9346b8c931815fa4967835b67560._comment |   21 -
 .../standalone_tarball_symlink_to_PATH_broken.mdwn |    9 -
 ...ent_1_c9b41b957df03fadf76d93b23508b85e._comment |    8 -
 ...ent_2_0cf22fe2518a52245ca4a8977aa3ed78._comment |    8 -
 doc/bugs/submodule_path_problem.mdwn               |   56 -
 ...ent_1_69aec9207d2e9da4bc042d3f4963d80e._comment |   48 -
 ...ent_2_53d9eb28cb70b51637470175a80ddf35._comment |    8 -
 ...ent_3_aa5e0f99000a5b4988bccbb2ca28353b._comment |   20 -
 ...ent_4_ab1508a5a04e2106aad5e7985775a6fa._comment |    8 -
 ...ent_5_8c7539d1c11b81f5d46aa8e1c61745ae._comment |   14 -
 ...ent_6_cacc91afcb1739dfca3a60590bb70356._comment |   67 -
 ...you_have_the_32bit_version_installed__41__.mdwn |   50 -
 ...ent_1_6208e70a21a048d5423926d16e32d421._comment |    9 -
 ...ent_2_8765b6190e79251637bb59ba28f245c1._comment |   21 -
 ...ies_to_copy_content_to_metadata_only_repos.mdwn |   34 -
 ...nect_new_remote_despite_not_being_asked_to.mdwn |   46 -
 ...ent_1_dcd52b57192e83fe365f21dc12461008._comment |   10 -
 doc/bugs/test_suite_failure_on_samba_mount.mdwn    |  281 --
 ...ent_1_e074b20801b921ee2661025a050a8af2._comment |   12 -
 .../test_suite_shouldn__39__t_fail_silently.mdwn   |    3 -
 ...there_is_no_global_.gitconfig_for_the_user.mdwn |   50 -
 ...uild_-_after_an_update_of_haskell_platform.mdwn |   23 -
 ...ent_1_20a6fe046111e9ae56fd4d9c9f41f536._comment |    8 -
 ...ent_2_6fdc5f8b07908c6eda8a97690408f44e._comment |   45 -
 ...ent_3_014474a133c7ff0131029d8721afc710._comment |   46 -
 ...ent_4_9c537e251dc99667fe87870804d802c2._comment |   10 -
 ...85211a41_disables_the_watch_command_on_OSX.mdwn |   22 -
 doc/bugs/three_character_directories_created.mdwn  |   56 -
 ...ent_1_dd91de24dab4f2eaded1f7d659869d4d._comment |    8 -
 ...ent_2_f6375964a6c8bb1e6c5b7238effca66d._comment |   62 -
 ...ent_3_776e0a9b938d8b260a5111594b442536._comment |    8 -
 ...ent_4_e288bacdb336c4886adb6eeb4dca1e92._comment |    8 -
 ...ent_5_359b80948ac92a0f1eb695599456486c._comment |   10 -
 doc/bugs/three_way_sync_via_S3_and_Jabber.mdwn     |  119 -
 ...nt_10_fc5ec5505f141bb9135e772d1094bc4d._comment |   12 -
 ...nt_11_0df2210c30dec6d88d7858d93eec19a3._comment |   10 -
 ...ent_1_41682b2e72e657e0f23af244f8345e85._comment |   10 -
 ...ent_2_c7b4ea9aea6839763eb8b89e8d6a5ad5._comment |   14 -
 ...ent_3_063f5e5e554ad6710f16394906d87616._comment |   33 -
 ...ent_4_197ad39b4a46936afeeb04eb26cf1ef3._comment |  138 -
 ...ent_5_0b0d829ccd255be0177ae9d8f6b10e63._comment |   61 -
 ...ent_6_37a8e19440c764317589bc4248cbccdf._comment |   10 -
 ...ent_7_12eb333327d31ca2bfee3f3c5e26d641._comment |   24 -
 ...ent_8_e6b1084b2f18d8e536c8692e165754a3._comment |   12 -
 ...ent_9_2120a1c3e5f490a55f68bb1bef5efd0d._comment |  183 -
 doc/bugs/tmp_file_handling.mdwn                    |   13 -
 ...ent_1_0300c11ee3f94a9e7c832671e16f5511._comment |   13 -
 ...ent_2_cc14c7a79a544e47654e4cd8abc85edd._comment |    8 -
 doc/bugs/transferkey_fails_due_to_gpg.mdwn         |   51 -
 ...ent_1_f6434400d528a0fa59c056995ff2e6f3._comment |   12 -
 ...ent_2_c540b05b62a3186a87efcb180ea2a52d._comment |   12 -
 ...ent_3_9ad2ef73169dbd2866da2f4259ab0f00._comment |    8 -
 ...ent_4_7631b8842efba6a4aad87386ce9443a7._comment |    8 -
 .../tweaks_to_directory_special_remote_doco.mdwn   |   80 -
 ...__ready_to_add_remote_server__34___message.mdwn |   16 -
 ...ins_of_missing_git-upload_and_receive_pack.mdwn |  208 --
 ...ent_1_8b0302bba2b99df0842dfead649080e7._comment |    8 -
 ...ninit_do_not_work_when_git_index_is_broken.mdwn |   17 -
 ...ent_1_1931e733f0698af5603a8b92267203d4._comment |    8 -
 ...ent_2_40920b88537b7715395808d8aa94bf03._comment |    8 -
 .../unannex_command_doesn__39__t_all_files.mdwn    |   30 -
 ...moves_object_even_if_referred_to_by_others.mdwn |   20 -
 ...ent_1_0ce72d0f67082f202cfa58b7c00f2fd3._comment |   39 -
 ...ent_2_647f49ffcaa348660659f9954a59b3ae._comment |   16 -
 ...ent_3_3f7f4b55b7ec2641a70109788e0b5672._comment |   10 -
 ...ent_4_313d393c416495aa0f8573113e41c2f7._comment |  431 ---
 ...ent_5_c0e7742672db2629bd906cebefe74f72._comment |   10 -
 ...ent_6_c56171665db3ed14109a09097d49ac5d._comment |    8 -
 doc/bugs/unannex_vs_unlock_hook_confusion.mdwn     |   15 -
 doc/bugs/unfinished_repos_in_webapp.mdwn           |   31 -
 ...ent_1_9628b100e39489be9f28ef75276a7341._comment |   11 -
 ...ent_2_ba0fbff536b1d067c4098db401dc49f2._comment |   10 -
 ...ent_3_fd554aa7d93117177784a29270ccf790._comment |   12 -
 doc/bugs/unhappy_without_UTF8_locale.mdwn          |   41 -
 doc/bugs/unicode_tags.mdwn                         |   49 -
 ...it_and_indirect_don__39__t_work_on_android.mdwn |   23 -
 ...ent_1_fec69c4c41987b9469eaa8f745c0a124._comment |    8 -
 ...ent_2_54c3fa77a069b36d03c41aad08fee9af._comment |    8 -
 ...es_not_abort_when_hard_link_creation_fails.mdwn |   47 -
 doc/bugs/uninit_does_not_work_in_old_repos.mdwn    |   20 -
 ...ent_1_bc0619c6e17139df74639448aa6a0f72._comment |    8 -
 ...data_if_git-annex_add_didn__39__t_complete.mdwn |   15 -
 ...t_run_when_branch_git-annex_is_checked_out.mdwn |   15 -
 ...ock_fails_silently_with_directory_symlinks.mdwn |   53 -
 ...ng_on_os_x_10.6_-_cp:_illegal_option_--_-_.mdwn |   22 -
 ...ent_1_a634a9f1c023bf836183de64abab1224._comment |   10 -
 ...ent_2_d9ae61a7c3f1eb243ca650945b40f21d._comment |   19 -
 ...ent_3_fe229c03c14e8eb2b57389e0e193ed99._comment |    8 -
 ...ent_4_fa12afe295de63c4aa7eb043b715325a._comment |   15 -
 ...ock_then_lock_of_uncommitted_file_loses_it.mdwn |    7 -
 ..._to_grab_archive_content_onto_client_again.mdwn |  434 ---
 ...nt_10_51097a6b84edcc607abc0e6e21ca21f2._comment |    8 -
 ...ent_1_c34a4009213c410bba3c147ae0552029._comment |   15 -
 ...ent_2_634542867fd28962c47b7bc3ea022175._comment |    8 -
 ...ent_3_301f3ff2d203ac4c58a037e553b2c14d._comment |   18 -
 ...ent_4_82ecdc88ccc1f87386b128adc4ff9af4._comment |   14 -
 ...ent_6_158b2ba3da815910505899606177d415._comment |   16 -
 ...ent_6_b068924802f3917e3e005350cb0cc2a2._comment |    8 -
 ...ent_7_f4772858c927d4a62edc3caf59b5da10._comment |    8 -
 ...ent_8_d0923d2950357f4444c5ef94ff196ba3._comment |    8 -
 ...ent_9_7fb30cb80aecc60e48c64846aa185206._comment |    9 -
 doc/bugs/utf8.mdwn                                 |  192 -
 ...nt_10_f298b8b480d3ab2dd9c279589afcd0ea._comment |   10 -
 ...nt_11_a8864a46f8154680beeea27449ac6f09._comment |  142 -
 ...nt_12_2202c3479d19d306f31aac5a47b55e7d._comment |   10 -
 ...nt_13_7044d2c5bb1c91ee37eb9868963a1ff2._comment |   41 -
 ...nt_14_656b3caa16ae93b092fb5804fa575a3b._comment |    8 -
 ...nt_15_25b3d4c47c45b72129b17b171a45c5f9._comment |    8 -
 ...nt_16_2aaab9253bbc75012292c7b5a7d55696._comment |  173 -
 ...ent_1_416ad6fb5f7379732129dc5283a7e550._comment |   23 -
 ...ent_2_cd55f6bbeb145fd554f331dcff64f5e1._comment |   10 -
 ...ent_3_bb583a419d6fa4e33e5364c4468b35c6._comment |    8 -
 ...ent_4_cd8a22cfb70d9d21f0a5339ccc52ee93._comment |   14 -
 ...ent_5_14eefd4bee283802e9c462fa20b7835c._comment |   19 -
 ...ent_6_58d8b5bdb9f11e8c344e86a675a075dd._comment |   11 -
 ...ent_7_00fa9672ce55b6bfa885b8a13287ac25._comment |   10 -
 ...ent_8_a01e26fa0fafbc291020f53dbfdf6443._comment |   10 -
 ...ent_9_b7c084be01ce985be51e48503fcba468._comment |    8 -
 ...g_trust.log_and_remote.log_merge_wackiness.mdwn |   36 -
 ..._even_though_the_content_has_the_same_hash.mdwn |   13 -
 ...ent_1_ffc5f79368b8927817e0e35a7a8f057b._comment |   12 -
 ...ent_2_1382b486d198d707db760ae119f33ad1._comment |    8 -
 ...ent_3_3c4074a1d4d7f63f6c07a05ca9717ce8._comment |    8 -
 ...ent_4_deb848e50f6767d8a5f4348137744ec2._comment |    8 -
 ...ent_5_b426c4569b7a788fbf963f787590e051._comment |   10 -
 ...Feeds__34___but_podcasting_feature_working.mdwn |   28 -
 ...ent_1_ce06ba4f65f322362b23797f6190c7c3._comment |   17 -
 ..._Internal_Server_Error__internal_liftAnnex.mdwn |   20 -
 ...ent_1_57547f9a480df2c3f7b3997b0fb7039a._comment |   12 -
 ...ent_2_99f12da3ef01141dc7a9105fcf966793._comment |   10 -
 ...on___40__handle_is_closed__41___on_Android.mdwn |   24 -
 ...ent_1_e8866dc15f8fc049229e7451addad1d5._comment |   12 -
 ...ent_2_ee616b0251ffaace9844cfd7af896c35._comment |   10 -
 ...ent_3_6b8bd314b647ea3a485f5faf4856f9a9._comment |   35 -
 ...ent_4_7009b6727ba40bc9bd1b1f939e75d093._comment |    8 -
 ...ent_5_00ddf7ade6cca758afa838be0b9588cb._comment |   20 -
 ...ent_6_6137ef0ad01d5600dab6fccbeed9a88b._comment |   14 -
 ...ent_7_4b79d7ea338d9f70eb80b8cc2c5a21e4._comment |    8 -
 ..._command_on_OSX_--_hangs_with_a_small_repo.mdwn |   41 -
 ...ent_1_63f04694610839db0c2381005b15da35._comment |   14 -
 ...ent_2_8afe4720e301cf7ccf11ff0a23261936._comment |    8 -
 doc/bugs/watch_command_on_OSX_10.7.mdwn            |   37 -
 doc/bugs/watcher_commits_unlocked_files.mdwn       |   37 -
 ...ent_1_f70e1912fde0eee59e208307df06b503._comment |    8 -
 doc/bugs/webapp_hang.mdwn                          |  144 -
 ...ent_1_08aa908a64d0fe2d50438d01545c3f01._comment |    8 -
 ...ent_2_2a21ac5657128a454f9deb77c4d18057._comment |   21 -
 ...erver_error_upon_creating_the_initial_repo.mdwn |   26 -
 ...ent_1_1bcf0f565eacac851bd21cd428c8e0a5._comment |   33 -
 ...ent_2_7dd2483b5b07df8f3b37a34651c05962._comment |    8 -
 ...p_requires_reload_for_notification_bubbles.mdwn |   41 -
 ...ent_1_b15480e5dec1ffbebb8cde1ca8d7c9d5._comment |   11 -
 ...ent_2_8dad57a852e1db804aa38f90f3bb398b._comment |    8 -
 ...shows___34__Added_x_files__34___a_bit_ugly.mdwn |   15 -
 doc/bugs/webapp_takes_100__37___of_the_cpu.mdwn    |   46 -
 ...ent_1_6312860de9f30cbb05762cd67edc705a._comment |    8 -
 ...pp_usability:_put_the_notices_on_the_right.mdwn |   18 -
 ...ent_1_ec7a444e09a028b5225bd41fb83442e8._comment |    9 -
 ...emote_fails_on_android___40__box.com__41__.mdwn |   32 -
 ...ent_1_f57757b4bcc4ace73bf660419d944c33._comment |    8 -
 doc/bugs/weird_local_clone_confuses.mdwn           |   20 -
 doc/bugs/wget_tarball_over_https_complains.mdwn    |   15 -
 ...ent_1_4227a75f2eb0de6a2422efe8d791e130._comment |   10 -
 ...ent_2_25fb35b2e707b174f255a1dafca8eff9._comment |   10 -
 ...ndows_fails_test___34__recoverEncode__34__.mdwn |   39 -
 ...ent_1_424b3536e21e02f192f7f2b8e833ed18._comment |   67 -
 ...ent_2_78db183aa401e2023d7faec5f7a4a573._comment |   10 -
 ...ent_3_ed2da19eaf0bd0864f6b28816a79bc23._comment |    8 -
 ...ws_port_-_can__39__t_directly_access_files.mdwn |  250 --
 ...ent_1_03ef9d33839173044dcc4f2b37f575d2._comment |    8 -
 ...ent_2_c65e5491c82908af46fe2c97e048d210._comment |   20 -
 ...angs_when_adding_17_files_at_once_or_more_.mdwn |  197 -
 ..._-_repo_can__39__t_pull_newly_added_files_.mdwn |  559 ---
 ...nt_10_b4f5e2d6a0d690f6b0089fa80a3c920b._comment |    8 -
 ...ent_1_c2092add1430667108a3fdc5e1c9b5f5._comment |    8 -
 ...ent_2_f0ea453951daf84dbddc653ac64822b6._comment |    8 -
 ...ent_3_35a8be5ecc9d1b72c38f8ddb47678160._comment |    8 -
 ...ent_4_29e72997b88f91f84639587b4cede34c._comment |   76 -
 ...ent_5_2de7f6532de4cbc21737ce53a89d6525._comment |   10 -
 ...ent_6_80d130b5af829763be77c61a9c5ca306._comment |   29 -
 ...ent_7_ec199db851952b40e8b18922da574ea4._comment |    8 -
 ...ent_8_d269fcadea9d5a668e3c6d6cf019f56a._comment |  353 --
 ...ent_9_908d1b981d56107f29d8972bf11aefc8._comment |   12 -
 ...___47__.config__47__git-annex__47__program.mdwn |   20 -
 ...ent_1_44c11918d00ead38d40556aade98c0af._comment |   12 -
 doc/bugs/xdg-user-dir_error.mdwn                   |    8 -
 ..._needs_one_account_per_distinct_repository.mdwn |  107 -
 ...ent_1_820732c4dcb15186b4f635c50fdb0805._comment |   19 -
 .../yesod-default_is_needed_as_a_dependancy.mdwn   |   10 -
 doc/bugs/yesod-form_missing.mdwn                   |   23 -
 doc/todo/Allow_syncing_only_selected_branches.mdwn |    8 -
 ...ent_1_bb687b1a50d8a926abd16ada639140e1._comment |   18 -
 ...ent_2_46d27fe74b4adac2e740fa555f549459._comment |   18 -
 doc/todo/Build_for_Synology_DSM.mdwn               |    4 -
 ...nt_10_e351084d9a83db3fd6d9d983227a6410._comment |    8 -
 ...nt_11_cc67a584f5c460a6fb63cf099c20e573._comment |    9 -
 ...nt_12_94023593d294b9cf69090fcfd6ca0e5a._comment |    9 -
 ...nt_13_314255fd503d125b5aeae2f62acfd592._comment |    8 -
 ...nt_15_9525cd0d75ff4c15182d10a855774b69._comment |   30 -
 ...nt_15_c12f525ef4cbe42cdf20fec0d53c8d86._comment |   10 -
 ...ent_1_4059016fa8da6af7a3eba8966821e8eb._comment |   10 -
 ...ent_2_8900c2985ab68b3b566c9f5d326471d6._comment |    8 -
 ...ent_3_f2b77368473d42b7f21e9d51d6415b58._comment |   10 -
 ...ent_4_a55fea734044c270ceb10adf9c8d9a76._comment |    8 -
 ...ent_5_59865ada057c640ac29855c65cf45dd9._comment |   23 -
 ...ent_6_6d860b1ad8816077b5fa596a71b12d5c._comment |    8 -
 ...ent_7_19ef2d293ba3bc7ece443d7278371c3f._comment |    8 -
 ...ent_8_609b7ad87dfbba49ec1f8c6fc2739ccd._comment |   12 -
 ...ent_9_d94a73b9a07c5cadf191005f817fd59a._comment |   29 -
 ...k_if_an_upgrade_is_available_in_the_webapp.mdwn |    5 -
 ...ent_1_c904182f6bff8b1a42070bbc038eb34e._comment |   17 -
 ...ent_2_ebe7a75ca291e7f749bfe9f46d10909d._comment |    8 -
 doc/todo/Enhancement:_git_annex_whereis_KEY.mdwn   |   19 -
 ...ent_1_5d768ab0065e6ecbc8ea25d66c226758._comment |    8 -
 ...ent_2_4189d9e91208a59381100613e254e731._comment |    8 -
 ...Feature_Request:_Sync_Now_Button_in_Webapp.mdwn |    3 -
 ...ent_1_0d5c90eb0e8fe61b82a19c5fea343613._comment |    8 -
 ...ent_2_196552002d70390e8b52b4af61dca903._comment |    8 -
 doc/todo/Limit_file_revision_history.mdwn          |  117 -
 .../Option_for_browser_to_launch_webapp_with.mdwn  |    7 -
 ...abort_build_if___34__make_test__34___fails.mdwn |    7 -
 ...Please_add_support_for_monad-control_0.3.x.mdwn |    9 -
 ...satisfy__95__num__95__copies__34___command.mdwn |   16 -
 doc/todo/S3.mdwn                                   |   24 -
 doc/todo/Sync_repo_names__63__.mdwn                |   10 -
 ...Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn |   18 -
 ...ent_1_a93805a8088402c6dc32d2b9785fcc7d._comment |   10 -
 doc/todo/Wishlist:_Import_youtube_playlists.mdwn   |   30 -
 ...ent_1_4235cbbb0c6f9d83524c970c4588cb2e._comment |    9 -
 ...rce_directory_and_also_in_the_target_annex.mdwn |   29 -
 ...ent_1_0cc16eb17151309113cec6d1cccf203d._comment |   20 -
 ...7__version__96___should_print_the_local_OS.mdwn |    6 -
 ...__44___tracking_info__44___and_actual_data.mdwn |    6 -
 .../add_--exclude_option_to_git_annex_find.mdwn    |    4 -
 doc/todo/add_-all_option.mdwn                      |   22 -
 doc/todo/add_a_git_backend.mdwn                    |   18 -
 doc/todo/add_an_icon_for_the_.desktop_file.mdwn    |    3 -
 doc/todo/add_metadata_to_annexed_files.mdwn        |   14 -
 ...ent_1_38af9b352020194e9ace34d7dde188cf._comment |   10 -
 doc/todo/assistant_git_sync_laddering.mdwn         |   10 -
 ...sistant_smarter_archive_directory_handling.mdwn |   31 -
 doc/todo/assistant_threaded_runtime.mdwn           |   40 -
 doc/todo/auto_remotes.mdwn                         |   29 -
 doc/todo/auto_remotes/discussion.mdwn              |    7 -
 doc/todo/automatic_bookkeeping_watch_command.mdwn  |   15 -
 doc/todo/avoid_unnecessary_union_merges.mdwn       |   20 -
 doc/todo/backendSHA1.mdwn                          |    7 -
 doc/todo/branching.mdwn                            |  159 -
 doc/todo/checkout.mdwn                             |   23 -
 doc/todo/direct_mode_guard.mdwn                    |  105 -
 ...ent_1_431b6e1577bbd30b07dce9002a8fe1a2._comment |   10 -
 ...ent_2_85bdb9dc601b87bd7c77150d7b0a5cde._comment |    8 -
 ...dir_remote___40__e.g._for_NAS_mounts__41__.mdwn |    7 -
 ...ent_1_5ed9a2336b432b842c1805add6d96509._comment |   10 -
 ...ent_2_e6ba58c5c31ba23a4575f1189689946f._comment |    8 -
 ...ent_3_e53cbc5765819de2d3c742e6cd4d77cd._comment |   11 -
 doc/todo/exclude_files_on_a_given_remote.mdwn      |   18 -
 doc/todo/faster_gnupg_cipher.mdwn                  |    9 -
 ...ent_1_8f61f7c724a8224e61c015be68f43db7._comment |   14 -
 ...ent_2_36e1f227a320527653500b445f7c001c._comment |   12 -
 ...ent_3_bd0c975494333dfe558de048d888ace8._comment |   17 -
 doc/todo/faster_rsync_remotes.mdwn                 |    4 -
 ...ent_1_0bc3ee0ae563357675eeccf42461e59a._comment |    8 -
 ...ent_2_ccf6f75450c89ca498c8130054f8d32d._comment |   24 -
 ...ent_3_2f6a9d23cb8351fbf0f60ed93752e76e._comment |   14 -
 ...ent_4_3a2f45defebae3dde336ee5f40c26d7e._comment |    8 -
 doc/todo/file_copy_progress_bar.mdwn               |    5 -
 doc/todo/fsck.mdwn                                 |   11 -
 doc/todo/fsck_special_remotes.mdwn                 |   13 -
 doc/todo/git-annex-shell.mdwn                      |   15 -
 doc/todo/git-annex_unused_eats_memory.mdwn         |   32 -
 ...ription_and__47__or_UUID_in_commit_message.mdwn |   13 -
 doc/todo/gitolite_and_gitosis_support.mdwn         |   39 -
 doc/todo/gitrm.mdwn                                |    5 -
 doc/todo/http_git_annex_404_retry.mdwn             |   18 -
 doc/todo/http_headers.mdwn                         |    8 -
 doc/todo/immutable_annexed_files.mdwn              |    8 -
 doc/todo/incremental_fsck.mdwn                     |   24 -
 ...ent_1_609b21141dd5686b2c0eaef2b8d63229._comment |   14 -
 doc/todo/link_file_to_remote_repo_feature.mdwn     |   52 -
 ...ate__34___valid_importfeed_template_option.mdwn |   18 -
 ...ent_1_9fa523d1eabb6e029a91413770e9af72._comment |   16 -
 ...ent_2_9090bb66713f48fbdd1e2a3f1292b7ba._comment |    8 -
 doc/todo/makefile:_respect___36__PREFIX.mdwn       |   25 -
 doc/todo/mdwn2man:_make_backticks_bold.mdwn        |   22 -
 doc/todo/network_remotes.mdwn                      |    5 -
 doc/todo/nicer_whereis_output.mdwn                 |  100 -
 doc/todo/object_dir_reorg_v2.mdwn                  |   25 -
 ...ent_1_ba03333dc76ff49eccaba375e68cb525._comment |    8 -
 ...ent_2_81276ac309959dc741bc90101c213ab7._comment |    8 -
 ...ent_3_79bdf9c51dec9f52372ce95b53233bb2._comment |   12 -
 ...ent_4_93aada9b1680fed56cc6f0f7c3aca5e5._comment |   12 -
 ...ent_5_821c382987f105da72a50e0a5ce61fdc._comment |   12 -
 ...ent_6_8834c3a3f1258c4349d23aff8549bf35._comment |   10 -
 ...ent_7_42501404c82ca07147e2cce0cff59474._comment |   12 -
 .../optinally_transfer_file_unencryptedly.mdwn     |    6 -
 ...ent_1_4be47e7ac85d0f4e7029a96b615545a7._comment |    8 -
 doc/todo/preferred_content_numcopies_check.mdwn    |   86 -
 doc/todo/pushpull.mdwn                             |    4 -
 doc/todo/quvi_0.9_support.mdwn                     |    8 -
 doc/todo/rsync.mdwn                                |    4 -
 ...nc_bwlimit_options_for_upload_and_download.mdwn |    4 -
 doc/todo/special_remote_for_amazon_glacier.mdwn    |   30 -
 ...ent_1_68f129441eefcbfebf7a9db680f52759._comment |    8 -
 ...ent_2_c5eeaf8ceee414fa0379831ca52e290c._comment |    7 -
 doc/todo/speed_up_fsck.mdwn                        |   40 -
 doc/todo/support-non-utf8-locales.mdwn             |   26 -
 doc/todo/support_for_lossy_remotes.mdwn            |   11 -
 ...ent_1_f5cd9f9deab13ab2d2290ad763906dd3._comment |    8 -
 ...pport_for_writing_external_special_remotes.mdwn |   27 -
 doc/todo/support_fsck_in_bare_repos.mdwn           |   17 -
 doc/todo/symlink_farming_commit_hook.mdwn          |   14 -
 ...__47__.local__47__bin_for_prebuilt_package.mdwn |   22 -
 doc/todo/untracked_remotes.mdwn                    |   27 -
 ...ent_1_ccc743554cf9270e1db5275273b28265._comment |   43 -
 ...ent_2_48cc5d0e2282fa53625e0037a035fee3._comment |   18 -
 ...ent_3_0d07c5bc8d42f35351c11411eaca88df._comment |   29 -
 ...ent_4_75ae13c2135a2951b2af548139cb25cd._comment |   46 -
 doc/todo/use_cp_reflink.mdwn                       |    7 -
 doc/todo/using_url_backend.mdwn                    |   11 -
 doc/todo/whishlist:_git_annex_drop_--dry-run.mdwn  |    5 -
 ...ent_1_20ecfa8ffa52c238d21b904076ac69a2._comment |   10 -
 ...ent_2_d19bc268c9467d24baa8d8f77a6e5e09._comment |    8 -
 ...allow_setting_annex-ignore_from_the_webapp.mdwn |    4 -
 ...ent_1_b3b5c12f89a0a6a91d681c67e2217199._comment |    8 -
 ...ist:_Add_to_Android_version_to_Google_Play.mdwn |    9 -
 .../wishlist:_An_--all_option_for_dropunused.mdwn  |    4 -
 ...ent_1_d8726d108b3b40116b4ec3c9935f2dff._comment |    8 -
 ...ent_2_578248f7686ba2d80d7dc8b17c0cdf52._comment |   16 -
 doc/todo/wishlist:_An_option_like_--git-dir.mdwn   |    5 -
 ...ent_1_5d877d90b8bdf21d4b8649744d229efd._comment |    8 -
 ...ent_2_462264821cbc48a433330cbf7ec6044d._comment |    8 -
 ...ent_3_0c3709b07a0a1091ceeee73b69e0f7ac._comment |    8 -
 doc/todo/wishlist:_GnuPG_options.mdwn              |   16 -
 ...ent_1_6662e8a71ce20acc62147ef41ecffa50._comment |   12 -
 ..._Have_a_preview_of_download_or_upload_size.mdwn |   10 -
 ...ent_1_019a2457e07377510feaa089a93bd76c._comment |    8 -
 ...ent_3_29a154699339bf040af0ee8aa24034f1._comment |   15 -
 ...ent_3_8f7e1c4a5c714cbd719ee170354d79fa._comment |   12 -
 ...ent_4_c7335f757e5546aa841cab38fffe7605._comment |   19 -
 ...ent_5_d2a845354f23d07880612740cf99ddd4._comment |    8 -
 ..._repeated_password_prompts_for_one_command.mdwn |   45 -
 ...ent_1_3f9c0d08932c2ede61c802a91261a1f7._comment |   14 -
 ...ex__34___command_that_will_skip_duplicates.mdwn |   28 -
 ...nt_10_d78d79fb2f3713aa69f45d2691cf8dfe._comment |   68 -
 ...nt_11_4316d9d74312112dc4c823077af7febe._comment |    8 -
 ...nt_12_ed6d07f16a11c6eee7e3d5005e8e6fa3._comment |    8 -
 ...ent_1_fd213310ee548d8726791d2b02237fde._comment |   29 -
 ...ent_2_4394bde1c6fd44acae649baffe802775._comment |   18 -
 ...ent_3_076cb22057583957d5179d8ba9004605._comment |   18 -
 ...ent_4_f120d1e83c1a447f2ecce302fc69cf74._comment |   35 -
 ...ent_5_5c30294b3c59fdebb1eef0ae5da4cd4f._comment |   10 -
 ...ent_6_f24541ada1c86d755acba7e9fa7cff24._comment |   16 -
 ...ent_7_c39f1bb7c61a89b238c61bee1c049767._comment |   54 -
 ...ent_8_221ed2e53420278072a6d879c6f251d1._comment |    8 -
 ...ent_9_aecfa896c97b9448f235bce18a40621d._comment |   14 -
 ..._40__not__41___to_annex_via_.gitattributes.mdwn |    9 -
 ...34__git_annex_add__34___multiple_processes.mdwn |   10 -
 ...ent_1_85b14478411a33e6186a64bd41f0910d._comment |   10 -
 ...ent_2_82e857f463cfdf73c70f6c0a9f9a31d6._comment |    8 -
 ...ent_3_8af85eba7472d9025c6fae4f03e3ad75._comment |    8 -
 ...fy_checksums_but_disregard_annex.numcopies.mdwn |   12 -
 ...ent_1_6bcf067e4860bdfeb1d7b9fd1702a43a._comment |    8 -
 ...__--_An_easy_way_to_get_data_into_an_annex.mdwn |   13 -
 ...ent_1_b9fd1bfaf9a3d238fdb7bc9c2d75fe5f._comment |   22 -
 ...ent_2_56f6972413c6f0d9f414245b6f4d27b9._comment |   62 -
 ...ent_3_2c094bef802a2182de4fcd0def1ad29b._comment |   12 -
 ...ent_4_14915c43001f7f72c9fe5119a104ef5c._comment |   10 -
 ..._needed___40__e.g.__44___with_WebDAV__41__.mdwn |   29 -
 ...ent_1_f46b0c9b49607e9f4f7a27f5a331ce83._comment |    8 -
 ...ent_2_1b34e1dd72011c65e881dec2543a0373._comment |   12 -
 doc/todo/wishlist:_addurl_https:.mdwn              |   11 -
 ...ent_1_4e8f5e1fc52c3000eb2a1dad0624906e._comment |   14 -
 ...low_configuration_of_downloader_for_addurl.mdwn |    3 -
 ...ote_to_be_accissable_via_different_methods.mdwn |    5 -
 ...ent_1_abb6263f3807160222bba1122475c89c._comment |    8 -
 ...ID_when_running___96__git_annex_init__96__.mdwn |    5 -
 ...nt_autostart_port_and_secret_configuration.mdwn |    4 -
 ...ent_1_be53b8456eed7eadad5d4b8465c8a42b._comment |   10 -
 doc/todo/wishlist:_command_options_changes.mdwn    |   17 -
 ...ent_1_bfba72a696789bf21b2435dea15f967a._comment |   17 -
 ...ent_2_f6a637c78c989382e3c22d41b7fb4cc2._comment |   19 -
 ...ent_3_bf1114533d2895804e531e76eb6b8095._comment |    8 -
 ...t:_define_remotes_that_must_have_all_files.mdwn |   22 -
 ...ent_1_cceccc1a1730ac688d712b81a44e31c3._comment |   10 -
 ...ent_2_eec848fcf3979c03cbff2b7407c75a7a._comment |   16 -
 .../wishlist:_detection_of_merge_conflicts.mdwn    |   13 -
 ...t_when_addWatcher_gets_a_permission_denied.mdwn |    6 -
 ...ent_1_d2665e7347689b520d37561cfddf0aa8._comment |    8 -
 ...ent_2_db153571a32fb072453ed583e3e9ccf4._comment |    8 -
 doc/todo/wishlist:_dropping_git-annex_history.mdwn |   28 -
 ...ent_1_a4bee2e26b22a9bdaadc05b7227769ef._comment |   10 -
 ...ent_2_f6d750bfe0c9d8a2aa6bc218ca5c49cc._comment |   14 -
 doc/todo/wishlist:_git-annex_replicate.mdwn        |   22 -
 ...ent_1_9926132ec6052760cdf28518a24e2358._comment |   10 -
 ...ent_2_c43932f4194aba8fb2470b18e0817599._comment |   12 -
 ...ent_3_c13f4f9c3d5884fc6255fd04feadc2b1._comment |   10 -
 ...ent_4_63f24abf086d644dced8b01e1a9948c9._comment |    8 -
 ...t:_git_annex_group_remote_return_the_group.mdwn |   11 -
 ..._put_--_same_as_get__44___but_for_defaults.mdwn |   20 -
 ...ent_1_d5413c8acce308505e4e2bec82fb1261._comment |   10 -
 ...ent_2_0aa227c85d34dfff4e94febca44abea8._comment |   12 -
 ...ent_3_2082f4d708a584a1403cc1d4d005fb56._comment |   10 -
 doc/todo/wishlist:_git_annex_status.mdwn           |   21 -
 ...ent_1_994bfd12c5d82e08040d6116915c5090._comment |    8 -
 ...ent_2_c2b0ce025805b774dc77ce264a222824._comment |   13 -
 ...ent_3_d1fd70c67243971c96d59e1ffb7ef6e7._comment |   23 -
 ...ent_4_9aeeb83d202dc8fb33ff364b0705ad94._comment |    8 -
 doc/todo/wishlist:_git_backend_for_git-annex.mdwn  |    9 -
 ...ent_1_04319051fedc583e6c326bb21fcce5a5._comment |   10 -
 ...ent_2_7f529f19a47e10b571f65ab382e97fd5._comment |   14 -
 ...ent_3_a077bbad3e4b07cce019eb55a45330e7._comment |   10 -
 ...ent_4_ecca429e12d734b509c671166a676c9d._comment |    8 -
 ...ent_5_3459f0b41d818c23c8fb33edb89df634._comment |    8 -
 ...s_twice_the_size_of_repo_to_complete__41__.mdwn |   10 -
 ...ent_1_067b29fc47d26b9da0766f9810684ae8._comment |   10 -
 doc/todo/wishlist:_metadata_metadata_view.mdwn     |   23 -
 ...ent_1_79dbf48cf2e0d649f32bd077f0c9bc5a._comment |    8 -
 ...ent_2_5763d0e403c476ac692c1cd50630f824._comment |   12 -
 ...ent_3_797e6578c60d8e2ed1f61a8d6403575f._comment |    8 -
 ...ent_4_d271fe711b3fe5ffeb52f1caf44622b3._comment |   10 -
 ...iptive_commit_messages_in_git-annex_branch.mdwn |   55 -
 ...option_to_disable_url_checking_with_addurl.mdwn |    9 -
 ...ent_1_868a380faa1e55faa3c2d314e3258e86._comment |   10 -
 ...te__39__s_repo__44___not_your_personal_one.mdwn |    3 -
 ...ent_1_3480b0ec629ef29a151408d869186bf8._comment |    8 -
 ..._things_like_description__44___trust_level.mdwn |    4 -
 ...ent_1_14311384788312b96e550749ab7de9ea._comment |   10 -
 ...ent_2_342d1ac07573c7ef4e27f003a692e261._comment |   32 -
 doc/todo/wishlist:_simple_url_for_webapp.mdwn      |   36 -
 ...ent_1_552aad504fbb68d1f85abfde8c535e69._comment |   10 -
 doc/todo/wishlist:_simpler_gpg_usage.mdwn          |   12 -
 ...ent_1_6923fa6ebc0bbe7d93edb1d01d7c46c5._comment |   19 -
 ...ent_2_6fc874b6c391df242bd2592c4a65eae8._comment |   10 -
 ...ent_3_012f340c8c572fe598fc860c1046dabd._comment |    8 -
 ...ent_4_e0c2a13217b795964f3b630c001661ef._comment |   10 -
 ...ent_5_9668b58eb71901e1db8da7db38e068ca._comment |    8 -
 ...ling_of_Youtube_URLs_in_Web_special_remote.mdwn |   22 -
 ...ent_1_1a383c30df4fb1767f13d8c670b0c0b5._comment |   10 -
 ...ent_2_81f7f893ac36c145b31f02db6a682a17._comment |   20 -
 ...ent_3_a7e3cd68c5e5f05139151a58f358df95._comment |   13 -
 ...ent_4_a57947ed257b28bbe995a68bfeb5eeaa._comment |    8 -
 ...ent_5_a0612ae05dbda7f7935be648b42b30fc._comment |    8 -
 ...wishlist:_special_remote_for_sftp_or_rsync.mdwn |   28 -
 ...ent_1_6f07d9cc92cf8b4927b3a7d1820c9140._comment |   10 -
 ...ent_2_84e4414c88ae91c048564a2cdc2d3250._comment |    8 -
 ...ent_3_79de7ac44e3c0f0f5691a56d3fb88897._comment |    8 -
 doc/todo/wishlist:_special_remote_mega.co.nz.mdwn  |    3 -
 ...ent_2_6ca08ef808d4336fc42d0f279d6627b5._comment |   44 -
 ...st:_support_copy_--from__61__x_--to__61__y.mdwn |   29 -
 ...ent_1_cf8e0f16b723516374c95a93e4da42fc._comment |   12 -
 ...ent_2_d35359c9dd4dd4365d9a7caf695ff833._comment |   16 -
 ...support_drop__44___find_on_special_remotes.mdwn |   18 -
 ...ent_1_f11ed642a83d965076778a162f701e84._comment |    8 -
 doc/todo/wishlist:_support_for_more_ssh_urls_.mdwn |   22 -
 ...rectory_into_a_git-annex_direct_repository.mdwn |   29 -
 ...ent_1_d48a98bad77400bd8384300e324d999f._comment |    8 -
 ...ent_2_1a1d15531c74eb0cc09f81dc09d95d39._comment |   10 -
 ...ent_3_66ceb7c793a2dbbd755b9595a2199aca._comment |    8 -
 .../wishlist:_vicfg_possible_repo_group_names.mdwn |   16 -
 1970 files changed, 56952 deletions(-)
 delete mode 100644 doc/bugs/127.0.0.1_references_on_remote_assistant_access.mdwn
 delete mode 100644 doc/bugs/3.20121112:_build_error_in_assistant.mdwn
 delete mode 100644 doc/bugs/3.20121112:_build_error_in_assistant/comment_1_b42f40ffd83321ab5cc0ef24ced15e98._comment
 delete mode 100644 doc/bugs/3.20121112:_build_error_in_assistant/comment_2_b1d2aa10ea84c5c370b3e76507fc8761._comment
 delete mode 100644 doc/bugs/3.20121112:_build_error_in_assistant/comment_3_b38e40d36bba95b16afbce68e7f25a80._comment
 delete mode 100644 doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04.mdwn
 delete mode 100644 doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_1_ce2efd2196e7682f4cdbabdb0616d449._comment
 delete mode 100644 doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_2_2a6faf662ebb85a8f1c89adcdfb9adb6._comment
 delete mode 100644 doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_3_37f34baa34068def1adf794d0942e462._comment
 delete mode 100644 doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_4_2f8a859fef9edc8eb93bf1cc74296702._comment
 delete mode 100644 doc/bugs/3.20121113_build_error___39__not_in_scope_getAddBoxComR__39__.mdwn
 delete mode 100644 doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build.mdwn
 delete mode 100644 doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build/comment_1_b7140e2bf1ea9c73ecc9e214095968e7._comment
 delete mode 100644 doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build/comment_2_6be87b2fb2ed828e7b4bf785729e910e._comment
 delete mode 100644 doc/bugs/4.20130601_xmpp_sync_error.mdwn
 delete mode 100644 doc/bugs/4.20130601_xmpp_sync_error/comment_1_5b50d97e44cbd5b31ff24537ec3f8603._comment
 delete mode 100644 doc/bugs/400_mode_leakage.mdwn
 delete mode 100644 doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop.mdwn
 delete mode 100644 doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_1_81839a6de7450734ee75b51e47a0898e._comment
 delete mode 100644 doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_2_907ce31a31df94984c2bd7aaafe5b10b._comment
 delete mode 100644 doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_3_d8a86ae0ae5fa1f91e0b40b8b2ba0406._comment
 delete mode 100644 doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_4_1f08fd5dd4f5d8723c2b5391cc3b60f9._comment
 delete mode 100644 doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one.mdwn
 delete mode 100644 doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one/comment_1_cb781d34889d583663e855c4074f8e0e._comment
 delete mode 100644 doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one/comment_2_c0c87957d7c7a09664e60571a2ca0e8c._comment
 delete mode 100644 doc/bugs/Adding_box.com_remote_on_Android_fails_for_me.mdwn
 delete mode 100644 doc/bugs/Adding_box.com_remote_on_Android_fails_for_me/comment_1_0303ce880415d7e043533551c2b24694._comment
 delete mode 100644 doc/bugs/Adding_git_ssh_remote_fails.mdwn
 delete mode 100644 doc/bugs/Adding_git_ssh_remote_fails/comment_1_05c0bd9ac7c6f0045217fd72fc1f0a1b._comment
 delete mode 100644 doc/bugs/Adding_git_ssh_remote_fails/comment_2_df05456cafdd89e8ceea830199f42d45._comment
 delete mode 100644 doc/bugs/Adding_second_remote_repository_over_ssh_fails.mdwn
 delete mode 100644 doc/bugs/Adding_second_remote_repository_over_ssh_fails/comment_1_308d5f517bf00c8edc53db438de52355._comment
 delete mode 100644 doc/bugs/Adding_unencrypted_repo_on_drive_in_webapp_gives_internal_server_error__.mdwn
 delete mode 100644 doc/bugs/Addurl_with_quvi_not_working.mdwn
 delete mode 100644 doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote.mdwn
 delete mode 100644 doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote/comment_1_13ecedfbb34c3564af3a790b8bf0f591._comment
 delete mode 100644 doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__.mdwn
 delete mode 100644 doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_1_91787407727f7ed833d5970d3226d0cb._comment
 delete mode 100644 doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_2_f4c52fe33e9c4c107c2469fabb0c6826._comment
 delete mode 100644 doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_3_20c1f9399321dd85cb584b8845140b1d._comment
 delete mode 100644 doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_4_d92c30061e087878a2462b5a2e495346._comment
 delete mode 100644 doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing.mdwn
 delete mode 100644 doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing/comment_1_a9b03d4f4760fea2754a4dc93547f0a3._comment
 delete mode 100644 doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing/comment_2_015e859a16b1ce4c0c7601df0594d555._comment
 delete mode 100644 doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password..mdwn
 delete mode 100644 doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_1_c973032e0b780bd3b26bf1f744f04082._comment
 delete mode 100644 doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_2_9ef5c13a7a28e9098a837d42e5c4c964._comment
 delete mode 100644 doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_3_0c8087dfbcd8811913e7b3b6376cab90._comment
 delete mode 100644 doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_4_8ad9047dd136e3b438fb9a6d50ecb04c._comment
 delete mode 100644 doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_5_5f478c24065fc9a50a1cff3148b83bec._comment
 delete mode 100644 doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__.mdwn
 delete mode 100644 doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__/comment_1_c034bb84e58b2dda1038ba205ec78c56._comment
 delete mode 100644 doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__/comment_2_99a754f41d59fdd401ba6d169945e7c9._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup.mdwn
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_10_dc06737997c8883ef0a12dbecd9ac30f._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_11_b444cd6717658116533745c51481dd3d._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_12_66181f34ed7496d1f6601b39e5ae3c65._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_1_ddf5761bf14de30ac97030ad338601ae._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_2_8b9fafa73ebf5f803c7da9531cfb5b34._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_3_58501bb043b4c5836d7472ffd6baa72c._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_4_d3a04dc7bbc1816cccc8d85c73ffb689._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_5_eeabbc0cc434ed84c36a3f4e03fcef36._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_6_4203b496bee1bdd424466ed63b5d31cf._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_7_74373eb2cc46b76659e3c463d6682d15._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_8_0923d2a09df01d152ec4784c92689c96._comment
 delete mode 100644 doc/bugs/Android_app_permission_denial_on_startup/comment_9_b60928e54a5b620899cf29820b9b8e70._comment
 delete mode 100644 doc/bugs/Android_daily_build_missing_webapp.mdwn
 delete mode 100644 doc/bugs/Android_version_apparently_unable_to_run_sha256sum.mdwn
 delete mode 100644 doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_1_51316a0a0d80cf8f9ee37b2eca64323d._comment
 delete mode 100644 doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_2_14341ee188b1248f68164b1d9aa4c929._comment
 delete mode 100644 doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_3_8624567ebc3af967fb59bad5a3fb6659._comment
 delete mode 100644 doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_4_84aed89077d339f5471f113a1bcc4306._comment
 delete mode 100644 doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_5_e1e6707042e52a1f07276c27af651339._comment
 delete mode 100644 doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_6_f28f65901c46d9543797f698b0eedb63._comment
 delete mode 100644 doc/bugs/Annex_thinks_file_exists_afer_being_dropped.mdwn
 delete mode 100644 doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_1_1d100441fd1ef529eb854b350fece9ee._comment
 delete mode 100644 doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_2_166c459c2b27859cf457e17da685fe75._comment
 delete mode 100644 doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_3_9d985b6e7973bfaaf8b4f5349d8c13ee._comment
 delete mode 100644 doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_4_3e084cff454b95c7170c0225a53f0c30._comment
 delete mode 100644 doc/bugs/Assistant_does_not_actually_check_newly_annex-added_files_into_git_until_daily_sanity_check.mdwn
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default.mdwn
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_1_8577fdaa4d49e6241c4372b159694c9c._comment
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_2_027521e48283c68b39315bb8213f6e45._comment
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_3_fd8f6938596aace60b04fb35c4069e37._comment
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_4_ca908021ab5a2a50fd0d4a7e8d12498f._comment
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_5_73532556cfc354ad5f37a3f3a048fb32._comment
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_6_ced397b9e6119a0798a282ee07e885df._comment
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_7_8acb66850e5db8337cf3f2b2dd236ccc._comment
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_8_7eb530851ae6fa1a69813725c4e8fcec._comment
 delete mode 100644 doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_9_c7d51a26e1febc3894d02546940d64e5._comment
 delete mode 100644 doc/bugs/Assistant_dropping_files_it_has_just_transferred_elsewhere_again.mdwn
 delete mode 100644 doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log.mdwn
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_10_b47d543e06a1a243211a2fa0cb5d09a3._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_11_399c1e4455dce105df95414fe3ff939d._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_12_1cfdd76e751ee3726bd80359cfc85c47._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_13_37aa5274874242861dc128efa1d29486._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_1_27fc71cadcbe6d5f146ffdb72b64689a._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_2_0fb01ff463e7da6df2864186dc28f8e4._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_3_10fa5082909f5e568623cf6d901d5161._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_4_f4e0fa25b7f466228622a6da02b157e7._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_5_6b9b87bfb8b94171b3dba51919fd1ceb._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_6_51f35f069c95a5ea7bd4dbab47b5702b._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_7_691661d902acbf9c11d713541d5d39e4._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_8_ef559feb7b350f2014055680d087c2bc._comment
 delete mode 100644 doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_9_278b41aaa73a214b2b38881242a29b17._comment
 delete mode 100644 doc/bugs/Assistant_redirects_to_127.0.0.1_in_some_cases__44___although_used_remotely.mdwn
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux.mdwn
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_10_ec4a7388ea7106a953f599b664b37f1d._comment
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_1_6a60c23850a5e2a7bba355e1317abc69._comment
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_2_90b6ed232b2917b9fe041532284e1212._comment
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_3_5a89d79395d96c43d7d8a6fd9dc275f1._comment
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_4_cdd26c71875428dbe3c100944a443d3f._comment
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_5_76242f5d6c815acd5bd58213bd8bb0fe._comment
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_6_10852171c0207ca61ea6df1082107353._comment
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_7_73e8a5696709f8154e63693ba5e569c3._comment
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_8_392fc344e5833b0eb665fcd38f956b7a._comment
 delete mode 100644 doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_9_9f0fc19a7fcaf7a5827e59e1495cf8c9._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor.mdwn
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_10_0e1db417a5815ea903c1f7ccd07308c4._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_1_28b0cfcba8902c9c16dbe6c4b07984c4._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_2_952b3f78da756ff5f89235db94bec67f._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_3_d86aba42d014c4b4f708dcb5fe86e055._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_4_9aaf296ef53da317d6dc6728705d5c56._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_5_0d5f8a05a1505660f7ff1bc4ac6ff271._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_6_3dfdfd49597c85575cb689adb70d2de6._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_7_943a446c60ed9d7d4f240ba7f00fe925._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_8_9563859850fb40b1cc2c20c516c12960._comment
 delete mode 100644 doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_9_cf6221c585ee3dbf039bdaea71842d9b._comment
 delete mode 100644 doc/bugs/Auto_update_not_updating_to_newest_version.mdwn
 delete mode 100644 doc/bugs/Auto_update_not_updating_to_newest_version/comment_1_6f75569dc960ea5bc4d334b2b321ebf8._comment
 delete mode 100644 doc/bugs/Auto_update_not_updating_to_newest_version/comment_2_4f26cce07a9f37c79b166111db499ce1._comment
 delete mode 100644 doc/bugs/Auto_update_not_updating_to_newest_version/comment_3_585bfcaa655b0e838f9b66a241d5ffc2._comment
 delete mode 100644 doc/bugs/Auto_update_not_updating_to_newest_version/comment_4_2705fbfd74652ab097ac48ec687517c7._comment
 delete mode 100644 doc/bugs/Auto_update_not_updating_to_newest_version/comment_5_ab1ee005dbd54e560ea6e3c716cc8f1b._comment
 delete mode 100644 doc/bugs/Auto_update_not_updating_to_newest_version/comment_6_8019fa061d74365ea72e32780d288eb4._comment
 delete mode 100644 doc/bugs/Automatic_upgrades_should_be_cryptographically_signed.mdwn
 delete mode 100644 doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment
 delete mode 100644 doc/bugs/Backup_repository_doesn__39__t_get_all_files.mdwn
 delete mode 100644 doc/bugs/Backup_repository_doesn__39__t_get_all_files/comment_1_a486dc0f741e08d5bcf2fd1a6ecbdf05._comment
 delete mode 100644 doc/bugs/Browser_fails_to_launch_on_Android___39__git_annex_webapp__39__.mdwn
 delete mode 100644 doc/bugs/Browser_fails_to_launch_on_Android___39__git_annex_webapp__39__/comment_1_173393b0b3d2d8c622c0d8a2eaace421._comment
 delete mode 100644 doc/bugs/Build-depends_needs___39__hxt__39___added_-_3.20121127.mdwn
 delete mode 100644 doc/bugs/Build_error:_Ambiguous_occurrence___96__callCommand__39__.mdwn
 delete mode 100644 doc/bugs/Build_error:_Ambiguous_occurrence___96__callCommand__39__/comment_1_3127b3c448888fdf70096f24c7cbfd3c._comment
 delete mode 100644 doc/bugs/Build_error_on_Linux.mdwn
 delete mode 100644 doc/bugs/Build_error_on_Mac_OSX_10.6.mdwn
 delete mode 100644 doc/bugs/Building_fails:_Could_not_find_module___96__Text.Blaze__39__.mdwn
 delete mode 100644 doc/bugs/Building_fails:__Could_not_find_module___96__Data.XML.Types__39__.mdwn
 delete mode 100644 doc/bugs/Building_fails:___Not_in_scope:_type_constructor_or_class___96__Html__39__.mdwn
 delete mode 100644 doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link.mdwn
 delete mode 100644 doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_1_c0f0a2878070ed86900815c6b6a5fa5e._comment
 delete mode 100644 doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_2_53f2de3d3993821d8502fd08a0fcce12._comment
 delete mode 100644 doc/bugs/Building_on_OpenBSD.mdwn
 delete mode 100644 doc/bugs/Building_on_OpenBSD/comment_1_bec4a7253e851567cd47b96ceead5d91._comment
 delete mode 100644 doc/bugs/Building_on_OpenBSD/comment_2_4a37935080b86643ecda717fe17f8f87._comment
 delete mode 100644 doc/bugs/Building_on_OpenBSD/comment_3_2df229eb965189e2f7ea6dcd66cf68ca._comment
 delete mode 100644 doc/bugs/Building_on_OpenBSD/comment_4_d141c0bac92bdfbc8b95d532d032174c._comment
 delete mode 100644 doc/bugs/Building_on_OpenBSD/comment_5_8aba96ef58eb6954f1d15029e0dda9ed._comment
 delete mode 100644 doc/bugs/Building_on_OpenBSD/comment_6_82e6744e246fe5caa72081d4e921b168._comment
 delete mode 100644 doc/bugs/Cabal_cannot_solve_dependencies.mdwn
 delete mode 100644 doc/bugs/Cabal_cannot_solve_dependencies/comment_1_1d41ac79867226dcb71f1c7b38da062d._comment
 delete mode 100644 doc/bugs/Cabal_cannot_solve_dependencies/comment_2_50e72633a4462f6f6eb33d57b137fdcc._comment
 delete mode 100644 doc/bugs/Cabal_cannot_solve_dependencies/comment_3_886f2d1f7c47a3973b8dc7d7c412289a._comment
 delete mode 100644 doc/bugs/Cabal_dependency_monadIO_missing.mdwn
 delete mode 100644 doc/bugs/Cabal_dependency_monadIO_missing/comment_1_14be660aa57fadec0d81b32a8b52c66f._comment
 delete mode 100644 doc/bugs/Cabal_dependency_monadIO_missing/comment_2_4f4d8e1e00a2a4f7e8a8ab082e16adac._comment
 delete mode 100644 doc/bugs/Calls_to_rsync_don__39__t_always_use__annex-rsync-options.mdwn
 delete mode 100644 doc/bugs/Can__39__t___34__git-annex_get__34___with_3.20111203.mdwn
 delete mode 100644 doc/bugs/Can__39__t_rename___34__here__34___repository.mdwn
 delete mode 100644 doc/bugs/Can__39__t_set_repositories_directory.mdwn
 delete mode 100644 doc/bugs/Can__39__t_set_repositories_directory/comment_1_beb5d5b66a8d0fab12be44a7d877e9b0._comment
 delete mode 100644 doc/bugs/Can__39__t_set_repositories_directory/comment_2_366aa798a5e55350d32b63b31c19112b._comment
 delete mode 100644 doc/bugs/Can__39__t_set_repositories_directory/comment_3_812554d58ad9274a50b2a33d5f4d2ec3._comment
 delete mode 100644 doc/bugs/Can__39__t_set_repositories_directory/comment_4_bec5f147441ad18c97845b44c90c728b._comment
 delete mode 100644 doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9.mdwn
 delete mode 100644 doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9/comment_1_91a961cfa5dd4d6f0e4abfbbcfb81e92._comment
 delete mode 100644 doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9/comment_2_0b5266e31fe7014bd11ea164f8e4744e._comment
 delete mode 100644 doc/bugs/Can__39__t_start_it_on_Debian_Wheezy.mdwn
 delete mode 100644 doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared.mdwn
 delete mode 100644 doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared/comment_1_ca7ec2041bbec330476fb040b1e66a92._comment
 delete mode 100644 doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared/comment_2_c476847665a5320214721497d8fad15b._comment
 delete mode 100644 doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1.mdwn
 delete mode 100644 doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_1_b25859c159d62f2e92b92f505535131b._comment
 delete mode 100644 doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_2_4c9eab9120718457fdc1ae9051e44bca._comment
 delete mode 100644 doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_3_61aec9801e1f76db4a286536ffacc3ed._comment
 delete mode 100644 doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_4_6381ff0ea419831d9bbed27511cad1e9._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote.mdwn
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_258a376cff4c62bc4be919322bb1bd88._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_d9b830a1fdea8760cb7da1d36b3cd34d._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_1_09d76e5f9480b9a35644a8f08790cd97._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_2_7b586c705a937d09a1b44bd6af2d4686._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_3_07dbd8f64982f1921077e23f468122cf._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_4_926fd494f0b27103a99083cd5d0702d5._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_5_80444a509cc340f5eb3cd08b193fd389._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_6_4c6b99cd67b4aa742da5101fb1b379f7._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_8_f45cdd2b6acc5f458b67539fced0e529._comment
 delete mode 100644 doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_9_5a455dd14fb9d3ff408bb3f81e366c38._comment
 delete mode 100644 doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__.mdwn
 delete mode 100644 doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_1_6f7b5c164ff64f00b8814b2ee334709f._comment
 delete mode 100644 doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_2_807ef1250237bf4426e3a24c1f9ba357._comment
 delete mode 100644 doc/bugs/Check_for_minimum_Git_version.mdwn
 delete mode 100644 doc/bugs/Committer_crashed.mdwn
 delete mode 100644 doc/bugs/Compile_needs_more_than_1.5gb_of_memory.mdwn
 delete mode 100644 doc/bugs/Compile_needs_more_than_1.5gb_of_memory/comment_1_0806b5132c55d7a5a17fbdad7e3f2291._comment
 delete mode 100644 doc/bugs/Complete_failure_trying_to_unannex_a_large_annex.mdwn
 delete mode 100644 doc/bugs/Complete_failure_trying_to_unannex_a_large_annex/comment_1_1c202695ab7fe62cdc8770e1fb428d0c._comment
 delete mode 100644 doc/bugs/Conflicting_archive_descriptions.mdwn
 delete mode 100644 doc/bugs/ControlPath_too_long_for_Unix_domain_socket.mdwn
 delete mode 100644 doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_1_60f58e205604eebe668b1e05dcfbf9a7._comment
 delete mode 100644 doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_2_9c0c65389a3b4e7e81b8de96d430a3f1._comment
 delete mode 100644 doc/bugs/Could_not_find_module_Data.Default.mdwn
 delete mode 100644 doc/bugs/Could_not_resolve_dependencies.mdwn
 delete mode 100644 doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh.mdwn
 delete mode 100644 doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_1_9705f295ad8101f3f0ede18e590b56ef._comment
 delete mode 100644 doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_2_0d751d81ac618f8d7e3f1dd20c830542._comment
 delete mode 100644 doc/bugs/Crash_when_adding_jabber_account_.mdwn
 delete mode 100644 doc/bugs/Crash_when_adding_jabber_account_/comment_1_2dc61ebcfa8919fb839656999c155c52._comment
 delete mode 100644 doc/bugs/Crash_when_adding_jabber_account_/comment_2_e49af3b8a937d82eda1509b6f67b21d4._comment
 delete mode 100644 doc/bugs/Crash_when_adding_jabber_account_/comment_3_e59f8813bf1a7c4e3c8c120fe82348b9._comment
 delete mode 100644 doc/bugs/Crash_when_adding_jabber_account_/comment_4_716ac138cb69eecd0fb586699b4aeb2a._comment
 delete mode 100644 doc/bugs/Crash_when_adding_jabber_account_/comment_5_9bfd8df548d5866599dfc69fb3aaf94a._comment
 delete mode 100644 doc/bugs/Creating_a_box.com_repository_fails.mdwn
 delete mode 100644 doc/bugs/Creating_a_box.com_repository_fails/comment_1_c0b4855b65cb7052daf6538c2ad73e99._comment
 delete mode 100644 doc/bugs/Creating_a_box.com_repository_fails/comment_2_b05a1e7b37989c698353cc6b3fd02d7c._comment
 delete mode 100644 doc/bugs/Creating_a_box.com_repository_fails/comment_3_6c3610fb95676592f17f36e4e1b09bd8._comment
 delete mode 100644 doc/bugs/Creating_a_box.com_repository_fails/comment_4_c9895712e72854e4b5ff7a58e82ae374._comment
 delete mode 100644 doc/bugs/Creating_a_box.com_repository_fails/comment_5_93981afe8162f64ebb9d8c2c6a7ef91e._comment
 delete mode 100644 doc/bugs/Creating_a_box.com_repository_fails/comment_6_752b5725b4596721438098d38af8fb66._comment
 delete mode 100644 doc/bugs/Creating_a_box.com_repository_fails/comment_7_73f71386f8eafbb65f4cc9769021710f._comment
 delete mode 100644 doc/bugs/Creating_a_box.com_repository_fails/comment_8_109e37051beb729834e05997c023b849._comment
 delete mode 100644 doc/bugs/Creating_an_S3_repository_with_an_invalid_name_throws_an_exception.mdwn
 delete mode 100644 doc/bugs/DS__95__Store_not_gitignored.mdwn
 delete mode 100644 doc/bugs/DS__95__Store_not_gitignored/comment_1_b93ac0ea3be82c361ceb4352e742ba39._comment
 delete mode 100644 doc/bugs/DS__95__Store_not_gitignored/comment_2_4136e1f4aba7aa7562dafcf6a213e10c._comment
 delete mode 100644 doc/bugs/Detection_assumes_that_shell_is_bash.mdwn
 delete mode 100644 doc/bugs/Difficult_to_troubleshoot_XMPP_login_failures.mdwn
 delete mode 100644 doc/bugs/Difficult_to_troubleshoot_XMPP_login_failures/comment_1_4205bccf515169031e4a9ed8e905262c._comment
 delete mode 100644 doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files.mdwn
 delete mode 100644 doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_1_cb10385a4f046bfe676720ded3409379._comment
 delete mode 100644 doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_2_4bcf1a897181e40c9c8969d597a844f0._comment
 delete mode 100644 doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_3_6a6d22d218f036c9977072973ed99aa8._comment
 delete mode 100644 doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_4_eaa7ffb3a1d9ffd6d89de301bd2cd5b2._comment
 delete mode 100644 doc/bugs/Direct_mode_repositories_end_up_with_unstaged_changes.mdwn
 delete mode 100644 doc/bugs/Direct_mode_repositories_end_up_with_unstaged_changes/comment_1_300a2b246182be3079db20a7e3322261._comment
 delete mode 100644 doc/bugs/Discrepancy_between_git_annex_add_and_git_annex_watch.mdwn
 delete mode 100644 doc/bugs/Displayed_copy_speed_is_wrong.mdwn
 delete mode 100644 doc/bugs/Displayed_copy_speed_is_wrong/comment_1_74de3091e8bfd7acd6795e61f39f07c6._comment
 delete mode 100644 doc/bugs/Displayed_copy_speed_is_wrong/comment_2_8b240de1d5ae9229fa2d77d1cc15a552._comment
 delete mode 100644 doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder.mdwn
 delete mode 100644 doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_1_ae4a13ff121d27f78904eee9bf5e716b._comment
 delete mode 100644 doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_2_32e360cd7b100ddb9a526e7833fc55e1._comment
 delete mode 100644 doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_3_650dc9ede4e16ef668d96840f63dad47._comment
 delete mode 100644 doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_4_721cf184fb5a5244ec5c15de3302ebf7._comment
 delete mode 100644 doc/bugs/Error___39__get__39__ting_files_from_rsync_remote__44___versions_3.20120315_and_3.20120430.mdwn
 delete mode 100644 doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__.mdwn
 delete mode 100644 doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_1_9be1b577fa4d5fe9754845073fdf5d32._comment
 delete mode 100644 doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_2_0da0d68b646f2b38be6ecf7c0fe13743._comment
 delete mode 100644 doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_3_09c56f5574931f2ebe903069f0731160._comment
 delete mode 100644 doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_4_0c127396e682ca6ced43aec7deeb0335._comment
 delete mode 100644 doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_5_6bc3eadefde4750eec67a55de6651b2d._comment
 delete mode 100644 doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_6_263ab9c1483438b1717c8061ac81a2fa._comment
 delete mode 100644 doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_7_eccc10990dff37584f8e60cd481a7140._comment
 delete mode 100644 doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_8_f897d20cbe5e0f3f58ce1a0bacad3d71._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__.mdwn
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_10_8742f7ac27b5f4ad6261d04a174a691c._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_11_b8e720340000537de6713c49b7733b2f._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_1_489fa3a717519cd5d8b4c1a9d143d8c6._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_2_b0796d3b1913e1b6f7b34d75a591be42._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_3_d8ca17ccaa5ee48d590736af8e77d88a._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_4_aa7a690aaf75d21f52051a31d7fce70e._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_5_dc235dc2d024b7f340721bb578630e00._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_6_5d1e6ea5b5725c773acc6e288add812c._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_7_6389b4f03ebc916358bc6674398d70c4._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_8_bcacc9fb3751042968118ebe33802e27._comment
 delete mode 100644 doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_9_6d4c9f0e133ebd94fc11346df446402e._comment
 delete mode 100644 doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location.mdwn
 delete mode 100644 doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_1_b524e70156e8bc1219d5c6741974ad99._comment
 delete mode 100644 doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_2_ff7349c396d1249204d621e71f6a7a52._comment
 delete mode 100644 doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_4_4bc7d4c51faea3fdafc977cb66b7f73a._comment
 delete mode 100644 doc/bugs/Error_while_adding_a_file___34__createSymbolicLink:_already_exists__34__.mdwn
 delete mode 100644 doc/bugs/Every_new_file_gets_symlinked_to_a_git_object.mdwn
 delete mode 100644 doc/bugs/Every_new_file_gets_symlinked_to_a_git_object/comment_1_d4e7ed56b16494a95e6c904c746cc91f._comment
 delete mode 100644 doc/bugs/Every_new_file_gets_symlinked_to_a_git_object/comment_2_656b2a2cc44e9102c86bdd57045549d5._comment
 delete mode 100644 doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__.mdwn
 delete mode 100644 doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__/comment_1_fb8a379ed7f4b88bd55245ce5b18042c._comment
 delete mode 100644 doc/bugs/Fails_to_create_remote_repo_if_no_global_email_set.mdwn
 delete mode 100644 doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles.mdwn
 delete mode 100644 doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles/comment_1_c258016dd545b0426e75a7c0132154d8._comment
 delete mode 100644 doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles/comment_2_c506f609390f8bf46433b67fc2a9ddf8._comment
 delete mode 100644 doc/bugs/Feature_request:___34__quvi__34___flag.mdwn
 delete mode 100644 doc/bugs/Feature_request:___34__quvi__34___flag/comment_1_908c38024fd252328566034608c2dec3._comment
 delete mode 100644 doc/bugs/Feature_request:___34__quvi__34___flag/comment_2_4b6822fe91aa865f2ac1297a3daa3fca._comment
 delete mode 100644 doc/bugs/Feature_request:___34__quvi__34___flag/comment_3_c72ef77e76b1c99b5e0c78d0742080e7._comment
 delete mode 100644 doc/bugs/Feature_request:___34__quvi__34___flag/comment_4_6092695d6afb1608447afe6f86e6fb83._comment
 delete mode 100644 doc/bugs/Finding_an_Unused_file.mdwn
 delete mode 100644 doc/bugs/Fix_for_opening_a_browser_on_a_mac___40__or_xdg-open_on_linux__47__bsd__63____41__.mdwn
 delete mode 100644 doc/bugs/Fix_to_thaoe_remote_to_work_with_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn
 delete mode 100644 doc/bugs/GPG_can__39__t_handle_some_files.mdwn
 delete mode 100644 doc/bugs/GPG_can__39__t_handle_some_files/comment_1_4388c971e991dbc0326e69c49994df1e._comment
 delete mode 100644 doc/bugs/GPG_problem_on_Mac.mdwn
 delete mode 100644 doc/bugs/GPG_problem_on_Mac/comment_1_9ccfa12e7a9569a7ae9a3b819917c275._comment
 delete mode 100644 doc/bugs/GPG_problem_on_Mac/comment_2_a5e07131e2bc1a646c8439fc2506128b._comment
 delete mode 100644 doc/bugs/GPG_problem_on_Mac/comment_3_388238360f2423f84881e904443efb86._comment
 delete mode 100644 doc/bugs/Git_annex_add_fails_on_read-only_files.mdwn
 delete mode 100644 doc/bugs/Git_annex_add_fails_on_read-only_files/comment_1_d31018e8bf31d729ee9fee43a0a07934._comment
 delete mode 100644 doc/bugs/Git_annex_add_fails_on_read-only_files/comment_2_e38e7048749f890169cd0be602be6ee7._comment
 delete mode 100644 doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android.mdwn
 delete mode 100644 doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_1_2fc435d1c741f9fc422401f682e7c8b7._comment
 delete mode 100644 doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_2_b73fb99a75aef912f8286626c5bde66d._comment
 delete mode 100644 doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_3_b7115f2c658439ff59a029f500697fc1._comment
 delete mode 100644 doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_4_67de7a56ddb06fc0e31cc011d281c633._comment
 delete mode 100644 doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_5_58fdb2a00f1737746cdbc804f831a0e7._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion.mdwn
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_10_f57ff027b19ca16e2ecf1fc6aee9ef4a._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_11_2ff78d2090d0fd3418ab50b27c6028ce._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_1_523d3c0c71f80536850a001b90fd0e9e._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_2_6c360c64093b016c2150206dc3ad1709._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_3_7b77fd9b7dc236c345f2f6149c8138ee._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_5_08289596445d7588e43d35490fbfe5f4._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_5_2a336fe7b8aed07cbdaa868bd34078f9._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_6_ea7a40c3b6748738421aed00a6f7ca10._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_7_00962da9288976f8a48d0cbc08e1d9e2._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_8_5d53d23e529f33f6e7deb10643831613._comment
 delete mode 100644 doc/bugs/Hanging_on_install_on_Mountain_lion/comment_9_f00c8761e3184975b6645c0c3e241365._comment
 delete mode 100644 doc/bugs/Hangs_on_creating_repository_when_using_--listen.mdwn
 delete mode 100644 doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_1_8cbe786de8cf8b407418149b9c811aab._comment
 delete mode 100644 doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_2_dc128eeddeaaf3f84e71aca0fb7d341f._comment
 delete mode 100644 doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__.mdwn
 delete mode 100644 doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment
 delete mode 100644 doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment
 delete mode 100644 doc/bugs/In_the_assistant__44___add_some_clarifications_near___34__Add_another_local_repository__34___for_the_case_of_adding_an_existing_repository.mdwn
 delete mode 100644 doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case.mdwn
 delete mode 100644 doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case/comment_1_73b4dc5f90c8ba5634caee35cd31af1a._comment
 delete mode 100644 doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case/comment_2_e84b93062c82453f18308a82ee270585._comment
 delete mode 100644 doc/bugs/Incorrect_version_on_64_Standalone_Build.mdwn
 delete mode 100644 doc/bugs/Incorrect_version_on_64_Standalone_Build/comment_1_1964e4cad33a9f98b2eedbf095e899ff._comment
 delete mode 100644 doc/bugs/Install_of_git-annex-3.20121112_fails.mdwn
 delete mode 100644 doc/bugs/Install_of_git-annex-3.20121112_fails/comment_1_80fc80151d4390bd8a4332f30723962e._comment
 delete mode 100644 doc/bugs/Install_of_git-annex-3.20121112_fails/comment_2_2613320a41a74dc757a3277c8c328bd0._comment
 delete mode 100644 doc/bugs/Install_of_git-annex-3.20121112_fails/comment_3_c364764d0c56e8dc3cac276905d99841._comment
 delete mode 100644 doc/bugs/Install_of_git-annex-3.20121112_fails/comment_4_f1057340dfa978071d3bbc9e2af1e612._comment
 delete mode 100644 doc/bugs/Install_of_git-annex-3.20121112_fails/comment_5_9007b1a3abd647945604968db19cb841._comment
 delete mode 100644 doc/bugs/Install_of_git-annex-3.20121112_fails/comment_6_0bb3ac5375f29ce9d3d0be93879267e3._comment
 delete mode 100644 doc/bugs/Install_of_git-annex-3.20121112_fails/comment_7_ae4443b8cd069080d1f77fca16aa8b04._comment
 delete mode 100644 doc/bugs/Internal_Server_Error_when_adding_an_uncrypted_box.com_repo_after_deleted_an_encrypted_one..mdwn
 delete mode 100644 doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X.mdwn
 delete mode 100644 doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_1_b2ef077d87a9da624f20649c21401b5b._comment
 delete mode 100644 doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_2_ef849e25b0264808bff800d9d3836119._comment
 delete mode 100644 doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_3_ae3cbd0eb69cbeb9b349e0060d056d43._comment
 delete mode 100644 doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_4_0ff2897805928b14829b7b369a3aed91._comment
 delete mode 100644 doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_5_414a45573aeb5201f4d80433955669d5._comment
 delete mode 100644 doc/bugs/Interrupted_switch_to_direct_mode_can_cause_all_following_switches_to_fail.mdwn
 delete mode 100644 doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn
 delete mode 100644 doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_1_380a49b3c132f9f529729a1cb5a69621._comment
 delete mode 100644 doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_2_282f5f89fb4a46e1fad0980e0b2994a0._comment
 delete mode 100644 doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_3_7ff98958146b7f6396226bdd878ec86e._comment
 delete mode 100644 doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_4_f9e460a09e7e5f53c16c20ded2649201._comment
 delete mode 100644 doc/bugs/Jabber__47__xmpp_not_supported_on_Debian_Wheezy_backport.mdwn
 delete mode 100644 doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind.mdwn
 delete mode 100644 doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind/comment_1_17879b98a5e79ace03b543064751e46e._comment
 delete mode 100644 doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind/comment_2_2dc877e281750004b16619ea7b931160._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss.mdwn
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_10_52364dc5b1b43b51748453d1896e35c6._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_11_99b4db1841f8630a9c5efd08910e87a3._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_1_fbb410a54bb0bd82d0953ef58a88600e._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_2_8007c9ba42a951a4426255ec3c37d961._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_3_73ecd4cb8ee58a8dfe7cab0e893dbe5b._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_4_e8a10886a564f35414c30a04335d9d32._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_5_6a318edfe45c80343d017dc7b4837acb._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_6_f7a1d9f9d40aff531d873a95d2196edd._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_7_1724ffdf986301bf37ef7a6d16b6ea8a._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_8_5470e2f50e6506139ecb1b342371c509._comment
 delete mode 100644 doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_9_e53148a9efa061a825f668a9492182f7._comment
 delete mode 100644 doc/bugs/Last_two_versions_didn__39__t_show_up_on_hackage.mdwn
 delete mode 100644 doc/bugs/Last_two_versions_didn__39__t_show_up_on_hackage/comment_1_74b56dea2100450e322e726bb55bb310._comment
 delete mode 100644 doc/bugs/Local_files_not_found.mdwn
 delete mode 100644 doc/bugs/Local_files_not_found/comment_1_5e1fcc0597594fa493ffa28aa32e1df8._comment
 delete mode 100644 doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn
 delete mode 100644 doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_1_b8c485bafd98be8c21595597af361255._comment
 delete mode 100644 doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_2_bc63489334f44a423645021415ffe196._comment
 delete mode 100644 doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_3_6345b174d04b6613c2c55a6ec9e50c21._comment
 delete mode 100644 doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_4_f39ec6c3d5a016b3c5260162c0b42177._comment
 delete mode 100644 doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_5_ca0c5ef6e6a6d2c4b64430ac68370b6a._comment
 delete mode 100644 doc/bugs/Log_rotation_loses_large_logs.mdwn
 delete mode 100644 doc/bugs/Lost_S3_Remote.mdwn
 delete mode 100644 doc/bugs/Lost_S3_Remote/comment_1_6e80e6db6671581d471fc9a54181c04c._comment
 delete mode 100644 doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment
 delete mode 100644 doc/bugs/Lost_S3_Remote/comment_3_1e434d5a20a692cd9dc7f6f8f20f30dd._comment
 delete mode 100644 doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__.mdwn
 delete mode 100644 doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_1_6e50d721c624ad82e94c8e5e93b38783._comment
 delete mode 100644 doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_2_07a22d9e9010a04ae0088ebfd4bbf4df._comment
 delete mode 100644 doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_3_0b64e2dada87cd79fa584e86a00529ea._comment
 delete mode 100644 doc/bugs/Makefile_is_missing_dependancies.mdwn
 delete mode 100644 doc/bugs/Makefile_is_missing_dependancies/comment_1_5a3da5f79c8563c7a450aa29728abe7c._comment
 delete mode 100644 doc/bugs/Makefile_is_missing_dependancies/comment_2_416f12dbd0c2b841fac8164645b81df5._comment
 delete mode 100644 doc/bugs/Makefile_is_missing_dependancies/comment_3_c38b6f4abc9b9ad413c3b83ca04386c3._comment
 delete mode 100644 doc/bugs/Makefile_is_missing_dependancies/comment_4_cc13873175edf191047282700315beee._comment
 delete mode 100644 doc/bugs/Makefile_is_missing_dependancies/comment_5_0a1c52e2c96d19b9c3eb7e99b8c2434f._comment
 delete mode 100644 doc/bugs/Makefile_is_missing_dependancies/comment_6_24119fc5d5963ce9dd669f7dcf006859._comment
 delete mode 100644 doc/bugs/Makefile_is_missing_dependancies/comment_7_96fd4725df4b54e670077a18d3ac4943._comment
 delete mode 100644 doc/bugs/Makefile_is_missing_dependancies/comment_8_a3555e3286cdc2bfeb9cde0ff727ba74._comment
 delete mode 100644 doc/bugs/Manual_mode_weirdness.mdwn
 delete mode 100644 doc/bugs/Manual_mode_weirdness/comment_1_f8ab3bac9e9a6768e5fd5a052f0d920f._comment
 delete mode 100644 doc/bugs/Manual_mode_weirdness/comment_2_e810daa488fad32ca8bdaae620051da8._comment
 delete mode 100644 doc/bugs/Matching_oddity_in_SafeCommand.hs.mdwn
 delete mode 100644 doc/bugs/Matching_oddity_in_SafeCommand.hs/comment_1_1a51630c0791547a7e0b68eea5d81e4c._comment
 delete mode 100644 doc/bugs/Missing_dependancy_in_commit_6cecc26206c4a539999b04664136c6f785211a41.mdwn
 delete mode 100644 doc/bugs/More_sync__39__ing_weirdness_with_the_assistant_branch_on_OSX.mdwn
 delete mode 100644 doc/bugs/More_sync__39__ing_weirdness_with_the_assistant_branch_on_OSX/comment_1_377525e70640751e1ead445aeed15efa._comment
 delete mode 100644 doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana.mdwn
 delete mode 100644 doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_1_f3c336ecfee51e074ea3a9fc95301de5._comment
 delete mode 100644 doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_2_102c0e998934e84deca92fd1c90145fa._comment
 delete mode 100644 doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_3_1449dd796ce9f2209f085d4b017a5f33._comment
 delete mode 100644 doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_4_c4aa8a4379b2c056ca9b7afcff412bbc._comment
 delete mode 100644 doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_5_6ca4dd2ad51182edf7198f38b336b9b6._comment
 delete mode 100644 doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn
 delete mode 100644 doc/bugs/Need_to_manually_install_c2hs_-_3.20121127_and_previous.mdwn
 delete mode 100644 doc/bugs/No_progress_bars_with_S3.mdwn
 delete mode 100644 doc/bugs/No_progress_bars_with_S3/comment_1_33a601201a9fdd2357f1c03e32fa6b9c._comment
 delete mode 100644 doc/bugs/No_progress_bars_with_S3/comment_2_52361805ced99c22d663b3b1e8a5b221._comment
 delete mode 100644 doc/bugs/No_progress_bars_with_S3/comment_3_5903c1c40c4562f4fbaccd1640fedb18._comment
 delete mode 100644 doc/bugs/No_progress_bars_with_S3/comment_4_80799c33e513384894b390fe34ab312a._comment
 delete mode 100644 doc/bugs/No_version_information_from_cli.mdwn
 delete mode 100644 doc/bugs/OSX_.dmg_unnecessarily_large_and_not_inherently_compressed.mdwn
 delete mode 100644 doc/bugs/OSX_alias_permissions_and_versions_problem.mdwn
 delete mode 100644 doc/bugs/OSX_alias_permissions_and_versions_problem/comment_1_4fabe32e7e626e6ca23aa0b6f449c4c6._comment
 delete mode 100644 doc/bugs/OSX_alias_permissions_and_versions_problem/comment_2_064d60fcc8366a70958540bc145e611a._comment
 delete mode 100644 doc/bugs/OSX_alias_permissions_and_versions_problem/comment_3_6c72d4f40ea0a9566a1185901beff5ba._comment
 delete mode 100644 doc/bugs/OSX_alias_permissions_and_versions_problem/comment_4_8a11f404bb72a1aeb2290744cce2d00d._comment
 delete mode 100644 doc/bugs/OSX_alias_permissions_and_versions_problem/comment_5_30888607199d6a48b76d0c48f5aa4f64._comment
 delete mode 100644 doc/bugs/OSX_build_broken.mdwn
 delete mode 100644 doc/bugs/OSX_build_broken/comment_1_0b570aa6c58effeace2a989184c9c601._comment
 delete mode 100644 doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__.mdwn
 delete mode 100644 doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_1_0dfa839f1ba689b23f811787515b8cff._comment
 delete mode 100644 doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_2_612b947eb5474f6d792a833e33105665._comment
 delete mode 100644 doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_3_549b8bcae6f1f8b21932b734e32fbdd1._comment
 delete mode 100644 doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_4_23078dfea127fa3ef20696eb10ce964c._comment
 delete mode 100644 doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_5_7da5ef8325b8787bbf1c6e2c17b1142e._comment
 delete mode 100644 doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp.mdwn
 delete mode 100644 doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_1_2653fe701a1bb20254f3d6b90f10a43b._comment
 delete mode 100644 doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_2_d9ce701d077e40f39b142ce2cc570a3b._comment
 delete mode 100644 doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_3_14964ab68253dc1a8903d14a821b8b40._comment
 delete mode 100644 doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_4_4a579e9a13305ab4157f4b3eba46b92d._comment
 delete mode 100644 doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_5_2a710960dc3a177ce62ef92f8546c496._comment
 delete mode 100644 doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_6_a4ad73530cd0f6621bcc6394d5f39af7._comment
 delete mode 100644 doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple.mdwn
 delete mode 100644 doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_1_971224d2c0c0ce8d4530b1991508f849._comment
 delete mode 100644 doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_2_6866f96277dbe83a8aadcdeb426b6750._comment
 delete mode 100644 doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_3_eaed9b5532e30e401f50193a72b98310._comment
 delete mode 100644 doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_4_1fab407f3823ce8cec87f5df55e49f8c._comment
 delete mode 100644 doc/bugs/On_Windows__44___annex_get_fails_with_HTTP_Remote__44___but_believes_it_has_succeeded..mdwn
 delete mode 100644 doc/bugs/On_Windows__44___wget_is_not_used__44___even_if_available.mdwn
 delete mode 100644 doc/bugs/Partial_direct__47__indirect_repo.mdwn
 delete mode 100644 doc/bugs/Partial_direct__47__indirect_repo/comment_1_42344fce051d759f95215c985e9d1135._comment
 delete mode 100644 doc/bugs/Partial_direct__47__indirect_repo/comment_2_8ba64f2750d0ef4adf595674c723bc65._comment
 delete mode 100644 doc/bugs/Partial_direct__47__indirect_repo/comment_3_bd4985864b7dcd70a609ca7bc2617e4a._comment
 delete mode 100644 doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn
 delete mode 100644 doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode/comment_1_84cb8c651584ec2887f6e1b7dc107190._comment
 delete mode 100644 doc/bugs/Possible_issues_with_git_1.7.10_and_newer___40__merge_command_now_asks_for_a_commit_message__34__.mdwn
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files.mdwn
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_10_d4f6bfe8e04560fc661a47b09ed8a5f4._comment
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_1_e1a99bd3eb8b3186653b52a52b1836de._comment
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_2_dec3e5ffe5cfdc439f418ee00d7d9810._comment
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_3_d106a87101db52f957da84d90dafcdbb._comment
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_4_f28ed0635612693e437e64d872af5c37._comment
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_5_f0237075653768c84deb702442645f28._comment
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_6_b509006e1590480a104627369bc910f2._comment
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_7_fe261c074211ccb94bbcb32cfd8ee654._comment
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_8_bc8e4dc7e0d6577ba5fcc98f56627b1f._comment
 delete mode 100644 doc/bugs/Problem_when_dropping_unused_files/comment_9_e9a22aa2ebcde5f6595b49dba9375761._comment
 delete mode 100644 doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn
 delete mode 100644 doc/bugs/Problems_building_on_Mac_OS_X.mdwn
 delete mode 100644 doc/bugs/Problems_building_on_Mac_OS_X/comment_1_1c199b826fdd84b5184b1466ad03a9a4._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx.mdwn
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_10_94e4ac430140042a2d0fb5a16d86b4e5._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_11_56f1143fa191361d63b441741699e17f._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_12_ec5131624d0d2285d3b6880e47033f97._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_13_88ed095a448096bf8a69015a04e64df1._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_14_89a960b6706ed703b390a81a8bc4e311._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_15_6b8867b8e48bf807c955779c9f8f0909._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_16_5c2dd6002aadaab30841b77a5f5aed34._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_17_62fccb04b0e4b695312f7a3f32fb96ee._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_18_64fab50d95de619eb2e8f08f90237de1._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_19_4253988ed178054c8b6400beeed68a29._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_1_34120e82331ace01a6a4960862d38f2d._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_20_7db27d1a22666c831848bc6c06d66a84._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_2_cc53d1681d576186dbc868dd9801d551._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_3_68f0f8ae953589ae26d57310b40c878d._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_4_c52be386f79f14c8570a8f1397c68581._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_5_7f1330a1e541b0f3e2192e596d7f7bee._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_6_0c46f5165ceb5a7b9ea9689c33b3a4f8._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_7_237a137cce58a28abcc736cbf2c420b0._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_8_efafa203addf8fa79e33e21a87fb5a2b._comment
 delete mode 100644 doc/bugs/Problems_running_make_on_osx/comment_9_cc283b485b3c95ba7eebc8f0c96969b3._comment
 delete mode 100644 doc/bugs/Problems_with_syncing_gnucash.mdwn
 delete mode 100644 doc/bugs/Problems_with_syncing_gnucash/comment_1_ca195af3ba4a286eb5ab687634192fa4._comment
 delete mode 100644 doc/bugs/Problems_with_syncing_gnucash/comment_2_754fb430381ad88e6248ecb902b32118._comment
 delete mode 100644 doc/bugs/Problems_with_syncing_gnucash/comment_4_25881998c6f149c70b1358f37b7c66ba._comment
 delete mode 100644 doc/bugs/Provide_64-bit_standalone_build.mdwn
 delete mode 100644 doc/bugs/Provide_64-bit_standalone_build/comment_1_1850bb3eb464f1d3c122cfeb4ccaf265._comment
 delete mode 100644 doc/bugs/Remote_repo_and_set_operation_with_find.mdwn
 delete mode 100644 doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository.mdwn
 delete mode 100644 doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_1_92211091daf9827a4ec7e5b5a6769d59._comment
 delete mode 100644 doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_2_f0fa97a9eba1c624f6f8720ba8a160b7._comment
 delete mode 100644 doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_3_e3d677ea4170c07cd31efe6dc85fa5f3._comment
 delete mode 100644 doc/bugs/Repository_deletion_error.mdwn
 delete mode 100644 doc/bugs/Repository_deletion_error/comment_1_31673d0300986b6098d1af2cc4b180c6._comment
 delete mode 100644 doc/bugs/Repository_in_manual_mode_does_not_hold_files.mdwn
 delete mode 100644 doc/bugs/Repository_in_manual_mode_does_not_hold_files/comment_1_86e8a4e546610e8e265806eb245d8aba._comment
 delete mode 100644 doc/bugs/Repository_in_manual_mode_does_not_hold_files/comment_2_17d5775a38b67ba4f0e73f6b89cff2d0._comment
 delete mode 100644 doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code.mdwn
 delete mode 100644 doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code/comment_1_66b21720cd1b2a4f66ef24252d3e6305._comment
 delete mode 100644 doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code/comment_2_18c9f55c5af1f4f690a7727df71ab561._comment
 delete mode 100644 doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file.mdwn
 delete mode 100644 doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file/comment_1_fd95e0bb61e80a72b4ac1304ef6c2e77._comment
 delete mode 100644 doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn
 delete mode 100644 doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_1_dc5ae7af499203cfd903e866595b8fea._comment
 delete mode 100644 doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_2_c62daf5b3bfcd2f684262c96ef6628c1._comment
 delete mode 100644 doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_3_e1f39c4af5bdb0daabf000da80858cd9._comment
 delete mode 100644 doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_4_bb6b814ab961818d514f6553455d2bf3._comment
 delete mode 100644 doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_5_5bb128f6d2ca4b5e4d881fae297fa1f8._comment
 delete mode 100644 doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_6_63fb74da342751fc35e1850409c506f6._comment
 delete mode 100644 doc/bugs/SSH:_command-line:_line_0:_Bad_configuration_option:_ControlPersist___40__SSH_too_old_on_OS_X_10.6.8__63____41__.mdwn
 delete mode 100644 doc/bugs/SSH:_command-line:_line_0:_Bad_configuration_option:_ControlPersist___40__SSH_too_old_on_OS_X_10.6.8__63____41__/comment_1_0c57a2196d35eb1ecfb0c51273bba05c._comment
 delete mode 100644 doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled.mdwn
 delete mode 100644 doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_1_f708d87aa65cd38c20087859d3ab2dc7._comment
 delete mode 100644 doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_2_fb7188db031147992f3c906783ebbee0._comment
 delete mode 100644 doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.mdwn
 delete mode 100644 doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment
 delete mode 100644 doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_2_8f5fa659c2ab91b1757bac31cd3b15eb._comment
 delete mode 100644 doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_3_ccf9623d60c58d036d8bf24757e50de3._comment
 delete mode 100644 doc/bugs/Should_ignore_.thumbnails__47___on_android.mdwn
 delete mode 100644 doc/bugs/Specifying_a_filename_starting_with___34__-c__34___instead_applies_it_to_all_files.mdwn
 delete mode 100644 doc/bugs/Specifying_a_filename_starting_with___34__-c__34___instead_applies_it_to_all_files/comment_1_2fe6d735bc075275a6b8890fac48ee58._comment
 delete mode 100644 doc/bugs/Stale_lock_files_on_Android.mdwn
 delete mode 100644 doc/bugs/Switching_between_direct_and_indirect_stomps_on___39__regular__39___git_files.mdwn
 delete mode 100644 doc/bugs/Switching_between_direct_and_indirect_stomps_on___39__regular__39___git_files/comment_1_0d2cb3b8509cd0eba50aafa14afefc02._comment
 delete mode 100644 doc/bugs/Switching_from_indirect_mode_to_direct_mode_breaks_duplicates.mdwn
 delete mode 100644 doc/bugs/Switching_repositories_in_webapp_on_a_remote_server_is_not_honoring_--listen_parameter.mdwn
 delete mode 100644 doc/bugs/Switching_repositories_in_webapp_on_a_remote_server_is_not_honoring_--listen_parameter/comment_1_4dd773372979dd95538bfba6516a11eb._comment
 delete mode 100644 doc/bugs/Syncing_creates_broken_links_instead_of_proper_files.mdwn
 delete mode 100644 doc/bugs/Syncing_creates_broken_links_instead_of_proper_files/comment_1_a2bedb2e77451b02fc66fc9ef5c4405c._comment
 delete mode 100644 doc/bugs/Test_failure_on_debian_dropunused.mdwn
 delete mode 100644 doc/bugs/The_assistant_hangs_forever.mdwn
 delete mode 100644 doc/bugs/The_assistant_hangs_forever/comment_1_b0291e32860e0da0b66837d14ed5aab6._comment
 delete mode 100644 doc/bugs/The_assistant_hangs_forever/comment_2_a2950cf91b8a4e4f2951f5522ef0e9c4._comment
 delete mode 100644 doc/bugs/The_assistant_hangs_forever/comment_3_db95f78519d5ffbad793906028730dab._comment
 delete mode 100644 doc/bugs/The_assistant_hangs_forever/comment_4_28b13fd3165b38a2fbc9e1a461c38921._comment
 delete mode 100644 doc/bugs/The_assistant_hangs_forever/comment_5_81a79c8840ff26307a9c6edad5b850f9._comment
 delete mode 100644 doc/bugs/The_assistant_hangs_forever/comment_6_b739719b14705f4d7e1d412b3cab090c._comment
 delete mode 100644 doc/bugs/The_assistant_hangs_forever/comment_7_2b300d960697c5b967c1f109dfd6dfbf._comment
 delete mode 100644 doc/bugs/The_assistant_hangs_forever/comment_8_8623220d08b1a72ed8b669a2d9cc0f75._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible.mdwn
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_10_8305becdc6e70abdaf17e42f263173fc._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_11_d75896a6e204d1abdda04923aa668d04._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_12_a36a4a64a04c01c2db467b09300e6ebd._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_13_c9d6631c304acb289e485fb901e1f274._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_14_10282c4352075c8d148b8674973b7b16._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_15_ceb68da01d9e2fe9a70fab6244116da0._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_16_cca4abde86a8be5e2919c4738f5bdd0c._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_17_2fa5d7d9110c91b0a3a833cb3d9f53fd._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_18_bf21d28142e4c304aa0bc740955ddea0._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_19_45537758fa937f16fc82120bf8b234e8._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_1_a38497772834a4b12137390b461ce70b._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_20_b685050ee6fbb1a685e33f9656a10e84._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_3_17bc0220c20553c848875475c5fd4ae6._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_4_76472bc58bb790f773c46ec2c39fcf88._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_4_dcd9286e314779c25764484beff40561._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_5_2146eec77b87b615100d0d003e8dce75._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_6_2bd6f4e04903ee251d43d0a97bd40b6e._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_7_7db8ed002eb6313b07f09bd1a34019e3._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_8_1bcb2a238006044bc78849e56cb21a01._comment
 delete mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_9_26c6937cf78e7141e0e3b20f25ed8f7a._comment
 delete mode 100644 doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories.mdwn
 delete mode 100644 doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_1_1b80f9cfedd25e34997fa07e08d15012._comment
 delete mode 100644 doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_2_53499da1185c56d8fd25f86ba41d96ce._comment
 delete mode 100644 doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_3_3e07b8386d2c7afce2a78d24b9c260b9._comment
 delete mode 100644 doc/bugs/Too_many_open_files.mdwn
 delete mode 100644 doc/bugs/Too_many_open_files/comment_1_d5d509b9b431d2ea6000ebc0aed62857._comment
 delete mode 100644 doc/bugs/Too_much_system_load_on_startup.mdwn
 delete mode 100644 doc/bugs/Too_much_system_load_on_startup/comment_1_4470cddc0965062588acff1bc77285e9._comment
 delete mode 100644 doc/bugs/TransferScanner_crash_on_Android.mdwn
 delete mode 100644 doc/bugs/TransferScanner_crash_on_Android/comment_1_6c3584ade1ee6cccddddeaa8e1697945._comment
 delete mode 100644 doc/bugs/TransferScanner_crash_on_Android/comment_2_06574e05149a677d666a722061586658._comment
 delete mode 100644 doc/bugs/TransferScanner_crash_on_Android/comment_3_54ae097d30bb7a49fe151f38c9bac033._comment
 delete mode 100644 doc/bugs/Trouble_initializing_git_annex_on_NFS.mdwn
 delete mode 100644 doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_1_e26952373150d63b8a5d3643a2762de1._comment
 delete mode 100644 doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_2_f80b10ed395738e50e345fc22c708ae5._comment
 delete mode 100644 doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_3_f99e0f05950fc2fc80fdecd35e17012c._comment
 delete mode 100644 doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_4_e42146d2dcc4052266dd61d204aeb551._comment
 delete mode 100644 doc/bugs/True_backup_support.mdwn
 delete mode 100644 doc/bugs/True_backup_support/comment_1_50aa0bc1e2502622585682cb703e0b85._comment
 delete mode 100644 doc/bugs/True_backup_support/comment_2_d6030c6c49b227e022f05d590746d4ca._comment
 delete mode 100644 doc/bugs/USB_drive_not_syncing.mdwn
 delete mode 100644 doc/bugs/USB_drive_not_syncing/comment_1_de76bd6b9f8eb2489d4854a4c8ddd308._comment
 delete mode 100644 doc/bugs/Unable_to_copy_from_Android.mdwn
 delete mode 100644 doc/bugs/Unable_to_copy_from_Android/comment_1_3bb70c44b6b8d451687591fcab5c1506._comment
 delete mode 100644 doc/bugs/Unable_to_import_feed.mdwn
 delete mode 100644 doc/bugs/Unable_to_import_feed/comment_1_16230fbbb996e165b84787ed4d5f72ea._comment
 delete mode 100644 doc/bugs/Unable_to_switch_back_to_direct_mode.mdwn
 delete mode 100644 doc/bugs/Unable_to_switch_back_to_direct_mode/comment_1_4585b251f011a153c62f377c324cf963._comment
 delete mode 100644 doc/bugs/Unable_to_switch_back_to_direct_mode/comment_2_5848ebbab38d1244347f7e7351b3a30d._comment
 delete mode 100644 doc/bugs/Unable_to_switch_back_to_direct_mode/comment_3_1c5c7b0c7bc336e00f43e257b87a6208._comment
 delete mode 100644 doc/bugs/Unable_to_switch_back_to_direct_mode/comment_4_b0bfd68998bc3e11d8e089646b8292a6._comment
 delete mode 100644 doc/bugs/Unable_to_sync_a_second_machine_through_Box.mdwn
 delete mode 100644 doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_1_cb43a2bc976e3eb1cfc3ee9d4d34e78e._comment
 delete mode 100644 doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_2_3375e9bfab3fed271413bd9bb5fa0121._comment
 delete mode 100644 doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_3_c4420e1a3db321b4135b1626d3582adb._comment
 delete mode 100644 doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_4_f4b2c88bb5938dacdd04dfe9a68560de._comment
 delete mode 100644 doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_5_6dcc95ffb3fc7bbbedd6be5df0111c85._comment
 delete mode 100644 doc/bugs/Unable_to_use_remotes_with_space_in_the_path.mdwn
 delete mode 100644 doc/bugs/Unfortunate_interaction_with_Calibre.mdwn
 delete mode 100644 doc/bugs/Unfortunate_interaction_with_Calibre/comment_1_7cb5561f11dfc7726a537ddde2477489._comment
 delete mode 100644 doc/bugs/Unfortunate_interaction_with_Calibre/comment_2_b8ae4bc589c787dacc08ab2ee5491d6e._comment
 delete mode 100644 doc/bugs/Unfortunate_interaction_with_Calibre/comment_3_977c5f6b82f9e18cdd81d57005bb8b89._comment
 delete mode 100644 doc/bugs/Unfortunate_interaction_with_Calibre/comment_4_ff7d2e9a39dfe12b975d04650ac57cc4._comment
 delete mode 100644 doc/bugs/Unfortunate_interaction_with_Calibre/comment_5_fc4d5301797589e92cc9a24697b2155d._comment
 delete mode 100644 doc/bugs/Unknown_command___39__list__39__.mdwn
 delete mode 100644 doc/bugs/Unknown_command___39__list__39__/comment_1_c625d03d1ed2019141ac9202f933466d._comment
 delete mode 100644 doc/bugs/Unknown_command___39__list__39__/comment_2_800e1b6417768bdadda311ebfb5df637._comment
 delete mode 100644 doc/bugs/Unknown_command___39__list__39__/comment_3_35dfc75ce9efffff139f8929dc311e29._comment
 delete mode 100644 doc/bugs/Unknown_remote_type_webdav.mdwn
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers.mdwn
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_10_b778fbb1386f0f51bf057ffacd590ebb._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_11_55430eac842d0a192dc7f41d7730e4d5._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_1_00c18e07678dc513a02d974fe059df73._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_2_2e9992dbfceabd6df535a2770626de16._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_3_a98f3091a6a658919f0562cf396439c2._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_4_417c1e8e27ee1a1f9ebf9160560605c5._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_5_eb5a2717a1f0c7bb761d2a7866b23def._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_6_89f756db1f3f2e60a3bd1f35f55fee43._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_7_5aaf8766a7ba05c4f92715e5d5175a8f._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_8_e856b350632cc865d16d1995a6cdf065._comment
 delete mode 100644 doc/bugs/Unnecessary_remote_transfers/comment_9_64f831545b34b78452952cf49b5f5b05._comment
 delete mode 100644 doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__.mdwn
 delete mode 100644 doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__/comment_1_8fe44da0581d9b8c6ab5fe6aea8d83d1._comment
 delete mode 100644 doc/bugs/Update_dependency_on_certificate___62____61___1.3.3.mdwn
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work.mdwn
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_2_bca95245b457631d08b47591da6163ad._comment
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_3_f54bb003096752dae0442660267a1e37._comment
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_4_38bb916ed5b90b92ffa91a452ff052a9._comment
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_5_5b6ef464ab1ad061f27122db40191e26._comment
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_6_3727bda5082cb1f2b1f746f9f80ced7d._comment
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_7_a7139f19f0b73c024cd9218eb01e6104._comment
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_8_35c949aca52de83af4881a9da6340185._comment
 delete mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_9_9100031689eaa460791191d9bfb746d8._comment
 delete mode 100644 doc/bugs/Using_Github_as_remote_throws_proxy_errors.mdwn
 delete mode 100644 doc/bugs/Using_Github_as_remote_throws_proxy_errors/comment_1_10616b17c3fb8286fdc64c841023f8a1._comment
 delete mode 100644 doc/bugs/Using_Github_as_remote_throws_proxy_errors/comment_2_8a72887d33e492a041f8246d93d0c778._comment
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key.mdwn
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key/comment_1_7bb01d081282e5b02b7720b2953fe5be._comment
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key/comment_2_9c0c40360f0058a4bd346c1362e302b6._comment
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key/comment_3_8f69f58107246595f5603f35c4aa7395._comment
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key/comment_4_78b3c52ba85edfa6ee6e273bec3bea5c._comment
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key/comment_5_a85ccf2f09ebe87147f8761b81a02326._comment
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key/comment_6_8b89eb5e6386acd0a922310c04f863ac._comment
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key/comment_7_20dc5a7ce7cb6ca97ccdfb923c3b24bb._comment
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key/comment_8_9dc921dc6077f828454a4444088b9a43._comment
 delete mode 100644 doc/bugs/Using_a_revoked_GPG_key/comment_9_f50c802d78041fd1522f0e7599ce6a45._comment
 delete mode 100644 doc/bugs/WEBDAV_443.mdwn
 delete mode 100644 doc/bugs/WEBDAV_443/comment_10_9ee2c5ed44295455af890caee7b06f1a._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_11_863a7d315212c9a8ab8f6fafa5d1b7f5._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_12_c17a4e23011e0a917dbe0ecf7e9f0cb5._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_13_3414416ff455d2fd1a7c7e7c4554b54d._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_14_e1da141eefb0445c217e5f5c119356da._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_15_41c3134bcc222b97bf183559723713d9._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_16_89621b526065b5bef753ce75db1af7b5._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_17_131a1b65c8008cf9f02c93d4fb75720b._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_18_b4f894a0b9ebb84ab73f6ffcf0778090._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_1_c6572ca1eaaf89b01c0ed99a4058412f._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_2_a357969cde382a91e13920ee1e9f711c._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_3_213815d6b827d467c60f3e8af925813b._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_4_b775be4b722fc7124d9fbe2d5d01cc9f._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_5_c4ea745da437e56b2426d1c2c00dfcec._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_6_ef05c0ae88fee9c626922c6064ffdf1e._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_7_eecabe8d5ed564cb540450770ca7d0b6._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_8_7f77ba8ebd90186d3b3949ae529ba393._comment
 delete mode 100644 doc/bugs/WEBDAV_443/comment_9_87ebdc92b48d672964fb3f248c53600f._comment
 delete mode 100644 doc/bugs/WORM:_Handle_long_filenames_correctly.mdwn
 delete mode 100644 doc/bugs/WORM:_Handle_long_filenames_correctly/comment_1_77aa9cafbe20367a41377f3edccc9ddb._comment
 delete mode 100644 doc/bugs/WORM:_Handle_long_filenames_correctly/comment_2_fe735d728878d889ccd34ec12b3a7dea._comment
 delete mode 100644 doc/bugs/WORM:_Handle_long_filenames_correctly/comment_3_2bf0f02d27190578e8f4a32ddb195a0a._comment
 delete mode 100644 doc/bugs/WORM:_Handle_long_filenames_correctly/comment_4_8f7ba9372463863dda5aae13205861bf._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults.mdwn
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_10_6c872dff4fcc63c16bf69d1e96891c89._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_1_5cad24007f819e4be193123dab0d511a._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_2_d449bf656a59d424833f9ab5a7fb4e82._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_3_ffb1ce41477ad60840abd7a89a133067._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_4_cebbc138c6861c086bb7937b54f5adbc._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_5_5e27737a5bb0e9e46c98708700318e67._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_6_1f92da712232d050e085a4f39063d7a6._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_7_4153dc8029c545f8e86584a38bd536fb._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_8_f85b6eb5bfd28ffc6973fb4ab0fe4337._comment
 delete mode 100644 doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_9_c747c488461c98cd285b51d3afc2c3eb._comment
 delete mode 100644 doc/bugs/Watcher_crashed:_addWatch:_does_not_exist.mdwn
 delete mode 100644 doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_1_24f511a8103727894c6e96798a559870._comment
 delete mode 100644 doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_2_e14eddbc09cadbf1e4dbbb0c07e0e5b0._comment
 delete mode 100644 doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_3_513fae4d379008f954a307be8df34976._comment
 delete mode 100644 doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_4_172eaeb3bb8b502379695aba35f96120._comment
 delete mode 100644 doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_5_8adb9de82cc8581422734acc66dd094c._comment
 delete mode 100644 doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_6_02f0beef1188bfa336bf4220eb5c6286._comment
 delete mode 100644 doc/bugs/WebDAV_HandshakeFailed_.mdwn
 delete mode 100644 doc/bugs/WebDAV_HandshakeFailed_/comment_1_40499110ea43bc99ad9dd9f642da434c._comment
 delete mode 100644 doc/bugs/WebDAV_HandshakeFailed_/comment_2_506712e8cc5b47b9bd69edf67ae54da7._comment
 delete mode 100644 doc/bugs/WebDAV_HandshakeFailed_/comment_3_5641481d9e9ed2b711b1516f1abc5c30._comment
 delete mode 100644 doc/bugs/WebDAV_HandshakeFailed_/comment_4_1d609de93fa66ce9dc802e67b5922243._comment
 delete mode 100644 doc/bugs/WebDAV_HandshakeFailed_/comment_5_62761882d30c1b02930c938cb8e30ed4._comment
 delete mode 100644 doc/bugs/WebDAV_HandshakeFailed_/comment_6_acda8fae848ec486ce2a0b3dff3bd0a5._comment
 delete mode 100644 doc/bugs/WebDAV_HandshakeFailed_/comment_7_6c51b6c7dd477d8911dd9a7a5c41ea2e._comment
 delete mode 100644 doc/bugs/WebDAV_HandshakeFailed_/comment_8_e834f791d3000669fab25732a7c72ab3._comment
 delete mode 100644 doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn
 delete mode 100644 doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes/comment_1_56474a69c2f174d83be9137d3c045a47._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace.mdwn
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_0._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_10_037a6dd6e15ef5f789a1f364f7507b53._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_11_614e4110188fc6474e7da50fc4281e13._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_12_dcb74fb91e1c2f0db4efd68c8bcbc96c._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_38671ba8d302f4d32460d1478abd2111._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_483244b1ed5744308022465f45c091fd._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_1_d2c63723fa4bf828873770a42ffaab20._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_3_52f0db73dc38c3e3a73f6c7a420bf016._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_4_93596b4d5a48ffcf4bc11ba9c83cf7ca._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_5_de94e80dde6d12485140bb079d74d775._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_6_5f34c3d449247b4bce4665b3ea4d054c._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_7_b43ae8aec23ba3acaf70edc0de058710._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_8_13b8e0a62f6b6d02960687e206a8b016._comment
 delete mode 100644 doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_9_818b94a74b01a210d1106dd35bc932d8._comment
 delete mode 100644 doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git.mdwn
 delete mode 100644 doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git/comment_1_155e0c4d3aa41eebfe27533ab70a91d3._comment
 delete mode 100644 doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn
 delete mode 100644 doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_1_a4fc30bf7d39cae337286e9e815e6cba._comment
 delete mode 100644 doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_2_e5d42b623017acedf6a3890ce15680a3._comment
 delete mode 100644 doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_3_e5150b65b514896e14b9ad3d951963f7._comment
 delete mode 100644 doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_4_47c2fc167b0c396edc40468fb7c7bfee._comment
 delete mode 100644 doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error..mdwn
 delete mode 100644 doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_1_6d821af99ab3c83a5b0f52d3713ab8e2._comment
 delete mode 100644 doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_2_206b6c8cce8350fc088f01c42fc4715b._comment
 delete mode 100644 doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_3_ed36f503f88611382b50687608b9b7e7._comment
 delete mode 100644 doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn
 delete mode 100644 doc/bugs/__34__drop__34___deletes_all_files_with_identical_content.mdwn
 delete mode 100644 doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_1_2eb20b65582fa7f271b1d0bb5560d08c._comment
 delete mode 100644 doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_2_b14e1d31dd6a8fb930fcc0bec798e194._comment
 delete mode 100644 doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_3_1892bcfbe3c462aa74552a241d65cad9._comment
 delete mode 100644 doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_4_dfa0e31996eaa14e2945c1d11670c4d9._comment
 delete mode 100644 doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_5_e2a9336cf1080c158765d4adfe72f26b._comment
 delete mode 100644 doc/bugs/__34__git_annex_watch__34___adds_map.dot.mdwn
 delete mode 100644 doc/bugs/__34__import__34___generates_a_commit_even_with_autocommit__61__false.mdwn
 delete mode 100644 doc/bugs/__34__make_test__34___fails_silently.mdwn
 delete mode 100644 doc/bugs/__34__make_test__34___fails_silently/comment_1_f868e34f41d828d4571968d1ab07820a._comment
 delete mode 100644 doc/bugs/__34__make_test__34___fails_silently/comment_2_fb9e8e2716b0dea15b0d4807ae7cd114._comment
 delete mode 100644 doc/bugs/__39__Cannot_write_a_repository_there__39___on_Windows.mdwn
 delete mode 100644 doc/bugs/__39__Internal_Server_Error__39___when_creating_repo_on_other_drive_than_C:_on_Windows.mdwn
 delete mode 100644 doc/bugs/__39__Internal_Server_Error__39___when_creating_repo_on_other_drive_than_C:_on_Windows/comment_1_ea3b2c0e3bdfb50ac0dce10ba1b6339f._comment
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content.mdwn
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_1_56f9cd5cc2e089b32cb076dc2e2a8ca5._comment
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_2_21c0f7f328cb51080fbd97e086c47a30._comment
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_3_3287b2f25f3b5ae4c27f4748694563ee._comment
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_4_e515eca68a70d40c522805d7e0d7c0e6._comment
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_5_b27f4c103dda050b6e9cf03ea3157abc._comment
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_6_2cc7083dab944705bf91fc00319b75e6._comment
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_7_1175f9be789d4c1907f0be98e435bd2f._comment
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_8_78e6164ef67a9560a3a9ead1f7a72473._comment
 delete mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_9_1d578fd13022dcd6382b415a7f6e097a._comment
 delete mode 100644 doc/bugs/__91__Installation__93___There_is_no_available_version_of_quickcheck_that_satisfies___62____61__2.1.mdwn
 delete mode 100644 doc/bugs/__91__webapp__93___pause_syncing_with_specific_repository.mdwn
 delete mode 100644 doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu.mdwn
 delete mode 100644 doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_1_9bb53c45d685b368c7ba1758885f2874._comment
 delete mode 100644 doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_2_251311a04f1a610e54ebe8e9b92de72e._comment
 delete mode 100644 doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_3_83ac87a01639776a6e519af226bd84d5._comment
 delete mode 100644 doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op.mdwn
 delete mode 100644 doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_1_9b671e583eec5adf870dccd1e97b5dbc._comment
 delete mode 100644 doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_2_d11744202213d6f897f4234bc4c70c18._comment
 delete mode 100644 doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_3_a729deb465ff44f5a9b87c963cd6235a._comment
 delete mode 100644 doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_4_3f735503df9a08472d42fabd219c2ec5._comment
 delete mode 100644 doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_5_2c61eabbba7fd2a52ba02d59a0a76a42._comment
 delete mode 100644 doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories.mdwn
 delete mode 100644 doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_1_94ccd548c084286163eeb2af1ddc18e3._comment
 delete mode 100644 doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_2_befde3ef3d2b171ebb691915ff3af172._comment
 delete mode 100644 doc/bugs/__96__git_annex_sync__96___ignores_remotes.mdwn
 delete mode 100644 doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_1_39421e6935233cd8f45949ebdef369fe._comment
 delete mode 100644 doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_2_53fb15d6fbf96d43564ff7c866239d18._comment
 delete mode 100644 doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn
 delete mode 100644 doc/bugs/add_script-friendly_output_options.mdwn
 delete mode 100644 doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error.mdwn
 delete mode 100644 doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error/comment_1_f55cfc133be72ac10cae93c877c487df._comment
 delete mode 100644 doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error/comment_2_24dd024ac4b21a82a781343b8fe3891e._comment
 delete mode 100644 doc/bugs/addurl_--relaxed_with_--file_doesn__39__t_actually_relax.mdwn
 delete mode 100644 doc/bugs/addurl_fails_on_the_internet_archive.mdwn
 delete mode 100644 doc/bugs/addurl_fails_on_the_internet_archive/comment_1_e227aa25eea0b41f1176037a601c5844._comment
 delete mode 100644 doc/bugs/addurl_fails_on_the_internet_archive/comment_2_6d4fd58f0caa1f75ee2dd3f0a909cd91._comment
 delete mode 100644 doc/bugs/addurl_file_doesn__39__t_work_with_spaces_in_filenames_and_--fast.mdwn
 delete mode 100644 doc/bugs/addurl_file_doesn__39__t_work_with_spaces_in_filenames_and_--fast/comment_1_eea9477ea1157cb88c8a07d8da5f0dba._comment
 delete mode 100644 doc/bugs/allows_repository_with_the_same_name_twice.mdwn
 delete mode 100644 doc/bugs/allows_repository_with_the_same_name_twice/comment_1_ba7801403e7138684704a3471c8bc4a6._comment
 delete mode 100644 doc/bugs/allows_repository_with_the_same_name_twice/comment_2_8c19a4ddedbe7ddb8bdcf84acac68cc8._comment
 delete mode 100644 doc/bugs/amd64_i386_standalone:_no_SKEIN.mdwn
 delete mode 100644 doc/bugs/amd64_i386_standalone:_no_SKEIN/comment_1_fcf7e1089b25993378df7574ccee8062._comment
 delete mode 100644 doc/bugs/amd64_standalone:_ld-linux-x86-64.so.2:_not_found.mdwn
 delete mode 100644 doc/bugs/amd64_standalone:_ld-linux-x86-64.so.2:_not_found/comment_1_5e40f32caf9c1177a5f7b9883cdcc6dd._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit.mdwn
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_1d841ff0b0ffd814efed2449dc1f35f3._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_cd101e0af45d8f463011fb0d04b3b822._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_11_8595041cfe703d9bea49e792732dc15f._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_1_8e7bc6965ea967a8d43240791a30c5bc._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_2_891c1073f908b204651899d41599f944._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_3_de02b8f1b5928fa1a7078c4aa2124bea._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_6_506acc4275a81ed9e9b08e8a40fcf96a._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_7_d38d6f40db4c9437764c7b2ddf36b5a9._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_8_9bb23e9cbc77ecca4b1209b0f66bc2b0._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_d1ce7fc251db076da61eed5bb9d71b9a._comment
 delete mode 100644 doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_feb71c1022ff65d82e66a3958a41dfb2._comment
 delete mode 100644 doc/bugs/android_cannot_get_from_5.20131221.mdwn
 delete mode 100644 doc/bugs/android_cannot_get_from_5.20131221/comment_1_f8eeb67e58bf2a4658dcc32a9f275f19._comment
 delete mode 100644 doc/bugs/android_cannot_get_from_5.20131221/comment_2_eba841b1978c70a4c20a8d96c9f71172._comment
 delete mode 100644 doc/bugs/android_cannot_get_from_5.20131221/comment_3_4ba8208822c7f66e23037564b3501391._comment
 delete mode 100644 doc/bugs/annex-rsync-options_shell-split_carelessly.mdwn
 delete mode 100644 doc/bugs/annex-rsync-options_shell-split_carelessly/comment_1_2636e0d224317f2e6db94658d8a094c4._comment
 delete mode 100644 doc/bugs/annex.numcopies_not_overriden_by_--numcopies_option.mdwn
 delete mode 100644 doc/bugs/annex_add_in_annex.mdwn
 delete mode 100644 doc/bugs/annex_get_fails:___34__No_such_file_or_directory__34__.mdwn
 delete mode 100644 doc/bugs/annex_get_fails:___34__No_such_file_or_directory__34__/comment_1_e44ae9c19796efc8eda5432d3bf1e5a3._comment
 delete mode 100644 doc/bugs/annex_get_over_SSH_is_very_slow.mdwn
 delete mode 100644 doc/bugs/annex_seems_to_ignore_core.bare_setting.mdwn
 delete mode 100644 doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment
 delete mode 100644 doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_2_bc5a4be517409f8da2f36299dc4cbbde._comment
 delete mode 100644 doc/bugs/another_build_error_in_assistant.mdwn
 delete mode 100644 doc/bugs/archiving_git_repositories.mdwn
 delete mode 100644 doc/bugs/archiving_git_repositories/comment_1_51f546a571303118446a9e0b3e6482c9._comment
 delete mode 100644 doc/bugs/assistant___40__OS_X_Lion__41___-___34__too_many_open_files__34___error.mdwn
 delete mode 100644 doc/bugs/assistant___40__OS_X_Lion__41___-___34__too_many_open_files__34___error/comment_1_9904c30a4c24a699d71e90ce5e9b89cf._comment
 delete mode 100644 doc/bugs/assistant_always_assumes_port_22__63__.mdwn
 delete mode 100644 doc/bugs/assistant_does_not_list_remote___39__origin__39__.mdwn
 delete mode 100644 doc/bugs/assistant_does_not_list_remote___39__origin__39__/comment_1_ffa008240c61b50396aa92f467731db6._comment
 delete mode 100644 doc/bugs/assistant_does_not_list_remote___39__origin__39__/comment_2_a53f80090bc2a0f32b8d8307cb24b563._comment
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add.mdwn
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_1_13b2f93b7d09c8fd6c22829a0dc6428b._comment
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_2_94e46bc0044b8a91a9fd51058825aa8f._comment
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_3_10a38bdbf31dd4071e4bc4ac746d9c56._comment
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_4_b8fdf502c7e80aece5a9544a2078c85c._comment
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_5_a2ff7668f2a0d549b362d7de97fac8a1._comment
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_6_60d72f34a6cfd1c081f74aa610f4305a._comment
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_7_53a73e662c9356b759fbfa1e5a3bd927._comment
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_8_10b65168b6a54d960427966d7e3d05f5._comment
 delete mode 100644 doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_9_b640e8fa6aafb041d66bbf8857a8fa3d._comment
 delete mode 100644 doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__.mdwn
 delete mode 100644 doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_1_a3dccf1db287ea5c1ac1763518d5d9f9._comment
 delete mode 100644 doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_2_cb85fb3ba0152671568c23d6b95f3b7a._comment
 delete mode 100644 doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_3_5d87371fa86ddbbcd31dfc932ab6080f._comment
 delete mode 100644 doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn
 delete mode 100644 doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_1_37acb3afafb1b4c4da7c778130cf3035._comment
 delete mode 100644 doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_2_9d58887ee0184663852bde83b8d497c7._comment
 delete mode 100644 doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_3_b70881c8026e30fd3ddc051bd01a888b._comment
 delete mode 100644 doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_4_43f756e2e6ff985c8e050da0e369d486._comment
 delete mode 100644 doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment
 delete mode 100644 doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files.mdwn
 delete mode 100644 doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_1_e3f545d9adc27a4e7340bf16177c4fe0._comment
 delete mode 100644 doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_2_1403076dbc47733607f0c8b2856e2381._comment
 delete mode 100644 doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_3_af83717bfb260bea6d52ff71c6b34743._comment
 delete mode 100644 doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_4_b4f811611d14e7392009c539fa6b8574._comment
 delete mode 100644 doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts.mdwn
 delete mode 100644 doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_1_91a62a2ce14a1027d2ac8b8e88df5f0c._comment
 delete mode 100644 doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_2_4982cd373eaaeee180be03c6e9fda7b1._comment
 delete mode 100644 doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_3_85d264e311acaa91dac0597ee8deda82._comment
 delete mode 100644 doc/bugs/assistant_on_windows_adding_remote_containing_linux_paths.mdwn
 delete mode 100644 doc/bugs/authentication_to_rsync.net_fails.mdwn
 delete mode 100644 doc/bugs/authentication_to_rsync.net_fails/comment_1_9db65f89415c8d825f268afb75244998._comment
 delete mode 100644 doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn
 delete mode 100644 doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa.mdwn
 delete mode 100644 doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_1_15cce6e6f455e83f4362a38c561bc973._comment
 delete mode 100644 doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_2_e9e1f38880a32610b3fbce475bffc3e4._comment
 delete mode 100644 doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_3_51da7f5881f65422328d341e5ab0d250._comment
 delete mode 100644 doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_4_ba384314c1e47ec4b72e1843e0500df9._comment
 delete mode 100644 doc/bugs/bare_git_repos.mdwn
 delete mode 100644 doc/bugs/bug_in_download_prebuilt_linux_tarball__44___and_constraints_issues_with_3.20121112.mdwn
 delete mode 100644 doc/bugs/bug_system_updates_when___34__done__34__.mdwn
 delete mode 100644 doc/bugs/build_is_broken_at_commit_cc0e5b7.mdwn
 delete mode 100644 doc/bugs/build_issue_with_latest_release_0.20110522-1-gde817ba.mdwn
 delete mode 100644 doc/bugs/build_problem_on_OSX.mdwn
 delete mode 100644 doc/bugs/building_on_lenny.mdwn
 delete mode 100644 doc/bugs/bup_initremote_failed_with_localhost_+_username.mdwn
 delete mode 100644 doc/bugs/bup_initremote_failed_with_localhost_+_username/comment_1_0e669c3039b089fa8a815d3ec11465d2._comment
 delete mode 100644 doc/bugs/cabal_build:___34__Could_not_find_module___96__Data.AssocList__39____34__.mdwn
 delete mode 100644 doc/bugs/cabal_build:___34__Could_not_find_module___96__Data.AssocList__39____34__/comment_1_0da9fd67c3cc01b316f95a1df4eb62ae._comment
 delete mode 100644 doc/bugs/cabal_configure_is_broken_on_OSX_builds.mdwn
 delete mode 100644 doc/bugs/cabal_install_fails_to_install_manpage.mdwn
 delete mode 100644 doc/bugs/cabal_install_on_Ubuntu_12.04_fails_with_complaint_about_regex-base.mdwn
 delete mode 100644 doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository.mdwn
 delete mode 100644 doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_1_dd202a7764d9df998868d595a86ffb21._comment
 delete mode 100644 doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_2_ca065c82ac8e3215b581660f3e44f459._comment
 delete mode 100644 doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_3_927a01f9961c71bedb42c519a31b5fe5._comment
 delete mode 100644 doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode.mdwn
 delete mode 100644 doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode/comment_1_20c31a844d8351a99cf69e05d2836e0e._comment
 delete mode 100644 doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode/comment_2_f26e0f763f9027d9dfc08cd840ced153._comment
 delete mode 100644 doc/bugs/can__39__t_drop_unused_files_that_never_were_added.mdwn
 delete mode 100644 doc/bugs/can__39__t_run_the_assistant_from_the_command_line_anymore__63__.mdwn
 delete mode 100644 doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax.mdwn
 delete mode 100644 doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax/comment_1_397eb359c3f8ef30460a9556b6f55848._comment
 delete mode 100644 doc/bugs/cannot_add_file__44___get___34__user_error__34__.mdwn
 delete mode 100644 doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_1_14aa717c1befcbbf526f25ca2f0af825._comment
 delete mode 100644 doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_2_7f7ac59e7f3dce9d7a7d0c3379c2edcf._comment
 delete mode 100644 doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_3_5ebf03120b12edb3fbb8954546e7603e._comment
 delete mode 100644 doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_4_1ba6d2614778949520b47896fd98b598._comment
 delete mode 100644 doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_5_4a6e55861a63b350a02edb888b4da99b._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server.mdwn
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_10_5072de8fcca9fe70bc235ea8c8ee2877._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_11_dabd74bba1f38b326a2d0c86d3027cd9._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_12_0245b426cc0ab64f8c167b8806b03f5d._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_1_307df11b5bcf289d7999e1e7f7c461c9._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_2_f24378cf30a7d32594da90749fabec3c._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_3_4b07093be844ac62b611cee1dfde5aa7._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_4_fe1ed152a485c4aebfa9b9f300101835._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_5_2d311f520aee04287df6bddfd8535734._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_6_d9f916f012184738446c5996ee9d2270._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_7_0b5f9350e2367301241c7668a15815ef._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_8_f00b6ae154004e405f0bd23b7359962e._comment
 delete mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_9_41b86468013da15f46be29da520afa10._comment
 delete mode 100644 doc/bugs/cannot_determine_uuid_for_origin.mdwn
 delete mode 100644 doc/bugs/case_sensitivity_on_FAT.mdwn
 delete mode 100644 doc/bugs/check_for_curl_in_configure.hs.mdwn
 delete mode 100644 doc/bugs/clicking_back_in_the_web_browser_crashes.mdwn
 delete mode 100644 doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment
 delete mode 100644 doc/bugs/clicking_back_in_the_web_browser_crashes/comment_2_643b2c99ecfe851c576a023ce4385dbb._comment
 delete mode 100644 doc/bugs/clicking_back_in_the_web_browser_crashes/comment_3_6e85c50439da81212f4239c74947b75e._comment
 delete mode 100644 doc/bugs/com.branchable.git-annex.assistant.plist_is_invalid.mdwn
 delete mode 100644 doc/bugs/commit_f20a40f_breaks_on_OSX_as_mntent.h_doesn__39__t_exist.mdwn
 delete mode 100644 doc/bugs/configure_mistakes_hashalot_bins_for_sha__63____63____63__sum_and_builds_a_broken_git-annex_executable.mdwn
 delete mode 100644 doc/bugs/configure_script_should_detect_uuidgen_instead_of_just_uuid.mdwn
 delete mode 100644 doc/bugs/conflicting_haskell_packages.mdwn
 delete mode 100644 doc/bugs/conflicting_haskell_packages/comment_1_e552a6cc6d7d1882e14130edfc2d6b3b._comment
 delete mode 100644 doc/bugs/conq:_invalid_command_syntax.mdwn
 delete mode 100644 doc/bugs/conq:_invalid_command_syntax/comment_1_f33b83025ce974e496f83f248275a66a._comment
 delete mode 100644 doc/bugs/conq:_invalid_command_syntax/comment_2_195106ca8dedad5f4d755f625e38e8af._comment
 delete mode 100644 doc/bugs/conq:_invalid_command_syntax/comment_3_55af43e2f43a4c373f7a0a33678d0b1c._comment
 delete mode 100644 doc/bugs/copy_doesn__39__t_scale.mdwn
 delete mode 100644 doc/bugs/copy_doesn__39__t_scale/comment_1_7c12499c9ac28a9883c029f8c659eb57._comment
 delete mode 100644 doc/bugs/copy_doesn__39__t_scale/comment_2_f85d8023cdbc203bb439644cf7245d4e._comment
 delete mode 100644 doc/bugs/copy_doesn__39__t_scale/comment_3_4592765c3d77bb5664b8d16867e9d79c._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog.mdwn
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_10_435f87d54052f264096a8f23e99eae06._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_11_9be0aef403a002c1706d17deee45763c._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_12_26d60661196f63fd01ee4fbb6e2340e7._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_13_ead55b915d3b92a62549b2957ad211c8._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_14_191de89d3988083d9cf001799818ff4a._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_15_b3e3b338ccfa0a32510c78ba1b1bb617._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_16_04a9f4468c3246c8eff3dbe21dd90101._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_1_6a41bf7e2db83db3a01722b516fb6886._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_2_9f5f1dbffb2dd24f4fcf8c2027bf0384._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_3_b596b5cfd3377e58dbbb5d509d026b90._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_4_d7112c315fb016a8a399e24e9b6461d8._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_5_4ea29a6f8152eddf806c536de33ef162._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_6_0d85f114a103bd6532a3b3b24466012e._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_7_d38d5bee6d360b0ea852f39e3a7b1bc6._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_8_29c3de4bf5fbd990b230c443c0303cbe._comment
 delete mode 100644 doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_9_2cee4f6bd6db7518fd61453c595162c6._comment
 delete mode 100644 doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work.mdwn
 delete mode 100644 doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work/comment_1_77629f620b28ac62364de44b41fa539d._comment
 delete mode 100644 doc/bugs/cross_platform_permissions_woes.mdwn
 delete mode 100644 doc/bugs/cross_platform_permissions_woes/comment_1_7f01104de38a6a319a8f36aa1dc8b4b3._comment
 delete mode 100644 doc/bugs/cross_platform_permissions_woes/comment_2_0a34e11b466fad287325425e76487fa1._comment
 delete mode 100644 doc/bugs/cross_platform_permissions_woes/comment_3_278f91b4bc4c32717ab1c39c2abf9305._comment
 delete mode 100644 doc/bugs/cross_platform_permissions_woes/comment_4_eb6a271cb63c71341469c9ff89dc0eb9._comment
 delete mode 100644 doc/bugs/cyclic_drop.mdwn
 delete mode 100644 doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn
 delete mode 100644 doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_1_294c33af08649256908a97894f93c05d._comment
 delete mode 100644 doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment
 delete mode 100644 doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_3_d296ef26fc90f4e3166bba6d2de0a1ee._comment
 delete mode 100644 doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_4_33ba2c890c962a71ae9fadc417359f8e._comment
 delete mode 100644 doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_5_39eb0bb96fd271bd0de4a3a40814ae1b._comment
 delete mode 100644 doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_6_d80c4b631bdf58901a06f29a2c5682e2._comment
 delete mode 100644 doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_.mdwn
 delete mode 100644 doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_1_eb6db7f6a156a065e2724c2de5fc4366._comment
 delete mode 100644 doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_2_59a96cade9e4881767562a139fc7fb4b._comment
 delete mode 100644 doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_3_bf9d2562d66f0f6a9478ac178606cf4e._comment
 delete mode 100644 doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_4_ad0dbdc448fff2e126ffec9aac6d7463._comment
 delete mode 100644 doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_5_e828585e56b10710598143483ce362b6._comment
 delete mode 100644 doc/bugs/detected_bad_bare_repository_with___60__SCREECH__62___files.mdwn
 delete mode 100644 doc/bugs/detected_bad_bare_repository_with___60__SCREECH__62___files/comment_1_523b80ad81ad49bddfb8855d12d5561d._comment
 delete mode 100644 doc/bugs/direct_mode_renames.mdwn
 delete mode 100644 doc/bugs/direct_mode_renames/comment_1_f18c335e0d6f4259d2470935ef391cb8._comment
 delete mode 100644 doc/bugs/direct_mode_sync_should_avoid_git_commit.mdwn
 delete mode 100644 doc/bugs/direct_mode_sync_should_avoid_git_commit/comment_1_d286800081f019651cd40355b7d5518a._comment
 delete mode 100644 doc/bugs/direct_mode_sync_should_avoid_git_commit/comment_2_4e23201d1d1d549f72eec75987601a73._comment
 delete mode 100644 doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__.mdwn
 delete mode 100644 doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_1_69dfbf566c75396cdaaf5ad70f1a94a8._comment
 delete mode 100644 doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_2_8d09cc0e06548c4ebde7956edd1b5d85._comment
 delete mode 100644 doc/bugs/dotdot_problem.mdwn
 delete mode 100644 doc/bugs/drop_fails_to_see_copies_that_whereis_sees.mdwn
 delete mode 100644 doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_1_f5a9d99d90daf5eba4773d361fa1807a._comment
 delete mode 100644 doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_2_040aa454cd8acd2857ef36884465576f._comment
 delete mode 100644 doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_3_f5d8faab325ee26800ecad5aba49b54b._comment
 delete mode 100644 doc/bugs/dropping_and_re-adding_from_web_remotes_doesn__39__t_work.mdwn
 delete mode 100644 doc/bugs/dropunused_doesn__39__t_handle_double_spaces_in_filename.mdwn
 delete mode 100644 doc/bugs/dropunused_doesn__39__t_work_in_my_case__63__.mdwn
 delete mode 100644 doc/bugs/enableremote_broken_with_direct_mode__63__.mdwn
 delete mode 100644 doc/bugs/enableremote_broken_with_direct_mode__63__/comment_1_a2e61f5de7a28498de0c2d5e3d51eab4._comment
 delete mode 100644 doc/bugs/encrypted_S3_stalls.mdwn
 delete mode 100644 doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption.mdwn
 delete mode 100644 doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption/comment_1_2f4ec4b7b92a0f0a0c4c0758da4a05a5._comment
 delete mode 100644 doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption/comment_2_7c0aeae6b1b2b0338735b0231c5db7d4._comment
 delete mode 100644 doc/bugs/encryption_key_is_surprising.mdwn
 delete mode 100644 doc/bugs/encryption_key_is_surprising/comment_1_5b172830ac31d51a1687bc8b1db489f9._comment
 delete mode 100644 doc/bugs/encryption_key_is_surprising/comment_2_5b7e6bb36c3333dfd71808e8b4544746._comment
 delete mode 100644 doc/bugs/encryption_key_is_surprising/comment_4_8ec86b8c35bce15337a143e275961cd5._comment
 delete mode 100644 doc/bugs/encryption_key_is_surprising/comment_4_c5e49b3a0eceabe6d14f5226d7ba4c7a._comment
 delete mode 100644 doc/bugs/encryption_key_is_surprising/comment_5_cd7cbf0c0ee9cafec344dfbf1acd9590._comment
 delete mode 100644 doc/bugs/encryption_key_is_surprising/comment_6_01381524114d885961704acc3f172536._comment
 delete mode 100644 doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment
 delete mode 100644 doc/bugs/error_building_git-annex_3.20120624_using_cabal.mdwn
 delete mode 100644 doc/bugs/error_propigation.mdwn
 delete mode 100644 doc/bugs/error_when_using_repositories_with_non-ASCII_characters.mdwn
 delete mode 100644 doc/bugs/error_when_using_repositories_with_non-ASCII_characters/comment_1_38cc2d2ed907649df085de8ad83cb9dd._comment
 delete mode 100644 doc/bugs/error_with_file_names_starting_with_dash.mdwn
 delete mode 100644 doc/bugs/fails_to_handle_lot_of_files.mdwn
 delete mode 100644 doc/bugs/fails_to_handle_lot_of_files/comment_1_09d8e4e66d8273fab611bd29e82dc7fc._comment
 delete mode 100644 doc/bugs/fails_to_handle_lot_of_files/comment_2_fd2ec05f4b5a7a6ae6bd9f5dbc3156de._comment
 delete mode 100644 doc/bugs/fatal:_Out_of_memory__63___mmap_failed:_No_error.mdwn
 delete mode 100644 doc/bugs/fatal:_Out_of_memory__63___mmap_failed:_No_error/comment_1_3bc14a8b093ebb2c0571f5a554ef8cf3._comment
 delete mode 100644 doc/bugs/fatal:_empty_ident_name.mdwn
 delete mode 100644 doc/bugs/fatal:_empty_ident_name/comment_1_ceae87308fb75a1f79c7c8d63ec47226._comment
 delete mode 100644 doc/bugs/fatal:_empty_ident_name/comment_2_68832ee3e0e7244ce62bccabe2e52630._comment
 delete mode 100644 doc/bugs/fatal:_empty_ident_name/comment_3_ed31ad316747343d7730e4c2d7dacd24._comment
 delete mode 100644 doc/bugs/fatal:_empty_ident_name/comment_4_b812d6f30e8a866bce7260a9ee3218e3._comment
 delete mode 100644 doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__.mdwn
 delete mode 100644 doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_1_8a4045634bffc29c8147056096b7089d._comment
 delete mode 100644 doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_2_a1539aaec74074b4667ac27cfcfcccd6._comment
 delete mode 100644 doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_3_d252f39ddb9c9c14784c85a8b850a4ec._comment
 delete mode 100644 doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_4_eb07c84dc0b15b68c99d0ef4144f82f5._comment
 delete mode 100644 doc/bugs/feature_request:_addhash.mdwn
 delete mode 100644 doc/bugs/feature_request:_addhash/comment_1_064e963adb6834813380fd836bb58566._comment
 delete mode 100644 doc/bugs/feature_request:_addhash/comment_2_7b712786c580dd1ca24479664c31eed6._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_10_fadf06f5ab34e36ab130536ec55afc8e._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_11_4a337f7b1140c45e5dd660b40202f696._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_1_05e1398e78218ced9c2da6a2510949e8._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_2_9226f0adf091154c0d8a08b340b71869._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_3_44d3e2096b7d45a1062222bee83a346d._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_4_f2e1d188b7b2d2daf0d832c59a68583e._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_5_998fe58994ecf855310e4b8e6cce9e18._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_7_c713f6316d889c8fc52326f21375c1c4._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_8_6dd23bab7983b8b1f938dd4f21a16f5a._comment
 delete mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_9_961c8f968eff0b39a85b607ee3f7630d._comment
 delete mode 100644 doc/bugs/file_modification_times.mdwn
 delete mode 100644 doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__.mdwn
 delete mode 100644 doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_1_a04b71f4f81c477d18f14d8dfe8b378f._comment
 delete mode 100644 doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_2_0dbc908984b4b5bcc1283db807e058cb._comment
 delete mode 100644 doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_3_ff6cd2bb007d41284a09e470e060c32d._comment
 delete mode 100644 doc/bugs/fix_for_makefile_to_check_if_OS_is_linux_or_not___40__relates_to_the_new_inotify_flag__41__.mdwn
 delete mode 100644 doc/bugs/free_space_checking.mdwn
 delete mode 100644 doc/bugs/free_space_checking/comment_1_a868e805be43c5a7c19c41f1af8e41e6._comment
 delete mode 100644 doc/bugs/free_space_checking/comment_2_8a65f6d3dcf5baa3f7f2dbe1346e2615._comment
 delete mode 100644 doc/bugs/free_space_checking/comment_3_0fc6ff79a357b1619d13018ccacc7c10._comment
 delete mode 100644 doc/bugs/fsck__47__fix_should_check__47__fix_the_permissions_of_.git__47__annex.mdwn
 delete mode 100644 doc/bugs/fsck_claims_failed_checksum_when_less_copies_than_required_are_found.mdwn
 delete mode 100644 doc/bugs/fsck_output.mdwn
 delete mode 100644 doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn
 delete mode 100644 doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_1_03af24b70adbcd9f4b94d009f6b71d0a._comment
 delete mode 100644 doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_2_41214a7d18c66b694645248d6ebeadbf._comment
 delete mode 100644 doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_3_e7ddd77ea35994f2051f840e9b4c7e0c._comment
 delete mode 100644 doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_4_36a70d5a378983a76fcdbb7fba044044._comment
 delete mode 100644 doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment
 delete mode 100644 doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_6_dbff51d00c5645eb1832aa4644889c5e._comment
 delete mode 100644 doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t.mdwn
 delete mode 100644 doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t/comment_1_cafb58eca97a0a66110ac39b169d8de3._comment
 delete mode 100644 doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn
 delete mode 100644 doc/bugs/get_failed__44___but_remote_has_the_file.mdwn
 delete mode 100644 doc/bugs/get_failed__44___but_remote_has_the_file/comment_1_55c8b73ce05dfca11a393bb296b99b9a._comment
 delete mode 100644 doc/bugs/get_failed__44___but_remote_has_the_file/comment_2_474c67a421dca4c245e7bfe495d3f6d3._comment
 delete mode 100644 doc/bugs/get_failed__44___but_remote_has_the_file/comment_3_845e8a23d63fb0b071c63ee736697d26._comment
 delete mode 100644 doc/bugs/get_failed__44___but_remote_has_the_file/comment_4_7dec21cb67e7f4dbdb49da97f2443e8f._comment
 delete mode 100644 doc/bugs/get_fails_for_file:__47____47___web_remotes_if_the_file_is_empty.mdwn
 delete mode 100644 doc/bugs/get_from_bup-remote_with_pubkey_failing.mdwn
 delete mode 100644 doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799.mdwn
 delete mode 100644 doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_1_1c19e716069911f17bbebd196d9e4b61._comment
 delete mode 100644 doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_2_a4d66f29d257044e548313e014ca3dc3._comment
 delete mode 100644 doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_3_f5f1081eb18143383b2fb1f57d8640f5._comment
 delete mode 100644 doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_4_b1f818b85c3540591c48e7ba8560d070._comment
 delete mode 100644 doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_5_67406dd8d9bd4944202353508468c907._comment
 delete mode 100644 doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__.mdwn
 delete mode 100644 doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__/comment_1_13510e954e36484e196e7395a3a9bf1f._comment
 delete mode 100644 doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__/comment_2_7edc478a76983a3b3c68d01f24dce613._comment
 delete mode 100644 doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option.mdwn
 delete mode 100644 doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_1_8cda861c11ef2fff3442e5a0df741939._comment
 delete mode 100644 doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_2_15e06f6db9a14a8217dea25e24ddc23a._comment
 delete mode 100644 doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_3_d36045e2b466882108c5bf09580755fa._comment
 delete mode 100644 doc/bugs/git-annex:_Argument_list_too_long.mdwn
 delete mode 100644 doc/bugs/git-annex:_Argument_list_too_long/comment_1_3f83ea525436b2379ab29a0f860c4669._comment
 delete mode 100644 doc/bugs/git-annex:_Argument_list_too_long/comment_2_b417c94169378ef7d0d278ebae517fa1._comment
 delete mode 100644 doc/bugs/git-annex:_Argument_list_too_long/comment_3_fa925cca216cb810ad80482b19fc6053._comment
 delete mode 100644 doc/bugs/git-annex:_Argument_list_too_long/comment_4_8bd2996107b2d272c32810658e07e715._comment
 delete mode 100644 doc/bugs/git-annex:_Argument_list_too_long/comment_5_378de7d7503a64611eab62f2f5cffef3._comment
 delete mode 100644 doc/bugs/git-annex:_Argument_list_too_long/comment_6_a94e17151348d02999442dd1219babfb._comment
 delete mode 100644 doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__.mdwn
 delete mode 100644 doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_1_f1a7352b04f395e06e0094c1f51b6fff._comment
 delete mode 100644 doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_2_c1890067079cd99667f31cbb4d2e4545._comment
 delete mode 100644 doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_3_213c96085c60c8e52cd803df07240158._comment
 delete mode 100644 doc/bugs/git-annex:_Not_in_a_git_repository._.mdwn
 delete mode 100644 doc/bugs/git-annex:_Not_in_a_git_repository._/comment_1_e10363a912953a646b87c824d1c6e5d4._comment
 delete mode 100644 doc/bugs/git-annex:_Not_in_a_git_repository._/comment_2_9e96063a664b2be8a36d7940e7632d3f._comment
 delete mode 100644 doc/bugs/git-annex:_Not_in_a_git_repository._/comment_3_8c9bd76b0e1200723ec13fbef943a2cc._comment
 delete mode 100644 doc/bugs/git-annex:_Not_in_a_git_repository._/comment_4_8c49979b8a815f0d6f9de39ee9a88730._comment
 delete mode 100644 doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error.mdwn
 delete mode 100644 doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_1_2c54c57f456e4570666fd7a5731dcd27._comment
 delete mode 100644 doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_2_c9a9f070b2eaff9f68f603ca1defec81._comment
 delete mode 100644 doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_3_62ff37a8429cfb3577d4250c701811d0._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed.mdwn
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_10_7cd9de88e55633fc75460f4fe0400f09._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_11_504a944aab34155046f2fd82c2878f3e._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_1_c235cc83c75474e6393e08d2d94b119d._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_2_932f6aaa712298a47868002872e16310._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_3_4bf55320439de152a65e2f21d4a0604b._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_4_cb2cfb798c6171f77eb7c4c4061c0f0c._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_5_05c84dde377298adfd3fc20749b3108f._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_6_bb5141e29c665bc0bb82611ea27d4be8._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_7_5fd39168c9e1bf43909ee0ab3c75c40c._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment
 delete mode 100644 doc/bugs/git-annex:_status:_1_failed/comment_9_573377d444aee0895b231082bc6839a4._comment
 delete mode 100644 doc/bugs/git-annex_3.20130216.1_tests_are_broken.mdwn
 delete mode 100644 doc/bugs/git-annex___38___rsync_can__39__t_copy_files_with___39__:__39___in_their_names.mdwn
 delete mode 100644 doc/bugs/git-annex_add_hangs_indefinitely_on_all_files.mdwn
 delete mode 100644 doc/bugs/git-annex_add_hangs_indefinitely_on_all_files/comment_1_f787155da9a4d92c41546c35f3bd6a08._comment
 delete mode 100644 doc/bugs/git-annex_add_hangs_indefinitely_on_all_files/comment_2_66ad95d98c12b4b26e06e3fe28f0ed01._comment
 delete mode 100644 doc/bugs/git-annex_add_should_repack_as_it_goes.mdwn
 delete mode 100644 doc/bugs/git-annex_add_should_repack_as_it_goes/comment_1_dbcaa0be4cd764128fb7263a95f73a32._comment
 delete mode 100644 doc/bugs/git-annex_add_should_repack_as_it_goes/comment_2_6a27551c4fb7f62ed9f627134c755d01._comment
 delete mode 100644 doc/bugs/git-annex_add_should_repack_as_it_goes/comment_3_ff8b589fbcf25c98abd1c58830074650._comment
 delete mode 100644 doc/bugs/git-annex_branch_corruption.mdwn
 delete mode 100644 doc/bugs/git-annex_branch_push_race.mdwn
 delete mode 100644 doc/bugs/git-annex_direct_fails_on_repositories_with_a_partial_set_of_files.mdwn
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_10_f3594de3ba2ab17771a4b116031511bb._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_11_97de7252bf5d2a4f1381f4b2b4e24ef8._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_12_f1c53c3058a587185e7a78d84987539d._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_13_4f56aea35effe5c10ef37d7ad7adb48c._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_14_cc2a53c31332fe4b828ef1e72c2a4d49._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_15_37f1d669c1fa53ee371f781c7bb820ae._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_16_8a4ab1af59098f4950726cf53636c2b3._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_17_515d5c5fbf5bd0c188a4f1e936d913e2._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_18_db64c91dd1322a0ab168190686db494f._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_19_ff555c271637af065203ca99c9eeaf89._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_1_9a7b09de132097100c1a68ea7b846727._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_20_7e328b970169fffb8bce373d1522743b._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_21_98f632652b0db9131b0173d3572f4d62._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_22_52d41afd7fd0b71a4c8e84ab1b4df5bd._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_23_c2cd8a69c37539c0511bae02016180ca._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_2_174952fc3e3be12912e5fcfe78f2dd13._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_3_a18ada7ac74c63be5753fdb2fe68dae5._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_4_039e945617a6c1852c96974a402db29c._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_5_eacd0b18475c05ab9feed8cf7290b79a._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_6_e55117cb628dc532e468519252571474._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_7_0f4f471102e394ebb01da40e4d0fd9f6._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_8_68e2d6ccdb9622b879e4bc7005804623._comment
 delete mode 100644 doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_9_45b11ddd200261115b653c7a14d28aa9._comment
 delete mode 100644 doc/bugs/git-annex_doesn__39__t_list_files_containing_ISO8859-15_characters.mdwn
 delete mode 100644 doc/bugs/git-annex_doesn__39__t_list_files_containing_ISO8859-15_characters/comment_1_b84e831298c03b12471fb75da597e365._comment
 delete mode 100644 doc/bugs/git-annex_dropunused_has_no_effect.mdwn
 delete mode 100644 doc/bugs/git-annex_dropunused_has_no_effect/comment_1_66b581eb7111a9e98c6406ec75b899cf._comment
 delete mode 100644 doc/bugs/git-annex_dropunused_has_no_effect/comment_2_11c46cd2087511c3d22b7ce7c149b3e9._comment
 delete mode 100644 doc/bugs/git-annex_dropunused_has_no_effect/comment_3_b1c3d8c6ec4b20727aaa9c4b746531b0._comment
 delete mode 100644 doc/bugs/git-annex_dropunused_has_no_effect/comment_4_f05a9a3760858c5ee5c98dd8ab059c28._comment
 delete mode 100644 doc/bugs/git-annex_fails_to_initialize_under_Windows.mdwn
 delete mode 100644 doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_1_082277b9b906a2cc0fcace6790f5cfad._comment
 delete mode 100644 doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_2_b9a3a0104bc56f9110fc58c9df140f12._comment
 delete mode 100644 doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_3_7aeeccd6c4bd97224980a2752e0f8ba8._comment
 delete mode 100644 doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_4_12b6ed59c8b7ded6b6b9150b32e58ce4._comment
 delete mode 100644 doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_5_f975059733fca678e93b791b2a250535._comment
 delete mode 100644 doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_6_66cfbb5ce75d322f68b4c41f11bb15ae._comment
 delete mode 100644 doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_7_9195b2373b0c5298ebbe309414d26ee4._comment
 delete mode 100644 doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_8_bf3f1e801bee930673907d9a8eb4c147._comment
 delete mode 100644 doc/bugs/git-annex_fix_not_noticing_file_renames.mdwn
 delete mode 100644 doc/bugs/git-annex_fix_not_noticing_file_renames/comment_1_4edd95200d59ec5a5426167b8da8e3f9._comment
 delete mode 100644 doc/bugs/git-annex_fix_not_noticing_file_renames/comment_2_a9a44debefb3bdd4b8ed2d1cf53f2338._comment
 delete mode 100644 doc/bugs/git-annex_fix_not_noticing_file_renames/comment_3_0efb11f35b872b75a3fbc4ebb71ac827._comment
 delete mode 100644 doc/bugs/git-annex_get:_requested_key_is_not_present.mdwn
 delete mode 100644 doc/bugs/git-annex_get:_requested_key_is_not_present/comment_1_d4baa6607a61d0e6a7cea1325a5ddf95._comment
 delete mode 100644 doc/bugs/git-annex_get:_requested_key_is_not_present/comment_2_b49725488c3db5e00ede7b65ed9d62fa._comment
 delete mode 100644 doc/bugs/git-annex_get:_requested_key_is_not_present/comment_3_c17a7138579b93c6f14e3444c11664ac._comment
 delete mode 100644 doc/bugs/git-annex_has_issues_with_git_when_staging__47__commiting_logs.mdwn
 delete mode 100644 doc/bugs/git-annex_immediately_re-gets_dropped_files.mdwn
 delete mode 100644 doc/bugs/git-annex_immediately_re-gets_dropped_files/comment_1_09e616a4866e726a48be4febe6375cc8._comment
 delete mode 100644 doc/bugs/git-annex_incorrectly_parses_bare_IPv6_addresses.mdwn
 delete mode 100644 doc/bugs/git-annex_losing_rsync_remotes_with_encryption_enabled.mdwn
 delete mode 100644 doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_.mdwn
 delete mode 100644 doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_/comment_1_850695231926dfe94f11342d3af7f63c._comment
 delete mode 100644 doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_/comment_2_c2a2f801a3e18ad597ff0acf2f104557._comment
 delete mode 100644 doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__.mdwn
 delete mode 100644 doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_1_97abb8442329d19c9687002f43afac74._comment
 delete mode 100644 doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_2_3405f3cd699860ee239cf23ade19e92c._comment
 delete mode 100644 doc/bugs/git-annex_sync_broken_on_squeeze_backports.mdwn
 delete mode 100644 doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn
 delete mode 100644 doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_1_6722fd627ec4add9f2b16546bd8ef341._comment
 delete mode 100644 doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_2_508e475f764e1cb453b756eb50bc3a15._comment
 delete mode 100644 doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_3_1656ba18c519a262c57ef626a3449e77._comment
 delete mode 100644 doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_4_347dc3b6e5bc6c4195ec09d54bc1398e._comment
 delete mode 100644 doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_5_a9c93bfc3278ef8b1117eac2af859bc3._comment
 delete mode 100644 doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_6_804dd62beef64f7d4e203bdb28cbe660._comment
 delete mode 100644 doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_7_4ef107d70647780eb5347cae6f467fed._comment
 delete mode 100644 doc/bugs/git-repair_real_world_failure_example.mdwn
 delete mode 100644 doc/bugs/git_annex_add_..._adds_too_much.mdwn
 delete mode 100644 doc/bugs/git_annex_add_eats_files_when_filename_is_too_long.mdwn
 delete mode 100644 doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_1_9650284913bec2a00cf551b90ab5d8ff._comment
 delete mode 100644 doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_2_c6c8d2a1f444d85c582bc5396b08e148._comment
 delete mode 100644 doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_3_5776864d78d56849001dd12e3adb9cbe._comment
 delete mode 100644 doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_4_371ec7b4ae73280ede31edfe90b42a95._comment
 delete mode 100644 doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_5_4fb04f646de591640f8504c0caf61acd._comment
 delete mode 100644 doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_6_b4055409fe48da95bb3101c0242ef0bc._comment
 delete mode 100644 doc/bugs/git_annex_add_error_with_Andrew_File_System.mdwn
 delete mode 100644 doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_1_bc783e551fc0e8da87bc95bff5b8f73a._comment
 delete mode 100644 doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_2_faefcf69bd61c47566131cb31b78cc19._comment
 delete mode 100644 doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_3_d5014c8b78437b9fddbb1e83d3679081._comment
 delete mode 100644 doc/bugs/git_annex_add_memory_leak.mdwn
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left.mdwn
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_10_9cc749a6efd4359a99316036f5bc867f._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_11_1fed5be9db29866e4dc3d3bb12907bf3._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_12_06d517ac4ef8def4629a40d7c3549bac._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_1_8f081aeba7065d143a453dc128543f59._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_2_54a4b10723fd8a80dd486377ff15ce0d._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_3_f1964e4e07991a251c2795da0361a4e2._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_4_73c38d843c30f00f6fd8883db8e55f62._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_5_7ede5ee312f3abdf78979c0d52a7871a._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_6_e37cf18708f09619442c3a9532d12ed9._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_7_a744ef7dd3a224a911ebb24858bc2fd6._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_8_f97141b255073b90120895148220c2d7._comment
 delete mode 100644 doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment
 delete mode 100644 doc/bugs/git_annex_assistant_--autostart_failed.mdwn
 delete mode 100644 doc/bugs/git_annex_assistant_--autostart_failed/comment_1_746545273b53849c42ff6272324e5155._comment
 delete mode 100644 doc/bugs/git_annex_assistant_--autostart_failed/comment_2_5bdf6f94da12e551ae12e7f550a84d62._comment
 delete mode 100644 doc/bugs/git_annex_assistant_--autostart_failed/comment_3_bfd646f69946a5fe926b270cf94f87cb._comment
 delete mode 100644 doc/bugs/git_annex_content_fails_with_a_parse_error.mdwn
 delete mode 100644 doc/bugs/git_annex_content_fails_with_a_parse_error/comment_1_2b60b6ae0115de13ecf837b34dadcd1d._comment
 delete mode 100644 doc/bugs/git_annex_copy_-f_REMOTE_._doesn__39__t_work_as_expected.mdwn
 delete mode 100644 doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved.mdwn
 delete mode 100644 doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved/comment_1_f1330935a07460c9c8bc82ee8d4709c5._comment
 delete mode 100644 doc/bugs/git_annex_describe_can_break_uuid.log.mdwn
 delete mode 100644 doc/bugs/git_annex_describe_can_break_uuid.log/comment_2_9ead36f13cbde6c822b231441de636ae._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful.mdwn
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_10_457354dc0018333002dc5049935c0feb._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_11_8a6d244165dd238ddf9dd629795de2f6._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_12_30d06bc0f1c37d988a1a31962b57533c._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_1_fc4f51ddcbc69631e2835b86c3489c8e._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_2_9bb1647e6c59f1ed7b13b81ecc33f920._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_3_d434f5c614a27b75d73530b5b918b851._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_4_998e33219d29ea41b0b2a5d2955a9862._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_5_c72e2571e5b8c06bbfa2276a7ad1e8a6._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_6_bc8b42432ba25de8f972c192bc3cdff6._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_7_e7469a4c5e45078ade775f5cbdd17cfc._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_8_bc9e6fd284440a59ffe4e4ed1f73f7d7._comment
 delete mode 100644 doc/bugs/git_annex_does_nothing_useful/comment_9_38a2dbeee3750d79ca9a943a02fceb29._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file.mdwn
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_10_6e29b60cd77f3288e33ad270f95f410e._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_11_ad13e3221ae06086e86800316912d951._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_12_41746b731eae7f280bb668c776022bcb._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_13_56ca8590110abffeed6d826c54ca1136._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_1_73ae438a37e4c5f56fe291448e1c64dd._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_2_aa237adebe7674b8cdb9a967bb5f96a8._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_3_ab403d7abbbbabd498b954b0b9742755._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_4_a35d04440b1220faf9088107c3f17762._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_5_8345331b9b313769ba401da2ffd89332._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_6_7eb535ca38b3e84d44d0f8cbf5e61b8b._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_7_a3aa4231a82917c56cbdf52b65db7133._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment
 delete mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_9_7d80f131f43312bb061df2be7fa956ef._comment
 delete mode 100644 doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files.mdwn
 delete mode 100644 doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_1_a6cde4aa495512344fa7f50e10749c68._comment
 delete mode 100644 doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_2_4ac3b87ec0bc0514c4eff9f5a75b9f5d._comment
 delete mode 100644 doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_3_d18b1fdc866edf2786d2c6b7ec55119f._comment
 delete mode 100644 doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_4_31e4fcbf63c11cc374a849daf3ce1dbc._comment
 delete mode 100644 doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn
 delete mode 100644 doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos/comment_1_fc59fbd1cdf8ca97b0a4471d9914aaa1._comment
 delete mode 100644 doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos/comment_2_273a45e6977d40d39e0d9ab924a83240._comment
 delete mode 100644 doc/bugs/git_annex_get_choke_when_remote_is_an_ssh_url_with_a_port.mdwn
 delete mode 100644 doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn
 delete mode 100644 doc/bugs/git_annex_import_destroys_a_fellow_git_annex_repository.mdwn
 delete mode 100644 doc/bugs/git_annex_importfeed_fails.mdwn
 delete mode 100644 doc/bugs/git_annex_indirect_can_fail_catastrophically.mdwn
 delete mode 100644 doc/bugs/git_annex_indirect_can_fail_catastrophically/comment_1_0b085e7e8c8e364f479574bc00c7c394._comment
 delete mode 100644 doc/bugs/git_annex_info_listings_can_be_confusing.mdwn
 delete mode 100644 doc/bugs/git_annex_initremote_needs_some___34__error_checking__34__.mdwn
 delete mode 100644 doc/bugs/git_annex_initremote_walks_.git-annex.mdwn
 delete mode 100644 doc/bugs/git_annex_lock_dangerous.mdwn
 delete mode 100644 doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn
 delete mode 100644 doc/bugs/git_annex_migrate_leaves_old_backend_versions_around/comment_1_f3e418144e5a5a9b3eda459546fc2bb0._comment
 delete mode 100644 doc/bugs/git_annex_should_use___39__git_add_-f__39___internally.mdwn
 delete mode 100644 doc/bugs/git_annex_should_use___39__git_add_-f__39___internally/comment_1_7683bf02cf9e97830fb4690314501568._comment
 delete mode 100644 doc/bugs/git_annex_sync___40__sync_content_without_--content_flag__41__.mdwn
 delete mode 100644 doc/bugs/git_annex_sync___40__sync_content_without_--content_flag__41__/comment_1_a797542acb1f0c51dd4c75e4566558f0._comment
 delete mode 100644 doc/bugs/git_annex_test_under_windows_8.1.mdwn
 delete mode 100644 doc/bugs/git_annex_uninit_loses_content_when_interrupted.mdwn
 delete mode 100644 doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment
 delete mode 100644 doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment
 delete mode 100644 doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex.mdwn
 delete mode 100644 doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment
 delete mode 100644 doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_2_3aa125635609fce41ab0c98cefb81f98._comment
 delete mode 100644 doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems.mdwn
 delete mode 100644 doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_1_8ba4fdb9f2d3bd44db5e910526cb9124._comment
 delete mode 100644 doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_2_2a4a2b3e287a0444a1c8e8d98768a206._comment
 delete mode 100644 doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_3_dacfdb8322045fc4ceefc9128bf7c505._comment
 delete mode 100644 doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_4_7889a3ff5ce80c6322448aa674df8525._comment
 delete mode 100644 doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_5_6d28c2537ce24eeb3496ca349823defd._comment
 delete mode 100644 doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_6_4bf14ecef622988e80976c0fb55c24b9._comment
 delete mode 100644 doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_7_d2e5382fe0f38fb9dd9ee69901c68151._comment
 delete mode 100644 doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_8_b282757537cda863d3dc6d0bbfd6b656._comment
 delete mode 100644 doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent.mdwn
 delete mode 100644 doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent/comment_1_a636ffe55b11c46a0afcc0b9a3a88cd4._comment
 delete mode 100644 doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent/comment_2_5e1ad57420efd16ae09c9e5cad55b5f2._comment
 delete mode 100644 doc/bugs/git_annex_unused_seems_to_check_for_current_path.mdwn
 delete mode 100644 doc/bugs/git_annex_upgrade_output_is_inconsistent_and_spammy.mdwn
 delete mode 100644 doc/bugs/git_annex_upgrade_output_is_inconsistent_and_spammy/comment_1_3a01c81efba321b0e46d1bc0426ad8d1._comment
 delete mode 100644 doc/bugs/git_annex_version_should_without_being_in_a_repo_.mdwn
 delete mode 100644 doc/bugs/git_annex_version_should_without_being_in_a_repo_/comment_1_e7b26eeb1a765fd83280ef907c0deef2._comment
 delete mode 100644 doc/bugs/git_annex_webapp_runs_on_wine.mdwn
 delete mode 100644 doc/bugs/git_annex_webapp_runs_on_wine/comment_1_c71dfa42780c0fc78f88ce054e5f3ee3._comment
 delete mode 100644 doc/bugs/git_annex_webapp_runs_on_wine/comment_2_f28441b18b0be90c1e58348455ce09d9._comment
 delete mode 100644 doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive.mdwn
 delete mode 100644 doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_1_7707017fbf3d92ee21d600fe0aefce4f._comment
 delete mode 100644 doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_2_f3392ec3ca7392823cbad2cc9b77f54e._comment
 delete mode 100644 doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_3_b3d016a487b12748fe2c4d14300eb158._comment
 delete mode 100644 doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_4_61f600511a3172f0707e5809fc444d0c._comment
 delete mode 100644 doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_5_8cf029ac7bf3c19dcb0b613eed3b52ac._comment
 delete mode 100644 doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_6_e40d88eba7d8aec1530ce1d32d1c85f2._comment
 delete mode 100644 doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_7_b101fab9e690d1b335a1a29abab68d6c._comment
 delete mode 100644 doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_8_b30d32086314a7e357f3dd6608828ee5._comment
 delete mode 100644 doc/bugs/git_annix_breaks_git_commit_after_uninstall.mdwn
 delete mode 100644 doc/bugs/git_annix_breaks_git_commit_after_uninstall/comment_1_c8b1bab40d3bb2468a5bba7b116e854e._comment
 delete mode 100644 doc/bugs/git_annix_breaks_git_commit_after_uninstall/comment_2_4173770375fca51dcaf9b974296d041a._comment
 delete mode 100644 doc/bugs/git_defunct_processes___40__child_of_git-annex_assistant__41__.mdwn
 delete mode 100644 doc/bugs/git_defunct_processes___40__child_of_git-annex_assistant__41__/comment_1_5e3f4b63db5cd32b63fb3e6a78f9b093._comment
 delete mode 100644 doc/bugs/git_repo_fails_to_checkout.mdwn
 delete mode 100644 doc/bugs/git_repo_fails_to_checkout/comment_1_d92e7e3b41382501a08f6a66c673b1fd._comment
 delete mode 100644 doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated.mdwn
 delete mode 100644 doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated/comment_1_2a5a07498df9d38531d4570f7b463b9a._comment
 delete mode 100644 doc/bugs/gix-annex_help_is_homicidal.mdwn
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails.mdwn
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails/comment_1_ec911f920db6c354ba998ffbb5886606._comment
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails/comment_2_bf2a3ab1bbe258bd501ec4b776882adf._comment
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails/comment_3_c0142427400323c00bd8294415ae32c5._comment
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails/comment_4_b56db4b5afc276f88a2b980e22fda8a0._comment
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails/comment_5_a4eda81e5f927c463593bc48fbe84077._comment
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails/comment_6_2f0b9331d16a208883bac586258a7b50._comment
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails/comment_7_c05c484a6134f93796cff08de0f63e80._comment
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails/comment_8_f2cb5467ebe80cf67e1155b771b73978._comment
 delete mode 100644 doc/bugs/gpg_bundled_with_OSX_build_fails/comment_9_27bbda7e31f55b29e1473555ee17e613._comment
 delete mode 100644 doc/bugs/gpg_error_on_android.mdwn
 delete mode 100644 doc/bugs/gpg_error_on_android/comment_1_870583fd1b7a33b688b9a228077d1333._comment
 delete mode 100644 doc/bugs/gpg_error_on_android/comment_2_9ce5511a109bde50d8cf87bad0268b4a._comment
 delete mode 100644 doc/bugs/gpg_error_on_android/comment_3_b345e80f38d38f82cfcfce3102138fb8._comment
 delete mode 100644 doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment
 delete mode 100644 doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant.mdwn
 delete mode 100644 doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant/comment_1_7b409701c650b55b3472accd70555f16._comment
 delete mode 100644 doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant/comment_2_40b00f7258512677516ec5036b89090f._comment
 delete mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation.mdwn
 delete mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment
 delete mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_2_dd11fd25c8bb1f2d7e1292c07abf553e._comment
 delete mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_3_543d8a13756c1355a5752867bdcbefd3._comment
 delete mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_4_6441cf25e6bd62c96d7e766da9bdd7fb._comment
 delete mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_5_72e152294e36bc5f2d78e8e2ebed6a23._comment
 delete mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_6_890e85df05903795e01efbd7879f9c87._comment
 delete mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_7_042047f9fcc45abbfa47c3973d79f08e._comment
 delete mode 100644 doc/bugs/gpg_needs_--use-agent.mdwn
 delete mode 100644 doc/bugs/gsha256sum_crashes.mdwn
 delete mode 100644 doc/bugs/gsha256sum_crashes/comment_1_8597d8ee29232494b1795526b6a0d8d1._comment
 delete mode 100644 doc/bugs/gsha256sum_crashes/comment_2_e410fc1998fbc7db8c13081f76acf7fc._comment
 delete mode 100644 doc/bugs/gsha256sum_crashes/comment_3_f796dd49097425148b785bb7b6213df6._comment
 delete mode 100644 doc/bugs/gsha256sum_crashes/comment_4_1c46b4ad0c981c6105ffb8531223f0b1._comment
 delete mode 100644 doc/bugs/gsha256sum_crashes/comment_5_3fa106ed7fb30226ee7c48b66edb963c._comment
 delete mode 100644 doc/bugs/gsha256sum_crashes/comment_6_276b181b2aeb1512e0468b88598e0a84._comment
 delete mode 100644 doc/bugs/gsha256sum_crashes/comment_7_c2898422ceb9e103d8acdde866b7a211._comment
 delete mode 100644 doc/bugs/hGetContents:_user_error.mdwn
 delete mode 100644 doc/bugs/hGetContents:_user_error/comment_1_30178f151f8c60d2ff856ca543dc506c._comment
 delete mode 100644 doc/bugs/hGetContents:_user_error/comment_2_f74eeed4a007058a22183fd678ecd6c6._comment
 delete mode 100644 doc/bugs/hGetContents:_user_error/comment_3_515e562228a89a13d6d857a874f4a468._comment
 delete mode 100644 doc/bugs/hGetContents:_user_error/comment_4_8c6ed5e459c5c66b77db446c6317114c._comment
 delete mode 100644 doc/bugs/hGetContents:_user_error/comment_5_f80bce48c3f96b0cd6892af43ee88a96._comment
 delete mode 100644 doc/bugs/hGetContents:_user_error/comment_6_69dc09e4ae726856dafbeec34170671c._comment
 delete mode 100644 doc/bugs/hGetContents:_user_error/comment_7_3f66b03f773341fad94ec16b4f55edaa._comment
 delete mode 100644 doc/bugs/hGetContents:_user_error/comment_8_a697e2d36abfc999e65c9f587c0de56e._comment
 delete mode 100644 doc/bugs/hGetContents:_user_error/comment_9_da7c5905a64bb6779970f9394155e629._comment
 delete mode 100644 doc/bugs/haskell-dbus_problems_on_OSX___40__or_this_a_general_problem__41__.mdwn
 delete mode 100644 doc/bugs/host_with_rysnc_installed__44___not_recognized.mdwn
 delete mode 100644 doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_1_3ff000eb3efde41426c7b086ae627dcf._comment
 delete mode 100644 doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_2_34e592ab057df2df54e13d3f5cae64f0._comment
 delete mode 100644 doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_3_05ffbae13d8f9b08315f40bb9b206f46._comment
 delete mode 100644 doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_4_99d1f151263ca3433dd4afa8a928b1fe._comment
 delete mode 100644 doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_5_6ef1a377b0b4d3efeffdf9693d0b496b._comment
 delete mode 100644 doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_6_d9e36828ad55f3181a1c650010f23d6b._comment
 delete mode 100644 doc/bugs/immediately_drops_files.mdwn
 delete mode 100644 doc/bugs/immediately_drops_files/comment_1_9ef6e694ef8a8eee7a42f88554475db7._comment
 delete mode 100644 doc/bugs/immediately_drops_files/comment_2_76e4f8b73ab60b2540dd2a3e5379791d._comment
 delete mode 100644 doc/bugs/immediately_drops_files/comment_3_788db083f5ba2e5589c3b952203ec954._comment
 delete mode 100644 doc/bugs/immediately_drops_files/comment_4_425b79865eb77d69d0b7a71a14639f81._comment
 delete mode 100644 doc/bugs/immediately_drops_files/comment_5_7c9f660b6bcec31827a44a650e9d4622._comment
 delete mode 100644 doc/bugs/importfeed_fails__44___bad_feed_content.mdwn
 delete mode 100644 doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast.mdwn
 delete mode 100644 doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast/comment_1_4ccfabbaf75e139b32f6fa6f7bc6a7fe._comment
 delete mode 100644 doc/bugs/importfeed_should_allow_pubdate_in_the_template.mdwn
 delete mode 100644 doc/bugs/importfeed_uses___34____95__foo__34___as_extension.mdwn
 delete mode 100644 doc/bugs/internal_server_error:_unknown_UUID_on_webapp.mdwn
 delete mode 100644 doc/bugs/internal_server_error_creating_repo_on_ssh_server.mdwn
 delete mode 100644 doc/bugs/internal_server_error_creating_repo_on_ssh_server/comment_1_4a2c9338d5c779496049d78e29cf5cbd._comment
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option.mdwn
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_1_14a2f775f43a86129ce3649a06f8ba0b._comment
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_2_7b277320fcffd8d03e0d3d31398eb571._comment
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_3_ba9dd8f2cc46640383d4339a3661571f._comment
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_4_274ae39d55545bde0be931d7a6c42c94._comment
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_5_242291d46acc61bdfc112e3316de528b._comment
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_6_76b936263e82ca6c415a16ed57e770b4._comment
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_7_9ccd3749fd9f32b0906c0b9428cc514f._comment
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_8_4e8982668b5044b2286d55c90adb9da3._comment
 delete mode 100644 doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_9_aaf0ee250972d737a2ca57de5b5f1c0a._comment
 delete mode 100644 doc/bugs/interrupting_migration_causes_problems.mdwn
 delete mode 100644 doc/bugs/javascript_functions_qouting_issue.mdwn
 delete mode 100644 doc/bugs/journal_commit_error_when_using_annex.mdwn
 delete mode 100644 doc/bugs/journal_commit_error_when_using_annex/comment_1_38f60ca3503ea1530c4bd2cde5c9182f._comment
 delete mode 100644 doc/bugs/journal_commit_error_when_using_annex/comment_2_6de455a67f37d9ee0a307a78123781bf._comment
 delete mode 100644 doc/bugs/json_is_broken_for_status.mdwn
 delete mode 100644 doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX.mdwn
 delete mode 100644 doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_1_91c911c29fd126ddc365c561591f627e._comment
 delete mode 100644 doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_2_c316aead931a6a2377a4515bbb34ac5b._comment
 delete mode 100644 doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn
 delete mode 100644 doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_1_f8d1720aa26c719609720acf0772606e._comment
 delete mode 100644 doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_2_0527569ea2924721d19dadcf4fe0ec5a._comment
 delete mode 100644 doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_3_5b67ff08a897ea3d2266ccc910ab4278._comment
 delete mode 100644 doc/bugs/mac_os_x_10.7_DMG_out_of_date.mdwn
 delete mode 100644 doc/bugs/make_SHA512E_the_default.mdwn
 delete mode 100644 doc/bugs/making_annex-merge_try_a_fast-forward.mdwn
 delete mode 100644 doc/bugs/map_not_respecting_annex_ssh_options__63__.mdwn
 delete mode 100644 doc/bugs/map_not_respecting_annex_ssh_options__63__/comment_1_c63a1ed5909d53f116f06e60aba74dc6._comment
 delete mode 100644 doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build.mdwn
 delete mode 100644 doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_1_0527581ea60d28bb28504fa2a355ed87._comment
 delete mode 100644 doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_2_926a87b60e20d286d49639c8dad13a1a._comment
 delete mode 100644 doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_3_c509fba1a9adacfd26a2bd12b4aea988._comment
 delete mode 100644 doc/bugs/minor_bug:_errors_are_not_verbose_enough.mdwn
 delete mode 100644 doc/bugs/missing_dependency_in_git-annex-3.20130216.mdwn
 delete mode 100644 doc/bugs/missing_kde__47__gnome_menu_item..mdwn
 delete mode 100644 doc/bugs/network___62____61___2.4.0.1_is_not_in_Haskell_Platform_2012.4.0.0.mdwn
 delete mode 100644 doc/bugs/network___62____61___2.4.0.1_is_not_in_Haskell_Platform_2012.4.0.0/comment_1_2c4b3757bb8de563edca65aeabcbbc5a._comment
 delete mode 100644 doc/bugs/nfs_mounted_repo_results_in_errors_on_drop_move.mdwn
 delete mode 100644 doc/bugs/no_git-annex_cli_for_performing_upgrades_or_setting_upgrade_options.mdwn
 delete mode 100644 doc/bugs/not_possible_to_have_annex_on_a_separate_filesystem.mdwn
 delete mode 100644 doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn
 delete mode 100644 doc/bugs/on--git-dir_and_--work-tree_options.mdwn
 delete mode 100644 doc/bugs/one_test_fail_on_osx.mdwn
 delete mode 100644 doc/bugs/ordering.mdwn
 delete mode 100644 doc/bugs/pages_of_packfile_errors.mdwn
 delete mode 100644 doc/bugs/pages_of_packfile_errors/comment_1_eb2989112b38bb27ce8f691dd5d318e5._comment
 delete mode 100644 doc/bugs/pages_of_packfile_errors/comment_2_69fba53035ebea213ae1c11be5326690._comment
 delete mode 100644 doc/bugs/pages_of_packfile_errors/comment_3_73b9f574e8ce36d5e0d0f6c6a89006b7._comment
 delete mode 100644 doc/bugs/pasting_into_annex_on_OSX.mdwn
 delete mode 100644 doc/bugs/pasting_into_annex_on_OSX/comment_1_4eab52bb6eda92e39bdaa8eee8f31a7f._comment
 delete mode 100644 doc/bugs/pasting_into_annex_on_OSX/comment_2_f1b58adfec179b75c1fc2bf578a3b5c4._comment
 delete mode 100644 doc/bugs/pasting_into_annex_on_OSX/comment_3_270aa7680c3b899a92ce6543eaba666a._comment
 delete mode 100644 doc/bugs/pasting_into_annex_on_OSX/comment_4_ec11a80d5b0f78c7a927f8aa71a6c57a._comment
 delete mode 100644 doc/bugs/pasting_into_annex_on_OSX/comment_5_1928bd25e5e6874a3b83c2f2adc776f5._comment
 delete mode 100644 doc/bugs/pasting_into_annex_on_OSX/comment_6_0fe288f54b781a0c51395cb32f0e2f9d._comment
 delete mode 100644 doc/bugs/problem_to_addurl_--file_with_ftp.mdwn
 delete mode 100644 doc/bugs/problem_to_addurl_--file_with_ftp/comment_1_2bf44f1653069fb2ed0b124cf8581a48._comment
 delete mode 100644 doc/bugs/problem_to_addurl_--file_with_ftp/comment_2_c85266a9359a9f45e632f31c016a45dc._comment
 delete mode 100644 doc/bugs/problem_to_addurl_--file_with_ftp/comment_3_5bba62e1dd4118bcf7e1c990c7009239._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names.mdwn
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_10_c53c309771caa41accab5523cc6998dd._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_1_3c7e3f021c2c94277eecf9c8af6cec5f._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_2_bad4c4c5f54358d1bc0ab2adc713782a._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_3_4f936a5d3f9c7df64c8a87e62b7fbfdc._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_4_93bee35f5fa7744834994bc7a253a6f9._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_5_519cda534c7aea7f5ad5acd3f76e21fa._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_6_52e0bfff2b177b6f92e226b25d2f3ff1._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_7_0cc588f787d6eecfa19a8f6cee4b07b5._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_8_ff5c6da9eadfee20c18c86b648a62c47._comment
 delete mode 100644 doc/bugs/problems_with_utf8_names/comment_9_f358e617799e5a4e3afc6536d419eb08._comment
 delete mode 100644 doc/bugs/quvi_0.9.5_does_not_work_with_git-annex.mdwn
 delete mode 100644 doc/bugs/quvi_0.9.5_does_not_work_with_git-annex/comment_1_d0d2bcd97ef5c9bce8a57c4184a176e0._comment
 delete mode 100644 doc/bugs/quvi_0.9.5_does_not_work_with_git-annex/comment_2_ff9661198257b8c5e2e8ca3d85a7471c._comment
 delete mode 100644 doc/bugs/reinject_should_leave_file_in_place_on_checksum_mismatch.mdwn
 delete mode 100644 doc/bugs/removable_device_configurator_chokes_on_spaces.mdwn
 delete mode 100644 doc/bugs/rename:_permission_denied__44___after_direct_mode_switch.mdwn
 delete mode 100644 doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment
 delete mode 100644 doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_2_93af8f48a01b6e2d011bd6f60499ccd2._comment
 delete mode 100644 doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_3_f8fba1955e62360061613e5898b3d74e._comment
 delete mode 100644 doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_4_abffe1fb3b3e684b126e4768089dc5f4._comment
 delete mode 100644 doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_5_bccc53d2d6f659f21965042a057358f5._comment
 delete mode 100644 doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_6_ac8b3b042b882680f0eb0d53ade1ce15._comment
 delete mode 100644 doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote.mdwn
 delete mode 100644 doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote/comment_1_d6aad1831674586fe4cdf61dd2a4bbb9._comment
 delete mode 100644 doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote/comment_2_8591e174c1a8cddfae9371407a58ff1c._comment
 delete mode 100644 doc/bugs/repair_fails_when_home_on_seperate_partition.mdwn
 delete mode 100644 doc/bugs/restart_daemon_required.mdwn
 delete mode 100644 doc/bugs/restart_daemon_required/comment_1_f79ac16cc9f1e3b08cd121bf5efb29c3._comment
 delete mode 100644 doc/bugs/restart_daemon_required/comment_2_50c1b268a3cc4514681059eabca674e3._comment
 delete mode 100644 doc/bugs/restart_daemon_required/comment_3_1716e0f3c7c44dc77ebf7f00fdd8f9e3._comment
 delete mode 100644 doc/bugs/restart_daemon_required/comment_4_3ce776786eca83fcb8ff94c8f6ff3eb9._comment
 delete mode 100644 doc/bugs/rsync_remote_shows_no_progress.mdwn
 delete mode 100644 doc/bugs/rsync_remote_shows_no_progress/comment_1_a7f5d646a924c462b987561cf6fc4318._comment
 delete mode 100644 doc/bugs/scp_interrupt_to_background.mdwn
 delete mode 100644 doc/bugs/show_version_without_having_to_be_in_a_git_repo.mdwn
 delete mode 100644 doc/bugs/smarter_flood_filling.mdwn
 delete mode 100644 doc/bugs/softlink_mtime.mdwn
 delete mode 100644 doc/bugs/ssh-askpass_locks_me_out_of_x_console.mdwn
 delete mode 100644 doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_1_1def05a57e25b6765b881f22bc6d82a2._comment
 delete mode 100644 doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_2_cd4869faf350c81deb1de6fa25f32876._comment
 delete mode 100644 doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_3_87c980feb28a05d12a259fb2b3091cdf._comment
 delete mode 100644 doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_4_33a367dbeb5c7bf8692a414f20d8de69._comment
 delete mode 100644 doc/bugs/ssh_connection_caching_broken_on_NTFS.mdwn
 delete mode 100644 doc/bugs/ssh_connection_caching_broken_on_NTFS/comment_1_54e7e12514f4c109fd57a4eb744b731a._comment
 delete mode 100644 doc/bugs/ssh_keys_have_wrong_permissions___40__Ubuntu_12.04_LTS__44___current_linux_build_as_of_Mar_6th___39__14__41__.mdwn
 delete mode 100644 doc/bugs/ssh_keys_have_wrong_permissions___40__Ubuntu_12.04_LTS__44___current_linux_build_as_of_Mar_6th___39__14__41__/comment_1_462c377dca2484e5598a0b71d91ab64a._comment
 delete mode 100644 doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__.mdwn
 delete mode 100644 doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_1_6203563196a70b8356102a48927e4ccd._comment
 delete mode 100644 doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_2_cee9428c651e6574f93effed31d83fb9._comment
 delete mode 100644 doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_3_9d8f9346b8c931815fa4967835b67560._comment
 delete mode 100644 doc/bugs/standalone_tarball_symlink_to_PATH_broken.mdwn
 delete mode 100644 doc/bugs/standalone_tarball_symlink_to_PATH_broken/comment_1_c9b41b957df03fadf76d93b23508b85e._comment
 delete mode 100644 doc/bugs/standalone_tarball_symlink_to_PATH_broken/comment_2_0cf22fe2518a52245ca4a8977aa3ed78._comment
 delete mode 100644 doc/bugs/submodule_path_problem.mdwn
 delete mode 100644 doc/bugs/submodule_path_problem/comment_1_69aec9207d2e9da4bc042d3f4963d80e._comment
 delete mode 100644 doc/bugs/submodule_path_problem/comment_2_53d9eb28cb70b51637470175a80ddf35._comment
 delete mode 100644 doc/bugs/submodule_path_problem/comment_3_aa5e0f99000a5b4988bccbb2ca28353b._comment
 delete mode 100644 doc/bugs/submodule_path_problem/comment_4_ab1508a5a04e2106aad5e7985775a6fa._comment
 delete mode 100644 doc/bugs/submodule_path_problem/comment_5_8c7539d1c11b81f5d46aa8e1c61745ae._comment
 delete mode 100644 doc/bugs/submodule_path_problem/comment_6_cacc91afcb1739dfca3a60590bb70356._comment
 delete mode 100644 doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__.mdwn
 delete mode 100644 doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__/comment_1_6208e70a21a048d5423926d16e32d421._comment
 delete mode 100644 doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__/comment_2_8765b6190e79251637bb59ba28f245c1._comment
 delete mode 100644 doc/bugs/sync_--content_tries_to_copy_content_to_metadata_only_repos.mdwn
 delete mode 100644 doc/bugs/sync_command_tries_to_connect_new_remote_despite_not_being_asked_to.mdwn
 delete mode 100644 doc/bugs/sync_command_tries_to_connect_new_remote_despite_not_being_asked_to/comment_1_dcd52b57192e83fe365f21dc12461008._comment
 delete mode 100644 doc/bugs/test_suite_failure_on_samba_mount.mdwn
 delete mode 100644 doc/bugs/test_suite_failure_on_samba_mount/comment_1_e074b20801b921ee2661025a050a8af2._comment
 delete mode 100644 doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn
 delete mode 100644 doc/bugs/tests_fail_when_there_is_no_global_.gitconfig_for_the_user.mdwn
 delete mode 100644 doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform.mdwn
 delete mode 100644 doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_1_20a6fe046111e9ae56fd4d9c9f41f536._comment
 delete mode 100644 doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_2_6fdc5f8b07908c6eda8a97690408f44e._comment
 delete mode 100644 doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_3_014474a133c7ff0131029d8721afc710._comment
 delete mode 100644 doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_4_9c537e251dc99667fe87870804d802c2._comment
 delete mode 100644 doc/bugs/the_tip_at_commit_6cecc26206c4a539999b04664136c6f785211a41_disables_the_watch_command_on_OSX.mdwn
 delete mode 100644 doc/bugs/three_character_directories_created.mdwn
 delete mode 100644 doc/bugs/three_character_directories_created/comment_1_dd91de24dab4f2eaded1f7d659869d4d._comment
 delete mode 100644 doc/bugs/three_character_directories_created/comment_2_f6375964a6c8bb1e6c5b7238effca66d._comment
 delete mode 100644 doc/bugs/three_character_directories_created/comment_3_776e0a9b938d8b260a5111594b442536._comment
 delete mode 100644 doc/bugs/three_character_directories_created/comment_4_e288bacdb336c4886adb6eeb4dca1e92._comment
 delete mode 100644 doc/bugs/three_character_directories_created/comment_5_359b80948ac92a0f1eb695599456486c._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber.mdwn
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_10_fc5ec5505f141bb9135e772d1094bc4d._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_11_0df2210c30dec6d88d7858d93eec19a3._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_1_41682b2e72e657e0f23af244f8345e85._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_2_c7b4ea9aea6839763eb8b89e8d6a5ad5._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_3_063f5e5e554ad6710f16394906d87616._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_4_197ad39b4a46936afeeb04eb26cf1ef3._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_5_0b0d829ccd255be0177ae9d8f6b10e63._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_6_37a8e19440c764317589bc4248cbccdf._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_7_12eb333327d31ca2bfee3f3c5e26d641._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_8_e6b1084b2f18d8e536c8692e165754a3._comment
 delete mode 100644 doc/bugs/three_way_sync_via_S3_and_Jabber/comment_9_2120a1c3e5f490a55f68bb1bef5efd0d._comment
 delete mode 100644 doc/bugs/tmp_file_handling.mdwn
 delete mode 100644 doc/bugs/tmp_file_handling/comment_1_0300c11ee3f94a9e7c832671e16f5511._comment
 delete mode 100644 doc/bugs/tmp_file_handling/comment_2_cc14c7a79a544e47654e4cd8abc85edd._comment
 delete mode 100644 doc/bugs/transferkey_fails_due_to_gpg.mdwn
 delete mode 100644 doc/bugs/transferkey_fails_due_to_gpg/comment_1_f6434400d528a0fa59c056995ff2e6f3._comment
 delete mode 100644 doc/bugs/transferkey_fails_due_to_gpg/comment_2_c540b05b62a3186a87efcb180ea2a52d._comment
 delete mode 100644 doc/bugs/transferkey_fails_due_to_gpg/comment_3_9ad2ef73169dbd2866da2f4259ab0f00._comment
 delete mode 100644 doc/bugs/transferkey_fails_due_to_gpg/comment_4_7631b8842efba6a4aad87386ce9443a7._comment
 delete mode 100644 doc/bugs/tweaks_to_directory_special_remote_doco.mdwn
 delete mode 100644 doc/bugs/typo_in___34__ready_to_add_remote_server__34___message.mdwn
 delete mode 100644 doc/bugs/unable_to_sync_complains_of_missing_git-upload_and_receive_pack.mdwn
 delete mode 100644 doc/bugs/unable_to_sync_complains_of_missing_git-upload_and_receive_pack/comment_1_8b0302bba2b99df0842dfead649080e7._comment
 delete mode 100644 doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken.mdwn
 delete mode 100644 doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken/comment_1_1931e733f0698af5603a8b92267203d4._comment
 delete mode 100644 doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken/comment_2_40920b88537b7715395808d8aa94bf03._comment
 delete mode 100644 doc/bugs/unannex_command_doesn__39__t_all_files.mdwn
 delete mode 100644 doc/bugs/unannex_removes_object_even_if_referred_to_by_others.mdwn
 delete mode 100644 doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_1_0ce72d0f67082f202cfa58b7c00f2fd3._comment
 delete mode 100644 doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_2_647f49ffcaa348660659f9954a59b3ae._comment
 delete mode 100644 doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_3_3f7f4b55b7ec2641a70109788e0b5672._comment
 delete mode 100644 doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_4_313d393c416495aa0f8573113e41c2f7._comment
 delete mode 100644 doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_5_c0e7742672db2629bd906cebefe74f72._comment
 delete mode 100644 doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_6_c56171665db3ed14109a09097d49ac5d._comment
 delete mode 100644 doc/bugs/unannex_vs_unlock_hook_confusion.mdwn
 delete mode 100644 doc/bugs/unfinished_repos_in_webapp.mdwn
 delete mode 100644 doc/bugs/unfinished_repos_in_webapp/comment_1_9628b100e39489be9f28ef75276a7341._comment
 delete mode 100644 doc/bugs/unfinished_repos_in_webapp/comment_2_ba0fbff536b1d067c4098db401dc49f2._comment
 delete mode 100644 doc/bugs/unfinished_repos_in_webapp/comment_3_fd554aa7d93117177784a29270ccf790._comment
 delete mode 100644 doc/bugs/unhappy_without_UTF8_locale.mdwn
 delete mode 100644 doc/bugs/unicode_tags.mdwn
 delete mode 100644 doc/bugs/uninit_and_indirect_don__39__t_work_on_android.mdwn
 delete mode 100644 doc/bugs/uninit_and_indirect_don__39__t_work_on_android/comment_1_fec69c4c41987b9469eaa8f745c0a124._comment
 delete mode 100644 doc/bugs/uninit_and_indirect_don__39__t_work_on_android/comment_2_54c3fa77a069b36d03c41aad08fee9af._comment
 delete mode 100644 doc/bugs/uninit_does_not_abort_when_hard_link_creation_fails.mdwn
 delete mode 100644 doc/bugs/uninit_does_not_work_in_old_repos.mdwn
 delete mode 100644 doc/bugs/uninit_does_not_work_in_old_repos/comment_1_bc0619c6e17139df74639448aa6a0f72._comment
 delete mode 100644 doc/bugs/uninit_loses_data_if_git-annex_add_didn__39__t_complete.mdwn
 delete mode 100644 doc/bugs/uninit_should_not_run_when_branch_git-annex_is_checked_out.mdwn
 delete mode 100644 doc/bugs/unlock_fails_silently_with_directory_symlinks.mdwn
 delete mode 100644 doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_.mdwn
 delete mode 100644 doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_1_a634a9f1c023bf836183de64abab1224._comment
 delete mode 100644 doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_2_d9ae61a7c3f1eb243ca650945b40f21d._comment
 delete mode 100644 doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_3_fe229c03c14e8eb2b57389e0e193ed99._comment
 delete mode 100644 doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_4_fa12afe295de63c4aa7eb043b715325a._comment
 delete mode 100644 doc/bugs/unlock_then_lock_of_uncommitted_file_loses_it.mdwn
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again.mdwn
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_10_51097a6b84edcc607abc0e6e21ca21f2._comment
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_1_c34a4009213c410bba3c147ae0552029._comment
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_2_634542867fd28962c47b7bc3ea022175._comment
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_3_301f3ff2d203ac4c58a037e553b2c14d._comment
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_4_82ecdc88ccc1f87386b128adc4ff9af4._comment
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_6_158b2ba3da815910505899606177d415._comment
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_6_b068924802f3917e3e005350cb0cc2a2._comment
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_7_f4772858c927d4a62edc3caf59b5da10._comment
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_8_d0923d2950357f4444c5ef94ff196ba3._comment
 delete mode 100644 doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_9_7fb30cb80aecc60e48c64846aa185206._comment
 delete mode 100644 doc/bugs/utf8.mdwn
 delete mode 100644 doc/bugs/utf8/comment_10_f298b8b480d3ab2dd9c279589afcd0ea._comment
 delete mode 100644 doc/bugs/utf8/comment_11_a8864a46f8154680beeea27449ac6f09._comment
 delete mode 100644 doc/bugs/utf8/comment_12_2202c3479d19d306f31aac5a47b55e7d._comment
 delete mode 100644 doc/bugs/utf8/comment_13_7044d2c5bb1c91ee37eb9868963a1ff2._comment
 delete mode 100644 doc/bugs/utf8/comment_14_656b3caa16ae93b092fb5804fa575a3b._comment
 delete mode 100644 doc/bugs/utf8/comment_15_25b3d4c47c45b72129b17b171a45c5f9._comment
 delete mode 100644 doc/bugs/utf8/comment_16_2aaab9253bbc75012292c7b5a7d55696._comment
 delete mode 100644 doc/bugs/utf8/comment_1_416ad6fb5f7379732129dc5283a7e550._comment
 delete mode 100644 doc/bugs/utf8/comment_2_cd55f6bbeb145fd554f331dcff64f5e1._comment
 delete mode 100644 doc/bugs/utf8/comment_3_bb583a419d6fa4e33e5364c4468b35c6._comment
 delete mode 100644 doc/bugs/utf8/comment_4_cd8a22cfb70d9d21f0a5339ccc52ee93._comment
 delete mode 100644 doc/bugs/utf8/comment_5_14eefd4bee283802e9c462fa20b7835c._comment
 delete mode 100644 doc/bugs/utf8/comment_6_58d8b5bdb9f11e8c344e86a675a075dd._comment
 delete mode 100644 doc/bugs/utf8/comment_7_00fa9672ce55b6bfa885b8a13287ac25._comment
 delete mode 100644 doc/bugs/utf8/comment_8_a01e26fa0fafbc291020f53dbfdf6443._comment
 delete mode 100644 doc/bugs/utf8/comment_9_b7c084be01ce985be51e48503fcba468._comment
 delete mode 100644 doc/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.mdwn
 delete mode 100644 doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash.mdwn
 delete mode 100644 doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_1_ffc5f79368b8927817e0e35a7a8f057b._comment
 delete mode 100644 doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_2_1382b486d198d707db760ae119f33ad1._comment
 delete mode 100644 doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_3_3c4074a1d4d7f63f6c07a05ca9717ce8._comment
 delete mode 100644 doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_4_deb848e50f6767d8a5f4348137744ec2._comment
 delete mode 100644 doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment
 delete mode 100644 doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working.mdwn
 delete mode 100644 doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working/comment_1_ce06ba4f65f322362b23797f6190c7c3._comment
 delete mode 100644 doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex.mdwn
 delete mode 100644 doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex/comment_1_57547f9a480df2c3f7b3997b0fb7039a._comment
 delete mode 100644 doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex/comment_2_99f12da3ef01141dc7a9105fcf966793._comment
 delete mode 100644 doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android.mdwn
 delete mode 100644 doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_1_e8866dc15f8fc049229e7451addad1d5._comment
 delete mode 100644 doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_2_ee616b0251ffaace9844cfd7af896c35._comment
 delete mode 100644 doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_3_6b8bd314b647ea3a485f5faf4856f9a9._comment
 delete mode 100644 doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_4_7009b6727ba40bc9bd1b1f939e75d093._comment
 delete mode 100644 doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_5_00ddf7ade6cca758afa838be0b9588cb._comment
 delete mode 100644 doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_6_6137ef0ad01d5600dab6fccbeed9a88b._comment
 delete mode 100644 doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_7_4b79d7ea338d9f70eb80b8cc2c5a21e4._comment
 delete mode 100644 doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo.mdwn
 delete mode 100644 doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo/comment_1_63f04694610839db0c2381005b15da35._comment
 delete mode 100644 doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo/comment_2_8afe4720e301cf7ccf11ff0a23261936._comment
 delete mode 100644 doc/bugs/watch_command_on_OSX_10.7.mdwn
 delete mode 100644 doc/bugs/watcher_commits_unlocked_files.mdwn
 delete mode 100644 doc/bugs/watcher_commits_unlocked_files/comment_1_f70e1912fde0eee59e208307df06b503._comment
 delete mode 100644 doc/bugs/webapp_hang.mdwn
 delete mode 100644 doc/bugs/webapp_hang/comment_1_08aa908a64d0fe2d50438d01545c3f01._comment
 delete mode 100644 doc/bugs/webapp_hang/comment_2_2a21ac5657128a454f9deb77c4d18057._comment
 delete mode 100644 doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo.mdwn
 delete mode 100644 doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo/comment_1_1bcf0f565eacac851bd21cd428c8e0a5._comment
 delete mode 100644 doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo/comment_2_7dd2483b5b07df8f3b37a34651c05962._comment
 delete mode 100644 doc/bugs/webapp_requires_reload_for_notification_bubbles.mdwn
 delete mode 100644 doc/bugs/webapp_requires_reload_for_notification_bubbles/comment_1_b15480e5dec1ffbebb8cde1ca8d7c9d5._comment
 delete mode 100644 doc/bugs/webapp_requires_reload_for_notification_bubbles/comment_2_8dad57a852e1db804aa38f90f3bb398b._comment
 delete mode 100644 doc/bugs/webapp_shows___34__Added_x_files__34___a_bit_ugly.mdwn
 delete mode 100644 doc/bugs/webapp_takes_100__37___of_the_cpu.mdwn
 delete mode 100644 doc/bugs/webapp_takes_100__37___of_the_cpu/comment_1_6312860de9f30cbb05762cd67edc705a._comment
 delete mode 100644 doc/bugs/webapp_usability:_put_the_notices_on_the_right.mdwn
 delete mode 100644 doc/bugs/webapp_usability:_put_the_notices_on_the_right/comment_1_ec7a444e09a028b5225bd41fb83442e8._comment
 delete mode 100644 doc/bugs/webdav_special_remote_fails_on_android___40__box.com__41__.mdwn
 delete mode 100644 doc/bugs/webdav_special_remote_fails_on_android___40__box.com__41__/comment_1_f57757b4bcc4ace73bf660419d944c33._comment
 delete mode 100644 doc/bugs/weird_local_clone_confuses.mdwn
 delete mode 100644 doc/bugs/wget_tarball_over_https_complains.mdwn
 delete mode 100644 doc/bugs/wget_tarball_over_https_complains/comment_1_4227a75f2eb0de6a2422efe8d791e130._comment
 delete mode 100644 doc/bugs/wget_tarball_over_https_complains/comment_2_25fb35b2e707b174f255a1dafca8eff9._comment
 delete mode 100644 doc/bugs/windows_fails_test___34__recoverEncode__34__.mdwn
 delete mode 100644 doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_1_424b3536e21e02f192f7f2b8e833ed18._comment
 delete mode 100644 doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_2_78db183aa401e2023d7faec5f7a4a573._comment
 delete mode 100644 doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_3_ed2da19eaf0bd0864f6b28816a79bc23._comment
 delete mode 100644 doc/bugs/windows_port_-_can__39__t_directly_access_files.mdwn
 delete mode 100644 doc/bugs/windows_port_-_can__39__t_directly_access_files/comment_1_03ef9d33839173044dcc4f2b37f575d2._comment
 delete mode 100644 doc/bugs/windows_port_-_can__39__t_directly_access_files/comment_2_c65e5491c82908af46fe2c97e048d210._comment
 delete mode 100644 doc/bugs/windows_port_-_git_annex_add_hangs_when_adding_17_files_at_once_or_more_.mdwn
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_.mdwn
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_10_b4f5e2d6a0d690f6b0089fa80a3c920b._comment
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_1_c2092add1430667108a3fdc5e1c9b5f5._comment
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_2_f0ea453951daf84dbddc653ac64822b6._comment
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_3_35a8be5ecc9d1b72c38f8ddb47678160._comment
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_4_29e72997b88f91f84639587b4cede34c._comment
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_5_2de7f6532de4cbc21737ce53a89d6525._comment
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_6_80d130b5af829763be77c61a9c5ca306._comment
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_7_ec199db851952b40e8b18922da574ea4._comment
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_8_d269fcadea9d5a668e3c6d6cf019f56a._comment
 delete mode 100644 doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_9_908d1b981d56107f29d8972bf11aefc8._comment
 delete mode 100644 doc/bugs/wrong_program_path_in___126____47__.config__47__git-annex__47__program.mdwn
 delete mode 100644 doc/bugs/wrong_program_path_in___126____47__.config__47__git-annex__47__program/comment_1_44c11918d00ead38d40556aade98c0af._comment
 delete mode 100644 doc/bugs/xdg-user-dir_error.mdwn
 delete mode 100644 doc/bugs/xmpp_needs_one_account_per_distinct_repository.mdwn
 delete mode 100644 doc/bugs/xmpp_needs_one_account_per_distinct_repository/comment_1_820732c4dcb15186b4f635c50fdb0805._comment
 delete mode 100644 doc/bugs/yesod-default_is_needed_as_a_dependancy.mdwn
 delete mode 100644 doc/bugs/yesod-form_missing.mdwn
 delete mode 100644 doc/todo/Allow_syncing_only_selected_branches.mdwn
 delete mode 100644 doc/todo/Allow_syncing_only_selected_branches/comment_1_bb687b1a50d8a926abd16ada639140e1._comment
 delete mode 100644 doc/todo/Allow_syncing_only_selected_branches/comment_2_46d27fe74b4adac2e740fa555f549459._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM.mdwn
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_10_e351084d9a83db3fd6d9d983227a6410._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_11_cc67a584f5c460a6fb63cf099c20e573._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_12_94023593d294b9cf69090fcfd6ca0e5a._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_13_314255fd503d125b5aeae2f62acfd592._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_15_9525cd0d75ff4c15182d10a855774b69._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_15_c12f525ef4cbe42cdf20fec0d53c8d86._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_1_4059016fa8da6af7a3eba8966821e8eb._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_2_8900c2985ab68b3b566c9f5d326471d6._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_3_f2b77368473d42b7f21e9d51d6415b58._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_4_a55fea734044c270ceb10adf9c8d9a76._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_5_59865ada057c640ac29855c65cf45dd9._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_6_6d860b1ad8816077b5fa596a71b12d5c._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_7_19ef2d293ba3bc7ece443d7278371c3f._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_8_609b7ad87dfbba49ec1f8c6fc2739ccd._comment
 delete mode 100644 doc/todo/Build_for_Synology_DSM/comment_9_d94a73b9a07c5cadf191005f817fd59a._comment
 delete mode 100644 doc/todo/Check_if_an_upgrade_is_available_in_the_webapp.mdwn
 delete mode 100644 doc/todo/Check_if_an_upgrade_is_available_in_the_webapp/comment_1_c904182f6bff8b1a42070bbc038eb34e._comment
 delete mode 100644 doc/todo/Check_if_an_upgrade_is_available_in_the_webapp/comment_2_ebe7a75ca291e7f749bfe9f46d10909d._comment
 delete mode 100644 doc/todo/Enhancement:_git_annex_whereis_KEY.mdwn
 delete mode 100644 doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment
 delete mode 100644 doc/todo/Enhancement:_git_annex_whereis_KEY/comment_2_4189d9e91208a59381100613e254e731._comment
 delete mode 100644 doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp.mdwn
 delete mode 100644 doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp/comment_1_0d5c90eb0e8fe61b82a19c5fea343613._comment
 delete mode 100644 doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp/comment_2_196552002d70390e8b52b4af61dca903._comment
 delete mode 100644 doc/todo/Limit_file_revision_history.mdwn
 delete mode 100644 doc/todo/Option_for_browser_to_launch_webapp_with.mdwn
 delete mode 100644 doc/todo/Please_abort_build_if___34__make_test__34___fails.mdwn
 delete mode 100644 doc/todo/Please_add_support_for_monad-control_0.3.x.mdwn
 delete mode 100644 doc/todo/Provide_a___34__git_annex_satisfy__95__num__95__copies__34___command.mdwn
 delete mode 100644 doc/todo/S3.mdwn
 delete mode 100644 doc/todo/Sync_repo_names__63__.mdwn
 delete mode 100644 doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn
 delete mode 100644 doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__/comment_1_a93805a8088402c6dc32d2b9785fcc7d._comment
 delete mode 100644 doc/todo/Wishlist:_Import_youtube_playlists.mdwn
 delete mode 100644 doc/todo/Wishlist:_Import_youtube_playlists/comment_1_4235cbbb0c6f9d83524c970c4588cb2e._comment
 delete mode 100644 doc/todo/__96__git_annex_import_--lazy__96___--_Delete_everything_that__39__s_in_the_source_directory_and_also_in_the_target_annex.mdwn
 delete mode 100644 doc/todo/__96__git_annex_import_--lazy__96___--_Delete_everything_that__39__s_in_the_source_directory_and_also_in_the_target_annex/comment_1_0cc16eb17151309113cec6d1cccf203d._comment
 delete mode 100644 doc/todo/__96__git_annex_status__47__version__96___should_print_the_local_OS.mdwn
 delete mode 100644 doc/todo/__96__git_annex_sync_--auto__96___or___96__git_annex_auto__96___--_synchronize_symlinks__44___tracking_info__44___and_actual_data.mdwn
 delete mode 100644 doc/todo/add_--exclude_option_to_git_annex_find.mdwn
 delete mode 100644 doc/todo/add_-all_option.mdwn
 delete mode 100644 doc/todo/add_a_git_backend.mdwn
 delete mode 100644 doc/todo/add_an_icon_for_the_.desktop_file.mdwn
 delete mode 100644 doc/todo/add_metadata_to_annexed_files.mdwn
 delete mode 100644 doc/todo/add_metadata_to_annexed_files/comment_1_38af9b352020194e9ace34d7dde188cf._comment
 delete mode 100644 doc/todo/assistant_git_sync_laddering.mdwn
 delete mode 100644 doc/todo/assistant_smarter_archive_directory_handling.mdwn
 delete mode 100644 doc/todo/assistant_threaded_runtime.mdwn
 delete mode 100644 doc/todo/auto_remotes.mdwn
 delete mode 100644 doc/todo/auto_remotes/discussion.mdwn
 delete mode 100644 doc/todo/automatic_bookkeeping_watch_command.mdwn
 delete mode 100644 doc/todo/avoid_unnecessary_union_merges.mdwn
 delete mode 100644 doc/todo/backendSHA1.mdwn
 delete mode 100644 doc/todo/branching.mdwn
 delete mode 100644 doc/todo/checkout.mdwn
 delete mode 100644 doc/todo/direct_mode_guard.mdwn
 delete mode 100644 doc/todo/direct_mode_guard/comment_1_431b6e1577bbd30b07dce9002a8fe1a2._comment
 delete mode 100644 doc/todo/direct_mode_guard/comment_2_85bdb9dc601b87bd7c77150d7b0a5cde._comment
 delete mode 100644 doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__.mdwn
 delete mode 100644 doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_1_5ed9a2336b432b842c1805add6d96509._comment
 delete mode 100644 doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_2_e6ba58c5c31ba23a4575f1189689946f._comment
 delete mode 100644 doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_3_e53cbc5765819de2d3c742e6cd4d77cd._comment
 delete mode 100644 doc/todo/exclude_files_on_a_given_remote.mdwn
 delete mode 100644 doc/todo/faster_gnupg_cipher.mdwn
 delete mode 100644 doc/todo/faster_gnupg_cipher/comment_1_8f61f7c724a8224e61c015be68f43db7._comment
 delete mode 100644 doc/todo/faster_gnupg_cipher/comment_2_36e1f227a320527653500b445f7c001c._comment
 delete mode 100644 doc/todo/faster_gnupg_cipher/comment_3_bd0c975494333dfe558de048d888ace8._comment
 delete mode 100644 doc/todo/faster_rsync_remotes.mdwn
 delete mode 100644 doc/todo/faster_rsync_remotes/comment_1_0bc3ee0ae563357675eeccf42461e59a._comment
 delete mode 100644 doc/todo/faster_rsync_remotes/comment_2_ccf6f75450c89ca498c8130054f8d32d._comment
 delete mode 100644 doc/todo/faster_rsync_remotes/comment_3_2f6a9d23cb8351fbf0f60ed93752e76e._comment
 delete mode 100644 doc/todo/faster_rsync_remotes/comment_4_3a2f45defebae3dde336ee5f40c26d7e._comment
 delete mode 100644 doc/todo/file_copy_progress_bar.mdwn
 delete mode 100644 doc/todo/fsck.mdwn
 delete mode 100644 doc/todo/fsck_special_remotes.mdwn
 delete mode 100644 doc/todo/git-annex-shell.mdwn
 delete mode 100644 doc/todo/git-annex_unused_eats_memory.mdwn
 delete mode 100644 doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn
 delete mode 100644 doc/todo/gitolite_and_gitosis_support.mdwn
 delete mode 100644 doc/todo/gitrm.mdwn
 delete mode 100644 doc/todo/http_git_annex_404_retry.mdwn
 delete mode 100644 doc/todo/http_headers.mdwn
 delete mode 100644 doc/todo/immutable_annexed_files.mdwn
 delete mode 100644 doc/todo/incremental_fsck.mdwn
 delete mode 100644 doc/todo/incremental_fsck/comment_1_609b21141dd5686b2c0eaef2b8d63229._comment
 delete mode 100644 doc/todo/link_file_to_remote_repo_feature.mdwn
 delete mode 100644 doc/todo/make___34__itemdate__34___valid_importfeed_template_option.mdwn
 delete mode 100644 doc/todo/make___34__itemdate__34___valid_importfeed_template_option/comment_1_9fa523d1eabb6e029a91413770e9af72._comment
 delete mode 100644 doc/todo/make___34__itemdate__34___valid_importfeed_template_option/comment_2_9090bb66713f48fbdd1e2a3f1292b7ba._comment
 delete mode 100644 doc/todo/makefile:_respect___36__PREFIX.mdwn
 delete mode 100644 doc/todo/mdwn2man:_make_backticks_bold.mdwn
 delete mode 100644 doc/todo/network_remotes.mdwn
 delete mode 100644 doc/todo/nicer_whereis_output.mdwn
 delete mode 100644 doc/todo/object_dir_reorg_v2.mdwn
 delete mode 100644 doc/todo/object_dir_reorg_v2/comment_1_ba03333dc76ff49eccaba375e68cb525._comment
 delete mode 100644 doc/todo/object_dir_reorg_v2/comment_2_81276ac309959dc741bc90101c213ab7._comment
 delete mode 100644 doc/todo/object_dir_reorg_v2/comment_3_79bdf9c51dec9f52372ce95b53233bb2._comment
 delete mode 100644 doc/todo/object_dir_reorg_v2/comment_4_93aada9b1680fed56cc6f0f7c3aca5e5._comment
 delete mode 100644 doc/todo/object_dir_reorg_v2/comment_5_821c382987f105da72a50e0a5ce61fdc._comment
 delete mode 100644 doc/todo/object_dir_reorg_v2/comment_6_8834c3a3f1258c4349d23aff8549bf35._comment
 delete mode 100644 doc/todo/object_dir_reorg_v2/comment_7_42501404c82ca07147e2cce0cff59474._comment
 delete mode 100644 doc/todo/optinally_transfer_file_unencryptedly.mdwn
 delete mode 100644 doc/todo/optinally_transfer_file_unencryptedly/comment_1_4be47e7ac85d0f4e7029a96b615545a7._comment
 delete mode 100644 doc/todo/preferred_content_numcopies_check.mdwn
 delete mode 100644 doc/todo/pushpull.mdwn
 delete mode 100644 doc/todo/quvi_0.9_support.mdwn
 delete mode 100644 doc/todo/rsync.mdwn
 delete mode 100644 doc/todo/separate_rsync_bwlimit_options_for_upload_and_download.mdwn
 delete mode 100644 doc/todo/special_remote_for_amazon_glacier.mdwn
 delete mode 100644 doc/todo/special_remote_for_amazon_glacier/comment_1_68f129441eefcbfebf7a9db680f52759._comment
 delete mode 100644 doc/todo/special_remote_for_amazon_glacier/comment_2_c5eeaf8ceee414fa0379831ca52e290c._comment
 delete mode 100644 doc/todo/speed_up_fsck.mdwn
 delete mode 100644 doc/todo/support-non-utf8-locales.mdwn
 delete mode 100644 doc/todo/support_for_lossy_remotes.mdwn
 delete mode 100644 doc/todo/support_for_lossy_remotes/comment_1_f5cd9f9deab13ab2d2290ad763906dd3._comment
 delete mode 100644 doc/todo/support_for_writing_external_special_remotes.mdwn
 delete mode 100644 doc/todo/support_fsck_in_bare_repos.mdwn
 delete mode 100644 doc/todo/symlink_farming_commit_hook.mdwn
 delete mode 100644 doc/todo/symlink_git-annex_binaries_to___126____47__.local__47__bin_for_prebuilt_package.mdwn
 delete mode 100644 doc/todo/untracked_remotes.mdwn
 delete mode 100644 doc/todo/untracked_remotes/comment_1_ccc743554cf9270e1db5275273b28265._comment
 delete mode 100644 doc/todo/untracked_remotes/comment_2_48cc5d0e2282fa53625e0037a035fee3._comment
 delete mode 100644 doc/todo/untracked_remotes/comment_3_0d07c5bc8d42f35351c11411eaca88df._comment
 delete mode 100644 doc/todo/untracked_remotes/comment_4_75ae13c2135a2951b2af548139cb25cd._comment
 delete mode 100644 doc/todo/use_cp_reflink.mdwn
 delete mode 100644 doc/todo/using_url_backend.mdwn
 delete mode 100644 doc/todo/whishlist:_git_annex_drop_--dry-run.mdwn
 delete mode 100644 doc/todo/whishlist:_git_annex_drop_--dry-run/comment_1_20ecfa8ffa52c238d21b904076ac69a2._comment
 delete mode 100644 doc/todo/whishlist:_git_annex_drop_--dry-run/comment_2_d19bc268c9467d24baa8d8f77a6e5e09._comment
 delete mode 100644 doc/todo/whislist:_allow_setting_annex-ignore_from_the_webapp.mdwn
 delete mode 100644 doc/todo/whislist:_allow_setting_annex-ignore_from_the_webapp/comment_1_b3b5c12f89a0a6a91d681c67e2217199._comment
 delete mode 100644 doc/todo/wishlist:_Add_to_Android_version_to_Google_Play.mdwn
 delete mode 100644 doc/todo/wishlist:_An_--all_option_for_dropunused.mdwn
 delete mode 100644 doc/todo/wishlist:_An_--all_option_for_dropunused/comment_1_d8726d108b3b40116b4ec3c9935f2dff._comment
 delete mode 100644 doc/todo/wishlist:_An_--all_option_for_dropunused/comment_2_578248f7686ba2d80d7dc8b17c0cdf52._comment
 delete mode 100644 doc/todo/wishlist:_An_option_like_--git-dir.mdwn
 delete mode 100644 doc/todo/wishlist:_An_option_like_--git-dir/comment_1_5d877d90b8bdf21d4b8649744d229efd._comment
 delete mode 100644 doc/todo/wishlist:_An_option_like_--git-dir/comment_2_462264821cbc48a433330cbf7ec6044d._comment
 delete mode 100644 doc/todo/wishlist:_An_option_like_--git-dir/comment_3_0c3709b07a0a1091ceeee73b69e0f7ac._comment
 delete mode 100644 doc/todo/wishlist:_GnuPG_options.mdwn
 delete mode 100644 doc/todo/wishlist:_GnuPG_options/comment_1_6662e8a71ce20acc62147ef41ecffa50._comment
 delete mode 100644 doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size.mdwn
 delete mode 100644 doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_1_019a2457e07377510feaa089a93bd76c._comment
 delete mode 100644 doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_3_29a154699339bf040af0ee8aa24034f1._comment
 delete mode 100644 doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_3_8f7e1c4a5c714cbd719ee170354d79fa._comment
 delete mode 100644 doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_4_c7335f757e5546aa841cab38fffe7605._comment
 delete mode 100644 doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_5_d2a845354f23d07880612740cf99ddd4._comment
 delete mode 100644 doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command.mdwn
 delete mode 100644 doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command/comment_1_3f9c0d08932c2ede61c802a91261a1f7._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates.mdwn
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_10_d78d79fb2f3713aa69f45d2691cf8dfe._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_11_4316d9d74312112dc4c823077af7febe._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_12_ed6d07f16a11c6eee7e3d5005e8e6fa3._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_1_fd213310ee548d8726791d2b02237fde._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_2_4394bde1c6fd44acae649baffe802775._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_3_076cb22057583957d5179d8ba9004605._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_4_f120d1e83c1a447f2ecce302fc69cf74._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_5_5c30294b3c59fdebb1eef0ae5da4cd4f._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_6_f24541ada1c86d755acba7e9fa7cff24._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_7_c39f1bb7c61a89b238c61bee1c049767._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_8_221ed2e53420278072a6d879c6f251d1._comment
 delete mode 100644 doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_9_aecfa896c97b9448f235bce18a40621d._comment
 delete mode 100644 doc/todo/wishlist:_Tell_git_annex___40__assistant__41___which_files___40__not__41___to_annex_via_.gitattributes.mdwn
 delete mode 100644 doc/todo/wishlist:___34__git_annex_add__34___multiple_processes.mdwn
 delete mode 100644 doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_1_85b14478411a33e6186a64bd41f0910d._comment
 delete mode 100644 doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_2_82e857f463cfdf73c70f6c0a9f9a31d6._comment
 delete mode 100644 doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_3_8af85eba7472d9025c6fae4f03e3ad75._comment
 delete mode 100644 doc/todo/wishlist:___96__git_annex_fsck_--checksums__96___--_verify_checksums_but_disregard_annex.numcopies.mdwn
 delete mode 100644 doc/todo/wishlist:___96__git_annex_fsck_--checksums__96___--_verify_checksums_but_disregard_annex.numcopies/comment_1_6bcf067e4860bdfeb1d7b9fd1702a43a._comment
 delete mode 100644 doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn
 delete mode 100644 doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_1_b9fd1bfaf9a3d238fdb7bc9c2d75fe5f._comment
 delete mode 100644 doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_2_56f6972413c6f0d9f414245b6f4d27b9._comment
 delete mode 100644 doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_3_2c094bef802a2182de4fcd0def1ad29b._comment
 delete mode 100644 doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_4_14915c43001f7f72c9fe5119a104ef5c._comment
 delete mode 100644 doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__.mdwn
 delete mode 100644 doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__/comment_1_f46b0c9b49607e9f4f7a27f5a331ce83._comment
 delete mode 100644 doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__/comment_2_1b34e1dd72011c65e881dec2543a0373._comment
 delete mode 100644 doc/todo/wishlist:_addurl_https:.mdwn
 delete mode 100644 doc/todo/wishlist:_addurl_https:/comment_1_4e8f5e1fc52c3000eb2a1dad0624906e._comment
 delete mode 100644 doc/todo/wishlist:_allow_configuration_of_downloader_for_addurl.mdwn
 delete mode 100644 doc/todo/wishlist:_allow_the_same_remote_to_be_accissable_via_different_methods.mdwn
 delete mode 100644 doc/todo/wishlist:_allow_the_same_remote_to_be_accissable_via_different_methods/comment_1_abb6263f3807160222bba1122475c89c._comment
 delete mode 100644 doc/todo/wishlist:_allow_users_to_provide_UUID_when_running___96__git_annex_init__96__.mdwn
 delete mode 100644 doc/todo/wishlist:_assistant_autostart_port_and_secret_configuration.mdwn
 delete mode 100644 doc/todo/wishlist:_assistant_autostart_port_and_secret_configuration/comment_1_be53b8456eed7eadad5d4b8465c8a42b._comment
 delete mode 100644 doc/todo/wishlist:_command_options_changes.mdwn
 delete mode 100644 doc/todo/wishlist:_command_options_changes/comment_1_bfba72a696789bf21b2435dea15f967a._comment
 delete mode 100644 doc/todo/wishlist:_command_options_changes/comment_2_f6a637c78c989382e3c22d41b7fb4cc2._comment
 delete mode 100644 doc/todo/wishlist:_command_options_changes/comment_3_bf1114533d2895804e531e76eb6b8095._comment
 delete mode 100644 doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn
 delete mode 100644 doc/todo/wishlist:_define_remotes_that_must_have_all_files/comment_1_cceccc1a1730ac688d712b81a44e31c3._comment
 delete mode 100644 doc/todo/wishlist:_define_remotes_that_must_have_all_files/comment_2_eec848fcf3979c03cbff2b7407c75a7a._comment
 delete mode 100644 doc/todo/wishlist:_detection_of_merge_conflicts.mdwn
 delete mode 100644 doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied.mdwn
 delete mode 100644 doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied/comment_1_d2665e7347689b520d37561cfddf0aa8._comment
 delete mode 100644 doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied/comment_2_db153571a32fb072453ed583e3e9ccf4._comment
 delete mode 100644 doc/todo/wishlist:_dropping_git-annex_history.mdwn
 delete mode 100644 doc/todo/wishlist:_dropping_git-annex_history/comment_1_a4bee2e26b22a9bdaadc05b7227769ef._comment
 delete mode 100644 doc/todo/wishlist:_dropping_git-annex_history/comment_2_f6d750bfe0c9d8a2aa6bc218ca5c49cc._comment
 delete mode 100644 doc/todo/wishlist:_git-annex_replicate.mdwn
 delete mode 100644 doc/todo/wishlist:_git-annex_replicate/comment_1_9926132ec6052760cdf28518a24e2358._comment
 delete mode 100644 doc/todo/wishlist:_git-annex_replicate/comment_2_c43932f4194aba8fb2470b18e0817599._comment
 delete mode 100644 doc/todo/wishlist:_git-annex_replicate/comment_3_c13f4f9c3d5884fc6255fd04feadc2b1._comment
 delete mode 100644 doc/todo/wishlist:_git-annex_replicate/comment_4_63f24abf086d644dced8b01e1a9948c9._comment
 delete mode 100644 doc/todo/wishlist:_git_annex_group_remote_return_the_group.mdwn
 delete mode 100644 doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults.mdwn
 delete mode 100644 doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_1_d5413c8acce308505e4e2bec82fb1261._comment
 delete mode 100644 doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_2_0aa227c85d34dfff4e94febca44abea8._comment
 delete mode 100644 doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_3_2082f4d708a584a1403cc1d4d005fb56._comment
 delete mode 100644 doc/todo/wishlist:_git_annex_status.mdwn
 delete mode 100644 doc/todo/wishlist:_git_annex_status/comment_1_994bfd12c5d82e08040d6116915c5090._comment
 delete mode 100644 doc/todo/wishlist:_git_annex_status/comment_2_c2b0ce025805b774dc77ce264a222824._comment
 delete mode 100644 doc/todo/wishlist:_git_annex_status/comment_3_d1fd70c67243971c96d59e1ffb7ef6e7._comment
 delete mode 100644 doc/todo/wishlist:_git_annex_status/comment_4_9aeeb83d202dc8fb33ff364b0705ad94._comment
 delete mode 100644 doc/todo/wishlist:_git_backend_for_git-annex.mdwn
 delete mode 100644 doc/todo/wishlist:_git_backend_for_git-annex/comment_1_04319051fedc583e6c326bb21fcce5a5._comment
 delete mode 100644 doc/todo/wishlist:_git_backend_for_git-annex/comment_2_7f529f19a47e10b571f65ab382e97fd5._comment
 delete mode 100644 doc/todo/wishlist:_git_backend_for_git-annex/comment_3_a077bbad3e4b07cce019eb55a45330e7._comment
 delete mode 100644 doc/todo/wishlist:_git_backend_for_git-annex/comment_4_ecca429e12d734b509c671166a676c9d._comment
 delete mode 100644 doc/todo/wishlist:_git_backend_for_git-annex/comment_5_3459f0b41d818c23c8fb33edb89df634._comment
 delete mode 100644 doc/todo/wishlist:_incremental_unannex___40__currently_requires_twice_the_size_of_repo_to_complete__41__.mdwn
 delete mode 100644 doc/todo/wishlist:_incremental_unannex___40__currently_requires_twice_the_size_of_repo_to_complete__41__/comment_1_067b29fc47d26b9da0766f9810684ae8._comment
 delete mode 100644 doc/todo/wishlist:_metadata_metadata_view.mdwn
 delete mode 100644 doc/todo/wishlist:_metadata_metadata_view/comment_1_79dbf48cf2e0d649f32bd077f0c9bc5a._comment
 delete mode 100644 doc/todo/wishlist:_metadata_metadata_view/comment_2_5763d0e403c476ac692c1cd50630f824._comment
 delete mode 100644 doc/todo/wishlist:_metadata_metadata_view/comment_3_797e6578c60d8e2ed1f61a8d6403575f._comment
 delete mode 100644 doc/todo/wishlist:_metadata_metadata_view/comment_4_d271fe711b3fe5ffeb52f1caf44622b3._comment
 delete mode 100644 doc/todo/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn
 delete mode 100644 doc/todo/wishlist:_option_to_disable_url_checking_with_addurl.mdwn
 delete mode 100644 doc/todo/wishlist:_option_to_disable_url_checking_with_addurl/comment_1_868a380faa1e55faa3c2d314e3258e86._comment
 delete mode 100644 doc/todo/wishlist:_push_to_cia.vc_from_the_website__39__s_repo__44___not_your_personal_one.mdwn
 delete mode 100644 doc/todo/wishlist:_push_to_cia.vc_from_the_website__39__s_repo__44___not_your_personal_one/comment_1_3480b0ec629ef29a151408d869186bf8._comment
 delete mode 100644 doc/todo/wishlist:_query_things_like_description__44___trust_level.mdwn
 delete mode 100644 doc/todo/wishlist:_query_things_like_description__44___trust_level/comment_1_14311384788312b96e550749ab7de9ea._comment
 delete mode 100644 doc/todo/wishlist:_query_things_like_description__44___trust_level/comment_2_342d1ac07573c7ef4e27f003a692e261._comment
 delete mode 100644 doc/todo/wishlist:_simple_url_for_webapp.mdwn
 delete mode 100644 doc/todo/wishlist:_simple_url_for_webapp/comment_1_552aad504fbb68d1f85abfde8c535e69._comment
 delete mode 100644 doc/todo/wishlist:_simpler_gpg_usage.mdwn
 delete mode 100644 doc/todo/wishlist:_simpler_gpg_usage/comment_1_6923fa6ebc0bbe7d93edb1d01d7c46c5._comment
 delete mode 100644 doc/todo/wishlist:_simpler_gpg_usage/comment_2_6fc874b6c391df242bd2592c4a65eae8._comment
 delete mode 100644 doc/todo/wishlist:_simpler_gpg_usage/comment_3_012f340c8c572fe598fc860c1046dabd._comment
 delete mode 100644 doc/todo/wishlist:_simpler_gpg_usage/comment_4_e0c2a13217b795964f3b630c001661ef._comment
 delete mode 100644 doc/todo/wishlist:_simpler_gpg_usage/comment_5_9668b58eb71901e1db8da7db38e068ca._comment
 delete mode 100644 doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote.mdwn
 delete mode 100644 doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_1_1a383c30df4fb1767f13d8c670b0c0b5._comment
 delete mode 100644 doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_2_81f7f893ac36c145b31f02db6a682a17._comment
 delete mode 100644 doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_3_a7e3cd68c5e5f05139151a58f358df95._comment
 delete mode 100644 doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_4_a57947ed257b28bbe995a68bfeb5eeaa._comment
 delete mode 100644 doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_5_a0612ae05dbda7f7935be648b42b30fc._comment
 delete mode 100644 doc/todo/wishlist:_special_remote_for_sftp_or_rsync.mdwn
 delete mode 100644 doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_1_6f07d9cc92cf8b4927b3a7d1820c9140._comment
 delete mode 100644 doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_2_84e4414c88ae91c048564a2cdc2d3250._comment
 delete mode 100644 doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_3_79de7ac44e3c0f0f5691a56d3fb88897._comment
 delete mode 100644 doc/todo/wishlist:_special_remote_mega.co.nz.mdwn
 delete mode 100644 doc/todo/wishlist:_special_remote_mega.co.nz/comment_2_6ca08ef808d4336fc42d0f279d6627b5._comment
 delete mode 100644 doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y.mdwn
 delete mode 100644 doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y/comment_1_cf8e0f16b723516374c95a93e4da42fc._comment
 delete mode 100644 doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y/comment_2_d35359c9dd4dd4365d9a7caf695ff833._comment
 delete mode 100644 doc/todo/wishlist:_support_drop__44___find_on_special_remotes.mdwn
 delete mode 100644 doc/todo/wishlist:_support_drop__44___find_on_special_remotes/comment_1_f11ed642a83d965076778a162f701e84._comment
 delete mode 100644 doc/todo/wishlist:_support_for_more_ssh_urls_.mdwn
 delete mode 100644 doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository.mdwn
 delete mode 100644 doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_1_d48a98bad77400bd8384300e324d999f._comment
 delete mode 100644 doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_2_1a1d15531c74eb0cc09f81dc09d95d39._comment
 delete mode 100644 doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_3_66ceb7c793a2dbbd755b9595a2199aca._comment
 delete mode 100644 doc/todo/wishlist:_vicfg_possible_repo_group_names.mdwn

diff --git a/doc/bugs/127.0.0.1_references_on_remote_assistant_access.mdwn b/doc/bugs/127.0.0.1_references_on_remote_assistant_access.mdwn
deleted file mode 100644
index bf62df8d5..000000000
--- a/doc/bugs/127.0.0.1_references_on_remote_assistant_access.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-### Please describe the problem.
-When I use git-annex webapp with a remote IP of a headless computer, I am sometimes redirected to a 127.0.0.1 address (with a different port as well)
-
-### What steps will reproduce the problem?
-1. Install git-annex as usual. 
-2. Open git-annex assistant from a headless machine and access the webapp with the --listen option. (e.g. git annex webapp --listen=xxx.yyy.zzz.www)
-3. Create your first local repository. Then create a second local repository.
-4. When assistant asks you if you want to merge these 2 repositories, try to select the second option (to keep them separated).
-5. You are redirected from your remote IP to 127.0.0.1 to a new port number.
-
-(I also encountered the same error at another menu or function, but I don't remember where. Sorry.) 
-
-### What version of git-annex are you using? On what operating system?
-4.20130815
-Ubuntu 13.10 64-bit (kernel 3.11.0-13-generic x86_64)
-
-### Please provide any additional information below.
-Please ask me for any additional information that may be useful.
-
-> [[dup]] of [[Hangs_on_creating_repository_when_using_--listen]]; [[done]] --[[Joey]]
diff --git a/doc/bugs/3.20121112:_build_error_in_assistant.mdwn b/doc/bugs/3.20121112:_build_error_in_assistant.mdwn
deleted file mode 100644
index de11dfbf7..000000000
--- a/doc/bugs/3.20121112:_build_error_in_assistant.mdwn
+++ /dev/null
@@ -1,432 +0,0 @@
-Git-annex stopped compiling with GHC 7.4.2 after updating Yesod and friends to the respective latest version. The complete build log is attached below. I hope this helps. Further build logs are available at <http://hydra.nixos.org/job/nixpkgs/trunk/gitAndTools.gitAnnex>, too.
-
-    building
-    make flags:  PREFIX=/nix/store/9az61h33v1j6fkdmwdfy7gi0rhspsb9k-git-annex-3.20121112
-    building Build/SysConfig.hs
-    ghc -O2 -Wall -outputdir tmp -IUtility  -DWITH_ASSISTANT -DWITH_S3 -DWITH_WEBAPP -DWITH_PAIRING -DWITH_XMPP -DWITH_DNS -DWITH_INOTIFY -DWITH_DBUS -threaded --make configure
-    [1 of 7] Compiling Utility.Exception ( Utility/Exception.hs, tmp/Utility/Exception.o )
-    [2 of 7] Compiling Utility.Misc     ( Utility/Misc.hs, tmp/Utility/Misc.o )
-    [3 of 7] Compiling Utility.Process  ( Utility/Process.hs, tmp/Utility/Process.o )
-    [4 of 7] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, tmp/Utility/SafeCommand.o )
-    [5 of 7] Compiling Build.TestConfig ( Build/TestConfig.hs, tmp/Build/TestConfig.o )
-    [6 of 7] Compiling Build.Configure  ( Build/Configure.hs, tmp/Build/Configure.o )
-    [7 of 7] Compiling Main             ( configure.hs, tmp/Main.o )
-    Linking configure ...
-    ./configure
-      checking version... 3.20121112
-      checking git... yes
-      checking git version... 1.8.0
-      checking cp -a... yes
-      checking cp -p... yes
-      checking cp --reflink=auto... yes
-      checking uuid generator... uuidgen
-      checking xargs -0... yes
-      checking rsync... yes
-      checking curl... yes
-      checking wget... no
-      checking bup... no
-      checking gpg... no
-      checking lsof... no
-      checking ssh connection caching... yes
-      checking sha1... sha1sum
-      checking sha256... sha256sum
-      checking sha512... sha512sum
-      checking sha224... sha224sum
-      checking sha384... sha384sum
-    building Utility/Touch.hs
-    hsc2hs Utility/Touch.hsc
-    building Utility/Mounts.hs
-    hsc2hs Utility/Mounts.hsc
-    building Utility/libdiskfree.o
-    cc -Wall   -c -o Utility/libdiskfree.o Utility/libdiskfree.c
-    building Utility/libmounts.o
-    cc -Wall   -c -o Utility/libmounts.o Utility/libmounts.c
-    building git-annex
-    install -d tmp
-    ghc -O2 -Wall -outputdir tmp -IUtility  -DWITH_ASSISTANT -DWITH_S3 -DWITH_WEBAPP -DWITH_PAIRING -DWITH_XMPP -DWITH_DNS -DWITH_INOTIFY -DWITH_DBUS -threaded --make git-annex -o tmp/git-annex Utility/libdiskfree.o Utility/libmounts.o
-    [  1 of 279] Compiling Utility.Dot      ( Utility/Dot.hs, tmp/Utility/Dot.o )
-    [  2 of 279] Compiling Utility.ThreadLock ( Utility/ThreadLock.hs, tmp/Utility/ThreadLock.o )
-    [  3 of 279] Compiling Utility.Mounts   ( Utility/Mounts.hs, tmp/Utility/Mounts.o )
-    [  4 of 279] Compiling Utility.Yesod    ( Utility/Yesod.hs, tmp/Utility/Yesod.o )
-    [  5 of 279] Compiling Utility.Tense    ( Utility/Tense.hs, tmp/Utility/Tense.o )
-    [  6 of 279] Compiling Utility.Verifiable ( Utility/Verifiable.hs, tmp/Utility/Verifiable.o )
-    [  7 of 279] Compiling Assistant.Types.TransferSlots ( Assistant/Types/TransferSlots.hs, tmp/Assistant/Types/TransferSlots.o )
-    [  8 of 279] Compiling Types.StandardGroups ( Types/StandardGroups.hs, tmp/Types/StandardGroups.o )
-    [  9 of 279] Compiling Utility.Percentage ( Utility/Percentage.hs, tmp/Utility/Percentage.o )
-    [ 10 of 279] Compiling Utility.Base64   ( Utility/Base64.hs, tmp/Utility/Base64.o )
-    [ 11 of 279] Compiling Utility.DataUnits ( Utility/DataUnits.hs, tmp/Utility/DataUnits.o )
-    [ 12 of 279] Compiling Utility.JSONStream ( Utility/JSONStream.hs, tmp/Utility/JSONStream.o )
-    [ 13 of 279] Compiling Messages.JSON    ( Messages/JSON.hs, tmp/Messages/JSON.o )
-    [ 14 of 279] Compiling Build.SysConfig  ( Build/SysConfig.hs, tmp/Build/SysConfig.o )
-    [ 15 of 279] Compiling Types.KeySource  ( Types/KeySource.hs, tmp/Types/KeySource.o )
-    [ 16 of 279] Compiling Utility.State    ( Utility/State.hs, tmp/Utility/State.o )
-    [ 17 of 279] Compiling Types.UUID       ( Types/UUID.hs, tmp/Types/UUID.o )
-    [ 18 of 279] Compiling Types.Messages   ( Types/Messages.hs, tmp/Types/Messages.o )
-    [ 19 of 279] Compiling Types.Group      ( Types/Group.hs, tmp/Types/Group.o )
-    [ 20 of 279] Compiling Types.TrustLevel ( Types/TrustLevel.hs, tmp/Types/TrustLevel.o )
-    [ 21 of 279] Compiling Types.BranchState ( Types/BranchState.hs, tmp/Types/BranchState.o )
-    [ 22 of 279] Compiling Utility.PartialPrelude ( Utility/PartialPrelude.hs, tmp/Utility/PartialPrelude.o )
-    [ 23 of 279] Compiling Utility.HumanTime ( Utility/HumanTime.hs, tmp/Utility/HumanTime.o )
-    [ 24 of 279] Compiling Utility.Format   ( Utility/Format.hs, tmp/Utility/Format.o )
-    [ 25 of 279] Compiling Utility.FileSystemEncoding ( Utility/FileSystemEncoding.hs, tmp/Utility/FileSystemEncoding.o )
-    [ 26 of 279] Compiling Utility.Touch    ( Utility/Touch.hs, tmp/Utility/Touch.o )
-    [ 27 of 279] Compiling Utility.Applicative ( Utility/Applicative.hs, tmp/Utility/Applicative.o )
-    [ 28 of 279] Compiling Utility.Monad    ( Utility/Monad.hs, tmp/Utility/Monad.o )
-    [ 29 of 279] Compiling Utility.Exception ( Utility/Exception.hs, tmp/Utility/Exception.o )
-    [ 30 of 279] Compiling Utility.DBus     ( Utility/DBus.hs, tmp/Utility/DBus.o )
-    [ 31 of 279] Compiling Utility.Misc     ( Utility/Misc.hs, tmp/Utility/Misc.o )
-    [ 32 of 279] Compiling Utility.Process  ( Utility/Process.hs, tmp/Utility/Process.o )
-    [ 33 of 279] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, tmp/Utility/SafeCommand.o )
-    [ 34 of 279] Compiling Utility.Network  ( Utility/Network.hs, tmp/Utility/Network.o )
-    [ 35 of 279] Compiling Utility.SRV      ( Utility/SRV.hs, tmp/Utility/SRV.o )
-
-    Utility/SRV.hs:88:1: Warning: Defined but not used: `lookupSRVHost'
-
-    Utility/SRV.hs:94:1: Warning: Defined but not used: `parseSrvHost'
-    [ 36 of 279] Compiling Git.Types        ( Git/Types.hs, tmp/Git/Types.o )
-    [ 37 of 279] Compiling Utility.UserInfo ( Utility/UserInfo.hs, tmp/Utility/UserInfo.o )
-    [ 38 of 279] Compiling Utility.Path     ( Utility/Path.hs, tmp/Utility/Path.o )
-    [ 39 of 279] Compiling Utility.TempFile ( Utility/TempFile.hs, tmp/Utility/TempFile.o )
-    [ 40 of 279] Compiling Utility.Directory ( Utility/Directory.hs, tmp/Utility/Directory.o )
-    [ 41 of 279] Compiling Utility.FreeDesktop ( Utility/FreeDesktop.hs, tmp/Utility/FreeDesktop.o )
-    [ 42 of 279] Compiling Assistant.Install.AutoStart ( Assistant/Install/AutoStart.hs, tmp/Assistant/Install/AutoStart.o )
-    [ 43 of 279] Compiling Common           ( Common.hs, tmp/Common.o )
-    [ 44 of 279] Compiling Utility.FileMode ( Utility/FileMode.hs, tmp/Utility/FileMode.o )
-    [ 45 of 279] Compiling Git              ( Git.hs, tmp/Git.o )
-    [ 46 of 279] Compiling Git.FilePath     ( Git/FilePath.hs, tmp/Git/FilePath.o )
-    [ 47 of 279] Compiling Utility.Matcher  ( Utility/Matcher.hs, tmp/Utility/Matcher.o )
-    [ 48 of 279] Compiling Utility.Gpg      ( Utility/Gpg.hs, tmp/Utility/Gpg.o )
-    [ 49 of 279] Compiling Types.Crypto     ( Types/Crypto.hs, tmp/Types/Crypto.o )
-    [ 50 of 279] Compiling Types.Key        ( Types/Key.hs, tmp/Types/Key.o )
-    [ 51 of 279] Compiling Types.Backend    ( Types/Backend.hs, tmp/Types/Backend.o )
-    [ 52 of 279] Compiling Types.Remote     ( Types/Remote.hs, tmp/Types/Remote.o )
-    [ 53 of 279] Compiling Git.Sha          ( Git/Sha.hs, tmp/Git/Sha.o )
-    [ 54 of 279] Compiling Utility.CoProcess ( Utility/CoProcess.hs, tmp/Utility/CoProcess.o )
-    [ 55 of 279] Compiling Git.Command      ( Git/Command.hs, tmp/Git/Command.o )
-    [ 56 of 279] Compiling Git.Ref          ( Git/Ref.hs, tmp/Git/Ref.o )
-    [ 57 of 279] Compiling Git.Branch       ( Git/Branch.hs, tmp/Git/Branch.o )
-    [ 58 of 279] Compiling Git.UpdateIndex  ( Git/UpdateIndex.hs, tmp/Git/UpdateIndex.o )
-    [ 59 of 279] Compiling Git.Queue        ( Git/Queue.hs, tmp/Git/Queue.o )
-    [ 60 of 279] Compiling Git.HashObject   ( Git/HashObject.hs, tmp/Git/HashObject.o )
-    [ 61 of 279] Compiling Git.CatFile      ( Git/CatFile.hs, tmp/Git/CatFile.o )
-    [ 62 of 279] Compiling Git.UnionMerge   ( Git/UnionMerge.hs, tmp/Git/UnionMerge.o )
-    [ 63 of 279] Compiling Git.Url          ( Git/Url.hs, tmp/Git/Url.o )
-    [ 64 of 279] Compiling Git.Construct    ( Git/Construct.hs, tmp/Git/Construct.o )
-    [ 65 of 279] Compiling Git.Config       ( Git/Config.hs, tmp/Git/Config.o )
-    [ 66 of 279] Compiling Git.SharedRepository ( Git/SharedRepository.hs, tmp/Git/SharedRepository.o )
-    [ 67 of 279] Compiling Git.Version      ( Git/Version.hs, tmp/Git/Version.o )
-    [ 68 of 279] Compiling Git.CheckAttr    ( Git/CheckAttr.hs, tmp/Git/CheckAttr.o )
-    [ 69 of 279] Compiling Annex            ( Annex.hs, tmp/Annex.o )
-    [ 70 of 279] Compiling Types.Option     ( Types/Option.hs, tmp/Types/Option.o )
-    [ 71 of 279] Compiling Types            ( Types.hs, tmp/Types.o )
-    [ 72 of 279] Compiling Messages         ( Messages.hs, tmp/Messages.o )
-    [ 73 of 279] Compiling Types.Command    ( Types/Command.hs, tmp/Types/Command.o )
-    [ 74 of 279] Compiling Locations        ( Locations.hs, tmp/Locations.o )
-    [ 75 of 279] Compiling Common.Annex     ( Common/Annex.hs, tmp/Common/Annex.o )
-    [ 76 of 279] Compiling Fields           ( Fields.hs, tmp/Fields.o )
-    [ 77 of 279] Compiling Annex.BranchState ( Annex/BranchState.hs, tmp/Annex/BranchState.o )
-    [ 78 of 279] Compiling Annex.CatFile    ( Annex/CatFile.hs, tmp/Annex/CatFile.o )
-    [ 79 of 279] Compiling Annex.Perms      ( Annex/Perms.hs, tmp/Annex/Perms.o )
-    [ 80 of 279] Compiling Crypto           ( Crypto.hs, tmp/Crypto.o )
-    [ 81 of 279] Compiling Annex.Exception  ( Annex/Exception.hs, tmp/Annex/Exception.o )
-    [ 82 of 279] Compiling Annex.Journal    ( Annex/Journal.hs, tmp/Annex/Journal.o )
-    [ 83 of 279] Compiling Annex.Branch     ( Annex/Branch.hs, tmp/Annex/Branch.o )
-    [ 84 of 279] Compiling Usage            ( Usage.hs, tmp/Usage.o )
-    [ 85 of 279] Compiling Annex.CheckAttr  ( Annex/CheckAttr.hs, tmp/Annex/CheckAttr.o )
-    [ 86 of 279] Compiling Remote.Helper.Special ( Remote/Helper/Special.hs, tmp/Remote/Helper/Special.o )
-    [ 87 of 279] Compiling Logs.Presence    ( Logs/Presence.hs, tmp/Logs/Presence.o )
-    [ 88 of 279] Compiling Logs.Location    ( Logs/Location.hs, tmp/Logs/Location.o )
-    [ 89 of 279] Compiling Logs.Web         ( Logs/Web.hs, tmp/Logs/Web.o )
-    [ 90 of 279] Compiling Annex.LockPool   ( Annex/LockPool.hs, tmp/Annex/LockPool.o )
-    [ 91 of 279] Compiling Logs.Transfer    ( Logs/Transfer.hs, tmp/Logs/Transfer.o )
-    [ 92 of 279] Compiling Backend.SHA      ( Backend/SHA.hs, tmp/Backend/SHA.o )
-    [ 93 of 279] Compiling Backend.WORM     ( Backend/WORM.hs, tmp/Backend/WORM.o )
-    [ 94 of 279] Compiling Backend.URL      ( Backend/URL.hs, tmp/Backend/URL.o )
-    [ 95 of 279] Compiling Assistant.Types.ScanRemotes ( Assistant/Types/ScanRemotes.hs, tmp/Assistant/Types/ScanRemotes.o )
-    [ 96 of 279] Compiling Assistant.Types.ThreadedMonad ( Assistant/Types/ThreadedMonad.hs, tmp/Assistant/Types/ThreadedMonad.o )
-    [ 97 of 279] Compiling Assistant.Types.TransferQueue ( Assistant/Types/TransferQueue.hs, tmp/Assistant/Types/TransferQueue.o )
-    [ 98 of 279] Compiling Assistant.Types.Pushes ( Assistant/Types/Pushes.hs, tmp/Assistant/Types/Pushes.o )
-    [ 99 of 279] Compiling Assistant.Types.BranchChange ( Assistant/Types/BranchChange.hs, tmp/Assistant/Types/BranchChange.o )
-    [100 of 279] Compiling Logs.UUIDBased   ( Logs/UUIDBased.hs, tmp/Logs/UUIDBased.o )
-    [101 of 279] Compiling Logs.Remote      ( Logs/Remote.hs, tmp/Logs/Remote.o )
-    [102 of 279] Compiling Logs.Group       ( Logs/Group.hs, tmp/Logs/Group.o )
-    [103 of 279] Compiling Utility.DiskFree ( Utility/DiskFree.hs, tmp/Utility/DiskFree.o )
-    [104 of 279] Compiling Utility.Url      ( Utility/Url.hs, tmp/Utility/Url.o )
-    [105 of 279] Compiling Utility.CopyFile ( Utility/CopyFile.hs, tmp/Utility/CopyFile.o )
-    [106 of 279] Compiling Utility.Rsync    ( Utility/Rsync.hs, tmp/Utility/Rsync.o )
-    [107 of 279] Compiling Git.LsFiles      ( Git/LsFiles.hs, tmp/Git/LsFiles.o )
-    [108 of 279] Compiling Git.AutoCorrect  ( Git/AutoCorrect.hs, tmp/Git/AutoCorrect.o )
-    [109 of 279] Compiling Git.CurrentRepo  ( Git/CurrentRepo.hs, tmp/Git/CurrentRepo.o )
-    [110 of 279] Compiling Locations.UserConfig ( Locations/UserConfig.hs, tmp/Locations/UserConfig.o )
-    [111 of 279] Compiling Utility.ThreadScheduler ( Utility/ThreadScheduler.hs, tmp/Utility/ThreadScheduler.o )
-    [112 of 279] Compiling Git.Merge        ( Git/Merge.hs, tmp/Git/Merge.o )
-    [113 of 279] Compiling Utility.Parallel ( Utility/Parallel.hs, tmp/Utility/Parallel.o )
-    [114 of 279] Compiling Git.Remote       ( Git/Remote.hs, tmp/Git/Remote.o )
-    [115 of 279] Compiling Assistant.Ssh    ( Assistant/Ssh.hs, tmp/Assistant/Ssh.o )
-    [116 of 279] Compiling Assistant.Pairing ( Assistant/Pairing.hs, tmp/Assistant/Pairing.o )
-    [117 of 279] Compiling Assistant.Types.NetMessager ( Assistant/Types/NetMessager.hs, tmp/Assistant/Types/NetMessager.o )
-    [118 of 279] Compiling Utility.NotificationBroadcaster ( Utility/NotificationBroadcaster.hs, tmp/Utility/NotificationBroadcaster.o )
-    [119 of 279] Compiling Assistant.Types.Buddies ( Assistant/Types/Buddies.hs, tmp/Assistant/Types/Buddies.o )
-    [120 of 279] Compiling Utility.TSet     ( Utility/TSet.hs, tmp/Utility/TSet.o )
-    [121 of 279] Compiling Assistant.Types.Commits ( Assistant/Types/Commits.hs, tmp/Assistant/Types/Commits.o )
-    [122 of 279] Compiling Assistant.Types.Changes ( Assistant/Types/Changes.hs, tmp/Assistant/Types/Changes.o )
-    [123 of 279] Compiling Utility.WebApp   ( Utility/WebApp.hs, tmp/Utility/WebApp.o )
-    [124 of 279] Compiling Utility.Daemon   ( Utility/Daemon.hs, tmp/Utility/Daemon.o )
-    [125 of 279] Compiling Utility.LogFile  ( Utility/LogFile.hs, tmp/Utility/LogFile.o )
-    [126 of 279] Compiling Git.Filename     ( Git/Filename.hs, tmp/Git/Filename.o )
-    [127 of 279] Compiling Git.LsTree       ( Git/LsTree.hs, tmp/Git/LsTree.o )
-    [128 of 279] Compiling Utility.Types.DirWatcher ( Utility/Types/DirWatcher.hs, tmp/Utility/Types/DirWatcher.o )
-    [129 of 279] Compiling Utility.INotify  ( Utility/INotify.hs, tmp/Utility/INotify.o )
-    [130 of 279] Compiling Utility.DirWatcher ( Utility/DirWatcher.hs, tmp/Utility/DirWatcher.o )
-    [131 of 279] Compiling Utility.Lsof     ( Utility/Lsof.hs, tmp/Utility/Lsof.o )
-    [132 of 279] Compiling Config           ( Config.hs, tmp/Config.o )
-    [133 of 279] Compiling Annex.UUID       ( Annex/UUID.hs, tmp/Annex/UUID.o )
-    [134 of 279] Compiling Logs.UUID        ( Logs/UUID.hs, tmp/Logs/UUID.o )
-    [135 of 279] Compiling Backend          ( Backend.hs, tmp/Backend.o )
-    [136 of 279] Compiling Remote.Helper.Hooks ( Remote/Helper/Hooks.hs, tmp/Remote/Helper/Hooks.o )
-    [137 of 279] Compiling Remote.Helper.Encryptable ( Remote/Helper/Encryptable.hs, tmp/Remote/Helper/Encryptable.o )
-    [138 of 279] Compiling Annex.Queue      ( Annex/Queue.hs, tmp/Annex/Queue.o )
-    [139 of 279] Compiling Annex.Content    ( Annex/Content.hs, tmp/Annex/Content.o )
-    [140 of 279] Compiling Remote.S3        ( Remote/S3.hs, tmp/Remote/S3.o )
-    [141 of 279] Compiling Remote.Directory ( Remote/Directory.hs, tmp/Remote/Directory.o )
-    [142 of 279] Compiling Remote.Rsync     ( Remote/Rsync.hs, tmp/Remote/Rsync.o )
-    [143 of 279] Compiling Remote.Web       ( Remote/Web.hs, tmp/Remote/Web.o )
-    [144 of 279] Compiling Remote.Hook      ( Remote/Hook.hs, tmp/Remote/Hook.o )
-    [145 of 279] Compiling Upgrade.V2       ( Upgrade/V2.hs, tmp/Upgrade/V2.o )
-    [146 of 279] Compiling Annex.Ssh        ( Annex/Ssh.hs, tmp/Annex/Ssh.o )
-    [147 of 279] Compiling Remote.Helper.Ssh ( Remote/Helper/Ssh.hs, tmp/Remote/Helper/Ssh.o )
-    [148 of 279] Compiling Remote.Bup       ( Remote/Bup.hs, tmp/Remote/Bup.o )
-    [149 of 279] Compiling Annex.Version    ( Annex/Version.hs, tmp/Annex/Version.o )
-    [150 of 279] Compiling Init             ( Init.hs, tmp/Init.o )
-    [151 of 279] Compiling Checks           ( Checks.hs, tmp/Checks.o )
-    [152 of 279] Compiling Remote.Git       ( Remote/Git.hs, tmp/Remote/Git.o )
-    [153 of 279] Compiling Remote.List      ( Remote/List.hs, tmp/Remote/List.o )
-    [154 of 279] Compiling Logs.Trust       ( Logs/Trust.hs, tmp/Logs/Trust.o )
-    [155 of 279] Compiling Remote           ( Remote.hs, tmp/Remote.o )
-    [156 of 279] Compiling Assistant.Alert  ( Assistant/Alert.hs, tmp/Assistant/Alert.o )
-    Loading package ghc-prim ... linking ... done.
-    Loading package integer-gmp ... linking ... done.
-    Loading package base ... linking ... done.
-    Loading object (static) Utility/libdiskfree.o ... done
-    Loading object (static) Utility/libmounts.o ... done
-    final link ... done
-    Loading package pretty-1.1.1.0 ... linking ... done.
-    Loading package filepath-1.3.0.0 ... linking ... done.
-    Loading package old-locale-1.0.0.4 ... linking ... done.
-    Loading package old-time-1.1.0.0 ... linking ... done.
-    Loading package bytestring-0.9.2.1 ... linking ... done.
-    Loading package unix-2.5.1.0 ... linking ... done.
-    Loading package directory-1.1.0.2 ... linking ... done.
-    Loading package process-1.1.0.1 ... linking ... done.
-    Loading package array-0.4.0.0 ... linking ... done.
-    Loading package deepseq-1.3.0.0 ... linking ... done.
-    Loading package time-1.4 ... linking ... done.
-    Loading package containers-0.4.2.1 ... linking ... done.
-    Loading package text-0.11.2.0 ... linking ... done.
-    Loading package blaze-builder-0.3.1.0 ... linking ... done.
-    Loading package blaze-markup-0.5.1.1 ... linking ... done.
-    Loading package blaze-html-0.5.1.0 ... linking ... done.
-    Loading package hashable-1.1.2.5 ... linking ... done.
-    Loading package case-insensitive-0.4.0.3 ... linking ... done.
-    Loading package primitive-0.5.0.1 ... linking ... done.
-    Loading package vector-0.10.0.1 ... linking ... done.
-    Loading package random-1.0.1.1 ... linking ... done.
-    Loading package dlist-0.5 ... linking ... done.
-    Loading package data-default-0.5.0 ... linking ... done.
-    Loading package transformers-0.3.0.0 ... linking ... done.
-    Loading package mtl-2.1.1 ... linking ... done.
-    Loading package parsec-3.1.2 ... linking ... done.
-    Loading package network-2.3.0.13 ... linking ... done.
-    Loading package failure-0.2.0.1 ... linking ... done.
-    Loading package template-haskell ... linking ... done.
-    Loading package shakespeare-1.0.2 ... linking ... done.
-    Loading package hamlet-1.1.1.1 ... linking ... done.
-    Loading package http-types-0.7.3.0.1 ... linking ... done.
-    Loading package base-unicode-symbols-0.2.2.4 ... linking ... done.
-    Loading package transformers-base-0.4.1 ... linking ... done.
-    Loading package monad-control-0.3.1.4 ... linking ... done.
-    Loading package lifted-base-0.2 ... linking ... done.
-    Loading package resourcet-0.4.3 ... linking ... done.
-    Loading package semigroups-0.8.4.1 ... linking ... done.
-    Loading package void-0.5.8 ... linking ... done.
-    Loading package conduit-0.5.4.1 ... linking ... done.
-    Loading package unordered-containers-0.2.2.1 ... linking ... done.
-    Loading package vault-0.2.0.1 ... linking ... done.
-    Loading package wai-1.3.0.1 ... linking ... done.
-    Loading package date-cache-0.3.0 ... linking ... done.
-    Loading package unix-time-0.1.2 ... linking ... done.
-    Loading package fast-logger-0.3.1 ... linking ... done.
-    Loading package attoparsec-0.10.2.0 ... linking ... done.
-    Loading package cookie-0.4.0.1 ... linking ... done.
-    Loading package shakespeare-css-1.0.2 ... linking ... done.
-    Loading package syb-0.3.6.1 ... linking ... done.
-    Loading package aeson-0.6.0.2 ... linking ... done.
-    Loading package shakespeare-js-1.1.0 ... linking ... done.
-    Loading package ansi-terminal-0.5.5 ... linking ... done.
-    Loading package blaze-builder-conduit-0.5.0.2 ... linking ... done.
-    Loading package stringsearch-0.3.6.4 ... linking ... done.
-    Loading package byteorder-1.0.3 ... linking ... done.
-    Loading package wai-logger-0.3.0 ... linking ... done.
-    Loading package zlib-0.5.3.3 ... linking ... done.
-    Loading package zlib-bindings-0.1.1.1 ... linking ... done.
-    Loading package zlib-conduit-0.5.0.2 ... linking ... done.
-    Loading package wai-extra-1.3.0.4 ... linking ... done.
-    Loading package monad-logger-0.2.1 ... linking ... done.
-    Loading package cereal-0.3.5.2 ... linking ... done.
-    Loading package base64-bytestring-1.0.0.0 ... linking ... done.
-    Loading package cipher-aes-0.1.2 ... linking ... done.
-    Loading package entropy-0.2.1 ... linking ... done.
-    Loading package largeword-1.0.3 ... linking ... done.
-    Loading package tagged-0.4.4 ... linking ... done.
-    Loading package crypto-api-0.10.2 ... linking ... done.
-    Loading package cpu-0.1.1 ... linking ... done.
-    Loading package crypto-pubkey-types-0.1.1 ... linking ... done.
-    Loading package cryptocipher-0.3.5 ... linking ... done.
-    Loading package cprng-aes-0.2.4 ... linking ... done.
-    Loading package skein-0.1.0.9 ... linking ... done.
-    Loading package clientsession-0.8.0.1 ... linking ... done.
-    Loading package path-pieces-0.1.2 ... linking ... done.
-    Loading package shakespeare-i18n-1.0.0.2 ... linking ... done.
-    Loading package yesod-routes-1.1.1.1 ... linking ... done.
-    Loading package yesod-core-1.1.5 ... linking ... done.
-    [157 of 279] Compiling Assistant.Types.DaemonStatus ( Assistant/Types/DaemonStatus.hs, tmp/Assistant/Types/DaemonStatus.o )
-    [158 of 279] Compiling Assistant.Monad  ( Assistant/Monad.hs, tmp/Assistant/Monad.o )
-    [159 of 279] Compiling Assistant.Types.NamedThread ( Assistant/Types/NamedThread.hs, tmp/Assistant/Types/NamedThread.o )
-    [160 of 279] Compiling Assistant.Common ( Assistant/Common.hs, tmp/Assistant/Common.o )
-    [161 of 279] Compiling Assistant.XMPP   ( Assistant/XMPP.hs, tmp/Assistant/XMPP.o )
-    [162 of 279] Compiling Assistant.XMPP.Buddies ( Assistant/XMPP/Buddies.hs, tmp/Assistant/XMPP/Buddies.o )
-    [163 of 279] Compiling Assistant.NetMessager ( Assistant/NetMessager.hs, tmp/Assistant/NetMessager.o )
-
-    Assistant/NetMessager.hs:12:1:
-        Warning: The import of `Types.Remote' is redundant
-                   except perhaps to import instances from `Types.Remote'
-                 To import instances alone, use: import Types.Remote()
-
-    Assistant/NetMessager.hs:13:1:
-        Warning: The import of `Git' is redundant
-                   except perhaps to import instances from `Git'
-                 To import instances alone, use: import Git()
-
-    Assistant/NetMessager.hs:20:1:
-        Warning: The import of `Data.Text' is redundant
-                   except perhaps to import instances from `Data.Text'
-                 To import instances alone, use: import Data.Text()
-    [164 of 279] Compiling Assistant.Pushes ( Assistant/Pushes.hs, tmp/Assistant/Pushes.o )
-    [165 of 279] Compiling Assistant.ScanRemotes ( Assistant/ScanRemotes.hs, tmp/Assistant/ScanRemotes.o )
-    [166 of 279] Compiling Assistant.Install ( Assistant/Install.hs, tmp/Assistant/Install.o )
-    [167 of 279] Compiling Assistant.XMPP.Client ( Assistant/XMPP/Client.hs, tmp/Assistant/XMPP/Client.o )
-    [168 of 279] Compiling Assistant.Commits ( Assistant/Commits.hs, tmp/Assistant/Commits.o )
-    [169 of 279] Compiling Assistant.BranchChange ( Assistant/BranchChange.hs, tmp/Assistant/BranchChange.o )
-    [170 of 279] Compiling Assistant.Changes ( Assistant/Changes.hs, tmp/Assistant/Changes.o )
-    [171 of 279] Compiling Assistant.WebApp.Types ( Assistant/WebApp/Types.hs, tmp/Assistant/WebApp/Types.o )
-    Loading package unix-compat-0.4.0.0 ... linking ... done.
-    Loading package file-embed-0.0.4.6 ... linking ... done.
-    Loading package system-filepath-0.4.7 ... linking ... done.
-    Loading package system-fileio-0.3.10 ... linking ... done.
-    Loading package cryptohash-0.7.8 ... linking ... done.
-    Loading package crypto-conduit-0.4.0.1 ... linking ... done.
-    Loading package http-date-0.0.2 ... linking ... done.
-    Loading package mime-types-0.1.0.0 ... linking ... done.
-    Loading package wai-app-static-1.3.0.4 ... linking ... done.
-    Loading package yesod-static-1.1.1.1 ... linking ... done.
-    [172 of 279] Compiling Assistant.WebApp ( Assistant/WebApp.hs, tmp/Assistant/WebApp.o )
-    Loading package network-conduit-0.6.1.1 ... linking ... done.
-    Loading package safe-0.3.3 ... linking ... done.
-    Loading package simple-sendfile-0.2.8 ... linking ... done.
-    Loading package warp-1.3.4.4 ... linking ... done.
-    Loading package yaml-0.8.1 ... linking ... done.
-    Loading package yesod-default-1.1.2 ... linking ... done.
-    [173 of 279] Compiling Assistant.WebApp.OtherRepos ( Assistant/WebApp/OtherRepos.hs, tmp/Assistant/WebApp/OtherRepos.o )
-    [174 of 279] Compiling Limit            ( Limit.hs, tmp/Limit.o )
-    [175 of 279] Compiling Option           ( Option.hs, tmp/Option.o )
-    [176 of 279] Compiling Seek             ( Seek.hs, tmp/Seek.o )
-    [177 of 279] Compiling Command          ( Command.hs, tmp/Command.o )
-    [178 of 279] Compiling CmdLine          ( CmdLine.hs, tmp/CmdLine.o )
-    [179 of 279] Compiling Command.ConfigList ( Command/ConfigList.hs, tmp/Command/ConfigList.o )
-    [180 of 279] Compiling Command.InAnnex  ( Command/InAnnex.hs, tmp/Command/InAnnex.o )
-    [181 of 279] Compiling Command.DropKey  ( Command/DropKey.hs, tmp/Command/DropKey.o )
-    [182 of 279] Compiling Command.SendKey  ( Command/SendKey.hs, tmp/Command/SendKey.o )
-    [183 of 279] Compiling Command.RecvKey  ( Command/RecvKey.hs, tmp/Command/RecvKey.o )
-    [184 of 279] Compiling Command.TransferInfo ( Command/TransferInfo.hs, tmp/Command/TransferInfo.o )
-    [185 of 279] Compiling Command.Commit   ( Command/Commit.hs, tmp/Command/Commit.o )
-    [186 of 279] Compiling Command.Add      ( Command/Add.hs, tmp/Command/Add.o )
-    [187 of 279] Compiling Command.Unannex  ( Command/Unannex.hs, tmp/Command/Unannex.o )
-    [188 of 279] Compiling Command.FromKey  ( Command/FromKey.hs, tmp/Command/FromKey.o )
-    [189 of 279] Compiling Command.ReKey    ( Command/ReKey.hs, tmp/Command/ReKey.o )
-    [190 of 279] Compiling Command.Fix      ( Command/Fix.hs, tmp/Command/Fix.o )
-    [191 of 279] Compiling Command.Describe ( Command/Describe.hs, tmp/Command/Describe.o )
-    [192 of 279] Compiling Command.InitRemote ( Command/InitRemote.hs, tmp/Command/InitRemote.o )
-    [193 of 279] Compiling Command.Unlock   ( Command/Unlock.hs, tmp/Command/Unlock.o )
-    [194 of 279] Compiling Command.Lock     ( Command/Lock.hs, tmp/Command/Lock.o )
-    [195 of 279] Compiling Command.PreCommit ( Command/PreCommit.hs, tmp/Command/PreCommit.o )
-    [196 of 279] Compiling Command.Log      ( Command/Log.hs, tmp/Command/Log.o )
-    [197 of 279] Compiling Command.Merge    ( Command/Merge.hs, tmp/Command/Merge.o )
-    [198 of 279] Compiling Command.Group    ( Command/Group.hs, tmp/Command/Group.o )
-    [199 of 279] Compiling Command.Ungroup  ( Command/Ungroup.hs, tmp/Command/Ungroup.o )
-    [200 of 279] Compiling Command.Import   ( Command/Import.hs, tmp/Command/Import.o )
-    [201 of 279] Compiling Logs.Unused      ( Logs/Unused.hs, tmp/Logs/Unused.o )
-    [202 of 279] Compiling Command.AddUnused ( Command/AddUnused.hs, tmp/Command/AddUnused.o )
-    [203 of 279] Compiling Command.Find     ( Command/Find.hs, tmp/Command/Find.o )
-    [204 of 279] Compiling Logs.PreferredContent ( Logs/PreferredContent.hs, tmp/Logs/PreferredContent.o )
-    [205 of 279] Compiling Annex.Wanted     ( Annex/Wanted.hs, tmp/Annex/Wanted.o )
-    [206 of 279] Compiling Command.Whereis  ( Command/Whereis.hs, tmp/Command/Whereis.o )
-    [207 of 279] Compiling Command.Trust    ( Command/Trust.hs, tmp/Command/Trust.o )
-    [208 of 279] Compiling Command.Untrust  ( Command/Untrust.hs, tmp/Command/Untrust.o )
-    [209 of 279] Compiling Command.Semitrust ( Command/Semitrust.hs, tmp/Command/Semitrust.o )
-    [210 of 279] Compiling Command.Dead     ( Command/Dead.hs, tmp/Command/Dead.o )
-    [211 of 279] Compiling Command.Vicfg    ( Command/Vicfg.hs, tmp/Command/Vicfg.o )
-    [212 of 279] Compiling Command.Map      ( Command/Map.hs, tmp/Command/Map.o )
-    [213 of 279] Compiling Command.Init     ( Command/Init.hs, tmp/Command/Init.o )
-    [214 of 279] Compiling Command.Uninit   ( Command/Uninit.hs, tmp/Command/Uninit.o )
-    [215 of 279] Compiling Command.Version  ( Command/Version.hs, tmp/Command/Version.o )
-    [216 of 279] Compiling Upgrade.V1       ( Upgrade/V1.hs, tmp/Upgrade/V1.o )
-    [217 of 279] Compiling Upgrade.V0       ( Upgrade/V0.hs, tmp/Upgrade/V0.o )
-    [218 of 279] Compiling Upgrade          ( Upgrade.hs, tmp/Upgrade.o )
-    [219 of 279] Compiling Command.Upgrade  ( Command/Upgrade.hs, tmp/Command/Upgrade.o )
-    [220 of 279] Compiling Command.Drop     ( Command/Drop.hs, tmp/Command/Drop.o )
-    [221 of 279] Compiling Command.Move     ( Command/Move.hs, tmp/Command/Move.o )
-    [222 of 279] Compiling Command.Copy     ( Command/Copy.hs, tmp/Command/Copy.o )
-    [223 of 279] Compiling Command.Get      ( Command/Get.hs, tmp/Command/Get.o )
-    [224 of 279] Compiling Command.TransferKey ( Command/TransferKey.hs, tmp/Command/TransferKey.o )
-    [225 of 279] Compiling Command.DropUnused ( Command/DropUnused.hs, tmp/Command/DropUnused.o )
-    [226 of 279] Compiling Command.Fsck     ( Command/Fsck.hs, tmp/Command/Fsck.o )
-    [227 of 279] Compiling Command.Reinject ( Command/Reinject.hs, tmp/Command/Reinject.o )
-    [228 of 279] Compiling Command.Migrate  ( Command/Migrate.hs, tmp/Command/Migrate.o )
-    [229 of 279] Compiling Command.Unused   ( Command/Unused.hs, tmp/Command/Unused.o )
-    [230 of 279] Compiling Command.Status   ( Command/Status.hs, tmp/Command/Status.o )
-    [231 of 279] Compiling Command.Sync     ( Command/Sync.hs, tmp/Command/Sync.o )
-    [232 of 279] Compiling Command.Help     ( Command/Help.hs, tmp/Command/Help.o )
-    [233 of 279] Compiling Command.AddUrl   ( Command/AddUrl.hs, tmp/Command/AddUrl.o )
-    [234 of 279] Compiling Assistant.DaemonStatus ( Assistant/DaemonStatus.hs, tmp/Assistant/DaemonStatus.o )
-    [235 of 279] Compiling Assistant.Sync   ( Assistant/Sync.hs, tmp/Assistant/Sync.o )
-    [236 of 279] Compiling Assistant.MakeRemote ( Assistant/MakeRemote.hs, tmp/Assistant/MakeRemote.o )
-    [237 of 279] Compiling Assistant.XMPP.Git ( Assistant/XMPP/Git.hs, tmp/Assistant/XMPP/Git.o )
-    [238 of 279] Compiling Command.XMPPGit  ( Command/XMPPGit.hs, tmp/Command/XMPPGit.o )
-    [239 of 279] Compiling Assistant.Threads.NetWatcher ( Assistant/Threads/NetWatcher.hs, tmp/Assistant/Threads/NetWatcher.o )
-    [240 of 279] Compiling Assistant.NamedThread ( Assistant/NamedThread.hs, tmp/Assistant/NamedThread.o )
-    [241 of 279] Compiling Assistant.WebApp.Notifications ( Assistant/WebApp/Notifications.hs, tmp/Assistant/WebApp/Notifications.o )
-
-    Assistant/WebApp/Notifications.hs:39:11:
-        No instances for (Text.Julius.ToJavascript String,
-                          Text.Julius.ToJavascript Text)
-          arising from a use of `Text.Julius.toJavascript'
-        Possible fix:
-          add instance declarations for
-          (Text.Julius.ToJavascript String, Text.Julius.ToJavascript Text)
-        In the first argument of `Text.Julius.Javascript', namely
-          `Text.Julius.toJavascript delay'
-        In the expression:
-          Text.Julius.Javascript (Text.Julius.toJavascript delay)
-        In the first argument of `Data.Monoid.mconcat', namely
-          `[Text.Julius.Javascript
-              ((Data.Text.Lazy.Builder.fromText . Text.Shakespeare.pack')
-                 "function longpoll_"),
-            Text.Julius.Javascript (Text.Julius.toJavascript ident),
-            Text.Julius.Javascript
-              ((Data.Text.Lazy.Builder.fromText . Text.Shakespeare.pack')
-                 "() {\
-                 \\tlongpoll(longpoll_"),
-            Text.Julius.Javascript (Text.Julius.toJavascript ident), ....]'
-    make: *** [git-annex] Error 1
-
-> Reproduced this and confirmed it's fixed in git. --[[Joey]] [[done]]
diff --git a/doc/bugs/3.20121112:_build_error_in_assistant/comment_1_b42f40ffd83321ab5cc0ef24ced15e98._comment b/doc/bugs/3.20121112:_build_error_in_assistant/comment_1_b42f40ffd83321ab5cc0ef24ced15e98._comment
deleted file mode 100644
index 9690885f0..000000000
--- a/doc/bugs/3.20121112:_build_error_in_assistant/comment_1_b42f40ffd83321ab5cc0ef24ced15e98._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.252.11.120"
- subject="comment 1"
- date="2012-11-17T20:21:12Z"
- content="""
-This looks rather like a bug in Yesod. I've made a change in git (b0a76592c313b4c8f51918d6469c40d1fd16a2b1) that *may* avoid the problem.
-"""]]
diff --git a/doc/bugs/3.20121112:_build_error_in_assistant/comment_2_b1d2aa10ea84c5c370b3e76507fc8761._comment b/doc/bugs/3.20121112:_build_error_in_assistant/comment_2_b1d2aa10ea84c5c370b3e76507fc8761._comment
deleted file mode 100644
index 0d4f3666c..000000000
--- a/doc/bugs/3.20121112:_build_error_in_assistant/comment_2_b1d2aa10ea84c5c370b3e76507fc8761._comment
+++ /dev/null
@@ -1,476 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkHZw2Vx0VPtb9XM8vum7nEnh6gHGSCQvM"
- nickname="Andrew"
- subject="comment 2"
- date="2012-11-24T18:48:23Z"
- content="""
-Not quite. Though this might just be an artifact of me disabling WITH_WEBDAV on account of that not compiling on OS X (can't find module Network.Protocol.HTTP.DAV).
-OS: OS X 10.8.0
-
-    % git branch -v
-    * master d1ba407 Added a comment: git annex fix
-    % grep \"FEATURES?=\" Makefile
-    FEATURES?=$(GIT_ANNEX_LOCAL_FEATURES) -DWITH_ASSISTANT -DWITH_S3 -DWITH_WEBAPP -DWITH_PAIRING -DWITH_XMPP -DWITH_DNS
-    $ make
-    ghc -O2 -Wall -outputdir tmp -IUtility  -DWITH_ASSISTANT -DWITH_S3 -DWITH_WEBAPP -DWITH_PAIRING -DWITH_XMPP -DWITH_DNS -DWITH_KQUEUE -threaded --make configure
-    [1 of 7] Compiling Utility.Exception ( Utility/Exception.hs, tmp/Utility/Exception.o )
-    [2 of 7] Compiling Utility.Misc     ( Utility/Misc.hs, tmp/Utility/Misc.o )
-    [3 of 7] Compiling Utility.Process  ( Utility/Process.hs, tmp/Utility/Process.o )
-    [4 of 7] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, tmp/Utility/SafeCommand.o )
-    [5 of 7] Compiling Build.TestConfig ( Build/TestConfig.hs, tmp/Build/TestConfig.o )
-    [6 of 7] Compiling Build.Configure  ( Build/Configure.hs, tmp/Build/Configure.o )
-    [7 of 7] Compiling Main             ( configure.hs, tmp/Main.o )
-    Linking configure ...
-    ./configure
-      checking version... 3.20121113
-      checking git... yes
-      checking git version... 1.7.10.2 (Apple Git-33)
-      checking cp -a... yes
-      checking cp -p... yes
-      checking cp --reflink=auto... no
-      checking uuid generator... uuidgen
-      checking xargs -0... yes
-      checking rsync... yes
-      checking curl... yes
-      checking wget... no
-      checking bup... no
-      checking gpg... no
-      checking lsof... yes
-      checking ssh connection caching... yes
-      checking sha1... sha1sum
-      checking sha256.../bin/sh: sha256sum: command not found
-     gsha256sum
-      checking sha512.../bin/sh: sha512sum: command not found
-     gsha512sum
-      checking sha224.../bin/sh: sha224sum: command not found
-     gsha224sum
-      checking sha384.../bin/sh: sha384sum: command not found
-     gsha384sum
-    hsc2hs Utility/Touch.hsc
-    Touch.hsc:117:2: warning: #warning \"utimensat and lutimes not available; building without symlink timestamp preservation support\"
-    Touch.hsc:117:2: warning: #warning \"utimensat and lutimes not available; building without symlink timestamp preservation support\"
-    Touch.hsc:117:2: warning: #warning \"utimensat and lutimes not available; building without symlink timestamp preservation support\"
-    hsc2hs Utility/Mounts.hsc
-    cc -Wall   -c -o Utility/libdiskfree.o Utility/libdiskfree.c
-    Utility/libdiskfree.c:53:6: warning: 'statfs64' is deprecated: first deprecated in Mac OS X 10.6 [-Wdeprecated-declarations]
-            if (STATCALL(path, &buf) != 0)
-                ^
-    Utility/libdiskfree.c:16:19: note: expanded from macro 'STATCALL'
-    # define STATCALL statfs64
-                      ^
-    /usr/include/sys/mount.h:381:5: note: 'statfs64' declared here
-    int     statfs64(const char *, struct statfs64 *) __OSX_AVAILABLE_BUT_DEPRECATED(__MAC_10_5,__MAC_10_6,__IPHONE_NA,__IPHONE_NA);
-            ^
-    1 warning generated.
-    cc -Wall   -c -o Utility/libmounts.o Utility/libmounts.c
-    cc -Wall   -c -o Utility/libkqueue.o Utility/libkqueue.c
-    install -d tmp
-    ghc -O2 -Wall -outputdir tmp -IUtility  -DWITH_ASSISTANT -DWITH_S3 -DWITH_WEBAPP -DWITH_PAIRING -DWITH_XMPP -DWITH_DNS -DWITH_KQUEUE -threaded --make git-annex -o tmp/git-annex Utility/libdiskfree.o Utility/libmounts.o Utility/libkqueue.o
-
-    Assistant/Threads/NetWatcher.hs:26:0:
-         warning: #warning Building without dbus support; will poll for network connection changes
-
-    Assistant/Threads/MountWatcher.hs:33:0:
-         warning: #warning Building without dbus support; will use mtab polling
-    [  1 of 285] Compiling Utility.Dot      ( Utility/Dot.hs, tmp/Utility/Dot.o )
-    [  2 of 285] Compiling Utility.Mounts   ( Utility/Mounts.hs, tmp/Utility/Mounts.o )
-    [  3 of 285] Compiling Utility.Yesod    ( Utility/Yesod.hs, tmp/Utility/Yesod.o )
-    [  4 of 285] Compiling Utility.Tense    ( Utility/Tense.hs, tmp/Utility/Tense.o )
-    [  5 of 285] Compiling Utility.Verifiable ( Utility/Verifiable.hs, tmp/Utility/Verifiable.o )
-    [  6 of 285] Compiling Assistant.Types.TransferSlots ( Assistant/Types/TransferSlots.hs, tmp/Assistant/Types/TransferSlots.o )
-    [  7 of 285] Compiling Types.StandardGroups ( Types/StandardGroups.hs, tmp/Types/StandardGroups.o )
-    [  8 of 285] Compiling Utility.Percentage ( Utility/Percentage.hs, tmp/Utility/Percentage.o )
-    [  9 of 285] Compiling Utility.Observed ( Utility/Observed.hs, tmp/Utility/Observed.o )
-    [ 10 of 285] Compiling Utility.Base64   ( Utility/Base64.hs, tmp/Utility/Base64.o )
-    [ 11 of 285] Compiling Utility.DataUnits ( Utility/DataUnits.hs, tmp/Utility/DataUnits.o )
-    [ 12 of 285] Compiling Utility.JSONStream ( Utility/JSONStream.hs, tmp/Utility/JSONStream.o )
-    [ 13 of 285] Compiling Messages.JSON    ( Messages/JSON.hs, tmp/Messages/JSON.o )
-    [ 14 of 285] Compiling Build.SysConfig  ( Build/SysConfig.hs, tmp/Build/SysConfig.o )
-    [ 15 of 285] Compiling Types.KeySource  ( Types/KeySource.hs, tmp/Types/KeySource.o )
-    [ 16 of 285] Compiling Types.Meters     ( Types/Meters.hs, tmp/Types/Meters.o )
-    [ 17 of 285] Compiling Utility.State    ( Utility/State.hs, tmp/Utility/State.o )
-    [ 18 of 285] Compiling Types.UUID       ( Types/UUID.hs, tmp/Types/UUID.o )
-    [ 19 of 285] Compiling Types.Messages   ( Types/Messages.hs, tmp/Types/Messages.o )
-    [ 20 of 285] Compiling Types.Group      ( Types/Group.hs, tmp/Types/Group.o )
-    [ 21 of 285] Compiling Types.TrustLevel ( Types/TrustLevel.hs, tmp/Types/TrustLevel.o )
-    [ 22 of 285] Compiling Types.BranchState ( Types/BranchState.hs, tmp/Types/BranchState.o )
-    [ 23 of 285] Compiling Utility.PartialPrelude ( Utility/PartialPrelude.hs, tmp/Utility/PartialPrelude.o )
-    [ 24 of 285] Compiling Utility.HumanTime ( Utility/HumanTime.hs, tmp/Utility/HumanTime.o )
-    [ 25 of 285] Compiling Utility.Format   ( Utility/Format.hs, tmp/Utility/Format.o )
-    [ 26 of 285] Compiling Utility.FileSystemEncoding ( Utility/FileSystemEncoding.hs, tmp/Utility/FileSystemEncoding.o )
-    [ 27 of 285] Compiling Utility.Touch    ( Utility/Touch.hs, tmp/Utility/Touch.o )
-
-    Utility/Touch.hsc:17:1:
-        Warning: The import of `Utility.FileSystemEncoding' is redundant
-                   except perhaps to import instances from `Utility.FileSystemEncoding'
-                 To import instances alone, use: import Utility.FileSystemEncoding()
-
-    Utility/Touch.hsc:19:1:
-        Warning: The import of `Foreign' is redundant
-                   except perhaps to import instances from `Foreign'
-                 To import instances alone, use: import Foreign()
-
-    Utility/Touch.hsc:21:1:
-        Warning: The import of `Control.Monad' is redundant
-                   except perhaps to import instances from `Control.Monad'
-                 To import instances alone, use: import Control.Monad()
-    [ 28 of 285] Compiling Utility.Applicative ( Utility/Applicative.hs, tmp/Utility/Applicative.o )
-    [ 29 of 285] Compiling Utility.Monad    ( Utility/Monad.hs, tmp/Utility/Monad.o )
-    [ 30 of 285] Compiling Utility.Exception ( Utility/Exception.hs, tmp/Utility/Exception.o )
-    [ 31 of 285] Compiling Utility.Misc     ( Utility/Misc.hs, tmp/Utility/Misc.o )
-    [ 32 of 285] Compiling Utility.Process  ( Utility/Process.hs, tmp/Utility/Process.o )
-    [ 33 of 285] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, tmp/Utility/SafeCommand.o )
-    [ 34 of 285] Compiling Utility.Network  ( Utility/Network.hs, tmp/Utility/Network.o )
-    [ 35 of 285] Compiling Utility.SRV      ( Utility/SRV.hs, tmp/Utility/SRV.o )
-
-    Utility/SRV.hs:88:1: Warning: Defined but not used: `lookupSRVHost'
-
-    Utility/SRV.hs:94:1: Warning: Defined but not used: `parseSrvHost'
-    [ 36 of 285] Compiling Git.Types        ( Git/Types.hs, tmp/Git/Types.o )
-    [ 37 of 285] Compiling Utility.UserInfo ( Utility/UserInfo.hs, tmp/Utility/UserInfo.o )
-    [ 38 of 285] Compiling Utility.Path     ( Utility/Path.hs, tmp/Utility/Path.o )
-    [ 39 of 285] Compiling Utility.TempFile ( Utility/TempFile.hs, tmp/Utility/TempFile.o )
-    [ 40 of 285] Compiling Utility.Directory ( Utility/Directory.hs, tmp/Utility/Directory.o )
-    [ 41 of 285] Compiling Utility.FreeDesktop ( Utility/FreeDesktop.hs, tmp/Utility/FreeDesktop.o )
-    [ 42 of 285] Compiling Utility.OSX      ( Utility/OSX.hs, tmp/Utility/OSX.o )
-
-    Utility/OSX.hs:10:1:
-        Warning: The import of `Utility.Path' is redundant
-                   except perhaps to import instances from `Utility.Path'
-                 To import instances alone, use: import Utility.Path()
-    [ 43 of 285] Compiling Assistant.Install.AutoStart ( Assistant/Install/AutoStart.hs, tmp/Assistant/Install/AutoStart.o )
-    [ 44 of 285] Compiling Common           ( Common.hs, tmp/Common.o )
-    [ 45 of 285] Compiling Utility.FileMode ( Utility/FileMode.hs, tmp/Utility/FileMode.o )
-    [ 46 of 285] Compiling Git              ( Git.hs, tmp/Git.o )
-    [ 47 of 285] Compiling Git.FilePath     ( Git/FilePath.hs, tmp/Git/FilePath.o )
-    [ 48 of 285] Compiling Utility.Matcher  ( Utility/Matcher.hs, tmp/Utility/Matcher.o )
-    [ 49 of 285] Compiling Utility.Gpg      ( Utility/Gpg.hs, tmp/Utility/Gpg.o )
-    [ 50 of 285] Compiling Types.Crypto     ( Types/Crypto.hs, tmp/Types/Crypto.o )
-    [ 51 of 285] Compiling Types.Key        ( Types/Key.hs, tmp/Types/Key.o )
-    [ 52 of 285] Compiling Types.Backend    ( Types/Backend.hs, tmp/Types/Backend.o )
-    [ 53 of 285] Compiling Types.Remote     ( Types/Remote.hs, tmp/Types/Remote.o )
-    [ 54 of 285] Compiling Meters           ( Meters.hs, tmp/Meters.o )
-    [ 55 of 285] Compiling Git.Sha          ( Git/Sha.hs, tmp/Git/Sha.o )
-    [ 56 of 285] Compiling Utility.CoProcess ( Utility/CoProcess.hs, tmp/Utility/CoProcess.o )
-    [ 57 of 285] Compiling Git.Command      ( Git/Command.hs, tmp/Git/Command.o )
-    [ 58 of 285] Compiling Git.Ref          ( Git/Ref.hs, tmp/Git/Ref.o )
-    [ 59 of 285] Compiling Git.Branch       ( Git/Branch.hs, tmp/Git/Branch.o )
-    [ 60 of 285] Compiling Git.UpdateIndex  ( Git/UpdateIndex.hs, tmp/Git/UpdateIndex.o )
-    [ 61 of 285] Compiling Git.Queue        ( Git/Queue.hs, tmp/Git/Queue.o )
-    [ 62 of 285] Compiling Git.HashObject   ( Git/HashObject.hs, tmp/Git/HashObject.o )
-    [ 63 of 285] Compiling Git.CatFile      ( Git/CatFile.hs, tmp/Git/CatFile.o )
-    [ 64 of 285] Compiling Git.UnionMerge   ( Git/UnionMerge.hs, tmp/Git/UnionMerge.o )
-    [ 65 of 285] Compiling Git.Url          ( Git/Url.hs, tmp/Git/Url.o )
-    [ 66 of 285] Compiling Git.Construct    ( Git/Construct.hs, tmp/Git/Construct.o )
-    [ 67 of 285] Compiling Git.Config       ( Git/Config.hs, tmp/Git/Config.o )
-    [ 68 of 285] Compiling Git.SharedRepository ( Git/SharedRepository.hs, tmp/Git/SharedRepository.o )
-    [ 69 of 285] Compiling Git.Version      ( Git/Version.hs, tmp/Git/Version.o )
-    [ 70 of 285] Compiling Git.CheckAttr    ( Git/CheckAttr.hs, tmp/Git/CheckAttr.o )
-    [ 71 of 285] Compiling Annex            ( Annex.hs, tmp/Annex.o )
-    [ 72 of 285] Compiling Types.Option     ( Types/Option.hs, tmp/Types/Option.o )
-    [ 73 of 285] Compiling Types            ( Types.hs, tmp/Types.o )
-    [ 74 of 285] Compiling Messages         ( Messages.hs, tmp/Messages.o )
-    [ 75 of 285] Compiling Types.Command    ( Types/Command.hs, tmp/Types/Command.o )
-    [ 76 of 285] Compiling Locations        ( Locations.hs, tmp/Locations.o )
-    [ 77 of 285] Compiling Common.Annex     ( Common/Annex.hs, tmp/Common/Annex.o )
-    [ 78 of 285] Compiling Fields           ( Fields.hs, tmp/Fields.o )
-    [ 79 of 285] Compiling Annex.BranchState ( Annex/BranchState.hs, tmp/Annex/BranchState.o )
-    [ 80 of 285] Compiling Annex.CatFile    ( Annex/CatFile.hs, tmp/Annex/CatFile.o )
-    [ 81 of 285] Compiling Annex.Perms      ( Annex/Perms.hs, tmp/Annex/Perms.o )
-    [ 82 of 285] Compiling Crypto           ( Crypto.hs, tmp/Crypto.o )
-    [ 83 of 285] Compiling Annex.Exception  ( Annex/Exception.hs, tmp/Annex/Exception.o )
-    [ 84 of 285] Compiling Annex.Journal    ( Annex/Journal.hs, tmp/Annex/Journal.o )
-    [ 85 of 285] Compiling Annex.Branch     ( Annex/Branch.hs, tmp/Annex/Branch.o )
-    [ 86 of 285] Compiling Usage            ( Usage.hs, tmp/Usage.o )
-    [ 87 of 285] Compiling Annex.CheckAttr  ( Annex/CheckAttr.hs, tmp/Annex/CheckAttr.o )
-    [ 88 of 285] Compiling Remote.Helper.Special ( Remote/Helper/Special.hs, tmp/Remote/Helper/Special.o )
-    [ 89 of 285] Compiling Logs.Presence    ( Logs/Presence.hs, tmp/Logs/Presence.o )
-    [ 90 of 285] Compiling Logs.Location    ( Logs/Location.hs, tmp/Logs/Location.o )
-    [ 91 of 285] Compiling Logs.Web         ( Logs/Web.hs, tmp/Logs/Web.o )
-    [ 92 of 285] Compiling Remote.Helper.Chunked ( Remote/Helper/Chunked.hs, tmp/Remote/Helper/Chunked.o )
-    [ 93 of 285] Compiling Annex.LockPool   ( Annex/LockPool.hs, tmp/Annex/LockPool.o )
-    [ 94 of 285] Compiling Logs.Transfer    ( Logs/Transfer.hs, tmp/Logs/Transfer.o )
-    [ 95 of 285] Compiling Backend.SHA      ( Backend/SHA.hs, tmp/Backend/SHA.o )
-    [ 96 of 285] Compiling Backend.WORM     ( Backend/WORM.hs, tmp/Backend/WORM.o )
-    [ 97 of 285] Compiling Backend.URL      ( Backend/URL.hs, tmp/Backend/URL.o )
-    [ 98 of 285] Compiling Assistant.Types.ScanRemotes ( Assistant/Types/ScanRemotes.hs, tmp/Assistant/Types/ScanRemotes.o )
-    [ 99 of 285] Compiling Assistant.Types.ThreadedMonad ( Assistant/Types/ThreadedMonad.hs, tmp/Assistant/Types/ThreadedMonad.o )
-    [100 of 285] Compiling Assistant.Types.TransferQueue ( Assistant/Types/TransferQueue.hs, tmp/Assistant/Types/TransferQueue.o )
-    [101 of 285] Compiling Assistant.Types.Pushes ( Assistant/Types/Pushes.hs, tmp/Assistant/Types/Pushes.o )
-    [102 of 285] Compiling Assistant.Types.BranchChange ( Assistant/Types/BranchChange.hs, tmp/Assistant/Types/BranchChange.o )
-    [103 of 285] Compiling Logs.UUIDBased   ( Logs/UUIDBased.hs, tmp/Logs/UUIDBased.o )
-    [104 of 285] Compiling Logs.Remote      ( Logs/Remote.hs, tmp/Logs/Remote.o )
-    [105 of 285] Compiling Logs.Group       ( Logs/Group.hs, tmp/Logs/Group.o )
-    [106 of 285] Compiling Utility.DiskFree ( Utility/DiskFree.hs, tmp/Utility/DiskFree.o )
-    [107 of 285] Compiling Utility.Url      ( Utility/Url.hs, tmp/Utility/Url.o )
-    [108 of 285] Compiling Utility.CopyFile ( Utility/CopyFile.hs, tmp/Utility/CopyFile.o )
-    [109 of 285] Compiling Utility.Rsync    ( Utility/Rsync.hs, tmp/Utility/Rsync.o )
-    [110 of 285] Compiling Git.LsFiles      ( Git/LsFiles.hs, tmp/Git/LsFiles.o )
-    [111 of 285] Compiling Git.AutoCorrect  ( Git/AutoCorrect.hs, tmp/Git/AutoCorrect.o )
-    [112 of 285] Compiling Git.CurrentRepo  ( Git/CurrentRepo.hs, tmp/Git/CurrentRepo.o )
-    [113 of 285] Compiling Locations.UserConfig ( Locations/UserConfig.hs, tmp/Locations/UserConfig.o )
-    [114 of 285] Compiling Git.Merge        ( Git/Merge.hs, tmp/Git/Merge.o )
-    [115 of 285] Compiling Utility.Parallel ( Utility/Parallel.hs, tmp/Utility/Parallel.o )
-    [116 of 285] Compiling Git.Remote       ( Git/Remote.hs, tmp/Git/Remote.o )
-    [117 of 285] Compiling Assistant.Ssh    ( Assistant/Ssh.hs, tmp/Assistant/Ssh.o )
-    [118 of 285] Compiling Assistant.Pairing ( Assistant/Pairing.hs, tmp/Assistant/Pairing.o )
-    [119 of 285] Compiling Assistant.Types.NetMessager ( Assistant/Types/NetMessager.hs, tmp/Assistant/Types/NetMessager.o )
-    [120 of 285] Compiling Utility.NotificationBroadcaster ( Utility/NotificationBroadcaster.hs, tmp/Utility/NotificationBroadcaster.o )
-    [121 of 285] Compiling Assistant.Types.Buddies ( Assistant/Types/Buddies.hs, tmp/Assistant/Types/Buddies.o )
-    [122 of 285] Compiling Utility.TSet     ( Utility/TSet.hs, tmp/Utility/TSet.o )
-    [123 of 285] Compiling Assistant.Types.Commits ( Assistant/Types/Commits.hs, tmp/Assistant/Types/Commits.o )
-    [124 of 285] Compiling Assistant.Types.Changes ( Assistant/Types/Changes.hs, tmp/Assistant/Types/Changes.o )
-    [125 of 285] Compiling Utility.WebApp   ( Utility/WebApp.hs, tmp/Utility/WebApp.o )
-    [126 of 285] Compiling Utility.Daemon   ( Utility/Daemon.hs, tmp/Utility/Daemon.o )
-    [127 of 285] Compiling Utility.ThreadScheduler ( Utility/ThreadScheduler.hs, tmp/Utility/ThreadScheduler.o )
-    [128 of 285] Compiling Utility.LogFile  ( Utility/LogFile.hs, tmp/Utility/LogFile.o )
-    [129 of 285] Compiling Git.Filename     ( Git/Filename.hs, tmp/Git/Filename.o )
-    [130 of 285] Compiling Git.LsTree       ( Git/LsTree.hs, tmp/Git/LsTree.o )
-    [131 of 285] Compiling Utility.Types.DirWatcher ( Utility/Types/DirWatcher.hs, tmp/Utility/Types/DirWatcher.o )
-    [132 of 285] Compiling Utility.Kqueue   ( Utility/Kqueue.hs, tmp/Utility/Kqueue.o )
-    [133 of 285] Compiling Utility.DirWatcher ( Utility/DirWatcher.hs, tmp/Utility/DirWatcher.o )
-    [134 of 285] Compiling Utility.Lsof     ( Utility/Lsof.hs, tmp/Utility/Lsof.o )
-    [135 of 285] Compiling Config           ( Config.hs, tmp/Config.o )
-    [136 of 285] Compiling Annex.UUID       ( Annex/UUID.hs, tmp/Annex/UUID.o )
-    [137 of 285] Compiling Logs.UUID        ( Logs/UUID.hs, tmp/Logs/UUID.o )
-    [138 of 285] Compiling Backend          ( Backend.hs, tmp/Backend.o )
-    [139 of 285] Compiling Remote.Helper.Hooks ( Remote/Helper/Hooks.hs, tmp/Remote/Helper/Hooks.o )
-    [140 of 285] Compiling Remote.Helper.Encryptable ( Remote/Helper/Encryptable.hs, tmp/Remote/Helper/Encryptable.o )
-    [141 of 285] Compiling Creds            ( Creds.hs, tmp/Creds.o )
-    [142 of 285] Compiling Remote.Helper.AWS ( Remote/Helper/AWS.hs, tmp/Remote/Helper/AWS.o )
-    [143 of 285] Compiling Annex.Queue      ( Annex/Queue.hs, tmp/Annex/Queue.o )
-    [144 of 285] Compiling Annex.Content    ( Annex/Content.hs, tmp/Annex/Content.o )
-    [145 of 285] Compiling Remote.S3        ( Remote/S3.hs, tmp/Remote/S3.o )
-    [146 of 285] Compiling Remote.Directory ( Remote/Directory.hs, tmp/Remote/Directory.o )
-    [147 of 285] Compiling Remote.Rsync     ( Remote/Rsync.hs, tmp/Remote/Rsync.o )
-    [148 of 285] Compiling Remote.Web       ( Remote/Web.hs, tmp/Remote/Web.o )
-    [149 of 285] Compiling Remote.Glacier   ( Remote/Glacier.hs, tmp/Remote/Glacier.o )
-    [150 of 285] Compiling Remote.Hook      ( Remote/Hook.hs, tmp/Remote/Hook.o )
-    [151 of 285] Compiling Upgrade.V2       ( Upgrade/V2.hs, tmp/Upgrade/V2.o )
-    [152 of 285] Compiling Annex.Ssh        ( Annex/Ssh.hs, tmp/Annex/Ssh.o )
-    [153 of 285] Compiling Remote.Helper.Ssh ( Remote/Helper/Ssh.hs, tmp/Remote/Helper/Ssh.o )
-    [154 of 285] Compiling Remote.Bup       ( Remote/Bup.hs, tmp/Remote/Bup.o )
-    [155 of 285] Compiling Annex.Version    ( Annex/Version.hs, tmp/Annex/Version.o )
-    [156 of 285] Compiling Init             ( Init.hs, tmp/Init.o )
-    [157 of 285] Compiling Checks           ( Checks.hs, tmp/Checks.o )
-    [158 of 285] Compiling Remote.Git       ( Remote/Git.hs, tmp/Remote/Git.o )
-    [159 of 285] Compiling Remote.List      ( Remote/List.hs, tmp/Remote/List.o )
-    [160 of 285] Compiling Logs.Trust       ( Logs/Trust.hs, tmp/Logs/Trust.o )
-    [161 of 285] Compiling Remote           ( Remote.hs, tmp/Remote.o )
-    [162 of 285] Compiling Assistant.Alert  ( Assistant/Alert.hs, tmp/Assistant/Alert.o )
-    [163 of 285] Compiling Assistant.Types.DaemonStatus ( Assistant/Types/DaemonStatus.hs, tmp/Assistant/Types/DaemonStatus.o )
-    [164 of 285] Compiling Assistant.Monad  ( Assistant/Monad.hs, tmp/Assistant/Monad.o )
-    [165 of 285] Compiling Assistant.Types.NamedThread ( Assistant/Types/NamedThread.hs, tmp/Assistant/Types/NamedThread.o )
-    [166 of 285] Compiling Assistant.Common ( Assistant/Common.hs, tmp/Assistant/Common.o )
-    [167 of 285] Compiling Assistant.XMPP   ( Assistant/XMPP.hs, tmp/Assistant/XMPP.o )
-    [168 of 285] Compiling Assistant.XMPP.Buddies ( Assistant/XMPP/Buddies.hs, tmp/Assistant/XMPP/Buddies.o )
-    [169 of 285] Compiling Assistant.NetMessager ( Assistant/NetMessager.hs, tmp/Assistant/NetMessager.o )
-    [170 of 285] Compiling Assistant.Pushes ( Assistant/Pushes.hs, tmp/Assistant/Pushes.o )
-    [171 of 285] Compiling Assistant.ScanRemotes ( Assistant/ScanRemotes.hs, tmp/Assistant/ScanRemotes.o )
-    [172 of 285] Compiling Assistant.Install ( Assistant/Install.hs, tmp/Assistant/Install.o )
-    [173 of 285] Compiling Assistant.XMPP.Client ( Assistant/XMPP/Client.hs, tmp/Assistant/XMPP/Client.o )
-    [174 of 285] Compiling Assistant.Commits ( Assistant/Commits.hs, tmp/Assistant/Commits.o )
-    [175 of 285] Compiling Assistant.BranchChange ( Assistant/BranchChange.hs, tmp/Assistant/BranchChange.o )
-    [176 of 285] Compiling Assistant.Changes ( Assistant/Changes.hs, tmp/Assistant/Changes.o )
-    [177 of 285] Compiling Assistant.WebApp.Types ( Assistant/WebApp/Types.hs, tmp/Assistant/WebApp/Types.o )
-    Loading package ghc-prim ... linking ... done.
-    Loading package integer-gmp ... linking ... done.
-    Loading package base ... linking ... done.
-    Loading object (static) Utility/libdiskfree.o ... done
-    Loading object (static) Utility/libmounts.o ... done
-    Loading object (static) Utility/libkqueue.o ... done
-    final link ... done
-    Loading package bytestring-0.9.2.1 ... linking ... done.
-    Loading package zlib-0.5.4.0 ... linking ... done.
-    Loading package array-0.4.0.0 ... linking ... done.
-    Loading package deepseq-1.3.0.0 ... linking ... done.
-    Loading package primitive-0.5.0.1 ... linking ... done.
-    Loading package vector-0.10.0.1 ... linking ... done.
-    Loading package transformers-0.3.0.0 ... linking ... done.
-    Loading package text-0.11.2.3 ... linking ... done.
-    Loading package old-locale-1.0.0.4 ... linking ... done.
-    Loading package time-1.4 ... linking ... done.
-    Loading package random-1.0.1.1 ... linking ... done.
-    Loading package mtl-2.1.2 ... linking ... done.
-    Loading package parsec-3.1.3 ... linking ... done.
-    Loading package pretty-1.1.1.0 ... linking ... done.
-    Loading package filepath-1.3.0.0 ... linking ... done.
-    Loading package old-time-1.1.0.0 ... linking ... done.
-    Loading package unix-2.5.1.1 ... linking ... done.
-    Loading package directory-1.1.0.2 ... linking ... done.
-    Loading package process-1.1.0.1 ... linking ... done.
-    Loading package containers-0.4.2.1 ... linking ... done.
-    Loading package base64-bytestring-1.0.0.0 ... linking ... done.
-    Loading package cereal-0.3.5.2 ... linking ... done.
-    Loading package base-unicode-symbols-0.2.2.4 ... linking ... done.
-    Loading package transformers-base-0.4.1 ... linking ... done.
-    Loading package monad-control-0.3.1.4 ... linking ... done.
-    Loading package lifted-base-0.2 ... linking ... done.
-    Loading package resourcet-0.4.4 ... linking ... done.
-    Loading package semigroups-0.8.4.1 ... linking ... done.
-    Loading package void-0.5.8 ... linking ... done.
-    Loading package conduit-0.5.4.1 ... linking ... done.
-    Loading package entropy-0.2.1 ... linking ... done.
-    Loading package largeword-1.0.3 ... linking ... done.
-    Loading package tagged-0.4.4 ... linking ... done.
-    Loading package crypto-api-0.10.2 ... linking ... done.
-    Loading package crypto-conduit-0.4.1 ... linking ... done.
-    Loading package cryptohash-0.7.8 ... linking ... done.
-    Loading package template-haskell ... linking ... done.
-    Loading package file-embed-0.0.4.6 ... linking ... done.
-    Loading package blaze-builder-0.3.1.0 ... linking ... done.
-    Loading package hashable-1.1.2.5 ... linking ... done.
-    Loading package case-insensitive-0.4.0.3 ... linking ... done.
-    Loading package http-types-0.7.3.0.1 ... linking ... done.
-    Loading package system-filepath-0.4.7 ... linking ... done.
-    Loading package unix-compat-0.4.0.0 ... linking ... done.
-    Loading package network-2.4.0.1 ... linking ... done.
-    Loading package unordered-containers-0.2.2.1 ... linking ... done.
-    Loading package vault-0.2.0.1 ... linking ... done.
-    Loading package wai-1.3.0.1 ... linking ... done.
-    Loading package blaze-markup-0.5.1.1 ... linking ... done.
-    Loading package blaze-html-0.5.1.0 ... linking ... done.
-    Loading package attoparsec-0.10.2.0 ... linking ... done.
-    Loading package http-date-0.0.3 ... linking ... done.
-    Loading package mime-types-0.1.0.0 ... linking ... done.
-    Loading package system-fileio-0.3.10 ... linking ... done.
-    Loading package wai-app-static-1.3.0.4 ... linking ... done.
-    Loading package dlist-0.5 ... linking ... done.
-    Loading package syb-0.3.7 ... linking ... done.
-    Loading package aeson-0.6.0.2 ... linking ... done.
-    Loading package cpu-0.1.1 ... linking ... done.
-    Loading package crypto-pubkey-types-0.2.0 ... linking ... done.
-    Loading package cryptocipher-0.3.6 ... linking ... done.
-    Loading package cprng-aes-0.2.4 ... linking ... done.
-    Loading package skein-0.1.0.10 ... linking ... done.
-    Loading package clientsession-0.8.0.1 ... linking ... done.
-    Loading package data-default-0.5.0 ... linking ... done.
-    Loading package cookie-0.4.0.1 ... linking ... done.
-    Loading package failure-0.2.0.1 ... linking ... done.
-    Loading package date-cache-0.3.0 ... linking ... done.
-    Loading package unix-time-0.1.2 ... linking ... done.
-    Loading package fast-logger-0.3.1 ... linking ... done.
-    Loading package shakespeare-1.0.2 ... linking ... done.
-    Loading package hamlet-1.1.1.1 ... linking ... done.
-    Loading package monad-logger-0.2.1 ... linking ... done.
-    Loading package path-pieces-0.1.2 ... linking ... done.
-    Loading package shakespeare-css-1.0.2 ... linking ... done.
-    Loading package shakespeare-i18n-1.0.0.2 ... linking ... done.
-    Loading package shakespeare-js-1.1.0 ... linking ... done.
-    Loading package ansi-terminal-0.5.5 ... linking ... done.
-    Loading package blaze-builder-conduit-0.5.0.3 ... linking ... done.
-    Loading package stringsearch-0.3.6.4 ... linking ... done.
-    Loading package byteorder-1.0.3 ... linking ... done.
-    Loading package wai-logger-0.3.0 ... linking ... done.
-    Loading package zlib-bindings-0.1.1.2 ... linking ... done.
-    Loading package zlib-conduit-0.5.0.3 ... linking ... done.
-    Loading package wai-extra-1.3.0.4 ... linking ... done.
-    Loading package yesod-routes-1.1.1.1 ... linking ... done.
-    Loading package yesod-core-1.1.6 ... linking ... done.
-    Loading package yesod-static-1.1.1.1 ... linking ... done.
-    [178 of 285] Compiling Assistant.WebApp ( Assistant/WebApp.hs, tmp/Assistant/WebApp.o )
-    Loading package network-conduit-0.6.1.1 ... linking ... done.
-    Loading package safe-0.3.3 ... linking ... done.
-    Loading package simple-sendfile-0.2.8 ... linking ... done.
-    Loading package warp-1.3.5 ... linking ... done.
-    Loading package yaml-0.8.1.1 ... linking ... done.
-    Loading package yesod-default-1.1.2 ... linking ... done.
-    [179 of 285] Compiling Assistant.WebApp.OtherRepos ( Assistant/WebApp/OtherRepos.hs, tmp/Assistant/WebApp/OtherRepos.o )
-    [180 of 285] Compiling Limit            ( Limit.hs, tmp/Limit.o )
-    [181 of 285] Compiling Option           ( Option.hs, tmp/Option.o )
-    [182 of 285] Compiling Seek             ( Seek.hs, tmp/Seek.o )
-    [183 of 285] Compiling Command          ( Command.hs, tmp/Command.o )
-    [184 of 285] Compiling CmdLine          ( CmdLine.hs, tmp/CmdLine.o )
-    [185 of 285] Compiling Command.ConfigList ( Command/ConfigList.hs, tmp/Command/ConfigList.o )
-    [186 of 285] Compiling Command.InAnnex  ( Command/InAnnex.hs, tmp/Command/InAnnex.o )
-    [187 of 285] Compiling Command.DropKey  ( Command/DropKey.hs, tmp/Command/DropKey.o )
-    [188 of 285] Compiling Command.SendKey  ( Command/SendKey.hs, tmp/Command/SendKey.o )
-    [189 of 285] Compiling Command.RecvKey  ( Command/RecvKey.hs, tmp/Command/RecvKey.o )
-    [190 of 285] Compiling Command.TransferInfo ( Command/TransferInfo.hs, tmp/Command/TransferInfo.o )
-    [191 of 285] Compiling Command.Commit   ( Command/Commit.hs, tmp/Command/Commit.o )
-    [192 of 285] Compiling Command.Add      ( Command/Add.hs, tmp/Command/Add.o )
-    [193 of 285] Compiling Command.Unannex  ( Command/Unannex.hs, tmp/Command/Unannex.o )
-    [194 of 285] Compiling Command.FromKey  ( Command/FromKey.hs, tmp/Command/FromKey.o )
-    [195 of 285] Compiling Command.ReKey    ( Command/ReKey.hs, tmp/Command/ReKey.o )
-    [196 of 285] Compiling Command.Fix      ( Command/Fix.hs, tmp/Command/Fix.o )
-    [197 of 285] Compiling Command.Describe ( Command/Describe.hs, tmp/Command/Describe.o )
-    [198 of 285] Compiling Command.InitRemote ( Command/InitRemote.hs, tmp/Command/InitRemote.o )
-    [199 of 285] Compiling Command.Unlock   ( Command/Unlock.hs, tmp/Command/Unlock.o )
-    [200 of 285] Compiling Command.Lock     ( Command/Lock.hs, tmp/Command/Lock.o )
-    [201 of 285] Compiling Command.PreCommit ( Command/PreCommit.hs, tmp/Command/PreCommit.o )
-    [202 of 285] Compiling Command.Log      ( Command/Log.hs, tmp/Command/Log.o )
-    [203 of 285] Compiling Command.Merge    ( Command/Merge.hs, tmp/Command/Merge.o )
-    [204 of 285] Compiling Command.Group    ( Command/Group.hs, tmp/Command/Group.o )
-    [205 of 285] Compiling Command.Ungroup  ( Command/Ungroup.hs, tmp/Command/Ungroup.o )
-    [206 of 285] Compiling Command.Import   ( Command/Import.hs, tmp/Command/Import.o )
-    [207 of 285] Compiling Logs.Unused      ( Logs/Unused.hs, tmp/Logs/Unused.o )
-    [208 of 285] Compiling Command.AddUnused ( Command/AddUnused.hs, tmp/Command/AddUnused.o )
-    [209 of 285] Compiling Command.Find     ( Command/Find.hs, tmp/Command/Find.o )
-    [210 of 285] Compiling Logs.PreferredContent ( Logs/PreferredContent.hs, tmp/Logs/PreferredContent.o )
-    [211 of 285] Compiling Annex.Wanted     ( Annex/Wanted.hs, tmp/Annex/Wanted.o )
-    [212 of 285] Compiling Command.Whereis  ( Command/Whereis.hs, tmp/Command/Whereis.o )
-    [213 of 285] Compiling Command.Trust    ( Command/Trust.hs, tmp/Command/Trust.o )
-    [214 of 285] Compiling Command.Untrust  ( Command/Untrust.hs, tmp/Command/Untrust.o )
-    [215 of 285] Compiling Command.Semitrust ( Command/Semitrust.hs, tmp/Command/Semitrust.o )
-    [216 of 285] Compiling Command.Dead     ( Command/Dead.hs, tmp/Command/Dead.o )
-    [217 of 285] Compiling Command.Vicfg    ( Command/Vicfg.hs, tmp/Command/Vicfg.o )
-    [218 of 285] Compiling Command.Map      ( Command/Map.hs, tmp/Command/Map.o )
-    [219 of 285] Compiling Command.Init     ( Command/Init.hs, tmp/Command/Init.o )
-    [220 of 285] Compiling Command.Uninit   ( Command/Uninit.hs, tmp/Command/Uninit.o )
-    [221 of 285] Compiling Command.Version  ( Command/Version.hs, tmp/Command/Version.o )
-    [222 of 285] Compiling Upgrade.V1       ( Upgrade/V1.hs, tmp/Upgrade/V1.o )
-    [223 of 285] Compiling Upgrade.V0       ( Upgrade/V0.hs, tmp/Upgrade/V0.o )
-    [224 of 285] Compiling Upgrade          ( Upgrade.hs, tmp/Upgrade.o )
-    [225 of 285] Compiling Command.Upgrade  ( Command/Upgrade.hs, tmp/Command/Upgrade.o )
-    [226 of 285] Compiling Command.Drop     ( Command/Drop.hs, tmp/Command/Drop.o )
-    [227 of 285] Compiling Command.Move     ( Command/Move.hs, tmp/Command/Move.o )
-    [228 of 285] Compiling Command.Copy     ( Command/Copy.hs, tmp/Command/Copy.o )
-    [229 of 285] Compiling Command.Get      ( Command/Get.hs, tmp/Command/Get.o )
-    [230 of 285] Compiling Command.TransferKey ( Command/TransferKey.hs, tmp/Command/TransferKey.o )
-    [231 of 285] Compiling Command.DropUnused ( Command/DropUnused.hs, tmp/Command/DropUnused.o )
-    [232 of 285] Compiling Command.Fsck     ( Command/Fsck.hs, tmp/Command/Fsck.o )
-    [233 of 285] Compiling Command.Reinject ( Command/Reinject.hs, tmp/Command/Reinject.o )
-    [234 of 285] Compiling Command.Migrate  ( Command/Migrate.hs, tmp/Command/Migrate.o )
-    [235 of 285] Compiling Command.Unused   ( Command/Unused.hs, tmp/Command/Unused.o )
-    [236 of 285] Compiling Command.Status   ( Command/Status.hs, tmp/Command/Status.o )
-    [237 of 285] Compiling Command.Sync     ( Command/Sync.hs, tmp/Command/Sync.o )
-    [238 of 285] Compiling Command.Help     ( Command/Help.hs, tmp/Command/Help.o )
-    [239 of 285] Compiling Command.AddUrl   ( Command/AddUrl.hs, tmp/Command/AddUrl.o )
-    [240 of 285] Compiling Assistant.DaemonStatus ( Assistant/DaemonStatus.hs, tmp/Assistant/DaemonStatus.o )
-    [241 of 285] Compiling Assistant.Sync   ( Assistant/Sync.hs, tmp/Assistant/Sync.o )
-    [242 of 285] Compiling Assistant.MakeRemote ( Assistant/MakeRemote.hs, tmp/Assistant/MakeRemote.o )
-    [243 of 285] Compiling Assistant.XMPP.Git ( Assistant/XMPP/Git.hs, tmp/Assistant/XMPP/Git.o )
-    [244 of 285] Compiling Command.XMPPGit  ( Command/XMPPGit.hs, tmp/Command/XMPPGit.o )
-    [245 of 285] Compiling Assistant.Threads.NetWatcher ( Assistant/Threads/NetWatcher.hs, tmp/Assistant/Threads/NetWatcher.o )
-    [246 of 285] Compiling Assistant.NamedThread ( Assistant/NamedThread.hs, tmp/Assistant/NamedThread.o )
-    [247 of 285] Compiling Assistant.WebApp.Notifications ( Assistant/WebApp/Notifications.hs, tmp/Assistant/WebApp/Notifications.o )
-    [248 of 285] Compiling Assistant.WebApp.SideBar ( Assistant/WebApp/SideBar.hs, tmp/Assistant/WebApp/SideBar.o )
-    [249 of 285] Compiling Assistant.WebApp.Configurators.Ssh ( Assistant/WebApp/Configurators/Ssh.hs, tmp/Assistant/WebApp/Configurators/Ssh.o )
-    [250 of 285] Compiling Assistant.WebApp.Configurators.S3 ( Assistant/WebApp/Configurators/S3.hs, tmp/Assistant/WebApp/Configurators/S3.o )
-    [251 of 285] Compiling Assistant.WebApp.Documentation ( Assistant/WebApp/Documentation.hs, tmp/Assistant/WebApp/Documentation.o )
-    [252 of 285] Compiling Assistant.WebApp.Configurators.XMPP ( Assistant/WebApp/Configurators/XMPP.hs, tmp/Assistant/WebApp/Configurators/XMPP.o )
-    [253 of 285] Compiling Assistant.Pairing.Network ( Assistant/Pairing/Network.hs, tmp/Assistant/Pairing/Network.o )
-    [254 of 285] Compiling Assistant.Pairing.MakeRemote ( Assistant/Pairing/MakeRemote.hs, tmp/Assistant/Pairing/MakeRemote.o )
-    [255 of 285] Compiling Assistant.TransferQueue ( Assistant/TransferQueue.hs, tmp/Assistant/TransferQueue.o )
-    [256 of 285] Compiling Assistant.Threads.Merger ( Assistant/Threads/Merger.hs, tmp/Assistant/Threads/Merger.o )
-    [257 of 285] Compiling Assistant.TransferSlots ( Assistant/TransferSlots.hs, tmp/Assistant/TransferSlots.o )
-    [258 of 285] Compiling Assistant.Threads.Transferrer ( Assistant/Threads/Transferrer.hs, tmp/Assistant/Threads/Transferrer.o )
-    [259 of 285] Compiling Assistant.Threads.DaemonStatus ( Assistant/Threads/DaemonStatus.hs, tmp/Assistant/Threads/DaemonStatus.o )
-    [260 of 285] Compiling Assistant.Threads.Pusher ( Assistant/Threads/Pusher.hs, tmp/Assistant/Threads/Pusher.o )
-    [261 of 285] Compiling Assistant.Threads.MountWatcher ( Assistant/Threads/MountWatcher.hs, tmp/Assistant/Threads/MountWatcher.o )
-    [262 of 285] Compiling Assistant.Threads.ConfigMonitor ( Assistant/Threads/ConfigMonitor.hs, tmp/Assistant/Threads/ConfigMonitor.o )
-    [263 of 285] Compiling Assistant.Threads.PairListener ( Assistant/Threads/PairListener.hs, tmp/Assistant/Threads/PairListener.o )
-    [264 of 285] Compiling Assistant.Threads.XMPPClient ( Assistant/Threads/XMPPClient.hs, tmp/Assistant/Threads/XMPPClient.o )
-    [265 of 285] Compiling Assistant.WebApp.Utility ( Assistant/WebApp/Utility.hs, tmp/Assistant/WebApp/Utility.o )
-    [266 of 285] Compiling Assistant.WebApp.Configurators.Edit ( Assistant/WebApp/Configurators/Edit.hs, tmp/Assistant/WebApp/Configurators/Edit.o )
-    [267 of 285] Compiling Assistant.WebApp.Configurators.Local ( Assistant/WebApp/Configurators/Local.hs, tmp/Assistant/WebApp/Configurators/Local.o )
-    [268 of 285] Compiling Assistant.WebApp.Configurators ( Assistant/WebApp/Configurators.hs, tmp/Assistant/WebApp/Configurators.o )
-    [269 of 285] Compiling Assistant.WebApp.DashBoard ( Assistant/WebApp/DashBoard.hs, tmp/Assistant/WebApp/DashBoard.o )
-    [270 of 285] Compiling Assistant.WebApp.Configurators.Pairing ( Assistant/WebApp/Configurators/Pairing.hs, tmp/Assistant/WebApp/Configurators/Pairing.o )
-    [271 of 285] Compiling Assistant.Threads.WebApp ( Assistant/Threads/WebApp.hs, tmp/Assistant/Threads/WebApp.o )
-
-    Assistant/Threads/WebApp.hs:47:1: Not in scope: `getAddBoxComR'
-
-    Assistant/Threads/WebApp.hs:47:1: Not in scope: `getEnableWebDAVR'
-    make: *** [git-annex] Error 1
-"""]]
diff --git a/doc/bugs/3.20121112:_build_error_in_assistant/comment_3_b38e40d36bba95b16afbce68e7f25a80._comment b/doc/bugs/3.20121112:_build_error_in_assistant/comment_3_b38e40d36bba95b16afbce68e7f25a80._comment
deleted file mode 100644
index 26bd0194b..000000000
--- a/doc/bugs/3.20121112:_build_error_in_assistant/comment_3_b38e40d36bba95b16afbce68e7f25a80._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.6.49"
- subject="comment 3"
- date="2012-11-25T18:36:49Z"
- content="""
-The webdav library should not be hard to install, but I've gotten the webapp to build without it.
-"""]]
diff --git a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04.mdwn b/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04.mdwn
deleted file mode 100644
index cd0897649..000000000
--- a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04.mdwn
+++ /dev/null
@@ -1,97 +0,0 @@
-What steps will reproduce the problem?
-
-* Start with Ubuntu 12.04
-* sudo apt-get install haskell-platform libgsasl7-dev gsasl g2hs
-* cabal install git-annex --bindir=$HOME/bin
-
-What is the expected output? What do you see instead?
-
-Expected omething like "installation successful"
-
-Actual output, after build notices:
-
-
-Loading package IfElse-0.85 ... linking ... done.
-Loading object (static) dist/build/git-annex/git-annex-tmp/Utility/libdiskfree.o ... done
-Loading object (static) dist/build/git-annex/git-annex-tmp/Utility/libmounts.o ... done
-final link ... done
-[157 of 279] Compiling Assistant.Types.DaemonStatus ( Assistant/Types/DaemonStatus.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/DaemonStatus.o )
-[158 of 279] Compiling Assistant.Monad  ( Assistant/Monad.hs, dist/build/git-annex/git-annex-tmp/Assistant/Monad.o )
-
-Assistant/Monad.hs:86:16:
-    Couldn't match expected type `Assistant a'
-                with actual type `Reader AssistantData a'
-    Expected type: (AssistantData -> a) -> Assistant a
-      Actual type: (AssistantData -> a) -> Reader AssistantData a
-    In the expression: reader
-    In an equation for `getAssistant': getAssistant = reader
-
-Assistant/Monad.hs:93:15:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: st <- reader threadState
-    In the expression:
-      do { st <- reader threadState;
-           liftIO $ runThreadState st a }
-
-Assistant/Monad.hs:99:14:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: d <- reader id
-    In the expression:
-      do { d <- reader id;
-           liftIO $ io $ runAssistant d a }
-
-Assistant/Monad.hs:105:14:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: d <- reader id
-    In the expression:
-      do { d <- reader id;
-           return $ runAssistant d a }
-
-Assistant/Monad.hs:110:14:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: d <- reader id
-    In the expression:
-      do { d <- reader id;
-           return $ \ v -> runAssistant d $ a v }
-
-Assistant/Monad.hs:115:14:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: d <- reader id
-    In the expression:
-      do { d <- reader id;
-           return $ \ v1 v2 -> runAssistant d (a v1 v2) }
-
-Assistant/Monad.hs:120:12:
-    Couldn't match expected type `Assistant a0'
-                with actual type `Reader r0 a1'
-    In the return type of a call of `reader'
-    In the first argument of `(>>=)', namely `reader v'
-    In the expression: reader v >>= liftIO . io
-cabal: Error: some packages failed to install:
-git-annex-3.20121112 failed during the building phase. The exception was:
-ExitFailure 1
-
-
-What version of git-annex are you using? On what operating system?
-
-git annex 3.20121112
-Ubuntu 12.04 (current "long term support", all packages up to date)
-
-Please provide any additional information below.
-
-No idea how important this is for git-annex in general but reporting in case it is. Thank you for working on git annex!
-
-> I was able to reproduce this build error when I force installed
-> an old version of the haskell mtl library. So git-annex needs version
-> 2.1.1 to build, and I have adjusted the build dependencies appropriately.
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_1_ce2efd2196e7682f4cdbabdb0616d449._comment b/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_1_ce2efd2196e7682f4cdbabdb0616d449._comment
deleted file mode 100644
index 49f43149c..000000000
--- a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_1_ce2efd2196e7682f4cdbabdb0616d449._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.252.11.120"
- subject="comment 1"
- date="2012-11-15T17:53:25Z"
- content="""
-I'm not quite sure what's going on here, but my guess is it's an out of date version of the haskell mtl library. Try installing a newer one with 'cabal install mtl'
-"""]]
diff --git a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_2_2a6faf662ebb85a8f1c89adcdfb9adb6._comment b/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_2_2a6faf662ebb85a8f1c89adcdfb9adb6._comment
deleted file mode 100644
index 09e7688fe..000000000
--- a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_2_2a6faf662ebb85a8f1c89adcdfb9adb6._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U"
- nickname="Carlo"
- subject="Not resolved"
- date="2012-11-15T21:44:11Z"
- content="""
-I did as instructed, same behavior though.
-
-I'll wait or keep trying things, whatever works better for you.
-"""]]
diff --git a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_3_37f34baa34068def1adf794d0942e462._comment b/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_3_37f34baa34068def1adf794d0942e462._comment
deleted file mode 100644
index 88cd12df9..000000000
--- a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_3_37f34baa34068def1adf794d0942e462._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.252.11.120"
- subject="comment 3"
- date="2012-11-18T18:13:31Z"
- content="""
-My other guess would be a too old version of ghc.
-"""]]
diff --git a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_4_2f8a859fef9edc8eb93bf1cc74296702._comment b/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_4_2f8a859fef9edc8eb93bf1cc74296702._comment
deleted file mode 100644
index 781259e79..000000000
--- a/doc/bugs/3.20121112_build_fails_on_Ubuntu_12.04/comment_4_2f8a859fef9edc8eb93bf1cc74296702._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlXlJDAF_lXaxbqeBdH4EGj6jsBjjrDODM"
- nickname="Antoine"
- subject="comment 4"
- date="2012-11-21T07:33:43Z"
- content="""
-I have the same problem (sorry, duplicate bug entry) on the same platform. The ghc version is 7.4.1 and is the one distributed by apt repos.
-"""]]
diff --git a/doc/bugs/3.20121113_build_error___39__not_in_scope_getAddBoxComR__39__.mdwn b/doc/bugs/3.20121113_build_error___39__not_in_scope_getAddBoxComR__39__.mdwn
deleted file mode 100644
index 59ca6b51f..000000000
--- a/doc/bugs/3.20121113_build_error___39__not_in_scope_getAddBoxComR__39__.mdwn
+++ /dev/null
@@ -1,33 +0,0 @@
-What steps will reproduce the problem?
-
-Building from latest source, Cabal update, cabal install --only dependencies, cabal configure, Cabal build
-
-What is the expected output? What do you see instead?
-
-Error message from build
-
-...
-
-Loading package DAV-0.2 ... linking ... done.
-
-Loading object (static) dist/build/git-annex/git-annex-tmp/Utility/libdiskfree.o ... done
-
-Loading object (static) dist/build/git-annex/git-annex-tmp/Utility/libmounts.o ... done
-
-final link ... done
-
-
-Assistant/Threads/WebApp.hs:47:1: Not in scope: `getAddBoxComR'
-
-Assistant/Threads/WebApp.hs:47:1: Not in scope: `getEnableWebDAVR'
-
-
-What version of git-annex are you using? On what operating system?
-
-Latest version via git from git-annex.branchable.com
-
-Debian Squeeze (6.0.6)
-
-Please provide any additional information below.
-
-> I noticed this earlier and fixed it. [[done]] --[[Joey]]
diff --git a/doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build.mdwn b/doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build.mdwn
deleted file mode 100644
index 5acc4d569..000000000
--- a/doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build.mdwn
+++ /dev/null
@@ -1,57 +0,0 @@
-What steps will reproduce the problem?
-
-install from a git checkout of tag 4.20130227; error comes up at the "cabal install" stage.
-
-
-What is the expected output? What do you see instead?
-
-Expected successful install; got:
-
-
-    git-annex.branchable.com$ cabal install --bindir=$HOME/bin
-    Resolving dependencies...
-    Configuring testpack-2.1.2...
-    Building testpack-2.1.2...
-    Preprocessing library testpack-2.1.2...
-    [1 of 3] Compiling Test.QuickCheck.Instances ( src/Test/QuickCheck/Instances.hs, dist/build/Test/QuickCheck/Instances.o )
-    [2 of 3] Compiling Test.QuickCheck.Tools ( src/Test/QuickCheck/Tools.hs, dist/build/Test/QuickCheck/Tools.o )
-    
-    src/Test/QuickCheck/Tools.hs:33:9:
-        Warning: Fields of `MkResult' not initialised: abort
-        In the expression:
-          MkResult
-            {ok = Just (expected == actual), expect = True,
-             interrupted = False,
-             reason = "Result: expected "
-                      ++ show expected ++ ", got " ++ show actual,
-             stamp = [], callbacks = []}
-        In an equation for `@=?':
-            expected @=? actual
-              = MkResult
-                  {ok = Just (expected == actual), expect = True,
-                   interrupted = False,
-                   reason = "Result: expected "
-                            ++ show expected ++ ", got " ++ show actual,
-                   stamp = [], callbacks = []}
-    [3 of 3] Compiling Test.HUnit.Tools ( src/Test/HUnit/Tools.hs, dist/build/Test/HUnit/Tools.o )
-    
-    src/Test/HUnit/Tools.hs:131:57:
-        `maxDiscard' is not a (visible) constructor field name
-    
-    src/Test/HUnit/Tools.hs:177:40: Not in scope: `maxDiscard'
-    Failed to install testpack-2.1.2
-    cabal: Error: some packages failed to install:
-    git-annex-4.20130227 depends on testpack-2.1.2 which failed to install.
-    testpack-2.1.2 failed during the building phase. The exception was:
-    ExitFailure 1
-    git-annex.branchable.com$ 
-
-
-What version of git-annex are you using? On what operating system?
-
-trying to compile git checkout of 4.20130227 on OS X Lion.
-
-Please provide any additional information below.
-
-
-> removed dependency on testpack [[done]] --[[Joey]]
diff --git a/doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build/comment_1_b7140e2bf1ea9c73ecc9e214095968e7._comment b/doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build/comment_1_b7140e2bf1ea9c73ecc9e214095968e7._comment
deleted file mode 100644
index b4e0c69f7..000000000
--- a/doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build/comment_1_b7140e2bf1ea9c73ecc9e214095968e7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-02-28T02:12:50Z"
- content="""
-Pass -f-TestSuite to cabal to disable building the test suite.
-"""]]
diff --git a/doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build/comment_2_6be87b2fb2ed828e7b4bf785729e910e._comment b/doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build/comment_2_6be87b2fb2ed828e7b4bf785729e910e._comment
deleted file mode 100644
index d2d1d6bac..000000000
--- a/doc/bugs/4.20130227_won__39__t_build_on_OS_X_Lion__44___because_testpack_won__39__t_build/comment_2_6be87b2fb2ed828e7b4bf785729e910e._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 2"
- date="2013-02-28T03:31:32Z"
- content="""
-that fixed it, thank you!
-
-"""]]
diff --git a/doc/bugs/4.20130601_xmpp_sync_error.mdwn b/doc/bugs/4.20130601_xmpp_sync_error.mdwn
deleted file mode 100644
index 0e1f512d3..000000000
--- a/doc/bugs/4.20130601_xmpp_sync_error.mdwn
+++ /dev/null
@@ -1,125 +0,0 @@
-4.20130601 xmpp sync error.
-
-setup: A debian machine, with indirect fresh annex, android galaxy s3 with a
-fresh direct annex, both running ga-20130601.
-
-steps:
-- Start assistant on both, add jabber account to both.
-- Add box.com account on desktop with no encryption, (now correctly shows up on android, wasn't the case with 20130521).
-- Add hello.txt on desktop repo, filename is now visible on android, but content is not.
-- Add greeting.txt on desktop, nothing shows up on android, content still missing for hello.txt
-- Webapp shows uploading messages, but no errors.
-- Manually checking box.com confirms that files have been uploaded.
-
-debian desktop daemon.log:
-
-    [2013-06-02 17:57:03 CEST] main: starting assistant version 4.20130601
-    (scanning...) [2013-06-02 17:57:03 CEST] Watcher: Performing startup scan
-    (started...) [2013-06-02 17:57:52 CEST] XMPPClient: Pairing with myJabberAccount in progress
-    [2013-06-02 17:57:53 CEST] XMPPReceivePack: Syncing with myJabberAccount 
-    [2013-06-02 17:58:03 CEST] XMPPClient: Pairing with myJabberAccount in progress
-    [2013-06-02 17:58:52 CEST] main: Syncing with box.com 
-    warning: Not updating non-default fetch respec
-	
-	Please update the configuration manually if necessary.
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 17:59:53 CEST] XMPPReceivePack: Syncing with myJabberAccount 
-    [2013-06-02 18:00:02 CEST] Committer: Adding hello.txt
-
-    (testing WebDAV server...)
-    add hello.txt (checksum...) [2013-06-02 18:00:02 CEST] Committer: Committing changes to git
-    [2013-06-02 18:00:02 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    Already up-to-date.
-    [2013-06-02 18:00:03 CEST] Committer: Committing changes to git
-    fatal: The remote end hung up unexpectedly
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 18:00:03 CEST] XMPPSendPack: Syncing with myJabberAccount 
-
-    
-100%          1.0 B/s 0s
-                        
-[2013-06-02 18:00:19 CEST] Transferrer: Uploaded hello.txt
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 18:01:53 CEST] XMPPReceivePack: Syncing with myJabberAccount 
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 18:02:04 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 18:03:53 CEST] XMPPReceivePack: Syncing with myJabberAccount 
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 18:05:10 CEST] Committer: Adding greeting.txt
-    ok
-    (Recording state in git...)
-    (Recording state in git...)
-
-    (Recording state in git...)
-    add greeting.txt (checksum...) [2013-06-02 18:05:10 CEST] Committer: Committing changes to git
-    [2013-06-02 18:05:10 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    Already up-to-date.
-    [2013-06-02 18:05:11 CEST] Committer: Committing changes to git
-
-    
-100%          9.0 B/s 0s
-                        
-[2013-06-02 18:05:24 CEST] Transferrer: Uploaded greeting.txt
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 18:06:13 CEST] XMPPReceivePack: Syncing with myJabberAccount 
-    ok
-    (Recording state in git...)
-    (Recording state in git...)
-
-    (Recording state in git...)
-    fatal: The remote end hung up unexpectedly
-
-Thanks as always.
-
-
-Android daemon.log:
-    [2013-06-02 17:53:07 CEST] main: starting assistant version 4.20130601-g7483ca4
-    (scanning...) [2013-06-02 17:53:07 CEST] Watcher: Performing startup scan
-    (started...) [2013-06-02 17:57:51 CEST] XMPPClient: Pairing with myJabberAccount in progress
-    [2013-06-02 17:57:52 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    Already up-to-date.
-    [2013-06-02 17:58:00 CEST] XMPPSendPack: Unable to download files from your other devices. 
-    [2013-06-02 17:58:00 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    [2013-06-02 17:58:02 CEST] XMPPClient: Pairing with myJabberAccount in progress
-    [2013-06-02 17:58:07 CEST] XMPPSendPack: Unable to download files from your other devices. 
-    [2013-06-02 17:58:07 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    [2013-06-02 17:58:15 CEST] XMPPSendPack: Unable to download files from your other devices. 
-    [2013-06-02 18:00:02 CEST] XMPPReceivePack: Syncing with myJabberAccount 
-    [2013-06-02 18:00:03 CEST] XMPPReceivePack: Unable to download files from your other devices. 
-    [2013-06-02 18:00:04 CEST] XMPPReceivePack: Syncing with myJabberAccount 
-    Merge made by the 'recursive' strategy.
-     hello.txt | 1 +
-     1 file changed, 1 insertion(+)
-     create mode 120000 hello.txt
-    [2013-06-02 18:00:05 CEST] Committer: Committing changes to git
-    [2013-06-02 18:00:06 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    Already up-to-date.
-    [2013-06-02 18:00:14 CEST] XMPPSendPack: Unable to download files from your other devices. 
-    [2013-06-02 18:00:14 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    [2013-06-02 18:00:25 CEST] XMPPSendPack: Unable to download files from your other devices. 
-    [2013-06-02 18:02:03 CEST] Committer: Committing changes to git
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 18:02:04 CEST] XMPPReceivePack: Unable to download files from your other devices. 
-    [2013-06-02 18:02:04 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    [2013-06-02 18:02:04 CEST] XMPPReceivePack: Syncing with myJabberAccount 
-    [2013-06-02 18:02:13 CEST] XMPPSendPack: Unable to download files from your other devices. 
-    [2013-06-02 18:02:15 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    [2013-06-02 18:02:24 CEST] XMPPSendPack: Unable to download files from your other devices. 
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 18:04:04 CEST] XMPPReceivePack: Unable to download files from your other devices. 
-    [2013-06-02 18:05:10 CEST] XMPPReceivePack: Syncing with myJabberAccount 
-    [2013-06-02 18:06:12 CEST] Committer: Committing changes to git
-    [2013-06-02 18:06:13 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    [2013-06-02 18:06:21 CEST] XMPPSendPack: Unable to download files from your other devices. 
-    [2013-06-02 18:06:21 CEST] XMPPSendPack: Syncing with myJabberAccount 
-    [2013-06-02 18:06:29 CEST] XMPPSendPack: Unable to download files from your other devices. 
-    fatal: The remote end hung up unexpectedly
-    [2013-06-02 18:07:10 CEST] XMPPReceivePack: Unable to download files from your other devices. 
-
-
-thanks
-
-> Since this seems clearly a lack of box.com being configured 
-> to be used on the Android, I'm closing the bug: [[done]]. 
-> If I'm wrong, write back, and I'll reopen ;) --[[Joey]]
diff --git a/doc/bugs/4.20130601_xmpp_sync_error/comment_1_5b50d97e44cbd5b31ff24537ec3f8603._comment b/doc/bugs/4.20130601_xmpp_sync_error/comment_1_5b50d97e44cbd5b31ff24537ec3f8603._comment
deleted file mode 100644
index 9c5062780..000000000
--- a/doc/bugs/4.20130601_xmpp_sync_error/comment_1_5b50d97e44cbd5b31ff24537ec3f8603._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-06-11T14:54:56Z"
- content="""
-When you add the box.com repo on the desktop, it will show up on Android pretty quickly thanks to XMPP syncing. But this does not cause the repository to be enabled to be used on Android. You need to select it and enable it there.
-
-I can see this is the case thanks to the log you posted. The Android is constantly complaining:
-
-> XMPPSendPack: Unable to download files from your other devices.
-
-This message should also be appearing in an alert message in the sidebar of the webapp.
-"""]]
diff --git a/doc/bugs/400_mode_leakage.mdwn b/doc/bugs/400_mode_leakage.mdwn
deleted file mode 100644
index 63f0fb11d..000000000
--- a/doc/bugs/400_mode_leakage.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-git-annex tends to preserve files that are added to an annex with
-a mode such as 400. (Happens to me sometimes with email attachments.) 
-As these files are rsynced around, and end up on eg, a
-publically visible repo with a webserver frontend, or a repo that is
-acessible to a whole group of users, they will not be readable. 
-
-I think it would make sense for git-annex to normalize file permissions
-when adding them. Of course, there's some tension here with generally
-storing file metadata when possible. Perhaps the normalization should only
-ensure that group and other have read access?
-
-(Security: We can assume that a repo that is not intended to be public is
-in a 700 directory. And since git-annex cannot preserve file modes when
-files transit through a special remote, using modes to limit access to
-individual files is not wise.)
-
---[[Joey]]
-
-> Revisiting this, git-annex already honors core.sharedrepository settings,
-> so I just needed to set it to `world` to allow everyone to read.
-> 
-> There was a code path in direct mode where that didn't work; fixed that.
-> 
-> [[done]]
-> --[[Joey]] 
diff --git a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop.mdwn b/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop.mdwn
deleted file mode 100644
index c5bff196e..000000000
--- a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-What steps will reproduce the problem?
-
-Mount USB drive formatted as FAT
-Make directory for repository in it.
-Set up another repository and choose to sync it with the existing one.
-
-What is the expected output? What do you see instead?
-The files should transfer from the main repository to the directory on the USB drive.
-This happens, but afterwards a new sync happens from the USB drive repository back to the other existing repositories, because the file date of all the files on the USB drive has been set to today.
-Further, git seemed to keep the USB key locked so umount was impossible until after killing it.
-
-What version of git-annex are you using? On what operating system?
-4.20130405
-Linux
-
-Please provide any additional information below.
-
-
-> Reproduced the core bug, which is that the assistant saw symlink standin
-> files as new files, and annexed them. Now it doesn't, and I have
-> it running on FAT with no trouble; can even rename symlink standin files
-> and it commits symlink changes. Calling this [[done]]. --[[Joey]]
diff --git a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_1_81839a6de7450734ee75b51e47a0898e._comment b/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_1_81839a6de7450734ee75b51e47a0898e._comment
deleted file mode 100644
index c90d67cc1..000000000
--- a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_1_81839a6de7450734ee75b51e47a0898e._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-09T17:33:06Z"
- content="""
-You seem to have told the assistant you want it to directly manage a git repository on the USB drive. So it keeps a git-annex assistant daemon running on that drive. Which yes, makes it impossible to unmount it.
-
-So, don't do that. Make the repository on the drive by selecting Add Repository -> Removable drive, which creates a bare repository and never runs the assistant in it.
-"""]]
diff --git a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_2_907ce31a31df94984c2bd7aaafe5b10b._comment b/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_2_907ce31a31df94984c2bd7aaafe5b10b._comment
deleted file mode 100644
index 20de13ade..000000000
--- a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_2_907ce31a31df94984c2bd7aaafe5b10b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/bBy7WkgQicYHIiiyj.Vm0TcMbxi2quzbPFef#6f9f7"
- nickname="Frederik Vanrenterghem"
- subject="comment 2"
- date="2013-04-10T03:25:40Z"
- content="""
-Thanks Joey, I will give that a try later today. How about the file last modified dates all having changed to the current date though - is that something that could have been avoided?
-"""]]
diff --git a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_3_d8a86ae0ae5fa1f91e0b40b8b2ba0406._comment b/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_3_d8a86ae0ae5fa1f91e0b40b8b2ba0406._comment
deleted file mode 100644
index 76f2b12a1..000000000
--- a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_3_d8a86ae0ae5fa1f91e0b40b8b2ba0406._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/bBy7WkgQicYHIiiyj.Vm0TcMbxi2quzbPFef#6f9f7"
- nickname="Frederik Vanrenterghem"
- subject="comment 3"
- date="2013-04-10T13:37:38Z"
- content="""
-The drawback of addding the extra repository as suggested is that the files can't be accessed on the USB drive when plugged into a Windows PC as far as I can tell,since they are stored in git. Isn't this a use case in scope of the assistant?
-
-Note that the setup I created yesterday effectively has resulted in all files being lost, also in the main repository. This because the files on the USB drive became links to their equivalent in the git directory on the usb drive, but they got transferred back to the laptop as 1kb files.
-"""]]
diff --git a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_4_1f08fd5dd4f5d8723c2b5391cc3b60f9._comment b/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_4_1f08fd5dd4f5d8723c2b5391cc3b60f9._comment
deleted file mode 100644
index 6c5d259f2..000000000
--- a/doc/bugs/Add_another_repository_on_USB_drive_causes_sync_loop/comment_4_1f08fd5dd4f5d8723c2b5391cc3b60f9._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 4"
- date="2013-04-10T22:58:07Z"
- content="""
-Accessing files from USB on Windows is in scope, but it needs a windows port. Then you could just run git-annex on windows and it would pull the files from USB into your main repository, like the assistant does now on Mac and Linux.
-
------
-
-I suspect you don't have actual irreparable data loss. Or, perhaps not. If you really need to get that data back I can try to help.
-
-As I understand what happened, files were sent over the the USB drive, and you had another assistant running in that repository. It seems to have done something wrong, and taken the 1-line standin files that git uses to represent symbolic links when on a FAT filesystem, and committed those to the annex. These new files were then sent back to your original repository.
-
-So, if you look at `git log --status`, you'll find a commit that touched every file, and if you `git revert` that commit, the tree would be returned to how it was before that rogue assistant chomped on it. The actual contents of the files, which is stored in the annex, will probably then have not been lost. Although if you're using direct mode for your repository it is possible to lose annexed content if a file is overrwitten by a newer version, so I can't guarantee that 100%, like I could for indirect mode.
-
-Anyway, I need to fix this misbehavior of the assistant when run on a FAT filesystem, it seems. 
-
-------
-
-I have reproduced the bug that the assistant, in a FAT filesystem, commits symlink standin files. It seems to do this at least at startup, to all such standin files. Oddly, I did not see this behavior before when using the assistant on FAT filesystems on Android.
-"""]]
diff --git a/doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one.mdwn b/doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one.mdwn
deleted file mode 100644
index c2e05dee0..000000000
--- a/doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-**What steps will reproduce the problem?**
-
-I generated repositories on two machines an then tried to sync them via ssh (by adding a "Remote server") but I ended up with a third (bare) repository next to my data on the remote server.
-
-**What is the expected output? What do you see instead?**
-
-The assistant should recognize the existing repository (especially the .git directory) and then start syncing only the needed files.
-
-**What version of git-annex are you using? On what operating system?**
-
-git-annex version: 4.20130324, Ubuntu 11.04
-
-**Please provide any additional information below.**
-
-[[!tag /design/assistant]]
-
-> I have made it check for the .git directory and reuse the existing
-> repository if it's there. [[done]] --[[Joey]]
-> 
-> (The comment about `git-annex-shell` is incorrect; it has nothing
-> to do with this.)
diff --git a/doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one/comment_1_cb781d34889d583663e855c4074f8e0e._comment b/doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one/comment_1_cb781d34889d583663e855c4074f8e0e._comment
deleted file mode 100644
index 1e36e21ba..000000000
--- a/doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one/comment_1_cb781d34889d583663e855c4074f8e0e._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 1"
- date="2013-04-11T13:55:29Z"
- content="""
-From what I understand, this happens when the assistant can't use git-annex-shell on the remote SSH server, as I have the same problem. The workaround I used was adding the remote SSH manually:
-
-    git remote add ssh://server/path/to/repo
-
-which the assistant recognises and uses properly.
-
-The actual fix is, obviously, get git-annex-shell working. A likely reason it is missing is that because the SSH connection the assistant uses is not interactive, git-annex-shell is not in $PATH.
-
-I think Joey's recommendation ([per our discussion here](http://git-annex.branchable.com/bugs/Can__39__t_access_files_from___39__Removable_drive__39___repo_even_if_set_as_client/#comment-8234271642283b51e173e20e217de3fc)) was to use local or XMPP pairing instead.
-"""]]
diff --git a/doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one/comment_2_c0c87957d7c7a09664e60571a2ca0e8c._comment b/doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one/comment_2_c0c87957d7c7a09664e60571a2ca0e8c._comment
deleted file mode 100644
index 881980240..000000000
--- a/doc/bugs/Adding_a_repository_as_a___34__remote_server__34___creates_a_bare_repository_next_to_the_existing_one/comment_2_c0c87957d7c7a09664e60571a2ca0e8c._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl99Gxq3NPNvwZHp3PDufaknQH4rZb_KKY"
- nickname="Florian"
- subject="comment 2"
- date="2013-04-12T15:21:11Z"
- content="""
-I found a different workaround. I added the remote repo via the \"remote server\" option. After that I shut down the local assistant and deleted all the new bare repository stuff on the remote machine. After restarting the local assistant syncing worked as expected and no new bare repository was initialized.
-
-On an other machine I was able to transform the bare repository into a non-bare one and check out the files. After that syncing also still worked.
-
-The remote git-annex-shell is working well. I already described this in an other bug report, where I always ended up in it while trying to log into the machine manually.
-"""]]
diff --git a/doc/bugs/Adding_box.com_remote_on_Android_fails_for_me.mdwn b/doc/bugs/Adding_box.com_remote_on_Android_fails_for_me.mdwn
deleted file mode 100644
index 62c6a3796..000000000
--- a/doc/bugs/Adding_box.com_remote_on_Android_fails_for_me.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-### Please describe the problem.
-
-After submitting the form in the webapp for adding a box.com remote, I get:
-
-   Internal Server Error - WEBDAV failed to write file: "Unauthorized": user error
-
-### What steps will reproduce the problem?
-
-Fill in the box.com add remote form. Username=username, password=password, "share..."=checked, directory=annex, Encryption="Encrypt all data" and hit the "Add repository" button.
-
-### What version of git-annex are you using? On what operating system?
-
-  git-annex version 4.20130513-g5185533 on Android 4.2.2
-
-### Please provide any additional information below.
-
-Didn't find a .git/annex/debug.log
-
-> This error seems entirely consistent with you entering the wrong password.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Adding_box.com_remote_on_Android_fails_for_me/comment_1_0303ce880415d7e043533551c2b24694._comment b/doc/bugs/Adding_box.com_remote_on_Android_fails_for_me/comment_1_0303ce880415d7e043533551c2b24694._comment
deleted file mode 100644
index a55f4eeb2..000000000
--- a/doc/bugs/Adding_box.com_remote_on_Android_fails_for_me/comment_1_0303ce880415d7e043533551c2b24694._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmmLfBDEDFfEOba8Ra46nsnTmoNHFsLObo"
- nickname="Brian"
- subject="It worked my second try"
- date="2013-05-14T00:39:08Z"
- content="""
-I enabled debug logging and tried again and this time the remote was successfully added! Maybe the first time I mistyped my password?
-
-Either way, it is working now and I created a file in my annex directory and the assistant successfully synced it to my box.com repo.
-"""]]
diff --git a/doc/bugs/Adding_git_ssh_remote_fails.mdwn b/doc/bugs/Adding_git_ssh_remote_fails.mdwn
deleted file mode 100644
index 392dc127b..000000000
--- a/doc/bugs/Adding_git_ssh_remote_fails.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-### Please describe the problem.
-
-While trying to add a ssh remote, the webapp promts the error:
-
-    Reinitialized existing shared Git repository in /home/chris/annex-test/
-    git-annex: please specify a description of this repository
-
-resp.
-
-    Initialized empty shared Git repository in /home/chris/annex-test-2/
-    git-annex: please specify a description of this repository
-
-### What steps will reproduce the problem?
-
-Adding a ssh git remote.
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130704-gaf18656 linux-amd64 and android
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-only successful ssh key generation in daemon.log
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; bad installation. --[[Joey]]
diff --git a/doc/bugs/Adding_git_ssh_remote_fails/comment_1_05c0bd9ac7c6f0045217fd72fc1f0a1b._comment b/doc/bugs/Adding_git_ssh_remote_fails/comment_1_05c0bd9ac7c6f0045217fd72fc1f0a1b._comment
deleted file mode 100644
index d976fcbb1..000000000
--- a/doc/bugs/Adding_git_ssh_remote_fails/comment_1_05c0bd9ac7c6f0045217fd72fc1f0a1b._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 1"
- date="2013-07-05T16:04:04Z"
- content="""
-Are you doing this on Android?
-
-Can you please enable debug logging, and post a debug log when this happens?
-"""]]
diff --git a/doc/bugs/Adding_git_ssh_remote_fails/comment_2_df05456cafdd89e8ceea830199f42d45._comment b/doc/bugs/Adding_git_ssh_remote_fails/comment_2_df05456cafdd89e8ceea830199f42d45._comment
deleted file mode 100644
index 89e9523b3..000000000
--- a/doc/bugs/Adding_git_ssh_remote_fails/comment_2_df05456cafdd89e8ceea830199f42d45._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="Chris"
- ip="89.14.216.1"
- subject="Reason found"
- date="2013-07-07T21:21:49Z"
- content="""
-I found the reason for the behavior. On the server, for non-interactive login shells, the right path to git-annex was not set and an old version that was installed by the OS was used instead. I've put the \"export $PATH\" at the right position in .bashrc and now it works. Sorry for the noise.
-
-Best regards, Chris
-"""]]
diff --git a/doc/bugs/Adding_second_remote_repository_over_ssh_fails.mdwn b/doc/bugs/Adding_second_remote_repository_over_ssh_fails.mdwn
deleted file mode 100644
index abb5226be..000000000
--- a/doc/bugs/Adding_second_remote_repository_over_ssh_fails.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-What steps will reproduce the problem?
-
-Create a local and "remote server" repository
-
-Create another local repositorty and keep it seperate from the first one. Fails while creating second repository on the remote.
-
-What is the expected output? What do you see instead?
-
-Expected to get two seperate repositories on the client and server. Only first one works.
-
-Got an error:
-
-    Failed to make repository
-
-    Something went wrong setting up the repository on the remote server.
-
-    Transcript: fatal: unrecognized command 'sh -c 'mkdir -p '"'"'second'"'"'&&cd '"'"'second'"'"'&&git init --bare --shared&&git annex init&&mkdir -p ~/.ssh&&if [ ! -e ~/.ssh/git-annex-shell ]; then (echo '"'"'#!/bin/sh'"'"';echo '"'"'set -e'"'"';echo '"'"'if [ "x$SSH_ORIGINAL_COMMAND" != "x" ]; then'"'"';echo '"'"'exec git-annex-shell -c "$SSH_ORIGINAL_COMMAND"'"'"';echo '"'"'else'"'"';echo '"'"'exec git-annex-shell -c "$@"'"'"';echo '"'"'fi'"'"') > ~/.ssh/git-annex-shell; fi&&chmod 700 ~/.ssh/git-annex-shell&&touch ~/.ssh/authorized_keys&&chmod 600 ~/.ssh/authorized_keys&&echo '"'"'command="GIT_ANNEX_SHELL_DIRECTORY='"'"'"'"'"'"'"'"'second'"'"'"'"'"'"'"'"' ~/.ssh/git-annex-shell",no-agent-forwarding,no-port-forwarding,no-X11-forwarding ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCvoTn+XBdlw/mQlu+NScAeuddUJqJaVXH6KUsO09OddnUvzv4W185ezbAjXfWDgN7ou0Q0xQzwiCzdoSl7T3USJQ1ywTG5Xt2sBV3RIqxyReNA7Nz0yhwWhZBJcFzof34ezNIsi9NVgEJcK2JEs2XqhO5wK5nxEDeays7ti2bqY6V21iOWSy9hlzjD4VTWTEFxQkDp4BCzDpPN934ztOtInwI8ayiTRJZlNQ+ej/AaA+/zOBWNvIFc/96iuMLKY6lLFThw1jNj5r5N7yPaysLdnwTJ3irtCzDygCpD4mau4frrOPvG90ZdcdrQSfIjRtM9nPZ5jIpohfvz0dIfgNFz marvin@marvin-U-100 '"'"' >>~/.ssh/authorized_keys'' git-annex-shell: git-shell failed
-
-
-What version of git-annex are you using? On what operating system?
-
-4.20130413-g5747bf4 ubuntu 12.10 local
-
-3.20120629 debian wheezy remote (also tried 4.20130413-g5747bf4)
-
-Please provide any additional information below.
-
-> This bug would appear to be the same as a bug I fixed today.
-> 
-> Except this last bit:
-
-**Also noticed if a user has no full name set in unix account, creating
-remote repository always fails**
-
-> So, I'm going to repurpose this bug to track that problem. --[[Joey]]
-
-[[!meta title="assistant can fail to make git repository if remote server is lacking GECOS"]]
-
->> [[done]]; git-annex always checks for missing gecos and enables
->> a workaround. This does mean the server needs to be upgraded in order
->> for the fix to work. --[[Joey]]
diff --git a/doc/bugs/Adding_second_remote_repository_over_ssh_fails/comment_1_308d5f517bf00c8edc53db438de52355._comment b/doc/bugs/Adding_second_remote_repository_over_ssh_fails/comment_1_308d5f517bf00c8edc53db438de52355._comment
deleted file mode 100644
index 6fcf8de7b..000000000
--- a/doc/bugs/Adding_second_remote_repository_over_ssh_fails/comment_1_308d5f517bf00c8edc53db438de52355._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="marvin"
- ip="91.152.75.65"
- subject="comment 1"
- date="2013-04-17T09:11:08Z"
- content="""
-Here is the message from the nameless error:
-
-    Failed to make repository
-
-    Something went wrong setting up the repository on the remote server.
-
-    Transcript: Initialized empty shared Git repository in /home/marvin/first/ init *** Please tell me who you are. Run git config --global user.email \"you@example.com\" git config --global user.name \"Your Name\" to set your account's default identity. Omit --global to set the identity only in this repository. fatal: empty ident <marvin@testy.mydomain.fi > not allowed git-annex: user error (git [\"--git-dir=/home/marvin/first\",\"commit-tree\",\"4b825dc642cb6eb9a060e54bf8d69288fbee4904\"] exited 128) failed git-annex: init: 1 failed
-"""]]
diff --git a/doc/bugs/Adding_unencrypted_repo_on_drive_in_webapp_gives_internal_server_error__.mdwn b/doc/bugs/Adding_unencrypted_repo_on_drive_in_webapp_gives_internal_server_error__.mdwn
deleted file mode 100644
index ab98c631e..000000000
--- a/doc/bugs/Adding_unencrypted_repo_on_drive_in_webapp_gives_internal_server_error__.mdwn
+++ /dev/null
@@ -1,69 +0,0 @@
-### Please describe the problem.
-
-"Internal Server Error This git repository is encrypted with a GnuPG key that you do not have" after having asked *not* to use encryption.
-
-### What steps will reproduce the problem?
-
-Here's what I did:
-
-On Ubuntu 10.4, install git-annex according to http://git-annex.branchable.com/install/Ubuntu/ then:
-
-$ git-annex webapp
-
-Create repo at suggested path Desktop/annex/.
-Add a file to that dir. Create subdir, move file there.
-Select "Add another repository" in webapp, "Removable drive", select external usb drive, leave suggested path "annex", "Use this drive", "Do not encrypt repository".
-
--> shows "Internal Server Error
-This git repository is encrypted with a GnuPG key that you do not have.
-git-annex version 4.20131002"
-
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version 4.20131002, Ubuntu 12.04.3 LTS
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is wit[2013-10-19 00:33:55 BST] main: starting assistant version 4.20131002
-(Recording state in git...)
-(scanning...) [2013-10-19 00:33:55 BST] Watcher: Performing startup scan
-(started...) 
-
-  The installed version of git is too old for .gitignores to be honored by git-annex.
-[2013-10-19 00:35:56 BST] Committer: Adding Git Annex..ation.odt
-add Git Annex installation.odt (checksum...) [2013-10-19 00:35:57 BST] Committer: Committing changes to git
-[2013-10-19 00:37:38 BST] Committer: Adding Git Annex..ation.odt
-[2013-10-19 00:37:38 BST] Committer: Committing changes to git
-git: 'remote-gcrypt' is not a git command. See 'git --help'.
-ok
-(Recording state in git...)
-(Recording state in git...)
-ok
-(Recording state in git...)
-(Recording state in git...)
-19/Oct/2013:00:38:54 +0100 [Error#yesod-core] This git repository is encrypted with a GnuPG key that you do not have. @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5)
-git: 'remote-gcrypt' is not a git command. See 'git --help'.
-19/Oct/2013:00:39:09 +0100 [Error#yesod-core] This git repository is encrypted with a GnuPG key that you do not have. @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5)
-.........+++++
-
-Not enough random bytes available.  Please do some other work to give
-the OS a chance to collect more entropy!  (Need 66 more bytes)
-.............+++++
-gpg: key E0424680 marked as ultimately trusted
-git: 'remote-gcrypt' is not a git command. See 'git --help'.
-19/Oct/2013:00:41:19 +0100 [Error#yesod-core] This git repository is encrypted with a GnuPG key that you do not have. @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5)
-git: 'remote-gcrypt' is not a git command. See 'git --help'.
-19/Oct/2013:00:54:33 +0100 [Error#yesod-core] This git repository is encrypted with a GnuPG key that you do not have. @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5)
-h the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-I'm not at my computer, will check upstream Git later. Sorry if this has been reported before.
-
-> This only occurred when git-remote-gcrypt was not installed.
-> I've fixed the bug. [[done]] --[[Joey]]
diff --git a/doc/bugs/Addurl_with_quvi_not_working.mdwn b/doc/bugs/Addurl_with_quvi_not_working.mdwn
deleted file mode 100644
index 279176bbd..000000000
--- a/doc/bugs/Addurl_with_quvi_not_working.mdwn
+++ /dev/null
@@ -1,74 +0,0 @@
-### Please describe the problem.
-
-When adding a video with "addurl", git-annex claims that quvi does not know how to download the url. When using "quvi get" on the same url the video gets downloaded.
-
-This seems to be independent of the video hosting site and occured on all I tested.
-
-### What steps will reproduce the problem?
-
-Download a video with
-
-    git annex addurl "[URL]"
-
-and do the same with
-
-    quvi get "[URL]"
-
-.
-
-
-### What version of git-annex are you using? On what operating system?
-
-OS: Archlinux, fully updated
-
-    git-annex version: 5.20131118-gc7e5cde
-    build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 5
-    upgrade supported from repository versions: 0 1 2 4
-
-
-### Please provide any additional information below.
-
-# Git-annex:
-
-    user@asus aaa [master] % git annex addurl "https://www.youtube.com/watch?v=TUrQsK5ouSg"
-    quvi v0.9.5
-      built on 2013-11-12 17:02:06 +0000 for x86_64-unknown-linux-gnu
-        with gcc, -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4
-      configuration: --prefix=/usr
-    libquvi v0.9.4
-      built on 2013-11-12 16:58:23 +0000 for x86_64-unknown-linux-gnu
-        with gcc, -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4
-      configuration: --prefix=/usr
-    libquvi-scripts v0.9.20131104
-      configuration: --prefix=/usr --with-nsfw --with-geoblocked
-    
-    Copyright (C) 2012,2013  Toni Gundogdu <legatvs@gmail.com>
-    quvi comes with ABSOLUTELY NO WARRANTY.  You may redistribute copies of
-    quvi under the terms of the GNU Affero General Public License version 3
-    or later. For more information, see <http://www.gnu.org/licenses/agpl.html>.
-    
-    To contact the developers, please mail to <quvi-devel@lists.sourceforge.net>
-    
-    Copyright (C) 2012,2013  Toni Gundogdu <legatvs@gmail.com>
-    quvi comes with ABSOLUTELY NO WARRANTY.  You may redistribute copies of
-    quvi under the terms of the GNU Affero General Public License version 3
-    or later. For more information, see <http://www.gnu.org/licenses/agpl.html>.
-    
-    To contact the developers, please mail to <quvi-devel@lists.sourceforge.net>
-    git-annex: quvi does not know how to download url https://www.youtube.com/watch?v=TUrQsK5ouSg
-
-# Quvi:
-
-    user@asus aaa [master] % quvi get "https://www.youtube.com/watch?v=TUrQsK5ouSg"
-    file: GitAnnex Assistant Hak5 14223.mp4  [media]                                                       
-      content length: 162.2Mi  content type: video/mp4  mode: resume
-    copy: --=-  100%   488.9Ki/s  00:05:37
-
-> git annex 5.20131127 is the first to support quvi 0.9. 
-> (And only if built on a system with that version of quvi installed).
-> Upgrade. [[done]] --[[Joey]]
diff --git a/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote.mdwn b/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote.mdwn
deleted file mode 100644
index 9c6a0c9fc..000000000
--- a/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-This follows up to the [comment made by
-Laszlo](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/#comment-f26d3b6b45bb66601ecfaa883ace161c)
-on the [recent
-poll](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/).
-
-I too need to be able to select the directory on the remote drive that the
-annex will be synced to.
-
-If I just add a remote drive via the web app, it syncs the repository to
-`/mnt/usb/annex`, and it looks like it just creates a bare repository in
-that folder. I need the repository to be synced to something like
-`/mnt/usb/subfolder/myspecifiedfoldername` and I need that remote to be a
-full repository.
-
-My use case is that I use the USB drive to keep annexes in sync between two
-computers. I have multiple annexes that need to be synced between the two
-computers, and none of them are in a directory called `annex`. I also need
-to be able to plug the drive into other computers and access the files
-directly, without doing a `git clone` or anything like that. I have all of
-this setup and working fine with just plain old git annex, but the web app
-does not seem to support creating new repositories with this workflow.
-
-I think it makes a lot of sense to allow the web application to add a new
-remote that is simply a directory. People like me could specify the path of
-the directory to be on the mounted USB drive. Others may want to add a
-remote that is a mounted network share or something like that.
-
-> [[done]], the webapp now has a "Add another repository" option,
-> and you can just enter the path to whatever place you like inside a USB
-> drive.  --[[Joey]]
diff --git a/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote/comment_1_13ecedfbb34c3564af3a790b8bf0f591._comment b/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote/comment_1_13ecedfbb34c3564af3a790b8bf0f591._comment
deleted file mode 100644
index cf13d97c1..000000000
--- a/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote/comment_1_13ecedfbb34c3564af3a790b8bf0f591._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmYiJgOvC4IDYkr2KIjMlfVD9r_1Sij_jY"
- nickname="Douglas"
- subject="Not limited to usb drives"
- date="2013-01-23T02:08:38Z"
- content="""
-I have a machine with multiple hard drives. One of these drives is strictly used for backups, ie /dev/sdc holds /home and /dev/sdd is a giant drive that i keep a backup of important items that I would like to have readily available in case of a drive failure.  Somewhere in \"add more repositories\" the assistant should be able to create a copy of the repository on the same computer. When I saw the add a removable drive feature i thought it might work but it will not let me select a specific directory. 
-
-Current setup, I have the assistant managing a group of repos:
-
-    /home/me/Videos.Annex
-    /home/me/Photos.Annex
-    /home/me/Documents.Annex
-
-
-I access these files via /home/me/DIRECTORY. However in case my /home drive breaks I would like to know that git-annex was faithfully keeping a copy in /mnt/bigdrive as well as on me@someothermachine. I would like to use the assistant to manage: 
-
-    /mnt/bigdrive/Annex.Backups/Videos.Annex
-    /mnt/bigdrive/Annex.Backups/Photos.Annex
-    /mnt/bigdrive/Annex.Backups/Documents.Annex
-
-
-
-
-"""]]
diff --git a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__.mdwn b/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__.mdwn
deleted file mode 100644
index d7035432a..000000000
--- a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-### Please describe the problem.
-On Andorid adding a respository on box.net account to an exisiting repository does not work. The following error message is displayed:
-
-
-Internal Server Error
-WebDAV failed to write file: /etc/ssl/certs/: getDirectoryContents: does not exist (No such file or directory): user error
-
-The directory does not exist, indeed.
-
-### What steps will reproduce the problem?
-Add a repository on a Box.net server to an existing repository from the webapp (encrypted and shared with other devices and friends). The error appears after clicking on "Add repository"
-
-
-### What version of git-annex are you using? On what operating system?
-
-git annex 5.20140128-g32f1f68 on Android 4.1.2 (Samsung GTN8010)
-Build flags: Assistant Webapp S3 WebDAV Inotify XMPP DNS Feeds Quvi TDFA CryptoHash
-
-> Cooincidentially I noticed I'd dropped the patch that fixes that on
-> Android, and have been in the process of rebuilding the Android
-> autobuilder with it today. That build has finished now. [[done]]
-> --[[Joey]] 
diff --git a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_1_91787407727f7ed833d5970d3226d0cb._comment b/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_1_91787407727f7ed833d5970d3226d0cb._comment
deleted file mode 100644
index 45d5da95e..000000000
--- a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_1_91787407727f7ed833d5970d3226d0cb._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkI9pq1WH6MWeExXHVQVEsniT3DdFv4AB8"
- nickname="Roberto"
- subject="problem still persists"
- date="2014-02-10T22:55:33Z"
- content="""
-I'm trying right now the latest build (5.20140210-gd99db49) but the problem persists. Am I missing something? 
-"""]]
diff --git a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_2_f4c52fe33e9c4c107c2469fabb0c6826._comment b/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_2_f4c52fe33e9c4c107c2469fabb0c6826._comment
deleted file mode 100644
index d566170c9..000000000
--- a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_2_f4c52fe33e9c4c107c2469fabb0c6826._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.172"
- subject="comment 2"
- date="2014-02-10T23:25:42Z"
- content="""
-Hmm, I've verified that the certificate library I built for android uses the right path. But for some reason that path is not showing up in the android executable.
-
-I think perhaps things have changed and a different library is now being used! Probably <http://hackage.haskell.org/package/x509-system>
-"""]]
diff --git a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_3_20c1f9399321dd85cb584b8845140b1d._comment b/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_3_20c1f9399321dd85cb584b8845140b1d._comment
deleted file mode 100644
index d728e35a8..000000000
--- a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_3_20c1f9399321dd85cb584b8845140b1d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.172"
- subject="finished rebuilding everything"
- date="2014-02-11T17:48:07Z"
- content="""
-All android builds are updated. Verified the path this time in the binary.
-"""]]
diff --git a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_4_d92c30061e087878a2462b5a2e495346._comment b/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_4_d92c30061e087878a2462b5a2e495346._comment
deleted file mode 100644
index 299364913..000000000
--- a/doc/bugs/Android:_Adding_Repository_on_Box.net_fails_with___34__Internal_Server_Error__34__/comment_4_d92c30061e087878a2462b5a2e495346._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkI9pq1WH6MWeExXHVQVEsniT3DdFv4AB8"
- nickname="Roberto"
- subject="fix confirmed"
- date="2014-02-12T12:05:42Z"
- content="""
-I can confirm the problem is now fixed.
-
-Unfortunately a new problem has emerged with gpg that might be related to other open issues. I will try to investigate it further before opening a new ticket.
-
-By the way thank you very much for your great work. I'm eager to see the new metadata framework in place. It sounds extremely interesting!
-"""]]
diff --git a/doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing.mdwn b/doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing.mdwn
deleted file mode 100644
index 147804d92..000000000
--- a/doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-### Please describe the problem.
-
-I expected at least a listing of files... ideally with basic navigation and options to select/deselect to be fetched/dropped
-
-### What steps will reproduce the problem?
-
-Click on "Files" link near "Repository: " on top right of the Dashboard
-
-### What version of git-annex are you using? On what operating system?
-
-last Android build from Nov 18 2013
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> Removed the UI element unless and until a file browser is available on
-> Android. [[done]] --[[Joey]]
diff --git a/doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing/comment_1_a9b03d4f4760fea2754a4dc93547f0a3._comment b/doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing/comment_1_a9b03d4f4760fea2754a4dc93547f0a3._comment
deleted file mode 100644
index 69cfaefd2..000000000
--- a/doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing/comment_1_a9b03d4f4760fea2754a4dc93547f0a3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 1"
- date="2013-11-26T16:12:42Z"
- content="""
-git-annex does not have a built-in file manager. I don't know how to get android to display a file manager; if there's a command that can be run, or an intent that can be used to get one, git-annex could do that. But I don't think android typically includes a file manager, I have only seen them as OEM addons on some of the more laptop form factor android devices.
-
-I think that the android web browser also does not support browsing file:// uri, which is what git-annex falls back to when it cannot file a file manager to top. 
-"""]]
diff --git a/doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing/comment_2_015e859a16b1ce4c0c7601df0594d555._comment b/doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing/comment_2_015e859a16b1ce4c0c7601df0594d555._comment
deleted file mode 100644
index 039acd440..000000000
--- a/doc/bugs/Android:_Clocking_on___34__Files__34___in_the_Dashboard_seems_to_do_nothing/comment_2_015e859a16b1ce4c0c7601df0594d555._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://yarikoptic.myopenid.com/"
- nickname="site-myopenid"
- subject="comment 2"
- date="2013-11-27T04:36:14Z"
- content="""
-Thanks for the explanation!  Might be better then to remove Files in Android build to prevent confusion?
-
-OI filemanager http://www.openintents.org/en/filemanager  I believe is open source.  according to app info it is only 1.53MB (thus negligible in comparison) and probably could be 'collaborated with' so they could ship basic support for annex (git annex get/drop)... I just don't know if it would be possible to start existing OI manager under annex user (that would be needed right?).
-"""]]
diff --git a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password..mdwn b/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password..mdwn
deleted file mode 100644
index 1721fca79..000000000
--- a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password..mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-### Please describe the problem.
-
-I get this error when configuring jabber:
-
-/etc/resolv.conf: openFile: does not exist (No such file or directory)
-
-### What steps will reproduce the problem?
-
-Just submit the jabber username and password.
-
-### What version of git-annex are you using? On what operating system?
-
-$ git annex version
-git-annex version: 5.20131130-gc25be33
-build flags: Assistant Webapp Testsuite S3 WebDAV Inotify XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-
-> This was already fixed in [[!commit > b2e9339b57ae5a4677dc4197d135d33f18e18f9c]]
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_1_c973032e0b780bd3b26bf1f744f04082._comment b/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_1_c973032e0b780bd3b26bf1f744f04082._comment
deleted file mode 100644
index e45fbcf23..000000000
--- a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_1_c973032e0b780bd3b26bf1f744f04082._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkAUMhKOSkh9JaBA6xst3XxQIIsDEq5Zd4"
- nickname="Ovidiu"
- subject="Still having this problem"
- date="2014-05-09T12:53:02Z"
- content="""
-[2014-05-09 07:37:42 SAST] Transferrer: Uploaded 1-564 Erk..08_04.pdf
-ok
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-git-annex: /etc/resolv.conf: openFile: does not exist (No such file or directory)
-[2014-05-09 08:39:53 SAST] NetWatcherFallback: Syncing with box.com, gitannexbackup
-
-I saw it in the log file but I have no idea what triggered it.
-
-Using the .dmg install for Mac OsX
-Version: 5.20140420-ga25b8bb 
-Build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-
-on Mac OSX 10.9.2
-"""]]
diff --git a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_2_9ef5c13a7a28e9098a837d42e5c4c964._comment b/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_2_9ef5c13a7a28e9098a837d42e5c4c964._comment
deleted file mode 100644
index 080d929b5..000000000
--- a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_2_9ef5c13a7a28e9098a837d42e5c4c964._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 2"
- date="2014-05-16T17:24:00Z"
- content="""
-This bug report is about *Android*, not OSX. Please file a new bug report about any similar problem you might have with OSX.
-
-(AFAICS, OSX systems do have a /etc/resolv.conf, so perhaps your system is broken?)
-"""]]
diff --git a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_3_0c8087dfbcd8811913e7b3b6376cab90._comment b/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_3_0c8087dfbcd8811913e7b3b6376cab90._comment
deleted file mode 100644
index 2060021c0..000000000
--- a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_3_0c8087dfbcd8811913e7b3b6376cab90._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkAUMhKOSkh9JaBA6xst3XxQIIsDEq5Zd4"
- nickname="Ovidiu"
- subject="comment 3"
- date="2014-05-16T17:26:59Z"
- content="""
-ah, no I spotted the ADNROID in the title, sorry.
-I will open a new bug report then, I do have a resolv.conf:
-
-ls -al /etc/resolv.conf
-lrwxr-xr-x  1 root  wheel  22 Nov  2  2013 /etc/resolv.conf -> ../var/run/resolv.conf
-"""]]
diff --git a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_4_8ad9047dd136e3b438fb9a6d50ecb04c._comment b/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_4_8ad9047dd136e3b438fb9a6d50ecb04c._comment
deleted file mode 100644
index dd796c397..000000000
--- a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_4_8ad9047dd136e3b438fb9a6d50ecb04c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 4"
- date="2014-05-16T17:30:21Z"
- content="""
-You have a symlink to a file that may or may not exist. I'd check if the file exists, and if your user can read it before fileing a bug report.
-"""]]
diff --git a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_5_5f478c24065fc9a50a1cff3148b83bec._comment b/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_5_5f478c24065fc9a50a1cff3148b83bec._comment
deleted file mode 100644
index 65daf46ff..000000000
--- a/doc/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./comment_5_5f478c24065fc9a50a1cff3148b83bec._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkAUMhKOSkh9JaBA6xst3XxQIIsDEq5Zd4"
- nickname="Ovidiu"
- subject="comment 5"
- date="2014-05-16T17:37:29Z"
- content="""
-I can read it just fine:
-
-cat /etc/resolv.conf
-#
-# Mac OS X Notice
-#
-# This file is not used by the host name and address resolution
-# or the DNS query routing mechanisms used by most processes on
-# this Mac OS X system.
-#
-# This file is automatically generated.
-#
-nameserver 172.20.10.1
-"""]]
diff --git a/doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__.mdwn b/doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__.mdwn
deleted file mode 100644
index 16b1b4c6f..000000000
--- a/doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-### Please describe the problem.
-
-Upon a new (re-)installation of Android ("proper" build as from http://downloads.kitenet.net/git-annex/android/current/4.0/git-annex.apk  Last-Modified: Mon, 18 Nov 2013 11:57:25 GMT), as well as whatever was day before a daily build, I am getting a message in web ui "not supported  This build of git-annex does not support XMPP pairing. Sorry!" whenever I am entering "Share with your other devices" among "Add more repositories".
-
-### What steps will reproduce the problem?
-
-I had some older and then freshier (yesterday daily build) installed.  Then uninstalled and current "proper" build installed.
-it picked up initialized repository I did yesterday but when I went into "Share ..." link  I saw the message without any option to add such another device
-
-### What version of git-annex are you using? On what operating system?
-
-Android
-
-About says   5.20131118-gc7e5cde.  
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__/comment_1_c034bb84e58b2dda1038ba205ec78c56._comment b/doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__/comment_1_c034bb84e58b2dda1038ba205ec78c56._comment
deleted file mode 100644
index ef0661cb8..000000000
--- a/doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__/comment_1_c034bb84e58b2dda1038ba205ec78c56._comment
+++ /dev/null
@@ -1,273 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 1"
- date="2013-11-26T17:23:52Z"
- content="""
-I think that older Android builds did support this (IIRC). However, I recently rebootstrapped my android dev environment, and when I enable the XMPP flag now:
-
-<pre>
-system.c:222:0:  error: undefined reference to 'pthread_atfork'
-
-cipher.c:213:0:  error: undefined reference to 'nettle_cbc_encrypt'
-
-cipher.c:213:0:  error: undefined reference to 'nettle_cbc_decrypt'
-
-cipher.c:213:0:  error: undefined reference to 'nettle_des_encrypt'
-
-cipher.c:213:0:  error: undefined reference to 'nettle_des_decrypt'
-
-cipher.c:213:0:
-     error: undefined reference to 'nettle_arcfour_crypt'
-
-cipher.c:213:0:
-     error: undefined reference to 'nettle_des3_encrypt'
-
-cipher.c:213:0:
-     error: undefined reference to 'nettle_des3_decrypt'
-
-cipher.c:213:0:
-     error: undefined reference to 'nettle_arctwo_encrypt'
-
-cipher.c:213:0:
-     error: undefined reference to 'nettle_arctwo_decrypt'
-
-cipher.c:265:0:
-     error: undefined reference to 'nettle_arcfour_set_key'
-
-cipher.c:68:0:
-     error: undefined reference to 'nettle_aes_set_encrypt_key'
-
-cipher.c:69:0:
-     error: undefined reference to 'nettle_aes_invert_key'
-
-cipher.c:96:0:
-     error: undefined reference to 'nettle_camellia_set_encrypt_key'
-
-cipher.c:97:0:
-     error: undefined reference to 'nettle_camellia_invert_key'
-
-cipher.c:268:0:
-     error: undefined reference to 'nettle_arctwo_set_key'
-
-cipher.c:239:0:
-     error: undefined reference to 'nettle_des_fix_parity'
-
-cipher.c:242:0:
-     error: undefined reference to 'nettle_des3_set_key'
-
-cipher.c:255:0:
-     error: undefined reference to 'nettle_des_fix_parity'
-
-cipher.c:257:0:  error: undefined reference to 'nettle_des_set_key'
-
-cipher.c:83:0:  error: undefined reference to 'nettle_aes_decrypt'
-
-cipher.c:76:0:  error: undefined reference to 'nettle_aes_encrypt'
-
-cipher.c:111:0:
-     error: undefined reference to 'nettle_camellia_crypt'
-
-cipher.c:104:0:
-     error: undefined reference to 'nettle_camellia_crypt'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha256_update'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha224_digest'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha224_set_key'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_md5_update'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_md5_digest'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_md5_set_key'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha1_update'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha1_digest'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha1_set_key'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha256_digest'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha256_set_key'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha512_update'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha384_digest'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha384_set_key'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha512_digest'
-
-mac.c:146:0:
-     error: undefined reference to 'nettle_hmac_sha512_set_key'
-
-mac.c:243:0:  error: undefined reference to 'nettle_sha224_init'
-
-mac.c:222:0:  error: undefined reference to 'nettle_md5_init'
-
-mac.c:229:0:  error: undefined reference to 'nettle_sha1_init'
-
-mac.c:236:0:  error: undefined reference to 'nettle_md2_init'
-
-mac.c:250:0:  error: undefined reference to 'nettle_sha256_init'
-
-mac.c:257:0:  error: undefined reference to 'nettle_sha384_init'
-
-mac.c:264:0:  error: undefined reference to 'nettle_sha512_init'
-
-mac.c:278:0:  error: undefined reference to 'nettle_sha256_update'
-
-mac.c:278:0:  error: undefined reference to 'nettle_sha224_digest'
-
-mac.c:278:0:  error: undefined reference to 'nettle_md5_update'
-
-mac.c:278:0:  error: undefined reference to 'nettle_md5_digest'
-
-mac.c:278:0:  error: undefined reference to 'nettle_sha1_update'
-
-mac.c:278:0:  error: undefined reference to 'nettle_sha1_digest'
-
-mac.c:278:0:  error: undefined reference to 'nettle_md2_update'
-
-mac.c:278:0:  error: undefined reference to 'nettle_md2_digest'
-
-mac.c:278:0:  error: undefined reference to 'nettle_sha256_digest'
-
-mac.c:278:0:  error: undefined reference to 'nettle_sha512_update'
-
-mac.c:278:0:  error: undefined reference to 'nettle_sha384_digest'
-
-mac.c:278:0:  error: undefined reference to 'nettle_sha512_digest'
-
-mpi.c:48:0:
-     error: undefined reference to 'nettle_mpz_sizeinbase_256_u'
-
-mpi.c:80:0:  error: undefined reference to 'nettle_mpz_get_str_256'
-
-mpi.c:76:0:  error: undefined reference to 'nettle_mpz_get_str_256'
-
-mpi.c:52:0:
-     error: undefined reference to 'nettle_mpz_sizeinbase_256_s'
-
-mpi.c:56:0:
-     error: undefined reference to 'nettle_mpz_sizeinbase_256_u'
-
-mpi.c:142:0:
-     error: undefined reference to 'nettle_mpz_set_str_256_u'
-
-mpi.c:117:0:
-     error: undefined reference to 'nettle_mpz_set_str_256_u'
-
-mpi.c:121:0:
-     error: undefined reference to 'nettle_mpz_set_str_256_s'
-
-mpi.c:470:0:
-     error: undefined reference to 'nettle_mpz_set_str_256_u'
-
-mpi.c:496:0:
-     error: undefined reference to 'nettle_mpz_set_str_256_u'
-
-pk.c:505:0:
-     error: undefined reference to 'nettle_dsa_public_key_init'
-
-pk.c:506:0:
-     error: undefined reference to 'nettle_dsa_private_key_init'
-
-pk.c:515:0:
-     error: undefined reference to 'nettle_dsa_generate_keypair'
-
-pk.c:545:0:
-     error: undefined reference to 'nettle_dsa_private_key_clear'
-
-pk.c:546:0:
-     error: undefined reference to 'nettle_dsa_public_key_clear'
-
-pk.c:558:0:
-     error: undefined reference to 'nettle_rsa_public_key_init'
-
-pk.c:559:0:
-     error: undefined reference to 'nettle_rsa_private_key_init'
-
-pk.c:563:0:
-     error: undefined reference to 'nettle_rsa_generate_keypair'
-
-pk.c:598:0:
-     error: undefined reference to 'nettle_rsa_private_key_clear'
-
-pk.c:599:0:
-     error: undefined reference to 'nettle_rsa_public_key_clear'
-
-pk.c:598:0:
-     error: undefined reference to 'nettle_rsa_private_key_clear'
-
-pk.c:599:0:
-     error: undefined reference to 'nettle_rsa_public_key_clear'
-
-pk.c:545:0:
-     error: undefined reference to 'nettle_dsa_private_key_clear'
-
-pk.c:546:0:
-     error: undefined reference to 'nettle_dsa_public_key_clear'
-
-pk.c:286:0:
-     error: undefined reference to 'nettle_dsa_signature_init'
-
-pk.c:296:0:  error: undefined reference to '_nettle_dsa_sign'
-
-pk.c:309:0:
-     error: undefined reference to 'nettle_dsa_signature_clear'
-
-pk.c:344:0:
-     error: undefined reference to 'nettle_rsa_compute_root'
-
-pk.c:309:0:
-     error: undefined reference to 'nettle_dsa_signature_clear'
-
-pk.c:231:0:
-     error: undefined reference to 'nettle_rsa_compute_root'
-
-pk.c:441:0:  error: undefined reference to '_nettle_dsa_verify'
-
-rnd.c:222:0:
-     error: undefined reference to 'nettle_yarrow256_update'
-
-rnd.c:340:0:
-     error: undefined reference to 'nettle_yarrow256_update'
-
-rnd.c:284:0:
-     error: undefined reference to 'nettle_yarrow256_update'
-
-rnd.c:388:0:
-     error: undefined reference to 'nettle_yarrow256_slow_reseed'
-
-rnd.c:465:0:
-     error: undefined reference to 'nettle_yarrow256_random'
-
-rnd.c:421:0:  error: undefined reference to 'nettle_yarrow256_init'
-
-rnd.c:437:0:
-     error: undefined reference to 'nettle_yarrow256_slow_reseed'
-collect2: error: ld returned 1 exit status
-make: *** [android] Error 1
-</pre>
-
-
-"""]]
diff --git a/doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__/comment_2_99a754f41d59fdd401ba6d169945e7c9._comment b/doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__/comment_2_99a754f41d59fdd401ba6d169945e7c9._comment
deleted file mode 100644
index 6c5f48d5c..000000000
--- a/doc/bugs/Android___34__This_build_of_git-annex_does_not_support_XMPP_pairing__34__/comment_2_99a754f41d59fdd401ba6d169945e7c9._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 2"
- date="2013-11-26T19:40:55Z"
- content="""
-Managed to get it to build with XMPP, but it was quite a hack job getting the C libraries to behave, and I have not been able to test it yet. The daily build has it if you want to give it a try.
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup.mdwn b/doc/bugs/Android_app_permission_denial_on_startup.mdwn
deleted file mode 100644
index 689d7a748..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-### Please describe the problem.
-
-Android app barfs on startup.
-
-### What steps will reproduce the problem?
-
-Download/install/start Android app :)
-
-### What version of git-annex are you using? On what operating system?
-
-Just downloaded the .apk (Friday May 3rd).  Android 4.2.2 on Google/LG Nexus 4 
-
-### Please provide any additional information below.
-
-See this [screenshot](https://docs.google.com/file/d/0B8tqeaAn45VORU1ET1ZpTWxLTjQ/edit?usp=sharing).
-Feel free to ping me on IRC if you need additional info or want to test a fix.
-
-> [[done]]; now comprehensively fixed. --[[Joey]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_10_dc06737997c8883ef0a12dbecd9ac30f._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_10_dc06737997c8883ef0a12dbecd9ac30f._comment
deleted file mode 100644
index 417d23e84..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_10_dc06737997c8883ef0a12dbecd9ac30f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlcxKZHglATIiJXD7jcxfYhkhgeFmcVFqE"
- nickname="James"
- subject="21-May-2013 still broken"
- date="2013-05-24T12:00:37Z"
- content="""
-I downloaded the android app dated 21-May-2013. I get the same permission error as before on startup.
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_11_b444cd6717658116533745c51481dd3d._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_11_b444cd6717658116533745c51481dd3d._comment
deleted file mode 100644
index b776c2e7d..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_11_b444cd6717658116533745c51481dd3d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 11"
- date="2013-05-29T17:01:55Z"
- content="""
-Today's autobuild of git-annex for Android has a workaround for this problem. You can select \"Open WebApp\" from the menu in the terminal emulator app, and it should work. Would appreciate confirmation from someone who has seen this problem. If that menu item works, I may later be able to make it open automatically.
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_12_66181f34ed7496d1f6601b39e5ae3c65._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_12_66181f34ed7496d1f6601b39e5ae3c65._comment
deleted file mode 100644
index 5a099121c..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_12_66181f34ed7496d1f6601b39e5ae3c65._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkGCmVc5qIJaQQgG82Hc5zzBdAVdhe2JEM"
- nickname="Bruno"
- subject="comment 12"
- date="2013-05-29T17:20:40Z"
- content="""
-It works!
-
-Note that the \"open webapp\" menu item is not available if my phone is set to French.
-
-French: http://i.imgur.com/cik0sIL.png
-English: http://i.imgur.com/8Oh6FEw.png
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_1_ddf5761bf14de30ac97030ad338601ae._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_1_ddf5761bf14de30ac97030ad338601ae._comment
deleted file mode 100644
index 0f72b661e..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_1_ddf5761bf14de30ac97030ad338601ae._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-03T22:44:36Z"
- content="""
-> startActivity asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
-
-The webapp continues running despite this, so you can certainly work around this by copying and pasting the displayed url into the web browser.
-
-<http://stackoverflow.com/questions/14744578/how-could-a-root-app-call-apis-with-signature-level-protected-permission>
-
-Based on this post, I cannot simply modify the app to request this permission. I don't know why your Android is requiring this permission, which AFAICS is supposed to be used to switch which user is logged in, when I'm merely trying to open a web browser. You might try closing any web browser you have open and see if that avoids the problem.
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_2_8b9fafa73ebf5f803c7da9531cfb5b34._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_2_8b9fafa73ebf5f803c7da9531cfb5b34._comment
deleted file mode 100644
index ca6a8b9ff..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_2_8b9fafa73ebf5f803c7da9531cfb5b34._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkGCmVc5qIJaQQgG82Hc5zzBdAVdhe2JEM"
- nickname="Bruno"
- subject="comment 2"
- date="2013-05-04T05:02:45Z"
- content="""
-I have the same problem. Also with a Nexus 4 (4.2.2).
-
-The problem still happens if I start git annex before any browser is open. I tested after a reboot.
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_3_58501bb043b4c5836d7472ffd6baa72c._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_3_58501bb043b4c5836d7472ffd6baa72c._comment
deleted file mode 100644
index 419e6bceb..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_3_58501bb043b4c5836d7472ffd6baa72c._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~subito"
- nickname="subito"
- subject="Galaxy Nexus: same here"
- date="2013-05-05T10:46:12Z"
- content="""
-    Falling back to hardcoded app location; cannot find expected files in /data/app-lib
-    git annex webapp
-    u0_a65@android:/sdcard/git-annex.home $ git annex webapp
-    Launching web browser on http://127.0.0.1:38549 /?auth=38bf9df739a9f1671fd99153e2ef1e81a54dece8b18469152692277c056208cda039e1d9486e3115144a3e3da14a51056b260400ee563cde30b28b10b25ca2d0
-    Starting: Intent { act=android.intent.action.VIEW dat=http://127.0.0.1:38549/?auth=38bf9df739a9f1671fd99153e2ef1e81a54dece8b18469152692277c056208cda039e1d9486e3115144a3e3da14a51056b260400ee563cde30b28b10b25ca2d0 }
-    java.lang.SecurityException: Permission Denial: startActivity asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
-            at android.os.Parcel.readException(Parcel.java:1425)
-            at android.os.Parcel.readException(Parcel.java:1379)
-            at android.app.ActivityManagerProxy.startActivityAsUser(ActivityManagerNative.java:1921)
-            at com.android.commands.am.Am.runStart(Am.java:494)
-            at com.android.commands.am.Am.run(Am.java:109)
-            at com.android.commands.am.Am.main(Am.java:82)
-            at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
-            at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
-            at dalvik.system.NativeStart.main(Native Method)
-    failed to start web browser
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_4_d3a04dc7bbc1816cccc8d85c73ffb689._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_4_d3a04dc7bbc1816cccc8d85c73ffb689._comment
deleted file mode 100644
index 5f6ce0b66..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_4_d3a04dc7bbc1816cccc8d85c73ffb689._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn26WQjIP5fnMgQF_L_k3Q3UrR5v8mjRTY"
- nickname="Ellis"
- subject="comment 4"
- date="2013-05-05T12:18:41Z"
- content="""
-I'm also using a Samsung Galaxy Nexus with the latest Android and git-annex, and I'm getting the same error as above (with different port, auth id, and uid).  Opening the url manually does work, as Joey said.
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_5_eeabbc0cc434ed84c36a3f4e03fcef36._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_5_eeabbc0cc434ed84c36a3f4e03fcef36._comment
deleted file mode 100644
index cfd0e8663..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_5_eeabbc0cc434ed84c36a3f4e03fcef36._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-05-06T14:13:51Z"
- content="""
-I have also had a report that this happens on a galaxy nexus 4.2.1.
-
-So far, every reporter has had a galaxy nexus. Hmm...
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_6_4203b496bee1bdd424466ed63b5d31cf._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_6_4203b496bee1bdd424466ed63b5d31cf._comment
deleted file mode 100644
index 1f2179271..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_6_4203b496bee1bdd424466ed63b5d31cf._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkGCmVc5qIJaQQgG82Hc5zzBdAVdhe2JEM"
- nickname="Bruno"
- subject="comment 6"
- date="2013-05-06T14:29:59Z"
- content="""
-The Galaxy Nexus (Samsung) is not the same as the Nexus 4 (LG).
-
-See: https://en.wikipedia.org/wiki/Google_Nexus#Comparison_of_phones
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_7_74373eb2cc46b76659e3c463d6682d15._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_7_74373eb2cc46b76659e3c463d6682d15._comment
deleted file mode 100644
index 12c1e3eed..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_7_74373eb2cc46b76659e3c463d6682d15._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn26WQjIP5fnMgQF_L_k3Q3UrR5v8mjRTY"
- nickname="Ellis"
- subject="addendum to comment 4"
- date="2013-05-06T15:32:51Z"
- content="""
-As a side node, my device is rooted.  The web browser starts properly when I start it as follows: adb shell; su; /data/data/ga.androidterm/runshell; git annex webapp
-
-However, with previous versions of git-annex for android, I had problems with git-annex when starting it this way; if I recall correctly, ``git annex get`` didn't work.  Will test again when I have time.
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_8_0923d2a09df01d152ec4784c92689c96._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_8_0923d2a09df01d152ec4784c92689c96._comment
deleted file mode 100644
index 98e1e19ed..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_8_0923d2a09df01d152ec4784c92689c96._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://adamspiers.myopenid.com/"
- nickname="Adam"
- subject="more info on original report"
- date="2013-05-08T11:16:30Z"
- content="""
-I should have said that I am running a recent-ish nightly of CyanogenMod 10.1.  This means that my Nexus 4 is rooted.  Bruno is quite correct to point out that the Nexus 4 (made by LG) is a very different beast to the Galaxy Nexus (made by Samsung).
-"""]]
diff --git a/doc/bugs/Android_app_permission_denial_on_startup/comment_9_b60928e54a5b620899cf29820b9b8e70._comment b/doc/bugs/Android_app_permission_denial_on_startup/comment_9_b60928e54a5b620899cf29820b9b8e70._comment
deleted file mode 100644
index 68ab46be1..000000000
--- a/doc/bugs/Android_app_permission_denial_on_startup/comment_9_b60928e54a5b620899cf29820b9b8e70._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmSbJHbvlxbCjtPXk_Io3qP3MFqJr3pUgQ"
- nickname="Christopher"
- subject="New permission type"
- date="2013-05-09T22:01:38Z"
- content="""
-I observe that I am encountering the same on my Galaxy Nexus running CM10.1; I see indication that the \"INTERACT_ACROSS_USERS_FULL\" is a new permission in Android 4.2 that relates to the use of multiple users, which is one of the new features of 4.2.
-
-It's possible that there are bugs here... See: https://code.google.com/p/android/issues/detail?id=39801
-"""]]
diff --git a/doc/bugs/Android_daily_build_missing_webapp.mdwn b/doc/bugs/Android_daily_build_missing_webapp.mdwn
deleted file mode 100644
index 682186b73..000000000
--- a/doc/bugs/Android_daily_build_missing_webapp.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-### Please describe the problem.
-
-The daily Android build is missing the webapp, raising a bug in case this is unexpected.
-
-### What steps will reproduce the problem?
-
-Down the daily APK, it is 9MB.
-
-### What version of git-annex are you using? On what operating system?
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> Probably several of them were. I've fixed the cabal file, re-running
-> android build now. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum.mdwn b/doc/bugs/Android_version_apparently_unable_to_run_sha256sum.mdwn
deleted file mode 100644
index 36f9a452b..000000000
--- a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-I’m running git-annex 5.20140517-gee56d21 on Android 4.3.
-
-Running “git annex add filename” from the command line fails to execute sha256sum:
-
-[[!format sh """
-git-annex: sha256sum: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory)
-failed
-git-annex: add: 1 failed
-"""]]
-
-“type sha256sum” says “sha256sum not found”, and indeed, /data/data/ga.androidterm/bin only contains the following files: busybox, git, git-annex, git-receive-pack, git-shell, git-upload-archive, git-upload-pack, gpg, rsync, ssh, ssh-keygen, trustedkeys.gpg.
-
-Running “busybox sha256sum” does the right thing.
-
-The assistant says “Added filename” every time it’s started but the file does not actually get added.
-
-The only relevant log lines seem to be:
-
-[[!format sh """
-[2014-05-18 16:57:06 EEST] Watcher: add direct git-annex.apk
-[2014-05-18 16:57:07 EEST] read: lsof ["-F0can","--","git-annex.apk"]
-[2014-05-18 16:57:08 EEST] Committer: Adding git-annex.apk
-add git-annex.apk [2014-05-18 16:57:08 EEST] chat: git [--git-dir=/storage/emulated/legacy/annex/.git","--work-tree=/storage/emulated/legacy/annex","-c","core.bare=false","check-attr","-z","--stdin","annex.backend","annex.numcopies","--"]
-[2014-05-18 16:57:08 EEST] read: sha256sum ["git-annex.apk"]
-"""]]
-
-> Modified runshell to use busybox install -s; [[done]] --[[Joey]]
diff --git a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_1_51316a0a0d80cf8f9ee37b2eca64323d._comment b/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_1_51316a0a0d80cf8f9ee37b2eca64323d._comment
deleted file mode 100644
index 403f302b1..000000000
--- a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_1_51316a0a0d80cf8f9ee37b2eca64323d._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="216.145.95.162"
- subject="comment 1"
- date="2014-05-18T16:33:29Z"
- content="""
-busybox is supposed to install these symlinks
-
-There may be a hint in `/sdcard/git-annex.home/git-annex-install.log`
-
-Or, you could try to run `busybox --install /data/data/ga.androidterm/bin`
-"""]]
diff --git a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_2_14341ee188b1248f68164b1d9aa4c929._comment b/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_2_14341ee188b1248f68164b1d9aa4c929._comment
deleted file mode 100644
index 47d068b15..000000000
--- a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_2_14341ee188b1248f68164b1d9aa4c929._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.3"
- subject="comment 2"
- date="2014-05-21T17:32:17Z"
- content="""
-I tested this version of git-annex on Android 4.0, doing both an upgrade and a fresh install. In both cases, sha256sum and the other busybox links were set up ok.
-
-At this point this looks to be either specific to your version of Android, or some problem that botched the install.
-Please follow-up with the requested information. Also, try removing and reinstalling git-annex from scratch.
-"""]]
diff --git a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_3_8624567ebc3af967fb59bad5a3fb6659._comment b/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_3_8624567ebc3af967fb59bad5a3fb6659._comment
deleted file mode 100644
index cb95c3a2f..000000000
--- a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_3_8624567ebc3af967fb59bad5a3fb6659._comment
+++ /dev/null
@@ -1,367 +0,0 @@
-[[!comment format=mdwn
- username="http://johan.kiviniemi.name/"
- nickname="Johan"
- subject="comment 3"
- date="2014-05-22T18:35:32Z"
- content="""
-I tried uninstalling and reinstalling, the result was the same. Here’s [[!toggle id=\"git-annex-install.log\" text=\"git-annex-install.log\"]].
-
-[[!toggleable id=\"git-annex-install.log\" text=\"\"\"
-Installation starting to /data/data/ga.androidterm
-ee56d21580dd66d62093af92ee687682b0f55d94
-installing busybox
-installing git-annex
-installing git-shell
-installing git-upload-pack
-installing git
-installing gpg
-installing rsync
-installing ssh
-installing ssh-keygen
-busybox: /data/data/ga.androidterm/bin/[: Permission denied
-busybox: /data/data/ga.androidterm/bin/[[: Permission denied
-busybox: /data/data/ga.androidterm/bin/ar: Permission denied
-busybox: /data/data/ga.androidterm/bin/arp: Permission denied
-busybox: /data/data/ga.androidterm/bin/ash: Permission denied
-busybox: /data/data/ga.androidterm/bin/base64: Permission denied
-busybox: /data/data/ga.androidterm/bin/basename: Permission denied
-busybox: /data/data/ga.androidterm/bin/beep: Permission denied
-busybox: /data/data/ga.androidterm/bin/blkid: Permission denied
-busybox: /data/data/ga.androidterm/bin/blockdev: Permission denied
-busybox: /data/data/ga.androidterm/bin/bunzip2: Permission denied
-busybox: /data/data/ga.androidterm/bin/bzcat: Permission denied
-busybox: /data/data/ga.androidterm/bin/bzip2: Permission denied
-busybox: /data/data/ga.androidterm/bin/cal: Permission denied
-busybox: /data/data/ga.androidterm/bin/cat: Permission denied
-busybox: /data/data/ga.androidterm/bin/catv: Permission denied
-busybox: /data/data/ga.androidterm/bin/chat: Permission denied
-busybox: /data/data/ga.androidterm/bin/chattr: Permission denied
-busybox: /data/data/ga.androidterm/bin/chgrp: Permission denied
-busybox: /data/data/ga.androidterm/bin/chmod: Permission denied
-busybox: /data/data/ga.androidterm/bin/chown: Permission denied
-busybox: /data/data/ga.androidterm/bin/chpst: Permission denied
-busybox: /data/data/ga.androidterm/bin/chroot: Permission denied
-busybox: /data/data/ga.androidterm/bin/chrt: Permission denied
-busybox: /data/data/ga.androidterm/bin/chvt: Permission denied
-busybox: /data/data/ga.androidterm/bin/cksum: Permission denied
-busybox: /data/data/ga.androidterm/bin/clear: Permission denied
-busybox: /data/data/ga.androidterm/bin/cmp: Permission denied
-busybox: /data/data/ga.androidterm/bin/comm: Permission denied
-busybox: /data/data/ga.androidterm/bin/cp: Permission denied
-busybox: /data/data/ga.androidterm/bin/cpio: Permission denied
-busybox: /data/data/ga.androidterm/bin/cttyhack: Permission denied
-busybox: /data/data/ga.androidterm/bin/cut: Permission denied
-busybox: /data/data/ga.androidterm/bin/dc: Permission denied
-busybox: /data/data/ga.androidterm/bin/dd: Permission denied
-busybox: /data/data/ga.androidterm/bin/deallocvt: Permission denied
-busybox: /data/data/ga.androidterm/bin/devmem: Permission denied
-busybox: /data/data/ga.androidterm/bin/diff: Permission denied
-busybox: /data/data/ga.androidterm/bin/dirname: Permission denied
-busybox: /data/data/ga.androidterm/bin/dmesg: Permission denied
-busybox: /data/data/ga.androidterm/bin/dnsd: Permission denied
-busybox: /data/data/ga.androidterm/bin/dos2unix: Permission denied
-busybox: /data/data/ga.androidterm/bin/dpkg: Permission denied
-busybox: /data/data/ga.androidterm/bin/dpkg-deb: Permission denied
-busybox: /data/data/ga.androidterm/bin/du: Permission denied
-busybox: /data/data/ga.androidterm/bin/dumpkmap: Permission denied
-busybox: /data/data/ga.androidterm/bin/echo: Permission denied
-busybox: /data/data/ga.androidterm/bin/envdir: Permission denied
-busybox: /data/data/ga.androidterm/bin/envuidgid: Permission denied
-busybox: /data/data/ga.androidterm/bin/expand: Permission denied
-busybox: /data/data/ga.androidterm/bin/fakeidentd: Permission denied
-busybox: /data/data/ga.androidterm/bin/false: Permission denied
-busybox: /data/data/ga.androidterm/bin/fbset: Permission denied
-busybox: /data/data/ga.androidterm/bin/fbsplash: Permission denied
-busybox: /data/data/ga.androidterm/bin/fdflush: Permission denied
-busybox: /data/data/ga.androidterm/bin/fdformat: Permission denied
-busybox: /data/data/ga.androidterm/bin/fdisk: Permission denied
-busybox: /data/data/ga.androidterm/bin/fgconsole: Permission denied
-busybox: /data/data/ga.androidterm/bin/find: Permission denied
-busybox: /data/data/ga.androidterm/bin/findfs: Permission denied
-busybox: /data/data/ga.androidterm/bin/flash_lock: Permission denied
-busybox: /data/data/ga.androidterm/bin/flash_unlock: Permission denied
-busybox: /data/data/ga.androidterm/bin/flashcp: Permission denied
-busybox: /data/data/ga.androidterm/bin/flock: Permission denied
-busybox: /data/data/ga.androidterm/bin/fold: Permission denied
-busybox: /data/data/ga.androidterm/bin/freeramdisk: Permission denied
-busybox: /data/data/ga.androidterm/bin/ftpd: Permission denied
-busybox: /data/data/ga.androidterm/bin/ftpget: Permission denied
-busybox: /data/data/ga.androidterm/bin/ftpput: Permission denied
-busybox: /data/data/ga.androidterm/bin/fuser: Permission denied
-busybox: /data/data/ga.androidterm/bin/getopt: Permission denied
-busybox: /data/data/ga.androidterm/bin/grep: Permission denied
-busybox: /data/data/ga.androidterm/bin/gunzip: Permission denied
-busybox: /data/data/ga.androidterm/bin/gzip: Permission denied
-busybox: /data/data/ga.androidterm/bin/hd: Permission denied
-busybox: /data/data/ga.androidterm/bin/hdparm: Permission denied
-busybox: /data/data/ga.androidterm/bin/head: Permission denied
-busybox: /data/data/ga.androidterm/bin/hexdump: Permission denied
-busybox: /data/data/ga.androidterm/bin/httpd: Permission denied
-busybox: /data/data/ga.androidterm/bin/ifconfig: Permission denied
-busybox: /data/data/ga.androidterm/bin/ifdown: Permission denied
-busybox: /data/data/ga.androidterm/bin/ifup: Permission denied
-busybox: /data/data/ga.androidterm/bin/inotifyd: Permission denied
-busybox: /data/data/ga.androidterm/bin/install: Permission denied
-busybox: /data/data/ga.androidterm/bin/iostat: Permission denied
-busybox: /data/data/ga.androidterm/bin/ip: Permission denied
-busybox: /data/data/ga.androidterm/bin/ipaddr: Permission denied
-busybox: /data/data/ga.androidterm/bin/ipcalc: Permission denied
-busybox: /data/data/ga.androidterm/bin/iplink: Permission denied
-busybox: /data/data/ga.androidterm/bin/iproute: Permission denied
-busybox: /data/data/ga.androidterm/bin/iprule: Permission denied
-busybox: /data/data/ga.androidterm/bin/iptunnel: Permission denied
-busybox: /data/data/ga.androidterm/bin/klogd: Permission denied
-busybox: /data/data/ga.androidterm/bin/ln: Permission denied
-busybox: /data/data/ga.androidterm/bin/loadkmap: Permission denied
-busybox: /data/data/ga.androidterm/bin/losetup: Permission denied
-busybox: /data/data/ga.androidterm/bin/lpd: Permission denied
-busybox: /data/data/ga.androidterm/bin/lpq: Permission denied
-busybox: /data/data/ga.androidterm/bin/lpr: Permission denied
-busybox: /data/data/ga.androidterm/bin/ls: Permission denied
-busybox: /data/data/ga.androidterm/bin/lsattr: Permission denied
-busybox: /data/data/ga.androidterm/bin/lsof: Permission denied
-busybox: /data/data/ga.androidterm/bin/lspci: Permission denied
-busybox: /data/data/ga.androidterm/bin/lsusb: Permission denied
-busybox: /data/data/ga.androidterm/bin/lzcat: Permission denied
-busybox: /data/data/ga.androidterm/bin/lzma: Permission denied
-busybox: /data/data/ga.androidterm/bin/lzop: Permission denied
-busybox: /data/data/ga.androidterm/bin/lzopcat: Permission denied
-busybox: /data/data/ga.androidterm/bin/makedevs: Permission denied
-busybox: /data/data/ga.androidterm/bin/makemime: Permission denied
-busybox: /data/data/ga.androidterm/bin/man: Permission denied
-busybox: /data/data/ga.androidterm/bin/md5sum: Permission denied
-busybox: /data/data/ga.androidterm/bin/mkdir: Permission denied
-busybox: /data/data/ga.androidterm/bin/mkfifo: Permission denied
-busybox: /data/data/ga.androidterm/bin/mknod: Permission denied
-busybox: /data/data/ga.androidterm/bin/mkswap: Permission denied
-busybox: /data/data/ga.androidterm/bin/mktemp: Permission denied
-busybox: /data/data/ga.androidterm/bin/more: Permission denied
-busybox: /data/data/ga.androidterm/bin/mpstat: Permission denied
-busybox: /data/data/ga.androidterm/bin/mv: Permission denied
-busybox: /data/data/ga.androidterm/bin/nbd-client: Permission denied
-busybox: /data/data/ga.androidterm/bin/nc: Permission denied
-busybox: /data/data/ga.androidterm/bin/netstat: Permission denied
-busybox: /data/data/ga.androidterm/bin/nice: Permission denied
-busybox: /data/data/ga.androidterm/bin/nmeter: Permission denied
-busybox: /data/data/ga.androidterm/bin/nohup: Permission denied
-busybox: /data/data/ga.androidterm/bin/od: Permission denied
-busybox: /data/data/ga.androidterm/bin/openvt: Permission denied
-busybox: /data/data/ga.androidterm/bin/patch: Permission denied
-busybox: /data/data/ga.androidterm/bin/pidof: Permission denied
-busybox: /data/data/ga.androidterm/bin/pipe_progress: Permission denied
-busybox: /data/data/ga.androidterm/bin/pmap: Permission denied
-busybox: /data/data/ga.androidterm/bin/popmaildir: Permission denied
-busybox: /data/data/ga.androidterm/bin/printenv: Permission denied
-busybox: /data/data/ga.androidterm/bin/printf: Permission denied
-busybox: /data/data/ga.androidterm/bin/pscan: Permission denied
-busybox: /data/data/ga.androidterm/bin/pstree: Permission denied
-busybox: /data/data/ga.androidterm/bin/pwd: Permission denied
-busybox: /data/data/ga.androidterm/bin/pwdx: Permission denied
-busybox: /data/data/ga.androidterm/bin/raidautorun: Permission denied
-busybox: /data/data/ga.androidterm/bin/rdev: Permission denied
-busybox: /data/data/ga.androidterm/bin/readlink: Permission denied
-busybox: /data/data/ga.androidterm/bin/readprofile: Permission denied
-busybox: /data/data/ga.androidterm/bin/realpath: Permission denied
-busybox: /data/data/ga.androidterm/bin/reformime: Permission denied
-busybox: /data/data/ga.androidterm/bin/renice: Permission denied
-busybox: /data/data/ga.androidterm/bin/reset: Permission denied
-busybox: /data/data/ga.androidterm/bin/resize: Permission denied
-busybox: /data/data/ga.androidterm/bin/rev: Permission denied
-busybox: /data/data/ga.androidterm/bin/rm: Permission denied
-busybox: /data/data/ga.androidterm/bin/rmdir: Permission denied
-busybox: /data/data/ga.androidterm/bin/route: Permission denied
-busybox: /data/data/ga.androidterm/bin/rpm: Permission denied
-busybox: /data/data/ga.androidterm/bin/rpm2cpio: Permission denied
-busybox: /data/data/ga.androidterm/bin/rtcwake: Permission denied
-busybox: /data/data/ga.androidterm/bin/run-parts: Permission denied
-busybox: /data/data/ga.androidterm/bin/runsv: Permission denied
-busybox: /data/data/ga.androidterm/bin/runsvdir: Permission denied
-busybox: /data/data/ga.androidterm/bin/rx: Permission denied
-busybox: /data/data/ga.androidterm/bin/script: Permission denied
-busybox: /data/data/ga.androidterm/bin/scriptreplay: Permission denied
-busybox: /data/data/ga.androidterm/bin/sed: Permission denied
-busybox: /data/data/ga.androidterm/bin/sendmail: Permission denied
-busybox: /data/data/ga.androidterm/bin/seq: Permission denied
-busybox: /data/data/ga.androidterm/bin/setconsole: Permission denied
-busybox: /data/data/ga.androidterm/bin/setkeycodes: Permission denied
-busybox: /data/data/ga.androidterm/bin/setlogcons: Permission denied
-busybox: /data/data/ga.androidterm/bin/setserial: Permission denied
-busybox: /data/data/ga.androidterm/bin/setsid: Permission denied
-busybox: /data/data/ga.androidterm/bin/setuidgid: Permission denied
-busybox: /data/data/ga.androidterm/bin/sh: Permission denied
-busybox: /data/data/ga.androidterm/bin/sha1sum: Permission denied
-busybox: /data/data/ga.androidterm/bin/sha256sum: Permission denied
-busybox: /data/data/ga.androidterm/bin/sha512sum: Permission denied
-busybox: /data/data/ga.androidterm/bin/showkey: Permission denied
-busybox: /data/data/ga.androidterm/bin/sleep: Permission denied
-busybox: /data/data/ga.androidterm/bin/smemcap: Permission denied
-busybox: /data/data/ga.androidterm/bin/softlimit: Permission denied
-busybox: /data/data/ga.androidterm/bin/sort: Permission denied
-busybox: /data/data/ga.androidterm/bin/split: Permission denied
-busybox: /data/data/ga.androidterm/bin/start-stop-daemon: Permission denied
-busybox: /data/data/ga.androidterm/bin/strings: Permission denied
-busybox: /data/data/ga.androidterm/bin/stty: Permission denied
-busybox: /data/data/ga.androidterm/bin/sum: Permission denied
-busybox: /data/data/ga.androidterm/bin/sv: Permission denied
-busybox: /data/data/ga.androidterm/bin/svlogd: Permission denied
-busybox: /data/data/ga.androidterm/bin/sync: Permission denied
-busybox: /data/data/ga.androidterm/bin/sysctl: Permission denied
-busybox: /data/data/ga.androidterm/bin/tac: Permission denied
-busybox: /data/data/ga.androidterm/bin/tail: Permission denied
-busybox: /data/data/ga.androidterm/bin/tar: Permission denied
-busybox: /data/data/ga.androidterm/bin/tcpsvd: Permission denied
-busybox: /data/data/ga.androidterm/bin/tee: Permission denied
-busybox: /data/data/ga.androidterm/bin/test: Permission denied
-busybox: /data/data/ga.androidterm/bin/time: Permission denied
-busybox: /data/data/ga.androidterm/bin/timeout: Permission denied
-busybox: /data/data/ga.androidterm/bin/top: Permission denied
-busybox: /data/data/ga.androidterm/bin/touch: Permission denied
-busybox: /data/data/ga.androidterm/bin/tr: Permission denied
-busybox: /data/data/ga.androidterm/bin/true: Permission denied
-busybox: /data/data/ga.androidterm/bin/ttysize: Permission denied
-busybox: /data/data/ga.androidterm/bin/tunctl: Permission denied
-busybox: /data/data/ga.androidterm/bin/tune2fs: Permission denied
-busybox: /data/data/ga.androidterm/bin/udhcpc: Permission denied
-busybox: /data/data/ga.androidterm/bin/uname: Permission denied
-busybox: /data/data/ga.androidterm/bin/uncompress: Permission denied
-busybox: /data/data/ga.androidterm/bin/unexpand: Permission denied
-busybox: /data/data/ga.androidterm/bin/uniq: Permission denied
-busybox: /data/data/ga.androidterm/bin/unix2dos: Permission denied
-busybox: /data/data/ga.androidterm/bin/unlzma: Permission denied
-busybox: /data/data/ga.androidterm/bin/unlzop: Permission denied
-busybox: /data/data/ga.androidterm/bin/unxz: Permission denied
-busybox: /data/data/ga.androidterm/bin/unzip: Permission denied
-busybox: /data/data/ga.androidterm/bin/uudecode: Permission denied
-busybox: /data/data/ga.androidterm/bin/uuencode: Permission denied
-busybox: /data/data/ga.androidterm/bin/vi: Permission denied
-busybox: /data/data/ga.androidterm/bin/volname: Permission denied
-busybox: /data/data/ga.androidterm/bin/watch: Permission denied
-busybox: /data/data/ga.androidterm/bin/wc: Permission denied
-busybox: /data/data/ga.androidterm/bin/wget: Permission denied
-busybox: /data/data/ga.androidterm/bin/which: Permission denied
-busybox: /data/data/ga.androidterm/bin/whoami: Permission denied
-busybox: /data/data/ga.androidterm/bin/whois: Permission denied
-busybox: /data/data/ga.androidterm/bin/xargs: Permission denied
-busybox: /data/data/ga.androidterm/bin/xz: Permission denied
-busybox: /data/data/ga.androidterm/bin/xzcat: Permission denied
-busybox: /data/data/ga.androidterm/bin/yes: Permission denied
-busybox: /data/data/ga.androidterm/bin/zcat: Permission denied
-linking ./bin/git-upload-archive to git
-linking ./bin/git-receive-pack to git
-linking ./libexec/git-core/git-help to git
-linking ./libexec/git-core/git-fsck to git
-linking ./libexec/git-core/git-cat-file to git
-linking ./libexec/git-core/git-init to git
-linking ./libexec/git-core/git-checkout-index to git
-linking ./libexec/git-core/git-notes to git
-linking ./libexec/git-core/git-grep to git
-linking ./libexec/git-core/git-blame to git
-linking ./libexec/git-core/git-verify-tag to git
-linking ./libexec/git-core/git-write-tree to git
-linking ./libexec/git-core/git-log to git
-linking ./libexec/git-core/git-stage to git
-linking ./libexec/git-core/git-update-ref to git
-linking ./libexec/git-core/git-status to git
-linking ./libexec/git-core/git-show-branch to git
-linking ./libexec/git-core/git-merge-file to git
-linking ./libexec/git-core/git-for-each-ref to git
-linking ./libexec/git-core/git to git
-linking ./libexec/git-core/git-replace to git
-linking ./libexec/git-core/git-update-index to git
-linking ./libexec/git-core/git-annotate to git
-linking ./libexec/git-core/git-patch-id to git
-linking ./libexec/git-core/git-merge-recursive to git
-linking ./libexec/git-core/git-rm to git
-linking ./libexec/git-core/git-ls-tree to git
-linking ./libexec/git-core/git-update-server-info to git
-linking ./libexec/git-core/git-diff-tree to git
-linking ./libexec/git-core/git-merge-tree to git
-linking ./libexec/git-core/git-mktag to git
-linking ./libexec/git-core/git-rev-list to git
-linking ./libexec/git-core/git-column to git
-linking ./libexec/git-core/git-apply to git
-linking ./libexec/git-core/git-var to git
-linking ./libexec/git-core/git-rev-parse to git
-linking ./libexec/git-core/git-archive to git
-linking ./libexec/git-core/git-verify-pack to git
-linking ./libexec/git-core/git-push to git
-linking ./libexec/git-core/git-commit to git
-linking ./libexec/git-core/git-tag to git
-linking ./libexec/git-core/git-pack-refs to git
-linking ./libexec/git-core/git-fmt-merge-msg to git
-linking ./libexec/git-core/git-fast-export to git
-linking ./libexec/git-core/git-remote-ext to git
-linking ./libexec/git-core/git-mailsplit to git
-linking ./libexec/git-core/git-send-pack to git
-linking ./libexec/git-core/git-diff-index to git
-linking ./libexec/git-core/git-mailinfo to git
-linking ./libexec/git-core/git-revert to git
-linking ./libexec/git-core/git-diff-files to git
-linking ./libexec/git-core/git-merge-ours to git
-linking ./libexec/git-core/git-show-ref to git
-linking ./libexec/git-core/git-diff to git
-linking ./libexec/git-core/git-clean to git
-linking ./libexec/git-core/git-bundle to git
-linking ./libexec/git-core/git-check-mailmap to git
-linking ./libexec/git-core/git-describe to git
-linking ./libexec/git-core/git-branch to git
-linking ./libexec/git-core/git-checkout to git
-linking ./libexec/git-core/git-name-rev to git
-linking ./libexec/git-core/git-gc to git
-linking ./libexec/git-core/git-fetch to git
-linking ./libexec/git-core/git-whatchanged to git
-linking ./libexec/git-core/git-cherry to git
-linking ./libexec/git-core/git-reflog to git
-linking ./libexec/git-core/git-hash-object to git
-linking ./libexec/git-core/git-init-db to git
-linking ./libexec/git-core/git-rerere to git
-linking ./libexec/git-core/git-reset to git
-linking ./libexec/git-core/git-stripspace to git
-linking ./libexec/git-core/git-prune to git
-linking ./libexec/git-core/git-mktree to git
-linking ./libexec/git-core/git-unpack-file to git
-linking ./libexec/git-core/git-remote to git
-linking ./libexec/git-core/git-commit-tree to git
-linking ./libexec/git-core/git-symbolic-ref to git
-linking ./libexec/git-core/git-credential to git
-linking ./libexec/git-core/git-check-ignore to git
-linking ./libexec/git-core/git-shortlog to git
-linking ./libexec/git-core/git-fetch-pack to git
-linking ./libexec/git-core/git-clone to git
-linking ./libexec/git-core/git-mv to git
-linking ./libexec/git-core/git-read-tree to git
-linking ./libexec/git-core/git-merge-subtree to git
-linking ./libexec/git-core/git-ls-remote to git
-linking ./libexec/git-core/git-config to git
-linking ./libexec/git-core/git-cherry-pick to git
-linking ./libexec/git-core/git-merge to git
-linking ./libexec/git-core/git-prune-packed to git
-linking ./libexec/git-core/git-count-objects to git
-linking ./libexec/git-core/git-merge-base to git
-linking ./libexec/git-core/git-index-pack to git
-linking ./libexec/git-core/git-repack to git
-linking ./libexec/git-core/git-show to git
-linking ./libexec/git-core/git-fsck-objects to git
-linking ./libexec/git-core/git-format-patch to git
-linking ./libexec/git-core/git-bisect--helper to git
-linking ./libexec/git-core/git-upload-archive to git
-linking ./libexec/git-core/git-ls-files to git
-linking ./libexec/git-core/git-check-attr to git
-linking ./libexec/git-core/git-get-tar-commit-id to git
-linking ./libexec/git-core/git-remote-fd to git
-linking ./libexec/git-core/git-unpack-objects to git
-linking ./libexec/git-core/git-add to git
-linking ./libexec/git-core/git-check-ref-format to git
-linking ./libexec/git-core/git-merge-index to git
-linking ./libexec/git-core/git-pack-objects to git
-linking ./libexec/git-core/git-receive-pack to git
-linking ./libexec/git-core/git-pack-redundant to git
-linking ./libexec/git-core/git-shell to git-shell
-linking ./libexec/git-core/git-upload-pack to git-upload-pack
-Installation complete
-\"\"\"]]
-
-Running “/data/data/ga.androidterm/bin/busybox --install /data/data/ga.androidterm/bin” outputs the same error messages. I can run “touch /data/data/ga.androidterm/bin/hello” or “ln -s busybox /data/data/ga.androidterm/bin/hello” and it works.
-
-It seems Samsung includes a SELinux thing (dubbed KNOX) on the Galaxy devices. Alas, I failed to find a clear answer as to what an app developer is supposed to do to make something like this work. “ls -Z /system/bin” shows various contexts such as u:object_r:system_file:s0, u:object_r:mtp_exec_s0, u:object_r:time_daemon_exec:s0. “ls -Z /data/data/ga.androidterm/{bin,lib}” shows u:object_r:app_data_file:s0 for everything. “ls -Z /data/app-lib/ga.androidterm-1” shows u:object_r:app_library_file:s0 for everything.
-"""]]
diff --git a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_4_84aed89077d339f5471f113a1bcc4306._comment b/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_4_84aed89077d339f5471f113a1bcc4306._comment
deleted file mode 100644
index d9bf17774..000000000
--- a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_4_84aed89077d339f5471f113a1bcc4306._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="24.159.78.125"
- subject="comment 4"
- date="2014-05-23T14:39:18Z"
- content="""
-Did a previous version of git-annex work with this particular Android variant before?
-
-Try: `/data/data/ga.androidterm/bin/busybox --install -s /data/data/ga.androidterm/bin`
-
-That should make symlinks, rather than hardlinks. It seems that the policy is somehow denying creation of hard links, but allowing symlinks.
-"""]]
diff --git a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_5_e1e6707042e52a1f07276c27af651339._comment b/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_5_e1e6707042e52a1f07276c27af651339._comment
deleted file mode 100644
index c4272cdbb..000000000
--- a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_5_e1e6707042e52a1f07276c27af651339._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://johan.kiviniemi.name/"
- nickname="Johan"
- subject="comment 5"
- date="2014-05-23T18:06:49Z"
- content="""
-Ah, thanks, I didn’t realize busybox --install created hardlinks by default. It worked with -s and git-annex is adding files successfully now. I only got this phone recently, I can’t say whether it has ever worked on Samsung Galaxy devices with Android 4.3. Perhaps it hasn’t.
-
-The issue remains that Assistant claimed a file was added successfully while there was a problem with sha256sum.
-"""]]
diff --git a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_6_f28f65901c46d9543797f698b0eedb63._comment b/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_6_f28f65901c46d9543797f698b0eedb63._comment
deleted file mode 100644
index 01e386a75..000000000
--- a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_6_f28f65901c46d9543797f698b0eedb63._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.36"
- subject="comment 6"
- date="2014-05-23T20:20:05Z"
- content="""
-I tried to reproduce the assistant behaving that way, but after removing sha256sum from PATH, the assistant failed to add files and complained strenuously.
-"""]]
diff --git a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped.mdwn b/doc/bugs/Annex_thinks_file_exists_afer_being_dropped.mdwn
deleted file mode 100644
index 48be21cee..000000000
--- a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-#### What steps will reproduce the problem?
-
-I've posted some code here:
-   https://gist.github.com/4552036
-
-
-#### What is the expected output? What do you see instead?
-
-I think I've found three bugs.  If they aren't bugs then there is a usage issue that could do with some documentation improvements.
-
-Problem 1 - With 3 local annexes git-annex doesn't seem to search properly for them  (See code)
-
-Problem 2 - Even after a sync an annex thinks another (local) annex has a file, even after it has been dropped  (See code)
-
-SCARY bug - `whereis` seems to think that a locally dropped file still exists  (See code) 
-
-
-#### What version of git-annex are you using? On what operating system?
-
-git-annex version: 3.20130114
-
-OS: OSX 10.6.8
-
-
-#### Please provide any additional information below.
-
-> [[done]]; see comments --[[Joey]] 
diff --git a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_1_1d100441fd1ef529eb854b350fece9ee._comment b/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_1_1d100441fd1ef529eb854b350fece9ee._comment
deleted file mode 100644
index 7ddc9d2dd..000000000
--- a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_1_1d100441fd1ef529eb854b350fece9ee._comment
+++ /dev/null
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 1"
- date="2013-01-17T00:46:27Z"
- content="""
-* Problem 1 - With 3 local annexes git-annex doesn't seem to search properly for them (See code)
-
-While test1 thinks test2 and test3 have the file, they don't; it was just dropped from them. So the check that the other repos have the file is done correctly here, and it correctly refuses to drop it. The message is confusing in that it suggests the repositories are not available.
-
-* Problem 2 - Even after a sync an annex thinks another (local) annex has a file, even after it has been dropped (See code)
-
-I have not fully analized this, but it does not have anything to do with direct mode, it's a location log bookeeping problem.
-
-The merge where this happens looks like this:
-
-<pre>
- - 1358382328.617882s 0 620af8a6-603c-11e2-b332-f3ecf1856be4 (test2)
- + 1358382324.420048s 1 620af8a6-603c-11e2-b332-f3ecf1856be4 (test2)
-  +1358382324.572356s 1 622cf3b6-603c-11e2-bb55-4fe0f1a02dee (test3)
-++ 1358382328.472266s 0 622cf3b6-603c-11e2-bb55-4fe0f1a02dee (test3)
-</pre>
-
-The first 2 lines are the problem, and in this merge, a newer line is deleted leaving behind an older, now incorrect line. Union merge should not be deleting lines at all, so this appears to be a bug in the union merge code.
-
-* SCARY bug - whereis seems to think that a locally dropped file still exists (See code)
-
-This is a consequence of problem 2; the bad location data gets synced back to test2. Of course fsck will fix this, and the location log's is not relied on when dropping files, so this cannot result in data loss at least.
-"""]]
diff --git a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_2_166c459c2b27859cf457e17da685fe75._comment b/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_2_166c459c2b27859cf457e17da685fe75._comment
deleted file mode 100644
index 661386d8e..000000000
--- a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_2_166c459c2b27859cf457e17da685fe75._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 2"
- date="2013-01-17T01:35:44Z"
- content="""
-All right, the bug here involves differing changes to location log info for the same file being synced from two repositories and merged. Which probably explains why this bug was not noticed before.
-
-The union merge code generates a stream of data to feed into a single call to update-index. For each ref being merged, it calculates a union merge between that ref and the index. However, this means that the merge data for test2 is fed into update-index, and this is followed by the merge data for test3, which overwrites the previous merge data, causing the unique line from it to be lost.
-
-A fix, although perhaps not the most efficient way, is to run update-index once for each ref to merge, so that each merge builds on the one before. I've put this in place and can confirm problems #2 and #3 are fixed. Leaving open for the minor wording problem #1.
-
-Thanks for an excellent test case for this most unusual bug! (Which I should haskell-ize and add to the regression test suite, when I have time..)
-"""]]
diff --git a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_3_9d985b6e7973bfaaf8b4f5349d8c13ee._comment b/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_3_9d985b6e7973bfaaf8b4f5349d8c13ee._comment
deleted file mode 100644
index 7301dda92..000000000
--- a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_3_9d985b6e7973bfaaf8b4f5349d8c13ee._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 3"
- date="2013-01-17T01:45:59Z"
- content="""
-Fixed problem #1; it now no longer says to make available repositories where it has confirmed the file is not present.
-"""]]
diff --git a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_4_3e084cff454b95c7170c0225a53f0c30._comment b/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_4_3e084cff454b95c7170c0225a53f0c30._comment
deleted file mode 100644
index a4fc5813a..000000000
--- a/doc/bugs/Annex_thinks_file_exists_afer_being_dropped/comment_4_3e084cff454b95c7170c0225a53f0c30._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://a-or-b.myopenid.com/"
- ip="203.45.2.230"
- subject="comment 4"
- date="2013-01-17T01:57:06Z"
- content="""
-No problem.  Glad to be of assistance.
-
-This was actually a bug that I ran into whilst testing direct mode.  Quantifying the commands needed to reproduce was a bit of a challenge.  :-)
-
-"""]]
diff --git a/doc/bugs/Assistant_does_not_actually_check_newly_annex-added_files_into_git_until_daily_sanity_check.mdwn b/doc/bugs/Assistant_does_not_actually_check_newly_annex-added_files_into_git_until_daily_sanity_check.mdwn
deleted file mode 100644
index d4f58b44d..000000000
--- a/doc/bugs/Assistant_does_not_actually_check_newly_annex-added_files_into_git_until_daily_sanity_check.mdwn
+++ /dev/null
@@ -1,106 +0,0 @@
-What steps will reproduce the problem?
-
-Move any file into a git annex repository using "mv".  The symlink is created, content is stored in .git/annex, content may even be moved to other repos, but the symlink is not checked into git.  A day later, the daily sanity check will add and check-in the link.
-
-What is the expected output? What do you see instead?
-
-After adding content to git-annex, "git status" should show a clean repo with everything checked in.
-
-Instead it looks like this:
-
-    ~$ touch foobar
-    ~$ rm foobar
-    ~$ echo "foo" > bar
-    ~$ mv bar annex/Incoming/
-    ~$ cd annex
-    annex$ git status
-    # On branch master
-    # Untracked files:
-    #   (use "git add <file>..." to include in what will be committed)
-    #
-    #	Incoming/bar
-    nothing added to commit but untracked files present (use "git add" to track)
-    annex$ 
-
-
-
-I ran the assistant with the --debug option and this is what was in the daemon.log when this happened:
-
-    [2013-03-13 09:23:36 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","ls-files","--others","--exclude-standard","-z","--","/Users/ed/annex/Incoming/bar"]
-    [2013-03-13 09:23:37 EDT] read: lsof ["-F0can","+d","/Users/ed/annex/.git/annex/tmp/"]
-    [2013-03-13 09:23:39 EDT] Committer: Adding bar
-    
-    
-    (Recording state in git...)
-    (Recording state in git...)
-    (Recording state in git...)
-    (Recording state in git...)
-    add Incoming/bar (checksum...) recv: resource vanished (Connection reset by peer)
-    [2013-03-13 09:23:39 EDT] 127.0.0.1 GET /sidebar/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:19.0) Gecko/20100101 Firefox/19.0
-    [2013-03-13 09:23:40 EDT] 127.0.0.1 GET /sidebar/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:19.0) Gecko/20100101 Firefox/19.0
-
-
-What version of git-annex are you using? On what operating system?
-
-A fresh compile from last night (git hash fe2df85f0db08227556897db3b076ef321e4303a).  OS X Lion.
-
-
-Please provide any additional information below.
-
-I get the same effect when doing this with a newly created "testannex" repo with nothing in it but a newly created file -- I just haven't left the assistant running in a test repo all day to confirm that the file doesn't get checked in till the next daily sanity check.
-
-Here it is on a newly-created, empty repo:
-
-    testannex$ git init
-    Initialized empty Git repository in /Users/ed/testannex/.git/
-    testannex$ git annex init
-    init  ok
-    (Recording state in git...)
-    testannex$ git annex assistant --debug
-    [2013-03-13 09:31:10 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","show-ref","git-annex"]
-    [2013-03-13 09:31:10 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","show-ref","--hash","refs/heads/git-annex"]
-    [2013-03-13 09:31:10 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","log","refs/heads/git-annex..4aeceaff629c83c35c1244da9eeeac4b7c228fef","--oneline","-n1"]
-    [2013-03-13 09:31:10 EDT] chat: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","cat-file","--batch"]
-    testannex$ cd
-    ~$ echo "foo" > bar
-    ~$ mv bar testannex/
-    ~$ cd testannex/
-    testannex$ git status
-    # On branch master
-    #
-    # Initial commit
-    #
-    # Untracked files:
-    #   (use "git add <file>..." to include in what will be committed)
-    #
-    #	bar
-    nothing added to commit but untracked files present (use "git add" to track)
-
-
-    (meanwhile.....)
-
-    ~$ cd testannex/.git/annex/
-    annex$ tail -f daemon.log 
-    [2013-03-13 09:31:10 EDT] TransferWatcher: watching for transfers
-    [2013-03-13 09:31:10 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","show-ref","git-annex"]
-    [2013-03-13 09:31:10 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","show-ref","--hash","refs/heads/git-annex"]
-    [2013-03-13 09:31:10 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","log","refs/heads/git-annex..4aeceaff629c83c35c1244da9eeeac4b7c228fef","--oneline","-n1"]
-    [2013-03-13 09:31:10 EDT] Merger: watching /Users/ed/testannex/.git/refs
-    [2013-03-13 09:31:10 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-    [2013-03-13 09:31:10 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-    (scanning...) [2013-03-13 09:31:10 EDT] Watcher: Performing startup scan
-    [2013-03-13 09:31:10 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","ls-files","--deleted","-z","--","/Users/ed/testannex"]
-    (started...) [2013-03-13 09:31:10 EDT] Watcher: watching .
-    [2013-03-13 09:31:48 EDT] read: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","ls-files","--others","--exclude-standard","-z","--","/Users/ed/testannex/bar"]
-    [2013-03-13 09:31:49 EDT] read: lsof ["-F0can","+d","/Users/ed/testannex/.git/annex/tmp/"]
-    [2013-03-13 09:31:51 EDT] Committer: Adding bar
-    
-    add bar [2013-03-13 09:31:51 EDT] chat: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","check-attr","-z","--stdin","annex.backend","annex.numcopies","--"]
-    (checksum...) [2013-03-13 09:31:51 EDT] chat: git ["--git-dir=/Users/ed/testannex/.git","--work-tree=/Users/ed/testannex","cat-file","--batch"]
-
-> This bug affected OSX when indirect mode repositories were used.
-> Direct mode repositories were ok.
-> I expected to get an event from fsevents when I made the symlink,
-> and this event is not arriving (or at least not always). Switched
-> the code to use the same method for fsevents as for kqueue and that fixed
-> it. [[done]] --[[Joey]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default.mdwn b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default.mdwn
deleted file mode 100644
index c3810350b..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-### Please describe the problem.
-
-I'm trying to use the assistant to replicate the basic dropbox functionality of having a synced folder between two machines. Instead of actually syncing file contents by default the assistant just creates broken symlinks.
-
-### What steps will reproduce the problem?
-
-I've setup two repositories with each other as ssh remotes and ran the assistant on each after setting them in direct mode. I can create files on each of the repositories and have them show up on the other but all that shows up is a broken link. Actual contents don't get transferred. If I do a "git annex get" I can get the contents just fine. I tried setting annex.numcopies to 2 and that didn't work either.
-
-What I'm missing here is some setting to tell the assistant "sync the contents of every new file". What it's doing instead is unacceptable. If I have the file in both repositories and change it in one, the other repository gets it's previous version of the file replaced by a broken symlink. From my point of view for the assistant to be a dropbox replacement it should never, under any circumstances, create a broken symlink in the sync folder. I had understood that that's what direct mode was, but it's not behaving that way right now at least.
-
-### What version of git-annex are you using? On what operating system?
-
-My basic setup for testing is two Ubuntu 12.04 LTS machines running git-annex 4.20130501
-
-> [[done]], broken ~/.config/git-annex/program file, which is now detected
-> and worked around. --[[Joey]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_1_8577fdaa4d49e6241c4372b159694c9c._comment b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_1_8577fdaa4d49e6241c4372b159694c9c._comment
deleted file mode 100644
index 5e300d557..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_1_8577fdaa4d49e6241c4372b159694c9c._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 1"
- date="2013-05-20T13:57:59Z"
- content="""
-just fyi -- *broken* symlinks represent content which git-annex knows about, but is not present on that machine.  They are there even in direct mode.  In indirect mode, content which is present is represented by non-broken symlinks.  In direct mode, content which is present is actual files.
-
-I'm not sure why your setup doesn't work.  It seems as if it would, from your description of it.
-
-Your machines are successfully syncing their knowledge about what files exist (which is stored in git), but not actually transferring the content of those files.  That's why symlinks are showing up (to show that those files exist) but not the content.  I would think numcopies=2 would force that to happen.
-"""]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_2_027521e48283c68b39315bb8213f6e45._comment b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_2_027521e48283c68b39315bb8213f6e45._comment
deleted file mode 100644
index 9d5e07eb7..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_2_027521e48283c68b39315bb8213f6e45._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkx5V3MTbzCXS3J7Mn9FEq8M9bPPYMkAHY"
- nickname="Pedro"
- subject="comment 2"
- date="2013-05-20T14:37:37Z"
- content="""
-I know what the broken symlinks are I just don't think they should ever happen in a direct mode repository. They're an artifact of the traditional way git-annex was run but the assistant in direct mode should never use them. Right now if one of the repositories changes a file and another finds out that has happened but hasn't synced the content yet you lose access to your file. That's not acceptable in a file sync utility. Dropbox certainly doesn't do that. What git-annex should do in this case is use the knowledge of the updated file to run a sync but before it can complete it maintain the file at its previous version. By definition direct mode should not be deleting my files and replacing them with symlinks, it should only replace existing files with newer versions of those same files.
-
-I also don't know why numcopies didn't work but it shouldn't be needed at all. What I want to do is to tell the assistant \"sync the contents of every file into this repository as soon as you can from whatever remote you happen to be able to copy it from\". I couldn't find a setting that would do that though.
-"""]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_3_fd8f6938596aace60b04fb35c4069e37._comment b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_3_fd8f6938596aace60b04fb35c4069e37._comment
deleted file mode 100644
index 65bccfb76..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_3_fd8f6938596aace60b04fb35c4069e37._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-05-20T16:06:50Z"
- content="""
-If git-annex did not update its working tree until all files referenced in it had been downloaded, then it would be possible, if you have a lot of files, for changes to take a long time, or forever, to show up. I prefer the current behavior. 
-
-In any case, is this bug report about the mechanics of how the assistant choses to update its working tree, or is it about your configuration of two repositories that are not syncing with one-another? Conflating two entirely separate issues in one bug report is a good way to add so much noise to it that nothing gets done.
-"""]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_4_ca908021ab5a2a50fd0d4a7e8d12498f._comment b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_4_ca908021ab5a2a50fd0d4a7e8d12498f._comment
deleted file mode 100644
index 035606957..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_4_ca908021ab5a2a50fd0d4a7e8d12498f._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 4"
- date="2013-05-20T16:08:14Z"
- content="""
-The broken symlinks are important to me, because they represent content in archive directories which is intentionally not present, and they allow me to prompt git annex to retrieve that content by dragging and dropping them out of the archive subdirectory.  I'm not sure what the issue is with transferring content for you though.
-
-"""]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_5_73532556cfc354ad5f37a3f3a048fb32._comment b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_5_73532556cfc354ad5f37a3f3a048fb32._comment
deleted file mode 100644
index 008ed98cb..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_5_73532556cfc354ad5f37a3f3a048fb32._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-05-20T16:09:47Z"
- content="""
-\"What I want to do is to tell the assistant \"sync the contents of every file into this repository as soon as you can from whatever remote you happen to be able to copy it from\". I couldn't find a setting that would do that though.\"
-
-The reason you cannot find a setting that does this, is because that is the default behavior of the assistent, when correctly configured.
-
-Since it syncs files for everyone else, I conclude there must be an error in your configuration. You need to descibe it in detail and/or enable debugging and paste a debug log.
-"""]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_6_ced397b9e6119a0798a282ee07e885df._comment b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_6_ced397b9e6119a0798a282ee07e885df._comment
deleted file mode 100644
index 61d5f9bd2..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_6_ced397b9e6119a0798a282ee07e885df._comment
+++ /dev/null
@@ -1,61 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 6"
- date="2013-05-20T16:22:18Z"
- content="""
-Here is a simple example of setting up 2 repositories in the way the bug reporter describes here and on IRC. As you can see, the assistant syncs file content without any configuration:
-
-[[!format sh \"\"\"
-joey@gnu:~/tmp/test>mkdir 1 2
-joey@gnu:~/tmp/test>cd 1; git init; git-annex init; git annex direct; echo \"file added to 1\" > file_from_1; cd ..
-Initialized empty Git repository in /home/joey/tmp/test/1/.git/
-init  ok
-(Recording state in git...)
-commit  
-# On branch master
-#
-# Initial commit
-#
-nothing to commit (create/copy files and use \"git add\" to track)
-ok
-direct  ok
-joey@gnu:~/tmp/test>cd 2; git init; git-annex init; git annex direct; echo \"file added to 2\" > file_from_2; cd ..
-Initialized empty Git repository in /home/joey/tmp/test/2/.git/
-init  ok
-(Recording state in git...)
-commit  
-# On branch master
-#
-# Initial commit
-#
-nothing to commit (create/copy files and use \"git add\" to track)
-ok
-direct  ok
-joey@gnu:~/tmp/test>cd 1; git remote add 2 ssh://localhost/~joey/tmp/test/2; git annex assistant; cd ..
-joey@gnu:~/tmp/test>cd 2; git remote add 1 ssh://localhost/~joey/tmp/test/1; git annex assistant; cd ..
-(merging synced/git-annex into git-annex...)
-(Recording state in git...)
-joey@gnu:~/tmp/test>cd 1
-joey@gnu:~/tmp/test/1>ls
-file_from_1
-joey@gnu:~/tmp/test/1>ls
-file_from_1  file_from_2
-joey@gnu:~/tmp/test/1>cat file_from_2
-file added to 2
-joey@gnu:~/tmp/test/1>cd ..
-joey@gnu:~/tmp/test>cd 2
-joey@gnu:~/tmp/test/2>cat file_from_1
-file added to 1
-joey@gnu:~/tmp/test/2>rm file_from_2
-joey@gnu:~/tmp/test/2>cd ..
-joey@gnu:~/tmp/test>cd 1
-joey@gnu:~/tmp/test/1>ls
-file_from_1
-joey@gnu:~/tmp/test/1>date > newfile
-joey@gnu:~/tmp/test/1>cd ..
-joey@gnu:~/tmp/test>cd 2
-joey@gnu:~/tmp/test/2>cat newfile
-Mon May 20 12:20:24 JEST 2013
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_7_8acb66850e5db8337cf3f2b2dd236ccc._comment b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_7_8acb66850e5db8337cf3f2b2dd236ccc._comment
deleted file mode 100644
index 8bd901688..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_7_8acb66850e5db8337cf3f2b2dd236ccc._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkx5V3MTbzCXS3J7Mn9FEq8M9bPPYMkAHY"
- nickname="Pedro"
- subject="comment 7"
- date="2013-05-20T19:52:30Z"
- content="""
-Your example is pretty much what I've done. I'll enable a debug log as soon as possible. By the away \"git annex assistant --foreground\" still logs to .git/annex/daemon.log instead of stdout/stderr, which I assume was not the intended behavior.
-
-This bug was indeed about the assistant not syncing, the comments about the broken symlinks were just in response to edheil's comment. I can post a separate bug report about this but the reason I don't think this should be default behavior is that it breaks several simple uses of git-annex. One simple example is using it to store your configs across machines (things like .bashrc). If at any point the git-annex can't sync a file (a network problem or ssh breakage or whatever) but becomes aware of a file change (for example through xmpp) you now have a broken login shell. In general it breaks the user expectations of having a \"folder that just happens to also sync\" for something where his files randomly get replaced with strange broken things for odd technical reasons.
-"""]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_8_7eb530851ae6fa1a69813725c4e8fcec._comment b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_8_7eb530851ae6fa1a69813725c4e8fcec._comment
deleted file mode 100644
index 157923a1e..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_8_7eb530851ae6fa1a69813725c4e8fcec._comment
+++ /dev/null
@@ -1,59 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkx5V3MTbzCXS3J7Mn9FEq8M9bPPYMkAHY"
- nickname="Pedro"
- subject="comment 8"
- date="2013-05-20T19:59:22Z"
- content="""
-Here's the same example you posted being followed by me and showing the problem
-
-[[!format sh \"\"\"
-$mkdir 1 2
-$cd 1; git init; git-annex init; git annex direct; echo \"file added to 1\" > file_from_1; cd ..
-Initialized empty Git repository in /home/pedrocr/Hacks/test-git-annex/1/.git/
-init  ok
-(Recording state in git...)
-commit  
-# On branch master
-#
-# Initial commit
-#
-nothing to commit (create/copy files and use \"git add\" to track)
-ok
-direct  ok
-$cd 2; git init; git-annex init; git annex direct; echo \"file added to 2\" > file_from_2; cd ..
-Initialized empty Git repository in /home/pedrocr/Hacks/test-git-annex/2/.git/
-init  ok
-(Recording state in git...)
-commit  
-# On branch master
-#
-# Initial commit
-#
-nothing to commit (create/copy files and use \"git add\" to track)
-ok
-direct  ok
-$cd 1; git remote add 2 ssh://localhost/~pedrocr/Hacks/test-git-annex/2; git annex assistant; cd ..
-$cd 2; git remote add 1 ssh://localhost/~pedrocr/Hacks/test-git-annex/1; git annex assistant; cd ..
-(merging synced/git-annex into git-annex...)
-$cd 1
-$ls
-file_from_1  file_from_2
-$ls -la
-total 20
-drwxrwxr-x 3 pedrocr pedrocr 4096 May 20 20:57 .
-drwxrwxr-x 4 pedrocr pedrocr 4096 May 20 20:55 ..
--rw-r--r-- 1 pedrocr pedrocr   16 May 20 20:56 file_from_1
-lrwxrwxrwx 1 pedrocr pedrocr  180 May 20 20:57 file_from_2 -> .git/annex/objects/1P/8w/SHA256E-s16--b651aaa274225b617cb4d3033047ac6aee29dd6f2465f94ec38dc6630b7d48c8/SHA256E-s16--b651aaa274225b617cb4d3033047ac6aee29dd6f2465f94ec38dc6630b7d48c8
-drwxrwxr-x 9 pedrocr pedrocr 4096 May 20 20:57 .git
-$cd ..
-$cd 2
-$ls -la
-total 20
-drwxrwxr-x 3 pedrocr pedrocr 4096 May 20 20:57 .
-drwxrwxr-x 4 pedrocr pedrocr 4096 May 20 20:55 ..
-lrwxrwxrwx 1 pedrocr pedrocr  180 May 20 20:57 file_from_1 -> .git/annex/objects/qQ/x9/SHA256E-s16--cca8b6c2db480aa680e12c48f471a351de69978c7665fac5b63d9a765f4c16f4/SHA256E-s16--cca8b6c2db480aa680e12c48f471a351de69978c7665fac5b63d9a765f4c16f4
--rw-r--r-- 1 pedrocr pedrocr   16 May 20 20:56 file_from_2
-drwxrwxr-x 9 pedrocr pedrocr 4096 May 20 20:57 .git
-$
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_9_c7d51a26e1febc3894d02546940d64e5._comment b/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_9_c7d51a26e1febc3894d02546940d64e5._comment
deleted file mode 100644
index 2f5e2d43d..000000000
--- a/doc/bugs/Assistant_doesn__39__t_actually_sync_file_contents_by_default/comment_9_c7d51a26e1febc3894d02546940d64e5._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 9"
- date="2013-05-20T21:43:04Z"
- content="""
-Based on the log, it appears that you have a `~/.config/git-annex/program` file that contains \"/home/pedrocr/software/git-annex/git-annex.linux/git-annex\", but that is either not where git-annex is actually installed, or running that program
-(which git-annex does when it needs to transfer a file contents) fails.
-
-I am able to exactly replicate the failure to transfer file content, and the log output, when I set things up in that way.
-
-This would be consistent with you, for example, having previously installed git-annex from the standalone tarball, used it at least once, and then deleted that installation, and installed it from, say, a Ubuntu repository.
-
-I've put in a fix so if the programfile is wrong, git-annex just tries PATH.
-
-(BTW, I do not advocate storing config files in the git annex. Small files that you want to have fully versioned are best stored in git. The git-annex assistant can still be used for syncing files that are checked into git in the regular way. See [[tips/replacing_Sparkleshare_or_dvcs-autosync_with_the_assistant]].)
-
-(git annex assistant --foreground intentionally logs to the log file, because otherwise the \"view logs\" page in the webapp can't show any logs.)
-"""]]
diff --git a/doc/bugs/Assistant_dropping_files_it_has_just_transferred_elsewhere_again.mdwn b/doc/bugs/Assistant_dropping_files_it_has_just_transferred_elsewhere_again.mdwn
deleted file mode 100644
index cb463ba07..000000000
--- a/doc/bugs/Assistant_dropping_files_it_has_just_transferred_elsewhere_again.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-Setup:
-
-* fresh install of Debian Wheezy on machines A & B, git-annex 4.20130227 pulled in from unstable
-* clone repository onto A & B and pair them (manual SSH key setup), and plug USB backup drive, U, into A
-* U has repository group `backup` and preferred content string `standard`
-* A & B have repository group `client` and preferred content string `present or include=subdir1/* or ...`
-
-Steps:
-
-* Add a new file to B
-* On B, `git annex copy -t A newfile`
-
-Expected:
-
-* File arrives at B and is copied to U by B's assistant
-* File remains on B
-
-Actual:
-
-* File arrives on B and is copied to U
-* File is dropped from B
-
-Seems like a resurfacing of [[forum/assistant_overzealously_moving_stuff_to_other_repos]]?  Thanks.
-
-> 4.20130227 used a regex library that was broken, at least for certian
-> filenames. I suspect that's what'd going on here. [[done]] --[[Joey]]
diff --git a/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn b/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn
deleted file mode 100644
index d3f539431..000000000
--- a/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-*What steps will reproduce the problem?*
-
-Log in to X, have the DE start the assistant with --autostart. Then kill X with ctrl+alt+backspace and log back in once X comes back up.
-
-*What is the expected output? What do you see instead?*
-
-It enters an eternal loop, quickly using up all of the available RAM as well as 100% of CPU. Initially noticed because the computer became extremely sluggish, at which point the assistant was using up over 7G (of the available 8G) of RAM, and all of the available power on one of the CPU cores.
-
-Killing the assistant and then starting it again results in it working normally again.
-
-*What version of git-annex are you using? On what operating system?*
-
-git-annex version: 3.20121010 on Debian Sid (under GNOME3/Gnome-Shell in case that's relevant).
-I've also seen it happen on another computer in similar circumstances. That one on Debian Testing, with git-annex from sid (so same git-annex version). In this case X was restarted while running with /etc/init.d/gdm3 restart, and again the issue appeared after logging out and then back in.
-
-*Please provide any additional information below.*
-
-Given that the assistant isn't really using X directly, I suppose this could be due to losing its connection to the gpg and ssh agents as a side-effect of X being shut down. I'm not sure if it happens immediately after X being killed, or once I log back in again.
-
-> Reproduced. Root caused to a bug in the haskell dbus library, which I can
-> reproduce with 2 line test case; basically anything using connectSession
-> will do this when the dbus session goes away. Sent test case and
-> profiling data to library author to get it fixed, and have disabled
-> dbus in git-annex in the meantime. [[done]] --[[Joey]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log.mdwn b/doc/bugs/Assistant_lost_dbus_connection_spamming_log.mdwn
deleted file mode 100644
index a4a0b0221..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log.mdwn
+++ /dev/null
@@ -1,88 +0,0 @@
-## what
-After starting the assistant, daemon.log is being spammed with "accept: unsupported operation (Function not implemented)" due to dbus failing.
-
-## version
-[[!format sh """
-$ git-annex version
-git-annex version: 5.20131224-g6ca5271
-"""]]
-(The armel standalone)
-
-## question
-Is this detrimental to the assistant?
-
-## partial daemon.log
-[[!format sh """
-[2014-01-04 23:03:34 PST] main: starting assistant version 5.20131224-g6ca5271
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-[                                                                                                       
-2f0a 1i 4ld-eb0du1 s-t 0of4 a ai2dl3de: d0w;3a :tf3ca5hl  lPoiSnnT g]d  ibTrarecacknt sotfroey r mS/tcva
-olnifeingt/Egrirto-raMnensesxa g(e/ v=a r\"/rsuenrCvliiceenst/:h oumneasb/lger etgo/ .dceotnefrimgi/ngei 
-
-xi s tl o(sNto  dsbuucsh  cfoinlnee cotri odni;r efcatlolriyn)g)
-back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)"
-                                                                                                        
-Already up-to-date.                                                                                     
-accept: unsupported operation (Function not implemented)
-(scanning...) [2014-01-04 23:03:36 PST] Watcher: Performing startup scan                                
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-Everything up-to-date                                                                                   
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-accept: unsupported operation (Function not implemented)
-                                                                                                        
-  lost dbus connection; falling back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-"""]]
-
-> [[done]]; This turned out to not be dbus related, but the http server failing,
-> and I fixed that bug.
-> 
-> AFAICS the user running git-annex did not have their own dbus daemon
-> running, and that's why the low-volume dbus messages come up. 
-> Probably because this is an embedded device, and so no desktop
-> environment. git-annex only uses dbus for detecting network connection
-> changes and removable media mounts. None of which probably matter in an
-> embedded environment. --[[Joey]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_10_b47d543e06a1a243211a2fa0cb5d09a3._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_10_b47d543e06a1a243211a2fa0cb5d09a3._comment
deleted file mode 100644
index 6d0abe8c6..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_10_b47d543e06a1a243211a2fa0cb5d09a3._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 10"
- date="2014-03-10T17:34:56Z"
- content="""
-I've found the 1 second delay on failure to accept in the warp source code.
-
-It's using Network.Socket.accept, which uses accept4 with NONBLOCK by default, but can be built without `HAVE_ACCEPT4` and in that case uses `accept` with blocking.
-
-I've put in a patch to build network without accept4 support, and am rebuilding the arm autobuilder. This will take a while..
-
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_11_399c1e4455dce105df95414fe3ff939d._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_11_399c1e4455dce105df95414fe3ff939d._comment
deleted file mode 100644
index 665b9d8db..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_11_399c1e4455dce105df95414fe3ff939d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.154"
- subject="comment 11"
- date="2014-03-11T03:02:21Z"
- content="""
-Autobuild is now updated with the accept fix.
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_12_1cfdd76e751ee3726bd80359cfc85c47._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_12_1cfdd76e751ee3726bd80359cfc85c47._comment
deleted file mode 100644
index fe19bf87e..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_12_1cfdd76e751ee3726bd80359cfc85c47._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.102"
- subject="ping?"
- date="2014-03-19T20:29:12Z"
- content="""
-Could either greg or Schnouki  please test with the current arm autobuild and see if you can connect to the webapp?
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_13_37aa5274874242861dc128efa1d29486._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_13_37aa5274874242861dc128efa1d29486._comment
deleted file mode 100644
index 5a99e0f55..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_13_37aa5274874242861dc128efa1d29486._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://schnouki.net/"
- nickname="Schnouki"
- subject="comment 13"
- date="2014-03-20T23:54:51Z"
- content="""
-Sorry for the delay (my laptop hard drive died so I was offline for a few days).
-
-Just tested git-annex 5.20140320 on my NAS and it works just fine! The webapp is running, I can connect to it, and there's no more spam in the daemon.log (except for the dbus message every minute, but that's not really a problem).
-
-Thanks a lot Joey! 
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_1_27fc71cadcbe6d5f146ffdb72b64689a._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_1_27fc71cadcbe6d5f146ffdb72b64689a._comment
deleted file mode 100644
index 8e87e86db..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_1_27fc71cadcbe6d5f146ffdb72b64689a._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.35"
- subject="comment 1"
- date="2014-01-05T18:26:10Z"
- content="""
-It's not clear to me that the accept message has anything to do with dbus.
-
-Does the accept message continue being logged past this point? Does the log contain \"unable to bind to local socket\"?
-
-Are you able to open the webapp? That's the part of git-annex that would use `accept()`..
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_2_0fb01ff463e7da6df2864186dc28f8e4._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_2_0fb01ff463e7da6df2864186dc28f8e4._comment
deleted file mode 100644
index dd46672a0..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_2_0fb01ff463e7da6df2864186dc28f8e4._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://grossmeier.net/"
- nickname="greg"
- subject="comment 2"
- date="2014-01-05T22:50:32Z"
- content="""
-The accept lines just keep coming and coming and coming and coming. About 58 of them between \"lost dbus connection...\" logs. There's interspersed \"Everything up-to-date\" and such.
-
-grep'ing for \"unable\" across all daemon log files gives me nothing.
-
-I haven't futzed with opening the webapp on the NAS yet. Correction: I just did try futzing and I fear there's something in the NAS software I need to figure out before I can do it successfully.
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_3_10fa5082909f5e568623cf6d901d5161._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_3_10fa5082909f5e568623cf6d901d5161._comment
deleted file mode 100644
index 249eb9c79..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_3_10fa5082909f5e568623cf6d901d5161._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.35"
- subject="comment 3"
- date="2014-01-06T16:22:49Z"
- content="""
-Is dbus running at all?
-
-What is the frequency of the messages?
-
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_4_f4e0fa25b7f466228622a6da02b157e7._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_4_f4e0fa25b7f466228622a6da02b157e7._comment
deleted file mode 100644
index 65e2f43f8..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_4_f4e0fa25b7f466228622a6da02b157e7._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="http://schnouki.net/"
- nickname="Schnouki"
- subject="comment 4"
- date="2014-03-06T00:10:09Z"
- content="""
-Same issue here: Arch chroot on a Synology DS413j NAS. Kernel 2.6.32.12 (by Synology), glibc 2.18-12.1, git-annex 5.20140227 (standalone armel). DBus is running as root, but not for the git-annex user.
-
-Ran it through strace, here is a hopefully relevant trace:
-
-    socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 11
-    fcntl64(11, F_GETFL)              = 0x2 (flags O_RDWR)
-    fcntl64(11, F_SETFL, O_RDWR|O_NONBLOCK) = 0
-    setsockopt(11, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
-    bind(11, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr(\"127.0.0.1\")}, 16) = 0
-    listen(11, 128)                   = 0
-    getsockname(11, {sa_family=AF_INET, sin_port=htons(50664), sin_addr=inet_addr(\"127.0.0.1\")}, [16]) = 0
-    ...
-    accept4(11, 0x40b7d3e0, [16], SOCK_NONBLOCK) = -1 ENOSYS (Function not implemented)
-
-According to `man accept`, `accept4()` is available since Linux 2.6.28 and glibc 2.10.
-
-And I can't connect to the webapp (neither to localhost using a SSH tunnel, nor to the LAN IP when using --listen=...).
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_5_6b9b87bfb8b94171b3dba51919fd1ceb._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_5_6b9b87bfb8b94171b3dba51919fd1ceb._comment
deleted file mode 100644
index d612cf35f..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_5_6b9b87bfb8b94171b3dba51919fd1ceb._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.146"
- subject="comment 5"
- date="2014-03-06T18:12:57Z"
- content="""
-Again the accept message does not seem to be related to dbus. A dbus client has no reason to do that; a web server does. The use of `O_NONBLOCK` with accept4 seems likely to be the culprit to me.
-
-How frequently is dbus mentioned in the log?
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_6_51f35f069c95a5ea7bd4dbab47b5702b._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_6_51f35f069c95a5ea7bd4dbab47b5702b._comment
deleted file mode 100644
index 478cb5a37..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_6_51f35f069c95a5ea7bd4dbab47b5702b._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://schnouki.net/"
- nickname="Schnouki"
- subject="comment 6"
- date="2014-03-07T08:52:12Z"
- content="""
-Agreed, the dbus and accept messages are probably unrelated. I just commented here because it's the same bug I'm encountering.
-
-The dbus message only appears once in the log (shortly after startup). The accept messages appears every second.
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_7_691661d902acbf9c11d713541d5d39e4._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_7_691661d902acbf9c11d713541d5d39e4._comment
deleted file mode 100644
index 46f147c7d..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_7_691661d902acbf9c11d713541d5d39e4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.146"
- subject="comment 7"
- date="2014-03-07T17:03:30Z"
- content="""
-Are you sure that the accept message happens every second? I don't see why the webapp would continue to try to bind a socket it it failed with a 1 second delay. (It does try 100 times if it fails, per [[!commit fe3009d83b08563875856152034e7c59a0c6ecca]], before ending with \"unable to bind to local socket\".)
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_8_ef559feb7b350f2014055680d087c2bc._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_8_ef559feb7b350f2014055680d087c2bc._comment
deleted file mode 100644
index 81af6d431..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_8_ef559feb7b350f2014055680d087c2bc._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.146"
- subject="comment 8"
- date="2014-03-07T17:16:41Z"
- content="""
-greg has confirmed that he can connect to the webapp, but it never replies to http requests. So, this could be the port being bound, but the accept failing.
-
-I don't know why it would retry the accept once per second, but this could be something in warp or the network library.
-"""]]
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_9_278b41aaa73a214b2b38881242a29b17._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_9_278b41aaa73a214b2b38881242a29b17._comment
deleted file mode 100644
index e43f03f03..000000000
--- a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_9_278b41aaa73a214b2b38881242a29b17._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://schnouki.net/"
- nickname="Schnouki"
- subject="comment 9"
- date="2014-03-09T16:29:26Z"
- content="""
-I did some more testing today.
-
-I have this message when using either git-annex assistant or git-annex webapp. When running the webapp, I can connect to its port, but there's no response from git-annex (either from a browser or when using telnet to send a simple \"GET / HTTP/1.0\").
-
-The accept message comes every second, the dbus one very minute (didn't test long enough last time, sorry about that).
-"""]]
diff --git a/doc/bugs/Assistant_redirects_to_127.0.0.1_in_some_cases__44___although_used_remotely.mdwn b/doc/bugs/Assistant_redirects_to_127.0.0.1_in_some_cases__44___although_used_remotely.mdwn
deleted file mode 100644
index 1b1738aec..000000000
--- a/doc/bugs/Assistant_redirects_to_127.0.0.1_in_some_cases__44___although_used_remotely.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-### Please describe the problem.
-When I use git-annex webapp with a remote IP of a headless computer,
-I am sometimes redirected to a 127.0.0.1 address (with a different
-port as well)
-
-### What steps will reproduce the problem?
-1. Install git-annex as usual.
-2. Open git-annex assistant from a headless machine and access the
-webapp with the --listen option. (e.g. git annex webapp
---listen=xxx.yyy.zzz.www)
-3. Create your first local repository. Then create a second local
-repository.
-4. When assistant asks you if you want to merge these 2
-repositories, try to select the second option (to keep them
-separated).
-5. You are redirected from your remote IP to 127.0.0.1 to a new port number.
-
-(I also encountered the same error at another menu or function, but
-I don't remember where. Sorry.)
-
-### What version of git-annex are you using? On what operating system?
-4.20130815
-Ubuntu 13.10 64-bit (kernel 3.11.0-13-generic x86_64)
-
-### Please provide any additional information below.
-Please ask me for any additional information that may be useful.
-
-> This is a duplicate of [[Switching_repositories_in_webapp_on_a_remote_server_is_not_honoring_--listen_parameter]]
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux.mdwn b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux.mdwn
deleted file mode 100644
index a2f79aa6c..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux.mdwn
+++ /dev/null
@@ -1,75 +0,0 @@
-### Please describe the problem.
-
-I am experiencing a weird issue with any install I've had on this one (and only) ArchLinux machine: all of aur/git-annex 4.20130516-1, aur/git-annex-bin-4.20130909-1, aur/git-annex-standalone-4.20130909-1 and a Cabal install just stall when trying to create the initial Git annex repo in the webapp.
-
-When started, it offers me to create the annex in ~/annex/ or ~/Desktop/annex/, where ~ gets turned into /home/USER when I press “Make repository”, but nothing else happens. This is regardless of if that repo exists when I try to create it or start the webapp.
-
-If I start the webapp from an existing annex (now in ~/annex), it seems to work a bit better, but any other remote (SSH) server that I try to add fails. I just get a fleeting Bootstrap message box when I click “Check this server”, and nothing in the logs of eithr git annex webapp or the ssh logs of the server.
-
-If an annex exists, but I start the webapp from another directory, it just behaves as if none were found.
-
-Calls to git annex assistant --autostart complain that "Nothing listed in /home/omehani/.config/git-annex/autostart". I have checked the permissions on that directory, and tried deleting it to let git-annex recreate it, which it did, to no avail.
-
-
-### What steps will reproduce the problem?
-
-Install any of the git-annex packages available from AUR
-
-### What version of git-annex are you using? On what operating system?
-
-* up-to-date ArchLinux, Linux cancey 3.10.10-1-ARCH #1 SMP PREEMPT Fri Aug 30 11:30:06 CEST 2013 x86_64 GNU/Linux
-* aur/git-annex 4.20130516-1, aur/git-annex-bin-4.20130909-1, aur/git-annex-standalone-4.20130909-1 or through Cabal (on 2013-09-12)
-
-### Please provide any additional information below.
-
-The following is the output of webapp --debug. Nothing actually appears when trying to add/edit a repo.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-~/annex (master)$ git annex webapp --debug
-[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","show-ref","git-annex"]
-[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","log","refs/heads/git-annex..27c891f84f6ea7a10c68c0dd696ab84d88ef0cec","--oneline","-n1"]
-[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","log","refs/heads/git-annex..d0a1cb518045af01b443694aa2cd9af6386de38a","--oneline","-n1"]
-[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","log","refs/heads/git-annex..3ff23e23d74ace008b03143120e84f07e52ed8ee","--oneline","-n1"]
-[2013-09-16 10:26:55 EST] chat: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","cat-file","--batch"]
-[2013-09-16 10:26:55 EST] logging to /home/omehani/annex/.git/annex/daemon.log
-[2013-09-16 10:26:55 EST] logging to /home/omehani/annex/.git/annex/daemon.log
-Launching web browser on file:///home/omehani/annex/.git/annex/webapp.html
-START /usr/lib/firefox/firefox "/home/omehani/annex/.git/annex/webapp.html"
-
-(process:2699): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
-
-
-# End of transcript or log.
-"""]]
-
-Running git annex from a different directory.
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-~$ git annex webapp --debug
-Launching web browser on file:///tmp/webapp3934.html
-START /usr/lib/firefox/firefox "/tmp/webapp3934.html"
-
-(process:4008): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
-
-# End of transcript or log.
-"""]]
-
-Trying the autostart:
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-~$ git annex assistant --autostart --debug
-git-annex: Nothing listed in /home/omehani/.config/git-annex/autostart
-
-
-# End of transcript or log.
-"""]]
-
-> workaround is in place [[done]] --[[Joey]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_10_ec4a7388ea7106a953f599b664b37f1d._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_10_ec4a7388ea7106a953f599b664b37f1d._comment
deleted file mode 100644
index b0d0bdd55..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_10_ec4a7388ea7106a953f599b664b37f1d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://olivier.mehani.name/"
- nickname="olivier-mehani"
- subject="comment 10"
- date="2013-10-23T03:30:17Z"
- content="""
-Right, I actually have 4.20131023-g9898139. This makes more sense.
-"""]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_1_6a60c23850a5e2a7bba355e1317abc69._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_1_6a60c23850a5e2a7bba355e1317abc69._comment
deleted file mode 100644
index ed9ace976..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_1_6a60c23850a5e2a7bba355e1317abc69._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://olivier.mehani.name/"
- nickname="olivier-mehani"
- subject="comment 1"
- date="2013-09-16T01:27:14Z"
- content="""
-The version with which the following tests were run (installed with Cabal)
-
-[[!format sh \"\"\"
-git-annex version: 4.20130827
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus DNS
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_2_90b6ed232b2917b9fe041532284e1212._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_2_90b6ed232b2917b9fe041532284e1212._comment
deleted file mode 100644
index 703be9a84..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_2_90b6ed232b2917b9fe041532284e1212._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.14.105"
- subject="comment 2"
- date="2013-09-19T17:12:39Z"
- content="""
-Please send the content of the file /home/omehani/annex/.git/annex/daemon.log
-
-It would also help if you could better describe what happens. Perhaps make a screenshot?
-"""]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_3_5a89d79395d96c43d7d8a6fd9dc275f1._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_3_5a89d79395d96c43d7d8a6fd9dc275f1._comment
deleted file mode 100644
index 39f0f39b8..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_3_5a89d79395d96c43d7d8a6fd9dc275f1._comment
+++ /dev/null
@@ -1,248 +0,0 @@
-[[!comment format=mdwn
- username="http://olivier.mehani.name/"
- nickname="olivier-mehani"
- subject="comment 3"
- date="2013-09-30T01:29:50Z"
- content="""
-This is when having manually created the local annex, and trying to add a remote one. Surprisingly, I cannot find any reference to the remote server's address or username...
-
-	[2013-09-30 11:14:38 EST] main: starting assistant version 4.20130827
-	[2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"show-ref\",\"git-annex\"]
-	[2013-09-30 11:14:38 EST] read: xdg-open [\"file:///home/USERNAME/annex/.git/annex/webapp.html\"]
-	[2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-	[2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"log\",\"refs/heads/git-annex..9d87789505628a2da8347574cc600e358ff76107\",\"--oneline\",\"-n1\"]
-	[2013-09-30 11:14:38 EST] Merger: watching /home/USERNAME/annex/.git/refs
-	[2013-09-30 11:14:38 EST] TransferWatcher: watching for transfers
-	[2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"]
-	
-	  No known network monitor available through dbus; falling back to polling
-	[2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"]
-	(scanning...) [2013-09-30 11:14:38 EST] Watcher: Performing startup scan
-	[2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"ls-files\",\"--deleted\",\"-z\",\"--\",\"/home/USERNAME/annex\"]
-	(started...) [2013-09-30 11:14:38 EST] Watcher: watching .
-	[2013-09-30 11:14:38 EST] MountWatcher: Started DBUS service org.gtk.Private.UDisks2VolumeMonitor to monitor mount events.
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET / Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"show-ref\",\"git-annex\"]
-	[2013-09-30 11:14:39 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-	[2013-09-30 11:14:39 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"log\",\"refs/heads/git-annex..9d87789505628a2da8347574cc600e358ff76107\",\"--oneline\",\"-n1\"]
-	[2013-09-30 11:14:39 EST] chat: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"cat-file\",\"--batch\"]
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.ui.core.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.ui.widget.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.ui.mouse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.ui.sortable.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /notifier/transfers Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%200)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:39 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%200)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:40 EST] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:40 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:40 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:40 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:14:40 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /config Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%200)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:16 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:17 EST] 127.0.0.1 GET /sidebar/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:17 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:17 EST] 127.0.0.1 GET /sidebar/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /config/addrepository Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.ui.core.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.ui.widget.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.ui.mouse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.ui.sortable.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:19 EST] 127.0.0.1 GET /notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:20 EST] 127.0.0.1 GET /sidebar/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:20 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%201)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:20 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%201)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:20 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:20 EST] 127.0.0.1 GET /sidebar/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /config/repository/add/ssh Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%201)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /sidebar/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:32 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:32 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:32 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:32 EST] 127.0.0.1 GET /sidebar/NotificationId%203 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:32 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:32 EST] 127.0.0.1 GET /sidebar/NotificationId%203 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET / Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.ui.core.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.ui.widget.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.ui.mouse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.ui.sortable.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /notifier/transfers Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /sidebar/NotificationId%204 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%202)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /transfers/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%202)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /transfers/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:37 EST] 127.0.0.1 GET /sidebar/NotificationId%204 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /about Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /sidebar/NotificationId%204 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /transfers/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%202)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /sidebar/NotificationId%205 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:47 EST] 127.0.0.1 GET /sidebar/NotificationId%205 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /config Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /sidebar/NotificationId%206 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:50 EST] 127.0.0.1 GET /sidebar/NotificationId%206 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /config/addrepository Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.ui.widget.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.ui.mouse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.ui.core.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.ui.sortable.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%203)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /sidebar/NotificationId%207 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:51 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%203)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:52 EST] 127.0.0.1 GET /sidebar/NotificationId%207 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /config/repository/add/ssh Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%203)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /sidebar/NotificationId%207 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /sidebar/NotificationId%208 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:15:56 EST] 127.0.0.1 GET /sidebar/NotificationId%208 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 POST /config/repository/add/ssh Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /sidebar/NotificationId%208 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /sidebar/NotificationId%209 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:23 EST] 127.0.0.1 GET /sidebar/NotificationId%209 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 POST /config/repository/add/ssh Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /sidebar/NotificationId%209 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:44 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:45 EST] 127.0.0.1 GET /sidebar/NotificationId%2010 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:16:45 EST] 127.0.0.1 GET /sidebar/NotificationId%2010 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /shutdown Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /sidebar/NotificationId%2011 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:01 EST] 127.0.0.1 GET /sidebar/NotificationId%2011 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	[2013-09-30 11:17:02 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
-	
-
-"""]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_4_cdd26c71875428dbe3c100944a443d3f._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_4_cdd26c71875428dbe3c100944a443d3f._comment
deleted file mode 100644
index 4ee062a80..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_4_cdd26c71875428dbe3c100944a443d3f._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://olivier.mehani.name/"
- nickname="olivier-mehani"
- subject="comment 4"
- date="2013-09-30T01:31:26Z"
- content="""
-Hum, I'm not allowed to upload images:
-    git-annex-webapp1.png 		prohibited by allowed_attachments (user is not an admin) 
-"""]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_5_76242f5d6c815acd5bd58213bd8bb0fe._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_5_76242f5d6c815acd5bd58213bd8bb0fe._comment
deleted file mode 100644
index 28a0f7cc4..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_5_76242f5d6c815acd5bd58213bd8bb0fe._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.80"
- subject="comment 5"
- date="2013-09-30T16:13:20Z"
- content="""
-I see a lot of activity, which looks like you started up the webapp and it ran displaying stuff for some minutes. I see that you clicked on pages to eg, add a ssh repository.
-
-So, what then do you mean by saying it stalls? You have still not described whatever problem you are having.
-"""]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_6_10852171c0207ca61ea6df1082107353._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_6_10852171c0207ca61ea6df1082107353._comment
deleted file mode 100644
index 452a898f6..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_6_10852171c0207ca61ea6df1082107353._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://olivier.mehani.name/"
- nickname="olivier-mehani"
- subject="comment 6"
- date="2013-10-04T05:14:16Z"
- content="""
-Right. By “it stalls”, I mean I get redirected to the same dialog page (either the one asking for the path to the repo to create, or the one asking for the details of the remote to add) that I just validated, rather than going further in the process.
-"""]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_7_73e8a5696709f8154e63693ba5e569c3._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_7_73e8a5696709f8154e63693ba5e569c3._comment
deleted file mode 100644
index b6df85923..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_7_73e8a5696709f8154e63693ba5e569c3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="64.134.31.139"
- subject="comment 7"
- date="2013-10-14T16:18:01Z"
- content="""
-I just ran into this problem myself. Some investigating shows it is a problem with Yesod's XSRF token. Apparently yesod is not seeing the _token, or is seeing one it does not like. However, I verified in chromium inspector that the form post was including the token with the same value used on the page. Also, it would intermittently accept the form, if I kept posting it over and over again.
-
-It seems this must be a bug in yesod, or on something with how I'm using yesod, or possibly in deeper layers like WAI not seeing the form post include the token, but I have not been able to figure out what. As a workaround, since git-annex webapp does its own authentication and only listens to localhost, and so does not actually need XSRF protection, I am going to change it to bypass that.
-"""]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_8_392fc344e5833b0eb665fcd38f956b7a._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_8_392fc344e5833b0eb665fcd38f956b7a._comment
deleted file mode 100644
index 37acd5e9a..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_8_392fc344e5833b0eb665fcd38f956b7a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://olivier.mehani.name/"
- nickname="olivier-mehani"
- subject="comment 8"
- date="2013-10-23T03:00:58Z"
- content="""
-I just tried installing git-annex using Cabal today, but only got git-annex-4.20131002, even from source, which seems to predate your last comment, and no other branch seem to provide the yesod fix. Should I get the source from somewhere else than kitenet to try this out (if you think it is in shape to be tested)?
-"""]]
diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_9_9f0fc19a7fcaf7a5827e59e1495cf8c9._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_9_9f0fc19a7fcaf7a5827e59e1495cf8c9._comment
deleted file mode 100644
index 1e7aa897b..000000000
--- a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_9_9f0fc19a7fcaf7a5827e59e1495cf8c9._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://olivier.mehani.name/"
- nickname="olivier-mehani"
- subject="comment 9"
- date="2013-10-23T03:03:30Z"
- content="""
-Strike that. It actually works. I could create the ~/annex store, and adding a remote also seems to work (I'm on a hotel Wi-Fi at the moment, so I fear the ssh connection will fail, but nothing to do with git-annex).
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor.mdwn b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor.mdwn
deleted file mode 100644
index c8110eaa0..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### What steps will reproduce the problem?
-
-Run `git annex assistant`.
-
-
-### What is the expected output? What do you see instead?
-
-git-annex complains:
-
-     dbus failed; falling back to mtab polling (ClientError {clientErrorMessage =
-        "Call failed: The name org.gtk.Private.GduVolumeMonitor was not provided
-        by any .service files", clientErrorFatal = False})
-
-This is because the `gvfs-gdu-volume-monitor` daemon has been obsoleted and removed from GNOME 3.6 (maybe even earlier).
-
-git-annex should start using `gvfs-udisks2-volume-monitor` at bus name `org.gtk.Private.UDisks2VolumeMonitor`.
-
-Alternatively, git-annex should stop relying on any per-user services, and use kernel interfaces directly when available. (This way, monitoring could work even if the user wasn't logged in and/or didn't have a DBus session bus.)
-
-  * On all Linux kernels since 2.6.15, the `/proc/self/mounts` file is pollable – you can use **select(), poll() or epoll** to detect new mounted filesystems, without having to rely on periodic checks. (Run `findmnt -p` to see it in action.)
-
-  * On BSD systems, kqueue on `/etc/mtab`.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex 3.20130102 on Linux 3.7.1, GNOME 3.7
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_10_0e1db417a5815ea903c1f7ccd07308c4._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_10_0e1db417a5815ea903c1f7ccd07308c4._comment
deleted file mode 100644
index 37e2613a2..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_10_0e1db417a5815ea903c1f7ccd07308c4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://nullroute.eu.org/~grawity/"
- nickname="Mantas"
- subject="comment 10"
- date="2013-01-10T21:51:29Z"
- content="""
-Works now.
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_1_28b0cfcba8902c9c16dbe6c4b07984c4._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_1_28b0cfcba8902c9c16dbe6c4b07984c4._comment
deleted file mode 100644
index fa71012d2..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_1_28b0cfcba8902c9c16dbe6c4b07984c4._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 1"
- date="2013-01-10T17:28:30Z"
- content="""
-Thanks, excellent info. 
-
-Any chance you could provide dbus-monitor output for the events generated by org.gtk.Private.UDisks2VolumeMonitor when a volume is mounted, and unmounted?
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_2_952b3f78da756ff5f89235db94bec67f._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_2_952b3f78da756ff5f89235db94bec67f._comment
deleted file mode 100644
index 2db95f8af..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_2_952b3f78da756ff5f89235db94bec67f._comment
+++ /dev/null
@@ -1,53 +0,0 @@
-[[!comment format=mdwn
- username="http://nullroute.eu.org/~grawity/"
- nickname="Mantas"
- subject="comment 2"
- date="2013-01-10T17:38:47Z"
- content="""
-When mounted:
-
-<pre>
-signal path=/org/gtk/Private/RemoteVolumeMonitor; interface=org.gtk.Private.RemoteVolumeMonitor; member=MountAdded
-   string \"org.gtk.Private.UDisks2VolumeMonitor\"
-   string \"0x1971ab0\"
-   struct {
-      string \"0x1971ab0\"
-      string \"grawpqi\"
-      string \". GThemedIcon media-removable media\"
-      string \". GThemedIcon media-removable-symbolic media-removable media\"
-      string \"\"
-      string \"file:///run/media/grawity/grawpqi\"
-      boolean true
-      string \"0x18f4e50\"
-      array [
-      ]
-      string \"gvfs.time_detected_usec.1357838999510252\"
-      array [
-      ]
-   }
-</pre>
-
-When unmounted:
-
-<pre>
-signal path=/org/gtk/Private/RemoteVolumeMonitor; interface=org.gtk.Private.RemoteVolumeMonitor; member=MountRemoved
-   string \"org.gtk.Private.UDisks2VolumeMonitor\"
-   string \"0x1971910\"
-   struct {
-      string \"0x1971910\"
-      string \"grawpqi\"
-      string \". GThemedIcon media-removable media\"
-      string \". GThemedIcon media-removable-symbolic media-removable media\"
-      string \"\"
-      string \"file:///run/media/grawity/grawpqi\"
-      boolean true
-      string \"\"
-      array [
-      ]
-      string \"gvfs.time_detected_usec.1357839107487969\"
-      array [
-      ]
-   }
-</pre>
-
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_3_d86aba42d014c4b4f708dcb5fe86e055._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_3_d86aba42d014c4b4f708dcb5fe86e055._comment
deleted file mode 100644
index 6256086c7..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_3_d86aba42d014c4b4f708dcb5fe86e055._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 3"
- date="2013-01-10T19:08:50Z"
- content="""
-I've just committed support for using the new name. I've not been able to test it yet, as I don't have a new enough gnome here. Any testing you can do much appreciated.
-
-Leaving this bug open until it gets tested, and also because it's certainly appealing to just use poll rather than this fragile dbus stuff. And in any case, should add OSX support.
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_4_9aaf296ef53da317d6dc6728705d5c56._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_4_9aaf296ef53da317d6dc6728705d5c56._comment
deleted file mode 100644
index 6df6f40f2..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_4_9aaf296ef53da317d6dc6728705d5c56._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://nullroute.eu.org/~grawity/"
- nickname="Mantas"
- subject="comment 4"
- date="2013-01-10T19:41:22Z"
- content="""
-I'm getting:
-
-    dbus failed; falling back to mtab polling (ClientError {clientErrorMessage =
-        \"Call failed: The name org.gtk.Private.RemoteVolumeMonitor was not provided
-        by any .service files\", clientErrorFatal = False})
-
-The volume monitor's bus name should be `org.gtk.Private.UDisks2VolumeMonitor`.
-
-`org.gtk.Private.RemoteVolumeMonitor` is the interface name, which all Gvfs monitors implement.
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_5_0d5f8a05a1505660f7ff1bc4ac6ff271._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_5_0d5f8a05a1505660f7ff1bc4ac6ff271._comment
deleted file mode 100644
index 22b1d923c..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_5_0d5f8a05a1505660f7ff1bc4ac6ff271._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="oops.."
- date="2013-01-10T20:09:56Z"
- content="""
-Think I have the right name in there now.
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_6_3dfdfd49597c85575cb689adb70d2de6._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_6_3dfdfd49597c85575cb689adb70d2de6._comment
deleted file mode 100644
index 3320b77da..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_6_3dfdfd49597c85575cb689adb70d2de6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://nullroute.eu.org/~grawity/"
- nickname="Mantas"
- subject="comment 6"
- date="2013-01-10T20:13:42Z"
- content="""
-It doesn't look completely right – the *service* name (in `checkMountMonitor`) is `org.gtk.Private.UDisks2VolumeMonitor`, but the *interface* name (in `mountChanged`) is `org.gtk.Private.RemoteVolumeMonitor`, so the fix changed too much.
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_7_943a446c60ed9d7d4f240ba7f00fe925._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_7_943a446c60ed9d7d4f240ba7f00fe925._comment
deleted file mode 100644
index 8f0cd64cc..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_7_943a446c60ed9d7d4f240ba7f00fe925._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="been a while.."
- date="2013-01-10T20:19:33Z"
- content="""
-Think I have it now.
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_8_9563859850fb40b1cc2c20c516c12960._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_8_9563859850fb40b1cc2c20c516c12960._comment
deleted file mode 100644
index 0a3ae95a7..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_8_9563859850fb40b1cc2c20c516c12960._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://nullroute.eu.org/~grawity/"
- nickname="Mantas"
- subject="build failure"
- date="2013-01-10T20:24:09Z"
- content="""
-<pre>
-$ cabal build
-Building git-annex-3.20130108...
-Preprocessing executable 'git-annex' for git-annex-3.20130108...
-[269 of 299] Compiling Assistant.Threads.MountWatcher ( Assistant/Threads/MountWatcher.hs,
-    dist/build/git-annex/git-annex-tmp/Assistant/Threads/MountWatcher.o )
-
-Assistant/Threads/MountWatcher.hs:122:17: Not in scope: `gvfs'
-</pre>
-"""]]
diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_9_cf6221c585ee3dbf039bdaea71842d9b._comment b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_9_cf6221c585ee3dbf039bdaea71842d9b._comment
deleted file mode 100644
index b5b66b8ea..000000000
--- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor/comment_9_cf6221c585ee3dbf039bdaea71842d9b._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 9"
- date="2013-01-10T20:44:37Z"
- content="""
-Realized that'd happen while away on a walk.. fixed now.
-
-"""]]
diff --git a/doc/bugs/Auto_update_not_updating_to_newest_version.mdwn b/doc/bugs/Auto_update_not_updating_to_newest_version.mdwn
deleted file mode 100644
index 186f39f1d..000000000
--- a/doc/bugs/Auto_update_not_updating_to_newest_version.mdwn
+++ /dev/null
@@ -1,72 +0,0 @@
-### Please describe the problem.
-
-I assume this is an assistant problem.
-
-My git-annex version on Mac OS seems to lag significantly behind current releases. I was today informed that it was updated to 5.20131221-g00d1673. Given that there are at least two newer versions I expected it to be updated to the newest one.
-
-There also seems no way to trigger a check for a new version.
-
-### What steps will reproduce the problem?
-
-Install on Mac. Observe over some days and see it not update.
-
-
-### What version of git-annex are you using? On what operating system?
-
-5.20131221-g00d1673,
-Mac OS
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-[2014-01-10 14:46:44 CET] main: starting assistant version 5.20131221-g00d1673
-[2014-01-10 14:46:44 CET] UpgradeWatcher: Finished upgrading git-annex to version 5.20131221-g00d1673 
-(scanning...) [2014-01-10 14:46:44 CET] Watcher: Performing startup scan
-(started...) [2014-01-10 14:47:02 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-10 14:47:02 CET] Watcher: Performing startup scan
-(started...) 
-[2014-01-10 14:48:44 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-10 14:48:44 CET] Watcher: Performing startup scan
-(started...) 
-[2014-01-10 14:49:35 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-10 14:49:35 CET] Watcher: Performing startup scan
-(started...) [2014-01-10 14:52:44 CET] UpgradeWatcher: Upgrading git-annex
-
-[2014-01-10 14:52:44 CET] main: starting assistant version 5.20131221-g00d1673
-[2014-01-10 14:52:44 CET] UpgradeWatcher: Finished upgrading git-annex to version 5.20131221-g00d1673 
-(scanning...) [2014-01-10 14:52:45 CET] Watcher: Performing startup scan
-(started...) [2014-01-10 14:53:13 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-10 14:53:13 CET] Watcher: Performing startup scan
-(started...) 
-[2014-01-15 15:22:29 CET] main: starting assistant version 5.20131221-g00d1673
-[2014-01-15 15:22:30 CET] Cronner: Consistency check in progress
-(scanning...) [2014-01-15 15:22:30 CET] Watcher: Performing startup scan
-(started...) 
-(scanning...) [2014-01-15 15:23:05 CET] Watcher: Performing startup scan
-[2014-01-15 15:23:05 CET] Committer: Committing changes to git
-(Recording state in git...)
-(started...) [2014-01-15 15:23:06 CET] main: Syncing with box.com 
-
-[2014-01-15 15:23:28 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-15 15:23:28 CET] Watcher: Performing startup scan
-(started...) [2014-01-15 16:23:30 CET] NetWatcherFallback: Syncing with box.com 
-[2014-01-15 17:23:31 CET] NetWatcherFallback: Syncing with box.com 
-[2014-01-15 18:23:32 CET] NetWatcherFallback: Syncing with box.com 
-[2014-01-16 16:42:15 CET] NetWatcherFallback: Syncing with box.com 
-[2014-01-16 16:56:33 CET] UpgradeWatcher: Upgrading git-annex
-
-[2014-01-16 16:56:33 CET] main: starting assistant version 5.20131221-g00d1673
-[2014-01-16 16:56:33 CET] Cronner: Consistency check in progress
-[2014-01-16 16:56:33 CET] UpgradeWatcher: Finished upgrading git-annex to version 5.20131221-g00d1673 
-(scanning...) [2014-01-16 16:56:33 CET] Watcher: Performing startup scan
-(started...) fsck dvi2bitmap ok
-[2014-01-16 16:58:14 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-16 16:58:14 CET] Watcher: Performing startup scan
-(started...) 
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; dup of [[bugs/git-annex_auto_upgrade_is_redundant]]. --[[Joey]]
diff --git a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_1_6f75569dc960ea5bc4d334b2b321ebf8._comment b/doc/bugs/Auto_update_not_updating_to_newest_version/comment_1_6f75569dc960ea5bc4d334b2b321ebf8._comment
deleted file mode 100644
index 7dd540eae..000000000
--- a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_1_6f75569dc960ea5bc4d334b2b321ebf8._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.43"
- subject="comment 1"
- date="2014-01-16T16:29:01Z"
- content="""
-What version of OSX?
-
-We can see it upgrading in the log, and 5.20131221 is consistent with this being OSX Lion, which no longer has an autobuilder, so won't be upgrading from that version unless someone steps up and makes a new autobuilder.
-
-It seems that the wrong version got into the .info file for Lion, which probably explains the repeated upgrade attempts since it thinks a newer version is available. I've fixed that.
-"""]]
diff --git a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_2_4f26cce07a9f37c79b166111db499ce1._comment b/doc/bugs/Auto_update_not_updating_to_newest_version/comment_2_4f26cce07a9f37c79b166111db499ce1._comment
deleted file mode 100644
index 73fc9dcb4..000000000
--- a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_2_4f26cce07a9f37c79b166111db499ce1._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk7iPiqWr3BVPLWEDvJhSSvcOqheLEbLNo"
- nickname="Dirk"
- subject="comment 2"
- date="2014-01-16T18:53:36Z"
- content="""
-Uup, sorry for forgetting this.
-
-This is happening on Mavericks for me.
-
-"""]]
diff --git a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_3_585bfcaa655b0e838f9b66a241d5ffc2._comment b/doc/bugs/Auto_update_not_updating_to_newest_version/comment_3_585bfcaa655b0e838f9b66a241d5ffc2._comment
deleted file mode 100644
index a0029b4e1..000000000
--- a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_3_585bfcaa655b0e838f9b66a241d5ffc2._comment
+++ /dev/null
@@ -1,2163 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk7iPiqWr3BVPLWEDvJhSSvcOqheLEbLNo"
- nickname="Dirk"
- subject="comment 3"
- date="2014-01-16T19:11:29Z"
- content="""
-Checking again after my last message it actually did upgrade now.
-
-For that I killed the running git-annex processes and then restarted git-annex via the dock icon. (I did this twice to see if something would happen the second time round.)
-
-Maybe this could be connected to your server side change? (Even so I am on 10.9.1.)
-
-The log now looks like follows (in case this is relevant):
-
-[[!format sh \"\"\"
-[2014-01-10 14:52:44 CET] main: starting assistant version 5.20131221-g00d1673
-[2014-01-10 14:52:44 CET] UpgradeWatcher: Finished upgrading git-annex to version 5.20131221-g00d1673 
-(scanning...) [2014-01-10 14:52:45 CET] Watcher: Performing startup scan
-(started...) [2014-01-10 14:53:13 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-10 14:53:13 CET] Watcher: Performing startup scan
-(started...) 
-[2014-01-15 15:22:29 CET] main: starting assistant version 5.20131221-g00d1673
-[2014-01-15 15:22:30 CET] Cronner: Consistency check in progress
-(scanning...) [2014-01-15 15:22:30 CET] Watcher: Performing startup scan
-(started...) 
-(scanning...) [2014-01-15 15:23:05 CET] Watcher: Performing startup scan
-[2014-01-15 15:23:05 CET] Committer: Committing changes to git
-(Recording state in git...)
-(started...) [2014-01-15 15:23:06 CET] main: Syncing with box.com 
-
-[2014-01-15 15:23:28 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-15 15:23:28 CET] Watcher: Performing startup scan
-(started...) [2014-01-15 16:23:30 CET] NetWatcherFallback: Syncing with box.com 
-[2014-01-15 17:23:31 CET] NetWatcherFallback: Syncing with box.com 
-[2014-01-15 18:23:32 CET] NetWatcherFallback: Syncing with box.com 
-[2014-01-16 16:42:15 CET] NetWatcherFallback: Syncing with box.com 
-[2014-01-16 16:56:33 CET] UpgradeWatcher: Upgrading git-annex
-
-[2014-01-16 16:56:33 CET] main: starting assistant version 5.20131221-g00d1673
-[2014-01-16 16:56:33 CET] Cronner: Consistency check in progress
-[2014-01-16 16:56:33 CET] UpgradeWatcher: Finished upgrading git-annex to version 5.20131221-g00d1673 
-(scanning...) [2014-01-16 16:56:33 CET] Watcher: Performing startup scan
-(started...) fsck dvi2bitmap ok
-[2014-01-16 16:58:14 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-16 16:58:14 CET] Watcher: Performing startup scan
-(started...) [2014-01-16 17:58:14 CET] NetWatcherFallback: Syncing with box.com 
-[2014-01-16 19:26:14 CET] NetWatcherFallback: Syncing with box.com 
-
-[2014-01-16 19:58:39 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-16 19:58:39 CET] Watcher: Performing startup scan
-(started...) --2014-01-16 19:58:40--  https://downloads.kitenet.net/git-annex/OSX/current/10.9_Mavericks/git-annex.dmg
-Resolving downloads.kitenet.net... 80.68.85.49, 2001:41c8:125:49::10
-Connecting to downloads.kitenet.net|80.68.85.49|:443... connected.
-HTTP request sent, awaiting response... 200 OK
-Length: 28756861 (27M) [application/x-apple-diskimage]
-Saving to: ‘/Users/kraft/annex/.git/annex/tmp/SHA256E-s28756861--4bea2d816a701dbfc88eada2288019c92c2774ee605e4ddfa62c4dd7655e53a1.dmg’
-
-     0K .......... .......... .......... .......... ..........  0% 3.04M 9s
-    50K .......... .......... .......... .......... ..........  0% 1.65M 13s
-   100K .......... .......... .......... .......... ..........  0% 10.7M 9s
-   150K .......... .......... .......... .......... ..........  0% 1.85M 11s
-   200K .......... .......... .......... .......... ..........  0% 11.1M 9s
-   250K .......... .......... .......... .......... ..........  1% 2.05M 10s
-   300K .......... .......... .......... .......... ..........  1% 10.4M 9s
-   350K .......... .......... .......... .......... ..........  1% 11.5M 8s
-   400K .......... .......... .......... .......... ..........  1% 1.07M 10s
-   450K .......... .......... .......... .......... ..........  1% 29.1M 9s
-   500K .......... .......... .......... .......... ..........  1% 36.0M 8s
-   550K .......... .......... .......... .......... ..........  2% 1.83M 9s
-   600K .......... .......... .......... .......... ..........  2% 10.4M 8s
-   650K .......... .......... .......... .......... ..........  2% 15.1M 8s
-   700K .......... .......... .......... .......... ..........  2% 10.6M 7s
-   750K .......... .......... .......... .......... ..........  2% 2.53M 8s
-   800K .......... .......... .......... .......... ..........  3% 7.05M 7s
-   850K .......... .......... .......... .......... ..........  3% 10.5M 7s
-   900K .......... .......... .......... .......... ..........  3% 2.72M 7s
-   950K .......... .......... .......... .......... ..........  3% 9.06M 7s
-  1000K .......... .......... .......... .......... ..........  3% 10.7M 7s
-  1050K .......... .......... .......... .......... ..........  3% 2.76M 7s
-  1100K .......... .......... .......... .......... ..........  4% 14.5M 7s
-  1150K .......... .......... .......... .......... ..........  4% 8.24M 6s
-  1200K .......... .......... .......... .......... ..........  4% 8.30M 6s
-  1250K .......... .......... .......... .......... ..........  4% 3.06M 6s
-  1300K .......... .......... .......... .......... ..........  4% 10.7M 6s
-  1350K .......... .......... .......... .......... ..........  4% 10.4M 6s
-  1400K .......... .......... .......... .......... ..........  5% 10.2M 6s
-  1450K .......... .......... .......... .......... ..........  5% 3.17M 6s
-  1500K .......... .......... .......... .......... ..........  5% 11.5M 6s
-  1550K .......... .......... .......... .......... ..........  5% 10.5M 6s
-  1600K .......... .......... .......... .......... ..........  5% 8.30M 6s
-  1650K .......... .......... .......... .......... ..........  6% 3.13M 6s
-  1700K .......... .......... .......... .......... ..........  6% 10.6M 6s
-  1750K .......... .......... .......... .......... ..........  6% 13.3M 6s
-  1800K .......... .......... .......... .......... ..........  6% 10.8M 5s
-  1850K .......... .......... .......... .......... ..........  6% 3.27M 5s
-  1900K .......... .......... .......... .......... ..........  6% 10.9M 5s
-  1950K .......... .......... .......... .......... ..........  7% 10.5M 5s
-  2000K .......... .......... .......... .......... ..........  7% 8.27M 5s
-  2050K .......... .......... .......... .......... ..........  7% 14.3M 5s
-  2100K .......... .......... .......... .......... ..........  7% 1.19M 6s
-  2150K .......... .......... .......... .......... ..........  7% 34.9M 5s
-  2200K .......... .......... .......... .......... ..........  8% 37.0M 5s
-  2250K .......... .......... .......... .......... ..........  8% 49.4M 5s
-  2300K .......... .......... .......... .......... ..........  8% 39.9M 5s
-  2350K .......... .......... .......... .......... ..........  8% 32.8M 5s
-  2400K .......... .......... .......... .......... ..........  8% 1.82M 5s
-  2450K .......... .......... .......... .......... ..........  8% 11.3M 5s
-  2500K .......... .......... .......... .......... ..........  9% 13.8M 5s
-  2550K .......... .......... .......... .......... ..........  9% 10.4M 5s
-  2600K .......... .......... .......... .......... ..........  9% 10.6M 5s
-  2650K .......... .......... .......... .......... ..........  9% 3.97M 5s
-  2700K .......... .......... .......... .......... ..........  9% 10.3M 5s
-  2750K .......... .......... .......... .......... ..........  9% 14.0M 5s
-  2800K .......... .......... .......... .......... .......... 10% 8.23M 5s
-  2850K .......... .......... .......... .......... .......... 10% 10.6M 5s
-  2900K .......... .......... .......... .......... .......... 10% 3.91M 5s
-  2950K .......... .......... .......... .......... .......... 10% 13.6M 5s
-  3000K .......... .......... .......... .......... .......... 10% 10.1M 5s
-  3050K .......... .......... .......... .......... .......... 11% 10.8M 5s
-  3100K .......... .......... .......... .......... .......... 11% 13.5M 4s
-  3150K .......... .......... .......... .......... .......... 11% 4.19M 4s
-  3200K .......... .......... .......... .......... .......... 11% 8.83M 4s
-  3250K .......... .......... .......... .......... .......... 11% 13.7M 4s
-  3300K .......... .......... .......... .......... .......... 11% 10.5M 4s
-  3350K .......... .......... .......... .......... .......... 12% 10.8M 4s
-  3400K .......... .......... .......... .......... .......... 12% 5.08M 4s
-  3450K .......... .......... .......... .......... .......... 12% 11.6M 4s
-  3500K .......... .......... .......... .......... .......... 12% 10.6M 4s
-  3550K .......... .......... .......... .......... .......... 12% 13.5M 4s
-  3600K .......... .......... .......... .......... .......... 12% 8.27M 4s
-  3650K .......... .......... .......... .......... .......... 13% 10.7M 4s
-  3700K .......... .......... .......... .......... .......... 13% 6.02M 4s
-  3750K .......... .......... .......... .......... .......... 13% 10.7M 4s
-  3800K .......... .......... .......... .......... .......... 13% 10.4M 4s
-  3850K .......... .......... .......... .......... .......... 13% 13.7M 4s
-  3900K .......... .......... .......... .......... .......... 14% 10.5M 4s
-  3950K .......... .......... .......... .......... .......... 14% 14.0M 4s
-  4000K .......... .......... .......... .......... .......... 14% 6.05M 4s
-  4050K .......... .......... .......... .......... .......... 14% 10.5M 4s
-  4100K .......... .......... .......... .......... .......... 14% 7.38M 4s
-  4150K .......... .......... .......... .......... .......... 14% 13.9M 4s
-  4200K .......... .......... .......... .......... .......... 15% 11.5M 4s
-  4250K .......... .......... .......... .......... .......... 15% 14.2M 4s
-  4300K .......... .......... .......... .......... .......... 15% 10.7M 4s
-  4350K .......... .......... .......... .......... .......... 15% 10.7M 4s
-  4400K .......... .......... .......... .......... .......... 15% 4.59M 4s
-  4450K .......... .......... .......... .......... .......... 16% 11.6M 4s
-  4500K .......... .......... .......... .......... .......... 16% 14.0M 4s
-  4550K .......... .......... .......... .......... .......... 16% 10.6M 4s
-  4600K .......... .......... .......... .......... .......... 16% 9.94M 4s
-  4650K .......... .......... .......... .......... .......... 16% 15.3M 4s
-  4700K .......... .......... .......... .......... .......... 16% 10.4M 4s
-  4750K .......... .......... .......... .......... .......... 17% 8.48M 4s
-  4800K .......... .......... .......... .......... .......... 17% 10.1M 4s
-  4850K .......... .......... .......... .......... .......... 17% 10.5M 4s
-  4900K .......... .......... .......... .......... .......... 17% 10.7M 4s
-  4950K .......... .......... .......... .......... .......... 17% 13.3M 3s
-  5000K .......... .......... .......... .......... .......... 17% 10.6M 3s
-  5050K .......... .......... .......... .......... .......... 18% 10.3M 3s
-  5100K .......... .......... .......... .......... .......... 18% 13.7M 3s
-  5150K .......... .......... .......... .......... .......... 18% 10.6M 3s
-  5200K .......... .......... .......... .......... .......... 18% 8.59M 3s
-  5250K .......... .......... .......... .......... .......... 18% 14.2M 3s
-  5300K .......... .......... .......... .......... .......... 19% 11.0M 3s
-  5350K .......... .......... .......... .......... .......... 19% 10.3M 3s
-  5400K .......... .......... .......... .......... .......... 19% 11.4M 3s
-  5450K .......... .......... .......... .......... .......... 19% 12.0M 3s
-  5500K .......... .......... .......... .......... .......... 19% 13.8M 3s
-  5550K .......... .......... .......... .......... .......... 19% 10.7M 3s
-  5600K .......... .......... .......... .......... .......... 20% 8.55M 3s
-  5650K .......... .......... .......... .......... .......... 20% 10.7M 3s
-  5700K .......... .......... .......... .......... .......... 20% 15.1M 3s
-  5750K .......... .......... .......... .......... .......... 20% 10.7M 3s
-  5800K .......... .......... .......... .......... .......... 20% 11.2M 3s
-  5850K .......... .......... .......... .......... .......... 21% 10.9M 3s
-  5900K .......... .......... .......... .......... .......... 21% 10.7M 3s
-  5950K .......... .......... .......... .......... .......... 21% 14.8M 3s
-  6000K .......... .......... .......... .......... .......... 21% 8.90M 3s
-  6050K .......... .......... .......... .......... .......... 21% 11.0M 3s
-  6100K .......... .......... .......... .......... .......... 21% 11.2M 3s
-  6150K .......... .......... .......... .......... .......... 22% 10.4M 3s
-  6200K .......... .......... .......... .......... .......... 22% 11.4M 3s
-  6250K .......... .......... .......... .......... .......... 22% 14.2M 3s
-  6300K .......... .......... .......... .......... .......... 22% 10.6M 3s
-  6350K .......... .......... .......... .......... .......... 22% 11.7M 3s
-  6400K .......... .......... .......... .......... .......... 22% 9.11M 3s
-  6450K .......... .......... .......... .......... .......... 23% 10.8M 3s
-  6500K .......... .......... .......... .......... .......... 23% 11.1M 3s
-  6550K .......... .......... .......... .......... .......... 23% 14.5M 3s
-  6600K .......... .......... .......... .......... .......... 23% 11.0M 3s
-  6650K .......... .......... .......... .......... .......... 23% 10.5M 3s
-  6700K .......... .......... .......... .......... .......... 24% 11.0M 3s
-  6750K .......... .......... .......... .......... .......... 24% 14.4M 3s
-  6800K .......... .......... .......... .......... .......... 24% 8.71M 3s
-  6850K .......... .......... .......... .......... .......... 24% 11.0M 3s
-  6900K .......... .......... .......... .......... .......... 24% 10.6M 3s
-  6950K .......... .......... .......... .......... .......... 24% 14.0M 3s
-  7000K .......... .......... .......... .......... .......... 25% 10.9M 3s
-  7050K .......... .......... .......... .......... .......... 25% 10.6M 3s
-  7100K .......... .......... .......... .......... .......... 25% 10.7M 3s
-  7150K .......... .......... .......... .......... .......... 25% 14.4M 3s
-  7200K .......... .......... .......... .......... .......... 25% 8.82M 3s
-  7250K .......... .......... .......... .......... .......... 25% 10.7M 3s
-  7300K .......... .......... .......... .......... .......... 26% 10.8M 3s
-  7350K .......... .......... .......... .......... .......... 26% 13.5M 3s
-  7400K .......... .......... .......... .......... .......... 26% 10.7M 3s
-  7450K .......... .......... .......... .......... .......... 26% 11.0M 3s
-  7500K .......... .......... .......... .......... .......... 26% 11.2M 3s
-  7550K .......... .......... .......... .......... .......... 27% 13.5M 3s
-  7600K .......... .......... .......... .......... .......... 27% 8.93M 3s
-  7650K .......... .......... .......... .......... .......... 27% 11.3M 3s
-  7700K .......... .......... .......... .......... .......... 27% 10.8M 3s
-  7750K .......... .......... .......... .......... .......... 27% 10.7M 3s
-  7800K .......... .......... .......... .......... .......... 27% 14.3M 3s
-  7850K .......... .......... .......... .......... .......... 28% 10.9M 3s
-  7900K .......... .......... .......... .......... .......... 28% 10.9M 3s
-  7950K .......... .......... .......... .......... .......... 28% 11.3M 3s
-  8000K .......... .......... .......... .......... .......... 28% 8.17M 3s
-  8050K .......... .......... .......... .......... .......... 28% 14.2M 3s
-  8100K .......... .......... .......... .......... .......... 29% 10.9M 3s
-  8150K .......... .......... .......... .......... .......... 29% 11.0M 3s
-  8200K .......... .......... .......... .......... .......... 29% 13.7M 3s
-  8250K .......... .......... .......... .......... .......... 29% 10.6M 2s
-  8300K .......... .......... .......... .......... .......... 29% 10.8M 2s
-  8350K .......... .......... .......... .......... .......... 29% 13.9M 2s
-  8400K .......... .......... .......... .......... .......... 30% 8.64M 2s
-  8450K .......... .......... .......... .......... .......... 30% 10.6M 2s
-  8500K .......... .......... .......... .......... .......... 30% 13.9M 2s
-  8550K .......... .......... .......... .......... .......... 30% 10.7M 2s
-  8600K .......... .......... .......... .......... .......... 30% 10.6M 2s
-  8650K .......... .......... .......... .......... .......... 30% 10.5M 2s
-  8700K .......... .......... .......... .......... .......... 31% 14.4M 2s
-  8750K .......... .......... .......... .......... .......... 31% 10.7M 2s
-  8800K .......... .......... .......... .......... .......... 31% 8.40M 2s
-  8850K .......... .......... .......... .......... .......... 31% 11.4M 2s
-  8900K .......... .......... .......... .......... .......... 31% 11.0M 2s
-  8950K .......... .......... .......... .......... .......... 32% 13.3M 2s
-  9000K .......... .......... .......... .......... .......... 32% 10.7M 2s
-  9050K .......... .......... .......... .......... .......... 32% 11.5M 2s
-  9100K .......... .......... .......... .......... .......... 32% 11.0M 2s
-  9150K .......... .......... .......... .......... .......... 32% 14.0M 2s
-  9200K .......... .......... .......... .......... .......... 32% 8.24M 2s
-  9250K .......... .......... .......... .......... .......... 33% 11.3M 2s
-  9300K .......... .......... .......... .......... .......... 33% 10.5M 2s
-  9350K .......... .......... .......... .......... .......... 33% 15.1M 2s
-  9400K .......... .......... .......... .......... .......... 33% 10.1M 2s
-  9450K .......... .......... .......... .......... .......... 33% 11.5M 2s
-  9500K .......... .......... .......... .......... .......... 34% 13.5M 2s
-  9550K .......... .......... .......... .......... .......... 34% 10.5M 2s
-  9600K .......... .......... .......... .......... .......... 34% 8.45M 2s
-  9650K .......... .......... .......... .......... .......... 34% 13.5M 2s
-  9700K .......... .......... .......... .......... .......... 34% 6.13M 2s
-  9750K .......... .......... .......... .......... .......... 34% 16.1M 2s
-  9800K .......... .......... .......... .......... .......... 35% 33.7M 2s
-  9850K .......... .......... .......... .......... .......... 35% 10.9M 2s
-  9900K .......... .......... .......... .......... .......... 35% 10.7M 2s
-  9950K .......... .......... .......... .......... .......... 35% 13.1M 2s
- 10000K .......... .......... .......... .......... .......... 35% 8.98M 2s
- 10050K .......... .......... .......... .......... .......... 35% 10.9M 2s
- 10100K .......... .......... .......... .......... .......... 36% 10.2M 2s
- 10150K .......... .......... .......... .......... .......... 36% 13.6M 2s
- 10200K .......... .......... .......... .......... .......... 36% 10.4M 2s
- 10250K .......... .......... .......... .......... .......... 36% 10.9M 2s
- 10300K .......... .......... .......... .......... .......... 36% 10.8M 2s
- 10350K .......... .......... .......... .......... .......... 37% 13.6M 2s
- 10400K .......... .......... .......... .......... .......... 37% 8.40M 2s
- 10450K .......... .......... .......... .......... .......... 37% 10.5M 2s
- 10500K .......... .......... .......... .......... .......... 37% 14.0M 2s
- 10550K .......... .......... .......... .......... .......... 37% 10.6M 2s
- 10600K .......... .......... .......... .......... .......... 37% 10.6M 2s
- 10650K .......... .......... .......... .......... .......... 38% 13.5M 2s
- 10700K .......... .......... .......... .......... .......... 38% 10.2M 2s
- 10750K .......... .......... .......... .......... .......... 38% 13.9M 2s
- 10800K .......... .......... .......... .......... .......... 38% 8.34M 2s
- 10850K .......... .......... .......... .......... .......... 38% 13.6M 2s
- 10900K .......... .......... .......... .......... .......... 38% 10.6M 2s
- 10950K .......... .......... .......... .......... .......... 39% 10.3M 2s
- 11000K .......... .......... .......... .......... .......... 39% 13.4M 2s
- 11050K .......... .......... .......... .......... .......... 39% 10.8M 2s
- 11100K .......... .......... .......... .......... .......... 39% 13.4M 2s
- 11150K .......... .......... .......... .......... .......... 39% 10.9M 2s
- 11200K .......... .......... .......... .......... .......... 40% 8.49M 2s
- 11250K .......... .......... .......... .......... .......... 40% 10.8M 2s
- 11300K .......... .......... .......... .......... .......... 40% 14.6M 2s
- 11350K .......... .......... .......... .......... .......... 40% 10.5M 2s
- 11400K .......... .......... .......... .......... .......... 40% 10.0M 2s
- 11450K .......... .......... .......... .......... .......... 40% 12.3M 2s
- 11500K .......... .......... .......... .......... .......... 41% 12.4M 2s
- 11550K .......... .......... .......... .......... .......... 41% 13.6M 2s
- 11600K .......... .......... .......... .......... .......... 41% 8.51M 2s
- 11650K .......... .......... .......... .......... .......... 41% 10.7M 2s
- 11700K .......... .......... .......... .......... .......... 41% 10.8M 2s
- 11750K .......... .......... .......... .......... .......... 42% 13.6M 2s
- 11800K .......... .......... .......... .......... .......... 42% 10.3M 2s
- 11850K .......... .......... .......... .......... .......... 42% 14.7M 2s
- 11900K .......... .......... .......... .......... .......... 42% 10.1M 2s
- 11950K .......... .......... .......... .......... .......... 42% 10.3M 2s
- 12000K .......... .......... .......... .......... .......... 42% 10.5M 2s
- 12050K .......... .......... .......... .......... .......... 43% 11.1M 2s
- 12100K .......... .......... .......... .......... .......... 43% 10.4M 2s
- 12150K .......... .......... .......... .......... .......... 43% 13.7M 2s
- 12200K .......... .......... .......... .......... .......... 43% 10.3M 2s
- 12250K .......... .......... .......... .......... .......... 43% 12.6M 2s
- 12300K .......... .......... .......... .......... .......... 43% 11.4M 2s
- 12350K .......... .......... .......... .......... .......... 44% 10.3M 2s
- 12400K .......... .......... .......... .......... .......... 44% 10.8M 2s
- 12450K .......... .......... .......... .......... .......... 44% 10.9M 2s
- 12500K .......... .......... .......... .......... .......... 44% 10.4M 2s
- 12550K .......... .......... .......... .......... .......... 44% 13.5M 2s
- 12600K .......... .......... .......... .......... .......... 45% 10.5M 2s
- 12650K .......... .......... .......... .......... .......... 45% 10.5M 2s
- 12700K .......... .......... .......... .......... .......... 45% 13.6M 2s
- 12750K .......... .......... .......... .......... .......... 45% 10.6M 2s
- 12800K .......... .......... .......... .......... .......... 45% 8.74M 2s
- 12850K .......... .......... .......... .......... .......... 45% 14.0M 2s
- 12900K .......... .......... .......... .......... .......... 46% 10.8M 2s
- 12950K .......... .......... .......... .......... .......... 46% 9.36M 2s
- 13000K .......... .......... .......... .......... .......... 46% 11.8M 2s
- 13050K .......... .......... .......... .......... .......... 46% 14.1M 2s
- 13100K .......... .......... .......... .......... .......... 46% 10.6M 2s
- 13150K .......... .......... .......... .......... .......... 47% 13.2M 2s
- 13200K .......... .......... .......... .......... .......... 47% 8.66M 2s
- 13250K .......... .......... .......... .......... .......... 47% 10.4M 2s
- 13300K .......... .......... .......... .......... .......... 47% 13.8M 2s
- 13350K .......... .......... .......... .......... .......... 47% 10.5M 2s
- 13400K .......... .......... .......... .......... .......... 47% 10.7M 2s
- 13450K .......... .......... .......... .......... .......... 48% 13.7M 2s
- 13500K .......... .......... .......... .......... .......... 48% 5.94M 2s
- 13550K .......... .......... .......... .......... .......... 48% 14.3M 2s
- 13600K .......... .......... .......... .......... .......... 48% 8.65M 2s
- 13650K .......... .......... .......... .......... .......... 48% 11.0M 2s
- 13700K .......... .......... .......... .......... .......... 48% 13.5M 2s
- 13750K .......... .......... .......... .......... .......... 49% 10.3M 2s
- 13800K .......... .......... .......... .......... .......... 49% 10.4M 2s
- 13850K .......... .......... .......... .......... .......... 49% 10.8M 2s
- 13900K .......... .......... .......... .......... .......... 49% 13.4M 2s
- 13950K .......... .......... .......... .......... .......... 49% 11.2M 2s
- 14000K .......... .......... .......... .......... .......... 50% 8.61M 2s
- 14050K .......... .......... .......... .......... .......... 50% 10.5M 2s
- 14100K .......... .......... .......... .......... .......... 50% 10.1M 2s
- 14150K .......... .......... .......... .......... .......... 50% 10.5M 2s
- 14200K .......... .......... .......... .......... .......... 50% 13.6M 2s
- 14250K .......... .......... .......... .......... .......... 50% 10.1M 2s
- 14300K .......... .......... .......... .......... .......... 51% 13.6M 2s
- 14350K .......... .......... .......... .......... .......... 51% 10.9M 2s
- 14400K .......... .......... .......... .......... .......... 51% 8.60M 2s
- 14450K .......... .......... .......... .......... .......... 51% 10.1M 1s
- 14500K .......... .......... .......... .......... .......... 51% 10.6M 1s
- 14550K .......... .......... .......... .......... .......... 51% 13.7M 1s
- 14600K .......... .......... .......... .......... .......... 52% 10.2M 1s
- 14650K .......... .......... .......... .......... .......... 52% 10.2M 1s
- 14700K .......... .......... .......... .......... .......... 52% 13.7M 1s
- 14750K .......... .......... .......... .......... .......... 52% 11.6M 1s
- 14800K .......... .......... .......... .......... .......... 52% 7.61M 1s
- 14850K .......... .......... .......... .......... .......... 53% 11.0M 1s
- 14900K .......... .......... .......... .......... .......... 53% 10.6M 1s
- 14950K .......... .......... .......... .......... .......... 53% 13.8M 1s
- 15000K .......... .......... .......... .......... .......... 53% 10.6M 1s
- 15050K .......... .......... .......... .......... .......... 53% 13.3M 1s
- 15100K .......... .......... .......... .......... .......... 53% 10.3M 1s
- 15150K .......... .......... .......... .......... .......... 54% 10.3M 1s
- 15200K .......... .......... .......... .......... .......... 54% 8.45M 1s
- 15250K .......... .......... .......... .......... .......... 54% 11.1M 1s
- 15300K .......... .......... .......... .......... .......... 54% 5.95M 1s
- 15350K .......... .......... .......... .......... .......... 54% 14.8M 1s
- 15400K .......... .......... .......... .......... .......... 55% 26.8M 1s
- 15450K .......... .......... .......... .......... .......... 55% 14.3M 1s
- 15500K .......... .......... .......... .......... .......... 55% 8.46M 1s
- 15550K .......... .......... .......... .......... .......... 55% 10.3M 1s
- 15600K .......... .......... .......... .......... .......... 55% 9.05M 1s
- 15650K .......... .......... .......... .......... .......... 55% 14.0M 1s
- 15700K .......... .......... .......... .......... .......... 56% 10.5M 1s
- 15750K .......... .......... .......... .......... .......... 56% 13.2M 1s
- 15800K .......... .......... .......... .......... .......... 56% 10.9M 1s
- 15850K .......... .......... .......... .......... .......... 56% 5.26M 1s
- 15900K .......... .......... .......... .......... .......... 56% 41.9M 1s
- 15950K .......... .......... .......... .......... .......... 56% 11.0M 1s
- 16000K .......... .......... .......... .......... .......... 57% 8.61M 1s
- 16050K .......... .......... .......... .......... .......... 57% 9.85M 1s
- 16100K .......... .......... .......... .......... .......... 57% 15.8M 1s
- 16150K .......... .......... .......... .......... .......... 57% 10.5M 1s
- 16200K .......... .......... .......... .......... .......... 57% 10.3M 1s
- 16250K .......... .......... .......... .......... .......... 58% 8.54M 1s
- 16300K .......... .......... .......... .......... .......... 58% 10.6M 1s
- 16350K .......... .......... .......... .......... .......... 58% 13.8M 1s
- 16400K .......... .......... .......... .......... .......... 58% 8.67M 1s
- 16450K .......... .......... .......... .......... .......... 58% 11.1M 1s
- 16500K .......... .......... .......... .......... .......... 58% 10.4M 1s
- 16550K .......... .......... .......... .......... .......... 59% 14.0M 1s
- 16600K .......... .......... .......... .......... .......... 59% 10.7M 1s
- 16650K .......... .......... .......... .......... .......... 59% 8.50M 1s
- 16700K .......... .......... .......... .......... .......... 59% 8.64M 1s
- 16750K .......... .......... .......... .......... .......... 59% 13.7M 1s
- 16800K .......... .......... .......... .......... .......... 60% 8.33M 1s
- 16850K .......... .......... .......... .......... .......... 60% 10.3M 1s
- 16900K .......... .......... .......... .......... .......... 60% 13.8M 1s
- 16950K .......... .......... .......... .......... .......... 60% 10.6M 1s
- 17000K .......... .......... .......... .......... .......... 60% 13.8M 1s
- 17050K .......... .......... .......... .......... .......... 60% 10.4M 1s
- 17100K .......... .......... .......... .......... .......... 61% 8.28M 1s
- 17150K .......... .......... .......... .......... .......... 61% 10.6M 1s
- 17200K .......... .......... .......... .......... .......... 61% 8.70M 1s
- 17250K .......... .......... .......... .......... .......... 61% 10.6M 1s
- 17300K .......... .......... .......... .......... .......... 61% 13.6M 1s
- 17350K .......... .......... .......... .......... .......... 61% 10.9M 1s
- 17400K .......... .......... .......... .......... .......... 62% 13.5M 1s
- 17450K .......... .......... .......... .......... .......... 62% 10.4M 1s
- 17500K .......... .......... .......... .......... .......... 62% 11.2M 1s
- 17550K .......... .......... .......... .......... .......... 62% 8.36M 1s
- 17600K .......... .......... .......... .......... .......... 62% 8.49M 1s
- 17650K .......... .......... .......... .......... .......... 63% 10.5M 1s
- 17700K .......... .......... .......... .......... .......... 63% 11.0M 1s
- 17750K .......... .......... .......... .......... .......... 63% 13.6M 1s
- 17800K .......... .......... .......... .......... .......... 63% 10.3M 1s
- 17850K .......... .......... .......... .......... .......... 63% 13.4M 1s
- 17900K .......... .......... .......... .......... .......... 63% 10.6M 1s
- 17950K .......... .......... .......... .......... .......... 64% 10.1M 1s
- 18000K .......... .......... .......... .......... .......... 64% 8.55M 1s
- 18050K .......... .......... .......... .......... .......... 64% 10.6M 1s
- 18100K .......... .......... .......... .......... .......... 64% 13.9M 1s
- 18150K .......... .......... .......... .......... .......... 64% 10.4M 1s
- 18200K .......... .......... .......... .......... .......... 64% 10.4M 1s
- 18250K .......... .......... .......... .......... .......... 65% 13.7M 1s
- 18300K .......... .......... .......... .......... .......... 65% 10.6M 1s
- 18350K .......... .......... .......... .......... .......... 65% 13.3M 1s
- 18400K .......... .......... .......... .......... .......... 65% 8.53M 1s
- 18450K .......... .......... .......... .......... .......... 65% 10.5M 1s
- 18500K .......... .......... .......... .......... .......... 66% 13.8M 1s
- 18550K .......... .......... .......... .......... .......... 66% 10.2M 1s
- 18600K .......... .......... .......... .......... .......... 66% 10.7M 1s
- 18650K .......... .......... .......... .......... .......... 66% 13.9M 1s
- 18700K .......... .......... .......... .......... .......... 66% 10.7M 1s
- 18750K .......... .......... .......... .......... .......... 66% 13.8M 1s
- 18800K .......... .......... .......... .......... .......... 67% 8.35M 1s
- 18850K .......... .......... .......... .......... .......... 67% 10.6M 1s
- 18900K .......... .......... .......... .......... .......... 67% 13.9M 1s
- 18950K .......... .......... .......... .......... .......... 67% 10.4M 1s
- 19000K .......... .......... .......... .......... .......... 67% 10.4M 1s
- 19050K .......... .......... .......... .......... .......... 68% 13.3M 1s
- 19100K .......... .......... .......... .......... .......... 68% 11.1M 1s
- 19150K .......... .......... .......... .......... .......... 68% 13.9M 1s
- 19200K .......... .......... .......... .......... .......... 68% 8.32M 1s
- 19250K .......... .......... .......... .......... .......... 68% 10.7M 1s
- 19300K .......... .......... .......... .......... .......... 68% 13.2M 1s
- 19350K .......... .......... .......... .......... .......... 69% 9.38M 1s
- 19400K .......... .......... .......... .......... .......... 69% 12.0M 1s
- 19450K .......... .......... .......... .......... .......... 69% 14.1M 1s
- 19500K .......... .......... .......... .......... .......... 69% 10.4M 1s
- 19550K .......... .......... .......... .......... .......... 69% 13.3M 1s
- 19600K .......... .......... .......... .......... .......... 69% 8.49M 1s
- 19650K .......... .......... .......... .......... .......... 70% 10.3M 1s
- 19700K .......... .......... .......... .......... .......... 70% 13.9M 1s
- 19750K .......... .......... .......... .......... .......... 70% 10.7M 1s
- 19800K .......... .......... .......... .......... .......... 70% 13.4M 1s
- 19850K .......... .......... .......... .......... .......... 70% 10.2M 1s
- 19900K .......... .......... .......... .......... .......... 71% 10.5M 1s
- 19950K .......... .......... .......... .......... .......... 71% 14.1M 1s
- 20000K .......... .......... .......... .......... .......... 71% 8.41M 1s
- 20050K .......... .......... .......... .......... .......... 71% 13.6M 1s
- 20100K .......... .......... .......... .......... .......... 71% 10.6M 1s
- 20150K .......... .......... .......... .......... .......... 71% 10.3M 1s
- 20200K .......... .......... .......... .......... .......... 72% 13.8M 1s
- 20250K .......... .......... .......... .......... .......... 72% 10.7M 1s
- 20300K .......... .......... .......... .......... .......... 72% 13.4M 1s
- 20350K .......... .......... .......... .......... .......... 72% 10.6M 1s
- 20400K .......... .......... .......... .......... .......... 72% 8.59M 1s
- 20450K .......... .......... .......... .......... .......... 72% 10.1M 1s
- 20500K .......... .......... .......... .......... .......... 73% 14.3M 1s
- 20550K .......... .......... .......... .......... .......... 73% 10.4M 1s
- 20600K .......... .......... .......... .......... .......... 73% 14.0M 1s
- 20650K .......... .......... .......... .......... .......... 73% 10.8M 1s
- 20700K .......... .......... .......... .......... .......... 73% 10.3M 1s
- 20750K .......... .......... .......... .......... .......... 74% 14.1M 1s
- 20800K .......... .......... .......... .......... .......... 74% 8.67M 1s
- 20850K .......... .......... .......... .......... .......... 74% 10.5M 1s
- 20900K .......... .......... .......... .......... .......... 74% 7.89M 1s
- 20950K .......... .......... .......... .......... .......... 74% 14.8M 1s
- 21000K .......... .......... .......... .......... .......... 74% 17.6M 1s
- 21050K .......... .......... .......... .......... .......... 75% 11.0M 1s
- 21100K .......... .......... .......... .......... .......... 75% 13.4M 1s
- 21150K .......... .......... .......... .......... .......... 75% 10.8M 1s
- 21200K .......... .......... .......... .......... .......... 75% 8.33M 1s
- 21250K .......... .......... .......... .......... .......... 75% 11.5M 1s
- 21300K .......... .......... .......... .......... .......... 76% 13.6M 1s
- 21350K .......... .......... .......... .......... .......... 76% 10.8M 1s
- 21400K .......... .......... .......... .......... .......... 76% 10.6M 1s
- 21450K .......... .......... .......... .......... .......... 76% 13.9M 1s
- 21500K .......... .......... .......... .......... .......... 76% 10.3M 1s
- 21550K .......... .......... .......... .......... .......... 76% 13.8M 1s
- 21600K .......... .......... .......... .......... .......... 77% 8.36M 1s
- 21650K .......... .......... .......... .......... .......... 77% 10.2M 1s
- 21700K .......... .......... .......... .......... .......... 77% 14.2M 1s
- 21750K .......... .......... .......... .......... .......... 77% 10.9M 1s
- 21800K .......... .......... .......... .......... .......... 77% 13.6M 1s
- 21850K .......... .......... .......... .......... .......... 77% 10.7M 1s
- 21900K .......... .......... .......... .......... .......... 78% 10.5M 1s
- 21950K .......... .......... .......... .......... .......... 78% 11.2M 1s
- 22000K .......... .......... .......... .......... .......... 78% 10.1M 1s
- 22050K .......... .......... .......... .......... .......... 78% 11.3M 1s
- 22100K .......... .......... .......... .......... .......... 78% 10.2M 1s
- 22150K .......... .......... .......... .......... .......... 79% 13.5M 1s
- 22200K .......... .......... .......... .......... .......... 79% 10.6M 1s
- 22250K .......... .......... .......... .......... .......... 79% 9.67M 1s
- 22300K .......... .......... .......... .......... .......... 79% 15.1M 1s
- 22350K .......... .......... .......... .......... .......... 79% 10.4M 1s
- 22400K .......... .......... .......... .......... .......... 79% 10.4M 1s
- 22450K .......... .......... .......... .......... .......... 80% 10.3M 1s
- 22500K .......... .......... .......... .......... .......... 80% 10.6M 1s
- 22550K .......... .......... .......... .......... .......... 80% 14.0M 1s
- 22600K .......... .......... .......... .......... .......... 80% 10.4M 1s
- 22650K .......... .......... .......... .......... .......... 80% 13.7M 1s
- 22700K .......... .......... .......... .......... .......... 81% 10.4M 1s
- 22750K .......... .......... .......... .......... .......... 81% 13.5M 1s
- 22800K .......... .......... .......... .......... .......... 81% 8.29M 1s
- 22850K .......... .......... .......... .......... .......... 81% 10.5M 1s
- 22900K .......... .......... .......... .......... .......... 81% 13.6M 1s
- 22950K .......... .......... .......... .......... .......... 81% 10.6M 1s
- 23000K .......... .......... .......... .......... .......... 82% 13.6M 1s
- 23050K .......... .......... .......... .......... .......... 82% 10.9M 1s
- 23100K .......... .......... .......... .......... .......... 82% 10.6M 1s
- 23150K .......... .......... .......... .......... .......... 82% 11.5M 0s
- 23200K .......... .......... .......... .......... .......... 82% 9.57M 0s
- 23250K .......... .......... .......... .......... .......... 82% 10.9M 0s
- 23300K .......... .......... .......... .......... .......... 83% 10.2M 0s
- 23350K .......... .......... .......... .......... .......... 83% 13.7M 0s
- 23400K .......... .......... .......... .......... .......... 83% 10.4M 0s
- 23450K .......... .......... .......... .......... .......... 83% 13.8M 0s
- 23500K .......... .......... .......... .......... .......... 83% 10.2M 0s
- 23550K .......... .......... .......... .......... .......... 84% 14.2M 0s
- 23600K .......... .......... .......... .......... .......... 84% 8.47M 0s
- 23650K .......... .......... .......... .......... .......... 84% 10.5M 0s
- 23700K .......... .......... .......... .......... .......... 84% 13.7M 0s
- 23750K .......... .......... .......... .......... .......... 84% 10.5M 0s
- 23800K .......... .......... .......... .......... .......... 84% 10.3M 0s
- 23850K .......... .......... .......... .......... .......... 85% 14.0M 0s
- 23900K .......... .......... .......... .......... .......... 85% 10.5M 0s
- 23950K .......... .......... .......... .......... .......... 85% 10.9M 0s
- 24000K .......... .......... .......... .......... .......... 85% 11.0M 0s
- 24050K .......... .......... .......... .......... .......... 85% 10.8M 0s
- 24100K .......... .......... .......... .......... .......... 85% 10.5M 0s
- 24150K .......... .......... .......... .......... .......... 86% 13.9M 0s
- 24200K .......... .......... .......... .......... .......... 86% 10.3M 0s
- 24250K .......... .......... .......... .......... .......... 86% 10.5M 0s
- 24300K .......... .......... .......... .......... .......... 86% 13.7M 0s
- 24350K .......... .......... .......... .......... .......... 86% 10.8M 0s
- 24400K .......... .......... .......... .......... .......... 87% 8.24M 0s
- 24450K .......... .......... .......... .......... .......... 87% 14.0M 0s
- 24500K .......... .......... .......... .......... .......... 87% 10.4M 0s
- 24550K .......... .......... .......... .......... .......... 87% 13.0M 0s
- 24600K .......... .......... .......... .......... .......... 87% 10.8M 0s
- 24650K .......... .......... .......... .......... .......... 87% 10.9M 0s
- 24700K .......... .......... .......... .......... .......... 88% 15.3M 0s
- 24750K .......... .......... .......... .......... .......... 88% 10.5M 0s
- 24800K .......... .......... .......... .......... .......... 88% 8.69M 0s
- 24850K .......... .......... .......... .......... .......... 88% 10.5M 0s
- 24900K .......... .......... .......... .......... .......... 88% 13.9M 0s
- 24950K .......... .......... .......... .......... .......... 89% 11.0M 0s
- 25000K .......... .......... .......... .......... .......... 89% 10.4M 0s
- 25050K .......... .......... .......... .......... .......... 89% 13.7M 0s
- 25100K .......... .......... .......... .......... .......... 89% 10.5M 0s
- 25150K .......... .......... .......... .......... .......... 89% 11.2M 0s
- 25200K .......... .......... .......... .......... .......... 89% 10.2M 0s
- 25250K .......... .......... .......... .......... .......... 90% 10.5M 0s
- 25300K .......... .......... .......... .......... .......... 90% 10.4M 0s
- 25350K .......... .......... .......... .......... .......... 90% 13.8M 0s
- 25400K .......... .......... .......... .......... .......... 90% 11.0M 0s
- 25450K .......... .......... .......... .......... .......... 90% 11.1M 0s
- 25500K .......... .......... .......... .......... .......... 90% 12.6M 0s
- 25550K .......... .......... .......... .......... .......... 91% 11.8M 0s
- 25600K .......... .......... .......... .......... .......... 91% 8.78M 0s
- 25650K .......... .......... .......... .......... .......... 91% 10.8M 0s
- 25700K .......... .......... .......... .......... .......... 91% 14.3M 0s
- 25750K .......... .......... .......... .......... .......... 91% 10.8M 0s
- 25800K .......... .......... .......... .......... .......... 92% 10.5M 0s
- 25850K .......... .......... .......... .......... .......... 92% 10.7M 0s
- 25900K .......... .......... .......... .......... .......... 92% 14.0M 0s
- 25950K .......... .......... .......... .......... .......... 92% 10.4M 0s
- 26000K .......... .......... .......... .......... .......... 92% 8.47M 0s
- 26050K .......... .......... .......... .......... .......... 92% 13.1M 0s
- 26100K .......... .......... .......... .......... .......... 93% 10.8M 0s
- 26150K .......... .......... .......... .......... .......... 93% 14.2M 0s
- 26200K .......... .......... .......... .......... .......... 93% 10.2M 0s
- 26250K .......... .......... .......... .......... .......... 93% 13.8M 0s
- 26300K .......... .......... .......... .......... .......... 93% 10.8M 0s
- 26350K .......... .......... .......... .......... .......... 94% 10.4M 0s
- 26400K .......... .......... .......... .......... .......... 94% 10.1M 0s
- 26450K .......... .......... .......... .......... .......... 94% 10.4M 0s
- 26500K .......... .......... .......... .......... .......... 94% 10.7M 0s
- 26550K .......... .......... .......... .......... .......... 94% 13.8M 0s
- 26600K .......... .......... .......... .......... .......... 94% 6.41M 0s
- 26650K .......... .......... .......... .......... .......... 95% 18.6M 0s
- 26700K .......... .......... .......... .......... .......... 95% 21.4M 0s
- 26750K .......... .......... .......... .......... .......... 95% 10.7M 0s
- 26800K .......... .......... .......... .......... .......... 95% 8.32M 0s
- 26850K .......... .......... .......... .......... .......... 95% 13.5M 0s
- 26900K .......... .......... .......... .......... .......... 95% 11.1M 0s
- 26950K .......... .......... .......... .......... .......... 96% 10.2M 0s
- 27000K .......... .......... .......... .......... .......... 96% 13.5M 0s
- 27050K .......... .......... .......... .......... .......... 96% 10.8M 0s
- 27100K .......... .......... .......... .......... .......... 96% 10.7M 0s
- 27150K .......... .......... .......... .......... .......... 96% 14.3M 0s
- 27200K .......... .......... .......... .......... .......... 97% 8.82M 0s
- 27250K .......... .......... .......... .......... .......... 97% 10.6M 0s
- 27300K .......... .......... .......... .......... .......... 97% 10.7M 0s
- 27350K .......... .......... .......... .......... .......... 97% 14.4M 0s
- 27400K .......... .......... .......... .......... .......... 97% 10.6M 0s
- 27450K .......... .......... .......... .......... .......... 97% 11.0M 0s
- 27500K .......... .......... .......... .......... .......... 98% 13.6M 0s
- 27550K .......... .......... .......... .......... .......... 98% 11.1M 0s
- 27600K .......... .......... .......... .......... .......... 98% 8.50M 0s
- 27650K .......... .......... .......... .......... .......... 98% 9.98M 0s
- 27700K .......... .......... .......... .......... .......... 98% 13.8M 0s
- 27750K .......... .......... .......... .......... .......... 98% 10.6M 0s
- 27800K .......... .......... .......... .......... .......... 99% 13.1M 0s
- 27850K .......... .......... .......... .......... .......... 99% 10.8M 0s
- 27900K .......... .......... .......... .......... .......... 99% 13.7M 0s
- 27950K .......... .......... .......... .......... .......... 99% 10.3M 0s
- 28000K .......... .......... .......... .......... .......... 99% 8.80M 0s
- 28050K .......... .......... .......... ..                   100% 24.9M=2.8s
-
-2014-01-16 19:58:45 (9.79 MB/s) - ‘/Users/kraft/annex/.git/annex/tmp/SHA256E-s28756861--4bea2d816a701dbfc88eada2288019c92c2774ee605e4ddfa62c4dd7655e53a1.dmg’ saved [28756861/28756861]
-
-[2014-01-16 19:58:45 CET] Transferrer: Downloaded git-annex.. upgrade)
-Checksumming Protective Master Boot Record (MBR : 0)…
-Protective Master Boot Record (MBR :: verified   CRC32 $BFC39E6D
-Checksumming GPT Header (Primary GPT Header : 1)…
- GPT Header (Primary GPT Header : 1): verified   CRC32 $1B4A1450
-Checksumming GPT Partition Data (Primary GPT Table : 2)…
-GPT Partition Data (Primary GPT Tabl: verified   CRC32 $78D54639
-Checksumming  (Apple_Free : 3)…
-                    (Apple_Free : 3): verified   CRC32 $00000000
-Checksumming disk image (Apple_HFS : 4)…
-          disk image (Apple_HFS : 4): verified   CRC32 $1E0144DA
-Checksumming  (Apple_Free : 5)…
-                    (Apple_Free : 5): verified   CRC32 $00000000
-Checksumming GPT Partition Data (Backup GPT Table : 6)…
-GPT Partition Data (Backup GPT Table: verified   CRC32 $78D54639
-Checksumming GPT Header (Backup GPT Header : 7)…
-  GPT Header (Backup GPT Header : 7): verified   CRC32 $61044DA0
-verified   CRC32 $E2335ED3
-/dev/disk4          	GUID_partition_scheme          	
-/dev/disk4s1        	Apple_HFS                      	/Applications/git-annex.upgrade.0
-
-(gpg) 
-
-0%            0.0 B/s 0s
-0%            0.0 B/s 0s
-0%            0.0 B/s 0s
-0%            0.0 B/s 0s
-0%            0.0 B/s 0s
-0%       191.9KB/s 2m25s
-0%        74.6KB/s 6m13s
-0%        85.3KB/s 5m26s
-1%        96.0KB/s 4m50s
-1%       106.6KB/s 4m20s
-1%       117.3KB/s 3m56s
-1%       127.9KB/s 3m37s
-1%       138.6KB/s 3m20s
-1%        149.3KB/s 3m5s
-1%       159.9KB/s 2m53s
-1%       170.6KB/s 2m42s
-1%       181.2KB/s 2m32s
-2%       191.9KB/s 2m23s
-2%       202.6KB/s 2m16s
-2%        213.2KB/s 2m9s
-2%        223.9KB/s 2m2s
-2%       234.6KB/s 1m57s
-2%       245.2KB/s 1m52s
-2%       255.9KB/s 1m47s
-2%       266.5KB/s 1m42s
-2%       277.2KB/s 1m38s
-3%       287.9KB/s 1m35s
-3%       298.5KB/s 1m31s
-3%       309.2KB/s 1m28s
-3%       319.8KB/s 1m25s
-3%       330.5KB/s 1m22s
-3%       341.2KB/s 1m19s
-3%       351.8KB/s 1m17s
-3%       362.5KB/s 1m14s
-3%       373.2KB/s 1m12s
-4%       383.8KB/s 1m10s
-4%        394.5KB/s 1m8s
-4%        405.1KB/s 1m6s
-4%        415.8KB/s 1m5s
-4%        426.5KB/s 1m3s
-4%        437.1KB/s 1m1s
-4%        447.8KB/s 1m0s
-4%         458.4KB/s 58s
-5%         469.1KB/s 57s
-5%         479.8KB/s 56s
-5%         490.4KB/s 54s
-5%         501.1KB/s 53s
-5%         511.8KB/s 52s
-5%         522.4KB/s 51s
-5%         533.1KB/s 50s
-5%         543.7KB/s 49s
-5%         554.4KB/s 48s
-6%         565.1KB/s 47s
-6%         575.7KB/s 46s
-6%         586.4KB/s 45s
-6%         597.0KB/s 44s
-6%         607.7KB/s 43s
-6%         618.4KB/s 42s
-6%         629.0KB/s 42s
-6%         639.7KB/s 41s
-6%         650.3KB/s 40s
-7%         661.0KB/s 39s
-7%         671.7KB/s 39s
-7%         682.3KB/s 38s
-7%         693.0KB/s 38s\"disk4\" unmounted.
-\"disk4\" ejected.
-
-7%         703.7KB/s 37s
-7%         714.3KB/s 36s
-7%         725.0KB/s 36s
-7%         735.6KB/s 35s
-7%         746.3KB/s 35s
-8%         757.0KB/s 34s
-8%         767.6KB/s 34s
-8%         778.3KB/s 33s
-8%         788.9KB/s 33s
-8%         799.6KB/s 32s
-8%         810.3KB/s 32s
-8%         820.9KB/s 31s
-8%         831.6KB/s 31s
-8%         842.3KB/s 30s
-9%         852.9KB/s 30s
-9%         863.6KB/s 30s
-9%         874.2KB/s 29s
-9%         884.9KB/s 29s
-9%         895.6KB/s 28s
-9%         906.2KB/s 28s
-9%         916.9KB/s 28s
-9%         927.5KB/s 27s
-10%        938.2KB/s 27s
-10%        948.9KB/s 27s
-10%        959.5KB/s 26s
-10%        970.2KB/s 26s
-10%        980.9KB/s 26s
-10%        991.5KB/s 25s
-10%       1002.2KB/s 25s
-10%       1012.8KB/s 25s
-10%       1023.5KB/s 24s
-11%          1.0MB/s 24s
-11%          1.0MB/s 24s
-11%          1.0MB/s 24s
-11%          1.0MB/s 23s
-11%          1.1MB/s 23s
-11%          1.1MB/s 23s
-11%          1.1MB/s 23s
-11%          1.1MB/s 22s
-11%          1.1MB/s 22s
-12%          1.1MB/s 22s
-12%          1.1MB/s 22s
-12%          1.1MB/s 21s
-12%          1.1MB/s 21s
-12%          1.1MB/s 21s
-12%          1.2MB/s 21s
-12%          1.2MB/s 21s
-12%          1.2MB/s 20s
-12%          1.2MB/s 20s
-13%          1.2MB/s 20s
-13%          1.2MB/s 20s
-13%          1.2MB/s 20s
-13%          1.2MB/s 19s
-13%          1.2MB/s 19s
-13%          1.2MB/s 19s
-13%          1.3MB/s 19s
-13%          1.3MB/s 19s
-14%          1.3MB/s 18s
-14%          1.3MB/s 18s
-14%          1.3MB/s 18s
-14%          1.3MB/s 18s
-14%          1.3MB/s 18s
-14%          1.3MB/s 18s
-14%          1.3MB/s 17s
-14%          1.4MB/s 17s
-14%          1.4MB/s 17s
-15%          1.4MB/s 17s
-15%          1.4MB/s 17s
-15%          1.4MB/s 17s
-15%          1.4MB/s 17s
-15%          1.4MB/s 16s
-15%          1.4MB/s 16s
-15%          1.4MB/s 16s
-15%          1.4MB/s 16s
-15%          1.5MB/s 16s
-16%          1.5MB/s 16s
-16%          1.5MB/s 16s
-16%          1.5MB/s 15s
-16%          1.5MB/s 15s
-16%          1.5MB/s 15s
-16%          1.5MB/s 15s
-16%          1.5MB/s 15s
-16%          1.5MB/s 15s
-16%          1.6MB/s 15s
-17%          1.6MB/s 15s
-17%          1.6MB/s 14s
-17%          1.6MB/s 14s
-17%          1.6MB/s 14s
-17%          1.6MB/s 14s
-17%          1.6MB/s 14s
-17%          1.6MB/s 14s
-17%          1.6MB/s 14s
-17%          1.6MB/s 14s
-18%          1.7MB/s 14s
-18%          1.7MB/s 13s
-18%          1.7MB/s 13s
-18%          1.7MB/s 13s
-18%          1.7MB/s 13s
-18%          1.7MB/s 13s
-18%          1.7MB/s 13s
-18%          1.7MB/s 13s
-19%          1.7MB/s 13s
-19%          1.7MB/s 13s
-19%          1.8MB/s 13s
-19%          1.8MB/s 12s
-19%          1.8MB/s 12s
-19%          1.8MB/s 12s
-19%          1.4MB/s 16s
-19%          1.4MB/s 16s
-19%          1.4MB/s 16s
-20%          1.4MB/s 16s
-20%          1.4MB/s 16s
-20%          1.4MB/s 16s
-20%          1.4MB/s 16s
-20%          1.4MB/s 16s
-20%          1.4MB/s 15s
-20%          1.4MB/s 15s
-20%          1.4MB/s 15s
-20%          1.4MB/s 15s
-21%          1.4MB/s 15s
-21%          1.5MB/s 15s
-21%          1.5MB/s 15s
-21%          1.5MB/s 15s
-21%          1.5MB/s 15s
-21%          1.5MB/s 14s
-21%          1.5MB/s 14s
-21%          1.5MB/s 14s
-21%          1.5MB/s 14s
-22%          1.5MB/s 14s
-22%          1.5MB/s 14s
-22%          1.5MB/s 14s
-22%          1.5MB/s 14s
-22%          1.5MB/s 14s
-22%          1.6MB/s 14s
-22%          1.6MB/s 14s
-22%          1.6MB/s 13s
-23%          1.6MB/s 13s
-23%          1.6MB/s 13s
-23%          1.6MB/s 13s
-23%          1.6MB/s 13s
-23%          1.6MB/s 13s
-23%          1.6MB/s 13s
-23%          1.6MB/s 13s
-23%          1.6MB/s 13s
-23%          1.6MB/s 13s
-24%          1.6MB/s 13s
-24%          1.7MB/s 13s
-24%          1.7MB/s 12s
-24%          1.7MB/s 12s
-24%          1.7MB/s 12s
-24%          1.7MB/s 12s
-24%          1.7MB/s 12s
-24%          1.7MB/s 12s
-24%          1.7MB/s 12s
-25%          1.7MB/s 12s
-25%          1.7MB/s 12s
-25%          1.7MB/s 12s
-25%          1.7MB/s 12s
-25%          1.7MB/s 12s
-25%          1.8MB/s 12s
-25%          1.8MB/s 12s
-25%          1.8MB/s 11s
-25%          1.8MB/s 11s
-26%          1.8MB/s 11s
-26%          1.8MB/s 11s
-26%          1.8MB/s 11s
-26%          1.8MB/s 11s
-26%          1.8MB/s 11s
-26%          1.8MB/s 11s
-26%          1.8MB/s 11s
-26%          1.8MB/s 11s
-26%          1.9MB/s 11s
-27%          1.9MB/s 11s
-27%          1.9MB/s 11s
-27%          1.9MB/s 11s
-27%          1.9MB/s 11s
-27%          1.9MB/s 11s
-27%          1.9MB/s 10s
-27%          1.9MB/s 10s
-27%          1.9MB/s 10s
-28%          1.9MB/s 10s
-28%          1.9MB/s 10s
-28%          1.9MB/s 10s
-28%          1.9MB/s 10s
-28%          2.0MB/s 10s
-28%          2.0MB/s 10s
-28%          2.0MB/s 10s
-28%          2.0MB/s 10s
-28%          2.0MB/s 10s
-29%          2.0MB/s 10s
-29%          2.0MB/s 10s
-29%          2.0MB/s 10s
-29%          2.0MB/s 10s
-29%          2.0MB/s 10s
-29%          2.0MB/s 10s
-29%           2.0MB/s 9s
-29%           2.0MB/s 9s
-29%           2.1MB/s 9s
-30%           2.1MB/s 9s
-30%           2.1MB/s 9s
-30%           2.1MB/s 9s
-30%           2.1MB/s 9s
-30%           2.1MB/s 9s
-30%           2.1MB/s 9s
-30%           2.1MB/s 9s
-30%           2.1MB/s 9s
-30%           2.1MB/s 9s
-31%           2.1MB/s 9s
-31%           2.1MB/s 9s
-31%           2.1MB/s 9s
-31%           2.2MB/s 9s
-31%           2.2MB/s 9s
-31%           2.2MB/s 9s
-31%           2.2MB/s 9s
-31%           2.2MB/s 9s
-32%           2.2MB/s 8s
-32%           2.2MB/s 8s
-32%           2.2MB/s 8s
-32%           2.2MB/s 8s
-32%           2.2MB/s 8s
-32%           2.2MB/s 8s
-32%           2.2MB/s 8s
-32%           2.2MB/s 8s
-32%           2.3MB/s 8s
-33%           2.3MB/s 8s
-33%           2.3MB/s 8s
-33%           2.3MB/s 8s
-33%           2.3MB/s 8s
-33%           2.3MB/s 8s
-33%           2.3MB/s 8s
-33%           2.3MB/s 8s
-33%           2.3MB/s 8s
-33%           2.3MB/s 8s
-34%           2.3MB/s 8s
-34%           2.3MB/s 8s
-34%           2.4MB/s 8s
-34%           2.4MB/s 8s
-34%           2.4MB/s 8s
-34%           2.4MB/s 8s
-34%           2.4MB/s 8s
-34%           2.4MB/s 7s
-34%           2.4MB/s 7s
-35%           2.4MB/s 7s
-35%           2.4MB/s 7s
-35%           2.4MB/s 7s
-35%           2.4MB/s 7sgit-annex version: 5.20140116-gd2fce02
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external
-local repository version: 5
-supported repository version: 5
-upgrade supported from repository versions: 0 1 2 4
-[2014-01-16 19:58:59 CET] Upgrader: Upgrading git-annex
-
-35%        665.3KB/s 27s
-35%        667.4KB/s 27s
-35%        669.5KB/s 27s
-35%        671.7KB/s 27s
-35%        673.8KB/s 27s
-36%        675.9KB/s 27s
-36%        678.1KB/s 26s
-36%        680.2KB/s 26s
-36%        682.3KB/s 26s
-36%        684.5KB/s 26s
-36%        686.6KB/s 26s
-36%        688.7KB/s 26s
-36%        690.9KB/s 26s
-37%        693.0KB/s 26s
-37%        695.1KB/s 25s
-37%        697.3KB/s 25s
-37%        699.4KB/s 25s
-37%        701.5KB/s 25s
-37%        703.7KB/s 25s
-37%        705.8KB/s 25s
-37%        707.9KB/s 25s
-37%        710.1KB/s 25s
-38%        712.2KB/s 24s
-38%        714.3KB/s 24s
-38%        716.4KB/s 24s
-38%        718.6KB/s 24s
-38%        720.7KB/s 24s
-38%        722.8KB/s 24s
-38%        725.0KB/s 24s
-38%        727.1KB/s 24s
-38%        729.2KB/s 24s
-39%        731.4KB/s 23s
-39%        733.5KB/s 23s
-39%        735.6KB/s 23s
-39%        737.8KB/s 23s
-39%        739.9KB/s 23s
-39%        742.0KB/s 23s
-39%        744.2KB/s 23s
-39%        746.3KB/s 23s
-39%        748.4KB/s 23s
-40%        750.6KB/s 22s
-40%        752.7KB/s 22s
-40%        754.8KB/s 22s
-40%        757.0KB/s 22s
-40%        759.1KB/s 22s
-40%        761.2KB/s 22s
-40%        763.4KB/s 22s
-40%        765.5KB/s 22s
-41%        767.6KB/s 22s
-41%        769.8KB/s 21s
-41%        771.9KB/s 21s
-41%        774.0KB/s 21s
-41%        776.2KB/s 21s
-41%        778.3KB/s 21s
-41%        780.4KB/s 21s
-41%        782.6KB/s 21s
-41%        784.7KB/s 21s
-42%        786.8KB/s 21s
-42%        788.9KB/s 21s
-42%        791.1KB/s 20s
-42%        793.2KB/s 20s
-42%        795.3KB/s 20s
-42%        797.5KB/s 20s
-42%        799.6KB/s 20s
-42%        801.7KB/s 20s
-42%        803.9KB/s 20s
-43%        806.0KB/s 20s
-43%        808.1KB/s 20s
-43%        810.3KB/s 20s
-43%        812.4KB/s 20s
-43%        814.5KB/s 19s
-43%        816.7KB/s 19s
-43%        818.8KB/s 19s
-43%        820.9KB/s 19s
-43%        823.1KB/s 19s
-44%        825.2KB/s 19s
-44%        827.3KB/s 19s
-44%        829.5KB/s 19s
-44%        831.6KB/s 19s
-44%        833.7KB/s 19s
-44%        835.9KB/s 19s
-44%        838.0KB/s 19s
-44%        840.1KB/s 18s
-44%        842.3KB/s 18s
-45%        844.4KB/s 18s
-45%        846.5KB/s 18s
-45%        848.7KB/s 18s
-45%        850.8KB/s 18s
-45%        852.9KB/s 18s
-45%        855.0KB/s 18s
-45%        857.2KB/s 18s
-45%        859.3KB/s 18s
-46%        861.4KB/s 18s
-46%        863.6KB/s 18s
-46%        865.7KB/s 17s
-46%        867.8KB/s 17s
-46%        870.0KB/s 17s
-46%        872.1KB/s 17s
-46%        874.2KB/s 17s
-46%        876.4KB/s 17s
-46%        878.5KB/s 17s
-47%        880.6KB/s 17s
-47%        882.8KB/s 17s
-47%        884.9KB/s 17s
-47%        887.0KB/s 17s
-47%        889.2KB/s 17s
-47%        891.3KB/s 17s
-47%        893.4KB/s 16s
-47%        895.6KB/s 16s
-47%        897.7KB/s 16s
-48%        899.8KB/s 16s
-48%        902.0KB/s 16s
-48%        904.1KB/s 16s
-48%        906.2KB/s 16s
-48%        908.4KB/s 16s
-48%        910.5KB/s 16s
-48%        912.6KB/s 16s
-48%        914.8KB/s 16s
-48%        916.9KB/s 16s
-49%        919.0KB/s 16s
-49%        921.1KB/s 15s
-49%        923.3KB/s 15s
-49%        925.4KB/s 15s
-49%        927.5KB/s 15s
-49%        929.7KB/s 15s
-49%        931.8KB/s 15s
-49%        933.9KB/s 15s
-49%        936.1KB/s 15s
-50%        938.2KB/s 15s
-50%        940.3KB/s 15s
-50%        942.5KB/s 15s
-50%        944.6KB/s 15s
-50%        946.7KB/s 15s
-50%        948.9KB/s 15s
-50%        951.0KB/s 15s
-50%        953.1KB/s 14s
-51%        955.3KB/s 14s
-51%        957.4KB/s 14s
-51%        959.5KB/s 14s
-51%        961.7KB/s 14s
-51%        963.8KB/s 14s
-51%        965.9KB/s 14s
-51%        968.1KB/s 14s
-51%        970.2KB/s 14s
-51%        972.3KB/s 14s
-52%        974.5KB/s 14s
-52%        976.6KB/s 14s
-52%        978.7KB/s 14s
-52%        980.9KB/s 14s
-52%        983.0KB/s 14s
-52%        985.1KB/s 14s
-52%        987.3KB/s 13s
-52%        989.4KB/s 13s
-52%        991.5KB/s 13s
-53%        993.6KB/s 13s
-53%        995.8KB/s 13s
-53%        997.9KB/s 13s
-53%       1000.0KB/s 13s
-53%       1002.2KB/s 13s
-53%       1004.3KB/s 13s
-53%       1006.4KB/s 13s
-53%       1008.6KB/s 13s
-53%       1010.7KB/s 13s
-54%       1012.8KB/s 13s
-54%       1015.0KB/s 13s
-54%       1017.1KB/s 13s
-54%       1019.2KB/s 13s
-54%       1021.4KB/s 12s
-54%       1023.5KB/s 12s
-54%          1.0MB/s 12s
-54%          1.0MB/s 12s
-55%          1.0MB/s 12s
-55%          1.0MB/s 12s
-55%          1.0MB/s 12s
-55%          1.0MB/s 12s
-55%          1.0MB/s 12s
-55%          1.0MB/s 12s
-55%          1.0MB/s 12s
-55%          1.0MB/s 12s
-55%          1.0MB/s 12s
-56%          1.0MB/s 12s
-56%          1.0MB/s 12s
-56%          1.0MB/s 12s
-56%          1.0MB/s 12s
-56%          1.0MB/s 12s
-56%          1.0MB/s 11s
-56%          1.0MB/s 11s
-56%          1.0MB/s 11s
-56%          1.0MB/s 11s
-57%          1.0MB/s 11s
-57%          1.0MB/s 11s
-57%          1.0MB/s 11s
-57%          1.0MB/s 11s
-57%          1.1MB/s 11s
-57%          1.1MB/s 11s
-57%          1.1MB/s 11s
-57%          1.1MB/s 11s
-57%          1.1MB/s 11s
-58%          1.1MB/s 11s
-58%          1.1MB/s 11s
-58%          1.1MB/s 11s
-58%          1.1MB/s 11s
-58%          1.1MB/s 11s
-58%          1.1MB/s 11s
-58%          1.1MB/s 11s
-58%          1.1MB/s 10s
-58%          1.1MB/s 10s
-59%          1.1MB/s 10s
-59%          1.1MB/s 10s
-59%          1.1MB/s 10s
-59%          1.1MB/s 10s
-59%          1.1MB/s 10s
-59%          1.1MB/s 10s
-59%          1.1MB/s 10s
-59%          1.1MB/s 10s
-60%          1.1MB/s 10s
-60%          1.1MB/s 10s
-60%          1.1MB/s 10s
-60%          1.1MB/s 10s
-60%          1.1MB/s 10s
-60%          1.1MB/s 10s
-60%          1.1MB/s 10s
-60%          1.1MB/s 10s
-60%          1.1MB/s 10s
-61%          1.1MB/s 10s
-61%          1.1MB/s 10s
-61%           1.1MB/s 9s
-61%           1.1MB/s 9s
-61%           1.1MB/s 9s
-61%           1.1MB/s 9s
-61%           1.1MB/s 9s
-61%           1.1MB/s 9s
-61%           1.1MB/s 9s
-62%           1.1MB/s 9s
-62%           1.1MB/s 9s
-62%           1.1MB/s 9s
-62%           1.1MB/s 9s
-62%           1.1MB/s 9s
-62%           1.1MB/s 9s
-62%           1.1MB/s 9s
-62%           1.1MB/s 9s
-62%           1.2MB/s 9s
-63%           1.2MB/s 9s
-63%           1.2MB/s 9s
-63%           1.2MB/s 9s
-63%           1.2MB/s 9s
-63%           1.2MB/s 9s
-63%           1.2MB/s 9s
-63%           1.2MB/s 9s
-63%           1.2MB/s 8s
-64%           1.2MB/s 8s
-64%           1.2MB/s 8s
-64%           1.2MB/s 8s
-64%           1.2MB/s 8s
-64%           1.2MB/s 8s
-64%           1.2MB/s 8s
-64%           1.2MB/s 8s
-64%           1.2MB/s 8s
-64%           1.2MB/s 8s
-65%           1.2MB/s 8s
-65%           1.2MB/s 8s
-65%           1.2MB/s 8s
-65%           1.2MB/s 8s
-65%           1.2MB/s 8s
-65%           1.2MB/s 8s
-65%           1.2MB/s 8s
-65%           1.2MB/s 8s
-65%           1.2MB/s 8s
-66%           1.2MB/s 8s
-66%           1.2MB/s 8s
-66%           1.2MB/s 8s
-66%           1.2MB/s 8s
-66%           1.2MB/s 8s
-66%           1.2MB/s 8s
-66%           1.2MB/s 7s
-66%           1.2MB/s 7s
-66%           1.2MB/s 7s
-67%           1.2MB/s 7s
-67%           1.2MB/s 7s
-67%           1.2MB/s 7s
-67%           1.2MB/s 7s
-67%           1.2MB/s 7s
-67%           1.2MB/s 7s
-67%           1.2MB/s 7s
-67%           1.2MB/s 7s
-67%           1.2MB/s 7s
-68%           1.2MB/s 7s
-68%           1.2MB/s 7s
-68%           1.2MB/s 7s
-68%           1.3MB/s 7s
-68%           1.3MB/s 7s
-68%           1.3MB/s 7s
-68%           1.3MB/s 7s
-68%           1.3MB/s 7s
-69%           1.3MB/s 7s
-69%           1.3MB/s 7s
-69%           1.3MB/s 7s
-69%           1.3MB/s 7s
-69%           1.3MB/s 7s
-69%           1.3MB/s 7s
-69%           1.3MB/s 7s
-69%           1.3MB/s 6s
-69%           1.3MB/s 6s
-70%           1.3MB/s 6s
-70%           1.2MB/s 7s
-70%           1.2MB/s 7s
-70%           1.2MB/s 7s
-70%           1.2MB/s 7s
-70%           1.2MB/s 7s
-70%           1.2MB/s 7s
-70%           1.2MB/s 7s
-70%           1.2MB/s 7s
-71%        767.6KB/s 11s
-71%        768.9KB/s 11s
-71%        770.1KB/s 10s
-71%        771.3KB/s 10s
-71%        772.5KB/s 10s
-71%        773.8KB/s 10s
-71%        775.0KB/s 10s
-71%        776.2KB/s 10s
-71%        777.5KB/s 10s
-72%        778.7KB/s 10s
-72%        779.9KB/s 10s
-72%        781.2KB/s 10s
-72%        782.4KB/s 10s
-72%        783.6KB/s 10s
-72%        784.8KB/s 10s
-72%        786.1KB/s 10s
-72%        787.3KB/s 10s
-73%        788.5KB/s 10s
-73%        789.8KB/s 10s
-73%        791.0KB/s 10s
-73%         792.2KB/s 9s
-73%         793.5KB/s 9s
-73%         794.7KB/s 9s
-73%         795.9KB/s 9s
-73%         797.1KB/s 9s
-73%         798.4KB/s 9s
-74%         799.6KB/s 9s
-74%         800.8KB/s 9s
-74%         802.1KB/s 9s
-74%         803.3KB/s 9s
-74%         804.5KB/s 9s
-74%         805.8KB/s 9s
-74%         807.0KB/s 9s
-74%         808.2KB/s 9s
-74%         809.5KB/s 9s
-75%         810.7KB/s 9s
-75%         811.9KB/s 9s
-75%         813.1KB/s 9s
-75%         814.4KB/s 8s
-75%         815.6KB/s 8s
-75%         816.8KB/s 8s
-75%         818.1KB/s 8s
-75%         819.3KB/s 8s
-75%         820.5KB/s 8s
-76%         821.8KB/s 8s
-76%         823.0KB/s 8s
-76%         824.2KB/s 8s
-76%         825.4KB/s 8s
-76%         826.7KB/s 8s
-76%         827.9KB/s 8s
-76%         829.1KB/s 8s
-76%         830.4KB/s 8s
-76%         831.6KB/s 8s
-77%         832.8KB/s 8s
-77%         834.1KB/s 8s
-77%         835.3KB/s 8s
-77%         836.5KB/s 8s
-77%         837.7KB/s 8s
-77%         839.0KB/s 7s
-77%         840.2KB/s 7s
-77%         841.4KB/s 7s
-78%         842.7KB/s 7s
-78%         843.9KB/s 7s
-78%         845.1KB/s 7s
-78%         846.4KB/s 7s
-78%         847.6KB/s 7s
-78%         848.8KB/s 7s
-78%         850.0KB/s 7s
-78%         851.3KB/s 7s
-78%         852.5KB/s 7s
-79%         853.7KB/s 7s
-79%         855.0KB/s 7s
-79%         856.2KB/s 7s
-79%         857.4KB/s 7s
-79%         858.7KB/s 7s
-79%         859.9KB/s 7s
-79%         861.1KB/s 7s
-79%         862.3KB/s 7s
-79%         863.6KB/s 7s
-80%         864.8KB/s 6s
-80%         866.0KB/s 6s
-80%         867.3KB/s 6s
-80%         868.5KB/s 6s
-80%         869.7KB/s 6s
-80%         871.0KB/s 6s
-80%         872.2KB/s 6s
-80%         873.4KB/s 6s
-80%         874.6KB/s 6s
-81%         875.9KB/s 6s
-81%         877.1KB/s 6s
-81%         878.3KB/s 6s
-81%         879.6KB/s 6s
-81%         880.8KB/s 6s
-81%         882.0KB/s 6s
-81%         883.3KB/s 6s
-81%         884.5KB/s 6s
-82%         885.7KB/s 6s
-82%         887.0KB/s 6s
-82%         888.2KB/s 6s
-82%         889.4KB/s 6s
-82%         890.6KB/s 6s
-82%         891.9KB/s 5s
-82%         893.1KB/s 5s
-82%         894.3KB/s 5s
-82%         895.6KB/s 5s
-83%         896.8KB/s 5s
-83%         898.0KB/s 5s
-83%         899.3KB/s 5s
-83%         900.5KB/s 5s
-83%         901.7KB/s 5s
-83%         902.9KB/s 5s
-83%         904.2KB/s 5s
-83%         905.4KB/s 5s
-83%         906.6KB/s 5s
-84%         907.9KB/s 5s
-84%         909.1KB/s 5s
-84%         910.3KB/s 5s
-84%         911.6KB/s 5s
-84%         912.8KB/s 5s
-84%         914.0KB/s 5s
-84%         915.2KB/s 5s
-84%         916.5KB/s 5s
-84%         917.7KB/s 5s
-85%         918.9KB/s 5s
-85%         920.2KB/s 5s
-85%         921.4KB/s 4s
-85%         922.6KB/s 4s
-85%         923.9KB/s 4s
-85%         925.1KB/s 4s
-85%         926.3KB/s 4s
-85%         927.5KB/s 4s
-85%         928.8KB/s 4s
-86%         930.0KB/s 4s
-86%         931.2KB/s 4s
-86%         932.5KB/s 4s
-86%         933.7KB/s 4s
-86%         934.9KB/s 4s
-86%         936.2KB/s 4s
-86%         937.4KB/s 4s
-86%         938.6KB/s 4s
-87%         939.8KB/s 4s
-87%         941.1KB/s 4s
-87%         942.3KB/s 4s
-87%         943.5KB/s 4s
-87%         944.8KB/s 4s
-87%         946.0KB/s 4s
-87%         947.2KB/s 4s
-87%         948.5KB/s 4s
-87%         949.7KB/s 4s
-88%         950.9KB/s 4s
-88%         952.1KB/s 3s
-88%         953.4KB/s 3s
-88%         954.6KB/s 3s
-88%         955.8KB/s 3s
-88%         957.1KB/s 3s
-88%         958.3KB/s 3s
-88%         959.5KB/s 3s
-88%         960.8KB/s 3s
-89%         962.0KB/s 3s
-89%         963.2KB/s 3s
-89%         964.5KB/s 3s
-89%         965.7KB/s 3s
-89%         966.9KB/s 3s
-89%         968.1KB/s 3s
-89%         969.4KB/s 3s
-89%         970.6KB/s 3s
-89%         971.8KB/s 3s
-90%         973.1KB/s 3s
-90%         974.3KB/s 3s
-90%         975.5KB/s 3s
-90%         976.8KB/s 3s
-90%         941.8KB/s 3s
-90%         942.9KB/s 3s
-90%         944.1KB/s 3s
-90%         945.3KB/s 3s
-91%         946.5KB/s 3s
-91%         947.7KB/s 3s
-91%         948.9KB/s 3s
-91%         950.1KB/s 3s
-91%         951.2KB/s 3s
-91%         952.4KB/s 2s
-91%         953.6KB/s 2s
-91%         954.8KB/s 2s
-91%         956.0KB/s 2s
-92%         957.2KB/s 2s
-92%         958.3KB/s 2s
-92%         959.5KB/s 2s
-92%         960.7KB/s 2s
-92%         961.9KB/s 2s
-92%         963.1KB/s 2s
-92%         964.3KB/s 2s
-92%         965.5KB/s 2s
-92%         966.6KB/s 2s
-93%         967.8KB/s 2s
-93%         969.0KB/s 2s
-93%         970.2KB/s 2s
-93%         971.4KB/s 2s
-93%         972.6KB/s 2s
-93%         973.7KB/s 2s
-93%         974.9KB/s 2s
-93%         976.1KB/s 2s
-93%         977.3KB/s 2s
-94%         978.5KB/s 2s
-94%         979.7KB/s 2s
-94%         980.9KB/s 2s
-94%         982.0KB/s 2s
-94%         983.2KB/s 2s
-94%         984.4KB/s 2s
-94%         985.6KB/s 1s
-94%         986.8KB/s 1s
-94%         988.0KB/s 1s
-95%         989.1KB/s 1s
-95%         990.3KB/s 1s
-95%         991.5KB/s 1s
-95%         992.7KB/s 1s
-95%         993.9KB/s 1s
-95%         995.1KB/s 1s
-95%         996.3KB/s 1s
-95%         997.4KB/s 1s
-96%         998.6KB/s 1s
-96%         999.8KB/s 1s
-96%        1001.0KB/s 1s
-96%        1002.2KB/s 1s
-96%        1003.4KB/s 1s
-96%        1004.5KB/s 1s
-96%        1005.7KB/s 1s
-96%        1006.9KB/s 1s
-96%        1008.1KB/s 1s
-97%        1009.3KB/s 1s
-97%        1010.5KB/s 1s
-97%        1011.7KB/s 1s
-97%        1012.8KB/s 1s
-97%        1014.0KB/s 1s
-97%        1015.2KB/s 1s
-97%        1016.4KB/s 1s
-97%        1017.6KB/s 1s
-97%        1018.8KB/s 1s
-98%        1019.9KB/s 1s
-98%        1021.1KB/s 1s
-98%        1022.3KB/s 0s
-98%        1023.5KB/s 0s
-98%           1.0MB/s 0s
-98%           1.0MB/s 0s
-98%           1.0MB/s 0s
-98%           1.0MB/s 0s
-98%           1.0MB/s 0s
-99%           1.0MB/s 0s
-99%           1.0MB/s 0s
-99%           1.0MB/s 0s
-99%           1.0MB/s 0s
-99%           1.0MB/s 0s
-99%           1.0MB/s 0s
-99%           1.0MB/s 0s
-99%           1.0MB/s 0s
-99%           1.0MB/s 0s
-100%          1.0MB/s 0s
-                        
-[2014-01-16 19:59:44 CET] Transferrer: Uploaded git-annex.. upgrade)
-
-(Recording state in git...)
-(\"remove\",\"/Applications/git-annex.app/Contents/MacOS\")
-(\"remove\",\"/Applications/git-annex.app/Contents/MacOS/bundle\")
-(\"remove\",\"/Applications/git-annex.app/Contents/MacOS/bundle/A\")
-(Recording state in git...)
-(Recording state in git...)
-[2014-01-16 19:58:59 CET] main: starting assistant version 5.20140116-gd2fce02
-[2014-01-16 19:58:59 CET] UpgradeWatcher: Finished upgrading git-annex to version 5.20140116-gd2fce02 
-(scanning...) [2014-01-16 19:58:59 CET] Watcher: Performing startup scan
-(started...) [2014-01-16 20:02:54 CET] main: starting assistant version 5.20131221-g00d1673
-(scanning...) [2014-01-16 20:02:54 CET] Watcher: Performing startup scan
-(started...) --2014-01-16 20:02:54--  https://downloads.kitenet.net/git-annex/OSX/current/10.9_Mavericks/git-annex.dmg
-Resolving downloads.kitenet.net... 80.68.85.49, 2001:41c8:125:49::10
-Connecting to downloads.kitenet.net|80.68.85.49|:443... connected.
-HTTP request sent, awaiting response... 200 OK
-Length: 28756861 (27M) [application/x-apple-diskimage]
-Saving to: ‘/Users/kraft/annex/.git/annex/tmp/SHA256E-s28756861--4bea2d816a701dbfc88eada2288019c92c2774ee605e4ddfa62c4dd7655e53a1.dmg’
-
-     0K .......... .......... .......... .......... ..........  0%  678K 41s
-    50K .......... .......... .......... .......... ..........  0% 2.61M 26s
-   100K .......... .......... .......... .......... ..........  0% 2.14M 21s
-   150K .......... .......... .......... .......... ..........  0% 2.16M 19s
-   200K .......... .......... .......... .......... ..........  0% 9.99M 16s
-   250K .......... .......... .......... .......... ..........  1% 1.15M 17s
-   300K .......... .......... .......... .......... ..........  1% 26.1M 15s
-   350K .......... .......... .......... .......... ..........  1% 37.0M 13s
-   400K .......... .......... .......... .......... ..........  1% 6.50M 12s
-   450K .......... .......... .......... .......... ..........  1%  917K 14s
-   500K .......... .......... .......... .......... ..........  1% 29.0M 13s
-   550K .......... .......... .......... .......... ..........  2% 41.5M 12s
-   600K .......... .......... .......... .......... ..........  2% 40.6M 11s
-   650K .......... .......... .......... .......... ..........  2% 3.43M 11s
-   700K .......... .......... .......... .......... ..........  2% 3.18M 10s
-   750K .......... .......... .......... .......... ..........  2% 10.8M 10s
-   800K .......... .......... .......... .......... ..........  3% 5.03M 10s
-   850K .......... .......... .......... .......... ..........  3% 3.04M 9s
-   900K .......... .......... .......... .......... ..........  3% 13.2M 9s
-   950K .......... .......... .......... .......... ..........  3% 6.36M 9s
-  1000K .......... .......... .......... .......... ..........  3% 2.83M 9s
-  1050K .......... .......... .......... .......... ..........  3% 17.0M 8s
-  1100K .......... .......... .......... .......... ..........  4% 10.8M 8s
-  1150K .......... .......... .......... .......... ..........  4% 7.25M 8s
-  1200K .......... .......... .......... .......... ..........  4% 2.73M 8s
-  1250K .......... .......... .......... .......... ..........  4% 11.7M 8s
-  1300K .......... .......... .......... .......... ..........  4% 10.7M 8s
-  1350K .......... .......... .......... .......... ..........  4% 10.3M 7s
-  1400K .......... .......... .......... .......... ..........  5% 3.03M 7s
-  1450K .......... .......... .......... .......... ..........  5% 10.4M 7s
-  1500K .......... .......... .......... .......... ..........  5% 13.9M 7s
-  1550K .......... .......... .......... .......... ..........  5% 10.4M 7s
-  1600K .......... .......... .......... .......... ..........  5% 2.54M 7s
-  1650K .......... .......... .......... .......... ..........  6% 17.4M 7s
-  1700K .......... .......... .......... .......... ..........  6% 12.4M 7s
-  1750K .......... .......... .......... .......... ..........  6% 13.7M 7s
-  1800K .......... .......... .......... .......... ..........  6% 3.06M 7s
-  1850K .......... .......... .......... .......... ..........  6% 10.6M 6s
-  1900K .......... .......... .......... .......... ..........  6% 10.6M 6s
-  1950K .......... .......... .......... .......... ..........  7% 10.9M 6s
-  2000K .......... .......... .......... .......... ..........  7% 3.54M 6s
-  2050K .......... .......... .......... .......... ..........  7% 8.47M 6s
-  2100K .......... .......... .......... .......... ..........  7% 13.6M 6s
-  2150K .......... .......... .......... .......... ..........  7% 10.5M 6s
-  2200K .......... .......... .......... .......... ..........  8% 10.1M 6s
-  2250K .......... .......... .......... .......... ..........  8% 3.53M 6s
-  2300K .......... .......... .......... .......... ..........  8% 13.7M 6s
-  2350K .......... .......... .......... .......... ..........  8% 11.1M 6s
-  2400K .......... .......... .......... .......... ..........  8% 8.59M 6s
-  2450K .......... .......... .......... .......... ..........  8% 4.69M 6s
-  2500K .......... .......... .......... .......... ..........  9% 8.56M 6s
-  2550K .......... .......... .......... .......... ..........  9% 10.6M 5s
-  2600K .......... .......... .......... .......... ..........  9% 10.9M 5s
-  2650K .......... .......... .......... .......... ..........  9% 10.4M 5s
-  2700K .......... .......... .......... .......... ..........  9% 13.6M 5s
-  2750K .......... .......... .......... .......... ..........  9% 4.73M 5s
-  2800K .......... .......... .......... .......... .......... 10% 6.21M 5s
-  2850K .......... .......... .......... .......... .......... 10% 10.4M 5s
-  2900K .......... .......... .......... .......... .......... 10% 14.2M 5s
-  2950K .......... .......... .......... .......... .......... 10% 8.62M 5s
-  3000K .......... .......... .......... .......... .......... 10% 5.97M 5s
-  3050K .......... .......... .......... .......... .......... 11% 11.0M 5s
-  3100K .......... .......... .......... .......... .......... 11% 10.6M 5s
-  3150K .......... .......... .......... .......... .......... 11% 10.1M 5s
-  3200K .......... .......... .......... .......... .......... 11% 8.09M 5s
-  3250K .......... .......... .......... .......... .......... 11% 8.28M 5s
-  3300K .......... .......... .......... .......... .......... 11% 7.31M 5s
-  3350K .......... .......... .......... .......... .......... 12% 11.1M 5s
-  3400K .......... .......... .......... .......... .......... 12% 13.2M 5s
-  3450K .......... .......... .......... .......... .......... 12% 8.47M 5s
-  3500K .......... .......... .......... .......... .......... 12% 13.7M 5s
-  3550K .......... .......... .......... .......... .......... 12% 10.3M 5s
-  3600K .......... .......... .......... .......... .......... 12% 5.25M 5s
-  3650K .......... .......... .......... .......... .......... 13% 6.90M 4s
-  3700K .......... .......... .......... .......... .......... 13% 12.2M 4s
-  3750K .......... .......... .......... .......... .......... 13% 32.1M 4s
-  3800K .......... .......... .......... .......... .......... 13% 9.01M 4s
-  3850K .......... .......... .......... .......... .......... 13% 7.23M 4s
-  3900K .......... .......... .......... .......... .......... 14% 6.05M 4s
-  3950K .......... .......... .......... .......... .......... 14% 11.7M 4s
-  4000K .......... .......... .......... .......... .......... 14% 8.74M 4s
-  4050K .......... .......... .......... .......... .......... 14% 10.8M 4s
-  4100K .......... .......... .......... .......... .......... 14% 10.6M 4s
-  4150K .......... .......... .......... .......... .......... 14% 10.9M 4s
-  4200K .......... .......... .......... .......... .......... 15% 8.60M 4s
-  4250K .......... .......... .......... .......... .......... 15% 8.74M 4s
-  4300K .......... .......... .......... .......... .......... 15% 13.0M 4s
-  4350K .......... .......... .......... .......... .......... 15% 11.0M 4s
-  4400K .......... .......... .......... .......... .......... 15% 9.44M 4s
-  4450K .......... .......... .......... .......... .......... 16% 10.8M 4s
-  4500K .......... .......... .......... .......... .......... 16% 10.3M 4s
-  4550K .......... .......... .......... .......... .......... 16% 10.7M 4s
-  4600K .......... .......... .......... .......... .......... 16% 10.7M 4s
-  4650K .......... .......... .......... .......... .......... 16% 10.5M 4s
-  4700K .......... .......... .......... .......... .......... 16% 11.2M 4s
-  4750K .......... .......... .......... .......... .......... 17% 11.1M 4s
-  4800K .......... .......... .......... .......... .......... 17% 8.86M 4s
-  4850K .......... .......... .......... .......... .......... 17% 10.4M 4s
-  4900K .......... .......... .......... .......... .......... 17% 9.17M 4s
-  4950K .......... .......... .......... .......... .......... 17% 17.9M 4s
-  5000K .......... .......... .......... .......... .......... 17% 10.7M 4s
-  5050K .......... .......... .......... .......... .......... 18% 10.6M 4s
-  5100K .......... .......... .......... .......... .......... 18% 13.5M 4s
-  5150K .......... .......... .......... .......... .......... 18% 9.65M 4s
-  5200K .......... .......... .......... .......... .......... 18% 9.31M 4s
-  5250K .......... .......... .......... .......... .......... 18% 10.7M 4s
-  5300K .......... .......... .......... .......... .......... 19% 13.8M 4s
-  5350K .......... .......... .......... .......... .......... 19% 8.37M 4s
-  5400K .......... .......... .......... .......... .......... 19% 8.20M 4s
-  5450K .......... .......... .......... .......... .......... 19% 14.5M 3s
-  5500K .......... .......... .......... .......... .......... 19% 10.2M 3s
-  5550K .......... .......... .......... .......... .......... 19% 14.4M 3s
-  5600K .......... .......... .......... .......... .......... 20% 7.02M 3s
-  5650K .......... .......... .......... .......... .......... 20% 8.57M 3s
-  5700K .......... .......... .......... .......... .......... 20% 10.1M 3s
-  5750K .......... .......... .......... .......... .......... 20% 14.4M 3s
-  5800K .......... .......... .......... .......... .......... 20% 10.2M 3s
-  5850K .......... .......... .......... .......... .......... 21% 10.6M 3s
-  5900K .......... .......... .......... .......... .......... 21% 13.6M 3s
-  5950K .......... .......... .......... .......... .......... 21% 10.8M 3s
-  6000K .......... .......... .......... .......... .......... 21% 8.41M 3s
-  6050K .......... .......... .......... .......... .......... 21% 14.0M 3s
-  6100K .......... .......... .......... .......... .......... 21% 10.3M 3s
-  6150K .......... .......... .......... .......... .......... 22% 13.9M 3s
-  6200K .......... .......... .......... .......... .......... 22% 10.5M 3s
-  6250K .......... .......... .......... .......... .......... 22% 10.6M 3s
-  6300K .......... .......... .......... .......... .......... 22% 13.9M 3s
-  6350K .......... .......... .......... .......... .......... 22% 10.9M 3s
-  6400K .......... .......... .......... .......... .......... 22% 8.47M 3s
-  6450K .......... .......... .......... .......... .......... 23% 13.9M 3s
-  6500K .......... .......... .......... .......... .......... 23% 11.0M 3s
-  6550K .......... .......... .......... .......... .......... 23% 10.6M 3s
-  6600K .......... .......... .......... .......... .......... 23% 10.3M 3s
-  6650K .......... .......... .......... .......... .......... 23% 13.3M 3s
-  6700K .......... .......... .......... .......... .......... 24% 10.7M 3s
-  6750K .......... .......... .......... .......... .......... 24% 13.9M 3s
-  6800K .......... .......... .......... .......... .......... 24% 6.09M 3s
-  6850K .......... .......... .......... .......... .......... 24% 11.0M 3s
-  6900K .......... .......... .......... .......... .......... 24% 10.6M 3s
-  6950K .......... .......... .......... .......... .......... 24% 10.6M 3s
-  7000K .......... .......... .......... .......... .......... 25% 10.2M 3s
-  7050K .......... .......... .......... .......... .......... 25% 13.6M 3s
-  7100K .......... .......... .......... .......... .......... 25% 7.14M 3s
-  7150K .......... .......... .......... .......... .......... 25% 13.7M 3s
-  7200K .......... .......... .......... .......... .......... 25% 8.64M 3s
-  7250K .......... .......... .......... .......... .......... 25% 10.5M 3s
-  7300K .......... .......... .......... .......... .......... 26% 13.8M 3s
-  7350K .......... .......... .......... .......... .......... 26% 10.3M 3s
-  7400K .......... .......... .......... .......... .......... 26% 10.7M 3s
-  7450K .......... .......... .......... .......... .......... 26% 13.9M 3s
-  7500K .......... .......... .......... .......... .......... 26% 10.6M 3s
-  7550K .......... .......... .......... .......... .......... 27% 10.4M 3s
-  7600K .......... .......... .......... .......... .......... 27% 10.6M 3s
-  7650K .......... .......... .......... .......... .......... 27% 10.6M 3s
-  7700K .......... .......... .......... .......... .......... 27% 10.4M 3s
-  7750K .......... .......... .......... .......... .......... 27% 13.3M 3s
-  7800K .......... .......... .......... .......... .......... 27% 10.9M 3s
-  7850K .......... .......... .......... .......... .......... 28% 10.7M 3s
-  7900K .......... .......... .......... .......... .......... 28% 13.4M 3s
-  7950K .......... .......... .......... .......... .......... 28% 10.6M 3s
-  8000K .......... .......... .......... .......... .......... 28% 8.99M 3s
-  8050K .......... .......... .......... .......... .......... 28% 10.4M 3s
-  8100K .......... .......... .......... .......... .......... 29% 13.4M 3s
-  8150K .......... .......... .......... .......... .......... 29% 11.1M 3s
-  8200K .......... .......... .......... .......... .......... 29% 10.3M 3s
-  8250K .......... .......... .......... .......... .......... 29% 8.12M 3s
-  8300K .......... .......... .......... .......... .......... 29% 10.9M 3s
-  8350K .......... .......... .......... .......... .......... 29% 10.9M 3s
-  8400K .......... .......... .......... .......... .......... 30% 8.68M 3s
-  8450K .......... .......... .......... .......... .......... 30% 10.2M 3s
-  8500K .......... .......... .......... .......... .......... 30% 11.0M 3s
-  8550K .......... .......... .......... .......... .......... 30% 8.39M 3s
-  8600K .......... .......... .......... .......... .......... 30% 13.2M 3s
-  8650K .......... .......... .......... .......... .......... 30% 10.4M 3s
-  8700K .......... .......... .......... .......... .......... 31% 10.9M 3s
-  8750K .......... .......... .......... .......... .......... 31% 13.6M 3s
-  8800K .......... .......... .......... .......... .......... 31% 8.53M 3s
-  8850K .......... .......... .......... .......... .......... 31% 13.5M 3s
-  8900K .......... .......... .......... .......... .......... 31% 10.8M 2s
-  8950K .......... .......... .......... .......... .......... 32% 10.3M 2s
-  9000K .......... .......... .......... .......... .......... 32% 4.73M 2s
-  9050K .......... .......... .......... .......... .......... 32% 10.7M 2s
-  9100K .......... .......... .......... .......... .......... 32% 22.9M 2s
-  9150K .......... .......... .......... .......... .......... 32% 21.4M 2s
-  9200K .......... .......... .......... .......... .......... 32% 16.9M 2s
-  9250K .......... .......... .......... .......... .......... 33% 10.8M 2s
-  9300K .......... .......... .......... .......... .......... 33% 11.3M 2s
-  9350K .......... .......... .......... .......... .......... 33% 10.5M 2s
-  9400K .......... .......... .......... .......... .......... 33% 14.1M 2s
-  9450K .......... .......... .......... .......... .......... 33% 11.4M 2s
-  9500K .......... .......... .......... .......... .......... 34% 10.4M 2s
-  9550K .......... .......... .......... .......... .......... 34% 10.7M 2s
-  9600K .......... .......... .......... .......... .......... 34% 8.70M 2s
-  9650K .......... .......... .......... .......... .......... 34% 14.2M 2s
-  9700K .......... .......... .......... .......... .......... 34% 10.6M 2s
-  9750K .......... .......... .......... .......... .......... 34% 8.24M 2s
-  9800K .......... .......... .......... .......... .......... 35% 10.6M 2s
-  9850K .......... .......... .......... .......... .......... 35% 10.3M 2s
-  9900K .......... .......... .......... .......... .......... 35% 10.5M 2s
-  9950K .......... .......... .......... .......... .......... 35% 10.8M 2s
- 10000K .......... .......... .......... .......... .......... 35% 8.75M 2s
- 10050K .......... .......... .......... .......... .......... 35% 14.2M 2s
- 10100K .......... .......... .......... .......... .......... 36% 10.9M 2s
- 10150K .......... .......... .......... .......... .......... 36% 11.3M 2s
- 10200K .......... .......... .......... .......... .......... 36% 10.2M 2s
- 10250K .......... .......... .......... .......... .......... 36% 15.1M 2s
- 10300K .......... .......... .......... .......... .......... 36% 10.7M 2s
- 10350K .......... .......... .......... .......... .......... 37% 11.1M 2s
- 10400K .......... .......... .......... .......... .......... 37% 8.88M 2s
- 10450K .......... .......... .......... .......... .......... 37% 11.1M 2s
- 10500K .......... .......... .......... .......... .......... 37% 10.9M 2s
- 10550K .......... .......... .......... .......... .......... 37% 10.8M 2s
- 10600K .......... .......... .......... .......... .......... 37% 13.8M 2s
- 10650K .......... .......... .......... .......... .......... 38% 11.0M 2s
- 10700K .......... .......... .......... .......... .......... 38% 10.4M 2s
- 10750K .......... .......... .......... .......... .......... 38% 10.7M 2s
- 10800K .......... .......... .......... .......... .......... 38% 10.7M 2s
- 10850K .......... .......... .......... .......... .......... 38% 10.5M 2s
- 10900K .......... .......... .......... .......... .......... 38% 11.0M 2s
- 10950K .......... .......... .......... .......... .......... 39% 13.2M 2s
- 11000K .......... .......... .......... .......... .......... 39% 10.4M 2s
- 11050K .......... .......... .......... .......... .......... 39% 14.1M 2s
- 11100K .......... .......... .......... .......... .......... 39% 10.1M 2s
- 11150K .......... .......... .......... .......... .......... 39% 10.6M 2s
- 11200K .......... .......... .......... .......... .......... 40% 10.3M 2s
- 11250K .......... .......... .......... .......... .......... 40% 10.7M 2s
- 11300K .......... .......... .......... .......... .......... 40% 10.6M 2s
- 11350K .......... .......... .......... .......... .......... 40% 14.0M 2s
- 11400K .......... .......... .......... .......... .......... 40% 10.2M 2s
- 11450K .......... .......... .......... .......... .......... 40% 11.1M 2s
- 11500K .......... .......... .......... .......... .......... 41% 13.6M 2s
- 11550K .......... .......... .......... .......... .......... 41% 10.6M 2s
- 11600K .......... .......... .......... .......... .......... 41% 8.08M 2s
- 11650K .......... .......... .......... .......... .......... 41% 15.4M 2s
- 11700K .......... .......... .......... .......... .......... 41% 10.4M 2s
- 11750K .......... .......... .......... .......... .......... 42% 13.9M 2s
- 11800K .......... .......... .......... .......... .......... 42% 10.6M 2s
- 11850K .......... .......... .......... .......... .......... 42% 10.5M 2s
- 11900K .......... .......... .......... .......... .......... 42% 13.5M 2s
- 11950K .......... .......... .......... .......... .......... 42% 10.5M 2s
- 12000K .......... .......... .......... .......... .......... 42% 8.47M 2s
- 12050K .......... .......... .......... .......... .......... 43% 13.8M 2s
- 12100K .......... .......... .......... .......... .......... 43% 10.5M 2s
- 12150K .......... .......... .......... .......... .......... 43% 10.5M 2s
- 12200K .......... .......... .......... .......... .......... 43% 13.3M 2s
- 12250K .......... .......... .......... .......... .......... 43% 10.5M 2s
- 12300K .......... .......... .......... .......... .......... 43% 14.2M 2s
- 12350K .......... .......... .......... .......... .......... 44% 10.6M 2s
- 12400K .......... .......... .......... .......... .......... 44% 8.62M 2s
- 12450K .......... .......... .......... .......... .......... 44% 10.6M 2s
- 12500K .......... .......... .......... .......... .......... 44% 13.9M 2s
- 12550K .......... .......... .......... .......... .......... 44% 10.1M 2s
- 12600K .......... .......... .......... .......... .......... 45% 14.0M 2s
- 12650K .......... .......... .......... .......... .......... 45% 10.8M 2s
- 12700K .......... .......... .......... .......... .......... 45% 10.5M 2s
- 12750K .......... .......... .......... .......... .......... 45% 13.5M 2s
- 12800K .......... .......... .......... .......... .......... 45% 8.55M 2s
- 12850K .......... .......... .......... .......... .......... 45% 10.2M 2s
- 12900K .......... .......... .......... .......... .......... 46% 15.4M 2s
- 12950K .......... .......... .......... .......... .......... 46% 10.6M 2s
- 13000K .......... .......... .......... .......... .......... 46% 10.2M 2s
- 13050K .......... .......... .......... .......... .......... 46% 14.0M 2s
- 13100K .......... .......... .......... .......... .......... 46% 10.5M 2s
- 13150K .......... .......... .......... .......... .......... 47% 13.8M 2s
- 13200K .......... .......... .......... .......... .......... 47% 7.17M 2s
- 13250K .......... .......... .......... .......... .......... 47% 15.1M 2s
- 13300K .......... .......... .......... .......... .......... 47% 10.4M 2s
- 13350K .......... .......... .......... .......... .......... 47% 14.4M 2s
- 13400K .......... .......... .......... .......... .......... 47% 10.2M 2s
- 13450K .......... .......... .......... .......... .......... 48% 10.7M 2s
- 13500K .......... .......... .......... .......... .......... 48% 13.8M 2s
- 13550K .......... .......... .......... .......... .......... 48% 10.8M 2s
- 13600K .......... .......... .......... .......... .......... 48% 8.70M 2s
- 13650K .......... .......... .......... .......... .......... 48% 10.3M 2s
- 13700K .......... .......... .......... .......... .......... 48% 13.6M 2s
- 13750K .......... .......... .......... .......... .......... 49% 10.9M 2s
- 13800K .......... .......... .......... .......... .......... 49% 13.2M 2s
- 13850K .......... .......... .......... .......... .......... 49% 10.6M 2s
- 13900K .......... .......... .......... .......... .......... 49% 13.6M 2s
- 13950K .......... .......... .......... .......... .......... 49% 10.9M 2s
- 14000K .......... .......... .......... .......... .......... 50% 8.44M 2s
- 14050K .......... .......... .......... .......... .......... 50% 10.9M 2s
- 14100K .......... .......... .......... .......... .......... 50% 10.5M 2s
- 14150K .......... .......... .......... .......... .......... 50% 13.8M 2s
- 14200K .......... .......... .......... .......... .......... 50% 10.4M 2s
- 14250K .......... .......... .......... .......... .......... 50% 13.9M 2s
- 14300K .......... .......... .......... .......... .......... 51% 10.3M 2s
- 14350K .......... .......... .......... .......... .......... 51% 11.1M 2s
- 14400K .......... .......... .......... .......... .......... 51% 10.3M 2s
- 14450K .......... .......... .......... .......... .......... 51% 10.1M 2s
- 14500K .......... .......... .......... .......... .......... 51% 10.9M 2s
- 14550K .......... .......... .......... .......... .......... 51% 14.1M 2s
- 14600K .......... .......... .......... .......... .......... 52% 10.4M 2s
- 14650K .......... .......... .......... .......... .......... 52% 13.1M 2s
- 14700K .......... .......... .......... .......... .......... 52% 6.99M 2s
- 14750K .......... .......... .......... .......... .......... 52% 18.7M 2s
- 14800K .......... .......... .......... .......... .......... 52% 10.0M 2s
- 14850K .......... .......... .......... .......... .......... 53% 13.6M 1s
- 14900K .......... .......... .......... .......... .......... 53% 10.8M 1s
- 14950K .......... .......... .......... .......... .......... 53% 10.9M 1s
- 15000K .......... .......... .......... .......... .......... 53% 13.7M 1s
- 15050K .......... .......... .......... .......... .......... 53% 10.6M 1s
- 15100K .......... .......... .......... .......... .......... 53% 10.3M 1s
- 15150K .......... .......... .......... .......... .......... 54% 14.2M 1s
- 15200K .......... .......... .......... .......... .......... 54% 8.33M 1s
- 15250K .......... .......... .......... .......... .......... 54% 11.4M 1s
- 15300K .......... .......... .......... .......... .......... 54% 13.7M 1s
- 15350K .......... .......... .......... .......... .......... 54% 10.3M 1s
- 15400K .......... .......... .......... .......... .......... 55% 11.0M 1s
- 15450K .......... .......... .......... .......... .......... 55% 10.8M 1s
- 15500K .......... .......... .......... .......... .......... 55% 13.6M 1s
- 15550K .......... .......... .......... .......... .......... 55% 11.0M 1s
- 15600K .......... .......... .......... .......... .......... 55% 8.67M 1s
- 15650K .......... .......... .......... .......... .......... 55% 13.5M 1s
- 15700K .......... .......... .......... .......... .......... 56% 10.7M 1s
- 15750K .......... .......... .......... .......... .......... 56% 10.4M 1s
- 15800K .......... .......... .......... .......... .......... 56% 13.6M 1s
- 15850K .......... .......... .......... .......... .......... 56% 10.5M 1s
- 15900K .......... .......... .......... .......... .......... 56% 13.6M 1s
- 15950K .......... .......... .......... .......... .......... 56% 10.4M 1s
- 16000K .......... .......... .......... .......... .......... 57% 8.40M 1s
- 16050K .......... .......... .......... .......... .......... 57% 13.9M 1s
- 16100K .......... .......... .......... .......... .......... 57% 10.3M 1s
- 16150K .......... .......... .......... .......... .......... 57% 13.7M 1s
- 16200K .......... .......... .......... .......... .......... 57% 10.7M 1s
- 16250K .......... .......... .......... .......... .......... 58% 10.9M 1s
- 16300K .......... .......... .......... .......... .......... 58% 13.7M 1s
- 16350K .......... .......... .......... .......... .......... 58% 10.1M 1s
- 16400K .......... .......... .......... .......... .......... 58% 8.63M 1s
- 16450K .......... .......... .......... .......... .......... 58% 14.2M 1s
- 16500K .......... .......... .......... .......... .......... 58% 10.3M 1s
- 16550K .......... .......... .......... .......... .......... 59% 10.7M 1s
- 16600K .......... .......... .......... .......... .......... 59% 13.7M 1s
- 16650K .......... .......... .......... .......... .......... 59% 10.4M 1s
- 16700K .......... .......... .......... .......... .......... 59% 13.7M 1s
- 16750K .......... .......... .......... .......... .......... 59% 10.9M 1s
- 16800K .......... .......... .......... .......... .......... 60% 8.52M 1s
- 16850K .......... .......... .......... .......... .......... 60% 10.7M 1s
- 16900K .......... .......... .......... .......... .......... 60% 13.7M 1s
- 16950K .......... .......... .......... .......... .......... 60% 10.5M 1s
- 17000K .......... .......... .......... .......... .......... 60% 13.5M 1s
- 17050K .......... .......... .......... .......... .......... 60% 10.3M 1s
- 17100K .......... .......... .......... .......... .......... 61% 10.0M 1s
- 17150K .......... .......... .......... .......... .......... 61% 14.5M 1s
- 17200K .......... .......... .......... .......... .......... 61% 8.33M 1s
- 17250K .......... .......... .......... .......... .......... 61% 11.0M 1s
- 17300K .......... .......... .......... .......... .......... 61% 13.5M 1s
- 17350K .......... .......... .......... .......... .......... 61% 10.6M 1s
- 17400K .......... .......... .......... .......... .......... 62% 10.3M 1s
- 17450K .......... .......... .......... .......... .......... 62% 13.5M 1s
- 17500K .......... .......... .......... .......... .......... 62% 10.3M 1s
- 17550K .......... .......... .......... .......... .......... 62% 14.2M 1s
- 17600K .......... .......... .......... .......... .......... 62% 8.63M 1s
- 17650K .......... .......... .......... .......... .......... 63% 10.5M 1s
- 17700K .......... .......... .......... .......... .......... 63% 6.89M 1s
- 17750K .......... .......... .......... .......... .......... 63% 13.9M 1s
- 17800K .......... .......... .......... .......... .......... 63% 10.3M 1s
- 17850K .......... .......... .......... .......... .......... 63% 10.4M 1s
- 17900K .......... .......... .......... .......... .......... 63% 13.5M 1s
- 17950K .......... .......... .......... .......... .......... 64% 10.6M 1s
- 18000K .......... .......... .......... .......... .......... 64% 8.49M 1s
- 18050K .......... .......... .......... .......... .......... 64% 14.3M 1s
- 18100K .......... .......... .......... .......... .......... 64% 10.6M 1s
- 18150K .......... .......... .......... .......... .......... 64% 11.5M 1s
- 18200K .......... .......... .......... .......... .......... 64% 10.2M 1s
- 18250K .......... .......... .......... .......... .......... 65% 13.7M 1s
- 18300K .......... .......... .......... .......... .......... 65% 10.4M 1s
- 18350K .......... .......... .......... .......... .......... 65% 13.7M 1s
- 18400K .......... .......... .......... .......... .......... 65% 8.40M 1s
- 18450K .......... .......... .......... .......... .......... 65% 10.7M 1s
- 18500K .......... .......... .......... .......... .......... 66% 13.6M 1s
- 18550K .......... .......... .......... .......... .......... 66% 10.8M 1s
- 18600K .......... .......... .......... .......... .......... 66% 13.2M 1s
- 18650K .......... .......... .......... .......... .......... 66% 10.4M 1s
- 18700K .......... .......... .......... .......... .......... 66% 10.8M 1s
- 18750K .......... .......... .......... .......... .......... 66% 10.6M 1s
- 18800K .......... .......... .......... .......... .......... 67% 10.3M 1s
- 18850K .......... .......... .......... .......... .......... 67% 10.5M 1s
- 18900K .......... .......... .......... .......... .......... 67% 13.6M 1s
- 18950K .......... .......... .......... .......... .......... 67% 10.4M 1s
- 19000K .......... .......... .......... .......... .......... 67% 10.4M 1s
- 19050K .......... .......... .......... .......... .......... 68% 14.3M 1s
- 19100K .......... .......... .......... .......... .......... 68% 10.8M 1s
- 19150K .......... .......... .......... .......... .......... 68% 10.5M 1s
- 19200K .......... .......... .......... .......... .......... 68% 10.1M 1s
- 19250K .......... .......... .......... .......... .......... 68% 7.01M 1s
- 19300K .......... .......... .......... .......... .......... 68% 13.8M 1s
- 19350K .......... .......... .......... .......... .......... 69% 10.6M 1s
- 19400K .......... .......... .......... .......... .......... 69% 10.3M 1s
- 19450K .......... .......... .......... .......... .......... 69% 13.7M 1s
- 19500K .......... .......... .......... .......... .......... 69% 10.6M 1s
- 19550K .......... .......... .......... .......... .......... 69% 13.7M 1s
- 19600K .......... .......... .......... .......... .......... 69% 8.42M 1s
- 19650K .......... .......... .......... .......... .......... 70% 10.6M 1s
- 19700K .......... .......... .......... .......... .......... 70% 13.6M 1s
- 19750K .......... .......... .......... .......... .......... 70% 10.5M 1s
- 19800K .......... .......... .......... .......... .......... 70% 13.3M 1s
- 19850K .......... .......... .......... .......... .......... 70% 10.6M 1s
- 19900K .......... .......... .......... .......... .......... 71% 10.2M 1s
- 19950K .......... .......... .......... .......... .......... 71% 15.0M 1s
- 20000K .......... .......... .......... .......... .......... 71% 8.37M 1s
- 20050K .......... .......... .......... .......... .......... 71% 10.4M 1s
- 20100K .......... .......... .......... .......... .......... 71% 13.7M 1s
- 20150K .......... .......... .......... .......... .......... 71% 10.3M 1s
- 20200K .......... .......... .......... .......... .......... 72% 13.4M 1s
- 20250K .......... .......... .......... .......... .......... 72% 10.7M 1s
- 20300K .......... .......... .......... .......... .......... 72% 5.78M 1s
- 20350K .......... .......... .......... .......... .......... 72% 23.6M 1s
- 20400K .......... .......... .......... .......... .......... 72% 16.9M 1s
- 20450K .......... .......... .......... .......... .......... 72% 10.5M 1s
- 20500K .......... .......... .......... .......... .......... 73% 10.6M 1s
- 20550K .......... .......... .......... .......... .......... 73% 10.9M 1s
- 20600K .......... .......... .......... .......... .......... 73% 13.9M 1s
- 20650K .......... .......... .......... .......... .......... 73% 10.5M 1s
- 20700K .......... .......... .......... .......... .......... 73% 13.2M 1s
- 20750K .......... .......... .......... .......... .......... 74% 11.6M 1s
- 20800K .......... .......... .......... .......... .......... 74% 8.34M 1s
- 20850K .......... .......... .......... .......... .......... 74% 10.5M 1s
- 20900K .......... .......... .......... .......... .......... 74% 14.8M 1s
- 20950K .......... .......... .......... .......... .......... 74% 10.7M 1s
- 21000K .......... .......... .......... .......... .......... 74% 10.3M 1s
- 21050K .......... .......... .......... .......... .......... 75% 13.7M 1s
- 21100K .......... .......... .......... .......... .......... 75% 10.3M 1s
- 21150K .......... .......... .......... .......... .......... 75% 10.5M 1s
- 21200K .......... .......... .......... .......... .......... 75% 8.52M 1s
- 21250K .......... .......... .......... .......... .......... 75% 13.9M 1s
- 21300K .......... .......... .......... .......... .......... 76% 9.85M 1s
- 21350K .......... .......... .......... .......... .......... 76% 13.6M 1s
- 21400K .......... .......... .......... .......... .......... 76% 10.3M 1s
- 21450K .......... .......... .......... .......... .......... 76% 13.6M 1s
- 21500K .......... .......... .......... .......... .......... 76% 10.9M 1s
- 21550K .......... .......... .......... .......... .......... 76% 10.9M 1s
- 21600K .......... .......... .......... .......... .......... 77% 10.1M 1s
- 21650K .......... .......... .......... .......... .......... 77% 10.4M 1s
- 21700K .......... .......... .......... .......... .......... 77% 10.6M 1s
- 21750K .......... .......... .......... .......... .......... 77% 14.1M 1s
- 21800K .......... .......... .......... .......... .......... 77% 9.90M 1s
- 21850K .......... .......... .......... .......... .......... 77% 11.5M 1s
- 21900K .......... .......... .......... .......... .......... 78% 13.6M 1s
- 21950K .......... .......... .......... .......... .......... 78% 10.9M 1s
- 22000K .......... .......... .......... .......... .......... 78% 8.19M 1s
- 22050K .......... .......... .......... .......... .......... 78% 14.9M 1s
- 22100K .......... .......... .......... .......... .......... 78% 10.6M 1s
- 22150K .......... .......... .......... .......... .......... 79% 10.3M 1s
- 22200K .......... .......... .......... .......... .......... 79% 13.2M 1s
- 22250K .......... .......... .......... .......... .......... 79% 11.2M 1s
- 22300K .......... .......... .......... .......... .......... 79% 14.1M 1s
- 22350K .......... .......... .......... .......... .......... 79% 10.3M 1s
- 22400K .......... .......... .......... .......... .......... 79% 8.35M 1s
- 22450K .......... .......... .......... .......... .......... 80% 13.6M 1s
- 22500K .......... .......... .......... .......... .......... 80% 10.6M 1s
- 22550K .......... .......... .......... .......... .......... 80% 10.4M 1s
- 22600K .......... .......... .......... .......... .......... 80% 13.6M 1s
- 22650K .......... .......... .......... .......... .......... 80% 10.7M 1s
- 22700K .......... .......... .......... .......... .......... 81% 13.6M 1s
- 22750K .......... .......... .......... .......... .......... 81% 11.1M 1s
- 22800K .......... .......... .......... .......... .......... 81% 8.39M 1s
- 22850K .......... .......... .......... .......... .......... 81% 13.9M 1s
- 22900K .......... .......... .......... .......... .......... 81% 10.6M 1s
- 22950K .......... .......... .......... .......... .......... 81% 11.0M 1s
- 23000K .......... .......... .......... .......... .......... 82% 13.7M 1s
- 23050K .......... .......... .......... .......... .......... 82% 10.8M 1s
- 23100K .......... .......... .......... .......... .......... 82% 10.6M 1s
- 23150K .......... .......... .......... .......... .......... 82% 13.4M 1s
- 23200K .......... .......... .......... .......... .......... 82% 8.85M 1s
- 23250K .......... .......... .......... .......... .......... 82% 10.4M 1s
- 23300K .......... .......... .......... .......... .......... 83% 10.3M 0s
- 23350K .......... .......... .......... .......... .......... 83% 13.5M 0s
- 23400K .......... .......... .......... .......... .......... 83% 10.4M 0s
- 23450K .......... .......... .......... .......... .......... 83% 14.6M 0s
- 23500K .......... .......... .......... .......... .......... 83% 10.5M 0s
- 23550K .......... .......... .......... .......... .......... 84% 10.5M 0s
- 23600K .......... .......... .......... .......... .......... 84% 10.1M 0s
- 23650K .......... .......... .......... .......... .......... 84% 10.5M 0s
- 23700K .......... .......... .......... .......... .......... 84% 10.3M 0s
- 23750K .......... .......... .......... .......... .......... 84% 14.3M 0s
- 23800K .......... .......... .......... .......... .......... 84% 10.3M 0s
- 23850K .......... .......... .......... .......... .......... 85% 13.5M 0s
- 23900K .......... .......... .......... .......... .......... 85% 10.5M 0s
- 23950K .......... .......... .......... .......... .......... 85% 14.3M 0s
- 24000K .......... .......... .......... .......... .......... 85% 8.25M 0s
- 24050K .......... .......... .......... .......... .......... 85% 10.4M 0s
- 24100K .......... .......... .......... .......... .......... 85% 11.5M 0s
- 24150K .......... .......... .......... .......... .......... 86% 14.0M 0s
- 24200K .......... .......... .......... .......... .......... 86% 10.6M 0s
- 24250K .......... .......... .......... .......... .......... 86% 10.7M 0s
- 24300K .......... .......... .......... .......... .......... 86% 13.2M 0s
- 24350K .......... .......... .......... .......... .......... 86% 10.8M 0s
- 24400K .......... .......... .......... .......... .......... 87% 8.49M 0s
- 24450K .......... .......... .......... .......... .......... 87% 13.9M 0s
- 24500K .......... .......... .......... .......... .......... 87% 10.7M 0s
- 24550K .......... .......... .......... .......... .......... 87% 10.4M 0s
- 24600K .......... .......... .......... .......... .......... 87% 14.0M 0s
- 24650K .......... .......... .......... .......... .......... 87% 10.0M 0s
- 24700K .......... .......... .......... .......... .......... 88% 13.9M 0s
- 24750K .......... .......... .......... .......... .......... 88% 10.9M 0s
- 24800K .......... .......... .......... .......... .......... 88% 8.49M 0s
- 24850K .......... .......... .......... .......... .......... 88% 10.6M 0s
- 24900K .......... .......... .......... .......... .......... 88% 13.8M 0s
- 24950K .......... .......... .......... .......... .......... 89% 10.7M 0s
- 25000K .......... .......... .......... .......... .......... 89% 13.6M 0s
- 25050K .......... .......... .......... .......... .......... 89% 10.6M 0s
- 25100K .......... .......... .......... .......... .......... 89% 10.7M 0s
- 25150K .......... .......... .......... .......... .......... 89% 13.7M 0s
- 25200K .......... .......... .......... .......... .......... 89% 8.53M 0s
- 25250K .......... .......... .......... .......... .......... 90% 10.5M 0s
- 25300K .......... .......... .......... .......... .......... 90% 13.6M 0s
- 25350K .......... .......... .......... .......... .......... 90% 10.7M 0s
- 25400K .......... .......... .......... .......... .......... 90% 10.6M 0s
- 25450K .......... .......... .......... .......... .......... 90% 13.5M 0s
- 25500K .......... .......... .......... .......... .......... 90% 10.3M 0s
- 25550K .......... .......... .......... .......... .......... 91% 10.6M 0s
- 25600K .......... .......... .......... .......... .......... 91% 10.0M 0s
- 25650K .......... .......... .......... .......... .......... 91% 11.5M 0s
- 25700K .......... .......... .......... .......... .......... 91% 10.9M 0s
- 25750K .......... .......... .......... .......... .......... 91% 13.5M 0s
- 25800K .......... .......... .......... .......... .......... 92% 10.3M 0s
- 25850K .......... .......... .......... .......... .......... 92% 10.3M 0s
- 25900K .......... .......... .......... .......... .......... 92% 14.4M 0s
- 25950K .......... .......... .......... .......... .......... 92% 10.6M 0s
- 26000K .......... .......... .......... .......... .......... 92% 5.04M 0s
- 26050K .......... .......... .......... .......... .......... 92% 14.1M 0s
- 26100K .......... .......... .......... .......... .......... 93% 37.3M 0s
- 26150K .......... .......... .......... .......... .......... 93% 12.2M 0s
- 26200K .......... .......... .......... .......... .......... 93% 13.6M 0s
- 26250K .......... .......... .......... .......... .......... 93% 10.4M 0s
- 26300K .......... .......... .......... .......... .......... 93% 11.4M 0s
- 26350K .......... .......... .......... .......... .......... 94% 13.5M 0s
- 26400K .......... .......... .......... .......... .......... 94% 8.37M 0s
- 26450K .......... .......... .......... .......... .......... 94% 10.9M 0s
- 26500K .......... .......... .......... .......... .......... 94% 13.4M 0s
- 26550K .......... .......... .......... .......... .......... 94% 10.3M 0s
- 26600K .......... .......... .......... .......... .......... 94% 10.7M 0s
- 26650K .......... .......... .......... .......... .......... 95% 14.0M 0s
- 26700K .......... .......... .......... .......... .......... 95% 10.2M 0s
- 26750K .......... .......... .......... .......... .......... 95% 13.9M 0s
- 26800K .......... .......... .......... .......... .......... 95% 8.44M 0s
- 26850K .......... .......... .......... .......... .......... 95% 10.5M 0s
- 26900K .......... .......... .......... .......... .......... 95% 13.5M 0s
- 26950K .......... .......... .......... .......... .......... 96% 10.9M 0s
- 27000K .......... .......... .......... .......... .......... 96% 10.6M 0s
- 27050K .......... .......... .......... .......... .......... 96% 13.5M 0s
- 27100K .......... .......... .......... .......... .......... 96% 10.5M 0s
- 27150K .......... .......... .......... .......... .......... 96% 10.8M 0s
- 27200K .......... .......... .......... .......... .......... 97% 10.6M 0s
- 27250K .......... .......... .......... .......... .......... 97% 10.7M 0s
- 27300K .......... .......... .......... .......... .......... 97% 10.4M 0s
- 27350K .......... .......... .......... .......... .......... 97% 13.4M 0s
- 27400K .......... .......... .......... .......... .......... 97% 10.7M 0s
- 27450K .......... .......... .......... .......... .......... 97% 10.1M 0s
- 27500K .......... .......... .......... .......... .......... 98% 13.7M 0s
- 27550K .......... .......... .......... .......... .......... 98% 10.8M 0s
- 27600K .......... .......... .......... .......... .......... 98% 10.5M 0s
- 27650K .......... .......... .......... .......... .......... 98% 10.7M 0s
- 27700K .......... .......... .......... .......... .......... 98% 10.4M 0s
- 27750K .......... .......... .......... .......... .......... 98% 13.9M 0s
- 27800K .......... .......... .......... .......... .......... 99% 10.7M 0s
- 27850K .......... .......... .......... .......... .......... 99% 10.4M 0s
- 27900K .......... .......... .......... .......... .......... 99% 13.3M 0s
- 27950K .......... .......... .......... .......... .......... 99% 11.4M 0s
- 28000K .......... .......... .......... .......... .......... 99% 8.42M 0s
- 28050K .......... .......... .......... ..                   100% 18.9M=2.9s
-
-2014-01-16 20:02:58 (9.61 MB/s) - ‘/Users/kraft/annex/.git/annex/tmp/SHA256E-s28756861--4bea2d816a701dbfc88eada2288019c92c2774ee605e4ddfa62c4dd7655e53a1.dmg’ saved [28756861/28756861]
-
-[2014-01-16 20:02:58 CET] Upgrader: Downloaded git-annex.. upgrade)
-Checksumming Protective Master Boot Record (MBR : 0)…
-Protective Master Boot Record (MBR :: verified   CRC32 $BFC39E6D
-Checksumming GPT Header (Primary GPT Header : 1)…
- GPT Header (Primary GPT Header : 1): verified   CRC32 $1B4A1450
-Checksumming GPT Partition Data (Primary GPT Table : 2)…
-GPT Partition Data (Primary GPT Tabl: verified   CRC32 $78D54639
-Checksumming  (Apple_Free : 3)…
-                    (Apple_Free : 3): verified   CRC32 $00000000
-Checksumming disk image (Apple_HFS : 4)…
-          disk image (Apple_HFS : 4): verified   CRC32 $1E0144DA
-Checksumming  (Apple_Free : 5)…
-                    (Apple_Free : 5): verified   CRC32 $00000000
-Checksumming GPT Partition Data (Backup GPT Table : 6)…
-GPT Partition Data (Backup GPT Table: verified   CRC32 $78D54639
-Checksumming GPT Header (Backup GPT Header : 7)…
-  GPT Header (Backup GPT Header : 7): verified   CRC32 $61044DA0
-verified   CRC32 $E2335ED3
-/dev/disk4          	GUID_partition_scheme          	
-/dev/disk4s1        	Apple_HFS                      	/Users/kraft/git-annex.upgrade.0
-\"disk4\" unmounted.
-\"disk4\" ejected.
-git-annex version: 5.20140116-gd2fce02
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external
-local repository version: 5
-supported repository version: 5
-upgrade supported from repository versions: 0 1 2 4
-[2014-01-16 20:03:15 CET] Upgrader: Upgrading git-annex
-
-(Recording state in git...)
-(\"remove\",\"/Applications/git-annex.app/Contents/MacOS\")
-(\"remove\",\"/Applications/git-annex.app/Contents/MacOS/bundle\")
-(\"remove\",\"/Applications/git-annex.app/Contents/MacOS/bundle/A\")
-
-(Recording state in git...)
-[2014-01-16 20:03:15 CET] main: starting assistant version 5.20140116-gd2fce02
-[2014-01-16 20:03:15 CET] UpgradeWatcher: Finished upgrading git-annex to version 5.20140116-gd2fce02 
-(scanning...) [2014-01-16 20:03:15 CET] Watcher: Performing startup scan
-(started...) 
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_4_2705fbfd74652ab097ac48ec687517c7._comment b/doc/bugs/Auto_update_not_updating_to_newest_version/comment_4_2705fbfd74652ab097ac48ec687517c7._comment
deleted file mode 100644
index f0e326846..000000000
--- a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_4_2705fbfd74652ab097ac48ec687517c7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.43"
- subject="comment 4"
- date="2014-01-17T19:36:39Z"
- content="""
-Well that upgrade did seem to succeed. The log almost looks like 2 git-annex assistant processes were running (which should not happen), it seems to have downloaded the upgrade twice somehow.
-"""]]
diff --git a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_5_ab1ee005dbd54e560ea6e3c716cc8f1b._comment b/doc/bugs/Auto_update_not_updating_to_newest_version/comment_5_ab1ee005dbd54e560ea6e3c716cc8f1b._comment
deleted file mode 100644
index b05a0b1e2..000000000
--- a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_5_ab1ee005dbd54e560ea6e3c716cc8f1b._comment
+++ /dev/null
@@ -1,70 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk7iPiqWr3BVPLWEDvJhSSvcOqheLEbLNo"
- nickname="Dirk"
- subject="Still problems"
- date="2014-02-14T11:30:10Z"
- content="""
-There seem to be still problems here.
-
-I removed all my old configurations and repositories and reinstalled the newest version from the site. After starting I get a message about an update being available. I update and end up with the same version.
-
-[[!format sh \"\"\"
-[2014-02-14 12:22:10 CET] main: starting assistant version 5.20140209-g3a61dbe
-(scanning...) [2014-02-14 12:22:10 CET] Watcher: Performing startup scan
-(started...) [2014-02-14 12:22:10 CET] Upgrader: An upgrade of git-annex is available.  (version 5.20140210)
---2014-02-14 12:23:24--  https://downloads.kitenet.net/git-annex/OSX/current/10.9_Mavericks/git-annex.dmg
-Resolving downloads.kitenet.net... 80.68.85.49, 2001:41c8:125:49::10
-Connecting to downloads.kitenet.net|80.68.85.49|:443... connected.
-HTTP request sent, awaiting response... 200 OK
-Length: 29053083 (28M) [application/x-apple-diskimage]
-Saving to: ‘/Users/kraft/Desktop/annex/.git/annex/tmp/SHA256E-s29053083--ee629137b511da8b874cdac78ece54b344b2b2a1763e4bf806949c9868117b13.dmg’
-
-     0K .......... .......... .......... .......... ..........  0% 2.46M 11s
-    50K .......... .......... .......... .......... ..........  0% 1.69M 14s
-   100K .......... .......... .......... .......... ..........  0% 4.39M 11s
-   150K .......... .......... .......... .......... ..........  0% 2.28M 11s
-   200K .......... .......... .......... .......... ..........  0% 7.15M 10s
-   250K .......... .......... .......... .......... ..........  1% 2.30M 10s
-   300K .......... .......... .......... .......... ..........  1% 15.5M 9s
-
- 28300K .......... .......... .......... .......... .......... 99% 11.0M 0s
- 28350K .......... .......... ..                              100% 16.8M=2.8s
-
-2014-02-14 12:23:28 (9.96 MB/s) - ‘/Users/kraft/Desktop/annex/.git/annex/tmp/SHA256E-s29053083--ee629137b511da8b874cdac78ece54b344b2b2a1763e4bf806949c9868117b13.dmg’ saved [29053083/29053083]
-
-[2014-02-14 12:23:28 CET] main: Downloaded git-annex.. upgrade)
-Checksumming Protective Master Boot Record (MBR : 0)…
-Protective Master Boot Record (MBR :: verified   CRC32 $BFC39E6D
-Checksumming GPT Header (Primary GPT Header : 1)…
- GPT Header (Primary GPT Header : 1): verified   CRC32 $3488C834
-Checksumming GPT Partition Data (Primary GPT Table : 2)…
-GPT Partition Data (Primary GPT Tabl: verified   CRC32 $CABDFFA1
-Checksumming  (Apple_Free : 3)…
-                    (Apple_Free : 3): verified   CRC32 $00000000
-Checksumming disk image (Apple_HFS : 4)…
-          disk image (Apple_HFS : 4): verified   CRC32 $0CFF6F1A
-Checksumming  (Apple_Free : 5)…
-                    (Apple_Free : 5): verified   CRC32 $00000000
-Checksumming GPT Partition Data (Backup GPT Table : 6)…
-GPT Partition Data (Backup GPT Table: verified   CRC32 $CABDFFA1
-Checksumming GPT Header (Backup GPT Header : 7)…
-  GPT Header (Backup GPT Header : 7): verified   CRC32 $4EC691C4
-verified   CRC32 $A78EB9FA
-/dev/disk4          	GUID_partition_scheme          	
-/dev/disk4s1        	Apple_HFS                      	/Applications/git-annex.upgrade.0
-\"disk4\" unmounted.
-\"disk4\" ejected.
-git-annex version: 5.20140209-g3a61dbe
-build flags: Assistant Webapp Pairing S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external
-local repository version: 5
-supported repository version: 5
-upgrade supported from repository versions: 0 1 2 4
-[2014-02-14 12:23:45 CET] main: Upgrading git-annex
-[2014-02-14 12:23:45 CET] main: starting assistant version 5.20140209-g3a61dbe
-[2014-02-14 12:23:45 CET] UpgradeWatcher: Finished upgrading git-annex to version 5.20140209-g3a61dbe 
-(scanning...) [2014-02-14 12:23:45 CET] Watcher: Performing startup scan
-(started...)
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_6_8019fa061d74365ea72e32780d288eb4._comment b/doc/bugs/Auto_update_not_updating_to_newest_version/comment_6_8019fa061d74365ea72e32780d288eb4._comment
deleted file mode 100644
index 0c38bd651..000000000
--- a/doc/bugs/Auto_update_not_updating_to_newest_version/comment_6_8019fa061d74365ea72e32780d288eb4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="216.145.95.162"
- subject="comment 6"
- date="2014-05-19T17:06:30Z"
- content="""
-See [[git-annex_auto_upgrade_is_redundant]] for analysis of this problem.
-"""]]
diff --git a/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed.mdwn b/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed.mdwn
deleted file mode 100644
index 1f190c47e..000000000
--- a/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-All builds of git-annex should be cryptographically signed.  Especially the automatic upgrades.
-
-Signing doesn't minimise the likelihood of unwanted software being installed, but it helps reduce it.
-
-*Please* Joey...
-
-> builds have been signed for a while now. auto-upgrader checks the sigs
-> too! [[done]] --[[Joey]] 
diff --git a/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment b/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment
deleted file mode 100644
index 8deae448c..000000000
--- a/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 1"
- date="2013-12-11T06:20:57Z"
- content="""
-The links to the builds use https. The automatic upgrades use https (and wget or curl, which will reject an invalid SSL certificate).
-
-So, it is cryptographically signed. Of course SSL certificates are only as secure as the CAs. But using a gpg key that most users have no particular reason to trust would not add a lot of security.
-"""]]
diff --git a/doc/bugs/Backup_repository_doesn__39__t_get_all_files.mdwn b/doc/bugs/Backup_repository_doesn__39__t_get_all_files.mdwn
deleted file mode 100644
index 62a0524ee..000000000
--- a/doc/bugs/Backup_repository_doesn__39__t_get_all_files.mdwn
+++ /dev/null
@@ -1,40 +0,0 @@
-[[!meta title="assistant should try sending old/deleted versions of files to backup repositories"]]
-
-### Please describe the problem.
-Backup group repositories don't download all "unused" files when running the webapp.
-
-
-### What steps will reproduce the problem?
-Run the webapp, set up two local repositories:
-
-1 - Use this for testing, set to manual type
-
-2 - Use for backups, set to full backup type
-
-Create some files, change them, etc.  See that files and history get transferred from #1 --> #2
-
-Change #2 to being "don't sync".  For example, you are running out of disk space, or are off the network.
-
-Edit a file in #1 a couple of times.  Now change #2 to synchronise.
-
-Now, #2 will reflect #1 in the current state.
-
-Stop the annex assistant.
-
-Change #2 to being indirect mode.  Try to checkout a previous revision. There will be broken symlinks.  git annex get will fail with "no copies of this file" type errors.
-
-
-My expectation (incorrectly?) was that all the "history" of my files would be automatically transferred to the backup group repos.  It seems only the git commits are transferred, but the "unused" file content isn't.
-
---- 
-
-What this tells me is that any changes that occur whilst I am not networked are entirely localised to my machine.  If this is the design expectation, can we squash commits before sending them?  There seems to be no point in having commits pointing to file content that has no chance of being accessed.
-
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 5.20131130-gc25be33
-
-
-> This was fixed in 5.20140127; the assistant now does a daily sweep of
-> unused files to move them to backup repositories when possible. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/Backup_repository_doesn__39__t_get_all_files/comment_1_a486dc0f741e08d5bcf2fd1a6ecbdf05._comment b/doc/bugs/Backup_repository_doesn__39__t_get_all_files/comment_1_a486dc0f741e08d5bcf2fd1a6ecbdf05._comment
deleted file mode 100644
index 54c579509..000000000
--- a/doc/bugs/Backup_repository_doesn__39__t_get_all_files/comment_1_a486dc0f741e08d5bcf2fd1a6ecbdf05._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 1"
- date="2013-12-12T17:20:27Z"
- content="""
-The assistant currently only considers transferring files to other remotes that are currently in the tree, not old versions of files, or files no longer in the tree. You can send everything, manually, by running `git annex copy --all --to backupremote`
-
-When you're using direct mode, git-annex does not try ensure that every historical version of a file is preserved. Because in direct mode there is only one copy of a file, and you can edit or delete it at any time. If preserving every version is important to you, don't use direct mode; indirect mode will handle this nicely. (Of course you can still force it to remove files in indirect mode.)
-
-I think it would make sense for the assistant to sometimes try to send everything to some remotes. The tricky part is probably working out which remotes it makes sense to send that to. Currenty, [[preferred_content]] expressions only indicate whether files currently in the tree are wanted. They would need to be expanded somehow, so that full backup repositories could indicate they also want every available past version of a file.
-"""]]
diff --git a/doc/bugs/Browser_fails_to_launch_on_Android___39__git_annex_webapp__39__.mdwn b/doc/bugs/Browser_fails_to_launch_on_Android___39__git_annex_webapp__39__.mdwn
deleted file mode 100644
index 8178e6dbc..000000000
--- a/doc/bugs/Browser_fails_to_launch_on_Android___39__git_annex_webapp__39__.mdwn
+++ /dev/null
@@ -1,35 +0,0 @@
-### Please describe the problem.
-
-When I launch git annex Android application, it fails to open the web browser. Workaround is to copy the url and manually paste it into web browser url line.
-
-### What steps will reproduce the problem?
-
-See above
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version 4.20130513-g5185533 on Android 4.2.2
-
-### Please provide any additional information below.
-
-[[!format sh """
-u0_a126@android:/sdcard/git-annex.home $ git annex webapp
-Launching web browser on http://127.0.0.1:47557/?auth=[...snip...]
-Starting: Intent { act=android.intent.action.VIEW dat=http://127.0.0.1:47557/?auth=[...snip...] }
-java.lang.SecurityException: Permission Denial: startActivity asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
-        at android.os.Parcel.readException(Parcel.java:1425)
-        at android.os.Parcel.readException(Parcel.java:1379)
-        at android.app.ActivityManagerProxy.startActivityAsUser(ActivityManagerNative.java:1921)
-        at com.android.commands.am.Am.runStart(Am.java:494)
-        at com.android.commands.am.Am.run(Am.java:109)
-        at com.android.commands.am.Am.main(Am.java:82)
-        at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
-        at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
-        at dalvik.system.NativeStart.main(Native Method)
-failed to start web browser
-u0_a126@android:/sdcard/git-annex.home $
-
-# End of transcript or log.
-"""]]
-
-[[done]], duplicate bug
diff --git a/doc/bugs/Browser_fails_to_launch_on_Android___39__git_annex_webapp__39__/comment_1_173393b0b3d2d8c622c0d8a2eaace421._comment b/doc/bugs/Browser_fails_to_launch_on_Android___39__git_annex_webapp__39__/comment_1_173393b0b3d2d8c622c0d8a2eaace421._comment
deleted file mode 100644
index 6104e6e75..000000000
--- a/doc/bugs/Browser_fails_to_launch_on_Android___39__git_annex_webapp__39__/comment_1_173393b0b3d2d8c622c0d8a2eaace421._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmmLfBDEDFfEOba8Ra46nsnTmoNHFsLObo"
- nickname="Brian"
- subject="Duplicate bug report"
- date="2013-05-15T02:35:34Z"
- content="""
-This report is a duplicate of [[Android app permission denial on startup]]
-"""]]
diff --git a/doc/bugs/Build-depends_needs___39__hxt__39___added_-_3.20121127.mdwn b/doc/bugs/Build-depends_needs___39__hxt__39___added_-_3.20121127.mdwn
deleted file mode 100644
index 83720cca2..000000000
--- a/doc/bugs/Build-depends_needs___39__hxt__39___added_-_3.20121127.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-What steps will reproduce the problem?
-
-Install git-annex via cabal - either from Hackage or as a manual install.  (i.e. <http://git-annex.branchable.com/install/cabal/>)
-
-What is the expected output? What do you see instead?
-
-Expect a clean install.
-
-However, get the following error:
-
-    Assistant/Install.hs:24:8:
-        Could not find module `Data.AssocList'
-        It is a member of the hidden package `hxt-9.3.1.1'.
-        Perhaps you need to add `hxt' to the build-depends in your .cabal file.
-        Use -v to see a list of the files searched for.
-
-
-What version of git-annex are you using? On what operating system?
-
-git-annex: 3.20121127
-OS: Mac OSX 10.6.8
-
-Please provide any additional information below.
-
-The fix seems to be as simple as adding 'htx' to the 'git-annex.cabal' file:
-
-    Executable git-annex
-      Main-Is: git-annex.hs
-      Build-Depends: MissingH, hslogger, directory, filepath,
-       unix, containers, utf8-string, network (>= 2.0), mtl (>= 2.1.1),
-       bytestring, old-locale, time,
-       -- Added htx here
-       hxt,
-       pcre-light, extensible-exceptions, dataenc, SHA, process, json, HTTP,
-
-> I removed the need for hxt, which was accidental. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Build_error:_Ambiguous_occurrence___96__callCommand__39__.mdwn b/doc/bugs/Build_error:_Ambiguous_occurrence___96__callCommand__39__.mdwn
deleted file mode 100644
index e7a849021..000000000
--- a/doc/bugs/Build_error:_Ambiguous_occurrence___96__callCommand__39__.mdwn
+++ /dev/null
@@ -1,74 +0,0 @@
-### Please describe the problem.
-
-I get the following error when building:
-
-[[!format sh """
-$ cabal install git-annex --bindir=$HOME/bin -f"-assistant -webapp -webdav -pairing -xmpp -dns"
-
-...
-
-Configuring git-annex-5.20140127...
-Building git-annex-5.20140127...
-Preprocessing executable 'git-annex' for git-annex-5.20140127...
-[  1 of 281] Compiling Utility.Dot      ( Utility/Dot.hs, dist/build/git-annex/git-annex-tmp/Utility/Dot.o )
-[  2 of 281] Compiling BuildFlags       ( BuildFlags.hs, dist/build/git-annex/git-annex-tmp/BuildFlags.o )
-[  3 of 281] Compiling Utility.Shell    ( Utility/Shell.hs, dist/build/git-annex/git-annex-tmp/Utility/Shell.o )
-
-...
-
-[111 of 281] Compiling Backend.Hash     ( Backend/Hash.hs, dist/build/git-annex/git-annex-tmp/Backend/Hash.o )
-[112 of 281] Compiling Annex.Queue      ( Annex/Queue.hs, dist/build/git-annex/git-annex-tmp/Annex/Queue.o )
-[113 of 281] Compiling RunCommand       ( RunCommand.hs, dist/build/git-annex/git-annex-tmp/RunCommand.o )
-
-RunCommand.hs:44:17:
-    Ambiguous occurrence `callCommand'
-    It could refer to either `RunCommand.callCommand',
-                             defined at RunCommand.hs:62:1
-                          or `Common.Annex.callCommand',
-                             imported from `Common.Annex' at RunCommand.hs:12:1-19
-                             (and originally defined in `System.Process')
-cabal: Error: some packages failed to install:
-git-annex-5.20140127 failed during the building phase. The exception was:
-ExitFailure 1
-"""]]
-
-### What steps will reproduce the problem?
-
-Try building the same version.
-
-### What version of git-annex are you using? On what operating system?
-
-Building git-annex-5.20140127...
-
-[[!format sh """
-$ cabal --version
-cabal-install version 0.14.0
-using version 1.14.0 of the Cabal library
-
-$ ghc --version
-The Glorious Glasgow Haskell Compilation System, version 7.4.1
-
-$ lsb_release -a 
-No LSB modules are available.
-Distributor ID:	Ubuntu
-Description:	Ubuntu 12.04.3 LTS
-Release:	12.04
-Codename:	precise
-
-$ uname -a
-Linux sahnlpt0116 3.2.0-58-generic #88-Ubuntu SMP Tue Dec 3 17:37:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
-"""]]
-
-### Please provide any additional information below.
-
-Sorry but I don't know what else could help you.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> fixed in git and will update cabal soon [[done]] --[[Joey]]
diff --git a/doc/bugs/Build_error:_Ambiguous_occurrence___96__callCommand__39__/comment_1_3127b3c448888fdf70096f24c7cbfd3c._comment b/doc/bugs/Build_error:_Ambiguous_occurrence___96__callCommand__39__/comment_1_3127b3c448888fdf70096f24c7cbfd3c._comment
deleted file mode 100644
index ad28f9cce..000000000
--- a/doc/bugs/Build_error:_Ambiguous_occurrence___96__callCommand__39__/comment_1_3127b3c448888fdf70096f24c7cbfd3c._comment
+++ /dev/null
@@ -1,50 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnzFs0ZJvkUvEVI_OAp0aAP1CTOw2UUXl4"
- nickname="Christian"
- subject="A patch to fix the problem"
- date="2014-01-29T17:26:58Z"
- content="""
-The following patch lets me compile everything, but I am not sure it is right:
-
-[[!format sh \"\"\"
-diff --git a/Command/PreCommit.hs b/Command/PreCommit.hs
-index 6644f6f..f3ad454 100644
---- a/Command/PreCommit.hs
-+++ b/Command/PreCommit.hs
-@@ -7,7 +7,7 @@
- 
- module Command.PreCommit where
- 
--import Common.Annex
-+import Common.Annex hiding (callCommand)
- import Command
- import Config
- import qualified Command.Add
-diff --git a/Command/Sync.hs b/Command/Sync.hs
-index 6ef111b..fde4a9a 100644
---- a/Command/Sync.hs
-+++ b/Command/Sync.hs
-@@ -8,7 +8,7 @@
- 
- module Command.Sync where
- 
--import Common.Annex
-+import Common.Annex hiding (callCommand)
- import Command
- import qualified Annex
- import qualified Annex.Branch
-diff --git a/RunCommand.hs b/RunCommand.hs
-index 937686d..d76b457 100644
---- a/RunCommand.hs
-+++ b/RunCommand.hs
-@@ -9,7 +9,7 @@
- 
- module RunCommand where
- 
--import Common.Annex
-+import Common.Annex hiding (callCommand)
- import qualified Annex
- import Types.Command
- import qualified Annex.Queue
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/Build_error_on_Linux.mdwn b/doc/bugs/Build_error_on_Linux.mdwn
deleted file mode 100644
index af560788a..000000000
--- a/doc/bugs/Build_error_on_Linux.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-### Please describe the problem.
-Building on Linux, with a particular combination of flags, failed due to missing `async`.
-
-### What steps will reproduce the problem?
-1. Configure with the following flag combination
-
-        cryptohash -quvi -feed tdfa -testsuite -android production -dns -xmpp -pairing -webapp -assistant dbus inotify -webdav s3
-
-2. Attempt to build and you'll get an error on line 16 of `Utility/Batch.hs` because `Control.Concurrent.Async` isn't available.
-
-### What version of git-annex are you using? On what operating system?
-Version 4.20131024 on Linux
-
-### Please provide any additional information below.
-
-This is the patch I applied to `git-annex.cabal`:
-
-                 CPP-Options: -DWITH_KQUEUE
-                 C-Sources: Utility/libkqueue.c
-     
-    +  if os(linux)
-    +    Build-Depends: async
-    +
-       if os(linux) && flag(Dbus)
-         Build-Depends: dbus (>= 0.10.3)
-         CPP-Options: -DWITH_DBUS
-
-> Feel async is core enough it should depend on it unconditionally.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Build_error_on_Mac_OSX_10.6.mdwn b/doc/bugs/Build_error_on_Mac_OSX_10.6.mdwn
deleted file mode 100644
index 43fb0323c..000000000
--- a/doc/bugs/Build_error_on_Mac_OSX_10.6.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-While following the instructions given at the OSX build page , I get this error:
-
-$ make
-ghc -O2 -Wall -ignore-package monads-fd -fspec-constr-count=5 --make git-annex
-
-Utility/JSONStream.hs:14:8:
-    Could not find module `Text.JSON':
-      Use -v to see a list of the files searched for.
-make: *** [git-annex] Error 1
-
-> Updated the instructions. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Building_fails:_Could_not_find_module___96__Text.Blaze__39__.mdwn b/doc/bugs/Building_fails:_Could_not_find_module___96__Text.Blaze__39__.mdwn
deleted file mode 100644
index b75d92e18..000000000
--- a/doc/bugs/Building_fails:_Could_not_find_module___96__Text.Blaze__39__.mdwn
+++ /dev/null
@@ -1,105 +0,0 @@
-What steps will reproduce the problem?
-
-<pre>
-dominik@Atlantis:/var/tmp$ git clone git://github.com/joeyh/git-annex.git
-Cloning into 'git-annex'...
-remote: Counting objects: 40580, done.
-remote: Compressing objects: 100% (10514/10514), done.
-remote: Total 40580 (delta 29914), reused 40502 (delta 29837)
-Receiving objects: 100% (40580/40580), 9.17 MiB | 238 KiB/s, done.
-Resolving deltas: 100% (29914/29914), done.
-dominik@Atlantis:/var/tmp$ cd git-annex/
-dominik@Atlantis:/var/tmp/git-annex$ cabal update
-Downloading the latest package list from hackage.haskell.org
-dominik@Atlantis:/var/tmp/git-annex$ cabal install --only-dependencies
-Resolving dependencies...
-All the requested packages are already installed:
-Use --reinstall if you want to reinstall anyway.
-dominik@Atlantis:/var/tmp/git-annex$ cabal configure
-Resolving dependencies...
-[ 1 of 21] Compiling Utility.FileSystemEncoding ( Utility/FileSystemEncoding.hs, dist/setup/Utility/FileSystemEncoding.o )
-[ 2 of 21] Compiling Utility.Applicative ( Utility/Applicative.hs, dist/setup/Utility/Applicative.o )
-[ 3 of 21] Compiling Utility.PartialPrelude ( Utility/PartialPrelude.hs, dist/setup/Utility/PartialPrelude.o )
-[ 4 of 21] Compiling Utility.UserInfo ( Utility/UserInfo.hs, dist/setup/Utility/UserInfo.o )
-[ 5 of 21] Compiling Utility.Monad    ( Utility/Monad.hs, dist/setup/Utility/Monad.o )
-[ 6 of 21] Compiling Utility.Path     ( Utility/Path.hs, dist/setup/Utility/Path.o )
-[ 7 of 21] Compiling Utility.OSX      ( Utility/OSX.hs, dist/setup/Utility/OSX.o )
-[ 8 of 21] Compiling Utility.Exception ( Utility/Exception.hs, dist/setup/Utility/Exception.o )
-[ 9 of 21] Compiling Utility.TempFile ( Utility/TempFile.hs, dist/setup/Utility/TempFile.o )
-[10 of 21] Compiling Utility.Misc     ( Utility/Misc.hs, dist/setup/Utility/Misc.o )
-[11 of 21] Compiling Utility.Process  ( Utility/Process.hs, dist/setup/Utility/Process.o )
-[12 of 21] Compiling Utility.FreeDesktop ( Utility/FreeDesktop.hs, dist/setup/Utility/FreeDesktop.o )
-[13 of 21] Compiling Assistant.Install.AutoStart ( Assistant/Install/AutoStart.hs, dist/setup/Assistant/Install/AutoStart.o )
-[14 of 21] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, dist/setup/Utility/SafeCommand.o )
-[15 of 21] Compiling Utility.Directory ( Utility/Directory.hs, dist/setup/Utility/Directory.o )
-[16 of 21] Compiling Common           ( Common.hs, dist/setup/Common.o )
-[17 of 21] Compiling Locations.UserConfig ( Locations/UserConfig.hs, dist/setup/Locations/UserConfig.o )
-[18 of 21] Compiling Build.TestConfig ( Build/TestConfig.hs, dist/setup/Build/TestConfig.o )
-[19 of 21] Compiling Build.Configure  ( Build/Configure.hs, dist/setup/Build/Configure.o )
-[20 of 21] Compiling Build.InstallDesktopFile ( Build/InstallDesktopFile.hs, dist/setup/Build/InstallDesktopFile.o )
-[21 of 21] Compiling Main             ( Setup.hs, dist/setup/Main.o )
-Linking ./dist/setup/setup ...
-  checking version... 3.20121018
-  checking git... yes
-  checking git version... 1.7.10.4
-  checking cp -a... yes
-  checking cp -p... yes
-  checking cp --reflink=auto... yes
-  checking uuid generator... uuidgen
-  checking xargs -0... yes
-  checking rsync... yes
-  checking curl... yes
-  checking wget... yes
-  checking bup... no
-  checking gpg... yes
-  checking lsof... yes
-  checking host... no
-  checking ssh connection caching... yes
-  checking sha1... sha1sum
-  checking sha256... sha256sum
-  checking sha512... sha512sum
-  checking sha224... sha224sum
-  checking sha384... sha384sum
-Configuring git-annex-3.20121018...
-dominik@Atlantis:/var/tmp/git-annex$ cabal build
-Building git-annex-3.20121018...
-Preprocessing executable 'git-annex' for git-annex-3.20121018...
-
-Assistant/Alert.hs:21:8:
-    Could not find module `Text.Blaze'
-    It is a member of the hidden package `blaze-markup-0.5.1.1'.
-    Perhaps you need to add `blaze-markup' to the build-depends in your .cabal file.
-    Use -v to see a list of the files searched for.
-</pre>
-
-What is the expected output? What do you see instead?
-
-I expect the latest git HEAD to build without an error message or provide me with a package I need to install. Instead the error above is shown. In fact the package requested is installed:
-
-<pre>
-dominik@Atlantis:/var/tmp/git-annex$ cabal install blaze-markup
-Resolving dependencies...
-All the requested packages are already installed:
-blaze-markup-0.5.1.1
-Use --reinstall if you want to reinstall anyway.
-</pre>
-
-What version of git-annex are you using? On what operating system?
-
-git HEAD, Ubuntu 12.10
-
-Please provide any additional information below.
-
-<pre>
-$ cabal --version
-cabal-install version 0.14.0
-using version 1.14.0 of the Cabal library 
-
-$ ghc --version
-The Glorious Glasgow Haskell Compilation System, version 7.4.2
-
-$ uname -a
-Linux Atlantis 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
-</pre>
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Building_fails:__Could_not_find_module___96__Data.XML.Types__39__.mdwn b/doc/bugs/Building_fails:__Could_not_find_module___96__Data.XML.Types__39__.mdwn
deleted file mode 100644
index c03353436..000000000
--- a/doc/bugs/Building_fails:__Could_not_find_module___96__Data.XML.Types__39__.mdwn
+++ /dev/null
@@ -1,82 +0,0 @@
-What steps will reproduce the problem?
-
-<pre>
-dominik@Atlantis:/var/tmp$ git clone git://github.com/joeyh/git-annex.git
-Cloning into 'git-annex'...
-remote: Counting objects: 40841, done.
-remote: Compressing objects: 100% (10648/10648), done.
-remote: Total 40841 (delta 30135), reused 40669 (delta 29964)
-Receiving objects: 100% (40841/40841), 9.21 MiB | 517 KiB/s, done.
-Resolving deltas: 100% (30135/30135), done.
-dominik@Atlantis:/var/tmp/git-annex$ cabal install --only-dependencies
-Resolving dependencies...
-All the requested packages are already installed:
-Use --reinstall if you want to reinstall anyway.
-dominik@Atlantis:/var/tmp/git-annex$ cabal configure
-Resolving dependencies...
-[ 1 of 21] Compiling Utility.FileSystemEncoding ( Utility/FileSystemEncoding.hs, dist/setup/Utility/FileSystemEncoding.o )
-[ 2 of 21] Compiling Utility.Applicative ( Utility/Applicative.hs, dist/setup/Utility/Applicative.o )
-[ 3 of 21] Compiling Utility.PartialPrelude ( Utility/PartialPrelude.hs, dist/setup/Utility/PartialPrelude.o )
-[ 4 of 21] Compiling Utility.UserInfo ( Utility/UserInfo.hs, dist/setup/Utility/UserInfo.o )
-[ 5 of 21] Compiling Utility.Monad    ( Utility/Monad.hs, dist/setup/Utility/Monad.o )
-[ 6 of 21] Compiling Utility.Path     ( Utility/Path.hs, dist/setup/Utility/Path.o )
-[ 7 of 21] Compiling Utility.OSX      ( Utility/OSX.hs, dist/setup/Utility/OSX.o )
-[ 8 of 21] Compiling Utility.Exception ( Utility/Exception.hs, dist/setup/Utility/Exception.o )
-[ 9 of 21] Compiling Utility.TempFile ( Utility/TempFile.hs, dist/setup/Utility/TempFile.o )
-[10 of 21] Compiling Utility.Misc     ( Utility/Misc.hs, dist/setup/Utility/Misc.o )
-[11 of 21] Compiling Utility.Process  ( Utility/Process.hs, dist/setup/Utility/Process.o )
-[12 of 21] Compiling Utility.FreeDesktop ( Utility/FreeDesktop.hs, dist/setup/Utility/FreeDesktop.o )
-[13 of 21] Compiling Assistant.Install.AutoStart ( Assistant/Install/AutoStart.hs, dist/setup/Assistant/Install/AutoStart.o )
-[14 of 21] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, dist/setup/Utility/SafeCommand.o )
-[15 of 21] Compiling Utility.Directory ( Utility/Directory.hs, dist/setup/Utility/Directory.o )
-[16 of 21] Compiling Common           ( Common.hs, dist/setup/Common.o )
-[17 of 21] Compiling Locations.UserConfig ( Locations/UserConfig.hs, dist/setup/Locations/UserConfig.o )
-[18 of 21] Compiling Build.TestConfig ( Build/TestConfig.hs, dist/setup/Build/TestConfig.o )
-[19 of 21] Compiling Build.Configure  ( Build/Configure.hs, dist/setup/Build/Configure.o )
-[20 of 21] Compiling Build.InstallDesktopFile ( Build/InstallDesktopFile.hs, dist/setup/Build/InstallDesktopFile.o )
-[21 of 21] Compiling Main             ( Setup.hs, dist/setup/Main.o )
-Linking ./dist/setup/setup ...
-  checking version... 3.20121018
-  checking git... yes
-  checking git version... 1.7.10.4
-  checking cp -a... yes
-  checking cp -p... yes
-  checking cp --reflink=auto... yes
-  checking uuid generator... uuidgen
-  checking xargs -0... yes
-  checking rsync... yes
-  checking curl... yes
-  checking wget... yes
-  checking bup... no
-  checking gpg... yes
-  checking lsof... yes
-  checking ssh connection caching... yes
-  checking sha1... sha1sum
-  checking sha256... sha256sum
-  checking sha512... sha512sum
-  checking sha224... sha224sum
-  checking sha384... sha384sum
-Configuring git-annex-3.20121018...
-dominik@Atlantis:/var/tmp/git-annex$ cabal build
-Building git-annex-3.20121018...
-Preprocessing executable 'git-annex' for git-annex-3.20121018...
-
-Assistant/XMPP.hs:18:8:
-    Could not find module `Data.XML.Types'
-    It is a member of the hidden package `xml-types-0.3.3'.
-    Perhaps you need to add `xml-types' to the build-depends in your .cabal file.
-    Use -v to see a list of the files searched for.
-</pre>
-
-What is the expected output? What do you see instead?
-
-I exepect the current git HEAD to build without errors.
-
-What version of git-annex are you using? On what operating system?
-
-git-annex HEAD from git, Ubuntu 12.10
-
-Please provide any additional information below.
-
-> [[done]] --[[Joey]] (and tested the whole cabal build, which I usually
-> only do on releases)
diff --git a/doc/bugs/Building_fails:___Not_in_scope:_type_constructor_or_class___96__Html__39__.mdwn b/doc/bugs/Building_fails:___Not_in_scope:_type_constructor_or_class___96__Html__39__.mdwn
deleted file mode 100644
index 6459e3f2e..000000000
--- a/doc/bugs/Building_fails:___Not_in_scope:_type_constructor_or_class___96__Html__39__.mdwn
+++ /dev/null
@@ -1,189 +0,0 @@
-What steps will reproduce the problem?
-
-<pre>
-dominik@Atlantis:/var/tmp/git-annex$ cabal build
-Building git-annex-3.20121018...
-Preprocessing executable 'git-annex' for git-annex-3.20121018...
-
-Assistant/Threads/NetWatcher.hs:26:2:
-     warning: #warning Building without dbus support; will poll for network connection changes [-Wcpp]
-
-Assistant/Threads/MountWatcher.hs:33:2:
-     warning: #warning Building without dbus support; will use mtab polling [-Wcpp]
-[  1 of 270] Compiling Utility.Dot      ( Utility/Dot.hs, dist/build/git-annex/git-annex-tmp/Utility/Dot.o )
-[  2 of 270] Compiling Utility.ThreadLock ( Utility/ThreadLock.hs, dist/build/git-annex/git-annex-tmp/Utility/ThreadLock.o )
-[  3 of 270] Compiling Utility.Mounts   ( dist/build/git-annex/git-annex-tmp/Utility/Mounts.hs, dist/build/git-annex/git-annex-tmp/Utility/Mounts.o )
-[  4 of 270] Compiling Utility.Yesod    ( Utility/Yesod.hs, dist/build/git-annex/git-annex-tmp/Utility/Yesod.o )
-[  5 of 270] Compiling Utility.Tense    ( Utility/Tense.hs, dist/build/git-annex/git-annex-tmp/Utility/Tense.o )
-[  6 of 270] Compiling Utility.Verifiable ( Utility/Verifiable.hs, dist/build/git-annex/git-annex-tmp/Utility/Verifiable.o )
-[  7 of 270] Compiling Assistant.Types.TransferSlots ( Assistant/Types/TransferSlots.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/TransferSlots.o )
-[  8 of 270] Compiling Types.StandardGroups ( Types/StandardGroups.hs, dist/build/git-annex/git-annex-tmp/Types/StandardGroups.o )
-[  9 of 270] Compiling Utility.Percentage ( Utility/Percentage.hs, dist/build/git-annex/git-annex-tmp/Utility/Percentage.o )
-[ 10 of 270] Compiling Utility.Base64   ( Utility/Base64.hs, dist/build/git-annex/git-annex-tmp/Utility/Base64.o )
-[ 11 of 270] Compiling Utility.DataUnits ( Utility/DataUnits.hs, dist/build/git-annex/git-annex-tmp/Utility/DataUnits.o )
-[ 12 of 270] Compiling Utility.JSONStream ( Utility/JSONStream.hs, dist/build/git-annex/git-annex-tmp/Utility/JSONStream.o )
-[ 13 of 270] Compiling Messages.JSON    ( Messages/JSON.hs, dist/build/git-annex/git-annex-tmp/Messages/JSON.o )
-[ 14 of 270] Compiling Build.SysConfig  ( Build/SysConfig.hs, dist/build/git-annex/git-annex-tmp/Build/SysConfig.o )
-[ 15 of 270] Compiling Types.KeySource  ( Types/KeySource.hs, dist/build/git-annex/git-annex-tmp/Types/KeySource.o )
-[ 16 of 270] Compiling Utility.State    ( Utility/State.hs, dist/build/git-annex/git-annex-tmp/Utility/State.o )
-[ 17 of 270] Compiling Types.UUID       ( Types/UUID.hs, dist/build/git-annex/git-annex-tmp/Types/UUID.o )
-[ 18 of 270] Compiling Types.Messages   ( Types/Messages.hs, dist/build/git-annex/git-annex-tmp/Types/Messages.o )
-[ 19 of 270] Compiling Types.Group      ( Types/Group.hs, dist/build/git-annex/git-annex-tmp/Types/Group.o )
-[ 20 of 270] Compiling Types.TrustLevel ( Types/TrustLevel.hs, dist/build/git-annex/git-annex-tmp/Types/TrustLevel.o )
-[ 21 of 270] Compiling Types.BranchState ( Types/BranchState.hs, dist/build/git-annex/git-annex-tmp/Types/BranchState.o )
-[ 22 of 270] Compiling Utility.UserInfo ( Utility/UserInfo.hs, dist/build/git-annex/git-annex-tmp/Utility/UserInfo.o )
-[ 23 of 270] Compiling Utility.PartialPrelude ( Utility/PartialPrelude.hs, dist/build/git-annex/git-annex-tmp/Utility/PartialPrelude.o )
-[ 24 of 270] Compiling Utility.HumanTime ( Utility/HumanTime.hs, dist/build/git-annex/git-annex-tmp/Utility/HumanTime.o )
-[ 25 of 270] Compiling Utility.Format   ( Utility/Format.hs, dist/build/git-annex/git-annex-tmp/Utility/Format.o )
-[ 26 of 270] Compiling Utility.FileSystemEncoding ( Utility/FileSystemEncoding.hs, dist/build/git-annex/git-annex-tmp/Utility/FileSystemEncoding.o )
-[ 27 of 270] Compiling Utility.Touch    ( dist/build/git-annex/git-annex-tmp/Utility/Touch.hs, dist/build/git-annex/git-annex-tmp/Utility/Touch.o )
-[ 28 of 270] Compiling Utility.Applicative ( Utility/Applicative.hs, dist/build/git-annex/git-annex-tmp/Utility/Applicative.o )
-[ 29 of 270] Compiling Utility.Monad    ( Utility/Monad.hs, dist/build/git-annex/git-annex-tmp/Utility/Monad.o )
-[ 30 of 270] Compiling Utility.Path     ( Utility/Path.hs, dist/build/git-annex/git-annex-tmp/Utility/Path.o )
-[ 31 of 270] Compiling Utility.Exception ( Utility/Exception.hs, dist/build/git-annex/git-annex-tmp/Utility/Exception.o )
-[ 32 of 270] Compiling Utility.TempFile ( Utility/TempFile.hs, dist/build/git-annex/git-annex-tmp/Utility/TempFile.o )
-[ 33 of 270] Compiling Utility.Misc     ( Utility/Misc.hs, dist/build/git-annex/git-annex-tmp/Utility/Misc.o )
-[ 34 of 270] Compiling Utility.Process  ( Utility/Process.hs, dist/build/git-annex/git-annex-tmp/Utility/Process.o )
-[ 35 of 270] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, dist/build/git-annex/git-annex-tmp/Utility/SafeCommand.o )
-[ 36 of 270] Compiling Utility.Directory ( Utility/Directory.hs, dist/build/git-annex/git-annex-tmp/Utility/Directory.o )
-[ 37 of 270] Compiling Utility.Network  ( Utility/Network.hs, dist/build/git-annex/git-annex-tmp/Utility/Network.o )
-[ 38 of 270] Compiling Utility.FreeDesktop ( Utility/FreeDesktop.hs, dist/build/git-annex/git-annex-tmp/Utility/FreeDesktop.o )
-[ 39 of 270] Compiling Assistant.Install.AutoStart ( Assistant/Install/AutoStart.hs, dist/build/git-annex/git-annex-tmp/Assistant/Install/AutoStart.o )
-[ 40 of 270] Compiling Utility.SRV      ( Utility/SRV.hs, dist/build/git-annex/git-annex-tmp/Utility/SRV.o )
-[ 41 of 270] Compiling Git.Types        ( Git/Types.hs, dist/build/git-annex/git-annex-tmp/Git/Types.o )
-[ 42 of 270] Compiling Common           ( Common.hs, dist/build/git-annex/git-annex-tmp/Common.o )
-[ 43 of 270] Compiling Utility.FileMode ( Utility/FileMode.hs, dist/build/git-annex/git-annex-tmp/Utility/FileMode.o )
-[ 44 of 270] Compiling Git              ( Git.hs, dist/build/git-annex/git-annex-tmp/Git.o )
-[ 45 of 270] Compiling Git.FilePath     ( Git/FilePath.hs, dist/build/git-annex/git-annex-tmp/Git/FilePath.o )
-[ 46 of 270] Compiling Utility.Matcher  ( Utility/Matcher.hs, dist/build/git-annex/git-annex-tmp/Utility/Matcher.o )
-[ 47 of 270] Compiling Utility.Gpg      ( Utility/Gpg.hs, dist/build/git-annex/git-annex-tmp/Utility/Gpg.o )
-[ 48 of 270] Compiling Types.Crypto     ( Types/Crypto.hs, dist/build/git-annex/git-annex-tmp/Types/Crypto.o )
-[ 49 of 270] Compiling Types.Key        ( Types/Key.hs, dist/build/git-annex/git-annex-tmp/Types/Key.o )
-[ 50 of 270] Compiling Types.Backend    ( Types/Backend.hs, dist/build/git-annex/git-annex-tmp/Types/Backend.o )
-[ 51 of 270] Compiling Types.Remote     ( Types/Remote.hs, dist/build/git-annex/git-annex-tmp/Types/Remote.o )
-[ 52 of 270] Compiling Git.Sha          ( Git/Sha.hs, dist/build/git-annex/git-annex-tmp/Git/Sha.o )
-[ 53 of 270] Compiling Utility.CoProcess ( Utility/CoProcess.hs, dist/build/git-annex/git-annex-tmp/Utility/CoProcess.o )
-[ 54 of 270] Compiling Git.Command      ( Git/Command.hs, dist/build/git-annex/git-annex-tmp/Git/Command.o )
-[ 55 of 270] Compiling Git.Ref          ( Git/Ref.hs, dist/build/git-annex/git-annex-tmp/Git/Ref.o )
-[ 56 of 270] Compiling Git.Branch       ( Git/Branch.hs, dist/build/git-annex/git-annex-tmp/Git/Branch.o )
-[ 57 of 270] Compiling Git.UpdateIndex  ( Git/UpdateIndex.hs, dist/build/git-annex/git-annex-tmp/Git/UpdateIndex.o )
-[ 58 of 270] Compiling Git.Queue        ( Git/Queue.hs, dist/build/git-annex/git-annex-tmp/Git/Queue.o )
-[ 59 of 270] Compiling Git.HashObject   ( Git/HashObject.hs, dist/build/git-annex/git-annex-tmp/Git/HashObject.o )
-[ 60 of 270] Compiling Git.CatFile      ( Git/CatFile.hs, dist/build/git-annex/git-annex-tmp/Git/CatFile.o )
-[ 61 of 270] Compiling Git.UnionMerge   ( Git/UnionMerge.hs, dist/build/git-annex/git-annex-tmp/Git/UnionMerge.o )
-[ 62 of 270] Compiling Git.Url          ( Git/Url.hs, dist/build/git-annex/git-annex-tmp/Git/Url.o )
-[ 63 of 270] Compiling Git.Construct    ( Git/Construct.hs, dist/build/git-annex/git-annex-tmp/Git/Construct.o )
-[ 64 of 270] Compiling Git.Config       ( Git/Config.hs, dist/build/git-annex/git-annex-tmp/Git/Config.o )
-[ 65 of 270] Compiling Git.SharedRepository ( Git/SharedRepository.hs, dist/build/git-annex/git-annex-tmp/Git/SharedRepository.o )
-[ 66 of 270] Compiling Git.Version      ( Git/Version.hs, dist/build/git-annex/git-annex-tmp/Git/Version.o )
-[ 67 of 270] Compiling Git.CheckAttr    ( Git/CheckAttr.hs, dist/build/git-annex/git-annex-tmp/Git/CheckAttr.o )
-[ 68 of 270] Compiling Annex            ( Annex.hs, dist/build/git-annex/git-annex-tmp/Annex.o )
-[ 69 of 270] Compiling Types.Option     ( Types/Option.hs, dist/build/git-annex/git-annex-tmp/Types/Option.o )
-[ 70 of 270] Compiling Types            ( Types.hs, dist/build/git-annex/git-annex-tmp/Types.o )
-[ 71 of 270] Compiling Messages         ( Messages.hs, dist/build/git-annex/git-annex-tmp/Messages.o )
-[ 72 of 270] Compiling Types.Command    ( Types/Command.hs, dist/build/git-annex/git-annex-tmp/Types/Command.o )
-[ 73 of 270] Compiling Locations        ( Locations.hs, dist/build/git-annex/git-annex-tmp/Locations.o )
-[ 74 of 270] Compiling Common.Annex     ( Common/Annex.hs, dist/build/git-annex/git-annex-tmp/Common/Annex.o )
-[ 75 of 270] Compiling Fields           ( Fields.hs, dist/build/git-annex/git-annex-tmp/Fields.o )
-[ 76 of 270] Compiling Annex.BranchState ( Annex/BranchState.hs, dist/build/git-annex/git-annex-tmp/Annex/BranchState.o )
-[ 77 of 270] Compiling Annex.CatFile    ( Annex/CatFile.hs, dist/build/git-annex/git-annex-tmp/Annex/CatFile.o )
-[ 78 of 270] Compiling Annex.Perms      ( Annex/Perms.hs, dist/build/git-annex/git-annex-tmp/Annex/Perms.o )
-[ 79 of 270] Compiling Crypto           ( Crypto.hs, dist/build/git-annex/git-annex-tmp/Crypto.o )
-[ 80 of 270] Compiling Annex.Exception  ( Annex/Exception.hs, dist/build/git-annex/git-annex-tmp/Annex/Exception.o )
-[ 81 of 270] Compiling Annex.Journal    ( Annex/Journal.hs, dist/build/git-annex/git-annex-tmp/Annex/Journal.o )
-[ 82 of 270] Compiling Annex.Branch     ( Annex/Branch.hs, dist/build/git-annex/git-annex-tmp/Annex/Branch.o )
-[ 83 of 270] Compiling Usage            ( Usage.hs, dist/build/git-annex/git-annex-tmp/Usage.o )
-[ 84 of 270] Compiling Annex.CheckAttr  ( Annex/CheckAttr.hs, dist/build/git-annex/git-annex-tmp/Annex/CheckAttr.o )
-[ 85 of 270] Compiling Remote.Helper.Special ( Remote/Helper/Special.hs, dist/build/git-annex/git-annex-tmp/Remote/Helper/Special.o )
-[ 86 of 270] Compiling Logs.Presence    ( Logs/Presence.hs, dist/build/git-annex/git-annex-tmp/Logs/Presence.o )
-[ 87 of 270] Compiling Logs.Location    ( Logs/Location.hs, dist/build/git-annex/git-annex-tmp/Logs/Location.o )
-[ 88 of 270] Compiling Logs.Web         ( Logs/Web.hs, dist/build/git-annex/git-annex-tmp/Logs/Web.o )
-[ 89 of 270] Compiling Annex.LockPool   ( Annex/LockPool.hs, dist/build/git-annex/git-annex-tmp/Annex/LockPool.o )
-[ 90 of 270] Compiling Logs.Transfer    ( Logs/Transfer.hs, dist/build/git-annex/git-annex-tmp/Logs/Transfer.o )
-[ 91 of 270] Compiling Backend.SHA      ( Backend/SHA.hs, dist/build/git-annex/git-annex-tmp/Backend/SHA.o )
-[ 92 of 270] Compiling Backend.WORM     ( Backend/WORM.hs, dist/build/git-annex/git-annex-tmp/Backend/WORM.o )
-[ 93 of 270] Compiling Backend.URL      ( Backend/URL.hs, dist/build/git-annex/git-annex-tmp/Backend/URL.o )
-[ 94 of 270] Compiling Assistant.Ssh    ( Assistant/Ssh.hs, dist/build/git-annex/git-annex-tmp/Assistant/Ssh.o )
-[ 95 of 270] Compiling Assistant.Types.ThreadedMonad ( Assistant/Types/ThreadedMonad.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/ThreadedMonad.o )
-[ 96 of 270] Compiling Assistant.Types.ScanRemotes ( Assistant/Types/ScanRemotes.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/ScanRemotes.o )
-[ 97 of 270] Compiling Assistant.Types.TransferQueue ( Assistant/Types/TransferQueue.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/TransferQueue.o )
-[ 98 of 270] Compiling Assistant.Types.BranchChange ( Assistant/Types/BranchChange.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/BranchChange.o )
-[ 99 of 270] Compiling Assistant.Pairing ( Assistant/Pairing.hs, dist/build/git-annex/git-annex-tmp/Assistant/Pairing.o )
-[100 of 270] Compiling Logs.UUIDBased   ( Logs/UUIDBased.hs, dist/build/git-annex/git-annex-tmp/Logs/UUIDBased.o )
-[101 of 270] Compiling Logs.Remote      ( Logs/Remote.hs, dist/build/git-annex/git-annex-tmp/Logs/Remote.o )
-[102 of 270] Compiling Logs.Group       ( Logs/Group.hs, dist/build/git-annex/git-annex-tmp/Logs/Group.o )
-[103 of 270] Compiling Utility.DiskFree ( Utility/DiskFree.hs, dist/build/git-annex/git-annex-tmp/Utility/DiskFree.o )
-[104 of 270] Compiling Utility.Url      ( Utility/Url.hs, dist/build/git-annex/git-annex-tmp/Utility/Url.o )
-[105 of 270] Compiling Utility.CopyFile ( Utility/CopyFile.hs, dist/build/git-annex/git-annex-tmp/Utility/CopyFile.o )
-[106 of 270] Compiling Utility.Rsync    ( Utility/Rsync.hs, dist/build/git-annex/git-annex-tmp/Utility/Rsync.o )
-[107 of 270] Compiling Git.LsFiles      ( Git/LsFiles.hs, dist/build/git-annex/git-annex-tmp/Git/LsFiles.o )
-[108 of 270] Compiling Git.AutoCorrect  ( Git/AutoCorrect.hs, dist/build/git-annex/git-annex-tmp/Git/AutoCorrect.o )
-[109 of 270] Compiling Git.CurrentRepo  ( Git/CurrentRepo.hs, dist/build/git-annex/git-annex-tmp/Git/CurrentRepo.o )
-[110 of 270] Compiling Git.Merge        ( Git/Merge.hs, dist/build/git-annex/git-annex-tmp/Git/Merge.o )
-[111 of 270] Compiling Utility.WebApp   ( Utility/WebApp.hs, dist/build/git-annex/git-annex-tmp/Utility/WebApp.o )
-[112 of 270] Compiling Utility.Daemon   ( Utility/Daemon.hs, dist/build/git-annex/git-annex-tmp/Utility/Daemon.o )
-[113 of 270] Compiling Locations.UserConfig ( Locations/UserConfig.hs, dist/build/git-annex/git-annex-tmp/Locations/UserConfig.o )
-[114 of 270] Compiling Utility.TSet     ( Utility/TSet.hs, dist/build/git-annex/git-annex-tmp/Utility/TSet.o )
-[115 of 270] Compiling Assistant.Types.Pushes ( Assistant/Types/Pushes.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/Pushes.o )
-[116 of 270] Compiling Assistant.Types.Commits ( Assistant/Types/Commits.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/Commits.o )
-[117 of 270] Compiling Assistant.Types.Changes ( Assistant/Types/Changes.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/Changes.o )
-[118 of 270] Compiling Utility.NotificationBroadcaster ( Utility/NotificationBroadcaster.hs, dist/build/git-annex/git-annex-tmp/Utility/NotificationBroadcaster.o )
-[119 of 270] Compiling Utility.Parallel ( Utility/Parallel.hs, dist/build/git-annex/git-annex-tmp/Utility/Parallel.o )
-[120 of 270] Compiling Utility.ThreadScheduler ( Utility/ThreadScheduler.hs, dist/build/git-annex/git-annex-tmp/Utility/ThreadScheduler.o )
-[121 of 270] Compiling Utility.LogFile  ( Utility/LogFile.hs, dist/build/git-annex/git-annex-tmp/Utility/LogFile.o )
-[122 of 270] Compiling Git.Filename     ( Git/Filename.hs, dist/build/git-annex/git-annex-tmp/Git/Filename.o )
-[123 of 270] Compiling Git.LsTree       ( Git/LsTree.hs, dist/build/git-annex/git-annex-tmp/Git/LsTree.o )
-[124 of 270] Compiling Utility.Types.DirWatcher ( Utility/Types/DirWatcher.hs, dist/build/git-annex/git-annex-tmp/Utility/Types/DirWatcher.o )
-[125 of 270] Compiling Utility.INotify  ( Utility/INotify.hs, dist/build/git-annex/git-annex-tmp/Utility/INotify.o )
-[126 of 270] Compiling Utility.DirWatcher ( Utility/DirWatcher.hs, dist/build/git-annex/git-annex-tmp/Utility/DirWatcher.o )
-[127 of 270] Compiling Utility.Lsof     ( Utility/Lsof.hs, dist/build/git-annex/git-annex-tmp/Utility/Lsof.o )
-[128 of 270] Compiling Config           ( Config.hs, dist/build/git-annex/git-annex-tmp/Config.o )
-[129 of 270] Compiling Annex.UUID       ( Annex/UUID.hs, dist/build/git-annex/git-annex-tmp/Annex/UUID.o )
-[130 of 270] Compiling Logs.UUID        ( Logs/UUID.hs, dist/build/git-annex/git-annex-tmp/Logs/UUID.o )
-[131 of 270] Compiling Backend          ( Backend.hs, dist/build/git-annex/git-annex-tmp/Backend.o )
-[132 of 270] Compiling Remote.Helper.Hooks ( Remote/Helper/Hooks.hs, dist/build/git-annex/git-annex-tmp/Remote/Helper/Hooks.o )
-[133 of 270] Compiling Remote.Helper.Encryptable ( Remote/Helper/Encryptable.hs, dist/build/git-annex/git-annex-tmp/Remote/Helper/Encryptable.o )
-[134 of 270] Compiling Annex.Queue      ( Annex/Queue.hs, dist/build/git-annex/git-annex-tmp/Annex/Queue.o )
-[135 of 270] Compiling Annex.Content    ( Annex/Content.hs, dist/build/git-annex/git-annex-tmp/Annex/Content.o )
-[136 of 270] Compiling Remote.S3        ( Remote/S3.hs, dist/build/git-annex/git-annex-tmp/Remote/S3.o )
-[137 of 270] Compiling Remote.Directory ( Remote/Directory.hs, dist/build/git-annex/git-annex-tmp/Remote/Directory.o )
-[138 of 270] Compiling Remote.Rsync     ( Remote/Rsync.hs, dist/build/git-annex/git-annex-tmp/Remote/Rsync.o )
-[139 of 270] Compiling Remote.Web       ( Remote/Web.hs, dist/build/git-annex/git-annex-tmp/Remote/Web.o )
-[140 of 270] Compiling Remote.Hook      ( Remote/Hook.hs, dist/build/git-annex/git-annex-tmp/Remote/Hook.o )
-[141 of 270] Compiling Upgrade.V2       ( Upgrade/V2.hs, dist/build/git-annex/git-annex-tmp/Upgrade/V2.o )
-[142 of 270] Compiling Annex.Ssh        ( Annex/Ssh.hs, dist/build/git-annex/git-annex-tmp/Annex/Ssh.o )
-[143 of 270] Compiling Remote.Helper.Ssh ( Remote/Helper/Ssh.hs, dist/build/git-annex/git-annex-tmp/Remote/Helper/Ssh.o )
-[144 of 270] Compiling Remote.Bup       ( Remote/Bup.hs, dist/build/git-annex/git-annex-tmp/Remote/Bup.o )
-[145 of 270] Compiling Annex.Version    ( Annex/Version.hs, dist/build/git-annex/git-annex-tmp/Annex/Version.o )
-[146 of 270] Compiling Init             ( Init.hs, dist/build/git-annex/git-annex-tmp/Init.o )
-[147 of 270] Compiling Checks           ( Checks.hs, dist/build/git-annex/git-annex-tmp/Checks.o )
-[148 of 270] Compiling Remote.Git       ( Remote/Git.hs, dist/build/git-annex/git-annex-tmp/Remote/Git.o )
-[149 of 270] Compiling Remote.List      ( Remote/List.hs, dist/build/git-annex/git-annex-tmp/Remote/List.o )
-[150 of 270] Compiling Logs.Trust       ( Logs/Trust.hs, dist/build/git-annex/git-annex-tmp/Logs/Trust.o )
-[151 of 270] Compiling Remote           ( Remote.hs, dist/build/git-annex/git-annex-tmp/Remote.o )
-[152 of 270] Compiling Assistant.Alert  ( Assistant/Alert.hs, dist/build/git-annex/git-annex-tmp/Assistant/Alert.o )
-
-Assistant/Alert.hs:60:26:
-    Not in scope: type constructor or class `Html'
-
-Assistant/Alert.hs:66:21: Not in scope: `preEscapedText'
-
-Assistant/Alert.hs:68:26:
-    Not in scope: type constructor or class `Html'
-
-Assistant/Alert.hs:69:19: Not in scope: `preEscapedText'
-</pre>
-
-What is the expected output? What do you see instead?
-
-The current git HEAD should build and not throw an error.
-
-What version of git-annex are you using? On what operating system?
-
-git-annex HEAD from git, Ubuntu 12.10.
-
-Please provide any additional information below.
-
-> Hmm, seems that Blaze's API is not stable, and I should avoid using it
-> directly. Converted this code to using Hamlet instead for its html
-> generation. [[done]] --[[Joey]]
diff --git a/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link.mdwn b/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link.mdwn
deleted file mode 100644
index 223568ca8..000000000
--- a/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-What steps will reproduce the problem?
-
-Download the sourcecode, build using 'cabal build', then install using 'cabal install --bindir ~/bin'. 
-
-What is the expected output? What do you see instead?
-
-The .desktop file contains `~/bin/git-annex webapp` as command which is of course a invalid command as ~ is not expanded when running the desktop file. 
-
-What version of git-annex are you using? On what operating system?
-Latest Head from git, Ubuntu 12.04
-
-Please provide any additional information below.
-I'm not sure whether this is a bug or not. I just ran into problems because I did not expect the cabal build process to create my desktop file but instead thought that git-annex will create it by it-self taking its own path. Perhaps it would make sense to produce an error if the bindir is invalid. An automatic expansion of '~' in the build script would be even better.
-
-> [[done]], I think it was a typo. --[[Joey]]
diff --git a/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_1_c0f0a2878070ed86900815c6b6a5fa5e._comment b/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_1_c0f0a2878070ed86900815c6b6a5fa5e._comment
deleted file mode 100644
index 82dfa0d48..000000000
--- a/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_1_c0f0a2878070ed86900815c6b6a5fa5e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.60"
- subject="comment 1"
- date="2012-09-15T16:39:19Z"
- content="""
-Something is going on that I don't understand. When I run `cabal install --bindir ~/bin`, my shell passes `/home/joey/bin` to cabal, so of course it works.
-"""]]
diff --git a/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_2_53f2de3d3993821d8502fd08a0fcce12._comment b/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_2_53f2de3d3993821d8502fd08a0fcce12._comment
deleted file mode 100644
index 69d795865..000000000
--- a/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link/comment_2_53f2de3d3993821d8502fd08a0fcce12._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-03-19T00:07:23Z"
- content="""
-It seems to me that --bindir ~/bin will work, but --bindir=~/bin will not; it prevents the shell's tilde expansion from working. 
-"""]]
diff --git a/doc/bugs/Building_on_OpenBSD.mdwn b/doc/bugs/Building_on_OpenBSD.mdwn
deleted file mode 100644
index b500d8a4b..000000000
--- a/doc/bugs/Building_on_OpenBSD.mdwn
+++ /dev/null
@@ -1,40 +0,0 @@
-### Please describe the problem.
-Hi!
-I just tried to build git-annex through cabal on OpenBSD and encountered some issues.
-
-First I had to install a certain commit of network-info that fixes some compile-time errors (https://github.com/jystic/network-info/issues/6)
-Then I had to disable WebDAV in git-annex because DAV wouldn't build (I don't use webdav anyway)
-
-After this git-annex still failed to build, though configure works.
-### What steps will reproduce the problem?
-Compiling on openbsd through cabal
-
-### What version of git-annex are you using? On what operating system?
-git-annex-5.20131130 on OpenBSD 5.4
-
-### Please provide any additional information below.
-
-[[!format sh """
-The error in question:
-[312 of 389] Compiling Assistant.Pairing.Network ( Assistant/Pairing/Network.hs, dist/build/git-annex/git-annex-tmp/Assistant/Pairing/Network.o )
-
-Assistant/Pairing/Network.hs:101:21:
-    Not in scope: type constructor or class `IPv4'
-
-Assistant/Pairing/Network.hs:102:21:
-    Not in scope: data constructor `IPv4'
-
-Assistant/Pairing/Network.hs:104:21:
-    Not in scope: type constructor or class `IPv6'
-
-Assistant/Pairing/Network.hs:105:21:
-    Not in scope: data constructor `IPv6'
-
-Assistant/Pairing/Network.hs:108:32:
-    Not in scope: data constructor `IPv4'
-
-Assistant/Pairing/Network.hs:109:47:
-    Not in scope: data constructor `IPv6'
-"""]]
-
-> [[done]]; see comment --[[Joey]]
diff --git a/doc/bugs/Building_on_OpenBSD/comment_1_bec4a7253e851567cd47b96ceead5d91._comment b/doc/bugs/Building_on_OpenBSD/comment_1_bec4a7253e851567cd47b96ceead5d91._comment
deleted file mode 100644
index 01304cc8f..000000000
--- a/doc/bugs/Building_on_OpenBSD/comment_1_bec4a7253e851567cd47b96ceead5d91._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 1"
- date="2013-12-12T17:32:23Z"
- content="""
-network-info is where IPv4 and IPv6 are defined. You have chosen to installs it \"dev\" branch, which removes those and has a top commit of \"wip - don't pull this, not working on unix yet\".
-
-What you should really do is just disable local pairing, which avoids the need for porting network-info to openbsd. You can do so by passing -f-Pairing to cabal configure. There are lots of other features that can be similarly disabled if their necessary depedencies cannot be installed (normally this is done automatically.)
-"""]]
diff --git a/doc/bugs/Building_on_OpenBSD/comment_2_4a37935080b86643ecda717fe17f8f87._comment b/doc/bugs/Building_on_OpenBSD/comment_2_4a37935080b86643ecda717fe17f8f87._comment
deleted file mode 100644
index 3a7f85fdc..000000000
--- a/doc/bugs/Building_on_OpenBSD/comment_2_4a37935080b86643ecda717fe17f8f87._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkzwmw_zyMpZC9_J7ey--woeYPoZkAOgGw"
- nickname="dxtrish"
- subject="comment 2"
- date="2014-02-04T13:45:25Z"
- content="""
-Sorry for the long delay, but I've tried what you said:
-``% cabal install git-annex --bindir=$HOME/bin --flags=\"-pairing -webdav\" -j2``
-
-and it STILL fails with:
-``cabal: user error (Error: some packages failed to install:
-git-annex-5.20140129 depends on network-info-0.2.0.3 which failed to install.
-network-info-0.2.0.3 failed during the building phase. The exception was:
-ExitFailure 1
-uuid-1.3.3 depends on network-info-0.2.0.3 which failed to install.
-)``
-
-"""]]
diff --git a/doc/bugs/Building_on_OpenBSD/comment_3_2df229eb965189e2f7ea6dcd66cf68ca._comment b/doc/bugs/Building_on_OpenBSD/comment_3_2df229eb965189e2f7ea6dcd66cf68ca._comment
deleted file mode 100644
index 51153b671..000000000
--- a/doc/bugs/Building_on_OpenBSD/comment_3_2df229eb965189e2f7ea6dcd66cf68ca._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkzwmw_zyMpZC9_J7ey--woeYPoZkAOgGw"
- nickname="dxtrish"
- subject="comment 3"
- date="2014-02-04T14:04:33Z"
- content="""
-And the UUID package requires network-info and git-annex seems to require the UUID package.
-Also notice that the configure can't find the SHA commands:
-     checking sha1... not available
-     checking sha256... not available
-     checking sha512... not available
-     checking sha224... not available
-     checking sha384... not available
-     Configuring git-annex-5.20140129...
-     setup: user error (At least the following dependencies are missing:
-     uuid -any)
-
-Even though:
-     % which sha1
-     /bin/sha1
-     % which sha256
-     /bin/sha256
-
-"""]]
diff --git a/doc/bugs/Building_on_OpenBSD/comment_4_d141c0bac92bdfbc8b95d532d032174c._comment b/doc/bugs/Building_on_OpenBSD/comment_4_d141c0bac92bdfbc8b95d532d032174c._comment
deleted file mode 100644
index 090fed454..000000000
--- a/doc/bugs/Building_on_OpenBSD/comment_4_d141c0bac92bdfbc8b95d532d032174c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkzwmw_zyMpZC9_J7ey--woeYPoZkAOgGw"
- nickname="dxtrish"
- subject="comment 4"
- date="2014-02-04T14:05:19Z"
- content="""
-And why isn't the formatting working? :p
-"""]]
diff --git a/doc/bugs/Building_on_OpenBSD/comment_5_8aba96ef58eb6954f1d15029e0dda9ed._comment b/doc/bugs/Building_on_OpenBSD/comment_5_8aba96ef58eb6954f1d15029e0dda9ed._comment
deleted file mode 100644
index 89bd81b60..000000000
--- a/doc/bugs/Building_on_OpenBSD/comment_5_8aba96ef58eb6954f1d15029e0dda9ed._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="206.74.132.139"
- subject="comment 5"
- date="2014-02-06T17:10:59Z"
- content="""
-Ok, I missed that uuid needs network-info. Actually, git-annex does not use that part of uuid (it does not put IP info in its uuids). There is a past version of uuid that did not depend on network-info. Perhaps you should first install it: `cabal install uuid-1.2.14`
-
-As far as it not finding or liking the sha* commands, it may be that it is not able to parse the OpenBSD output, or doesn't see the output it expects when testing them. These commands are only used as a minor optimisation, if not available it will fall back to using a haskell implementation which is a few percent slower (or faster) than the linux coreutils version of sha*. I don't know how the speeds compare on OpenBSD, but it's probably not worth worrying about.
-"""]]
diff --git a/doc/bugs/Building_on_OpenBSD/comment_6_82e6744e246fe5caa72081d4e921b168._comment b/doc/bugs/Building_on_OpenBSD/comment_6_82e6744e246fe5caa72081d4e921b168._comment
deleted file mode 100644
index ac01f1a5c..000000000
--- a/doc/bugs/Building_on_OpenBSD/comment_6_82e6744e246fe5caa72081d4e921b168._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkzwmw_zyMpZC9_J7ey--woeYPoZkAOgGw"
- nickname="dxtrish"
- subject="comment 6"
- date="2014-02-07T11:16:17Z"
- content="""
-Actually what I did was to patch network-info to build under openbsd.
-I've literally never touched Haskell but fortunately it was C code that needed fixing and so far it seems to be working.
-
-I'm intending to contact the maintainer of that package and let him know
-"""]]
diff --git a/doc/bugs/Cabal_cannot_solve_dependencies.mdwn b/doc/bugs/Cabal_cannot_solve_dependencies.mdwn
deleted file mode 100644
index ac9738b03..000000000
--- a/doc/bugs/Cabal_cannot_solve_dependencies.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-### Please describe the problem.
-
-This is a follow up of [[Problems building on Mac OS X]].
-As of 4.20130521.1, cabal still cannot resolve the dependencies.
-
-### What steps will reproduce the problem?
-
-    cabal update
-    cabal install git-annex-4.20130521.1 --user --only-dependencies
-
-### Please provide any additional information below.
-
-[[!format sh """
-Resolving dependencies...
-cabal: Could not resolve dependencies:
-trying: git-annex-4.20130521.1
-trying: git-annex-4.20130521.1:+webapp
-trying: yesod-form-1.3.0
-trying: yesod-core-1.2.1
-rejecting: yesod-default-1.2.0 (conflict: git-annex-4.20130521.1:webapp =>
-yesod-default(<1.2))
-rejecting: yesod-default-1.1.3.2, 1.1.3.1, 1.1.3, 1.1.2, 1.1.1, 1.1.0.2,
-1.1.0.1, 1.1.0 (conflict: yesod-core==1.2.1, yesod-default => yesod-core>=1.1
-&& <1.2)
-rejecting: yesod-default-1.0.1.1, 1.0.1, 1.0.0 (conflict: yesod-core==1.2.1,
-yesod-default => yesod-core>=1.0 && <1.1)
-rejecting: yesod-default-0.6.1 (conflict: yesod-core==1.2.1, yesod-default =>
-yesod-core>=0.10.1 && <0.11)
-rejecting: yesod-default-0.5.0 (conflict: yesod-core==1.2.1, yesod-default =>
-yesod-core>=0.9.4 && <0.10)
-rejecting: yesod-default-0.4.1, 0.4.0, 0.3.1 (conflict: yesod-core==1.2.1,
-yesod-default => yesod-core>=0.9 && <0.10
-"""]]
-
-> At the risk of closing early again, I have uploaded a .2 with
-> hints for the version of yesod-form and yesod-static. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Cabal_cannot_solve_dependencies/comment_1_1d41ac79867226dcb71f1c7b38da062d._comment b/doc/bugs/Cabal_cannot_solve_dependencies/comment_1_1d41ac79867226dcb71f1c7b38da062d._comment
deleted file mode 100644
index 91bcbe42f..000000000
--- a/doc/bugs/Cabal_cannot_solve_dependencies/comment_1_1d41ac79867226dcb71f1c7b38da062d._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-24T14:21:03Z"
- content="""
-Since I tested this release in a clean system, I suspect you have a ~/.ghc and ~/.cabal with something installed that is causing this dependency problem for you. 
-
-<pre>
-# rm -rf .ghc .cabal
-# cabal update
-Config file path source is default config file.
-Config file /root/.cabal/config not found.
-Writing default configuration to /root/.cabal/config
-Downloading the latest package list from hackage.haskell.org
-# cabal install git-annex
-Resolving dependencies...
-Downloading HUnit-1.2.5.2...
-Configuring HUnit-1.2.5.2...
-</pre>
-"""]]
diff --git a/doc/bugs/Cabal_cannot_solve_dependencies/comment_2_50e72633a4462f6f6eb33d57b137fdcc._comment b/doc/bugs/Cabal_cannot_solve_dependencies/comment_2_50e72633a4462f6f6eb33d57b137fdcc._comment
deleted file mode 100644
index 78faa6732..000000000
--- a/doc/bugs/Cabal_cannot_solve_dependencies/comment_2_50e72633a4462f6f6eb33d57b137fdcc._comment
+++ /dev/null
@@ -1,48 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmu416zAYgYzbXVZAe30MiXoOWO4z6nGX8"
- nickname="Johannes"
- subject="comment 2"
- date="2013-05-24T14:59:54Z"
- content="""
-Thanks for the quick comment. I was already trying to build this on a clean cabal system.
-
-However, as of 4.20130521.2, I now get this:
-
-[[!format  sh \"\"\"
-Resolving dependencies...
-cabal: Could not resolve dependencies:
-trying: git-annex-4.20130521.2
-trying: git-annex-4.20130521.2:+webapp
-rejecting: yesod-1.2.0.1, 1.2.0 (conflict: git-annex-4.20130521.2:webapp =>
-yesod(<1.2))
-trying: yesod-1.1.9.3
-trying: http-conduit-1.9.3
-trying: certificate-1.3.7
-rejecting: crypto-pubkey-types-0.4.0 (conflict: certificate =>
-crypto-pubkey-types>=0.3 && <0.4)
-trying: crypto-pubkey-types-0.3.2
-trying: tls-extra-0.6.3
-rejecting: crypto-pubkey-0.1.4 (conflict: crypto-pubkey-types==0.3.2,
-crypto-pubkey => crypto-pubkey-types>=0.4 && <0.5)
-rejecting: crypto-pubkey-0.1.3, 0.1.2, 0.1.1, 0.1.0 (conflict: tls-extra =>
-crypto-pubkey>=0.1.4)
-\"\"\"]]
-
-Also tried adding a --constraint='tls-extra<0.6.3' with the following result:
-[[!format  sh \"\"\"
-Resolving dependencies...
-cabal: Could not resolve dependencies:
-trying: git-annex-4.20130521.2
-trying: git-annex-4.20130521.2:+webapp
-trying: git-annex-4.20130521.2:+dns
-trying: dns-0.3.6
-trying: binary-0.7.1.0/installed-caa...
-rejecting: yesod-1.2.0.1, 1.2.0 (conflict: git-annex-4.20130521.2:webapp =>
-yesod(<1.2))
-trying: yesod-1.1.9.3
-trying: ghc-7.6.3/installed-875...
-rejecting: bin-package-db-0.0.0.0/installed-608... (conflict:
-binary==0.7.1.0/installed-caa..., bin-package-db =>
-binary==0.5.1.1/installed-72e...)
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/Cabal_cannot_solve_dependencies/comment_3_886f2d1f7c47a3973b8dc7d7c412289a._comment b/doc/bugs/Cabal_cannot_solve_dependencies/comment_3_886f2d1f7c47a3973b8dc7d7c412289a._comment
deleted file mode 100644
index a91a95953..000000000
--- a/doc/bugs/Cabal_cannot_solve_dependencies/comment_3_886f2d1f7c47a3973b8dc7d7c412289a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-05-24T15:05:13Z"
- content="""
-bin-package-db is shipped with ghc, so this may be down to your version of ghc. FWIW, I have tested .2 on OSX with ghc 7.4.2 & it works.
-
-(I can only support users cabal hell problems so far. Cabal is, unfortunately, basically buggy, and this is a large part of why I provide autobuilds.)
-"""]]
diff --git a/doc/bugs/Cabal_dependency_monadIO_missing.mdwn b/doc/bugs/Cabal_dependency_monadIO_missing.mdwn
deleted file mode 100644
index 13980dd29..000000000
--- a/doc/bugs/Cabal_dependency_monadIO_missing.mdwn
+++ /dev/null
@@ -1,17 +0,0 @@
-Just issuing the command `cabal install` results in the following error message.
-
-    Command/Add.hs:54:3:
-        No instance for (Control.Monad.IO.Control.MonadControlIO
-                           (Control.Monad.State.Lazy.StateT Annex.AnnexState IO))
-          arising from a use of `handle' at Command/Add.hs:54:3-24
-
-Adding the dependency for `monadIO` to `git-annex.cabal` should fix this?  
--- Thomas
-
-> No, it's already satisfied by `monad-control` being listed as a
-> dependency in the cabal file. Your system might be old/new/or broken,
-> perhaps it's time to provide some details about the version of haskell
-> and of `monad-control` you have installed? --[[Joey]] 
-
->> Closing as apparently user error or a broken system.
->> If you see this problem please do say. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Cabal_dependency_monadIO_missing/comment_1_14be660aa57fadec0d81b32a8b52c66f._comment b/doc/bugs/Cabal_dependency_monadIO_missing/comment_1_14be660aa57fadec0d81b32a8b52c66f._comment
deleted file mode 100644
index 8e38205f0..000000000
--- a/doc/bugs/Cabal_dependency_monadIO_missing/comment_1_14be660aa57fadec0d81b32a8b52c66f._comment
+++ /dev/null
@@ -1,75 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmFgsNxmnGznb5bbmcoWhoQOoxZZ-io61s"
- nickname="Thomas"
- subject="comment 1"
- date="2011-08-08T09:04:20Z"
- content="""
-I use Debian Squeeze, I have the Debian package cabal-install 0.8.0-1 installed.
-
-    $ git clone git://git-annex.branchable.com/
-    $ cd git-annex.branchable.com
-    $ cabal update
-    $ cabal install cabal-install
-
-This installed: Cabal-1.10.2.0, zlib-0.5.3.1, cabal-install 0.10.2.
-No version of monad-control or monadIO installed.
-
-    $ ~/.cabal/bin/cabal install
-    Registering QuickCheck-2.4.1.1...
-    Registering Crypto-4.2.3...
-    Registering base-unicode-symbols-0.2.2.1...
-    Registering deepseq-1.1.0.2...
-    Registering hxt-charproperties-9.1.0...
-    Registering hxt-regex-xmlschema-9.0.0...
-    Registering hxt-unicode-9.0.1...
-    Registering hxt-9.1.2...
-    Registering stm-2.2.0.1...
-    Registering hS3-0.5.6...
-    Registering transformers-0.2.2.0...
-    Registering monad-control-0.2.0.1...
-    [1 of 1] Compiling Main             ( Setup.hs, dist/setup/Main.o )
-    Linking ./dist/setup/setup ...
-    ghc -O2 -Wall -ignore-package monads-fd -fspec-constr-count=5 --make configure
-    [1 of 2] Compiling TestConfig       ( TestConfig.hs, TestConfig.o )
-    [2 of 2] Compiling Main             ( configure.hs, configure.o )
-    Linking configure ...
-    ./configure
-      checking version... 3.20110720
-      checking cp -a... yes
-      checking cp -p... yes
-      checking cp --reflink=auto... yes
-      checking uuid generator... uuid
-      checking xargs -0... yes
-      checking rsync... yes
-      checking curl... yes
-      checking bup... yes
-      checking gpg... yes
-      checking sha1... sha1sum
-      checking sha256... sha256sum
-      checking sha512... sha512sum
-      checking sha224... sha224sum
-      checking sha384... sha384sum
-
-    ...
-
-    Command/Add.hs:54:3:
-        No instance for (Control.Monad.IO.Control.MonadControlIO
-                           (Control.Monad.State.Lazy.StateT Annex.AnnexState IO))
-          arising from a use of `handle' at Command/Add.hs:54:3-24
-        Possible fix:
-          add an instance declaration for
-          (Control.Monad.IO.Control.MonadControlIO
-             (Control.Monad.State.Lazy.StateT Annex.AnnexState IO))
-        In the first argument of `($)', namely `handle (undo file key)'
-        In a stmt of a 'do' expression:
-              handle (undo file key) $ moveAnnex key file
-        In the expression:
-            do { handle (undo file key) $ moveAnnex key file;
-                 next $ cleanup file key }
-    cabal: Error: some packages failed to install:
-    git-annex-3.20110719 failed during the building phase. The exception was:
-    ExitFailure 1
-
-After I added a depencency for monadIO to the git-annex.cabal file, it installed correctly.  
--- Thomas
-"""]]
diff --git a/doc/bugs/Cabal_dependency_monadIO_missing/comment_2_4f4d8e1e00a2a4f7e8a8ab082e16adac._comment b/doc/bugs/Cabal_dependency_monadIO_missing/comment_2_4f4d8e1e00a2a4f7e8a8ab082e16adac._comment
deleted file mode 100644
index adf7a34e6..000000000
--- a/doc/bugs/Cabal_dependency_monadIO_missing/comment_2_4f4d8e1e00a2a4f7e8a8ab082e16adac._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-08-17T04:56:30Z"
- content="""
-Finally got a chance to try to reproduce this. I followed your recipe exactly in a clean squeeze chroot. monadIO was not installed, but git-annex built ok, using monad-control.
-"""]]
diff --git a/doc/bugs/Calls_to_rsync_don__39__t_always_use__annex-rsync-options.mdwn b/doc/bugs/Calls_to_rsync_don__39__t_always_use__annex-rsync-options.mdwn
deleted file mode 100644
index df1163b46..000000000
--- a/doc/bugs/Calls_to_rsync_don__39__t_always_use__annex-rsync-options.mdwn
+++ /dev/null
@@ -1,35 +0,0 @@
-What steps will reproduce the problem?
-
-Add a rsync special remote - one that you need a username/password to access (stored in text file $HOME/.rsync.password):
-
-    $ git annex initremote myrsync type=rsync rsyncurl=rsync://username@rsync.example.com/myrsync encryption=none
-    $ git annex describe myrsync "rsync server"
-    $ git config remote.myrsync.annex-rsync-options "--password-file=$HOME/.rsync.password"
-
-Copy a file to the remote:
-
-    $ git annex -d copy my-file --to myrsync
-
-What is the expected output? What do you see instead?
-
-Expect to see the file copied over to the rsync remote, but the check doesn't use the annex-rsync-options and asks for a password.  The debug output is:
-
-    copy my-file (checking myrsync...) [2012-10-28 01:01:01 EST] call: sh ["-c","rsync --quiet 'rsync://username@rsync.example.com/myrsync/[...SNIP...]' 2>/dev/null"]
-
-However the actual copy does use annex-rsync-options and the copy works:
-
-    [2012-10-28 01:01:05 EST] read: rsync ["--password-file=/home/blah/.rsync.password","--progress","--recursive","--partial","--partial-dir=.rsync-partial","/home/blah/annex/.git/annex/tmp/rsynctmp/12345/","rsync://username@rsync.example.com/myrsync"]
-
-
-What version of git-annex are you using? On what operating system?
-
-git-annex: 3.20121017
-
-OS: Ubuntu 12.04
-
-Please provide any additional information below.
-
-I think this fix is as easy as including the annex-rsync-options wherever rsync is called.
-
-> I belive there was only the one place this was neglected. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/Can__39__t___34__git-annex_get__34___with_3.20111203.mdwn b/doc/bugs/Can__39__t___34__git-annex_get__34___with_3.20111203.mdwn
deleted file mode 100644
index ea56c3732..000000000
--- a/doc/bugs/Can__39__t___34__git-annex_get__34___with_3.20111203.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-Hi there,
-
-After updating to 3.20111203 (on Arch Linux) I noticed I was not able to use `git annex get` from a SSH remote (server running Arch Linux, same version of git-annex): "requested key is not present". Same behavior with current master (commit 6cf28585). I had no issue with the previous version (3.20111122).
-
-On this server, I was able to track down the issue using `git-annex-shell inannex` and `strace`:
-
-    $ strace -f -o log git-annex-shell inannex ~/photos-annex.git WORM-s369360-m1321602916--2011-11-17.jpg   
-    $ echo $?
-    1
-    $ tail -n20 log
-    [...]
-    25623 chdir("/home/schnouki/git-annex") = 0
-    25623 stat("/home/schnouki/photos-annex.git/annex/objects/082/676/WORM-s369360-m1321602916--2011-11-17.jpg/WORM-s369360-m1321602916--2011-11-17.jpg", {st_mode=S_IFREG|0400, st_size=369360, ...}) = 0
-    25623 open("annex/objects/082/676/WORM-s369360-m1321602916--2011-11-17.jpg/WORM-s369360-m1321602916--2011-11-17.jpg", O_RDONLY) = -1 ENOENT (No such file or directory)
-    [...]
-
-Note there is a call to `stat()` with the full path to the requested file, and *then* a call to `open()` with a relative path -- which calls this call to fail, and git-annex-shell to return 1. With 3.20111122, there was no call to `stat()`, just a successful call to `open()` with a full absolute path.
-
-Using `git bisect` I was able to determine that this bug appeared in commit 64672c62 ("refactor"). Reverting it makes `git-annex-shell` work as expected, but I'm sure there are better ways to fix this. However I don't know enough Haskell to do it myself.
-
-Could you please try to fix this in a future version?
-
-> Thanks for a very good bug report. 
-> 
-> I've fixed this stupid mistake introduced in the code refactoring.
-> [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/Can__39__t_rename___34__here__34___repository.mdwn b/doc/bugs/Can__39__t_rename___34__here__34___repository.mdwn
deleted file mode 100644
index af3330670..000000000
--- a/doc/bugs/Can__39__t_rename___34__here__34___repository.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-### Please describe the problem.
-Trying to rename the "here" repository fails
-
-### What steps will reproduce the problem?
-* Start git-annex webapp in the console (for the first time, or remove old annex directory + .config/git-annex)
-* In the browser window that opens click "Make repository"
-* The "here" repository should show up in the dashboard
-* Go to settings and select edit
-* Change the repository name (e.g. to here2) and click save changes
-* You should be back at the dashboard and the repository name is still "here"
-
-
-### What version of git-annex are you using? On what operating system?
-* git-annex version: 4.20130601
-* build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-* built using cabal
-* on Ubuntu 13.04 32bit
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[2013-06-12 22:22:57 CEST] main: starting assistant version 4.20130601
-(scanning...) [2013-06-12 22:22:57 CEST] Watcher: Performing startup scan
-(started...) 
-
-# End of transcript or log.
-"""]]
-
-> Made text field for this repository disabled. The current repository has no remote name to edit. [[done]] --[[Joey]]
diff --git a/doc/bugs/Can__39__t_set_repositories_directory.mdwn b/doc/bugs/Can__39__t_set_repositories_directory.mdwn
deleted file mode 100644
index f1ce5dea5..000000000
--- a/doc/bugs/Can__39__t_set_repositories_directory.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-Can't set the repository directory
-
-
-At beginning during the webapp installation
-
-
-0.0.1 for OS X 10.8.2
-
-
-user error (git ["--git-dir=/Users/filippo/Desktop/annex/.git","--work-tree=/Users/filippo/Desktop/annex","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] exited 128)
-
-[[!tag moreinfo assistant]]
-
-> [[done]]; based on the comment, this was a broken git email issue, which
-> git-annex now works around. --[[Joey]]
diff --git a/doc/bugs/Can__39__t_set_repositories_directory/comment_1_beb5d5b66a8d0fab12be44a7d877e9b0._comment b/doc/bugs/Can__39__t_set_repositories_directory/comment_1_beb5d5b66a8d0fab12be44a7d877e9b0._comment
deleted file mode 100644
index d769219cc..000000000
--- a/doc/bugs/Can__39__t_set_repositories_directory/comment_1_beb5d5b66a8d0fab12be44a7d877e9b0._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-19T20:12:18Z"
- content="""
-There has never been a git-annex version 0.0.1. What is the real version you have installed?
-"""]]
diff --git a/doc/bugs/Can__39__t_set_repositories_directory/comment_2_366aa798a5e55350d32b63b31c19112b._comment b/doc/bugs/Can__39__t_set_repositories_directory/comment_2_366aa798a5e55350d32b63b31c19112b._comment
deleted file mode 100644
index 2af33522b..000000000
--- a/doc/bugs/Can__39__t_set_repositories_directory/comment_2_366aa798a5e55350d32b63b31c19112b._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnGrQBFPptA2GU_Nx8KrxRGtyAS7PIlwjw"
- nickname="Nathan"
- subject="same problem here"
- date="2013-06-27T12:32:28Z"
- content="""
-Ran into this same problem just now. I can't start as I cant make a repository.
-
-Error:
-
-Internal Server Error
-user error (git [\"--git-dir=/Users/Nathan/annex/.git\",\"--work-tree=/Users/Nathan/annex\",\"commit-tree\",\"4b825dc642cb6eb9a060e54bf8d69288fbee4904\"] exited 128)
-
-git-annex version: 
-
-4.20130626-g2dd6f84
-
-Could this have something to do with me first frigging around trying to get git-annex installed via homebrew? Maybe I broke something first?
-"""]]
diff --git a/doc/bugs/Can__39__t_set_repositories_directory/comment_3_812554d58ad9274a50b2a33d5f4d2ec3._comment b/doc/bugs/Can__39__t_set_repositories_directory/comment_3_812554d58ad9274a50b2a33d5f4d2ec3._comment
deleted file mode 100644
index 75145b709..000000000
--- a/doc/bugs/Can__39__t_set_repositories_directory/comment_3_812554d58ad9274a50b2a33d5f4d2ec3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.193"
- subject="comment 3"
- date="2013-06-27T18:19:57Z"
- content="""
-Maybe git is broken somehow? 
-
-What you can do is run `/Volumes/git-annex/git-annex.app/Contents/MacOS/git-annex-webapp` manually, in a console, and hopefully there will be a more informative error message displayed there.
-"""]]
diff --git a/doc/bugs/Can__39__t_set_repositories_directory/comment_4_bec5f147441ad18c97845b44c90c728b._comment b/doc/bugs/Can__39__t_set_repositories_directory/comment_4_bec5f147441ad18c97845b44c90c728b._comment
deleted file mode 100644
index cdbcce515..000000000
--- a/doc/bugs/Can__39__t_set_repositories_directory/comment_4_bec5f147441ad18c97845b44c90c728b._comment
+++ /dev/null
@@ -1,28 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnGrQBFPptA2GU_Nx8KrxRGtyAS7PIlwjw"
- nickname="Nathan"
- subject="comment 4"
- date="2013-06-28T04:01:22Z"
- content="""
-Okay I did that and got the following:
-
-
-
-     Launching web browser on file:///var/folders/7x/cmkqk6jn7ql7h_2wrc7kk4bc0000gn/T/webapp897.html
-
-     *** Please tell me who you are.
-
-     Run
-
-       git config --global user.email \"you@example.com\"
-       git config --global user.name \"Your Name\"
-
-     to set your account's default identity.
-     Omit --global to set the identity only in this repository.
-
-     fatal: unable to auto-detect email address (got 'Nathan@nathans-mac-pro.(none)')
-     28/Jun/2013:13:54:04 +1000 [Error#yesod-core] user error (git [\"--git-dir=/Users/Nathan/Annex/.git\",\"--work-tree=/Users/Nathan/Annex\",\"commit-tree\",\"4b825dc642cb6eb9a060e54bf8d69288fbee4904\"] exited 128) @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5)
-
-
-So I did what it asked and now it's working. Thanks for your help!
-"""]]
diff --git a/doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9.mdwn b/doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9.mdwn
deleted file mode 100644
index 76f53fe10..000000000
--- a/doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-### Please describe the problem.
-
-I can't seem to add the rsync.net remote on an OS X 10.9 machine running git-annex assistant version 5.20140128-g0ac94c3. The process complains about a missing `/usr/libexec/ssh-askpass` in the logs, and after a few retries rsync.net locks me out. This program doesn't exist on my system.
-
-### What steps will reproduce the problem?
-
-1. Click "Add another repository"
-2. Pick rsync.net
-3. Enter the credentials I got in the email from rsync.net
-4. Click "Use this rsync repository"
-
-The resulting logs will state that `/usr/libexec/ssh-askpass` can't be found.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex assistant version 5.20140128-g0ac94c3 on OS X 10.9.1.
-
-### Please provide any additional information below.
-
-I think I have found a workaround in creating that program as a shell script which echoes my password to stdout, but can't test right now because rsync.net have wisely ratelimited my password login attempts. (-:
-
-I'll update this page if I can confirm the workaround works.
-
-(I fully intend to roll that password as soon as I'm in, so no worries about a stale password falling into evildoers' hands.)
-
-> [[done]]; the webapp now handles ssh password prompting. --[[Joey]]
diff --git a/doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9/comment_1_91a961cfa5dd4d6f0e4abfbbcfb81e92._comment b/doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9/comment_1_91a961cfa5dd4d6f0e4abfbbcfb81e92._comment
deleted file mode 100644
index 7ab46c3bb..000000000
--- a/doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9/comment_1_91a961cfa5dd4d6f0e4abfbbcfb81e92._comment
+++ /dev/null
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl7Tgnd2BBdIXVlNKjG4dkTj3paf7FHeHQ"
- nickname="Andreas"
- subject="ssh-askpass workaround does work"
- date="2014-02-01T06:28:41Z"
- content="""
-I've just gotten my rsync.net account unwedged, and can confirm that the ssh-askpass hack does work. After what seemed like git-annex successfully uploading an ssh keypair to the rsync.net remote, I removed the ssh-askpass stub script and rolled my rsync.net password. Now, I'm getting these log entries:
-
-```
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-Received disconnect from 69.43.165.5: 2: Too many authentication failures for 40407
-rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-42/rsync/io.c(452) [sender=2.6.9]
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-Permission denied, please try again.
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-Received disconnect from 69.43.165.5: 2: Too many authentication failures for 40407
-rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-42/rsync/io.c(452) [sender=2.6.9]
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-Permission denied, please try again.
-ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
-Received disconnect from 69.43.165.5: 2: Too many authentication failures for 40407
-rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-42/rsync/io.c(452) [sender=2.6.9]
-```
-
-Looks like git-annex asks for the password for some reason? I'm not sure what's going on here, please advise.
-"""]]
diff --git a/doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9/comment_2_0b5266e31fe7014bd11ea164f8e4744e._comment b/doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9/comment_2_0b5266e31fe7014bd11ea164f8e4744e._comment
deleted file mode 100644
index 7792d2396..000000000
--- a/doc/bugs/Can__39__t_set_up_rsync.net_repo_on_OS_X_10.9/comment_2_0b5266e31fe7014bd11ea164f8e4744e._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="71.80.94.56"
- subject="comment 2"
- date="2014-02-07T19:21:21Z"
- content="""
-git-annex does not run ssh-askpass. But your ssh program may try to do so, if git-annex is started without a controlling terminal. So a workaround is to start git-annex from a terminal window and then password prompts will happen there.
-
-[[design/assistant/sshpassword]] is on the roadmap to fix this so git-annex overrides ssh's password prompting, which seems to be broken on a number of systems.
-
-I don't know why it would continue prompting for a ssh password if git-annex successfully set up a ssh keypair for rsync.net. My guess is that it failed to do so.
-"""]]
diff --git a/doc/bugs/Can__39__t_start_it_on_Debian_Wheezy.mdwn b/doc/bugs/Can__39__t_start_it_on_Debian_Wheezy.mdwn
deleted file mode 100644
index a7e7613d5..000000000
--- a/doc/bugs/Can__39__t_start_it_on_Debian_Wheezy.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-### Please describe the problem.
-After install I dont get any link to start the program even though can start it from terminal.
-
-### What steps will reproduce the problem?
-$ sudo apt-get install git-annex
---->After install...
-$ git annex assistant
-$ git annex webapp
---->Seems like syntax of the command is not correct, I get the help to write the command correctly.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 3.20120629
-Debian Wheezy 64bits XFCE
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-I don't know where is that log
-
-# End of transcript or log.
-"""]]
-
-> Wheezy was released before git-annex had the webapp. If you want it,
-> install the backport. [[done]] --[[Joey]]
diff --git a/doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared.mdwn b/doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared.mdwn
deleted file mode 100644
index 31f37f6e5..000000000
--- a/doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared.mdwn
+++ /dev/null
@@ -1,54 +0,0 @@
-I'm trying to transfer 3 files to my rsync.net remote. It was set up a few months ago with encryption=shared.
-
-Here's what I get:
-
-    % LC_ALL=C git annex copy --to rsn 2012-11-26*
-    copy 2012-11-26 1.jpg (gpg) (checking rsn...) (to rsn...) gpg: no valid OpenPGP data found.
-    gpg: decrypt_message failed: Unknown system error
-    failed
-    copy 2012-11-26 2.jpg (checking rsn...) (to rsn...) gpg: no valid OpenPGP data found.
-    gpg: decrypt_message failed: Unknown system error
-    failed
-    copy 2012-11-26 3.jpg (checking rsn...) (to rsn...) gpg: no valid OpenPGP data found.
-    gpg: decrypt_message failed: Unknown system error
-    failed
-    git-annex: copy: 3 failed
-
-
-Here's the output with `--debug`:
-
-    % LC_ALL=C git annex --debug copy --to rsn 2012-11-26*
-    [2012-11-27 18:28:22 CET] read: git ["--git-dir=/home/schnouki/Photos/.git","--work-tree=/home/schnouki/Photos","show-ref","git-annex"]
-    [2012-11-27 18:28:22 CET] read: git ["--git-dir=/home/schnouki/Photos/.git","--work-tree=/home/schnouki/Photos","show-ref","--hash","refs/heads/git-annex"]
-    [2012-11-27 18:28:22 CET] read: git ["--git-dir=/home/schnouki/Photos/.git","--work-tree=/home/schnouki/Photos","log","refs/heads/git-annex..0164d6150fcd56e035926c72c9a519114735d2a1","--oneline","-n1"]
-    [2012-11-27 18:28:22 CET] read: git ["--git-dir=/home/schnouki/Photos/.git","--work-tree=/home/schnouki/Photos","log","refs/heads/git-annex..04bb9b87872200d5712b17463fc81d4de27b9acf","--oneline","-n1"]
-    [2012-11-27 18:28:22 CET] read: git ["--git-dir=/home/schnouki/Photos/.git","--work-tree=/home/schnouki/Photos","log","refs/heads/git-annex..59c38c176971cd6323817e568f4c32305ba708b0","--oneline","-n1"]
-    [2012-11-27 18:28:22 CET] chat: git ["--git-dir=/home/schnouki/Photos/.git","--work-tree=/home/schnouki/Photos","cat-file","--batch"]
-    [2012-11-27 18:28:22 CET] read: git ["--git-dir=/home/schnouki/Photos/.git","--work-tree=/home/schnouki/Photos","ls-files","--cached","-z","--","2012-11-26 1.jpg","2012-11-26 2.jpg","2012-11-26 3.jpg"]
-    copy 2012-11-26 1.jpg (gpg) (checking rsn...) [2012-11-27 18:28:22 CET] read: rsync ["rsn:photos/123/3a1/GPGHMACSHA1--4f4b2440da1f41aa42a590dc558fbfff39e44b5e/GPGHMACSHA1--4f4b2440da1f41aa42a590dc558fbfff39e44b5e"]
-    [2012-11-27 18:28:22 CET] read: rsync ["rsn:photos/jg/8p/GPGHMACSHA1--4f4b2440da1f41aa42a590dc558fbfff39e44b5e/GPGHMACSHA1--4f4b2440da1f41aa42a590dc558fbfff39e44b5e"]
-    (to rsn...) [2012-11-27 18:28:22 CET] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--passphrase-fd","11","--decrypt"]
-    gpg: no valid OpenPGP data found.
-    gpg: decrypt_message failed: Unknown system error
-    failed
-    copy 2012-11-26 2.jpg (checking rsn...) [2012-11-27 18:28:22 CET] read: rsync ["rsn:photos/61b/da7/GPGHMACSHA1--9c17b4b7414b830a0e7b86cbe08afd1e0878bdbd/GPGHMACSHA1--9c17b4b7414b830a0e7b86cbe08afd1e0878bdbd"]
-    [2012-11-27 18:28:23 CET] read: rsync ["rsn:photos/Z1/9V/GPGHMACSHA1--9c17b4b7414b830a0e7b86cbe08afd1e0878bdbd/GPGHMACSHA1--9c17b4b7414b830a0e7b86cbe08afd1e0878bdbd"]
-    (to rsn...) [2012-11-27 18:28:23 CET] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--passphrase-fd","10","--decrypt"]
-    gpg: no valid OpenPGP data found.
-    gpg: decrypt_message failed: Unknown system error
-    failed
-    copy 2012-11-26 3.jpg (checking rsn...) [2012-11-27 18:28:23 CET] read: rsync ["rsn:photos/340/2ec/GPGHMACSHA1--ce18f116ae33176c8387cecf9d62b0e694501a6e/GPGHMACSHA1--ce18f116ae33176c8387cecf9d62b0e694501a6e"]
-    [2012-11-27 18:28:23 CET] read: rsync ["rsn:photos/8f/V0/GPGHMACSHA1--ce18f116ae33176c8387cecf9d62b0e694501a6e/GPGHMACSHA1--ce18f116ae33176c8387cecf9d62b0e694501a6e"]
-    (to rsn...) [2012-11-27 18:28:23 CET] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--passphrase-fd","12","--decrypt"]
-    gpg: no valid OpenPGP data found.
-    gpg: decrypt_message failed: Unknown system error
-    failed
-    git-annex: copy: 3 failed
-
-I'm using git-annex 3.20121127. I think I was able to transfer files to that remote with the previous release.
-
-Any idea how to fix this? Am I doing something wrong?
-
-> Damn. This was a completely stupid bug, calling "decrypt" where it was
-> supposed to call "encrypt". [[done]] in git; I'll have to
-> make a new release to fix this. --[[Joey]]
diff --git a/doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared/comment_1_ca7ec2041bbec330476fb040b1e66a92._comment b/doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared/comment_1_ca7ec2041bbec330476fb040b1e66a92._comment
deleted file mode 100644
index 36061bac2..000000000
--- a/doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared/comment_1_ca7ec2041bbec330476fb040b1e66a92._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://schnouki.net/"
- nickname="Schnouki"
- subject="comment 1"
- date="2012-11-27T17:39:38Z"
- content="""
-Downgraded to 3.20121112 and the transfer went fine. In both cases I used the [prebuilt tarball](http://downloads.kitenet.net/git-annex/linux/). So it must be a regression in the current release.
-"""]]
diff --git a/doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared/comment_2_c476847665a5320214721497d8fad15b._comment b/doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared/comment_2_c476847665a5320214721497d8fad15b._comment
deleted file mode 100644
index def9d19c8..000000000
--- a/doc/bugs/Can__39__t_transfer_files_to_rsync_remote_with_encryption__61__shared/comment_2_c476847665a5320214721497d8fad15b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://schnouki.net/"
- nickname="Schnouki"
- subject="comment 2"
- date="2012-11-27T22:33:54Z"
- content="""
-Thanks for the quick fix! :)
-"""]]
diff --git a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1.mdwn b/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1.mdwn
deleted file mode 100644
index f4ae47b32..000000000
--- a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-What steps will reproduce the problem?
-
-cabal install git-annex
-
-What is the expected output? What do you see instead?
-
-I get this:
-
-    Assistant/WebApp/Configurators/Local.hs:55:11:
-    `fieldEnctype' is not a (visible) field of constructor `Field'
-
-What version of git-annex are you using? On what operating system?
-
-20121127
-
-Please provide any additional information below.
-
-> [[done]]; see comments. --[[Joey]] 
diff --git a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_1_b25859c159d62f2e92b92f505535131b._comment b/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_1_b25859c159d62f2e92b92f505535131b._comment
deleted file mode 100644
index f01f4382a..000000000
--- a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_1_b25859c159d62f2e92b92f505535131b._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmLB39PC89rfGaA8SwrsnB6tbumezj-aC0"
- nickname="Tobias"
- subject="comment 1"
- date="2012-11-27T15:48:33Z"
- content="""
-I was told to my yesod was too old.
-
-Either upgrade yesod with cabal (After a \"cabal install yesod\" it worked on one of my computers, still failing on the other...)
-
-Or use the Makefile (failed on both the computers i tested).
-
-
-"""]]
diff --git a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_2_4c9eab9120718457fdc1ae9051e44bca._comment b/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_2_4c9eab9120718457fdc1ae9051e44bca._comment
deleted file mode 100644
index cca43f63e..000000000
--- a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_2_4c9eab9120718457fdc1ae9051e44bca._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmLB39PC89rfGaA8SwrsnB6tbumezj-aC0"
- nickname="Tobias"
- subject="comment 2"
- date="2012-11-27T16:03:06Z"
- content="""
-For reference here is a run of:
-
-cabal install yesod --force-reinstalls ; make
-
-http://pastebin.com/3Tr5BA0u
-
-Tried adding -DWITH_OLD_YESOD to the FEATURES in Makefile and got this after a \"make clean; make\":
-
-http://pastebin.com/GV84YgjZ
-"""]]
diff --git a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_3_61aec9801e1f76db4a286536ffacc3ed._comment b/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_3_61aec9801e1f76db4a286536ffacc3ed._comment
deleted file mode 100644
index 32cdf6676..000000000
--- a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_3_61aec9801e1f76db4a286536ffacc3ed._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmLB39PC89rfGaA8SwrsnB6tbumezj-aC0"
- nickname="Tobias"
- subject="comment 3"
- date="2012-11-27T16:06:22Z"
- content="""
-For the machine that could compile and install the latest git-annex after updating yesod. \"make\" still fails.
-
-The first run here is without -DWITH_OLD_YESOD, the second is with.
-
-http://pastebin.com/T3RpPTX
-"""]]
diff --git a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_4_6381ff0ea419831d9bbed27511cad1e9._comment b/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_4_6381ff0ea419831d9bbed27511cad1e9._comment
deleted file mode 100644
index fb58e28ce..000000000
--- a/doc/bugs/Cannot_build_the_latest_with_GHC_7.6.1/comment_4_6381ff0ea419831d9bbed27511cad1e9._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmLB39PC89rfGaA8SwrsnB6tbumezj-aC0"
- nickname="Tobias"
- subject="comment 4"
- date="2012-11-27T16:10:31Z"
- content="""
-cabal install yesod --force-reinstalls
-
-Then \"cabal configure, cabal build\" worked on my secondary machine...
-
-Woohooo, i have the latest git-annex running on both my machines now. Though neither can compile using the Makefile.
-
-Sorry for the spam here, just hoping it will help someone else jump through less hoops.
-
-
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote.mdwn b/doc/bugs/Cannot_copy_to_a_git-annex_remote.mdwn
deleted file mode 100644
index c9e0309b8..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-What steps will reproduce the problem?
-
-I really have no way to reproduce.  I have these two annex repository, both living on CentOS 6.3 machines, using SSH to copy from one to the other.  Everything has always worked fine, and I've copied hundreds of gigabytes and tens of thousands of files so far without a problem.
-
-What is the expected output? What do you see instead?
-
-I do "git copy --to storage FILE" and it says "Copying FILE... failed".  That's it.
-
-How do I fix things so that I can copy again?  Nothing that I tried had any effect on the problem.
-
-Thanks!
-
-> Thanks to Jim's smart correlation of this with another bug, I've fixed
-> them both. [[done]] --[[Joey]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_258a376cff4c62bc4be919322bb1bd88._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_258a376cff4c62bc4be919322bb1bd88._comment
deleted file mode 100644
index 5150d9611..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_258a376cff4c62bc4be919322bb1bd88._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 10"
- date="2013-03-19T00:14:59Z"
- content="""
-Comment 7 was misplaced. Apologies.
-
-Hint for stracing: If you strace \"git-annex\" instead of \"git annex\", you don't need to strace -f, which keeps it a lot simpler.
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_d9b830a1fdea8760cb7da1d36b3cd34d._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_d9b830a1fdea8760cb7da1d36b3cd34d._comment
deleted file mode 100644
index 5fb3fe8ea..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_10_d9b830a1fdea8760cb7da1d36b3cd34d._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck"
- nickname="Jim"
- subject="Same bug"
- date="2013-03-19T13:59:32Z"
- content="""
-Hi,
-
-This looks like the exact same issue as [get failed, but remote has the file](http://git-annex.branchable.com/bugs/get_failed__44___but_remote_has_the_file/).
-I can reproduce your problem here by doing a `git annex copy --to bucket bigfile.gz`, then stopping that transfer with `^Z`, and finally running the `copy` command
-again.  It will fail with the same debug output as you show here.
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_1_09d76e5f9480b9a35644a8f08790cd97._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_1_09d76e5f9480b9a35644a8f08790cd97._comment
deleted file mode 100644
index cb750097c..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_1_09d76e5f9480b9a35644a8f08790cd97._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="enable debugging"
- date="2013-03-18T15:13:53Z"
- content="""
-try
-
-    git-annex --debug copy --to storage FILE
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_2_7b586c705a937d09a1b44bd6af2d4686._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_2_7b586c705a937d09a1b44bd6af2d4686._comment
deleted file mode 100644
index c50bc905c..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_2_7b586c705a937d09a1b44bd6af2d4686._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-03-18T15:15:30Z"
- content="""
-What version of git-annex are you using? Are your repositories using direct mode? What does --debug output?
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_3_07dbd8f64982f1921077e23f468122cf._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_3_07dbd8f64982f1921077e23f468122cf._comment
deleted file mode 100644
index a86c68410..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_3_07dbd8f64982f1921077e23f468122cf._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 3"
- date="2013-03-18T15:32:31Z"
- content="""
-git-annex version on both machines is 4.20130314.  Here is the debug output:
-
-
-    [root@titan BoostPro]# git annex --verbose copy --to storage embt-virtual-machines.tar.xz  
-    copy embt-virtual-machines.tar.xz (checking storage...) (to storage...) failed  
-    git-annex: copy: 1 failed  
-    [root@titan BoostPro]# git annex --debug copy --to storage embt-virtual-machines.tar.xz  
-    [2013-03-18 10:31:33 CDT] read: git [\"--git-dir=/tank/Backups/BoostPro/.git\",\"--work-tree=/tank/Backups/BoostPro\",\"show-ref\",\"git-annex\"]  
-    [2013-03-18 10:31:33 CDT] read: git [\"--git-dir=/tank/Backups/BoostPro/.git\",\"--work-tree=/tank/Backups/BoostPro\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]  
-    [2013-03-18 10:31:33 CDT] read: git [\"--git-dir=/tank/Backups/BoostPro/.git\",\"--work-tree=/tank/Backups/BoostPro\",\"log\",\"refs/heads/git-annex..de30985dc380b49f50ae82046934457177b8d273\",\"--oneline\",\"-n1\"]  
-    [2013-03-18 10:31:33 CDT] read: git [\"--git-dir=/tank/Backups/BoostPro/.git\",\"--work-tree=/tank/Backups/BoostPro\",\"log\",\"refs/heads/git-annex..678538248a63e4d4da706a4b703938f6b8e58657\",\"--oneline\",\"-n1\"]  
-    [2013-03-18 10:31:33 CDT] read: git [\"--git-dir=/tank/Backups/BoostPro/.git\",\"--work-tree=/tank/Backups/BoostPro\",\"log\",\"refs/heads/git-annex..12346a2c23771268e2af5bfa3f813db172493354\",\"--oneline\",\"-n1\"]  
-    [2013-03-18 10:31:33 CDT] chat: git [\"--git-dir=/tank/Backups/BoostPro/.git\",\"--work-tree=/tank/Backups/BoostPro\",\"cat-file\",\"--batch\"]  
-    [2013-03-18 10:31:33 CDT] read: git [\"--git-dir=/tank/Backups/BoostPro/.git\",\"--work-tree=/tank/Backups/BoostPro\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"embt-virtual-machines.tar.xz\"]  
-    copy embt-virtual-machines.tar.xz (checking storage...) [2013-03-18 10:31:33 CDT] call: ssh [\"-T\",\"storage\",\"git-annex-shell 'inannex' '/tank/Backups/BoostPro' 'SHA256E-s51189502084--ad50567a43f10210e7cdae49f91dbfcc449b7f0629795da1fc268993ff59319b.tar.xz' --uuid ad6ef11f-ecad-48d5-af7c-43f8197ac124\"]  
-    (to storage...) failed  
-    git-annex: copy: 1 failed  
-
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_4_926fd494f0b27103a99083cd5d0702d5._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_4_926fd494f0b27103a99083cd5d0702d5._comment
deleted file mode 100644
index f33feffca..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_4_926fd494f0b27103a99083cd5d0702d5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 4"
- date="2013-03-18T16:44:42Z"
- content="""
-Oh, and neither repository is in direct mode.
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_5_80444a509cc340f5eb3cd08b193fd389._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_5_80444a509cc340f5eb3cd08b193fd389._comment
deleted file mode 100644
index ecc4a93e1..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_5_80444a509cc340f5eb3cd08b193fd389._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-03-18T17:23:56Z"
- content="""
-Does this only happen with one file, or with all files?
-
-I think you will need to strace git-annex to determine what the problem is. I cannot see how this could happen in indirect mode.
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_6_4c6b99cd67b4aa742da5101fb1b379f7._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_6_4c6b99cd67b4aa742da5101fb1b379f7._comment
deleted file mode 100644
index 977eed926..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_6_4c6b99cd67b4aa742da5101fb1b379f7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 6"
- date="2013-03-18T18:42:14Z"
- content="""
-It only happens with this one file, because it's the last file to be copied to the remote repository.
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_8_f45cdd2b6acc5f458b67539fced0e529._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_8_f45cdd2b6acc5f458b67539fced0e529._comment
deleted file mode 100644
index 59014a082..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_8_f45cdd2b6acc5f458b67539fced0e529._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 8"
- date="2013-03-18T23:08:06Z"
- content="""
-I don't understand what you're saying about it being the last file to be copied. This can't be stopping the copy from processing files after the one it fails on, and the order of the file in the list of files it's processing cannot be significant, unless you know something I don't know.
-
-What I meant to ask you is whether there is one, particular, specific file on your system that it refuses to copy, or whether it refuses to copy all files, or what.
-
-Anyway, you are going to need to send me a strace, I'm utterly stuck on this.
-"""]]
diff --git a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_9_5a455dd14fb9d3ff408bb3f81e366c38._comment b/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_9_5a455dd14fb9d3ff408bb3f81e366c38._comment
deleted file mode 100644
index 145458120..000000000
--- a/doc/bugs/Cannot_copy_to_a_git-annex_remote/comment_9_5a455dd14fb9d3ff408bb3f81e366c38._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 9"
- date="2013-03-18T23:46:39Z"
- content="""
-I don't quite follow what comment 7 is trying to say, did you intend that to go to another bug report?
-
-As for strace, I'll give it a try tomorrow.
-"""]]
diff --git a/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__.mdwn b/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__.mdwn
deleted file mode 100644
index 4d1154650..000000000
--- a/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-###What steps will reproduce the problem?
-
-Suppose you have two types of folders you want to sync on two machines, e.g. Images and Documents.
-
-I already setup the Documents folders on both machines to sync using local pairing and they sync happily. Now I want to do the same and I execute the same steps again for the Images and I choose to not combine the Documents and Images repositories, but keep them separate.
-
-###What is the expected output? What do you see instead?
-
-The git repositories between both machines should be synced and all files should be transfered sucessfully between them.
-
-Instead the one machine shows a message "Failed to sync with host1_Images" and in the log it says
-
-    [2013-04-15 15:57:22 CEST] PairListener: Syncing with host1_Images 
-    git-annex-shell: Only allowed to access ~/Documents not ~/Images/
-    fatal: The remote end hung up unexpectedly
-    Already up-to-date.
-
-I do not know how to debug this further cause I do not understand where this access-permission is configured.
-
-###What version of git-annex are you using? On what operating system?
-
-Machine 1: Gentoo Linux with Git-annex 4.20130405 from haskell-overlay.
-Machine 2: Ubuntu 12.04 with Git-Annex 4.20130405 installed using cabal.
-
-###Please provide any additional information below.
-
-> [[done]]; when setting up a new repo it will now use
-> a ssh key that is different for each repository on the host.
-> --[[Joey]]
diff --git a/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_1_6f7b5c164ff64f00b8814b2ee334709f._comment b/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_1_6f7b5c164ff64f00b8814b2ee334709f._comment
deleted file mode 100644
index f2a5f1b9d..000000000
--- a/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_1_6f7b5c164ff64f00b8814b2ee334709f._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-16T17:11:36Z"
- content="""
-Yeah, this is indeed a bug. It sets up a locked down ssh key to use for the first repository, and then the second repository sees there is a key for that server already, and does not try to set up a new one.
-
-This is configured in `~/.ssh/authorized_keys` on the server. You will see a key in there with a `GIT_ANNEX_SHELL_DIRECTORY` environment variable specified, which is what prevents it from using other directories. The simplest fix in your situation is to 
-remove that variable, and then that key can be used to access any repository on the server.
-
-What I need to do is include the path to the repository in the ssh key name, for new repositories created by the webapp.
-"""]]
diff --git a/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_2_807ef1250237bf4426e3a24c1f9ba357._comment b/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_2_807ef1250237bf4426e3a24c1f9ba357._comment
deleted file mode 100644
index 625c12fbf..000000000
--- a/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_2_807ef1250237bf4426e3a24c1f9ba357._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~maestro-alubia"
- nickname="maestro-alubia"
- subject="Thanks!"
- date="2013-04-17T22:55:24Z"
- content="""
-Thank you very much for the fast fix! I will try that soon.
-
-I love git-annex, keep up the excellent work :)
-"""]]
diff --git a/doc/bugs/Check_for_minimum_Git_version.mdwn b/doc/bugs/Check_for_minimum_Git_version.mdwn
deleted file mode 100644
index f7eabb2b8..000000000
--- a/doc/bugs/Check_for_minimum_Git_version.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-### Please describe the problem.
-
-git-annex does not check for the minimum version of Git that it requires, and therefore it sometimes uses flags which my installed Git does not recognize.
-This happens when converting some indirect repositories to direct ones on an older server.
-
-### What steps will reproduce the problem?
-
-git annex direct
-
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 5.20131130
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-direct iTunes/iTunes Media/iTunes U/Statistics 110_ Probability/Strategic Practice and Homework 9.pdf ok
-direct iTunes/iTunes Media/iTunes U/Statistics 110_ Probability/Syllabus.pdf ok
-direct  error: unknown switch `B'
-usage: git checkout [options] <branch>
-   or: git checkout [options] [<branch>] -- <file>...
-
-# End of transcript or log.
-"""]]
-
-> git-annex checks the git version at compile time and arranges to use
-> commands that will work with that version of git at run time.
-> 
-> Adding a runtime check for a minimum git version would slow every git-annex
-> command down and so I don't want to do it. It's up to the user to not
-> built git-annex with a new version of git and then try to use it with an
-> old version of git.
-> 
-> `git checkout -B` seems to have been added to git quite a long time ago
-> (2010), in version 1.7.1.1. I've made git-annex check at compile
-> time if being built with such an old version and refuse to build.
-> [[done]]. --[[Joey]]
diff --git a/doc/bugs/Committer_crashed.mdwn b/doc/bugs/Committer_crashed.mdwn
deleted file mode 100644
index caa8b1c50..000000000
--- a/doc/bugs/Committer_crashed.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-# What steps will reproduce the problem?
-
-Editing a text file with vim
-
-#What is the expected output? What do you see instead?
-
-    # On branch master
-    # Changes not staged for commit:
-
-    #   (use "git add <file>..." to update what will be committed)
-    #   (use "git checkout -- <file>..." to discard changes in working directory)
-    #
-    #       typechange: test
-    #
-    # Untracked files:
-    #   (use "git add <file>..." to include in what will be committed)
-    #
-    #       .test.swp
-
-    no changes added to commit (use "git add" and/or "git commit -a")
-
-    /.test.swp still has writers, not adding
-
-    Committer crashed: ./test~: createLink: does not exist (No such file or directory)
-
-# What version of git-annex are you using? On what operating system?
-
-3.20130107 prebuilt tar ball on Debian testing
-
-> Could also fail in `getFileStatus`. In either case it's a race
-> with the file being deleted while it's still in the process of being
-> locked down. Fixed this [[done]] --[[Joey]]
diff --git a/doc/bugs/Compile_needs_more_than_1.5gb_of_memory.mdwn b/doc/bugs/Compile_needs_more_than_1.5gb_of_memory.mdwn
deleted file mode 100644
index 4fa9648c1..000000000
--- a/doc/bugs/Compile_needs_more_than_1.5gb_of_memory.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-What steps will reproduce the problem?
-
-> cabal install git-annex
-
-What is the expected output? What do you see instead?
-
-> I would expect a working git-annex on my little linode. I have a linode 768 and trouble building the latest version. The process get's killed because of an out of memory condition.
-
-What version of git-annex are you using? On what operating system?
-
-> git-annex version: 4.20130314
-> Ubuntu 12.04
-
-Please provide any additional information below.
-
-[[done]]
diff --git a/doc/bugs/Compile_needs_more_than_1.5gb_of_memory/comment_1_0806b5132c55d7a5a17fbdad7e3f2291._comment b/doc/bugs/Compile_needs_more_than_1.5gb_of_memory/comment_1_0806b5132c55d7a5a17fbdad7e3f2291._comment
deleted file mode 100644
index bc0853763..000000000
--- a/doc/bugs/Compile_needs_more_than_1.5gb_of_memory/comment_1_0806b5132c55d7a5a17fbdad7e3f2291._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-15T21:49:49Z"
- content="""
-You don't need a webapp on your linode, probably, so disable it:
-
-cabal install git-annex -f-WebApp
-
-The template haskell in the webapp about doubles the amount of memory needed to compile it.
-
-----
-
-Alternatively, since git-annex compiles down to a self-contained binary, you can build it on another machine of the same architecture, and just copy the binary over. Or there are all kinds of pre-compiled binaries available for Linux distributions that you can use on your linode.
-"""]]
diff --git a/doc/bugs/Complete_failure_trying_to_unannex_a_large_annex.mdwn b/doc/bugs/Complete_failure_trying_to_unannex_a_large_annex.mdwn
deleted file mode 100644
index 5531a1939..000000000
--- a/doc/bugs/Complete_failure_trying_to_unannex_a_large_annex.mdwn
+++ /dev/null
@@ -1,56 +0,0 @@
-I really don't know what's happened here, I just did `git annex unannex .` in a very large annex:
-
-    unannex Inbox/Lolcat.JPG (Recording state in git...)
-    ok
-    unannex Inbox/Lolcat.jpg (Recording state in git...)
-    ok
-    unannex Inbox/May 2012 Photo Stream/120502_0004.JPG (Recording state in git...)
-    ok
-    unannex Inbox/May 2012 Photo Stream/120518_0005.JPG (Recording state in git...)
-    ok
-    unannex Inbox/May 2012 Photo Stream/120523_0006.JPG (Recording state in git...)
-    ok
-    unannex Inbox/May 2012 Photo Stream/120523_0007.JPG (Recording state in git...)
-    ok
-    unannex Inbox/My boyfriend of 7 years and I are both physicists. Here's how he proposed to me. - Imgur.jpg (Recording state in git...)
-    ok
-    unannex Inbox/Nov 2012 Photo Stream/121102_0035.JPG (Recording state in git...)
-    ok
-    unannex Inbox/Nov 2012 Photo Stream/121102_0036.JPG (Recording state in git...)
-    ok
-    unannex Inbox/Nov 2012 Photo Stream/121102_0037.JPG (Recording state in git...)
-    ok
-    unannex Inbox/Nov 2012 Photo Stream/121102_0038.JPG (Recording state in git...)
-    ok
-    unannex Inbox/Nov 2012 Photo Stream/121102_0039.JPG (Recording state in git...)
-    ok
-    unannex Inbox/Nov 2012 Photo Stream/121103_0040.JPG (Recording state in git...)
-    ok
-    unannex Inbox/Nov 2012 Photo Stream/121104_0041.JPG (Recording state in git...)
-    ok
-    unannex Inbox/Nov 2012 Photo Stream/121105_0042.JPG (Recording state in git...)
-    error: bad index file sha1 signature
-    fatal: index file corrupt
-    git-annex: failed to read sha from git write-tree
-    git-annex: git commit [Param "-q",Params "-m",Param "content removed from git annex",Param "--",File "Inbox/Nov 2012 Photo Stream/121105_0042.JPG"] failed
-    Vulcan:~/Pictures $ ga unannex .
-    unannex Inbox/Nov 2012 Photo Stream/121109_0043.JPG error: bad index file sha1 signature
-    fatal: index file corrupt
-
-    git-annex: fd:12: hClose: resource vanished (Broken pipe)
-    failed
-    git-annex: pre-commit: 1 failed
-    git-annex: git commit [Param "-q",Params "-m",Param "content removed from git annex",Param "--",File "Inbox/Nov 2012 Photo Stream/121109_0043.JPG"] failed
-    Vulcan:~/Pictures $ ga -F unannex .
-    unannex Inbox/Nov 2012 Photo Stream/121124_0044.JPG error: bad index file sha1 signature
-    fatal: index file corrupt
-
-    git-annex: fd:12: hClose: resource vanished (Broken pipe)
-    failed
-    git-annex: pre-commit: 1 failed
-    git-annex: git commit [Param "-q",Params "-m",Param "content removed from git annex",Param "--",File "Inbox/Nov 2012 Photo Stream/121124_0044.JPG"] failed
-
-I guess now I'll just try to unlink the symlinks by hand, and drop the `.git` directory?
-
-> [[done]]; per my comment this seems like a corrupt git repository.
-> --[[Joey]]
diff --git a/doc/bugs/Complete_failure_trying_to_unannex_a_large_annex/comment_1_1c202695ab7fe62cdc8770e1fb428d0c._comment b/doc/bugs/Complete_failure_trying_to_unannex_a_large_annex/comment_1_1c202695ab7fe62cdc8770e1fb428d0c._comment
deleted file mode 100644
index 82acacd75..000000000
--- a/doc/bugs/Complete_failure_trying_to_unannex_a_large_annex/comment_1_1c202695ab7fe62cdc8770e1fb428d0c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-08T19:02:54Z"
- content="""
-You seem to have a corrupt .git/index file, or .git/annex/index, or maybe a whole corrupt git repository. I'm not sure. I'd start by running `git fsck`, and if that's ok, remove `.git/annex/index` and `.git/annex/index.lck`. git-annex will recover from that automatically. If that still doesn't help, you might need to delete .git/index and do some reset to get it back.
-
-I don't see much evidence of an actual bug here, just bad data that is somehow on disk.
-"""]]
diff --git a/doc/bugs/Conflicting_archive_descriptions.mdwn b/doc/bugs/Conflicting_archive_descriptions.mdwn
deleted file mode 100644
index 832daa4ea..000000000
--- a/doc/bugs/Conflicting_archive_descriptions.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-This is confusing:
-
-"Next we come to the archive repositories.The archive repositories coordinate together, so that each file is archived in only one place. **When you move files into a folder named "archive"**, they'll be moved to an archive repository, and removed from all your client repositories. This is handy if you have old files you don't need anymore, but want to keep archived for later. When you copy or move a file out of an "archive" folder, it'll be retrieved from the archive repository."
-
-"The small archive repositories are like other archive repositories, but smaller. While archive repositories normally accumulate every file they can, small archive repositories only accumulate files **once you put them in an "archive" directory.**"
-
-Based upon those descriptions, I don't know what the difference is.
-
-> Improved wording to not imply that files are only put into archive
-> repositories once the files are moved to archive directories.
-> (Which is how small archive repositories work.)
-> 
-> If you're still confused about it, see
-> <http://git-annex.branchable.com/assistant/archival_walkthrough/>
-> 
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/ControlPath_too_long_for_Unix_domain_socket.mdwn b/doc/bugs/ControlPath_too_long_for_Unix_domain_socket.mdwn
deleted file mode 100644
index 9cf453164..000000000
--- a/doc/bugs/ControlPath_too_long_for_Unix_domain_socket.mdwn
+++ /dev/null
@@ -1,53 +0,0 @@
-What steps will reproduce the problem?
-Pairing an existing git annex repository with a fresh repository on another computer in the git-annex webapp
-
-
-What is the expected output? What do you see instead?
-Expected result is that the two machines sync correctly.
-
-What i see are some "ControlPath <data>  too long for unix domain socket" errors from ssh, but the computers do actually sync properly. 
-
-Even though the data is synced properly, either the sender(or both of the clients) don't actually realize this. And the queue circles, all the transfers are being redone constantly(On every start of git-annex webapp on the original repository at least).
-
-
-What version of git-annex are you using? On what operating system?
-Latest git master as of this post. Debian sid and Ubuntu 12.04
-
-
-Please provide any additional information below.
-
-
-stdout snippet from git-annex webapp:
-
-
-    ControlPath "/home/alansmithee/Desktop/annex/.git/annex/ssh/alansmithee@git-annex-debbook.local-alansmithee.dxpXHVCkLhsxvWaH" too long for Unix domain socket
-    SHA256-s51233--0b4c59b3ab03b1ca6d95d4084fa6ff7220cf26695b6e3dd575f78af3dec6b701
-           51233 100%    5.43MB/s    0:00:00 (xfer#1, to-check=0/1)
-
-    sent 30 bytes  received 51385 bytes  102830.00 bytes/sec
-    total size is 51233  speedup is 1.00
-    ok
-    (Recording state in git...)
-
-    ControlPath "/home/alansmithee/Desktop/annex/.git/annex/ssh/alansmithee@git-annex-debbook.local-alansmithee.9ZQwEjraTxi20B6W" too long for Unix domain socket
-    SHA256-s47883982--4b7cbb49506dcdd223a9db7b400cc41fc2e3ebbf5b2b17b75c9334bb949b6754
-        47883982 100%    1.34MB/s    0:00:34 (xfer#1, to-check=0/1)
-
-    sent 30 bytes  received 47889978 bytes  1388116.17 bytes/sec
-    total size is 47883982  speedup is 1.00
-    ok
-    (Recording state in git...)
-
-
-This data appears on both the sending and receiving git-annex stdout. At least for the initial sync. For later syncs it only appears on the sender, though the client system is using a lot of resources.
-
-> I've made git-annex detect if the control path would be too long,
-> and disable ssh connection caching. It also tries a relative path
-> to the file, which tends to make it shorter, and I think would
-> keep ssh connection caching working in your example.
-> 
-> Please test and see if it works, and also if the "looping" problem
-> still happens. --[[Joey]]
-
->> Closing; I'm pretty sure the looping is just transfer retrying, to be
->> expected if they fail. [[done]] --[[Joey]] 
diff --git a/doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_1_60f58e205604eebe668b1e05dcfbf9a7._comment b/doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_1_60f58e205604eebe668b1e05dcfbf9a7._comment
deleted file mode 100644
index 0cba1a693..000000000
--- a/doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_1_60f58e205604eebe668b1e05dcfbf9a7._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.30"
- subject="comment 1"
- date="2012-09-13T22:00:53Z"
- content="""
-You can work around the ControlPath too long by running in your git repo:
-
-git config annex.sshcaching false
-
-While I could reproduce that part of your problem, I did *not* see any data actually be transferred when the ControlPath was too long. For example:
-
-<pre>
-joey@gnu:~/tmp/t/1>git annex transferkey --to foo SHA256E-s29--66ffceb8b7a1af9c2eb896f26fb8f3bdab0a606da59a7a2d71ae4f7d78ad13c4/SHA256E-s29--66ffceb8b7a1af9c2eb896f26fb8f3bdab0a606da59a7a2d71ae4f7d78ad13c4
-
-ControlPath too long
-rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
-
-  rsync failed -- run git annex again to resume file transfer
-failed
-git-annex: transferkey: 1 failed
-</pre>
-"""]]
diff --git a/doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_2_9c0c65389a3b4e7e81b8de96d430a3f1._comment b/doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_2_9c0c65389a3b4e7e81b8de96d430a3f1._comment
deleted file mode 100644
index 9f62af956..000000000
--- a/doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_2_9c0c65389a3b4e7e81b8de96d430a3f1._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmI_rfI0tsu93LcMlAvh5WTXtKFIMkHrJQ"
- nickname="Pawan"
- subject="Long Path Tool"
- date="2014-01-24T10:43:09Z"
- content="""
-Well, you can also use Long Path Tool for such problems, it really works good I will say.
-"""]]
diff --git a/doc/bugs/Could_not_find_module_Data.Default.mdwn b/doc/bugs/Could_not_find_module_Data.Default.mdwn
deleted file mode 100644
index 64202de42..000000000
--- a/doc/bugs/Could_not_find_module_Data.Default.mdwn
+++ /dev/null
@@ -1,33 +0,0 @@
-**What steps will reproduce the problem?**
-
-Manually building git-annex from git.
-
-**What is the expected output? What do you see instead?**
-
-    $ cabal update
-    ...
-    $ cabal install --only-dependencies
-    ...
-    $ cabal configure
-    ...
-    $ cabal build
-    Building git-annex-3.20120826...
-    Preprocessing executable 'git-annex' for git-annex-3.20120826...
-    
-    Utility/Yesod.hs:15:8:
-        Could not find module `Data.Default'
-        It is a member of the hidden package `data-default-0.5.0'.
-        Perhaps you need to add `data-default' to the build-depends in your .cabal file.
-        Use -v to see a list of the files searched for.
-    $
-
-**What version of git-annex are you using? On what operating system?**
-
-commit e7d728672a5fc923be9ab1d6fe4b65f2058b49c7
-Arch Linux
-
-**Please provide any additional information below.**
-
-When I add data-default to git-annex.cabal's Build-Deps it works fine.
-
-> Thanks, [[done]]. --[[Joey]]
diff --git a/doc/bugs/Could_not_resolve_dependencies.mdwn b/doc/bugs/Could_not_resolve_dependencies.mdwn
deleted file mode 100644
index 9eb98f31e..000000000
--- a/doc/bugs/Could_not_resolve_dependencies.mdwn
+++ /dev/null
@@ -1,40 +0,0 @@
-I'm not able to install git-annex with cabal.
-
-What steps will reproduce the problem?
-
-    bbigras@bbigras-VirtualBox:~$ cabal update
-    Downloading the latest package list from hackage.haskell.org
-    bbigras@bbigras-VirtualBox:~$ cabal install git-annex --bindir=$HOME/bin
-    Resolving dependencies...
-    cabal: Could not resolve dependencies:
-    trying: git-annex-3.20130207 (user goal)
-    trying: git-annex-3.20130207:+webdav
-    trying: git-annex-3.20130207:+webapp
-    trying: git-annex-3.20130207:+assistant
-    trying: yesod-1.1.8.2 (dependency of git-annex-3.20130207:+assistant)
-    trying: yesod-auth-1.1.5.2 (dependency of yesod-1.1.8.2)
-    trying: authenticate-1.3.2.4 (dependency of yesod-auth-1.1.5.2)
-    trying: xml-conduit-1.1.0.1 (dependency of authenticate-1.3.2.4)
-    next goal: DAV (dependency of git-annex-3.20130207:+webdav)
-    rejecting: DAV-0.3 (conflict: xml-conduit==1.1.0.1, DAV => xml-conduit>=1.0 &&
-    <=1.1)
-    rejecting: DAV-0.2, 0.1, 0.0.1, 0.0 (conflict: git-annex-3.20130207:webdav =>
-    DAV(>=0.3))
-    bbigras@bbigras-VirtualBox:~$
-
-
-What version of git-annex are you using? On what operating system?
-
-Ubuntu 12.10 x86_64
-
-cabal-install version 0.14.0
-using version 1.14.0 of the Cabal library
-
-> The Haskell DAV library needs to be updated to build with
-> the newer version of xml-conduit. Library skew of this sort 
-> is common when using cabal.
-> 
-> You can work around this by building git-annex without webdav:
-> `cabal configure --flags=-WebDAV`
-> 
-> This is not a git-annex bug. [[done]] --[[Joey]]
diff --git a/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh.mdwn b/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh.mdwn
deleted file mode 100644
index 38f54d2b6..000000000
--- a/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh.mdwn
+++ /dev/null
@@ -1,43 +0,0 @@
-What steps will reproduce the problem?
-
-I create a new annex, added in a bunch of files.
-
-I cloned this annex to another machine, where I already had those files, so I copied them into a directory named "foo", did "git annex add foo", and then did "git rm -r foo", and git commit'd my clone of the annex.
-
-Then I try to "git annex sync" with the remote.
-
-What is the expected output? What do you see instead?
-
-I don't know, I've never used git-annex before.  This is what I get each time:
-
-    Hermes ~/Products/tmp/Movies (master) $ ga sync
-    git-annex-shell: Prelude.(!!): index too large
-
-What version of git-annex are you using? On what operating system?
-
-It's the 'master' as of yesterday: c504f4025fec49e62601fbd4a3cd8f1270c7d221
-
-I'm on OS X 10.8.2, using GHC 7.6.1.  The annex in question has 38G in a few hundred files.
-
-Please provide any additional information below.
-
-I'm willing to help track this down!
-
-> I've got it, October 9th's release 
-> included commit bc649a35bacbecef93e378b1497f6a05b30bf452, which included a
-> change to a `segment` function. It was supposed to be a
-> rewrite in terms of a more general version, but it introduced a bug
-> in what it returned in an edge case and this in turn led git-annex-shell's
-> parameter parser to fail in a code path that was never reachable before.
-> 
-> It'd fail both when a new repo was running `git-annex-shell configlist`,
-> and in `git-annex-shell commit`, although this latter crash was less
-> noticible and I'm sure you saw the former.
-> 
-> Fixed the reversion; fixed insufficient guards around the partial code
-> (which I cannot see a way to entirely eliminate sadly; look at
-> GitAnnexShell.hs's `partitionParams` and weep or let me know if you have 
-> any smart ideas..); added a regression test to check the non-obvious
-> behavior of segment with an empty segment. I'll be releasing a new
-> version with this fix as soon as I have bandwidth, ie tomorrow.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_1_9705f295ad8101f3f0ede18e590b56ef._comment b/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_1_9705f295ad8101f3f0ede18e590b56ef._comment
deleted file mode 100644
index 660b52e7f..000000000
--- a/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_1_9705f295ad8101f3f0ede18e590b56ef._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="I can confirm the fix"
- date="2012-10-16T05:53:15Z"
- content="""
-It's working great now, thanks Joey!
-"""]]
diff --git a/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_2_0d751d81ac618f8d7e3f1dd20c830542._comment b/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_2_0d751d81ac618f8d7e3f1dd20c830542._comment
deleted file mode 100644
index 5622bd6da..000000000
--- a/doc/bugs/Crash_trying_to_sync_with_a_repo_over_ssh/comment_2_0d751d81ac618f8d7e3f1dd20c830542._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.8"
- subject="comment 2"
- date="2012-10-16T05:56:10Z"
- content="""
-And I found a clean way to avoid that partial !! too. :) Down to 22 of the little monsters to clean up now.
-"""]]
diff --git a/doc/bugs/Crash_when_adding_jabber_account_.mdwn b/doc/bugs/Crash_when_adding_jabber_account_.mdwn
deleted file mode 100644
index 678890cad..000000000
--- a/doc/bugs/Crash_when_adding_jabber_account_.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-*What steps will reproduce the problem?*
-
-1. Start git-annex webapp
-2. Configuration
-3. Configure Jabber Account
-4. Insert user and pass
-5. Click "User this account"
-
-Tryed 4 times, all the same.
-
-
-*What is the expected output? What do you see instead?*
-
-On Chrome I get "Error 101 (net::ERR_CONNECTION_RESET): The connection was reset." or "Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data."
-
-On the terminal where git-annex was running I get "Segmentation fault (core dumped)"
-
-
-*What version of git-annex are you using? On what operating system?*
-
-git-annex version: I downloaded 3.20130107 (twice to be sure), but for some reason 'git-annex version' reports 3.20130102 
-
-OS: Ubuntu 12.04.1 LTS 3.2.0-35-generic-pae #55-Ubuntu SMP Wed Dec 5 18:04:39 UTC 2012 i686 i686 i386 GNU/Linux
-
-
-*Please provide any additional information below.*
-
-On dmesg: 
-[45773.212717] git-annex[26779]: segfault at b724e840 ip 09699150 sp b4cfd038 error 7 in git-annex[8048000+1762000]
-
-[[!tag /design/assistant]]
-> [[done]], see comments --[[Joey]] 
diff --git a/doc/bugs/Crash_when_adding_jabber_account_/comment_1_2dc61ebcfa8919fb839656999c155c52._comment b/doc/bugs/Crash_when_adding_jabber_account_/comment_1_2dc61ebcfa8919fb839656999c155c52._comment
deleted file mode 100644
index c32ee75de..000000000
--- a/doc/bugs/Crash_when_adding_jabber_account_/comment_1_2dc61ebcfa8919fb839656999c155c52._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 1"
- date="2013-01-14T16:39:00Z"
- content="""
-Are you using the 64 bit or the 32 bit build? Did you download the standalone tarball? How are you running git-annex exactly? (Using runshell, or by hand?)
-
-A segfault here seems likely to involve the Haskell GNUTLS binding. At least, the only other time git-annex has segfaulted, which also involved jabber, it was a bug in the GNUTLS binding.
-"""]]
diff --git a/doc/bugs/Crash_when_adding_jabber_account_/comment_2_e49af3b8a937d82eda1509b6f67b21d4._comment b/doc/bugs/Crash_when_adding_jabber_account_/comment_2_e49af3b8a937d82eda1509b6f67b21d4._comment
deleted file mode 100644
index 03f7a2069..000000000
--- a/doc/bugs/Crash_when_adding_jabber_account_/comment_2_e49af3b8a937d82eda1509b6f67b21d4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn-4QWOFI0QQ4n-yu-oFq3PHeuSPUv_-b4"
- nickname="Rodrigo"
- subject="comment 2"
- date="2013-01-14T22:10:44Z"
- content="""
-32 bit. Yes, the standalone tarball. From terminal, I'm simply running: git-annex webapp
-"""]]
diff --git a/doc/bugs/Crash_when_adding_jabber_account_/comment_3_e59f8813bf1a7c4e3c8c120fe82348b9._comment b/doc/bugs/Crash_when_adding_jabber_account_/comment_3_e59f8813bf1a7c4e3c8c120fe82348b9._comment
deleted file mode 100644
index 763f6fe53..000000000
--- a/doc/bugs/Crash_when_adding_jabber_account_/comment_3_e59f8813bf1a7c4e3c8c120fe82348b9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-03-18T23:42:55Z"
- content="""
-I tried to reproduce this with the standalone i386 tarball for 4.20130314. Was able to add a jabber account using my google talk account with no crash.
-
-Given the age of this bug report, I'm just going to close it. But if you still see it with the current verison, please let me know! (And I guess you'd have to tell me which jabber server you're using then..)
-"""]]
diff --git a/doc/bugs/Crash_when_adding_jabber_account_/comment_4_716ac138cb69eecd0fb586699b4aeb2a._comment b/doc/bugs/Crash_when_adding_jabber_account_/comment_4_716ac138cb69eecd0fb586699b4aeb2a._comment
deleted file mode 100644
index 9039faca5..000000000
--- a/doc/bugs/Crash_when_adding_jabber_account_/comment_4_716ac138cb69eecd0fb586699b4aeb2a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmu416zAYgYzbXVZAe30MiXoOWO4z6nGX8"
- nickname="Johannes"
- subject="signal 11"
- date="2013-04-03T15:13:05Z"
- content="""
-I'm getting a \"error: git-annex died of signal 11\" when trying to add a self-hosted jabber account. I'm using ejabberd and a self-signed SSL certificate.
-"""]]
diff --git a/doc/bugs/Crash_when_adding_jabber_account_/comment_5_9bfd8df548d5866599dfc69fb3aaf94a._comment b/doc/bugs/Crash_when_adding_jabber_account_/comment_5_9bfd8df548d5866599dfc69fb3aaf94a._comment
deleted file mode 100644
index 40bc68dcb..000000000
--- a/doc/bugs/Crash_when_adding_jabber_account_/comment_5_9bfd8df548d5866599dfc69fb3aaf94a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlm_3m5gLhML9bHbZ8FpJ-HBZhWaRfFeO8"
- nickname="Corey"
- subject="I got this error too."
- date="2014-02-25T17:23:33Z"
- content="""
-With the armel tarbell downloaded 2014-02-21 on an Ubuntu (precise) chroot running on a Chromebook.
-"""]]
diff --git a/doc/bugs/Creating_a_box.com_repository_fails.mdwn b/doc/bugs/Creating_a_box.com_repository_fails.mdwn
deleted file mode 100644
index ecebd7a00..000000000
--- a/doc/bugs/Creating_a_box.com_repository_fails.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-### Please describe the problem.
-
-Adding a repository on box.com, using the assistant, fails with an error message (as seen in the log below).
-
-### What steps will reproduce the problem?
-
-Start up the assistant. Create a new empty repository. Enable consistency checking as suggested. Click add another repository, select box.com, fill in your credentials, keep shared ticked and encrypt all selected, click add repository. Error message appears.
-
-
-### What version of git-annex are you using? On what operating system?
-
-5.20140117.1 from ppa of François Marier
-
-ubuntu 13.10 (saucy), i686
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[2014-01-26 20:40:10 CET] main: starting assistant version 5.20140117.1
-[2014-01-26 20:40:10 CET] Cronner: You should enable consistency checking to protect your data. 
-(Recording state in git...)
-(scanning...) [2014-01-26 20:40:10 CET] Watcher: Performing startup scan
-(started...) [2014-01-26 20:41:10 CET] Cronner: Consistency check in progress
-
-(Recording state in git...)
-(encryption setup) (shared cipher) (testing WebDAV server...)
-26/Jan/2014:20:41:24 +0100 [Error#yesod-core] InternalIOException <socket: 32>: hPutBuf: illegal operation (handle is closed) @(yesod-core-1.2.3:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:471:5)
-
-# End of transcript or log.
-"""]]
-
-> Seems that [DAV-0.6 is badly broken](http://bugs.debian.org/737902).
-> I have adjusted the cabal file to refuse to build with that broken
-> version.
-> 
->> Update: Had to work around additional breakage in DAV-0.6. It's
->> fully tested and working now, although not yet uploaded to Debian
->> unstable. [[done]] --[[Joey]]
diff --git a/doc/bugs/Creating_a_box.com_repository_fails/comment_1_c0b4855b65cb7052daf6538c2ad73e99._comment b/doc/bugs/Creating_a_box.com_repository_fails/comment_1_c0b4855b65cb7052daf6538c2ad73e99._comment
deleted file mode 100644
index 0aee0102a..000000000
--- a/doc/bugs/Creating_a_box.com_repository_fails/comment_1_c0b4855b65cb7052daf6538c2ad73e99._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8"
- nickname="Jon Ander"
- subject="comment 1"
- date="2014-02-02T16:48:37Z"
- content="""
-I'm also experiencing a similar issue, I get this error when I try to upload a file to Box.com:
-
-    git annex copy my_file --to box.com
-    copy my_file (gpg) (checking box.com...) git-annex: InternalIOException <socket: 10>: hPutBuf: illegal operation (handle is closed)
-"""]]
diff --git a/doc/bugs/Creating_a_box.com_repository_fails/comment_2_b05a1e7b37989c698353cc6b3fd02d7c._comment b/doc/bugs/Creating_a_box.com_repository_fails/comment_2_b05a1e7b37989c698353cc6b3fd02d7c._comment
deleted file mode 100644
index c278ced96..000000000
--- a/doc/bugs/Creating_a_box.com_repository_fails/comment_2_b05a1e7b37989c698353cc6b3fd02d7c._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8"
- nickname="Jon Ander"
- subject="comment 2"
- date="2014-02-03T11:31:48Z"
- content="""
-I have more information on the issue. I have another computer synced with my main one, but with Box.com disabled. When trying to enable it now I get the following error:
-
-    StatusCodeException (Status {statusCode = 404, statusMessage = \"Not Found\"}) [(\"Server\",\"nginx\"),(\"Date\",\"Mon, 03 Feb 2014 11:29:17 GMT\"),(\"Content-Type\",\"text/html; charset=UTF-8\"),(\"Content-Length\",\"0\"),(\"Connection\",\"keep-alive\"),(\"X-Robots-Tag\",\"noindex, nofollow\"),(\"Set-Cookie\",\"box_visitor_id=52ef7d8cf20e56.10269052; expires=Tue, 03-Feb-2015 11:29:16 GMT; path=/; domain=.box.com\"),(\"Set-Cookie\",\"bv=OPS-35591; expires=Mon, 10-Feb-2014 11:29:16 GMT; path=/; domain=.box.com\"),(\"Set-Cookie\",\"cn=11; expires=Mon, 10-Feb-2014 11:29:16 GMT; path=/; domain=.box.com\"),(\"Set-Cookie\",\"presentation=desktop; path=/; domain=.box.com\"),(\"Set-Cookie\",\"box_locale=es_ES; expires=Thu, 03-Apr-2014 10:29:17 GMT; path=/; domain=.box.com\"),(\"X-Response-Body-Start\",\"\")] (CJ {expose = [Cookie {cookie_name = \"box_locale\", cookie_value = \"es_ES\", cookie_expiry_time = 2014-04-03 10:29:17 UTC, cookie_domain = \"box.com\", cookie_path = \"/\", cookie_creation_time = 2014-02-03 11:29:17.202283 UTC, cookie_last_access_time = 2014-02-03 11:29:17.202283 UTC, cookie_persistent = True, cookie_host_only = False, cookie_secure_only = False, cookie_http_only = False},Cookie {cookie_name = \"presentation\", cookie_value = \"desktop\", cookie_expiry_time = 3013-06-06 00:00:00 UTC, cookie_domain = \"box.com\", cookie_path = \"/\", cookie_creation_time = 2014-02-03 11:29:17.202283 UTC, cookie_last_access_time = 2014-02-03 11:29:17.202283 UTC, cookie_persistent = False, cookie_host_only = False, cookie_secure_only = False, cookie_http_only = False},Cookie {cookie_name = \"cn\", cookie_value = \"11\", cookie_expiry_time = 2014-02-10 11:29:16 UTC, cookie_domain = \"box.com\", cookie_path = \"/\", cookie_creation_time = 2014-02-03 11:29:17.202283 UTC, cookie_last_access_time = 2014-02-03 11:29:17.202283 UTC, cookie_persistent = True, cookie_host_only = False, cookie_secure_only = False, cookie_http_only = False},Cookie {cookie_name = \"bv\", cookie_value = \"OPS-35591\", cookie_expiry_time = 2014-02-10 11:29:16 UTC, cookie_domain = \"box.com\", cookie_path = \"/\", cookie_creation_time = 2014-02-03 11:29:17.202283 UTC, cookie_last_access_time = 2014-02-03 11:29:17.202283 UTC, cookie_persistent = True, cookie_host_only = False, cookie_secure_only = False, cookie_http_only = False},Cookie {cookie_name = \"box_visitor_id\", cookie_value = \"52ef7d8cf20e56.10269052\", cookie_expiry_time = 2015-02-03 11:29:16 UTC, cookie_domain = \"box.com\", cookie_path = \"/\", cookie_creation_time = 2014-02-03 11:29:17.202283 UTC, cookie_last_access_time = 2014-02-03 11:29:17.202283 UTC, cookie_persistent = True, cookie_host_only = False, cookie_secure_only = False, cookie_http_only = False}]})
-
-This computer is running 5.20140127 in Debian testing and my main computer is running the same git-annex but in Debian sid. Both are using the webapp.
-"""]]
diff --git a/doc/bugs/Creating_a_box.com_repository_fails/comment_3_6c3610fb95676592f17f36e4e1b09bd8._comment b/doc/bugs/Creating_a_box.com_repository_fails/comment_3_6c3610fb95676592f17f36e4e1b09bd8._comment
deleted file mode 100644
index cff2e605d..000000000
--- a/doc/bugs/Creating_a_box.com_repository_fails/comment_3_6c3610fb95676592f17f36e4e1b09bd8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8"
- nickname="Jon Ander"
- subject="comment 3"
- date="2014-02-11T08:01:47Z"
- content="""
-I'm getting the same error in version 5.20140210
-"""]]
diff --git a/doc/bugs/Creating_a_box.com_repository_fails/comment_4_c9895712e72854e4b5ff7a58e82ae374._comment b/doc/bugs/Creating_a_box.com_repository_fails/comment_4_c9895712e72854e4b5ff7a58e82ae374._comment
deleted file mode 100644
index 19350f3e0..000000000
--- a/doc/bugs/Creating_a_box.com_repository_fails/comment_4_c9895712e72854e4b5ff7a58e82ae374._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm78jq1Uo-ZbyOPG3diJUWVvEiM0kyAcvk"
- nickname="Dorian"
- subject="Same problem here"
- date="2014-02-12T13:17:50Z"
- content="""
-<pre>
-[2014-02-12 14:11:12 CET] main: starting assistant version 5.20140127.1
-[2014-02-12 14:11:12 CET] Cronner: You should enable consistency checking to protect your data. 
-(scanning...) [2014-02-12 14:11:12 CET] Watcher: Performing startup scan
-(started...) 
-(encryption setup) (shared cipher) (testing WebDAV server...)
-12/Feb/2014:14:11:49 +0100 [Error#yesod-core] InternalIOException <socket: 112>: hPutBuf: illegal operation (handle is closed) @(yesod-core-1.2.3:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:471:5)
-(encryption setup) (shared cipher) (testing WebDAV server...)
-12/Feb/2014:14:13:01 +0100 [Error#yesod-core] InternalIOException <socket: 116>: hPutBuf: illegal operation (handle is closed) @(yesod-core-1.2.3:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:471:5)
-</pre>
-"""]]
diff --git a/doc/bugs/Creating_a_box.com_repository_fails/comment_5_93981afe8162f64ebb9d8c2c6a7ef91e._comment b/doc/bugs/Creating_a_box.com_repository_fails/comment_5_93981afe8162f64ebb9d8c2c6a7ef91e._comment
deleted file mode 100644
index bcff92ac9..000000000
--- a/doc/bugs/Creating_a_box.com_repository_fails/comment_5_93981afe8162f64ebb9d8c2c6a7ef91e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8"
- nickname="Jon Ander"
- subject="Not fixed"
- date="2014-02-14T09:03:29Z"
- content="""
-This bug has been marked as fixed but I'm still experiencing it in 5.20140210
-"""]]
diff --git a/doc/bugs/Creating_a_box.com_repository_fails/comment_6_752b5725b4596721438098d38af8fb66._comment b/doc/bugs/Creating_a_box.com_repository_fails/comment_6_752b5725b4596721438098d38af8fb66._comment
deleted file mode 100644
index 4804e1671..000000000
--- a/doc/bugs/Creating_a_box.com_repository_fails/comment_6_752b5725b4596721438098d38af8fb66._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk7iPiqWr3BVPLWEDvJhSSvcOqheLEbLNo"
- nickname="Dirk"
- subject="No working ubuntu package"
- date="2014-02-16T20:50:50Z"
- content="""
-The 5.20140210 package from François Marier tells me \"WebDAV not supported by this build\" when trying to add a box.com repository. So, can't really test this anymore on ubuntu.
-"""]]
diff --git a/doc/bugs/Creating_a_box.com_repository_fails/comment_7_73f71386f8eafbb65f4cc9769021710f._comment b/doc/bugs/Creating_a_box.com_repository_fails/comment_7_73f71386f8eafbb65f4cc9769021710f._comment
deleted file mode 100644
index 016371346..000000000
--- a/doc/bugs/Creating_a_box.com_repository_fails/comment_7_73f71386f8eafbb65f4cc9769021710f._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8"
- nickname="Jon Ander"
- subject="comment 7"
- date="2014-02-24T13:20:27Z"
- content="""
-This is what I get in the log in version 5.20140221 in Debian Sid:
-
-    100%         46.5KB/s 0sInternalIOException <socket: 28>: hPutBuf: illegal operation (handle is closed)
-    InternalIOException <socket: 25>: hPutBuf: illegal operation (handle is closed)
-
-It seams that the file is being uploaded (folders are being created in box.com) but it crashes when reaching 100%
-"""]]
diff --git a/doc/bugs/Creating_a_box.com_repository_fails/comment_8_109e37051beb729834e05997c023b849._comment b/doc/bugs/Creating_a_box.com_repository_fails/comment_8_109e37051beb729834e05997c023b849._comment
deleted file mode 100644
index 24c9153a8..000000000
--- a/doc/bugs/Creating_a_box.com_repository_fails/comment_8_109e37051beb729834e05997c023b849._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="fmarier"
- ip="192.81.133.89"
- subject="Re: No working ubuntu package"
- date="2014-02-26T02:06:24Z"
- content="""
-I have just uploaded version 5.20140221.1 of the git-annex package in my PPA. It should re-enable DAV support.
-"""]]
diff --git a/doc/bugs/Creating_an_S3_repository_with_an_invalid_name_throws_an_exception.mdwn b/doc/bugs/Creating_an_S3_repository_with_an_invalid_name_throws_an_exception.mdwn
deleted file mode 100644
index 48b30eceb..000000000
--- a/doc/bugs/Creating_an_S3_repository_with_an_invalid_name_throws_an_exception.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-What steps will reproduce the problem?
-
-Attempt to create an S3 repository called 'S3 (encrypted)' via the web app.
-
-What is the expected output? What do you see instead?
-
-Expected to either accept this input, or tell me that it's invalid. Instead, I see:
-
-Internal Server Error
-user error (openTCPConnection: host lookup failure for "S3 (encrypted)-610526e6-5ce2-11e2-997e-970cbca93f19.s3.amazonaws.com")
-
-What version of git-annex are you using? On what operating system?
-
-3.20130107 On Fedora 17 (64-bit).
-
-Please provide any additional information below.
-
-> [[done]], the name will now be sanitized. --[[Joey]]
diff --git a/doc/bugs/DS__95__Store_not_gitignored.mdwn b/doc/bugs/DS__95__Store_not_gitignored.mdwn
deleted file mode 100644
index 269eb417a..000000000
--- a/doc/bugs/DS__95__Store_not_gitignored.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-What steps will reproduce the problem?
-
-Create a new git repo on OS X.  create a .gitignore file containing the line ".DS_Store".  Check it into git.  do "git annex init" to make the directory into a git annex repo.  do "git annex direct" to put it in direct mode.  do "git annex assistant" to start the assistant and watch it with "git annex webapp".
-
-Open the directory in the finder.  Drag in some files and watch the assistant as it checks them in.  Play with your window's viewing preferences, maybe view things as "icons" so that the finder is forced to store metadata about where you dragged the icons in the window in the .DS_Store file.  As you do this, watch the webapp.  .DS_Store will start to be checked into git annex, and rechecked in frequently as it is updated.  Git annex assistant is not respecting the .gitignore file.  Is there some other way to tell git annex assistant that certain files should be ignored than .gitignore?
-
-
-What is the expected output? What do you see instead?
-
-.DS_Store files are ignored by the assistant.
-
-
-What version of git-annex are you using? On what operating system?
-
-git-annex version: 3.20130124
-
-OS X Lion
-
-Please provide any additional information below.
-
-> Assistant does not support .gitignore yet. Requires an efficient query
-> interface for ignores, which git does not provide.
->
-> However, I've added a special case, OSX only ignore for .DS_Store files.
-> [[done]] --[[Joey]] 
-
diff --git a/doc/bugs/DS__95__Store_not_gitignored/comment_1_b93ac0ea3be82c361ceb4352e742ba39._comment b/doc/bugs/DS__95__Store_not_gitignored/comment_1_b93ac0ea3be82c361ceb4352e742ba39._comment
deleted file mode 100644
index 0bc821f87..000000000
--- a/doc/bugs/DS__95__Store_not_gitignored/comment_1_b93ac0ea3be82c361ceb4352e742ba39._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 1"
- date="2013-01-28T14:31:53Z"
- content="""
-outstanding!  Thank you.
-"""]]
diff --git a/doc/bugs/DS__95__Store_not_gitignored/comment_2_4136e1f4aba7aa7562dafcf6a213e10c._comment b/doc/bugs/DS__95__Store_not_gitignored/comment_2_4136e1f4aba7aa7562dafcf6a213e10c._comment
deleted file mode 100644
index 209e0545a..000000000
--- a/doc/bugs/DS__95__Store_not_gitignored/comment_2_4136e1f4aba7aa7562dafcf6a213e10c._comment
+++ /dev/null
@@ -1,58 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q"
- nickname="Andrew"
- subject="comment 2"
- date="2013-01-28T23:26:27Z"
- content="""
-This actually explains an interesting quirk (I wouldn't necessarily call it a bug) that results because of annex's handling of .gitignore:
-
-    %  › git annex import ~/Downloads/BoxcarMac.dmg
-    import BoxcarMac.dmg (checksum...) ok
-    (Recording state in git...)
-    The following paths are ignored by one of your .gitignore files:
-    BoxcarMac.dmg
-    Use -f if you really want to add them.
-    fatal: no files added
-    
-    git-annex: user error (xargs [\"-0\",\"git\",\"--git-dir=/Users/akraut/Desktop/annexes/test/.git\",\"--work-tree=/Users/akraut/Desktop/annexes/test\",\"add\",\"--\"] exited 1)
-    failed
-    git-annex: import: 1 failed
-    
-    %  › ls -l
-    total 8
-    lrwxr-xr-x 1 akraut staff 198 Jan 28 15:01 BoxcarMac.dmg -> .git/annex/objects/K4/Q8/SHA256E-s6240024--2d3b032f29c8411f81f9379bd79abfa713b66b9783559ef48cd945ab418e97a3.dmg/SHA256E-s6240024--2d3b032f29c8411f81f9379bd79abfa713b66b9783559ef48cd945ab418e97a3.dmg
-    -rw-r--r-- 1 akraut staff   0 Jan 28 14:56 README
-    lrwxr-xr-x 1 akraut staff 200 Jan 28 14:58 Wireshark 1.8.4 Intel 64.dmg -> .git/annex/objects/vj/55/SHA256E-s21772874--eb01484d832a9dc5b8fdecacdccabc4ef28fb17a2e20bc2837ccc43a69df30c5.dmg/SHA256E-s21772874--eb01484d832a9dc5b8fdecacdccabc4ef28fb17a2e20bc2837ccc43a69df30c5.dmg
-    
-    %  › cp ~/Downloads/Wireshark\ 1.8.4\ Intel\ 64.dmg .
-    
-    %  › git annex add Wireshark\ 1.8.4\ Intel\ 64.dmg
-    (Recording state in git...)
-    
-    %  › ls -l
-    total 21264
-    -rw-r--r-- 1 akraut staff        0 Jan 28 14:56 README
-    -rw-r--r-- 1 akraut staff 21772874 Jan 28 14:58 Wireshark 1.8.4 Intel 64.dmg
-    
-    %  › git annex import Wireshark\ 1.8.4\ Intel\ 64.dmg
-    import Wireshark 1.8.4 Intel 64.dmg git-annex: not overwriting existing Wireshark 1.8.4 Intel 64.dmg (use --force to override)
-    
-    %  › git annex import --force Wireshark\ 1.8.4\ Intel\ 64.dmg
-    import Wireshark 1.8.4 Intel 64.dmg (checksum...) ok
-    (Recording state in git...)
-    
-    %  › ls
-    README  Wireshark 1.8.4 Intel 64.dmg@
-    
-    %  › git annex sync
-    commit  
-    [master 0a17811] git-annex automatic sync
-     1 file changed, 1 insertion(+)
-     create mode 120000 Wireshark 1.8.4 Intel 64.dmg
-    ok
-    
-    %  › ls -l
-    total 4
-    -rw-r--r-- 1 akraut staff   0 Jan 28 14:56 README
-    lrwxr-xr-x 1 akraut staff 200 Jan 28 14:58 Wireshark 1.8.4 Intel 64.dmg -> .git/annex/objects/vj/55/SHA256E-s21772874--eb01484d832a9dc5b8fdecacdccabc4ef28fb17a2e20bc2837ccc43a69df30c5.dmg/SHA256E-s21772874--eb01484d832a9dc5b8fdecacdccabc4ef28fb17a2e20bc2837ccc43a69df30c5.dmg
-"""]]
diff --git a/doc/bugs/Detection_assumes_that_shell_is_bash.mdwn b/doc/bugs/Detection_assumes_that_shell_is_bash.mdwn
deleted file mode 100644
index 9bb0629d3..000000000
--- a/doc/bugs/Detection_assumes_that_shell_is_bash.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-###What steps will reproduce the problem?###
-
-"Adding a remote server using ssh" and try to add a remote server where the account has ex. tcsh as loginshell
-
-###What is the expected output? What do you see instead?###
-
-To discover remote programs, it dumps away some born-shell code like:
-"echo git-annex-probe loggedin;if which git-annex-shell; then echo git-annex-probe git-annex-shell; fi;if which rsync; then echo git-annex-probe rsync; fi;if which ~/.ssh/git-annex-shell; then echo git-annex-probe ~/.ssh/git-annex-shell; fi"
-
-just wrap it with a bash -c '..' and you know that its interpreted by bash.
-
-###What version of git-annex are you using? On what operating system?###
-
-git-annex version: 3.20121017
-
-###Please provide any additional information below.###
-
-Not everyone has bash as there login-shell.
-
-[[!tag /design/assistant]]
-
-> [[done]]; assistant now uses sh -c "sane shell stuff here" to work
-> around csh. (There are systems without bash, but probably fewer without sh)
-> --[[Joey]]
diff --git a/doc/bugs/Difficult_to_troubleshoot_XMPP_login_failures.mdwn b/doc/bugs/Difficult_to_troubleshoot_XMPP_login_failures.mdwn
deleted file mode 100644
index 3b1b74d16..000000000
--- a/doc/bugs/Difficult_to_troubleshoot_XMPP_login_failures.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-### Please describe the problem.
-
-I have a jabber account on `jabber.ccc.de`. When trying to log in to that account, I get "Unable to connect to the Jabber server. Maybe you entered the wrong password? (Error message: AuthenticationFailure)" I've typed the password enough times that I'm relatively certain that I've typed it correctly at least once. It's difficult to see behind this error message. This is the only thing that shows up in the debug log:
-
-    [2013-05-26 21:40:16 EDT] read: host ["-t","SRV","--","_xmpp-client._tcp.jabber.ccc.de"]
-    [2013-05-26 21:40:16 EDT] read: host ["-t","SRV","--","_xmpp-client._tcp.jabber.ccc.de"]
-
-It'd be great if this error were a wee bit more verbose.
-
-> The XMPP library has been updated to include the actual error message from the server.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Difficult_to_troubleshoot_XMPP_login_failures/comment_1_4205bccf515169031e4a9ed8e905262c._comment b/doc/bugs/Difficult_to_troubleshoot_XMPP_login_failures/comment_1_4205bccf515169031e4a9ed8e905262c._comment
deleted file mode 100644
index e1b38ac5b..000000000
--- a/doc/bugs/Difficult_to_troubleshoot_XMPP_login_failures/comment_1_4205bccf515169031e4a9ed8e905262c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-27T18:35:45Z"
- content="""
-That's all I get back from the underlying library. I have asked the library's author to propigate up the actual error message from the XMPP server if possible. The only other information I could provide is which host and port it tried to connect to. I've added that to the error message.
-
-We recently tracked a \"AuthenticationFailure\" error back to a bug in the ejabberd server's implementation of SCRAM. If jabber.ccc.de is using ejabberd, it needs to be upgraded. See <https://support.process-one.net/browse/EJAB-1632>
-"""]]
diff --git a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files.mdwn b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files.mdwn
deleted file mode 100644
index 123786b65..000000000
--- a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-##What steps will reproduce the problem?
-
-    mkdir test
-    git init
-    git annex init "test"
-    echo "test" > a
-    echo "test" > b
-    git annex add a b
-    git annex sync
-    git annex direct
-    git annex sync | grep add
-    git annex sync | grep add
-
-##What is the expected output? What do you see instead?
-
-The last two syncs shouldn't need to add or checksum anything.
-Firstly, the output is very confusing because the files have already been added.
-Secondly, the sync can take quite a while if you have lots of duplicates or a lot of files that are incidentally similar.
-
-##What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130227 on Archlinux
-
-> [[done]]; fixed inode caching code to support multiple files for the
-> same content. --[[Joey]] 
diff --git a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_1_cb10385a4f046bfe676720ded3409379._comment b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_1_cb10385a4f046bfe676720ded3409379._comment
deleted file mode 100644
index 6a5178bb6..000000000
--- a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_1_cb10385a4f046bfe676720ded3409379._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-11T06:31:09Z"
- content="""
-It seems that, to fully fix this, direct mode will need to be changed to store multiple inode caches for each key.
-
-Since the files have the same content, but different inodes and/or mtimes, at least one of them is going to appear changed to sync each time.
-
-What currently happens is that the first is re-added, and so its inode cache gets stored, and then that means the second's inode cache no longer matches, and it's re-added, and its inode cache gets stored. Putting the inode cache right back in position to force re-adding the first again..
-
-Storing multiple inode caches appears easy enough, but I have not yet worked out exactly how to clear out old inode caches.
-"""]]
diff --git a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_2_4bcf1a897181e40c9c8969d597a844f0._comment b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_2_4bcf1a897181e40c9c8969d597a844f0._comment
deleted file mode 100644
index 68c8847ae..000000000
--- a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_2_4bcf1a897181e40c9c8969d597a844f0._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnR7hb8IaKB3IKZptRukje0yahmhfLOO98"
- nickname="Adam"
- subject="comment 2"
- date="2013-04-01T19:23:12Z"
- content="""
-I think I hit this same issue when trying to work with a significant amount of files and data. It'd be good if git-annex were smarter about when a file is identical, especially if the file was copied through `rsync -a`.
-"""]]
diff --git a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_3_6a6d22d218f036c9977072973ed99aa8._comment b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_3_6a6d22d218f036c9977072973ed99aa8._comment
deleted file mode 100644
index 8f4e9bc86..000000000
--- a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_3_6a6d22d218f036c9977072973ed99aa8._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="identical filename"
- date="2013-04-06T09:09:17Z"
- content="""
-Same happens, with identical filename+content just in a different subdirectory.
-
-    annex/a.txt
-    annex/back/a.txt
-"""]]
diff --git a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_4_eaa7ffb3a1d9ffd6d89de301bd2cd5b2._comment b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_4_eaa7ffb3a1d9ffd6d89de301bd2cd5b2._comment
deleted file mode 100644
index 413ad8612..000000000
--- a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_4_eaa7ffb3a1d9ffd6d89de301bd2cd5b2._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="comment 4"
- date="2013-04-18T05:56:41Z"
- content="""
-Ok, seems like it is fixed in latest (2013.04.17) release.
-
-Laszlo
-
-"""]]
diff --git a/doc/bugs/Direct_mode_repositories_end_up_with_unstaged_changes.mdwn b/doc/bugs/Direct_mode_repositories_end_up_with_unstaged_changes.mdwn
deleted file mode 100644
index 839653e34..000000000
--- a/doc/bugs/Direct_mode_repositories_end_up_with_unstaged_changes.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-### Please describe the problem.
-
-After running two repositories syncing with one another in direct mode "git status" shows unstaged changes in both.
-
-### What steps will reproduce the problem?
-
-1. Create two direct mode repositories with each other as ssh remotes
-2. Run "git annex assistant" on each
-3. Create files on each and they get synced
-4. Run "git status"
-
-In my current repository the output is:
-
-[[!format sh """
-$ git status
-# On branch master
-# Changes not staged for commit:
-#   (use "git add <file>..." to update what will be committed)
-#   (use "git checkout -- <file>..." to discard changes in working directory)
-#
-#	typechange: fromgolias
-#	typechange: fromwintermute
-#
-no changes added to commit (use "git add" and/or "git commit -a")
-"""]]
-
-### What version of git-annex are you using? On what operating system?
-
-[[!format sh """
-$ git annex version
-git-annex version: 4.20130516.1
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-local repository version: 4
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-
-$ lsb_release -a
-No LSB modules are available.
-Distributor ID:	Ubuntu
-Description:	Ubuntu 12.04.2 LTS
-Release:	12.04
-Codename:	precise
-"""]]
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Direct_mode_repositories_end_up_with_unstaged_changes/comment_1_300a2b246182be3079db20a7e3322261._comment b/doc/bugs/Direct_mode_repositories_end_up_with_unstaged_changes/comment_1_300a2b246182be3079db20a7e3322261._comment
deleted file mode 100644
index 87e90ebe7..000000000
--- a/doc/bugs/Direct_mode_repositories_end_up_with_unstaged_changes/comment_1_300a2b246182be3079db20a7e3322261._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-29T16:18:33Z"
- content="""
-This does not indicate a problem. Nor are there any unstaged changes. `git status` simply does not know about git-annex's direct mode. Please see [[/direct_mode]] for caveats about this and other problems with using regular git commands with git-annex repositories in direct mode.
-"""]]
diff --git a/doc/bugs/Discrepancy_between_git_annex_add_and_git_annex_watch.mdwn b/doc/bugs/Discrepancy_between_git_annex_add_and_git_annex_watch.mdwn
deleted file mode 100644
index 8e836e345..000000000
--- a/doc/bugs/Discrepancy_between_git_annex_add_and_git_annex_watch.mdwn
+++ /dev/null
@@ -1,33 +0,0 @@
-### Please describe the problem.
-
-`git annex add` does not add dotfiles (as per the man page) while `git annex watch` does (nothing on the man page). It's not a bug, but rather a surprise (at least to me).
-
-### What steps will reproduce the problem?
-
-[[!format sh """
-git init dotfiles
-cd dotfiles
-git annex init "my dotfiles"
-echo test > test.txt
-echo dottest > .dotest.txt
-git annex add
-git commit -a -m "initial dots"
-git annex whereis .dotest.txt # no answer, as expected
-git annex watch
-git annex whereis .dotest.txt # answers that .dotest.txt is here
-"""]]
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20131101, ubuntu 12.04 with all updates.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> Improved documentation. [[done]] --[[Joey]]
diff --git a/doc/bugs/Displayed_copy_speed_is_wrong.mdwn b/doc/bugs/Displayed_copy_speed_is_wrong.mdwn
deleted file mode 100644
index cf3b31cf4..000000000
--- a/doc/bugs/Displayed_copy_speed_is_wrong.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-When copying data to my remote, I regularly see speeds in excess of 100 MB/s on my home DSL line.
-
-    2073939 100%  176.96MB/s    0:00:00 (xfer#1, to-check=0/1)
-
-This is definitely not correct.
-
-> Closing, as rsync does this to show you when it's making your life
-> faster than it would be w/o rsync. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Displayed_copy_speed_is_wrong/comment_1_74de3091e8bfd7acd6795e61f39f07c6._comment b/doc/bugs/Displayed_copy_speed_is_wrong/comment_1_74de3091e8bfd7acd6795e61f39f07c6._comment
deleted file mode 100644
index 62a595be7..000000000
--- a/doc/bugs/Displayed_copy_speed_is_wrong/comment_1_74de3091e8bfd7acd6795e61f39f07c6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-04-03T01:37:29Z"
- content="""
-That is displayed by rsync. It's not unheard of for rsync to resume a transfer and display extremely high speeds.
-"""]]
diff --git a/doc/bugs/Displayed_copy_speed_is_wrong/comment_2_8b240de1d5ae9229fa2d77d1cc15a552._comment b/doc/bugs/Displayed_copy_speed_is_wrong/comment_2_8b240de1d5ae9229fa2d77d1cc15a552._comment
deleted file mode 100644
index 28305d3ac..000000000
--- a/doc/bugs/Displayed_copy_speed_is_wrong/comment_2_8b240de1d5ae9229fa2d77d1cc15a552._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2011-04-03T08:56:48Z"
- content="""
-Pity. Mark as done/upstream (or similar) for house-keeping?
-"""]]
diff --git a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder.mdwn b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder.mdwn
deleted file mode 100644
index d011e4416..000000000
--- a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder.mdwn
+++ /dev/null
@@ -1,3747 +0,0 @@
-### Please describe the problem.
-Two repositories A and B. B carries the full data, A only carries a subset of the data by excluding a couple of directories with a preferred content expression. Both repos in direct mode. A was modified quite heavily (thousands of files moved, deleted) with git-annex assistant running but without a possibility to synchronise with B.
-
-During synchronisation (by starting the webapp on A and git-annex assistant on B) suddenly former top-level folders, e.g.
-
-  ./201207
-
-appear in 
-
-  ./incoming/5d/201207
-
-in both repositories.
-
-Then deleting 
-
-  ./incoming/5d/201207
-
-in repo A unfortunately removes the top-level directory 
-
-  ./201207
-
-as well and removes them in both repositories.
- 
-### What steps will reproduce the problem?
-I don't know how to reproduce apart from the description above.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20131002, 
-Debian jessie, A: amd64, B: armhf
-
-### Please provide any additional information below.
-
-A paste of .git/annex/daemon.log of repoA below, as I haven't realised the problem immediatly I cannot tell whether this is the relevant log or not. If more is needed, I can provide additional logs.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-[2013-10-27 18:35:52 CET] main: Syncing with repoB 
-From repoB:/media/srv/img
-   d1e3763..5eba12c  git-annex  -> repoB/git-annex
-   611e4f5..a7b9fd7  master     -> repoB/master
-   714ed67..a7b9fd7  synced/master -> repoB/synced/master
-Auto packing the repository for optimum performance. You may also
-run "git gc" manually. See "git help gc" for more information.
-Updating 714ed67..a7b9fd7
-Fast-forward
- 201109/jmg_7250.cr2                   | 1 -
- 201109/jmg_7250.jpg                   | 1 -
- 201109/jmg_7251.cr2                   | 1 -
- 201109/jmg_7251.jpg                   | 1 -
- 201109/jmg_7253.cr2                   | 1 -
- 201109/jmg_7253.jpg                   | 1 -
- 201109/jmg_7256_raw.jpg               | 1 -
- 201109/jmg_7259.cr2                   | 1 -
- 201109/jmg_7259.jpg                   | 1 -
- 201109/jmg_7261.cr2                   | 1 -
- 201109/jmg_7261.jpg                   | 1 -
- 201109/jmg_7265.cr2                   | 1 -
- 201109/jmg_7265.jpg                   | 1 -
- 201109/jmg_7272.jpg                   | 1 -
- 201109/jmg_7274.jpg                   | 1 -
- 201109/jmg_7275.jpg                   | 1 -
- 201109/jmg_7276.jpg                   | 1 -
- 201109/jmg_7280.jpg                   | 1 -
- 201109/jmg_7284.jpg                   | 1 -
- 201109/jmg_7286.jpg                   | 1 -
- 201109/jmg_7288.jpg                   | 1 -
- 201109/jmg_7289.jpg                   | 1 -
- 201109/jmg_7292.jpg                   | 1 -
- 201109/jmg_7293.jpg                   | 1 -
- 201109/jmg_7295.cr2                   | 1 -
- 201109/jmg_7295.jpg                   | 1 -
- 201109/jmg_7296.cr2                   | 1 -
- 201109/jmg_7296.jpg                   | 1 -
- 201109/jmg_7299.cr2                   | 1 -
- 201109/jmg_7299.jpg                   | 1 -
- 201109/jmg_7300.cr2                   | 1 -
- 201109/jmg_7300.jpg                   | 1 -
- 201109/jmg_7304.jpg                   | 1 -
- 201109/jmg_7305_raw.jpg               | 1 -
- 201109/jmg_7307_raw.jpg               | 1 -
- 201202/jmg_8528.jpg                   | 1 -
- 201202/jmg_8529.jpg                   | 1 -
- 201202/jmg_8595.jpg                   | 1 -
- 201202/jmg_8596.jpg                   | 1 -
- 201202/jmg_8597.jpg                   | 1 -
- 201202/jmg_8601.jpg                   | 1 -
- 201202/jmg_8602.cr2                   | 1 -
- 201202/jmg_8602.jpg                   | 1 -
- 201202/jmg_8603.cr2                   | 1 -
- 201202/jmg_8603.jpg                   | 1 -
- 201202/jmg_8604.jpg                   | 1 -
- 201202/jmg_8605.jpg                   | 1 -
- 201202/jmg_8606.jpg                   | 1 -
- 201202/jmg_8607.jpg                   | 1 -
- 201202/jmg_8608.jpg                   | 1 -
- 201202/jmg_8609.jpg                   | 1 -
- 201202/jmg_8610.jpg                   | 1 -
- 201202/jmg_8611.jpg                   | 1 -
- 201202/jmg_8612.cr2                   | 1 -
- 201202/jmg_8612.jpg                   | 1 -
- 201202/jmg_8613.jpg                   | 1 -
- 201202/jmg_8614.jpg                   | 1 -
- 201202/jmg_8615.jpg                   | 1 -
- 201202/jmg_8616_raw.jpg               | 1 -
- 201202/jmg_8617.jpg                   | 1 -
- 201202/jmg_8618.jpg                   | 1 -
- 201202/jmg_8619.jpg                   | 1 -
- 201202/jmg_8620.jpg                   | 1 -
- 201202/jmg_8621.jpg                   | 1 -
- 201202/jmg_8622.jpg                   | 1 -
- 201202/jmg_8624.jpg                   | 1 -
- 201202/jmg_8625.cr2                   | 1 -
- 201202/jmg_8625.jpg                   | 1 -
- 201202/jmg_8626.jpg                   | 1 -
- 201202/jmg_8627.jpg                   | 1 -
- 201202/jmg_8628.jpg                   | 1 -
- 201202/jmg_8629.jpg                   | 1 -
- 201202/jmg_8630.jpg                   | 1 -
- 201202/jmg_8631.jpg                   | 1 -
- 201202/jmg_8632.jpg                   | 1 -
- 201202/jmg_8633.cr2                   | 1 -
- 201202/jmg_8633.jpg                   | 1 -
- 201202/jmg_8634.jpg                   | 1 -
- 201202/jmg_8637.jpg                   | 1 -
- 201202/jmg_8639.jpg                   | 1 -
- 201202/jmg_8640.jpg                   | 1 -
- 201202/jmg_8641.jpg                   | 1 -
- 201202/jmg_8642_raw.jpg               | 1 -
- 201202/jmg_8643.jpg                   | 1 -
- 201202/jmg_8644.jpg                   | 1 -
- 201202/jmg_8647.jpg                   | 1 -
- 201202/jmg_8648.jpg                   | 1 -
- 201202/jmg_8651.cr2                   | 1 -
- 201202/jmg_8651.jpg                   | 1 -
- 201202/jmg_8652.jpg                   | 1 -
- 201202/jmg_8653.jpg                   | 1 -
- 201202/jmg_8654.jpg                   | 1 -
- 201202/jmg_8655.jpg                   | 1 -
- 201202/jmg_8657.jpg                   | 1 -
- 201202/jmg_8665.jpg                   | 1 -
- 201202/jmg_8670.jpg                   | 1 -
- 201202/jmg_8671.jpg                   | 1 -
- 201202/jmg_8673.cr2                   | 1 -
- 201202/jmg_8673.jpg                   | 1 -
- 201202/jmg_8674.jpg                   | 1 -
- 201202/jmg_8675.jpg                   | 1 -
- 201202/jmg_8676.jpg                   | 1 -
- 201202/jmg_8677.jpg                   | 1 -
- 201202/jmg_8678.jpg                   | 1 -
- 201202/jmg_8679.jpg                   | 1 -
- 201202/jmg_8680.jpg                   | 1 -
- 201202/jmg_8681.jpg                   | 1 -
- 201203/jmg_8701.cr2                   | 1 -
- 201203/jmg_8702.jpg                   | 1 -
- 201203/jmg_8705.jpg                   | 1 -
- 201203/jmg_8711.jpg                   | 1 -
- 201203/jmg_8717.jpg                   | 1 -
- 201203/jmg_8718.jpg                   | 1 -
- 201203/jmg_8719.jpg                   | 1 -
- 201203/jmg_8721.jpg                   | 1 -
- 201203/jmg_8725.jpg                   | 1 -
- 201203/jmg_8726.jpg                   | 1 -
- 201203/jmg_8731.jpg                   | 1 -
- 201203/jmg_8739.jpg                   | 1 -
- 201203/jmg_8745.jpg                   | 1 -
- 201203/jmg_8747_raw.jpg               | 1 -
- 201203/jmg_8750.cr2                   | 1 -
- 201203/jmg_8750.jpg                   | 1 -
- 201204/jmg_8751.jpg                   | 1 -
- 201204/jmg_8752.jpg                   | 1 -
- 201204/jmg_8755.jpg                   | 1 -
- 201204/jmg_8756.jpg                   | 1 -
- 201204/jmg_8757.jpg                   | 1 -
- 201204/jmg_8759.jpg                   | 1 -
- 201204/jmg_8760.jpg                   | 1 -
- 201204/jmg_8761.jpg                   | 1 -
- 201204/jmg_8762.jpg                   | 1 -
- 201204/jmg_8763.cr2                   | 1 -
- 201204/jmg_8763.jpg                   | 1 -
- 201204/jmg_8766.jpg                   | 1 -
- 201204/jmg_8767.cr2                   | 1 -
- 201204/jmg_8767.jpg                   | 1 -
- 201204/jmg_8768.jpg                   | 1 -
- 201204/jmg_8769.jpg                   | 1 -
- 201204/jmg_8770.jpg                   | 1 -
- 201204/jmg_8771.jpg                   | 1 -
- 201204/jmg_8772.jpg                   | 1 -
- 201204/jmg_8773.jpg                   | 1 -
- 201205/jmg_8822.jpg                   | 1 -
- 201205/jmg_8823.jpg                   | 1 -
- 201205/jmg_8824.jpg                   | 1 -
- 201205/jmg_8826.jpg                   | 1 -
- 201205/jmg_8831.jpg                   | 1 -
- 201205/jmg_8834.jpg                   | 1 -
- 201205/jmg_8835.jpg                   | 1 -
- 201205/jmg_8835_raw.jpg               | 1 -
- 201205/jmg_8837.jpg                   | 1 -
- 201205/jmg_8839.cr2                   | 1 -
- 201205/jmg_8839.jpg                   | 1 -
- 201205/jmg_8839_raw.jpg               | 1 -
- 201205/jmg_8840.cr2                   | 1 -
- 201205/jmg_8840.jpg                   | 1 -
- 201205/jmg_8840_raw.jpg               | 1 -
- 201205/jmg_8841.jpg                   | 1 -
- 201205/jmg_8842.jpg                   | 1 -
- 201205/jmg_8844.cr2                   | 1 -
- 201205/jmg_8844.jpg                   | 1 -
- 201205/jmg_8844_raw.jpg               | 1 -
- 201205/jmg_8845.jpg                   | 1 -
- 201205/jmg_8846.jpg                   | 1 -
- 201205/jmg_8847.cr2                   | 1 -
- 201205/jmg_8847.jpg                   | 1 -
- 201205/jmg_8847_raw.jpg               | 1 -
- 201205/jmg_8848.jpg                   | 1 -
- 201205/jmg_8849.jpg                   | 1 -
- 201205/jmg_8851.cr2                   | 1 -
- 201205/jmg_8851.jpg                   | 1 -
- 201205/jmg_8851_raw.jpg               | 1 -
- 201205/jmg_8856.cr2                   | 1 -
- 201205/jmg_8856.jpg                   | 1 -
- 201205/jmg_8856_raw.jpg               | 1 -
- 201205/jmg_8857.jpg                   | 1 -
- 201205/jmg_8858.jpg                   | 1 -
- 201205/jmg_8859.jpg                   | 1 -
- 201205/jmg_8861.jpg                   | 1 -
- 201205/jmg_8862.jpg                   | 1 -
- 201205/jmg_8863.jpg                   | 1 -
- 201205/jmg_8871.cr2                   | 1 -
- 201205/jmg_8871.jpg                   | 1 -
- 201205/jmg_8872.jpg                   | 1 -
- 201205/jmg_8873.jpg                   | 1 -
- 201205/jmg_8875.jpg                   | 1 -
- 201205/jmg_8876.cr2                   | 1 -
- 201205/jmg_8876.jpg                   | 1 -
- 201205/jmg_8878.cr2                   | 1 -
- 201205/jmg_8878.jpg                   | 1 -
- 201205/jmg_8879.cr2                   | 1 -
- 201205/jmg_8879.jpg                   | 1 -
- 201205/jmg_8880.cr2                   | 1 -
- 201205/jmg_8880.jpg                   | 1 -
- 201205/jmg_8881.cr2                   | 1 -
- 201205/jmg_8881.jpg                   | 1 -
- 201205/jmg_8892.cr2                   | 1 -
- 201205/jmg_8892.jpg                   | 1 -
- 201205/jmg_8893.cr2                   | 1 -
- 201205/jmg_8893.jpg                   | 1 -
- 201205/jmg_8894.cr2                   | 1 -
- 201205/jmg_8894.jpg                   | 1 -
- 201206/jmg_8989.cr2                   | 1 -
- 201206/jmg_8989.jpg                   | 1 -
- 201206/jmg_8990.cr2                   | 1 -
- 201206/jmg_8990.jpg                   | 1 -
- 201206/jmg_8995.jpg                   | 1 -
- 201206/jmg_8996.jpg                   | 1 -
- 201206/jmg_8998.jpg                   | 1 -
- 201206/jmg_9001.jpg                   | 1 -
- 201206/jmg_9003.jpg                   | 1 -
- 201206/jmg_9006.jpg                   | 1 -
- 201206/jmg_9007.jpg                   | 1 -
- 201206/jmg_9011.jpg                   | 1 -
- 201206/jmg_9014.jpg                   | 1 -
- 201206/jmg_9014_raw.jpg               | 1 -
- 201206/jmg_9015.jpg                   | 1 -
- 201206/jmg_9016.cr2                   | 1 -
- 201206/jmg_9016.jpg                   | 1 -
- 201206/jmg_9017.cr2                   | 1 -
- 201206/jmg_9017.jpg                   | 1 -
- 201206/jmg_9018.cr2                   | 1 -
- 201206/jmg_9018.jpg                   | 1 -
- 201206/jmg_9019.cr2                   | 1 -
- 201206/jmg_9019.jpg                   | 1 -
- 201206/jmg_9023.cr2                   | 1 -
- 201206/jmg_9023.jpg                   | 1 -
- 201206/jmg_9024.cr2                   | 1 -
- 201206/jmg_9024.jpg                   | 1 -
- 201206/jmg_9025.cr2                   | 1 -
- 201206/jmg_9025.jpg                   | 1 -
- 201206/jmg_9028.jpg                   | 1 -
- 201206/jmg_9029.jpg                   | 1 -
- 201206/jmg_9030.jpg                   | 1 -
- 201206/jmg_9031.jpg                   | 1 -
- 201206/jmg_9032_raw.jpg               | 1 -
- 201206/jmg_9033.jpg                   | 1 -
- 201206/jmg_9033_raw.jpg               | 1 -
- 201206/jmg_9034.jpg                   | 1 -
- 201206/jmg_9035.jpg                   | 1 -
- 201206/jmg_9035_raw.jpg               | 1 -
- 201206/jmg_9036.jpg                   | 1 -
- 201206/jmg_9039.cr2                   | 1 -
- 201206/jmg_9039.jpg                   | 1 -
- 201206/jmg_9040.cr2                   | 1 -
- 201206/jmg_9040.jpg                   | 1 -
- 201206/jmg_9043.cr2                   | 1 -
- 201206/jmg_9043.jpg                   | 1 -
- 201206/jmg_9047.cr2                   | 1 -
- 201206/jmg_9047.jpg                   | 1 -
- 201207/jmg_9048.jpg                   | 1 -
- 201207/jmg_9053.jpg                   | 1 -
- 201207/jmg_9054.jpg                   | 1 -
- 201207/jmg_9069.cr2                   | 1 -
- 201207/jmg_9069.jpg                   | 1 -
- 201207/jmg_9070.cr2                   | 1 -
- 201207/jmg_9070.jpg                   | 1 -
- 201207/jmg_9072.cr2                   | 1 -
- 201207/jmg_9072.jpg                   | 1 -
- 201207/jmg_9076.cr2                   | 1 -
- 201207/jmg_9076.jpg                   | 1 -
- 201208/jmg_9077.jpg                   | 1 -
- 201208/jmg_9302_raw.jpg               | 1 -
- 201208/jmg_9303.jpg                   | 1 -
- 201208/jmg_9304.cr2                   | 1 -
- 201208/jmg_9304.jpg                   | 1 -
- 201208/jmg_9305.cr2                   | 1 -
- 201208/jmg_9305.jpg                   | 1 -
- 201208/jmg_9306_raw.jpg               | 1 -
- 201208/jmg_9307.cr2                   | 1 -
- 201208/jmg_9307.jpg                   | 1 -
- 201208/jmg_9308_raw.jpg               | 1 -
- 201208/jmg_9309_raw.jpg               | 1 -
- 201208/jmg_9310.cr2                   | 1 -
- 201208/jmg_9310.jpg                   | 1 -
- 201208/jmg_9310_bw.jpg                | 1 -
- 201208/jmg_9310_raw.jpg               | 1 -
- 201208/jmg_9312.jpg                   | 1 -
- 201208/jmg_9313.jpg                   | 1 -
- 201208/jmg_9314.jpg                   | 1 -
- 201208/jmg_9315.jpg                   | 1 -
- 201208/jmg_9319.jpg                   | 1 -
- 201208/jmg_9523.jpg                   | 1 -
- 201208/jmg_9524.jpg                   | 1 -
- 201208/jmg_9525.jpg                   | 1 -
- 201208/jmg_9526.jpg                   | 1 -
- 201208/jmg_9527.jpg                   | 1 -
- 201208/jmg_9527_raw.jpg               | 1 -
- 201208/jmg_9528.jpg                   | 1 -
- 201208/jmg_9529.jpg                   | 1 -
- 201208/jmg_9530.jpg                   | 1 -
- 201208/jmg_9531.jpg                   | 1 -
- 201208/jmg_9532.jpg                   | 1 -
- 201208/jmg_9533.cr2                   | 1 -
- 201208/jmg_9533.jpg                   | 1 -
- 201208/jmg_9534.cr2                   | 1 -
- 201208/jmg_9534.jpg                   | 1 -
- 201208/jmg_9535.jpg                   | 1 -
- 201208/jmg_9536.jpg                   | 1 -
- 201208/jmg_9537.cr2                   | 1 -
- 201208/jmg_9537.jpg                   | 1 -
- 201208/jmg_9538.jpg                   | 1 -
- 201208/jmg_9539.jpg                   | 1 -
- 201208/jmg_9540.jpg                   | 1 -
- 201208/jmg_9541.cr2                   | 1 -
- 201208/jmg_9542.jpg                   | 1 -
- 201208/jmg_9543.cr2                   | 1 -
- 201208/jmg_9543.jpg                   | 1 -
- 201208/jmg_9544.cr2                   | 1 -
- 201208/jmg_9544.jpg                   | 1 -
- 201208/jmg_9545.jpg                   | 1 -
- 201209/jmg_9547.jpg                   | 1 -
- 201209/jmg_9548.jpg                   | 1 -
- 201209/jmg_9549.jpg                   | 1 -
- 201209/jmg_9550.jpg                   | 1 -
- 201209/jmg_9551.jpg                   | 1 -
- 201209/jmg_9552.jpg                   | 1 -
- 201209/jmg_9553.jpg                   | 1 -
- 201209/jmg_9555.jpg                   | 1 -
- 201209/jmg_9556.jpg                   | 1 -
- 201209/jmg_9558.jpg                   | 1 -
- 201209/jmg_9559.cr2                   | 1 -
- 201209/jmg_9559.jpg                   | 1 -
- 201209/jmg_9560.cr2                   | 1 -
- 201209/jmg_9560.jpg                   | 1 -
- 201209/jmg_9561.jpg                   | 1 -
- 201209/jmg_9562.jpg                   | 1 -
- 201209/jmg_9568.jpg                   | 1 -
- 201210/jmg_0001.jpg                   | 1 -
- 201210/jmg_0021.jpg                   | 1 -
- 201210/jmg_0022.cr2                   | 1 -
- 201210/jmg_0022.jpg                   | 1 -
- 201210/jmg_0025.jpg                   | 1 -
- 201210/jmg_0026.jpg                   | 1 -
- 201210/jmg_0027.jpg                   | 1 -
- 201210/jmg_0028.jpg                   | 1 -
- 201210/jmg_0029.jpg                   | 1 -
- 201210/jmg_0030.jpg                   | 1 -
- 201210/jmg_0032.jpg                   | 1 -
- 201210/jmg_0034.jpg                   | 1 -
- 201210/jmg_0035.jpg                   | 1 -
- 201210/jmg_0036.jpg                   | 1 -
- 201210/jmg_0037.jpg                   | 1 -
- 201210/jmg_0039.cr2                   | 1 -
- 201210/jmg_0039.jpg                   | 1 -
- 201210/jmg_0040.jpg                   | 1 -
- 201210/jmg_9572.jpg                   | 1 -
- 201210/jmg_9573.jpg                   | 1 -
- 201210/jmg_9574.jpg                   | 1 -
- 201210/jmg_9575.jpg                   | 1 -
- 201210/jmg_9576.jpg                   | 1 -
- 201210/jmg_9578.jpg                   | 1 -
- 201210/jmg_9580.jpg                   | 1 -
- 201210/jmg_9581.jpg                   | 1 -
- 201210/jmg_9582.cr2                   | 1 -
- 201210/jmg_9582.jpg                   | 1 -
- 201210/jmg_9585.cr2                   | 1 -
- 201210/jmg_9585.jpg                   | 1 -
- 201210/jmg_9587.cr2                   | 1 -
- 201210/jmg_9587.jpg                   | 1 -
- 201210/jmg_9588.jpg                   | 1 -
- 201210/jmg_9589.jpg                   | 1 -
- 201210/jmg_9590.jpg                   | 1 -
- 201210/jmg_9591.jpg                   | 1 -
- 201210/jmg_9594.jpg                   | 1 -
- 201210/jmg_9595.jpg                   | 1 -
- 201210/jmg_9596.jpg                   | 1 -
- 201210/jmg_9597.cr2                   | 1 -
- 201210/jmg_9597.jpg                   | 1 -
- 201210/jmg_9598.cr2                   | 1 -
- 201210/jmg_9598.jpg                   | 1 -
- 201210/jmg_9599.cr2                   | 1 -
- 201210/jmg_9599.jpg                   | 1 -
- 201210/jmg_9600.jpg                   | 1 -
- 201210/jmg_9602.jpg                   | 1 -
- 201210/jmg_9603.jpg                   | 1 -
- 201210/jmg_9604.jpg                   | 1 -
- 201210/jmg_9605.cr2                   | 1 -
- 201210/jmg_9605.jpg                   | 1 -
- 201210/jmg_9606.jpg                   | 1 -
- 201210/jmg_9608.jpg                   | 1 -
- 201210/jmg_9609.jpg                   | 1 -
- 201210/jmg_9610.jpg                   | 1 -
- 201210/jmg_9611.jpg                   | 1 -
- 201210/jmg_9612.jpg                   | 1 -
- 201210/jmg_9613.jpg                   | 1 -
- 201210/jmg_9614.jpg                   | 1 -
- 201210/jmg_9616.cr2                   | 1 -
- 201210/jmg_9616.jpg                   | 1 -
- 201210/jmg_9617.jpg                   | 1 -
- 201210/jmg_9619.jpg                   | 1 -
- 201210/jmg_9620.jpg                   | 1 -
- 201210/jmg_9621.jpg                   | 1 -
- 201210/jmg_9622.jpg                   | 1 -
- 201210/jmg_9623.cr2                   | 1 -
- 201210/jmg_9623.jpg                   | 1 -
- 201210/jmg_9624.cr2                   | 1 -
- 201210/jmg_9624.jpg                   | 1 -
- 201210/jmg_9736_raw.jpg               | 1 -
- 201210/jmg_9738_raw.jpg               | 1 -
- 201210/jmg_9740.cr2                   | 1 -
- 201210/jmg_9740.jpg                   | 1 -
- 201210/jmg_9743.jpg                   | 1 -
- 201210/jmg_9744.jpg                   | 1 -
- 201210/jmg_9745.cr2                   | 1 -
- 201210/jmg_9745.jpg                   | 1 -
- 201210/jmg_9746.cr2                   | 1 -
- 201210/jmg_9746.jpg                   | 1 -
- 201210/jmg_9748.jpg                   | 1 -
- 201210/jmg_9749_raw.jpg               | 1 -
- 201210/jmg_9751.jpg                   | 1 -
- 201210/jmg_9752.jpg                   | 1 -
- 201210/jmg_9754.jpg                   | 1 -
- 201210/jmg_9755.jpg                   | 1 -
- 201210/jmg_9756.jpg                   | 1 -
- 201210/jmg_9760.cr2                   | 1 -
- 201210/jmg_9760.jpg                   | 1 -
- 201210/jmg_9761.cr2                   | 1 -
- 201210/jmg_9761.jpg                   | 1 -
- 201210/jmg_9763.jpg                   | 1 -
- 201210/jmg_9764.jpg                   | 1 -
- 201210/jmg_9766.jpg                   | 1 -
- 201210/jmg_9767.cr2                   | 1 -
- 201210/jmg_9767.jpg                   | 1 -
- 201210/jmg_9768.jpg                   | 1 -
- 201210/jmg_9771.jpg                   | 1 -
- 201210/jmg_9772.jpg                   | 1 -
- 201210/jmg_9791.jpg                   | 1 -
- 201210/jmg_9792.jpg                   | 1 -
- 201210/jmg_9793.jpg                   | 1 -
- 201210/jmg_9794.jpg                   | 1 -
- 201210/jmg_9796.jpg                   | 1 -
- 201210/jmg_9797.jpg                   | 1 -
- 201210/jmg_9799.jpg                   | 1 -
- 201210/jmg_9800.jpg                   | 1 -
- 201210/jmg_9801.jpg                   | 1 -
- 201210/jmg_9803.jpg                   | 1 -
- 201210/jmg_9807.jpg                   | 1 -
- 201210/jmg_9808.jpg                   | 1 -
- 201210/jmg_9809.jpg                   | 1 -
- 201210/jmg_9810.jpg                   | 1 -
- 201210/jmg_9811.jpg                   | 1 -
- 201210/jmg_9812.jpg                   | 1 -
- 201210/jmg_9813.jpg                   | 1 -
- 201210/jmg_9815.jpg                   | 1 -
- 201210/jmg_9818.jpg                   | 1 -
- 201210/jmg_9819.jpg                   | 1 -
- 201210/jmg_9820.jpg                   | 1 -
- 201210/jmg_9821.jpg                   | 1 -
- 201210/jmg_9822.jpg                   | 1 -
- 201210/jmg_9823.jpg                   | 1 -
- 201210/jmg_9825.jpg                   | 1 -
- 201210/jmg_9826.jpg                   | 1 -
- 201210/jmg_9827.jpg                   | 1 -
- 201210/jmg_9828.jpg                   | 1 -
- 201210/jmg_9829.jpg                   | 1 -
- 201210/jmg_9830.cr2                   | 1 -
- 201210/jmg_9830.jpg                   | 1 -
- 201210/jmg_9832.cr2                   | 1 -
- 201210/jmg_9832.jpg                   | 1 -
- 201210/jmg_9834.jpg                   | 1 -
- 201210/jmg_9836.jpg                   | 1 -
- 201210/jmg_9838.jpg                   | 1 -
- 201210/jmg_9839.jpg                   | 1 -
- 201210/jmg_9841.jpg                   | 1 -
- 201210/jmg_9843.jpg                   | 1 -
- 201210/jmg_9845.jpg                   | 1 -
- 201210/jmg_9846.jpg                   | 1 -
- 201210/jmg_9848.jpg                   | 1 -
- 201210/jmg_9849.jpg                   | 1 -
- 201210/jmg_9852.jpg                   | 1 -
- 201210/jmg_9853.jpg                   | 1 -
- 201210/jmg_9854.jpg                   | 1 -
- 201210/jmg_9855.jpg                   | 1 -
- 201210/jmg_9856.jpg                   | 1 -
- 201210/jmg_9857.cr2                   | 1 -
- 201210/jmg_9857.jpg                   | 1 -
- 201210/jmg_9858.cr2                   | 1 -
- 201210/jmg_9858.jpg                   | 1 -
- 201210/jmg_9859.jpg                   | 1 -
- 201210/jmg_9860.jpg                   | 1 -
- 201210/jmg_9915.jpg                   | 1 -
- 201210/jmg_9917.jpg                   | 1 -
- 201210/jmg_9918.jpg                   | 1 -
- 201210/jmg_9919.jpg                   | 1 -
- 201210/jmg_9922.jpg                   | 1 -
- 201210/jmg_9923.jpg                   | 1 -
- 201210/jmg_9925.jpg                   | 1 -
- 201210/jmg_9926.cr2                   | 1 -
- 201210/jmg_9926.jpg                   | 1 -
- 201210/jmg_9928.jpg                   | 1 -
- 201210/jmg_9975.cr2                   | 1 -
- 201210/jmg_9975.jpg                   | 1 -
- 201210/jmg_9976.cr2                   | 1 -
- 201210/jmg_9976.jpg                   | 1 -
- 201210/jmg_9978.jpg                   | 1 -
- 201210/jmg_9986.jpg                   | 1 -
- 201210/jmg_9987.jpg                   | 1 -
- 201210/jmg_9988.jpg                   | 1 -
- 201210/jmg_9989.jpg                   | 1 -
- 201210/jmg_9991.jpg                   | 1 -
- 201210/jmg_9993.jpg                   | 1 -
- 201210/jmg_9994.cr2                   | 1 -
- 201210/jmg_9994.jpg                   | 1 -
- 201210/jmg_9997.jpg                   | 1 -
- 201210/jmg_9998.jpg                   | 1 -
- 201210/jmg_9999.jpg                   | 1 -
- 201212/jmg_0131.jpg                   | 1 -
- 201212/jmg_0134.jpg                   | 1 -
- 201212/jmg_0135.jpg                   | 1 -
- 201212/jmg_0152.jpg                   | 1 -
- 201212/jmg_0155.jpg                   | 1 -
- 201212/jmg_0156.jpg                   | 1 -
- 201212/jmg_0162.jpg                   | 1 -
- 201212/jmg_0163.jpg                   | 1 -
- 201212/jmg_0165.jpg                   | 1 -
- 201212/jmg_0176.cr2                   | 1 -
- 201212/jmg_0176.jpg                   | 1 -
- 201212/jmg_0177.cr2                   | 1 -
- 201212/jmg_0177.jpg                   | 1 -
- 201212/jmg_0178.jpg                   | 1 -
- 201212/jmg_0179.jpg                   | 1 -
- 201212/jmg_0180.jpg                   | 1 -
- 201212/jmg_0184.jpg                   | 1 -
- 201212/jmg_0185.jpg                   | 1 -
- 201212/jmg_0186.jpg                   | 1 -
- 201212/jmg_0187.jpg                   | 1 -
- 201212/jmg_0306.jpg                   | 1 -
- 201212/jmg_0307.jpg                   | 1 -
- 201212/jmg_0308.jpg                   | 1 -
- 201212/jmg_0310.jpg                   | 1 -
- 201212/jmg_0311.jpg                   | 1 -
- 201212/jmg_0312.jpg                   | 1 -
- 201212/jmg_0313.jpg                   | 1 -
- 201212/jmg_0314.jpg                   | 1 -
- 201212/jmg_0315.jpg                   | 1 -
- 201212/jmg_0316.jpg                   | 1 -
- 201212/jmg_0317.jpg                   | 1 -
- 201212/jmg_0321.jpg                   | 1 -
- 201212/jmg_0326.jpg                   | 1 -
- 201212/jmg_0328.jpg                   | 1 -
- 201212/jmg_0330.jpg                   | 1 -
- 201212/jmg_0333.jpg                   | 1 -
- 201212/jmg_0336.jpg                   | 1 -
- 201212/jmg_0340.jpg                   | 1 -
- 201212/jmg_0343.jpg                   | 1 -
- 201212/jmg_0345.jpg                   | 1 -
- 201212/jmg_0360.jpg                   | 1 -
- 201212/jmg_0362.jpg                   | 1 -
- 201212/jmg_0363.jpg                   | 1 -
- 201212/jmg_0364.jpg                   | 1 -
- 201212/jmg_0366.jpg                   | 1 -
- 201212/jmg_0367.jpg                   | 1 -
- 201212/jmg_0368.jpg                   | 1 -
- 201212/jmg_0369.jpg                   | 1 -
- 201212/jmg_0370.jpg                   | 1 -
- 201212/jmg_0372.jpg                   | 1 -
- 201212/jmg_0382.jpg                   | 1 -
- 201212/jmg_0383.jpg                   | 1 -
- 201212/jmg_0384.jpg                   | 1 -
- 201212/jmg_0385.jpg                   | 1 -
- 201212/jmg_0387.jpg                   | 1 -
- 201212/jmg_0388.jpg                   | 1 -
- 201212/jmg_0389.jpg                   | 1 -
- 201212/jmg_0390.jpg                   | 1 -
- 201212/jmg_0392.jpg                   | 1 -
- 201212/jmg_0396.jpg                   | 1 -
- 201212/jmg_0397.jpg                   | 1 -
- 201212/jmg_0398.jpg                   | 1 -
- 201212/jmg_0399.jpg                   | 1 -
- 201212/jmg_0402.jpg                   | 1 -
- 201212/jmg_0404.jpg                   | 1 -
- 201212/jmg_0405.jpg                   | 1 -
- 201212/jmg_0406.jpg                   | 1 -
- 201212/jmg_0407.jpg                   | 1 -
- 201212/jmg_0408.jpg                   | 1 -
- 201212/jmg_0410.jpg                   | 1 -
- 201212/jmg_0411.jpg                   | 1 -
- 201212/jmg_0412.jpg                   | 1 -
- 201212/jmg_0415.jpg                   | 1 -
- 201212/jmg_0417.jpg                   | 1 -
- 201212/jmg_0418.jpg                   | 1 -
- 201302/jmg_0502.cr2                   | 1 -
- 201302/jmg_0502.jpg                   | 1 -
- 201302/jmg_0503.jpg                   | 1 -
- 201302/jmg_0507.jpg                   | 1 -
- 201302/jmg_0510.jpg                   | 1 -
- 201302/jmg_0512.jpg                   | 1 -
- 201302/jmg_0513.jpg                   | 1 -
- 201302/jmg_0514.jpg                   | 1 -
- 201302/jmg_0516.jpg                   | 1 -
- 201302/jmg_0517.jpg                   | 1 -
- 201302/jmg_0518.jpg                   | 1 -
- 201302/jmg_0521.jpg                   | 1 -
- 201302/jmg_0522.jpg                   | 1 -
- 201302/jmg_0523.jpg                   | 1 -
- 201302/jmg_0524.jpg                   | 1 -
- 201302/jmg_0526.jpg                   | 1 -
- 201302/jmg_0527.jpg                   | 1 -
- 201302/jmg_0528.jpg                   | 1 -
- 201302/jmg_0532.cr2                   | 1 -
- 201302/jmg_0532.jpg                   | 1 -
- 201302/jmg_0534.jpg                   | 1 -
- 201302/jmg_0535.jpg                   | 1 -
- 201302/jmg_0537.jpg                   | 1 -
- 201302/jmg_0539.jpg                   | 1 -
- 201302/jmg_0541.jpg                   | 1 -
- 201302/jmg_0543.jpg                   | 1 -
- 201304/bruecke_saeckingen.tif         | 1 -
- 201304/jmg_0685.cr2                   | 1 -
- 201304/jmg_0685.jpg                   | 1 -
- 201304/jmg_0687.cr2                   | 1 -
- 201304/jmg_0687.jpg                   | 1 -
- 201304/jmg_0699.jpg                   | 1 -
- 201304/jmg_0700.jpg                   | 1 -
- 201304/jmg_0726.jpg                   | 1 -
- 201304/jmg_0727.jpg                   | 1 -
- 201304/jmg_0728.jpg                   | 1 -
- 201304/jmg_0729.cr2                   | 1 -
- 201304/jmg_0729.jpg                   | 1 -
- 201304/jmg_0730.jpg                   | 1 -
- 201304/jmg_0731.jpg                   | 1 -
- 201304/jmg_0733.cr2                   | 1 -
- 201304/jmg_0733.jpg                   | 1 -
- 201304/jmg_0734.cr2                   | 1 -
- 201304/jmg_0734.jpg                   | 1 -
- 201304/jmg_0736.cr2                   | 1 -
- 201304/jmg_0736.jpg                   | 1 -
- 201304/jmg_0737.cr2                   | 1 -
- 201304/jmg_0737.jpg                   | 1 -
- 201304/jmg_0738.jpg                   | 1 -
- 201304/jmg_0739.jpg                   | 1 -
- 201304/jmg_0740.jpg                   | 1 -
- 201304/jmg_0741.jpg                   | 1 -
- 201304/jmg_0742.jpg                   | 1 -
- 201304/jmg_0744.cr2                   | 1 -
- 201304/jmg_0744.jpg                   | 1 -
- 201304/jmg_0749.jpg                   | 1 -
- 201304/jmg_0750.jpg                   | 1 -
- 201304/jmg_0751.jpg                   | 1 -
- 201304/jmg_0752.jpg                   | 1 -
- 201304/jmg_0753.jpg                   | 1 -
- 201304/jmg_0755.cr2                   | 1 -
- 201304/jmg_0755.jpg                   | 1 -
- 201304/jmg_0757.cr2                   | 1 -
- 201304/jmg_0757.jpg                   | 1 -
- 201304/jmg_0758.jpg                   | 1 -
- 201304/jmg_0759.jpg                   | 1 -
- 201304/jmg_0760.cr2                   | 1 -
- 201304/jmg_0760.jpg                   | 1 -
- 201304/jmg_0762.cr2                   | 1 -
- 201304/jmg_0762.jpg                   | 1 -
- 201304/jmg_0763.jpg                   | 1 -
- 201304/jmg_0764.jpg                   | 1 -
- 201304/jmg_0765.jpg                   | 1 -
- 201304/jmg_0766.jpg                   | 1 -
- 201304/jmg_0769.jpg                   | 1 -
- 201304/jmg_0770.jpg                   | 1 -
- 201304/jmg_0771.jpg                   | 1 -
- 201304/jmg_0785.cr2                   | 1 -
- 201304/jmg_0785.jpg                   | 1 -
- 201304/jmg_0786.cr2                   | 1 -
- 201304/jmg_0786.jpg                   | 1 -
- 201304/jmg_0787.cr2                   | 1 -
- 201304/jmg_0787.jpg                   | 1 -
- 201304/jmg_0789.jpg                   | 1 -
- 201304/jmg_0790.jpg                   | 1 -
- 201304/jmg_0791.jpg                   | 1 -
- 201304/jmg_0800.jpg                   | 1 -
- 201304/jmg_0801.jpg                   | 1 -
- 201304/jmg_0802.jpg                   | 1 -
- 201304/jmg_0803.jpg                   | 1 -
- 201304/jmg_0809.jpg                   | 1 -
- 201304/jmg_0810.jpg                   | 1 -
- 201304/jmg_0812.jpg                   | 1 -
- 201304/jmg_0813.jpg                   | 1 -
- 201304/jmg_0824.jpg                   | 1 -
- 201304/jmg_0825.jpg                   | 1 -
- 201304/jmg_0827.jpg                   | 1 -
- 201304/jmg_0831.jpg                   | 1 -
- 201304/jmg_0833.jpg                   | 1 -
- 201304/jmg_0834.jpg                   | 1 -
- 201304/jmg_0836.jpg                   | 1 -
- 201304/jmg_0837.jpg                   | 1 -
- 201304/jmg_0845.jpg                   | 1 -
- 201304/jmg_0846.jpg                   | 1 -
- 201304/jmg_0847.jpg                   | 1 -
- 201304/jmg_0848.jpg                   | 1 -
- 201304/jmg_0849.jpg                   | 1 -
- 201304/jmg_0850.jpg                   | 1 -
- 201304/jmg_0851.jpg                   | 1 -
- 201304/jmg_0857.jpg                   | 1 -
- 201304/jmg_0858.jpg                   | 1 -
- 201304/jmg_0860.jpg                   | 1 -
- 201304/jmg_0861.jpg                   | 1 -
- 201304/jmg_0862.jpg                   | 1 -
- 201304/jmg_0863.jpg                   | 1 -
- 201304/jmg_0864.jpg                   | 1 -
- 201304/jmg_0866.jpg                   | 1 -
- 201304/jmg_0867.jpg                   | 1 -
- 201304/jmg_0868.cr2                   | 1 -
- 201304/jmg_0868.jpg                   | 1 -
- 201304/jmg_0869.cr2                   | 1 -
- 201304/jmg_0869.jpg                   | 1 -
- 201304/jmg_0872.cr2                   | 1 -
- 201304/jmg_0872.jpg                   | 1 -
- 201304/jmg_0874.cr2                   | 1 -
- 201304/jmg_0874.jpg                   | 1 -
- 201304/jmg_0875.jpg                   | 1 -
- 201304/jmg_0875_raw.jpg               | 1 -
- 201304/jmg_0876.jpg                   | 1 -
- 201304/jmg_0877.jpg                   | 1 -
- 201304/jmg_0878.jpg                   | 1 -
- 201304/jmg_0880.jpg                   | 1 -
- 201304/jmg_0881.jpg                   | 1 -
- 201304/jmg_0882.jpg                   | 1 -
- 201304/jmg_0884.jpg                   | 1 -
- 201304/jmg_0885.jpg                   | 1 -
- 201304/jmg_0886.jpg                   | 1 -
- 201304/jmg_0888.jpg                   | 1 -
- 201304/jmg_0889.jpg                   | 1 -
- 201304/jmg_0890.jpg                   | 1 -
- 201304/jmg_0891.jpg                   | 1 -
- 201304/jmg_0892.jpg                   | 1 -
- 201304/jmg_0893.cr2                   | 1 -
- 201304/jmg_0893.jpg                   | 1 -
- 201304/jmg_0894.jpg                   | 1 -
- 201304/jmg_0896.jpg                   | 1 -
- 201304/jmg_0897.jpg                   | 1 -
- 201304/jmg_0898.jpg                   | 1 -
- 201304/jmg_0899.jpg                   | 1 -
- 201304/jmg_0900.jpg                   | 1 -
- 201304/jmg_0902.jpg                   | 1 -
- 201304/jmg_0905.jpg                   | 1 -
- 201304/jmg_0921.jpg                   | 1 -
- 201304/jmg_0922.jpg                   | 1 -
- 201304/jmg_0932.jpg                   | 1 -
- 201304/jmg_0935.jpg                   | 1 -
- 201304/jmg_0936.jpg                   | 1 -
- 201304/jmg_0937.jpg                   | 1 -
- 201304/jmg_0938.jpg                   | 1 -
- 201304/jmg_0942.jpg                   | 1 -
- 201304/jmg_0944.jpg                   | 1 -
- 201304/jmg_0946.jpg                   | 1 -
- 201304/jmg_0947.jpg                   | 1 -
- 201304/jmg_0948.jpg                   | 1 -
- 201304/jmg_0949.jpg                   | 1 -
- 201304/jmg_0950.jpg                   | 1 -
- 201304/jmg_0951.jpg                   | 1 -
- 201304/jmg_0952.jpg                   | 1 -
- 201304/jmg_0953.jpg                   | 1 -
- 201304/jmg_0954.jpg                   | 1 -
- 201304/jmg_0958.jpg                   | 1 -
- 201304/jmg_0959.jpg                   | 1 -
- 201304/jmg_0960.jpg                   | 1 -
- 201304/jmg_0961.jpg                   | 1 -
- 201304/jmg_0962.jpg                   | 1 -
- 201304/jmg_0963.jpg                   | 1 -
- 201304/jmg_0964.jpg                   | 1 -
- 201304/jmg_0965.jpg                   | 1 -
- 201304/jmg_0966.jpg                   | 1 -
- 201304/jmg_0967.jpg                   | 1 -
- 201304/jmg_0968.jpg                   | 1 -
- 201304/jmg_0969.jpg                   | 1 -
- 201304/jmg_0976.cr2                   | 1 -
- 201304/jmg_0976.jpg                   | 1 -
- 201304/jmg_0978.jpg                   | 1 -
- 201304/jmg_0979.jpg                   | 1 -
- 201304/jmg_0980.jpg                   | 1 -
- 201304/jmg_0981.cr2                   | 1 -
- 201304/jmg_0981.jpg                   | 1 -
- 201304/jmg_0982.jpg                   | 1 -
- 201304/jmg_0984.cr2                   | 1 -
- 201304/jmg_0984.jpg                   | 1 -
- 201304/jmg_0987.jpg                   | 1 -
- 201304/jmg_0988.jpg                   | 1 -
- 201304/jmg_0989.jpg                   | 1 -
- 201304/jmg_0990.jpg                   | 1 -
- 201304/jmg_0991.jpg                   | 1 -
- 201304/jmg_0992.jpg                   | 1 -
- 201304/jmg_1206.jpg                   | 1 -
- 201304/jmg_1207.jpg                   | 1 -
- 201304/jmg_1208.jpg                   | 1 -
- 201304/jmg_1209.jpg                   | 1 -
- 201304/jmg_1210.cr2                   | 1 -
- 201304/jmg_1210.jpg                   | 1 -
- 201304/jmg_1211.jpg                   | 1 -
- 201304/jmg_1212.jpg                   | 1 -
- 201304/jmg_1213.jpg                   | 1 -
- 201304/jmg_1214.cr2                   | 1 -
- 201304/jmg_1214.jpg                   | 1 -
- 201304/jmg_1215.jpg                   | 1 -
- 201304/jmg_1216.cr2                   | 1 -
- 201304/jmg_1216.jpg                   | 1 -
- 201304/jmg_1217.cr2                   | 1 -
- 201304/jmg_1217.jpg                   | 1 -
- 201304/jmg_1220.cr2                   | 1 -
- 201304/jmg_1220.jpg                   | 1 -
- 201304/jmg_1222.cr2                   | 1 -
- 201304/jmg_1222.jpg                   | 1 -
- 201304/jmg_1223.jpg                   | 1 -
- 201306/jmg_1465.jpg                   | 1 -
- 201306/jmg_1466.jpg                   | 1 -
- 201306/jmg_1467.jpg                   | 1 -
- 201306/jmg_1468.jpg                   | 1 -
- 201306/jmg_1469.jpg                   | 1 -
- 201306/jmg_1470.jpg                   | 1 -
- 201306/jmg_1471.jpg                   | 1 -
- 201306/jmg_1472.jpg                   | 1 -
- 201306/jmg_1473.jpg                   | 1 -
- 201306/jmg_1475.jpg                   | 1 -
- 201306/jmg_1476.jpg                   | 1 -
- 201306/jmg_1477.jpg                   | 1 -
- 201306/jmg_1478.jpg                   | 1 -
- 201306/jmg_1479.jpg                   | 1 -
- 201306/jmg_1480.jpg                   | 1 -
- 201306/jmg_1481.jpg                   | 1 -
- 201306/jmg_1482.jpg                   | 1 -
- 201306/jmg_1483.jpg                   | 1 -
- 201306/jmg_1484.jpg                   | 1 -
- 201306/jmg_1485.jpg                   | 1 -
- 201306/jmg_1486.jpg                   | 1 -
- 201306/jmg_1487.jpg                   | 1 -
- 201306/jmg_1488.jpg                   | 1 -
- 201306/jmg_1489.jpg                   | 1 -
- 201306/jmg_1490.jpg                   | 1 -
- 201306/jmg_1491.jpg                   | 1 -
- 201306/jmg_1492.jpg                   | 1 -
- 201306/jmg_1495.jpg                   | 1 -
- 201306/jmg_1496.jpg                   | 1 -
- 201306/jmg_1498.jpg                   | 1 -
- 201306/jmg_1499.jpg                   | 1 -
- 201306/jmg_1500.jpg                   | 1 -
- 201306/jmg_1501.jpg                   | 1 -
- 201306/jmg_1502.jpg                   | 1 -
- 201306/jmg_1504.jpg                   | 1 -
- 201306/jmg_1506.jpg                   | 1 -
- 201306/jmg_1510.jpg                   | 1 -
- 201306/jmg_1512.jpg                   | 1 -
- 201306/jmg_1513.jpg                   | 1 -
- 201306/jmg_1514.jpg                   | 1 -
- 201306/jmg_1515.jpg                   | 1 -
- 201306/jmg_1517.jpg                   | 1 -
- 201306/jmg_1520.jpg                   | 1 -
- 201306/jmg_1521.jpg                   | 1 -
- 201306/jmg_1526.jpg                   | 1 -
- 201306/jmg_1533.jpg                   | 1 -
- 201306/jmg_1540.jpg                   | 1 -
- 201306/jmg_1546.jpg                   | 1 -
- 201306/jmg_1547.jpg                   | 1 -
- 201306/jmg_1549.jpg                   | 1 -
- 201306/jmg_1550.jpg                   | 1 -
- 201306/jmg_1551.jpg                   | 1 -
- 201306/jmg_1552.jpg                   | 1 -
- 201306/jmg_1553.jpg                   | 1 -
- 201306/jmg_1555.jpg                   | 1 -
- 201306/jmg_1556.jpg                   | 1 -
- 201306/jmg_1557.jpg                   | 1 -
- 201306/jmg_1558.jpg                   | 1 -
- 201306/jmg_1559.jpg                   | 1 -
- 201306/jmg_1560.jpg                   | 1 -
- 201306/jmg_1562.jpg                   | 1 -
- 201306/jmg_1566.jpg                   | 1 -
- 201306/jmg_1568.jpg                   | 1 -
- 201306/jmg_1570.jpg                   | 1 -
- 201306/jmg_1571.jpg                   | 1 -
- 201306/jmg_1572.jpg                   | 1 -
- 201306/jmg_1574.jpg                   | 1 -
- 201306/jmg_1575.jpg                   | 1 -
- 201306/jmg_1576.jpg                   | 1 -
- 201306/jmg_1577.jpg                   | 1 -
- 201306/jmg_1578.jpg                   | 1 -
- 201306/jmg_1579.jpg                   | 1 -
- 201306/jmg_1579_raw.jpg               | 1 -
- 201306/jmg_1581.jpg                   | 1 -
- 201306/jmg_1583.jpg                   | 1 -
- 201306/jmg_1583_cut.jpg               | 1 -
- 201306/jmg_1583_raw.jpg               | 1 -
- 201306/jmg_1584.jpg                   | 1 -
- 201306/jmg_1586.jpg                   | 1 -
- 201306/jmg_1587.jpg                   | 1 -
- 201306/jmg_1588.jpg                   | 1 -
- 201306/jmg_1589.jpg                   | 1 -
- 201306/jmg_1591.jpg                   | 1 -
- 201306/jmg_1592.jpg                   | 1 -
- 201306/jmg_1593.jpg                   | 1 -
- 201306/jmg_1593_raw.jpg               | 1 -
- 201306/jmg_1594.jpg                   | 1 -
- 201306/jmg_1594_raw.jpg               | 1 -
- 201306/jmg_1595.jpg                   | 1 -
- 201306/jmg_1596.jpg                   | 1 -
- 201306/jmg_1597.jpg                   | 1 -
- 201306/jmg_1599.jpg                   | 1 -
- 201306/jmg_1626.jpg                   | 1 -
- 201306/jmg_1628.jpg                   | 1 -
- 201306/jmg_1629.jpg                   | 1 -
- 201306/jmg_1630.jpg                   | 1 -
- 201306/jmg_1631.jpg                   | 1 -
- 201306/jmg_1633.jpg                   | 1 -
- 201306/jmg_1635.jpg                   | 1 -
- 201306/jmg_1636.jpg                   | 1 -
- 201306/jmg_1637.jpg                   | 1 -
- 201306/jmg_1638.jpg                   | 1 -
- 201306/jmg_1640.jpg                   | 1 -
- 201306/jmg_1642.jpg                   | 1 -
- 201306/jmg_1643.jpg                   | 1 -
- 201306/jmg_1644.jpg                   | 1 -
- 201306/jmg_1647.jpg                   | 1 -
- 201306/jmg_1649.jpg                   | 1 -
- 201306/jmg_1650.jpg                   | 1 -
- 201306/jmg_1651.jpg                   | 1 -
- 201306/jmg_1652.jpg                   | 1 -
- 201306/jmg_1653.jpg                   | 1 -
- 201306/jmg_1655.jpg                   | 1 -
- 201306/jmg_1656.jpg                   | 1 -
- 201306/jmg_1660.jpg                   | 1 -
- 201306/jmg_1667.jpg                   | 1 -
- 201306/jmg_1682.jpg                   | 1 -
- 201306/jmg_1688.jpg                   | 1 -
- 201306/jmg_1689.jpg                   | 1 -
- 201306/jmg_1701.jpg                   | 1 -
- 201306/jmg_1702.jpg                   | 1 -
- 201306/jmg_1703.jpg                   | 1 -
- 201306/jmg_1710.jpg                   | 1 -
- 201306/jmg_1710_raw.jpg               | 1 -
- 201306/jmg_1715.jpg                   | 1 -
- 201306/jmg_1716.jpg                   | 1 -
- 201306/jmg_1719.jpg                   | 1 -
- 201306/jmg_1722.jpg                   | 1 -
- 201306/jmg_1723.jpg                   | 1 -
- 201306/jmg_1729.cr2                   | 1 -
- 201308/jmg_2038.jpg                   | 1 -
- 201308/jmg_2039.jpg                   | 1 -
- 201308/jmg_2040.jpg                   | 1 -
- 201308/jmg_2041.jpg                   | 1 -
- 201308/jmg_2042.jpg                   | 1 -
- 201308/jmg_2043.jpg                   | 1 -
- 201308/jmg_2045.jpg                   | 1 -
- 201308/jmg_2047.jpg                   | 1 -
- 201308/jmg_2048.jpg                   | 1 -
- 201308/jmg_2049.jpg                   | 1 -
- 201308/jmg_2050.jpg                   | 1 -
- 201308/jmg_2051.jpg                   | 1 -
- 201308/jmg_2052.jpg                   | 1 -
- 201308/jmg_2053.jpg                   | 1 -
- 201308/jmg_2054.jpg                   | 1 -
- 201308/jmg_2055.jpg                   | 1 -
- 201308/jmg_2056.jpg                   | 1 -
- 201308/jmg_2057.jpg                   | 1 -
- 201308/jmg_2058.jpg                   | 1 -
- 201308/jmg_2059.jpg                   | 1 -
- 201308/jmg_2060.jpg                   | 1 -
- 201308/jmg_2061.jpg                   | 1 -
- 201308/jmg_2062.jpg                   | 1 -
- 201308/jmg_2089.cr2                   | 1 -
- 201308/jmg_2089.jpg                   | 1 -
- 201308/jmg_2089_raw.jpg               | 1 -
- 201308/jmg_2090.jpg                   | 1 -
- 201308/jmg_2091.jpg                   | 1 -
- 201308/jmg_2092.jpg                   | 1 -
- 201308/jmg_2093.jpg                   | 1 -
- 201308/jmg_2096.jpg                   | 1 -
- 201308/jmg_2097.jpg                   | 1 -
- 201308/jmg_2098.jpg                   | 1 -
- 201308/jmg_2099.cr2                   | 1 -
- 201308/jmg_2099.jpg                   | 1 -
- 201308/jmg_2099_raw.jpg               | 1 -
- 201308/jmg_2100.cr2                   | 1 -
- 201308/jmg_2100.jpg                   | 1 -
- 201308/jmg_2100_raw.jpg               | 1 -
- 201308/jmg_2102.jpg                   | 1 -
- 201308/jmg_2103.jpg                   | 1 -
- 201308/jmg_2104.jpg                   | 1 -
- 201308/jmg_2105.jpg                   | 1 -
- 201308/jmg_2106.jpg                   | 1 -
- 201308/jmg_2107.jpg                   | 1 -
- 201308/jmg_2108.jpg                   | 1 -
- 201308/jmg_2109.jpg                   | 1 -
- 201308/jmg_2110.jpg                   | 1 -
- 201308/jmg_2111.jpg                   | 1 -
- 201308/jmg_2112.jpg                   | 1 -
- 201308/jmg_2113.jpg                   | 1 -
- 201308/jmg_2114.jpg                   | 1 -
- 201308/jmg_2115.jpg                   | 1 -
- 201308/jmg_2117.jpg                   | 1 -
- 201308/jmg_2118.jpg                   | 1 -
- 201308/jmg_2119.jpg                   | 1 -
- 201308/jmg_2120.jpg                   | 1 -
- 201308/jmg_2122.jpg                   | 1 -
- 201308/jmg_2125.jpg                   | 1 -
- 201308/jmg_2127.jpg                   | 1 -
- 201308/jmg_2129.jpg                   | 1 -
- 201308/jmg_2130.jpg                   | 1 -
- 201308/jmg_2132.jpg                   | 1 -
- 201308/jmg_2134.jpg                   | 1 -
- 201308/jmg_2135.jpg                   | 1 -
- 201308/jmg_2136.jpg                   | 1 -
- 201308/jmg_2137.jpg                   | 1 -
- 201308/jmg_2138.jpg                   | 1 -
- 201308/jmg_2148.jpg                   | 1 -
- 201308/jmg_2150.jpg                   | 1 -
- 201308/jmg_2151.jpg                   | 1 -
- 201308/jmg_2156.jpg                   | 1 -
- 201308/jmg_2158.cr2                   | 1 -
- 201308/jmg_2158.jpg                   | 1 -
- 201308/jmg_2159.jpg                   | 1 -
- 201308/jmg_2160.jpg                   | 1 -
- 201308/jmg_2161.jpg                   | 1 -
- 201308/jmg_2162.jpg                   | 1 -
- 201308/jmg_2165.jpg                   | 1 -
- 201308/jmg_2166.jpg                   | 1 -
- 201308/jmg_2168.jpg                   | 1 -
- 201308/jmg_2169.jpg                   | 1 -
- 201308/jmg_2171.jpg                   | 1 -
- 201308/jmg_2173.jpg                   | 1 -
- 201308/jmg_2174.jpg                   | 1 -
- 201308/jmg_2175.jpg                   | 1 -
- 201308/jmg_2177.jpg                   | 1 -
- 201308/jmg_2178.jpg                   | 1 -
- 201308/jmg_2180.jpg                   | 1 -
- 201308/jmg_2181.jpg                   | 1 -
- 201308/jmg_2182.jpg                   | 1 -
- 201308/jmg_2183.jpg                   | 1 -
- 201308/jmg_2184.jpg                   | 1 -
- 201308/jmg_2187.jpg                   | 1 -
- 201308/jmg_2188.jpg                   | 1 -
- 201308/jmg_2189.jpg                   | 1 -
- 201308/jmg_2191.cr2                   | 1 -
- 201308/jmg_2191.jpg                   | 1 -
- 201308/jmg_2193.cr2                   | 1 -
- 201308/jmg_2193.jpg                   | 1 -
- 201308/jmg_2194.cr2                   | 1 -
- 201308/jmg_2194.jpg                   | 1 -
- 201308/jmg_2197.cr2                   | 1 -
- 201308/jmg_2197.jpg                   | 1 -
- 201308/jmg_2200.cr2                   | 1 -
- 201308/jmg_2200.jpg                   | 1 -
- 201308/jmg_2201.cr2                   | 1 -
- 201308/jmg_2201.jpg                   | 1 -
- 201308/jmg_2202.cr2                   | 1 -
- 201308/jmg_2202.jpg                   | 1 -
- 201308/jmg_2209.jpg                   | 1 -
- 201308/jmg_2210.jpg                   | 1 -
- 201308/jmg_2215.jpg                   | 1 -
- 201308/jmg_2216.jpg                   | 1 -
- 201308/jmg_2217.cr2                   | 1 -
- 201308/jmg_2217.jpg                   | 1 -
- 201308/jmg_2219.cr2                   | 1 -
- 201308/jmg_2219.jpg                   | 1 -
- 201308/jmg_2223.jpg                   | 1 -
- 201308/jmg_2224.jpg                   | 1 -
- 201308/jmg_2225.cr2                   | 1 -
- 201308/jmg_2225.jpg                   | 1 -
- 201308/jmg_2227.jpg                   | 1 -
- 201308/jmg_2228.jpg                   | 1 -
- 201308/jmg_2235.jpg                   | 1 -
- 201308/jmg_2237.jpg                   | 1 -
- 201308/jmg_2238.jpg                   | 1 -
- 201308/jmg_2239.cr2                   | 1 -
- 201308/jmg_2239.jpg                   | 1 -
- 201308/jmg_2239_raw.jpg               | 1 -
- 201308/jmg_2240.jpg                   | 1 -
- 201308/jmg_2243.jpg                   | 1 -
- 201308/jmg_2244.jpg                   | 1 -
- 201308/jmg_2245.jpg                   | 1 -
- 201308/jmg_2247.cr2                   | 1 -
- 201308/jmg_2247.jpg                   | 1 -
- 201308/jmg_2249.jpg                   | 1 -
- 201308/jmg_2250.cr2                   | 1 -
- 201308/jmg_2250.jpg                   | 1 -
- 201308/jmg_2252.jpg                   | 1 -
- 201308/jmg_2253.jpg                   | 1 -
- 201308/jmg_2254.jpg                   | 1 -
- incoming/5d/201203/jmg_8701.cr2       | 1 +
- incoming/5d/201203/jmg_8702.jpg       | 1 +
- incoming/5d/201203/jmg_8705.jpg       | 1 +
- incoming/5d/201203/jmg_8711.jpg       | 1 +
- incoming/5d/201203/jmg_8717.jpg       | 1 +
- incoming/5d/201203/jmg_8718.jpg       | 1 +
- incoming/5d/201203/jmg_8719.jpg       | 1 +
- incoming/5d/201203/jmg_8721.jpg       | 1 +
- incoming/5d/201203/jmg_8725.jpg       | 1 +
- incoming/5d/201203/jmg_8726.jpg       | 1 +
- incoming/5d/201203/jmg_8731.jpg       | 1 +
- incoming/5d/201203/jmg_8745.jpg       | 1 +
- incoming/5d/201203/jmg_8747_raw.jpg   | 1 +
- incoming/5d/201203/jmg_8750.cr2       | 1 +
- incoming/5d/201203/jmg_8750.jpg       | 1 +
- incoming/5d/201207/jmg_9048.jpg       | 1 +
- incoming/5d/201207/jmg_9053.jpg       | 1 +
- incoming/5d/201207/jmg_9054.jpg       | 1 +
- incoming/5d/201207/jmg_9069.cr2       | 1 +
- incoming/5d/201207/jmg_9069.jpg       | 1 +
- incoming/5d/201207/jmg_9070.cr2       | 1 +
- incoming/5d/201207/jmg_9070.jpg       | 1 +
- incoming/5d/201207/jmg_9072.cr2       | 1 +
- incoming/5d/201207/jmg_9072.jpg       | 1 +
- incoming/5d/201207/jmg_9076.cr2       | 1 +
- incoming/5d/201207/jmg_9076.jpg       | 1 +
- incoming/5d/201302/jmg_0502.cr2       | 1 +
- incoming/5d/201302/jmg_0502.jpg       | 1 +
- incoming/5d/201302/jmg_0503.jpg       | 1 +
- incoming/5d/201302/jmg_0507.jpg       | 1 +
- incoming/5d/201302/jmg_0510.jpg       | 1 +
- incoming/5d/201302/jmg_0512.jpg       | 1 +
- incoming/5d/201302/jmg_0513.jpg       | 1 +
- incoming/5d/201302/jmg_0514.jpg       | 1 +
- incoming/5d/201302/jmg_0516.jpg       | 1 +
- incoming/5d/201302/jmg_0517.jpg       | 1 +
- incoming/5d/201302/jmg_0518.jpg       | 1 +
- incoming/5d/201302/jmg_0521.jpg       | 1 +
- incoming/5d/201302/jmg_0522.jpg       | 1 +
- incoming/5d/201302/jmg_0523.jpg       | 1 +
- incoming/5d/201302/jmg_0524.jpg       | 1 +
- incoming/5d/201302/jmg_0526.jpg       | 1 +
- incoming/5d/201302/jmg_0527.jpg       | 1 +
- incoming/5d/201302/jmg_0528.jpg       | 1 +
- incoming/5d/201302/jmg_0532.cr2       | 1 +
- incoming/5d/201302/jmg_0532.jpg       | 1 +
- incoming/5d/201302/jmg_0534.jpg       | 1 +
- incoming/5d/201302/jmg_0535.jpg       | 1 +
- incoming/5d/201302/jmg_0537.jpg       | 1 +
- incoming/5d/201302/jmg_0539.jpg       | 1 +
- incoming/5d/201302/jmg_0541.jpg       | 1 +
- incoming/5d/201302/jmg_0543.jpg       | 1 +
- incoming/5d/jmg_0021.jpg              | 1 +
- incoming/5d/jmg_0025.jpg              | 1 +
- incoming/5d/jmg_0026.jpg              | 1 +
- incoming/5d/jmg_0027.jpg              | 1 +
- incoming/5d/jmg_0034.jpg              | 1 +
- incoming/5d/jmg_0035.jpg              | 1 +
- incoming/5d/jmg_0036.jpg              | 1 +
- incoming/5d/jmg_0130.jpg              | 1 +
- incoming/5d/jmg_0131.jpg              | 1 +
- incoming/5d/jmg_0133.jpg              | 1 +
- incoming/5d/jmg_0155.jpg              | 1 +
- incoming/5d/jmg_0156.jpg              | 1 +
- incoming/5d/jmg_0158.cr2              | 1 +
- incoming/5d/jmg_0165.cr2              | 1 +
- incoming/5d/jmg_0166.cr2              | 1 +
- incoming/5d/jmg_0178.cr2              | 1 +
- incoming/5d/jmg_0179.jpg              | 1 +
- incoming/5d/jmg_0180.cr2              | 1 +
- incoming/5d/jmg_0184.jpg              | 1 +
- incoming/5d/jmg_0185.cr2              | 1 +
- incoming/5d/jmg_0187.cr2              | 1 +
- incoming/5d/jmg_0310.jpg              | 1 +
- incoming/5d/jmg_0312.jpg              | 1 +
- incoming/5d/jmg_0315.jpg              | 1 +
- incoming/5d/jmg_0340.jpg              | 1 +
- incoming/5d/jmg_0357.jpg              | 1 +
- incoming/5d/jmg_0364.jpg              | 1 +
- incoming/5d/jmg_0365.jpg              | 1 +
- incoming/5d/jmg_0368.jpg              | 1 +
- incoming/5d/jmg_0374.jpg              | 1 +
- incoming/5d/jmg_0375.jpg              | 1 +
- incoming/5d/jmg_0386.jpg              | 1 +
- incoming/5d/jmg_0399.jpg              | 1 +
- incoming/5d/jmg_0411.jpg              | 1 +
- incoming/5d/jmg_0418.jpg              | 1 +
- incoming/5d/jmg_0476.cr2              | 1 +
- incoming/5d/jmg_0476.jpg              | 1 +
- incoming/5d/jmg_0503.jpg              | 1 +
- incoming/5d/jmg_0507.cr2              | 1 +
- incoming/5d/jmg_0513.cr2              | 1 +
- incoming/5d/jmg_0513.jpg              | 1 +
- incoming/5d/jmg_0516.cr2              | 1 +
- incoming/5d/jmg_0517.cr2              | 1 +
- incoming/5d/jmg_0518.jpg              | 1 +
- incoming/5d/jmg_0522.cr2              | 1 +
- incoming/5d/jmg_0524.cr2              | 1 +
- incoming/5d/jmg_0524.jpg              | 1 +
- incoming/5d/jmg_0530.jpg              | 1 +
- incoming/5d/jmg_0541.cr2              | 1 +
- incoming/5d/jmg_0550.jpg              | 1 +
- incoming/5d/jmg_0554.jpg              | 1 +
- incoming/5d/jmg_0555.jpg              | 1 +
- incoming/5d/jmg_0558.jpg              | 1 +
- incoming/5d/jmg_0563.jpg              | 1 +
- incoming/5d/jmg_0573.jpg              | 1 +
- incoming/5d/jmg_0575.cr2              | 1 +
- incoming/5d/jmg_0578.cr2              | 1 +
- incoming/5d/jmg_0579.cr2              | 1 +
- incoming/5d/jmg_0582.jpg              | 1 +
- incoming/5d/jmg_0593.cr2              | 1 +
- incoming/5d/jmg_0594.cr2              | 1 +
- incoming/5d/jmg_0594.jpg              | 1 +
- incoming/5d/jmg_0595.cr2              | 1 +
- incoming/5d/jmg_0600.jpg              | 1 +
- incoming/5d/jmg_0606.cr2              | 1 +
- incoming/5d/jmg_0607.jpg              | 1 +
- incoming/5d/jmg_0610.cr2              | 1 +
- incoming/5d/jmg_0610.jpg              | 1 +
- incoming/5d/jmg_0612.jpg              | 1 +
- incoming/5d/jmg_0613.cr2              | 1 +
- incoming/5d/jmg_0614.jpg              | 1 +
- incoming/5d/jmg_0619.cr2              | 1 +
- incoming/5d/jmg_0623.jpg              | 1 +
- incoming/5d/jmg_0628.cr2              | 1 +
- incoming/5d/jmg_0628.jpg              | 1 +
- incoming/5d/jmg_0639.jpg              | 1 +
- incoming/5d/jmg_0645.cr2              | 1 +
- incoming/5d/jmg_0646.jpg              | 1 +
- incoming/5d/jmg_0647.cr2              | 1 +
- incoming/5d/jmg_0648.jpg              | 1 +
- incoming/5d/jmg_0649.jpg              | 1 +
- incoming/5d/jmg_0655.jpg              | 1 +
- incoming/5d/jmg_0667.jpg              | 1 +
- incoming/5d/jmg_0670.jpg              | 1 +
- incoming/5d/jmg_0673.jpg              | 1 +
- incoming/5d/jmg_0679.jpg              | 1 +
- incoming/5d/jmg_0685.jpg              | 1 +
- incoming/5d/jmg_0699.cr2              | 1 +
- incoming/5d/jmg_0700.cr2              | 1 +
- incoming/5d/jmg_0701.cr2              | 1 +
- incoming/5d/jmg_0708.jpg              | 1 +
- incoming/5d/jmg_0718.jpg              | 1 +
- incoming/5d/jmg_0726.cr2              | 1 +
- incoming/5d/jmg_0728.jpg              | 1 +
- incoming/5d/jmg_0730.jpg              | 1 +
- incoming/5d/jmg_0734.jpg              | 1 +
- incoming/5d/jmg_0740.jpg              | 1 +
- incoming/5d/jmg_0743.cr2              | 1 +
- incoming/5d/jmg_0744.cr2              | 1 +
- incoming/5d/jmg_0745.cr2              | 1 +
- incoming/5d/jmg_0747.jpg              | 1 +
- incoming/5d/jmg_0750.cr2              | 1 +
- incoming/5d/jmg_0755.cr2              | 1 +
- incoming/5d/jmg_0759.cr2              | 1 +
- incoming/5d/jmg_0760.cr2              | 1 +
- incoming/5d/jmg_0761.jpg              | 1 +
- incoming/5d/jmg_0765.jpg              | 1 +
- incoming/5d/jmg_0768.jpg              | 1 +
- incoming/5d/jmg_0771.jpg              | 1 +
- incoming/5d/jmg_0778.jpg              | 1 +
- incoming/5d/jmg_0780.jpg              | 1 +
- incoming/5d/jmg_0782.cr2              | 1 +
- incoming/5d/jmg_0786.cr2              | 1 +
- incoming/5d/jmg_0787.cr2              | 1 +
- incoming/5d/jmg_0788.cr2              | 1 +
- incoming/5d/jmg_0794.jpg              | 1 +
- incoming/5d/jmg_0796.jpg              | 1 +
- incoming/5d/jmg_0801.cr2              | 1 +
- incoming/5d/jmg_0803.cr2              | 1 +
- incoming/5d/jmg_0804.cr2              | 1 +
- incoming/5d/jmg_0812.jpg              | 1 +
- incoming/5d/jmg_0819.jpg              | 1 +
- incoming/5d/jmg_0827.jpg              | 1 +
- incoming/5d/jmg_0830.jpg              | 1 +
- incoming/5d/jmg_0842.jpg              | 1 +
- incoming/5d/jmg_0846.jpg              | 1 +
- incoming/5d/jmg_0857.cr2              | 1 +
- incoming/5d/jmg_0863.jpg              | 1 +
- incoming/5d/jmg_0866.cr2              | 1 +
- incoming/5d/jmg_0868.cr2              | 1 +
- incoming/5d/jmg_0868.jpg              | 1 +
- incoming/5d/jmg_0870.jpg              | 1 +
- incoming/5d/jmg_0877.jpg              | 1 +
- incoming/5d/jmg_0882.cr2              | 1 +
- incoming/5d/jmg_0883.jpg              | 1 +
- incoming/5d/jmg_0888.jpg              | 1 +
- incoming/5d/jmg_0891.jpg              | 1 +
- incoming/5d/jmg_0894.cr2              | 1 +
- incoming/5d/jmg_0896.cr2              | 1 +
- incoming/5d/jmg_0897.cr2              | 1 +
- incoming/5d/jmg_0898.jpg              | 1 +
- incoming/5d/jmg_0899.cr2              | 1 +
- incoming/5d/jmg_0900.jpg              | 1 +
- incoming/5d/jmg_0905.jpg              | 1 +
- incoming/5d/jmg_0908.jpg              | 1 +
- incoming/5d/jmg_0914.jpg              | 1 +
- incoming/5d/jmg_0915.jpg              | 1 +
- incoming/5d/jmg_0916.jpg              | 1 +
- incoming/5d/jmg_0923.jpg              | 1 +
- incoming/5d/jmg_0924.jpg              | 1 +
- incoming/5d/jmg_0926.jpg              | 1 +
- incoming/5d/jmg_0928.jpg              | 1 +
- incoming/5d/jmg_0929.jpg              | 1 +
- incoming/5d/jmg_0936.jpg              | 1 +
- incoming/5d/jmg_0942.jpg              | 1 +
- incoming/5d/jmg_0944.jpg              | 1 +
- incoming/5d/jmg_0948.jpg              | 1 +
- incoming/5d/jmg_0960.jpg              | 1 +
- incoming/5d/jmg_0966.jpg              | 1 +
- incoming/5d/jmg_0970.cr2              | 1 +
- incoming/5d/jmg_0970.jpg              | 1 +
- incoming/5d/jmg_0972.jpg              | 1 +
- incoming/5d/jmg_0976.jpg              | 1 +
- incoming/5d/jmg_0983.cr2              | 1 +
- incoming/5d/jmg_0985.cr2              | 1 +
- incoming/5d/jmg_0985.jpg              | 1 +
- incoming/5d/jmg_0994.jpg              | 1 +
- incoming/5d/jmg_1005.jpg              | 2 +-
- incoming/5d/jmg_1009.jpg              | 2 +-
- incoming/5d/jmg_1012.jpg              | 2 +-
- incoming/5d/jmg_1020.jpg              | 2 +-
- incoming/5d/jmg_1021.jpg              | 2 +-
- incoming/5d/jmg_1032.jpg              | 2 +-
- incoming/5d/jmg_1033.jpg              | 2 +-
- incoming/5d/jmg_1037.jpg              | 2 +-
- incoming/5d/jmg_1039.jpg              | 2 +-
- incoming/5d/jmg_1048.jpg              | 2 +-
- incoming/5d/jmg_1051.jpg              | 2 +-
- incoming/5d/jmg_1063.jpg              | 2 +-
- incoming/5d/jmg_1064.jpg              | 2 +-
- incoming/5d/jmg_1067.jpg              | 2 +-
- incoming/5d/jmg_1116.jpg              | 2 +-
- incoming/5d/jmg_1118.jpg              | 2 +-
- incoming/5d/jmg_1125.jpg              | 2 +-
- incoming/5d/jmg_1126.jpg              | 2 +-
- incoming/5d/jmg_1129.jpg              | 2 +-
- incoming/5d/jmg_1133.jpg              | 2 +-
- incoming/5d/jmg_1138.jpg              | 2 +-
- incoming/5d/jmg_1139.jpg              | 2 +-
- incoming/5d/jmg_1143.jpg              | 2 +-
- incoming/5d/jmg_1149.jpg              | 2 +-
- incoming/5d/jmg_1150.jpg              | 2 +-
- incoming/5d/jmg_1155.jpg              | 2 +-
- incoming/5d/jmg_1160.jpg              | 2 +-
- incoming/5d/jmg_1168.jpg              | 2 +-
- incoming/5d/jmg_1173.jpg              | 2 +-
- incoming/5d/jmg_1175.jpg              | 2 +-
- incoming/5d/jmg_1177.jpg              | 2 +-
- incoming/5d/jmg_1179.jpg              | 2 +-
- incoming/5d/jmg_1183.jpg              | 2 +-
- incoming/5d/jmg_1185.jpg              | 2 +-
- incoming/5d/jmg_1189.jpg              | 2 +-
- incoming/5d/jmg_1192.jpg              | 2 +-
- incoming/5d/jmg_1199.jpg              | 2 +-
- incoming/5d/jmg_1205.jpg              | 2 +-
- incoming/5d/jmg_1209.cr2              | 1 +
- incoming/5d/jmg_1209.jpg              | 1 +
- incoming/5d/jmg_1211.cr2              | 1 +
- incoming/5d/jmg_1211.jpg              | 1 +
- incoming/5d/jmg_1217.cr2              | 1 +
- incoming/5d/jmg_1467.cr2              | 1 +
- incoming/5d/jmg_1469.jpg              | 1 +
- incoming/5d/jmg_1470.cr2              | 1 +
- incoming/5d/jmg_1471.cr2              | 1 +
- incoming/5d/jmg_1472.cr2              | 1 +
- incoming/5d/jmg_1477.cr2              | 1 +
- incoming/5d/jmg_1477.jpg              | 1 +
- incoming/5d/jmg_1481.cr2              | 1 +
- incoming/5d/jmg_1483.cr2              | 1 +
- incoming/5d/jmg_1485.jpg              | 1 +
- incoming/5d/jmg_1488.jpg              | 1 +
- incoming/5d/jmg_1491.jpg              | 1 +
- incoming/5d/jmg_1496.cr2              | 1 +
- incoming/5d/jmg_1502.jpg              | 1 +
- incoming/5d/jmg_1503.cr2              | 1 +
- incoming/5d/jmg_1504.jpg              | 1 +
- incoming/5d/jmg_1507.jpg              | 1 +
- incoming/5d/jmg_1515.jpg              | 1 +
- incoming/5d/jmg_1520.jpg              | 1 +
- incoming/5d/jmg_1523.jpg              | 1 +
- incoming/5d/jmg_1525.jpg              | 1 +
- incoming/5d/jmg_1539.jpg              | 1 +
- incoming/5d/jmg_1542.jpg              | 1 +
- incoming/5d/jmg_1546.jpg              | 1 +
- incoming/5d/jmg_1547.cr2              | 1 +
- incoming/5d/jmg_1549.jpg              | 1 +
- incoming/5d/jmg_1552.jpg              | 1 +
- incoming/5d/jmg_1554.cr2              | 1 +
- incoming/5d/jmg_1555.cr2              | 1 +
- incoming/5d/jmg_1556.cr2              | 1 +
- incoming/5d/jmg_1559.cr2              | 1 +
- incoming/5d/jmg_1560.cr2              | 1 +
- incoming/5d/jmg_1561.cr2              | 1 +
- incoming/5d/jmg_1562.cr2              | 1 +
- incoming/5d/jmg_1565.cr2              | 1 +
- incoming/5d/jmg_1567.cr2              | 1 +
- incoming/5d/jmg_1572.cr2              | 1 +
- incoming/5d/jmg_1577.cr2              | 1 +
- incoming/5d/jmg_1578.jpg              | 1 +
- incoming/5d/jmg_1583_cut.jpg          | 1 +
- incoming/5d/jmg_1583_raw.jpg          | 1 +
- incoming/5d/jmg_1592.cr2              | 1 +
- incoming/5d/jmg_1593.jpg              | 1 +
- incoming/5d/jmg_1626.cr2              | 1 +
- incoming/5d/jmg_1627.jpg              | 1 +
- incoming/5d/jmg_1628.cr2              | 1 +
- incoming/5d/jmg_1629.jpg              | 1 +
- incoming/5d/jmg_1630.cr2              | 1 +
- incoming/5d/jmg_1631.cr2              | 1 +
- incoming/5d/jmg_1633.cr2              | 1 +
- incoming/5d/jmg_1638.jpg              | 1 +
- incoming/5d/jmg_1639.cr2              | 1 +
- incoming/5d/jmg_1646.cr2              | 1 +
- incoming/5d/jmg_1646.jpg              | 1 +
- incoming/5d/jmg_1650.jpg              | 1 +
- incoming/5d/jmg_1651.cr2              | 1 +
- incoming/5d/jmg_1654.cr2              | 1 +
- incoming/5d/jmg_1656.jpg              | 1 +
- incoming/5d/jmg_1677.jpg              | 1 +
- incoming/5d/jmg_1689.jpg              | 1 +
- incoming/5d/jmg_1701.jpg              | 1 +
- incoming/5d/jmg_1703.jpg              | 1 +
- incoming/5d/jmg_1723.jpg              | 1 +
- incoming/5d/jmg_2039.jpg              | 1 +
- incoming/5d/jmg_2041.jpg              | 1 +
- incoming/5d/jmg_2048.cr2              | 1 +
- incoming/5d/jmg_2052.jpg              | 1 +
- incoming/5d/jmg_2061.jpg              | 1 +
- incoming/5d/jmg_2064_raw.jpg          | 1 -
- incoming/5d/jmg_2065_mo.jpg           | 1 -
- incoming/5d/jmg_2065_raw.jpg          | 1 -
- incoming/5d/jmg_2066_mo.jpg           | 1 -
- incoming/5d/jmg_2066_raw.jpg          | 1 -
- incoming/5d/jmg_2090.jpg              | 1 +
- incoming/5d/jmg_2093.jpg              | 1 +
- incoming/5d/jmg_2100.cr2              | 1 +
- incoming/5d/jmg_2103.jpg              | 1 +
- incoming/5d/jmg_2107.jpg              | 1 +
- incoming/5d/jmg_2108.jpg              | 1 +
- incoming/5d/jmg_2112.jpg              | 1 +
- incoming/5d/jmg_2118.jpg              | 1 +
- incoming/5d/jmg_2119.jpg              | 1 +
- incoming/5d/jmg_2122.jpg              | 1 +
- incoming/5d/jmg_2125.jpg              | 1 +
- incoming/5d/jmg_2137.jpg              | 1 +
- incoming/5d/jmg_2149.jpg              | 1 +
- incoming/5d/jmg_2150.jpg              | 1 +
- incoming/5d/jmg_2158.cr2              | 1 +
- incoming/5d/jmg_2160.jpg              | 1 +
- incoming/5d/jmg_2165.jpg              | 1 +
- incoming/5d/jmg_2188.jpg              | 1 +
- incoming/5d/jmg_2189.jpg              | 1 +
- incoming/5d/jmg_2193.jpg              | 1 +
- incoming/5d/jmg_2194.cr2              | 1 +
- incoming/5d/jmg_2200.jpg              | 1 +
- incoming/5d/jmg_2201.cr2              | 1 +
- incoming/5d/jmg_2201.jpg              | 1 +
- incoming/5d/jmg_2210.jpg              | 1 +
- incoming/5d/jmg_2215.cr2              | 1 +
- incoming/5d/jmg_2216.cr2              | 1 +
- incoming/5d/jmg_2216.jpg              | 1 +
- incoming/5d/jmg_2224.jpg              | 1 +
- incoming/5d/jmg_2235.jpg              | 1 +
- incoming/5d/jmg_2238.jpg              | 1 +
- incoming/5d/jmg_2239.cr2              | 1 +
- incoming/5d/jmg_2239.jpg              | 1 +
- incoming/5d/jmg_2240.jpg              | 1 +
- incoming/5d/jmg_2244.jpg              | 1 +
- incoming/5d/jmg_2247.jpg              | 1 +
- incoming/5d/jmg_7250.cr2              | 1 +
- incoming/5d/jmg_7250.jpg              | 1 +
- incoming/5d/jmg_7256.jpg              | 1 +
- incoming/5d/jmg_7257.cr2              | 1 +
- incoming/5d/jmg_7259.cr2              | 1 +
- incoming/5d/jmg_7263.jpg              | 1 +
- incoming/5d/jmg_7265.cr2              | 1 +
- incoming/5d/jmg_7269.cr2              | 1 +
- incoming/5d/jmg_7270.cr2              | 1 +
- incoming/5d/jmg_7279.cr2              | 1 +
- incoming/5d/jmg_7286.cr2              | 1 +
- incoming/5d/jmg_7286.jpg              | 1 +
- incoming/5d/jmg_7290.cr2              | 1 +
- incoming/5d/jmg_7290.jpg              | 1 +
- incoming/5d/jmg_7293.cr2              | 1 +
- incoming/5d/jmg_7296.cr2              | 1 +
- incoming/5d/jmg_7299.jpg              | 1 +
- incoming/5d/jmg_7300.cr2              | 1 +
- incoming/5d/jmg_7300.jpg              | 1 +
- incoming/5d/jmg_7305_raw.jpg          | 1 +
- incoming/5d/jmg_8532.cr2              | 1 +
- incoming/5d/jmg_8533.cr2              | 1 +
- incoming/5d/jmg_8534.cr2              | 1 +
- incoming/5d/jmg_8536.jpg              | 1 +
- incoming/5d/jmg_8538.cr2              | 1 +
- incoming/5d/jmg_8549.cr2              | 1 +
- incoming/5d/jmg_8549.jpg              | 1 +
- incoming/5d/jmg_8552.cr2              | 1 +
- incoming/5d/jmg_8557.cr2              | 1 +
- incoming/5d/jmg_8560.cr2              | 1 +
- incoming/5d/jmg_8565.cr2              | 1 +
- incoming/5d/jmg_8566.cr2              | 1 +
- incoming/5d/jmg_8569.jpg              | 1 +
- incoming/5d/jmg_8575.jpg              | 1 +
- incoming/5d/jmg_8576.jpg              | 1 +
- incoming/5d/jmg_8578.cr2              | 1 +
- incoming/5d/jmg_8579.cr2              | 1 +
- incoming/5d/jmg_8580.jpg              | 1 +
- incoming/5d/jmg_8583.cr2              | 1 +
- incoming/5d/jmg_8588.cr2              | 1 +
- incoming/5d/jmg_8589.cr2              | 1 +
- incoming/5d/jmg_8595.jpg              | 1 +
- incoming/5d/jmg_8597.jpg              | 1 +
- incoming/5d/jmg_8599.jpg              | 1 +
- incoming/5d/jmg_8602.cr2              | 1 +
- incoming/5d/jmg_8603.cr2              | 1 +
- incoming/5d/jmg_8606.cr2              | 1 +
- incoming/5d/jmg_8606.jpg              | 1 +
- incoming/5d/jmg_8609.jpg              | 1 +
- incoming/5d/jmg_8613.jpg              | 1 +
- incoming/5d/jmg_8615.cr2              | 1 +
- incoming/5d/jmg_8617.jpg              | 1 +
- incoming/5d/jmg_8619.cr2              | 1 +
- incoming/5d/jmg_8620.jpg              | 1 +
- incoming/5d/jmg_8625.jpg              | 1 +
- incoming/5d/jmg_8627.jpg              | 1 +
- incoming/5d/jmg_8628.jpg              | 1 +
- incoming/5d/jmg_8632.cr2              | 1 +
- incoming/5d/jmg_8636.cr2              | 1 +
- incoming/5d/jmg_8636.jpg              | 1 +
- incoming/5d/jmg_8637.cr2              | 1 +
- incoming/5d/jmg_8639.jpg              | 1 +
- incoming/5d/jmg_8640.cr2              | 1 +
- incoming/5d/jmg_8655.jpg              | 1 +
- incoming/5d/jmg_8657.jpg              | 1 +
- incoming/5d/jmg_8670.cr2              | 1 +
- incoming/5d/jmg_8673.jpg              | 1 +
- incoming/5d/jmg_8674.cr2              | 1 +
- incoming/5d/jmg_8676.cr2              | 1 +
- incoming/5d/jmg_8676.jpg              | 1 +
- incoming/5d/jmg_8677.cr2              | 1 +
- incoming/5d/jmg_8681.jpg              | 1 +
- incoming/5d/jmg_8682.cr2              | 1 +
- incoming/5d/jmg_8702.cr2              | 1 +
- incoming/5d/jmg_8702.jpg              | 1 +
- incoming/5d/jmg_8707.jpg              | 1 +
- incoming/5d/jmg_8714.jpg              | 1 +
- incoming/5d/jmg_8716.jpg              | 1 +
- incoming/5d/jmg_8717.cr2              | 1 +
- incoming/5d/jmg_8719.jpg              | 1 +
- incoming/5d/jmg_8721.jpg              | 1 +
- incoming/5d/jmg_8727.cr2              | 1 +
- incoming/5d/jmg_8730.jpg              | 1 +
- incoming/5d/jmg_8736.cr2              | 1 +
- incoming/5d/jmg_8737.cr2              | 1 +
- incoming/5d/jmg_8742.cr2              | 1 +
- incoming/5d/jmg_8742.jpg              | 1 +
- incoming/5d/jmg_8745.jpg              | 1 +
- incoming/5d/jmg_8748.cr2              | 1 +
- incoming/5d/jmg_8748.jpg              | 1 +
- incoming/5d/jmg_8751.cr2              | 1 +
- incoming/5d/jmg_8755.cr2              | 1 +
- incoming/5d/jmg_8757.cr2              | 1 +
- incoming/5d/jmg_8760.cr2              | 1 +
- incoming/5d/jmg_8760.jpg              | 1 +
- incoming/5d/jmg_8765.cr2              | 1 +
- incoming/5d/jmg_8771.jpg              | 1 +
- incoming/5d/jmg_8801.jpg              | 1 +
- incoming/5d/jmg_8803.cr2              | 1 +
- incoming/5d/jmg_8803.jpg              | 1 +
- incoming/5d/jmg_8804.jpg              | 1 +
- incoming/5d/jmg_8805.jpg              | 1 +
- incoming/5d/jmg_8813.jpg              | 1 +
- incoming/5d/jmg_8816.cr2              | 1 +
- incoming/5d/jmg_8823.jpg              | 1 +
- incoming/5d/jmg_8827.cr2              | 1 +
- incoming/5d/jmg_8829.cr2              | 1 +
- incoming/5d/jmg_8832.jpg              | 1 +
- incoming/5d/jmg_8833.cr2              | 1 +
- incoming/5d/jmg_8837.cr2              | 1 +
- incoming/5d/jmg_8838.jpg              | 1 +
- incoming/5d/jmg_8840.jpg              | 1 +
- incoming/5d/jmg_8842.jpg              | 1 +
- incoming/5d/jmg_8844.cr2              | 1 +
- incoming/5d/jmg_8850.cr2              | 1 +
- incoming/5d/jmg_8850.jpg              | 1 +
- incoming/5d/jmg_8852.cr2              | 1 +
- incoming/5d/jmg_8853.cr2              | 1 +
- incoming/5d/jmg_8853.jpg              | 1 +
- incoming/5d/jmg_8856.cr2              | 1 +
- incoming/5d/jmg_8859.jpg              | 1 +
- incoming/5d/jmg_8863.jpg              | 1 +
- incoming/5d/jmg_8870.jpg              | 1 +
- incoming/5d/jmg_8871.cr2              | 1 +
- incoming/5d/jmg_8871.jpg              | 1 +
- incoming/5d/jmg_8881.jpg              | 1 +
- incoming/5d/jmg_8883.jpg              | 1 +
- incoming/5d/jmg_8886.jpg              | 1 +
- incoming/5d/jmg_8887.cr2              | 1 +
- incoming/5d/jmg_8889.cr2              | 1 +
- incoming/5d/jmg_8894.cr2              | 1 +
- incoming/5d/jmg_8897.cr2              | 1 +
- incoming/5d/jmg_8898.cr2              | 1 +
- incoming/5d/jmg_8900.jpg              | 1 +
- incoming/5d/jmg_8901.cr2              | 1 +
- incoming/5d/jmg_8902.cr2              | 1 +
- incoming/5d/jmg_8904.cr2              | 1 +
- incoming/5d/jmg_8906.jpg              | 1 +
- incoming/5d/jmg_8908.cr2              | 1 +
- incoming/5d/jmg_8920.cr2              | 1 +
- incoming/5d/jmg_8920.jpg              | 1 +
- incoming/5d/jmg_8922.cr2              | 1 +
- incoming/5d/jmg_8922.jpg              | 1 +
- incoming/5d/jmg_8923.cr2              | 1 +
- incoming/5d/jmg_8924.jpg              | 1 +
- incoming/5d/jmg_8925.cr2              | 1 +
- incoming/5d/jmg_8929.jpg              | 1 +
- incoming/5d/jmg_8930.jpg              | 1 +
- incoming/5d/jmg_8937.cr2              | 1 +
- incoming/5d/jmg_8939.cr2              | 1 +
- incoming/5d/jmg_8940.jpg              | 1 +
- incoming/5d/jmg_8941.jpg              | 1 +
- incoming/5d/jmg_8943.cr2              | 1 +
- incoming/5d/jmg_8944.jpg              | 1 +
- incoming/5d/jmg_8950.cr2              | 1 +
- incoming/5d/jmg_8951.jpg              | 1 +
- incoming/5d/jmg_8955.jpg              | 1 +
- incoming/5d/jmg_8959.cr2              | 1 +
- incoming/5d/jmg_8960.jpg              | 1 +
- incoming/5d/jmg_8962.cr2              | 1 +
- incoming/5d/jmg_8964.cr2              | 1 +
- incoming/5d/jmg_8965.jpg              | 1 +
- incoming/5d/jmg_8966.jpg              | 1 +
- incoming/5d/jmg_8971.jpg              | 1 +
- incoming/5d/jmg_8976.jpg              | 1 +
- incoming/5d/jmg_8978.cr2              | 1 +
- incoming/5d/jmg_8981.jpg              | 1 +
- incoming/5d/jmg_8982.jpg              | 1 +
- incoming/5d/jmg_8985.jpg              | 1 +
- incoming/5d/jmg_8988.cr2              | 1 +
- incoming/5d/jmg_8988.jpg              | 1 +
- incoming/5d/jmg_8992.cr2              | 1 +
- incoming/5d/jmg_8995.jpg              | 1 +
- incoming/5d/jmg_8996.cr2              | 1 +
- incoming/5d/jmg_8997.cr2              | 1 +
- incoming/5d/jmg_8999.cr2              | 1 +
- incoming/5d/jmg_9000.cr2              | 1 +
- incoming/5d/jmg_9015.cr2              | 1 +
- incoming/5d/jmg_9017.cr2              | 1 +
- incoming/5d/jmg_9019.cr2              | 1 +
- incoming/5d/jmg_9021.cr2              | 1 +
- incoming/5d/jmg_9021.jpg              | 1 +
- incoming/5d/jmg_9022.cr2              | 1 +
- incoming/5d/jmg_9027.cr2              | 1 +
- incoming/5d/jmg_9028.jpg              | 1 +
- incoming/5d/jmg_9031.cr2              | 1 +
- incoming/5d/jmg_9035.cr2              | 1 +
- incoming/5d/jmg_9043.jpg              | 1 +
- incoming/5d/jmg_9057.cr2              | 1 +
- incoming/5d/jmg_9064.cr2              | 1 +
- incoming/5d/jmg_9077.jpg              | 1 +
- incoming/5d/jmg_9078.jpg              | 1 +
- incoming/5d/jmg_9081.jpg              | 1 +
- incoming/5d/jmg_9082.cr2              | 1 +
- incoming/5d/jmg_9083.jpg              | 1 +
- incoming/5d/jmg_9086.cr2              | 1 +
- incoming/5d/jmg_9088.jpg              | 1 +
- incoming/5d/jmg_9308.jpg              | 1 +
- incoming/5d/jmg_9312.cr2              | 1 +
- incoming/5d/jmg_9313.jpg              | 1 +
- incoming/5d/jmg_9319.jpg              | 1 +
- incoming/5d/jmg_9521.cr2              | 1 +
- incoming/5d/jmg_9522.cr2              | 1 +
- incoming/5d/jmg_9533.jpg              | 1 +
- incoming/5d/jmg_9534.jpg              | 1 +
- incoming/5d/jmg_9535.cr2              | 1 +
- incoming/5d/jmg_9538.cr2              | 1 +
- incoming/5d/jmg_9538.jpg              | 1 +
- incoming/5d/jmg_9540.jpg              | 1 +
- incoming/5d/jmg_9542.cr2              | 1 +
- incoming/5d/jmg_9545.jpg              | 1 +
- incoming/5d/jmg_9554.jpg              | 1 +
- incoming/5d/jmg_9555.jpg              | 1 +
- incoming/5d/jmg_9558.jpg              | 1 +
- incoming/5d/jmg_9561.cr2              | 1 +
- incoming/5d/jmg_9585.cr2              | 1 +
- incoming/5d/jmg_9587.jpg              | 1 +
- incoming/5d/jmg_9591.jpg              | 1 +
- incoming/5d/jmg_9595.jpg              | 1 +
- incoming/5d/jmg_9598.cr2              | 1 +
- incoming/5d/jmg_9600.jpg              | 1 +
- incoming/5d/jmg_9604.jpg              | 1 +
- incoming/5d/jmg_9610.jpg              | 1 +
- incoming/5d/jmg_9613.cr2              | 1 +
- incoming/5d/jmg_9613.jpg              | 1 +
- incoming/5d/jmg_9614.cr2              | 1 +
- incoming/5d/jmg_9618.jpg              | 1 +
- incoming/5d/jmg_9619.jpg              | 1 +
- incoming/5d/jmg_9620.jpg              | 1 +
- incoming/5d/jmg_9621.jpg              | 1 +
- incoming/5d/jmg_9623.cr2              | 1 +
- incoming/5d/jmg_9746.jpg              | 1 +
- incoming/5d/jmg_9763.cr2              | 1 +
- incoming/5d/jmg_9763.jpg              | 1 +
- incoming/5d/jmg_9764.cr2              | 1 +
- incoming/5d/jmg_9772.jpg              | 1 +
- incoming/5d/jmg_9773.jpg              | 1 +
- incoming/5d/jmg_9781.jpg              | 1 +
- incoming/5d/jmg_9790.jpg              | 1 +
- incoming/5d/jmg_9800.jpg              | 1 +
- incoming/5d/jmg_9808.jpg              | 1 +
- incoming/5d/jmg_9830.jpg              | 1 +
- incoming/5d/jmg_9834.cr2              | 1 +
- incoming/5d/jmg_9843.jpg              | 1 +
- incoming/5d/jmg_9848.jpg              | 1 +
- incoming/5d/jmg_9849.jpg              | 1 +
- incoming/5d/jmg_9853.cr2              | 1 +
- incoming/5d/jmg_9856.jpg              | 1 +
- incoming/5d/jmg_9857.cr2              | 1 +
- incoming/5d/jmg_9859.cr2              | 1 +
- incoming/5d/jmg_9860.jpg              | 1 +
- incoming/5d/jmg_9917.jpg              | 1 +
- incoming/5d/jmg_9923.jpg              | 1 +
- incoming/5d/jmg_9926.jpg              | 1 +
- incoming/5d/jmg_9975.cr2              | 1 +
- incoming/5d/jmg_9976.cr2              | 1 +
- incoming/5d/jmg_9978.jpg              | 1 +
- incoming/5d/jmg_9988.jpg              | 1 +
- incoming/5d/jmg_9997.cr2              | 1 +
- incoming/5d/jmg_9998.jpg              | 1 +
- incoming/5d/jmg_9999.jpg              | 1 +
- list_5d_repoB                        | 1 -
- only_on_repoB                        | 1 +
- dir/2012/dir2/jmg_0128.cr2    | 1 -
- dir/2012/dir2/jmg_0128.jpg    | 1 -
- dir/2012/dir2/jmg_0129.cr2    | 1 -
- dir/2012/dir2/jmg_0129.jpg    | 1 -
- dir/2012/dir2/jmg_0353.jpg    | 1 -
- dir/2012/dir2/jmg_0354.jpg    | 1 -
- dir/2012/dir2/jmg_0375.jpg    | 1 -
- dir/2012/dir2/jmg_0376.jpg    | 1 -
- dir/2012/dir2/jmg_0378.jpg    | 1 -
- dir/2012/dir2/jmg_8707.cr2    | 1 -
- dir/2012/dir2/jmg_8707.jpg    | 1 -
- dir/2012/dir2/jmg_8727.cr2    | 1 -
- dir/2012/dir2/jmg_8727.jpg    | 1 -
- dir/2012/dir2/jmg_8728.cr2    | 1 -
- dir/2012/dir2/jmg_8728.jpg    | 1 -
- dir/2012/dir2/jmg_8729.cr2    | 1 -
- dir/2012/dir2/jmg_8729.jpg    | 1 -
- dir/2012/dir2/jmg_8740.cr2    | 1 -
- dir/2012/dir2/jmg_8740.jpg    | 1 -
- dir/2012/dir2/jmg_8742.cr2    | 1 -
- dir/2012/dir2/jmg_8742.jpg    | 1 -
- dir/2012/dir2/jmg_8825.cr2    | 1 -
- dir/2012/dir2/jmg_8825.jpg    | 1 -
- dir/2012/dir2/jmg_8991.cr2    | 1 -
- dir/2012/dir2/jmg_8991.jpg    | 1 -
- dir/2012/dir2/jmg_8992.cr2    | 1 -
- dir/2012/dir2/jmg_8992.jpg    | 1 -
- dir/2012/dir2/jmg_8993.cr2    | 1 -
- dir/2012/dir2/jmg_8993.jpg    | 1 -
- dir/2012/dir2/jmg_9059.cr2    | 1 -
- dir/2012/dir2/jmg_9059.jpg    | 1 -
- dir/2012/dir2/jmg_9060.cr2    | 1 -
- dir/2012/dir2/jmg_9060.jpg    | 1 -
- dir/2012/dir2/jmg_9064.cr2    | 1 -
- dir/2012/dir2/jmg_9064.jpg    | 1 -
- dir/2012/dir2/jmg_9065.cr2    | 1 -
- dir/2012/dir2/jmg_9065.jpg    | 1 -
- dir/2012/dir2/jmg_9081.cr2    | 1 -
- dir/2012/dir2/jmg_9081.jpg    | 1 -
- dir/2012/dir2/jmg_9082.cr2    | 1 -
- dir/2012/dir2/jmg_9082.jpg    | 1 -
- dir/2012/dir2/jmg_9083.cr2    | 1 -
- dir/2012/dir2/jmg_9083.jpg    | 1 -
- dir/2012/dir1/jmg_0132.cr2 | 1 -
- dir/2012/dir1/jmg_0132.jpg | 1 -
- dir/2012/dir1/jmg_0133.cr2 | 1 -
- dir/2012/dir1/jmg_0133.jpg | 1 -
- dir/2012/dir1/jmg_0347.jpg | 1 -
- dir/2012/dir1/jmg_0351.jpg | 1 -
- dir/2012/dir1/jmg_0352.jpg | 1 -
- dir/2012/dir1/jmg_0374.jpg | 1 -
- dir/2012/dir1/jmg_8714.cr2 | 1 -
- dir/2012/dir1/jmg_8714.jpg | 1 -
- dir/2012/dir1/jmg_8716.cr2 | 1 -
- dir/2012/dir1/jmg_8716.jpg | 1 -
- dir/2012/dir1/jmg_8734.cr2 | 1 -
- dir/2012/dir1/jmg_8734.jpg | 1 -
- dir/2012/dir1/jmg_8735.cr2 | 1 -
- dir/2012/dir1/jmg_8735.jpg | 1 -
- dir/2012/dir1/jmg_8736.cr2 | 1 -
- dir/2012/dir1/jmg_8736.jpg | 1 -
- dir/2012/dir1/jmg_8743.cr2 | 1 -
- dir/2012/dir1/jmg_8743.jpg | 1 -
- dir/2012/dir1/jmg_8746.cr2 | 1 -
- dir/2012/dir1/jmg_8746.jpg | 1 -
- dir/2012/dir1/jmg_8828.cr2 | 1 -
- dir/2012/dir1/jmg_8828.jpg | 1 -
- dir/2012/dir1/jmg_8984.cr2 | 1 -
- dir/2012/dir1/jmg_8984.jpg | 1 -
- dir/2012/dir1/jmg_8985.cr2 | 1 -
- dir/2012/dir1/jmg_8985.jpg | 1 -
- dir/2012/dir1/jmg_8986.cr2 | 1 -
- dir/2012/dir1/jmg_8986.jpg | 1 -
- dir/2012/dir1/jmg_8988.cr2 | 1 -
- dir/2012/dir1/jmg_8988.jpg | 1 -
- dir/2012/dir1/jmg_9057.cr2 | 1 -
- dir/2012/dir1/jmg_9057.jpg | 1 -
- dir/2012/dir1/jmg_9058.cr2 | 1 -
- dir/2012/dir1/jmg_9058.jpg | 1 -
- dir/2012/dir1/jmg_9086.cr2 | 1 -
- dir/2012/dir1/jmg_9086.jpg | 1 -
- dir/2012/dir1/jmg_9087.cr2 | 1 -
- dir/2012/dir1/jmg_9087.jpg | 1 -
- dir/2013/dir2/jmg_0477.cr2    | 1 -
- dir/2013/dir2/jmg_0477.jpg    | 1 -
- dir/2013/dir2/jmg_0478.cr2    | 1 -
- dir/2013/dir2/jmg_0478.jpg    | 1 -
- dir/2013/dir2/jmg_0479.cr2    | 1 -
- dir/2013/dir2/jmg_0479.jpg    | 1 -
- dir/2013/dir2/jmg_0604.cr2    | 1 -
- dir/2013/dir2/jmg_0604.jpg    | 1 -
- dir/2013/dir2/jmg_0605.cr2    | 1 -
- dir/2013/dir2/jmg_0605.jpg    | 1 -
- dir/2013/dir2/jmg_0606.cr2    | 1 -
- dir/2013/dir2/jmg_0606.jpg    | 1 -
- dir/2013/dir2/jmg_0607.cr2    | 1 -
- dir/2013/dir2/jmg_0607.jpg    | 1 -
- dir/2013/dir2/jmg_0608.cr2    | 1 -
- dir/2013/dir2/jmg_0608.jpg    | 1 -
- dir/2013/dir2/jmg_0708.cr2    | 1 -
- dir/2013/dir2/jmg_0708.jpg    | 1 -
- dir/2013/dir2/jmg_0709.cr2    | 1 -
- dir/2013/dir2/jmg_0709.jpg    | 1 -
- dir/2013/dir2/jmg_0710.cr2    | 1 -
- dir/2013/dir2/jmg_0710.jpg    | 1 -
- dir/2013/dir1/jmg_0475.cr2 | 1 -
- dir/2013/dir1/jmg_0475.jpg | 1 -
- dir/2013/dir1/jmg_0476.cr2 | 1 -
- dir/2013/dir1/jmg_0476.jpg | 1 -
- dir/2013/dir1/jmg_0718.cr2 | 1 -
- dir/2013/dir1/jmg_0718.jpg | 1 -
- dir/2013/dir1/jmg_0719.cr2 | 1 -
- dir/2013/dir1/jmg_0719.jpg | 1 -
- 1821 files changed, 628 insertions(+), 1231 deletions(-)
- delete mode 120000 201109/jmg_7250.cr2
- delete mode 120000 201109/jmg_7250.jpg
- delete mode 120000 201109/jmg_7251.cr2
- delete mode 120000 201109/jmg_7251.jpg
- delete mode 120000 201109/jmg_7253.cr2
- delete mode 120000 201109/jmg_7253.jpg
- delete mode 120000 201109/jmg_7256_raw.jpg
- delete mode 120000 201109/jmg_7259.cr2
- delete mode 120000 201109/jmg_7259.jpg
- delete mode 120000 201109/jmg_7261.cr2
- delete mode 120000 201109/jmg_7261.jpg
- delete mode 120000 201109/jmg_7265.cr2
- delete mode 120000 201109/jmg_7265.jpg
- delete mode 120000 201109/jmg_7272.jpg
- delete mode 120000 201109/jmg_7274.jpg
- delete mode 120000 201109/jmg_7275.jpg
- delete mode 120000 201109/jmg_7276.jpg
- delete mode 120000 201109/jmg_7280.jpg
- delete mode 120000 201109/jmg_7284.jpg
- delete mode 120000 201109/jmg_7286.jpg
- delete mode 120000 201109/jmg_7288.jpg
- delete mode 120000 201109/jmg_7289.jpg
- delete mode 120000 201109/jmg_7292.jpg
- delete mode 120000 201109/jmg_7293.jpg
- delete mode 120000 201109/jmg_7295.cr2
- delete mode 120000 201109/jmg_7295.jpg
- delete mode 120000 201109/jmg_7296.cr2
- delete mode 120000 201109/jmg_7296.jpg
- delete mode 120000 201109/jmg_7299.cr2
- delete mode 120000 201109/jmg_7299.jpg
- delete mode 120000 201109/jmg_7300.cr2
- delete mode 120000 201109/jmg_7300.jpg
- delete mode 120000 201109/jmg_7304.jpg
- delete mode 120000 201109/jmg_7305_raw.jpg
- delete mode 120000 201109/jmg_7307_raw.jpg
- delete mode 120000 201202/jmg_8528.jpg
- delete mode 120000 201202/jmg_8529.jpg
- delete mode 120000 201202/jmg_8595.jpg
- delete mode 120000 201202/jmg_8596.jpg
- delete mode 120000 201202/jmg_8597.jpg
- delete mode 120000 201202/jmg_8601.jpg
- delete mode 120000 201202/jmg_8602.cr2
- delete mode 120000 201202/jmg_8602.jpg
- delete mode 120000 201202/jmg_8603.cr2
- delete mode 120000 201202/jmg_8603.jpg
- delete mode 120000 201202/jmg_8604.jpg
- delete mode 120000 201202/jmg_8605.jpg
- delete mode 120000 201202/jmg_8606.jpg
- delete mode 120000 201202/jmg_8607.jpg
- delete mode 120000 201202/jmg_8608.jpg
- delete mode 120000 201202/jmg_8609.jpg
- delete mode 120000 201202/jmg_8610.jpg
- delete mode 120000 201202/jmg_8611.jpg
- delete mode 120000 201202/jmg_8612.cr2
- delete mode 120000 201202/jmg_8612.jpg
- delete mode 120000 201202/jmg_8613.jpg
- delete mode 120000 201202/jmg_8614.jpg
- delete mode 120000 201202/jmg_8615.jpg
- delete mode 120000 201202/jmg_8616_raw.jpg
- delete mode 120000 201202/jmg_8617.jpg
- delete mode 120000 201202/jmg_8618.jpg
- delete mode 120000 201202/jmg_8619.jpg
- delete mode 120000 201202/jmg_8620.jpg
- delete mode 120000 201202/jmg_8621.jpg
- delete mode 120000 201202/jmg_8622.jpg
- delete mode 120000 201202/jmg_8624.jpg
- delete mode 120000 201202/jmg_8625.cr2
- delete mode 120000 201202/jmg_8625.jpg
- delete mode 120000 201202/jmg_8626.jpg
- delete mode 120000 201202/jmg_8627.jpg
- delete mode 120000 201202/jmg_8628.jpg
- delete mode 120000 201202/jmg_8629.jpg
- delete mode 120000 201202/jmg_8630.jpg
- delete mode 120000 201202/jmg_8631.jpg
- delete mode 120000 201202/jmg_8632.jpg
- delete mode 120000 201202/jmg_8633.cr2
- delete mode 120000 201202/jmg_8633.jpg
- delete mode 120000 201202/jmg_8634.jpg
- delete mode 120000 201202/jmg_8637.jpg
- delete mode 120000 201202/jmg_8639.jpg
- delete mode 120000 201202/jmg_8640.jpg
- delete mode 120000 201202/jmg_8641.jpg
- delete mode 120000 201202/jmg_8642_raw.jpg
- delete mode 120000 201202/jmg_8643.jpg
- delete mode 120000 201202/jmg_8644.jpg
- delete mode 120000 201202/jmg_8647.jpg
- delete mode 120000 201202/jmg_8648.jpg
- delete mode 120000 201202/jmg_8651.cr2
- delete mode 120000 201202/jmg_8651.jpg
- delete mode 120000 201202/jmg_8652.jpg
- delete mode 120000 201202/jmg_8653.jpg
- delete mode 120000 201202/jmg_8654.jpg
- delete mode 120000 201202/jmg_8655.jpg
- delete mode 120000 201202/jmg_8657.jpg
- delete mode 120000 201202/jmg_8665.jpg
- delete mode 120000 201202/jmg_8670.jpg
- delete mode 120000 201202/jmg_8671.jpg
- delete mode 120000 201202/jmg_8673.cr2
- delete mode 120000 201202/jmg_8673.jpg
- delete mode 120000 201202/jmg_8674.jpg
- delete mode 120000 201202/jmg_8675.jpg
- delete mode 120000 201202/jmg_8676.jpg
- delete mode 120000 201202/jmg_8677.jpg
- delete mode 120000 201202/jmg_8678.jpg
- delete mode 120000 201202/jmg_8679.jpg
- delete mode 120000 201202/jmg_8680.jpg
- delete mode 120000 201202/jmg_8681.jpg
- delete mode 120000 201203/jmg_8701.cr2
- delete mode 120000 201203/jmg_8702.jpg
- delete mode 120000 201203/jmg_8705.jpg
- delete mode 120000 201203/jmg_8711.jpg
- delete mode 120000 201203/jmg_8717.jpg
- delete mode 120000 201203/jmg_8718.jpg
- delete mode 120000 201203/jmg_8719.jpg
- delete mode 120000 201203/jmg_8721.jpg
- delete mode 120000 201203/jmg_8725.jpg
- delete mode 120000 201203/jmg_8726.jpg
- delete mode 120000 201203/jmg_8731.jpg
- delete mode 120000 201203/jmg_8739.jpg
- delete mode 120000 201203/jmg_8745.jpg
- delete mode 120000 201203/jmg_8747_raw.jpg
- delete mode 120000 201203/jmg_8750.cr2
- delete mode 120000 201203/jmg_8750.jpg
- delete mode 120000 201204/jmg_8751.jpg
- delete mode 120000 201204/jmg_8752.jpg
- delete mode 120000 201204/jmg_8755.jpg
- delete mode 120000 201204/jmg_8756.jpg
- delete mode 120000 201204/jmg_8757.jpg
- delete mode 120000 201204/jmg_8759.jpg
- delete mode 120000 201204/jmg_8760.jpg
- delete mode 120000 201204/jmg_8761.jpg
- delete mode 120000 201204/jmg_8762.jpg
- delete mode 120000 201204/jmg_8763.cr2
- delete mode 120000 201204/jmg_8763.jpg
- delete mode 120000 201204/jmg_8766.jpg
- delete mode 120000 201204/jmg_8767.cr2
- delete mode 120000 201204/jmg_8767.jpg
- delete mode 120000 201204/jmg_8768.jpg
- delete mode 120000 201204/jmg_8769.jpg
- delete mode 120000 201204/jmg_8770.jpg
- delete mode 120000 201204/jmg_8771.jpg
- delete mode 120000 201204/jmg_8772.jpg
- delete mode 120000 201204/jmg_8773.jpg
- delete mode 120000 201205/jmg_8822.jpg
- delete mode 120000 201205/jmg_8823.jpg
- delete mode 120000 201205/jmg_8824.jpg
- delete mode 120000 201205/jmg_8826.jpg
- delete mode 120000 201205/jmg_8831.jpg
- delete mode 120000 201205/jmg_8834.jpg
- delete mode 120000 201205/jmg_8835.jpg
- delete mode 120000 201205/jmg_8835_raw.jpg
- delete mode 120000 201205/jmg_8837.jpg
- delete mode 120000 201205/jmg_8839.cr2
- delete mode 120000 201205/jmg_8839.jpg
- delete mode 120000 201205/jmg_8839_raw.jpg
- delete mode 120000 201205/jmg_8840.cr2
- delete mode 120000 201205/jmg_8840.jpg
- delete mode 120000 201205/jmg_8840_raw.jpg
- delete mode 120000 201205/jmg_8841.jpg
- delete mode 120000 201205/jmg_8842.jpg
- delete mode 120000 201205/jmg_8844.cr2
- delete mode 120000 201205/jmg_8844.jpg
- delete mode 120000 201205/jmg_8844_raw.jpg
- delete mode 120000 201205/jmg_8845.jpg
- delete mode 120000 201205/jmg_8846.jpg
- delete mode 120000 201205/jmg_8847.cr2
- delete mode 120000 201205/jmg_8847.jpg
- delete mode 120000 201205/jmg_8847_raw.jpg
- delete mode 120000 201205/jmg_8848.jpg
- delete mode 120000 201205/jmg_8849.jpg
- delete mode 120000 201205/jmg_8851.cr2
- delete mode 120000 201205/jmg_8851.jpg
- delete mode 120000 201205/jmg_8851_raw.jpg
- delete mode 120000 201205/jmg_8856.cr2
- delete mode 120000 201205/jmg_8856.jpg
- delete mode 120000 201205/jmg_8856_raw.jpg
- delete mode 120000 201205/jmg_8857.jpg
- delete mode 120000 201205/jmg_8858.jpg
- delete mode 120000 201205/jmg_8859.jpg
- delete mode 120000 201205/jmg_8861.jpg
- delete mode 120000 201205/jmg_8862.jpg
- delete mode 120000 201205/jmg_8863.jpg
- delete mode 120000 201205/jmg_8871.cr2
- delete mode 120000 201205/jmg_8871.jpg
- delete mode 120000 201205/jmg_8872.jpg
- delete mode 120000 201205/jmg_8873.jpg
- delete mode 120000 201205/jmg_8875.jpg
- delete mode 120000 201205/jmg_8876.cr2
- delete mode 120000 201205/jmg_8876.jpg
- delete mode 120000 201205/jmg_8878.cr2
- delete mode 120000 201205/jmg_8878.jpg
- delete mode 120000 201205/jmg_8879.cr2
- delete mode 120000 201205/jmg_8879.jpg
- delete mode 120000 201205/jmg_8880.cr2
- delete mode 120000 201205/jmg_8880.jpg
- delete mode 120000 201205/jmg_8881.cr2
- delete mode 120000 201205/jmg_8881.jpg
- delete mode 120000 201205/jmg_8892.cr2
- delete mode 120000 201205/jmg_8892.jpg
- delete mode 120000 201205/jmg_8893.cr2
- delete mode 120000 201205/jmg_8893.jpg
- delete mode 120000 201205/jmg_8894.cr2
- delete mode 120000 201205/jmg_8894.jpg
- delete mode 120000 201206/jmg_8989.cr2
- delete mode 120000 201206/jmg_8989.jpg
- delete mode 120000 201206/jmg_8990.cr2
- delete mode 120000 201206/jmg_8990.jpg
- delete mode 120000 201206/jmg_8995.jpg
- delete mode 120000 201206/jmg_8996.jpg
- delete mode 120000 201206/jmg_8998.jpg
- delete mode 120000 201206/jmg_9001.jpg
- delete mode 120000 201206/jmg_9003.jpg
- delete mode 120000 201206/jmg_9006.jpg
- delete mode 120000 201206/jmg_9007.jpg
- delete mode 120000 201206/jmg_9011.jpg
- delete mode 120000 201206/jmg_9014.jpg
- delete mode 120000 201206/jmg_9014_raw.jpg
- delete mode 120000 201206/jmg_9015.jpg
- delete mode 120000 201206/jmg_9016.cr2
- delete mode 120000 201206/jmg_9016.jpg
- delete mode 120000 201206/jmg_9017.cr2
- delete mode 120000 201206/jmg_9017.jpg
- delete mode 120000 201206/jmg_9018.cr2
- delete mode 120000 201206/jmg_9018.jpg
- delete mode 120000 201206/jmg_9019.cr2
- delete mode 120000 201206/jmg_9019.jpg
- delete mode 120000 201206/jmg_9023.cr2
- delete mode 120000 201206/jmg_9023.jpg
- delete mode 120000 201206/jmg_9024.cr2
- delete mode 120000 201206/jmg_9024.jpg
- delete mode 120000 201206/jmg_9025.cr2
- delete mode 120000 201206/jmg_9025.jpg
- delete mode 120000 201206/jmg_9028.jpg
- delete mode 120000 201206/jmg_9029.jpg
- delete mode 120000 201206/jmg_9030.jpg
- delete mode 120000 201206/jmg_9031.jpg
- delete mode 120000 201206/jmg_9032_raw.jpg
- delete mode 120000 201206/jmg_9033.jpg
- delete mode 120000 201206/jmg_9033_raw.jpg
- delete mode 120000 201206/jmg_9034.jpg
- delete mode 120000 201206/jmg_9035.jpg
- delete mode 120000 201206/jmg_9035_raw.jpg
- delete mode 120000 201206/jmg_9036.jpg
- delete mode 120000 201206/jmg_9039.cr2
- delete mode 120000 201206/jmg_9039.jpg
- delete mode 120000 201206/jmg_9040.cr2
- delete mode 120000 201206/jmg_9040.jpg
- delete mode 120000 201206/jmg_9043.cr2
- delete mode 120000 201206/jmg_9043.jpg
- delete mode 120000 201206/jmg_9047.cr2
- delete mode 120000 201206/jmg_9047.jpg
- delete mode 120000 201207/jmg_9048.jpg
- delete mode 120000 201207/jmg_9053.jpg
- delete mode 120000 201207/jmg_9054.jpg
- delete mode 120000 201207/jmg_9069.cr2
- delete mode 120000 201207/jmg_9069.jpg
- delete mode 120000 201207/jmg_9070.cr2
- delete mode 120000 201207/jmg_9070.jpg
- delete mode 120000 201207/jmg_9072.cr2
- delete mode 120000 201207/jmg_9072.jpg
- delete mode 120000 201207/jmg_9076.cr2
- delete mode 120000 201207/jmg_9076.jpg
- delete mode 120000 201208/jmg_9077.jpg
- delete mode 120000 201208/jmg_9302_raw.jpg
- delete mode 120000 201208/jmg_9303.jpg
- delete mode 120000 201208/jmg_9304.cr2
- delete mode 120000 201208/jmg_9304.jpg
- delete mode 120000 201208/jmg_9305.cr2
- delete mode 120000 201208/jmg_9305.jpg
- delete mode 120000 201208/jmg_9306_raw.jpg
- delete mode 120000 201208/jmg_9307.cr2
- delete mode 120000 201208/jmg_9307.jpg
- delete mode 120000 201208/jmg_9308_raw.jpg
- delete mode 120000 201208/jmg_9309_raw.jpg
- delete mode 120000 201208/jmg_9310.cr2
- delete mode 120000 201208/jmg_9310.jpg
- delete mode 120000 201208/jmg_9310_bw.jpg
- delete mode 120000 201208/jmg_9310_raw.jpg
- delete mode 120000 201208/jmg_9312.jpg
- delete mode 120000 201208/jmg_9313.jpg
- delete mode 120000 201208/jmg_9314.jpg
- delete mode 120000 201208/jmg_9315.jpg
- delete mode 120000 201208/jmg_9319.jpg
- delete mode 120000 201208/jmg_9523.jpg
- delete mode 120000 201208/jmg_9524.jpg
- delete mode 120000 201208/jmg_9525.jpg
- delete mode 120000 201208/jmg_9526.jpg
- delete mode 120000 201208/jmg_9527.jpg
- delete mode 120000 201208/jmg_9527_raw.jpg
- delete mode 120000 201208/jmg_9528.jpg
- delete mode 120000 201208/jmg_9529.jpg
- delete mode 120000 201208/jmg_9530.jpg
- delete mode 120000 201208/jmg_9531.jpg
- delete mode 120000 201208/jmg_9532.jpg
- delete mode 120000 201208/jmg_9533.cr2
- delete mode 120000 201208/jmg_9533.jpg
- delete mode 120000 201208/jmg_9534.cr2
- delete mode 120000 201208/jmg_9534.jpg
- delete mode 120000 201208/jmg_9535.jpg
- delete mode 120000 201208/jmg_9536.jpg
- delete mode 120000 201208/jmg_9537.cr2
- delete mode 120000 201208/jmg_9537.jpg
- delete mode 120000 201208/jmg_9538.jpg
- delete mode 120000 201208/jmg_9539.jpg
- delete mode 120000 201208/jmg_9540.jpg
- delete mode 120000 201208/jmg_9541.cr2
- delete mode 120000 201208/jmg_9542.jpg
- delete mode 120000 201208/jmg_9543.cr2
- delete mode 120000 201208/jmg_9543.jpg
- delete mode 120000 201208/jmg_9544.cr2
- delete mode 120000 201208/jmg_9544.jpg
- delete mode 120000 201208/jmg_9545.jpg
- delete mode 120000 201209/jmg_9547.jpg
- delete mode 120000 201209/jmg_9548.jpg
- delete mode 120000 201209/jmg_9549.jpg
- delete mode 120000 201209/jmg_9550.jpg
- delete mode 120000 201209/jmg_9551.jpg
- delete mode 120000 201209/jmg_9552.jpg
- delete mode 120000 201209/jmg_9553.jpg
- delete mode 120000 201209/jmg_9555.jpg
- delete mode 120000 201209/jmg_9556.jpg
- delete mode 120000 201209/jmg_9558.jpg
- delete mode 120000 201209/jmg_9559.cr2
- delete mode 120000 201209/jmg_9559.jpg
- delete mode 120000 201209/jmg_9560.cr2
- delete mode 120000 201209/jmg_9560.jpg
- delete mode 120000 201209/jmg_9561.jpg
- delete mode 120000 201209/jmg_9562.jpg
- delete mode 120000 201209/jmg_9568.jpg
- delete mode 120000 201210/jmg_0001.jpg
- delete mode 120000 201210/jmg_0021.jpg
- delete mode 120000 201210/jmg_0022.cr2
- delete mode 120000 201210/jmg_0022.jpg
- delete mode 120000 201210/jmg_0025.jpg
- delete mode 120000 201210/jmg_0026.jpg
- delete mode 120000 201210/jmg_0027.jpg
- delete mode 120000 201210/jmg_0028.jpg
- delete mode 120000 201210/jmg_0029.jpg
- delete mode 120000 201210/jmg_0030.jpg
- delete mode 120000 201210/jmg_0032.jpg
- delete mode 120000 201210/jmg_0034.jpg
- delete mode 120000 201210/jmg_0035.jpg
- delete mode 120000 201210/jmg_0036.jpg
- delete mode 120000 201210/jmg_0037.jpg
- delete mode 120000 201210/jmg_0039.cr2
- delete mode 120000 201210/jmg_0039.jpg
- delete mode 120000 201210/jmg_0040.jpg
- delete mode 120000 201210/jmg_9572.jpg
- delete mode 120000 201210/jmg_9573.jpg
- delete mode 120000 201210/jmg_9574.jpg
- delete mode 120000 201210/jmg_9575.jpg
- delete mode 120000 201210/jmg_9576.jpg
- delete mode 120000 201210/jmg_9578.jpg
- delete mode 120000 201210/jmg_9580.jpg
- delete mode 120000 201210/jmg_9581.jpg
- delete mode 120000 201210/jmg_9582.cr2
- delete mode 120000 201210/jmg_9582.jpg
- delete mode 120000 201210/jmg_9585.cr2
- delete mode 120000 201210/jmg_9585.jpg
- delete mode 120000 201210/jmg_9587.cr2
- delete mode 120000 201210/jmg_9587.jpg
- delete mode 120000 201210/jmg_9588.jpg
- delete mode 120000 201210/jmg_9589.jpg
- delete mode 120000 201210/jmg_9590.jpg
- delete mode 120000 201210/jmg_9591.jpg
- delete mode 120000 201210/jmg_9594.jpg
- delete mode 120000 201210/jmg_9595.jpg
- delete mode 120000 201210/jmg_9596.jpg
- delete mode 120000 201210/jmg_9597.cr2
- delete mode 120000 201210/jmg_9597.jpg
- delete mode 120000 201210/jmg_9598.cr2
- delete mode 120000 201210/jmg_9598.jpg
- delete mode 120000 201210/jmg_9599.cr2
- delete mode 120000 201210/jmg_9599.jpg
- delete mode 120000 201210/jmg_9600.jpg
- delete mode 120000 201210/jmg_9602.jpg
- delete mode 120000 201210/jmg_9603.jpg
- delete mode 120000 201210/jmg_9604.jpg
- delete mode 120000 201210/jmg_9605.cr2
- delete mode 120000 201210/jmg_9605.jpg
- delete mode 120000 201210/jmg_9606.jpg
- delete mode 120000 201210/jmg_9608.jpg
- delete mode 120000 201210/jmg_9609.jpg
- delete mode 120000 201210/jmg_9610.jpg
- delete mode 120000 201210/jmg_9611.jpg
- delete mode 120000 201210/jmg_9612.jpg
- delete mode 120000 201210/jmg_9613.jpg
- delete mode 120000 201210/jmg_9614.jpg
- delete mode 120000 201210/jmg_9616.cr2
- delete mode 120000 201210/jmg_9616.jpg
- delete mode 120000 201210/jmg_9617.jpg
- delete mode 120000 201210/jmg_9619.jpg
- delete mode 120000 201210/jmg_9620.jpg
- delete mode 120000 201210/jmg_9621.jpg
- delete mode 120000 201210/jmg_9622.jpg
- delete mode 120000 201210/jmg_9623.cr2
- delete mode 120000 201210/jmg_9623.jpg
- delete mode 120000 201210/jmg_9624.cr2
- delete mode 120000 201210/jmg_9624.jpg
- delete mode 120000 201210/jmg_9736_raw.jpg
- delete mode 120000 201210/jmg_9738_raw.jpg
- delete mode 120000 201210/jmg_9740.cr2
- delete mode 120000 201210/jmg_9740.jpg
- delete mode 120000 201210/jmg_9743.jpg
- delete mode 120000 201210/jmg_9744.jpg
- delete mode 120000 201210/jmg_9745.cr2
- delete mode 120000 201210/jmg_9745.jpg
- delete mode 120000 201210/jmg_9746.cr2
- delete mode 120000 201210/jmg_9746.jpg
- delete mode 120000 201210/jmg_9748.jpg
- delete mode 120000 201210/jmg_9749_raw.jpg
- delete mode 120000 201210/jmg_9751.jpg
- delete mode 120000 201210/jmg_9752.jpg
- delete mode 120000 201210/jmg_9754.jpg
- delete mode 120000 201210/jmg_9755.jpg
- delete mode 120000 201210/jmg_9756.jpg
- delete mode 120000 201210/jmg_9760.cr2
- delete mode 120000 201210/jmg_9760.jpg
- delete mode 120000 201210/jmg_9761.cr2
- delete mode 120000 201210/jmg_9761.jpg
- delete mode 120000 201210/jmg_9763.jpg
- delete mode 120000 201210/jmg_9764.jpg
- delete mode 120000 201210/jmg_9766.jpg
- delete mode 120000 201210/jmg_9767.cr2
- delete mode 120000 201210/jmg_9767.jpg
- delete mode 120000 201210/jmg_9768.jpg
- delete mode 120000 201210/jmg_9771.jpg
- delete mode 120000 201210/jmg_9772.jpg
- delete mode 120000 201210/jmg_9791.jpg
- delete mode 120000 201210/jmg_9792.jpg
- delete mode 120000 201210/jmg_9793.jpg
- delete mode 120000 201210/jmg_9794.jpg
- delete mode 120000 201210/jmg_9796.jpg
- delete mode 120000 201210/jmg_9797.jpg
- delete mode 120000 201210/jmg_9799.jpg
- delete mode 120000 201210/jmg_9800.jpg
- delete mode 120000 201210/jmg_9801.jpg
- delete mode 120000 201210/jmg_9803.jpg
- delete mode 120000 201210/jmg_9807.jpg
- delete mode 120000 201210/jmg_9808.jpg
- delete mode 120000 201210/jmg_9809.jpg
- delete mode 120000 201210/jmg_9810.jpg
- delete mode 120000 201210/jmg_9811.jpg
- delete mode 120000 201210/jmg_9812.jpg
- delete mode 120000 201210/jmg_9813.jpg
- delete mode 120000 201210/jmg_9815.jpg
- delete mode 120000 201210/jmg_9818.jpg
- delete mode 120000 201210/jmg_9819.jpg
- delete mode 120000 201210/jmg_9820.jpg
- delete mode 120000 201210/jmg_9821.jpg
- delete mode 120000 201210/jmg_9822.jpg
- delete mode 120000 201210/jmg_9823.jpg
- delete mode 120000 201210/jmg_9825.jpg
- delete mode 120000 201210/jmg_9826.jpg
- delete mode 120000 201210/jmg_9827.jpg
- delete mode 120000 201210/jmg_9828.jpg
- delete mode 120000 201210/jmg_9829.jpg
- delete mode 120000 201210/jmg_9830.cr2
- delete mode 120000 201210/jmg_9830.jpg
- delete mode 120000 201210/jmg_9832.cr2
- delete mode 120000 201210/jmg_9832.jpg
- delete mode 120000 201210/jmg_9834.jpg
- delete mode 120000 201210/jmg_9836.jpg
- delete mode 120000 201210/jmg_9838.jpg
- delete mode 120000 201210/jmg_9839.jpg
- delete mode 120000 201210/jmg_9841.jpg
- delete mode 120000 201210/jmg_9843.jpg
- delete mode 120000 201210/jmg_9845.jpg
- delete mode 120000 201210/jmg_9846.jpg
- delete mode 120000 201210/jmg_9848.jpg
- delete mode 120000 201210/jmg_9849.jpg
- delete mode 120000 201210/jmg_9852.jpg
- delete mode 120000 201210/jmg_9853.jpg
- delete mode 120000 201210/jmg_9854.jpg
- delete mode 120000 201210/jmg_9855.jpg
- delete mode 120000 201210/jmg_9856.jpg
- delete mode 120000 201210/jmg_9857.cr2
- delete mode 120000 201210/jmg_9857.jpg
- delete mode 120000 201210/jmg_9858.cr2
- delete mode 120000 201210/jmg_9858.jpg
- delete mode 120000 201210/jmg_9859.jpg
- delete mode 120000 201210/jmg_9860.jpg
- delete mode 120000 201210/jmg_9915.jpg
- delete mode 120000 201210/jmg_9917.jpg
- delete mode 120000 201210/jmg_9918.jpg
- delete mode 120000 201210/jmg_9919.jpg
- delete mode 120000 201210/jmg_9922.jpg
- delete mode 120000 201210/jmg_9923.jpg
- delete mode 120000 201210/jmg_9925.jpg
- delete mode 120000 201210/jmg_9926.cr2
- delete mode 120000 201210/jmg_9926.jpg
- delete mode 120000 201210/jmg_9928.jpg
- delete mode 120000 201210/jmg_9975.cr2
- delete mode 120000 201210/jmg_9975.jpg
- delete mode 120000 201210/jmg_9976.cr2
- delete mode 120000 201210/jmg_9976.jpg
- delete mode 120000 201210/jmg_9978.jpg
- delete mode 120000 201210/jmg_9986.jpg
- delete mode 120000 201210/jmg_9987.jpg
- delete mode 120000 201210/jmg_9988.jpg
- delete mode 120000 201210/jmg_9989.jpg
- delete mode 120000 201210/jmg_9991.jpg
- delete mode 120000 201210/jmg_9993.jpg
- delete mode 120000 201210/jmg_9994.cr2
- delete mode 120000 201210/jmg_9994.jpg
- delete mode 120000 201210/jmg_9997.jpg
- delete mode 120000 201210/jmg_9998.jpg
- delete mode 120000 201210/jmg_9999.jpg
- delete mode 120000 201212/jmg_0131.jpg
- delete mode 120000 201212/jmg_0134.jpg
- delete mode 120000 201212/jmg_0135.jpg
- delete mode 120000 201212/jmg_0152.jpg
- delete mode 120000 201212/jmg_0155.jpg
- delete mode 120000 201212/jmg_0156.jpg
- delete mode 120000 201212/jmg_0162.jpg
- delete mode 120000 201212/jmg_0163.jpg
- delete mode 120000 201212/jmg_0165.jpg
- delete mode 120000 201212/jmg_0176.cr2
- delete mode 120000 201212/jmg_0176.jpg
- delete mode 120000 201212/jmg_0177.cr2
- delete mode 120000 201212/jmg_0177.jpg
- delete mode 120000 201212/jmg_0178.jpg
- delete mode 120000 201212/jmg_0179.jpg
- delete mode 120000 201212/jmg_0180.jpg
- delete mode 120000 201212/jmg_0184.jpg
- delete mode 120000 201212/jmg_0185.jpg
- delete mode 120000 201212/jmg_0186.jpg
- delete mode 120000 201212/jmg_0187.jpg
- delete mode 120000 201212/jmg_0306.jpg
- delete mode 120000 201212/jmg_0307.jpg
- delete mode 120000 201212/jmg_0308.jpg
- delete mode 120000 201212/jmg_0310.jpg
- delete mode 120000 201212/jmg_0311.jpg
- delete mode 120000 201212/jmg_0312.jpg
- delete mode 120000 201212/jmg_0313.jpg
- delete mode 120000 201212/jmg_0314.jpg
- delete mode 120000 201212/jmg_0315.jpg
- delete mode 120000 201212/jmg_0316.jpg
- delete mode 120000 201212/jmg_0317.jpg
- delete mode 120000 201212/jmg_0321.jpg
- delete mode 120000 201212/jmg_0326.jpg
- delete mode 120000 201212/jmg_0328.jpg
- delete mode 120000 201212/jmg_0330.jpg
- delete mode 120000 201212/jmg_0333.jpg
- delete mode 120000 201212/jmg_0336.jpg
- delete mode 120000 201212/jmg_0340.jpg
- delete mode 120000 201212/jmg_0343.jpg
- delete mode 120000 201212/jmg_0345.jpg
- delete mode 120000 201212/jmg_0360.jpg
- delete mode 120000 201212/jmg_0362.jpg
- delete mode 120000 201212/jmg_0363.jpg
- delete mode 120000 201212/jmg_0364.jpg
- delete mode 120000 201212/jmg_0366.jpg
- delete mode 120000 201212/jmg_0367.jpg
- delete mode 120000 201212/jmg_0368.jpg
- delete mode 120000 201212/jmg_0369.jpg
- delete mode 120000 201212/jmg_0370.jpg
- delete mode 120000 201212/jmg_0372.jpg
- delete mode 120000 201212/jmg_0382.jpg
- delete mode 120000 201212/jmg_0383.jpg
- delete mode 120000 201212/jmg_0384.jpg
- delete mode 120000 201212/jmg_0385.jpg
- delete mode 120000 201212/jmg_0387.jpg
- delete mode 120000 201212/jmg_0388.jpg
- delete mode 120000 201212/jmg_0389.jpg
- delete mode 120000 201212/jmg_0390.jpg
- delete mode 120000 201212/jmg_0392.jpg
- delete mode 120000 201212/jmg_0396.jpg
- delete mode 120000 201212/jmg_0397.jpg
- delete mode 120000 201212/jmg_0398.jpg
- delete mode 120000 201212/jmg_0399.jpg
- delete mode 120000 201212/jmg_0402.jpg
- delete mode 120000 201212/jmg_0404.jpg
- delete mode 120000 201212/jmg_0405.jpg
- delete mode 120000 201212/jmg_0406.jpg
- delete mode 120000 201212/jmg_0407.jpg
- delete mode 120000 201212/jmg_0408.jpg
- delete mode 120000 201212/jmg_0410.jpg
- delete mode 120000 201212/jmg_0411.jpg
- delete mode 120000 201212/jmg_0412.jpg
- delete mode 120000 201212/jmg_0415.jpg
- delete mode 120000 201212/jmg_0417.jpg
- delete mode 120000 201212/jmg_0418.jpg
- delete mode 120000 201302/jmg_0502.cr2
- delete mode 120000 201302/jmg_0502.jpg
- delete mode 120000 201302/jmg_0503.jpg
- delete mode 120000 201302/jmg_0507.jpg
- delete mode 120000 201302/jmg_0510.jpg
- delete mode 120000 201302/jmg_0512.jpg
- delete mode 120000 201302/jmg_0513.jpg
- delete mode 120000 201302/jmg_0514.jpg
- delete mode 120000 201302/jmg_0516.jpg
- delete mode 120000 201302/jmg_0517.jpg
- delete mode 120000 201302/jmg_0518.jpg
- delete mode 120000 201302/jmg_0521.jpg
- delete mode 120000 201302/jmg_0522.jpg
- delete mode 120000 201302/jmg_0523.jpg
- delete mode 120000 201302/jmg_0524.jpg
- delete mode 120000 201302/jmg_0526.jpg
- delete mode 120000 201302/jmg_0527.jpg
- delete mode 120000 201302/jmg_0528.jpg
- delete mode 120000 201302/jmg_0532.cr2
- delete mode 120000 201302/jmg_0532.jpg
- delete mode 120000 201302/jmg_0534.jpg
- delete mode 120000 201302/jmg_0535.jpg
- delete mode 120000 201302/jmg_0537.jpg
- delete mode 120000 201302/jmg_0539.jpg
- delete mode 120000 201302/jmg_0541.jpg
- delete mode 120000 201302/jmg_0543.jpg
- delete mode 120000 201304/bruecke_saeckingen.tif
- delete mode 120000 201304/jmg_0685.cr2
- delete mode 120000 201304/jmg_0685.jpg
- delete mode 120000 201304/jmg_0687.cr2
- delete mode 120000 201304/jmg_0687.jpg
- delete mode 120000 201304/jmg_0699.jpg
- delete mode 120000 201304/jmg_0700.jpg
- delete mode 120000 201304/jmg_0726.jpg
- delete mode 120000 201304/jmg_0727.jpg
- delete mode 120000 201304/jmg_0728.jpg
- delete mode 120000 201304/jmg_0729.cr2
- delete mode 120000 201304/jmg_0729.jpg
- delete mode 120000 201304/jmg_0730.jpg
- delete mode 120000 201304/jmg_0731.jpg
- delete mode 120000 201304/jmg_0733.cr2
- delete mode 120000 201304/jmg_0733.jpg
- delete mode 120000 201304/jmg_0734.cr2
- delete mode 120000 201304/jmg_0734.jpg
- delete mode 120000 201304/jmg_0736.cr2
- delete mode 120000 201304/jmg_0736.jpg
- delete mode 120000 201304/jmg_0737.cr2
- delete mode 120000 201304/jmg_0737.jpg
- delete mode 120000 201304/jmg_0738.jpg
- delete mode 120000 201304/jmg_0739.jpg
- delete mode 120000 201304/jmg_0740.jpg
- delete mode 120000 201304/jmg_0741.jpg
- delete mode 120000 201304/jmg_0742.jpg
- delete mode 120000 201304/jmg_0744.cr2
- delete mode 120000 201304/jmg_0744.jpg
- delete mode 120000 201304/jmg_0749.jpg
- delete mode 120000 201304/jmg_0750.jpg
- delete mode 120000 201304/jmg_0751.jpg
- delete mode 120000 201304/jmg_0752.jpg
- delete mode 120000 201304/jmg_0753.jpg
- delete mode 120000 201304/jmg_0755.cr2
- delete mode 120000 201304/jmg_0755.jpg
- delete mode 120000 201304/jmg_0757.cr2
- delete mode 120000 201304/jmg_0757.jpg
- delete mode 120000 201304/jmg_0758.jpg
- delete mode 120000 201304/jmg_0759.jpg
- delete mode 120000 201304/jmg_0760.cr2
- delete mode 120000 201304/jmg_0760.jpg
- delete mode 120000 201304/jmg_0762.cr2
- delete mode 120000 201304/jmg_0762.jpg
- delete mode 120000 201304/jmg_0763.jpg
- delete mode 120000 201304/jmg_0764.jpg
- delete mode 120000 201304/jmg_0765.jpg
- delete mode 120000 201304/jmg_0766.jpg
- delete mode 120000 201304/jmg_0769.jpg
- delete mode 120000 201304/jmg_0770.jpg
- delete mode 120000 201304/jmg_0771.jpg
- delete mode 120000 201304/jmg_0785.cr2
- delete mode 120000 201304/jmg_0785.jpg
- delete mode 120000 201304/jmg_0786.cr2
- delete mode 120000 201304/jmg_0786.jpg
- delete mode 120000 201304/jmg_0787.cr2
- delete mode 120000 201304/jmg_0787.jpg
- delete mode 120000 201304/jmg_0789.jpg
- delete mode 120000 201304/jmg_0790.jpg
- delete mode 120000 201304/jmg_0791.jpg
- delete mode 120000 201304/jmg_0800.jpg
- delete mode 120000 201304/jmg_0801.jpg
- delete mode 120000 201304/jmg_0802.jpg
- delete mode 120000 201304/jmg_0803.jpg
- delete mode 120000 201304/jmg_0809.jpg
- delete mode 120000 201304/jmg_0810.jpg
- delete mode 120000 201304/jmg_0812.jpg
- delete mode 120000 201304/jmg_0813.jpg
- delete mode 120000 201304/jmg_0824.jpg
- delete mode 120000 201304/jmg_0825.jpg
- delete mode 120000 201304/jmg_0827.jpg
- delete mode 120000 201304/jmg_0831.jpg
- delete mode 120000 201304/jmg_0833.jpg
- delete mode 120000 201304/jmg_0834.jpg
- delete mode 120000 201304/jmg_0836.jpg
- delete mode 120000 201304/jmg_0837.jpg
- delete mode 120000 201304/jmg_0845.jpg
- delete mode 120000 201304/jmg_0846.jpg
- delete mode 120000 201304/jmg_0847.jpg
- delete mode 120000 201304/jmg_0848.jpg
- delete mode 120000 201304/jmg_0849.jpg
- delete mode 120000 201304/jmg_0850.jpg
- delete mode 120000 201304/jmg_0851.jpg
- delete mode 120000 201304/jmg_0857.jpg
- delete mode 120000 201304/jmg_0858.jpg
- delete mode 120000 201304/jmg_0860.jpg
- delete mode 120000 201304/jmg_0861.jpg
- delete mode 120000 201304/jmg_0862.jpg
- delete mode 120000 201304/jmg_0863.jpg
- delete mode 120000 201304/jmg_0864.jpg
- delete mode 120000 201304/jmg_0866.jpg
- delete mode 120000 201304/jmg_0867.jpg
- delete mode 120000 201304/jmg_0868.cr2
- delete mode 120000 201304/jmg_0868.jpg
- delete mode 120000 201304/jmg_0869.cr2
- delete mode 120000 201304/jmg_0869.jpg
- delete mode 120000 201304/jmg_0872.cr2
- delete mode 120000 201304/jmg_0872.jpg
- delete mode 120000 201304/jmg_0874.cr2
- delete mode 120000 201304/jmg_0874.jpg
- delete mode 120000 201304/jmg_0875.jpg
- delete mode 120000 201304/jmg_0875_raw.jpg
- delete mode 120000 201304/jmg_0876.jpg
- delete mode 120000 201304/jmg_0877.jpg
- delete mode 120000 201304/jmg_0878.jpg
- delete mode 120000 201304/jmg_0880.jpg
- delete mode 120000 201304/jmg_0881.jpg
- delete mode 120000 201304/jmg_0882.jpg
- delete mode 120000 201304/jmg_0884.jpg
- delete mode 120000 201304/jmg_0885.jpg
- delete mode 120000 201304/jmg_0886.jpg
- delete mode 120000 201304/jmg_0888.jpg
- delete mode 120000 201304/jmg_0889.jpg
- delete mode 120000 201304/jmg_0890.jpg
- delete mode 120000 201304/jmg_0891.jpg
- delete mode 120000 201304/jmg_0892.jpg
- delete mode 120000 201304/jmg_0893.cr2
- delete mode 120000 201304/jmg_0893.jpg
- delete mode 120000 201304/jmg_0894.jpg
- delete mode 120000 201304/jmg_0896.jpg
- delete mode 120000 201304/jmg_0897.jpg
- delete mode 120000 201304/jmg_0898.jpg
- delete mode 120000 201304/jmg_0899.jpg
- delete mode 120000 201304/jmg_0900.jpg
- delete mode 120000 201304/jmg_0902.jpg
- delete mode 120000 201304/jmg_0905.jpg
- delete mode 120000 201304/jmg_0921.jpg
- delete mode 120000 201304/jmg_0922.jpg
- delete mode 120000 201304/jmg_0932.jpg
- delete mode 120000 201304/jmg_0935.jpg
- delete mode 120000 201304/jmg_0936.jpg
- delete mode 120000 201304/jmg_0937.jpg
- delete mode 120000 201304/jmg_0938.jpg
- delete mode 120000 201304/jmg_0942.jpg
- delete mode 120000 201304/jmg_0944.jpg
- delete mode 120000 201304/jmg_0946.jpg
- delete mode 120000 201304/jmg_0947.jpg
- delete mode 120000 201304/jmg_0948.jpg
- delete mode 120000 201304/jmg_0949.jpg
- delete mode 120000 201304/jmg_0950.jpg
- delete mode 120000 201304/jmg_0951.jpg
- delete mode 120000 201304/jmg_0952.jpg
- delete mode 120000 201304/jmg_0953.jpg
- delete mode 120000 201304/jmg_0954.jpg
- delete mode 120000 201304/jmg_0958.jpg
- delete mode 120000 201304/jmg_0959.jpg
- delete mode 120000 201304/jmg_0960.jpg
- delete mode 120000 201304/jmg_0961.jpg
- delete mode 120000 201304/jmg_0962.jpg
- delete mode 120000 201304/jmg_0963.jpg
- delete mode 120000 201304/jmg_0964.jpg
- delete mode 120000 201304/jmg_0965.jpg
- delete mode 120000 201304/jmg_0966.jpg
- delete mode 120000 201304/jmg_0967.jpg
- delete mode 120000 201304/jmg_0968.jpg
- delete mode 120000 201304/jmg_0969.jpg
- delete mode 120000 201304/jmg_0976.cr2
- delete mode 120000 201304/jmg_0976.jpg
- delete mode 120000 201304/jmg_0978.jpg
- delete mode 120000 201304/jmg_0979.jpg
- delete mode 120000 201304/jmg_0980.jpg
- delete mode 120000 201304/jmg_0981.cr2
- delete mode 120000 201304/jmg_0981.jpg
- delete mode 120000 201304/jmg_0982.jpg
- delete mode 120000 201304/jmg_0984.cr2
- delete mode 120000 201304/jmg_0984.jpg
- delete mode 120000 201304/jmg_0987.jpg
- delete mode 120000 201304/jmg_0988.jpg
- delete mode 120000 201304/jmg_0989.jpg
- delete mode 120000 201304/jmg_0990.jpg
- delete mode 120000 201304/jmg_0991.jpg
- delete mode 120000 201304/jmg_0992.jpg
- delete mode 120000 201304/jmg_1206.jpg
- delete mode 120000 201304/jmg_1207.jpg
- delete mode 120000 201304/jmg_1208.jpg
- delete mode 120000 201304/jmg_1209.jpg
- delete mode 120000 201304/jmg_1210.cr2
- delete mode 120000 201304/jmg_1210.jpg
- delete mode 120000 201304/jmg_1211.jpg
- delete mode 120000 201304/jmg_1212.jpg
- delete mode 120000 201304/jmg_1213.jpg
- delete mode 120000 201304/jmg_1214.cr2
- delete mode 120000 201304/jmg_1214.jpg
- delete mode 120000 201304/jmg_1215.jpg
- delete mode 120000 201304/jmg_1216.cr2
- delete mode 120000 201304/jmg_1216.jpg
- delete mode 120000 201304/jmg_1217.cr2
- delete mode 120000 201304/jmg_1217.jpg
- delete mode 120000 201304/jmg_1220.cr2
- delete mode 120000 201304/jmg_1220.jpg
- delete mode 120000 201304/jmg_1222.cr2
- delete mode 120000 201304/jmg_1222.jpg
- delete mode 120000 201304/jmg_1223.jpg
- delete mode 120000 201306/jmg_1465.jpg
- delete mode 120000 201306/jmg_1466.jpg
- delete mode 120000 201306/jmg_1467.jpg
- delete mode 120000 201306/jmg_1468.jpg
- delete mode 120000 201306/jmg_1469.jpg
- delete mode 120000 201306/jmg_1470.jpg
- delete mode 120000 201306/jmg_1471.jpg
- delete mode 120000 201306/jmg_1472.jpg
- delete mode 120000 201306/jmg_1473.jpg
- delete mode 120000 201306/jmg_1475.jpg
- delete mode 120000 201306/jmg_1476.jpg
- delete mode 120000 201306/jmg_1477.jpg
- delete mode 120000 201306/jmg_1478.jpg
- delete mode 120000 201306/jmg_1479.jpg
- delete mode 120000 201306/jmg_1480.jpg
- delete mode 120000 201306/jmg_1481.jpg
- delete mode 120000 201306/jmg_1482.jpg
- delete mode 120000 201306/jmg_1483.jpg
- delete mode 120000 201306/jmg_1484.jpg
- delete mode 120000 201306/jmg_1485.jpg
- delete mode 120000 201306/jmg_1486.jpg
- delete mode 120000 201306/jmg_1487.jpg
- delete mode 120000 201306/jmg_1488.jpg
- delete mode 120000 201306/jmg_1489.jpg
- delete mode 120000 201306/jmg_1490.jpg
- delete mode 120000 201306/jmg_1491.jpg
- delete mode 120000 201306/jmg_1492.jpg
- delete mode 120000 201306/jmg_1495.jpg
- delete mode 120000 201306/jmg_1496.jpg
- delete mode 120000 201306/jmg_1498.jpg
- delete mode 120000 201306/jmg_1499.jpg
- delete mode 120000 201306/jmg_1500.jpg
- delete mode 120000 201306/jmg_1501.jpg
- delete mode 120000 201306/jmg_1502.jpg
- delete mode 120000 201306/jmg_1504.jpg
- delete mode 120000 201306/jmg_1506.jpg
- delete mode 120000 201306/jmg_1510.jpg
- delete mode 120000 201306/jmg_1512.jpg
- delete mode 120000 201306/jmg_1513.jpg
- delete mode 120000 201306/jmg_1514.jpg
- delete mode 120000 201306/jmg_1515.jpg
- delete mode 120000 201306/jmg_1517.jpg
- delete mode 120000 201306/jmg_1520.jpg
- delete mode 120000 201306/jmg_1521.jpg
- delete mode 120000 201306/jmg_1526.jpg
- delete mode 120000 201306/jmg_1533.jpg
- delete mode 120000 201306/jmg_1540.jpg
- delete mode 120000 201306/jmg_1546.jpg
- delete mode 120000 201306/jmg_1547.jpg
- delete mode 120000 201306/jmg_1549.jpg
- delete mode 120000 201306/jmg_1550.jpg
- delete mode 120000 201306/jmg_1551.jpg
- delete mode 120000 201306/jmg_1552.jpg
- delete mode 120000 201306/jmg_1553.jpg
- delete mode 120000 201306/jmg_1555.jpg
- delete mode 120000 201306/jmg_1556.jpg
- delete mode 120000 201306/jmg_1557.jpg
- delete mode 120000 201306/jmg_1558.jpg
- delete mode 120000 201306/jmg_1559.jpg
- delete mode 120000 201306/jmg_1560.jpg
- delete mode 120000 201306/jmg_1562.jpg
- delete mode 120000 201306/jmg_1566.jpg
- delete mode 120000 201306/jmg_1568.jpg
- delete mode 120000 201306/jmg_1570.jpg
- delete mode 120000 201306/jmg_1571.jpg
- delete mode 120000 201306/jmg_1572.jpg
- delete mode 120000 201306/jmg_1574.jpg
- delete mode 120000 201306/jmg_1575.jpg
- delete mode 120000 201306/jmg_1576.jpg
- delete mode 120000 201306/jmg_1577.jpg
- delete mode 120000 201306/jmg_1578.jpg
- delete mode 120000 201306/jmg_1579.jpg
- delete mode 120000 201306/jmg_1579_raw.jpg
- delete mode 120000 201306/jmg_1581.jpg
- delete mode 120000 201306/jmg_1583.jpg
- delete mode 120000 201306/jmg_1583_cut.jpg
- delete mode 120000 201306/jmg_1583_raw.jpg
- delete mode 120000 201306/jmg_1584.jpg
- delete mode 120000 201306/jmg_1586.jpg
- delete mode 120000 201306/jmg_1587.jpg
- delete mode 120000 201306/jmg_1588.jpg
- delete mode 120000 201306/jmg_1589.jpg
- delete mode 120000 201306/jmg_1591.jpg
- delete mode 120000 201306/jmg_1592.jpg
- delete mode 120000 201306/jmg_1593.jpg
- delete mode 120000 201306/jmg_1593_raw.jpg
- delete mode 120000 201306/jmg_1594.jpg
- delete mode 120000 201306/jmg_1594_raw.jpg
- delete mode 120000 201306/jmg_1595.jpg
- delete mode 120000 201306/jmg_1596.jpg
- delete mode 120000 201306/jmg_1597.jpg
- delete mode 120000 201306/jmg_1599.jpg
- delete mode 120000 201306/jmg_1626.jpg
- delete mode 120000 201306/jmg_1628.jpg
- delete mode 120000 201306/jmg_1629.jpg
- delete mode 120000 201306/jmg_1630.jpg
- delete mode 120000 201306/jmg_1631.jpg
- delete mode 120000 201306/jmg_1633.jpg
- delete mode 120000 201306/jmg_1635.jpg
- delete mode 120000 201306/jmg_1636.jpg
- delete mode 120000 201306/jmg_1637.jpg
- delete mode 120000 201306/jmg_1638.jpg
- delete mode 120000 201306/jmg_1640.jpg
- delete mode 120000 201306/jmg_1642.jpg
- delete mode 120000 201306/jmg_1643.jpg
- delete mode 120000 201306/jmg_1644.jpg
- delete mode 120000 201306/jmg_1647.jpg
- delete mode 120000 201306/jmg_1649.jpg
- delete mode 120000 201306/jmg_1650.jpg
- delete mode 120000 201306/jmg_1651.jpg
- delete mode 120000 201306/jmg_1652.jpg
- delete mode 120000 201306/jmg_1653.jpg
- delete mode 120000 201306/jmg_1655.jpg
- delete mode 120000 201306/jmg_1656.jpg
- delete mode 120000 201306/jmg_1660.jpg
- delete mode 120000 201306/jmg_1667.jpg
- delete mode 120000 201306/jmg_1682.jpg
- delete mode 120000 201306/jmg_1688.jpg
- delete mode 120000 201306/jmg_1689.jpg
- delete mode 120000 201306/jmg_1701.jpg
- delete mode 120000 201306/jmg_1702.jpg
- delete mode 120000 201306/jmg_1703.jpg
- delete mode 120000 201306/jmg_1710.jpg
- delete mode 120000 201306/jmg_1710_raw.jpg
- delete mode 120000 201306/jmg_1715.jpg
- delete mode 120000 201306/jmg_1716.jpg
- delete mode 120000 201306/jmg_1719.jpg
- delete mode 120000 201306/jmg_1722.jpg
- delete mode 120000 201306/jmg_1723.jpg
- delete mode 120000 201306/jmg_1729.cr2
- delete mode 120000 201308/jmg_2038.jpg
- delete mode 120000 201308/jmg_2039.jpg
- delete mode 120000 201308/jmg_2040.jpg
- delete mode 120000 201308/jmg_2041.jpg
- delete mode 120000 201308/jmg_2042.jpg
- delete mode 120000 201308/jmg_2043.jpg
- delete mode 120000 201308/jmg_2045.jpg
- delete mode 120000 201308/jmg_2047.jpg
- delete mode 120000 201308/jmg_2048.jpg
- delete mode 120000 201308/jmg_2049.jpg
- delete mode 120000 201308/jmg_2050.jpg
- delete mode 120000 201308/jmg_2051.jpg
- delete mode 120000 201308/jmg_2052.jpg
- delete mode 120000 201308/jmg_2053.jpg
- delete mode 120000 201308/jmg_2054.jpg
- delete mode 120000 201308/jmg_2055.jpg
- delete mode 120000 201308/jmg_2056.jpg
- delete mode 120000 201308/jmg_2057.jpg
- delete mode 120000 201308/jmg_2058.jpg
- delete mode 120000 201308/jmg_2059.jpg
- delete mode 120000 201308/jmg_2060.jpg
- delete mode 120000 201308/jmg_2061.jpg
- delete mode 120000 201308/jmg_2062.jpg
- delete mode 120000 201308/jmg_2089.cr2
- delete mode 120000 201308/jmg_2089.jpg
- delete mode 120000 201308/jmg_2089_raw.jpg
- delete mode 120000 201308/jmg_2090.jpg
- delete mode 120000 201308/jmg_2091.jpg
- delete mode 120000 201308/jmg_2092.jpg
- delete mode 120000 201308/jmg_2093.jpg
- delete mode 120000 201308/jmg_2096.jpg
- delete mode 120000 201308/jmg_2097.jpg
- delete mode 120000 201308/jmg_2098.jpg
- delete mode 120000 201308/jmg_2099.cr2
- delete mode 120000 201308/jmg_2099.jpg
- delete mode 120000 201308/jmg_2099_raw.jpg
- delete mode 120000 201308/jmg_2100.cr2
- delete mode 120000 201308/jmg_2100.jpg
- delete mode 120000 201308/jmg_2100_raw.jpg
- delete mode 120000 201308/jmg_2102.jpg
- delete mode 120000 201308/jmg_2103.jpg
- delete mode 120000 201308/jmg_2104.jpg
- delete mode 120000 201308/jmg_2105.jpg
- delete mode 120000 201308/jmg_2106.jpg
- delete mode 120000 201308/jmg_2107.jpg
- delete mode 120000 201308/jmg_2108.jpg
- delete mode 120000 201308/jmg_2109.jpg
- delete mode 120000 201308/jmg_2110.jpg
- delete mode 120000 201308/jmg_2111.jpg
- delete mode 120000 201308/jmg_2112.jpg
- delete mode 120000 201308/jmg_2113.jpg
- delete mode 120000 201308/jmg_2114.jpg
- delete mode 120000 201308/jmg_2115.jpg
- delete mode 120000 201308/jmg_2117.jpg
- delete mode 120000 201308/jmg_2118.jpg
- delete mode 120000 201308/jmg_2119.jpg
- delete mode 120000 201308/jmg_2120.jpg
- delete mode 120000 201308/jmg_2122.jpg
- delete mode 120000 201308/jmg_2125.jpg
- delete mode 120000 201308/jmg_2127.jpg
- delete mode 120000 201308/jmg_2129.jpg
- delete mode 120000 201308/jmg_2130.jpg
- delete mode 120000 201308/jmg_2132.jpg
- delete mode 120000 201308/jmg_2134.jpg
- delete mode 120000 201308/jmg_2135.jpg
- delete mode 120000 201308/jmg_2136.jpg
- delete mode 120000 201308/jmg_2137.jpg
- delete mode 120000 201308/jmg_2138.jpg
- delete mode 120000 201308/jmg_2148.jpg
- delete mode 120000 201308/jmg_2150.jpg
- delete mode 120000 201308/jmg_2151.jpg
- delete mode 120000 201308/jmg_2156.jpg
- delete mode 120000 201308/jmg_2158.cr2
- delete mode 120000 201308/jmg_2158.jpg
- delete mode 120000 201308/jmg_2159.jpg
- delete mode 120000 201308/jmg_2160.jpg
- delete mode 120000 201308/jmg_2161.jpg
- delete mode 120000 201308/jmg_2162.jpg
- delete mode 120000 201308/jmg_2165.jpg
- delete mode 120000 201308/jmg_2166.jpg
- delete mode 120000 201308/jmg_2168.jpg
- delete mode 120000 201308/jmg_2169.jpg
- delete mode 120000 201308/jmg_2171.jpg
- delete mode 120000 201308/jmg_2173.jpg
- delete mode 120000 201308/jmg_2174.jpg
- delete mode 120000 201308/jmg_2175.jpg
- delete mode 120000 201308/jmg_2177.jpg
- delete mode 120000 201308/jmg_2178.jpg
- delete mode 120000 201308/jmg_2180.jpg
- delete mode 120000 201308/jmg_2181.jpg
- delete mode 120000 201308/jmg_2182.jpg
- delete mode 120000 201308/jmg_2183.jpg
- delete mode 120000 201308/jmg_2184.jpg
- delete mode 120000 201308/jmg_2187.jpg
- delete mode 120000 201308/jmg_2188.jpg
- delete mode 120000 201308/jmg_2189.jpg
- delete mode 120000 201308/jmg_2191.cr2
- delete mode 120000 201308/jmg_2191.jpg
- delete mode 120000 201308/jmg_2193.cr2
- delete mode 120000 201308/jmg_2193.jpg
- delete mode 120000 201308/jmg_2194.cr2
- delete mode 120000 201308/jmg_2194.jpg
- delete mode 120000 201308/jmg_2197.cr2
- delete mode 120000 201308/jmg_2197.jpg
- delete mode 120000 201308/jmg_2200.cr2
- delete mode 120000 201308/jmg_2200.jpg
- delete mode 120000 201308/jmg_2201.cr2
- delete mode 120000 201308/jmg_2201.jpg
- delete mode 120000 201308/jmg_2202.cr2
- delete mode 120000 201308/jmg_2202.jpg
- delete mode 120000 201308/jmg_2209.jpg
- delete mode 120000 201308/jmg_2210.jpg
- delete mode 120000 201308/jmg_2215.jpg
- delete mode 120000 201308/jmg_2216.jpg
- delete mode 120000 201308/jmg_2217.cr2
- delete mode 120000 201308/jmg_2217.jpg
- delete mode 120000 201308/jmg_2219.cr2
- delete mode 120000 201308/jmg_2219.jpg
- delete mode 120000 201308/jmg_2223.jpg
- delete mode 120000 201308/jmg_2224.jpg
- delete mode 120000 201308/jmg_2225.cr2
- delete mode 120000 201308/jmg_2225.jpg
- delete mode 120000 201308/jmg_2227.jpg
- delete mode 120000 201308/jmg_2228.jpg
- delete mode 120000 201308/jmg_2235.jpg
- delete mode 120000 201308/jmg_2237.jpg
- delete mode 120000 201308/jmg_2238.jpg
- delete mode 120000 201308/jmg_2239.cr2
- delete mode 120000 201308/jmg_2239.jpg
- delete mode 120000 201308/jmg_2239_raw.jpg
- delete mode 120000 201308/jmg_2240.jpg
- delete mode 120000 201308/jmg_2243.jpg
- delete mode 120000 201308/jmg_2244.jpg
- delete mode 120000 201308/jmg_2245.jpg
- delete mode 120000 201308/jmg_2247.cr2
- delete mode 120000 201308/jmg_2247.jpg
- delete mode 120000 201308/jmg_2249.jpg
- delete mode 120000 201308/jmg_2250.cr2
- delete mode 120000 201308/jmg_2250.jpg
- delete mode 120000 201308/jmg_2252.jpg
- delete mode 120000 201308/jmg_2253.jpg
- delete mode 120000 201308/jmg_2254.jpg
- create mode 120000 incoming/5d/201203/jmg_8701.cr2
- create mode 120000 incoming/5d/201203/jmg_8702.jpg
- create mode 120000 incoming/5d/201203/jmg_8705.jpg
- create mode 120000 incoming/5d/201203/jmg_8711.jpg
- create mode 120000 incoming/5d/201203/jmg_8717.jpg
- create mode 120000 incoming/5d/201203/jmg_8718.jpg
- create mode 120000 incoming/5d/201203/jmg_8719.jpg
- create mode 120000 incoming/5d/201203/jmg_8721.jpg
- create mode 120000 incoming/5d/201203/jmg_8725.jpg
- create mode 120000 incoming/5d/201203/jmg_8726.jpg
- create mode 120000 incoming/5d/201203/jmg_8731.jpg
- create mode 120000 incoming/5d/201203/jmg_8745.jpg
- create mode 120000 incoming/5d/201203/jmg_8747_raw.jpg
- create mode 120000 incoming/5d/201203/jmg_8750.cr2
- create mode 120000 incoming/5d/201203/jmg_8750.jpg
- create mode 120000 incoming/5d/201207/jmg_9048.jpg
- create mode 120000 incoming/5d/201207/jmg_9053.jpg
- create mode 120000 incoming/5d/201207/jmg_9054.jpg
- create mode 120000 incoming/5d/201207/jmg_9069.cr2
- create mode 120000 incoming/5d/201207/jmg_9069.jpg
- create mode 120000 incoming/5d/201207/jmg_9070.cr2
- create mode 120000 incoming/5d/201207/jmg_9070.jpg
- create mode 120000 incoming/5d/201207/jmg_9072.cr2
- create mode 120000 incoming/5d/201207/jmg_9072.jpg
- create mode 120000 incoming/5d/201207/jmg_9076.cr2
- create mode 120000 incoming/5d/201207/jmg_9076.jpg
- create mode 120000 incoming/5d/201302/jmg_0502.cr2
- create mode 120000 incoming/5d/201302/jmg_0502.jpg
- create mode 120000 incoming/5d/201302/jmg_0503.jpg
- create mode 120000 incoming/5d/201302/jmg_0507.jpg
- create mode 120000 incoming/5d/201302/jmg_0510.jpg
- create mode 120000 incoming/5d/201302/jmg_0512.jpg
- create mode 120000 incoming/5d/201302/jmg_0513.jpg
- create mode 120000 incoming/5d/201302/jmg_0514.jpg
- create mode 120000 incoming/5d/201302/jmg_0516.jpg
- create mode 120000 incoming/5d/201302/jmg_0517.jpg
- create mode 120000 incoming/5d/201302/jmg_0518.jpg
- create mode 120000 incoming/5d/201302/jmg_0521.jpg
- create mode 120000 incoming/5d/201302/jmg_0522.jpg
- create mode 120000 incoming/5d/201302/jmg_0523.jpg
- create mode 120000 incoming/5d/201302/jmg_0524.jpg
- create mode 120000 incoming/5d/201302/jmg_0526.jpg
- create mode 120000 incoming/5d/201302/jmg_0527.jpg
- create mode 120000 incoming/5d/201302/jmg_0528.jpg
- create mode 120000 incoming/5d/201302/jmg_0532.cr2
- create mode 120000 incoming/5d/201302/jmg_0532.jpg
- create mode 120000 incoming/5d/201302/jmg_0534.jpg
- create mode 120000 incoming/5d/201302/jmg_0535.jpg
- create mode 120000 incoming/5d/201302/jmg_0537.jpg
- create mode 120000 incoming/5d/201302/jmg_0539.jpg
- create mode 120000 incoming/5d/201302/jmg_0541.jpg
- create mode 120000 incoming/5d/201302/jmg_0543.jpg
- create mode 120000 incoming/5d/jmg_0021.jpg
- create mode 120000 incoming/5d/jmg_0025.jpg
- create mode 120000 incoming/5d/jmg_0026.jpg
- create mode 120000 incoming/5d/jmg_0027.jpg
- create mode 120000 incoming/5d/jmg_0034.jpg
- create mode 120000 incoming/5d/jmg_0035.jpg
- create mode 120000 incoming/5d/jmg_0036.jpg
- create mode 120000 incoming/5d/jmg_0130.jpg
- create mode 120000 incoming/5d/jmg_0131.jpg
- create mode 120000 incoming/5d/jmg_0133.jpg
- create mode 120000 incoming/5d/jmg_0155.jpg
- create mode 120000 incoming/5d/jmg_0156.jpg
- create mode 120000 incoming/5d/jmg_0158.cr2
- create mode 120000 incoming/5d/jmg_0165.cr2
- create mode 120000 incoming/5d/jmg_0166.cr2
- create mode 120000 incoming/5d/jmg_0178.cr2
- create mode 120000 incoming/5d/jmg_0179.jpg
- create mode 120000 incoming/5d/jmg_0180.cr2
- create mode 120000 incoming/5d/jmg_0184.jpg
- create mode 120000 incoming/5d/jmg_0185.cr2
- create mode 120000 incoming/5d/jmg_0187.cr2
- create mode 120000 incoming/5d/jmg_0310.jpg
- create mode 120000 incoming/5d/jmg_0312.jpg
- create mode 120000 incoming/5d/jmg_0315.jpg
- create mode 120000 incoming/5d/jmg_0340.jpg
- create mode 120000 incoming/5d/jmg_0357.jpg
- create mode 120000 incoming/5d/jmg_0364.jpg
- create mode 120000 incoming/5d/jmg_0365.jpg
- create mode 120000 incoming/5d/jmg_0368.jpg
- create mode 120000 incoming/5d/jmg_0374.jpg
- create mode 120000 incoming/5d/jmg_0375.jpg
- create mode 120000 incoming/5d/jmg_0386.jpg
- create mode 120000 incoming/5d/jmg_0399.jpg
- create mode 120000 incoming/5d/jmg_0411.jpg
- create mode 120000 incoming/5d/jmg_0418.jpg
- create mode 120000 incoming/5d/jmg_0476.cr2
- create mode 120000 incoming/5d/jmg_0476.jpg
- create mode 120000 incoming/5d/jmg_0503.jpg
- create mode 120000 incoming/5d/jmg_0507.cr2
- create mode 120000 incoming/5d/jmg_0513.cr2
- create mode 120000 incoming/5d/jmg_0513.jpg
- create mode 120000 incoming/5d/jmg_0516.cr2
- create mode 120000 incoming/5d/jmg_0517.cr2
- create mode 120000 incoming/5d/jmg_0518.jpg
- create mode 120000 incoming/5d/jmg_0522.cr2
- create mode 120000 incoming/5d/jmg_0524.cr2
- create mode 120000 incoming/5d/jmg_0524.jpg
- create mode 120000 incoming/5d/jmg_0530.jpg
- create mode 120000 incoming/5d/jmg_0541.cr2
- create mode 120000 incoming/5d/jmg_0550.jpg
- create mode 120000 incoming/5d/jmg_0554.jpg
- create mode 120000 incoming/5d/jmg_0555.jpg
- create mode 120000 incoming/5d/jmg_0558.jpg
- create mode 120000 incoming/5d/jmg_0563.jpg
- create mode 120000 incoming/5d/jmg_0573.jpg
- create mode 120000 incoming/5d/jmg_0575.cr2
- create mode 120000 incoming/5d/jmg_0578.cr2
- create mode 120000 incoming/5d/jmg_0579.cr2
- create mode 120000 incoming/5d/jmg_0582.jpg
- create mode 120000 incoming/5d/jmg_0593.cr2
- create mode 120000 incoming/5d/jmg_0594.cr2
- create mode 120000 incoming/5d/jmg_0594.jpg
- create mode 120000 incoming/5d/jmg_0595.cr2
- create mode 120000 incoming/5d/jmg_0600.jpg
- create mode 120000 incoming/5d/jmg_0606.cr2
- create mode 120000 incoming/5d/jmg_0607.jpg
- create mode 120000 incoming/5d/jmg_0610.cr2
- create mode 120000 incoming/5d/jmg_0610.jpg
- create mode 120000 incoming/5d/jmg_0612.jpg
- create mode 120000 incoming/5d/jmg_0613.cr2
- create mode 120000 incoming/5d/jmg_0614.jpg
- create mode 120000 incoming/5d/jmg_0619.cr2
- create mode 120000 incoming/5d/jmg_0623.jpg
- create mode 120000 incoming/5d/jmg_0628.cr2
- create mode 120000 incoming/5d/jmg_0628.jpg
- create mode 120000 incoming/5d/jmg_0639.jpg
- create mode 120000 incoming/5d/jmg_0645.cr2
- create mode 120000 incoming/5d/jmg_0646.jpg
- create mode 120000 incoming/5d/jmg_0647.cr2
- create mode 120000 incoming/5d/jmg_0648.jpg
- create mode 120000 incoming/5d/jmg_0649.jpg
- create mode 120000 incoming/5d/jmg_0655.jpg
- create mode 120000 incoming/5d/jmg_0667.jpg
- create mode 120000 incoming/5d/jmg_0670.jpg
- create mode 120000 incoming/5d/jmg_0673.jpg
- create mode 120000 incoming/5d/jmg_0679.jpg
- create mode 120000 incoming/5d/jmg_0685.jpg
- create mode 120000 incoming/5d/jmg_0699.cr2
- create mode 120000 incoming/5d/jmg_0700.cr2
- create mode 120000 incoming/5d/jmg_0701.cr2
- create mode 120000 incoming/5d/jmg_0708.jpg
- create mode 120000 incoming/5d/jmg_0718.jpg
- create mode 120000 incoming/5d/jmg_0726.cr2
- create mode 120000 incoming/5d/jmg_0728.jpg
- create mode 120000 incoming/5d/jmg_0730.jpg
- create mode 120000 incoming/5d/jmg_0734.jpg
- create mode 120000 incoming/5d/jmg_0740.jpg
- create mode 120000 incoming/5d/jmg_0743.cr2
- create mode 120000 incoming/5d/jmg_0744.cr2
- create mode 120000 incoming/5d/jmg_0745.cr2
- create mode 120000 incoming/5d/jmg_0747.jpg
- create mode 120000 incoming/5d/jmg_0750.cr2
- create mode 120000 incoming/5d/jmg_0755.cr2
- create mode 120000 incoming/5d/jmg_0759.cr2
- create mode 120000 incoming/5d/jmg_0760.cr2
- create mode 120000 incoming/5d/jmg_0761.jpg
- create mode 120000 incoming/5d/jmg_0765.jpg
- create mode 120000 incoming/5d/jmg_0768.jpg
- create mode 120000 incoming/5d/jmg_0771.jpg
- create mode 120000 incoming/5d/jmg_0778.jpg
- create mode 120000 incoming/5d/jmg_0780.jpg
- create mode 120000 incoming/5d/jmg_0782.cr2
- create mode 120000 incoming/5d/jmg_0786.cr2
- create mode 120000 incoming/5d/jmg_0787.cr2
- create mode 120000 incoming/5d/jmg_0788.cr2
- create mode 120000 incoming/5d/jmg_0794.jpg
- create mode 120000 incoming/5d/jmg_0796.jpg
- create mode 120000 incoming/5d/jmg_0801.cr2
- create mode 120000 incoming/5d/jmg_0803.cr2
- create mode 120000 incoming/5d/jmg_0804.cr2
- create mode 120000 incoming/5d/jmg_0812.jpg
- create mode 120000 incoming/5d/jmg_0819.jpg
- create mode 120000 incoming/5d/jmg_0827.jpg
- create mode 120000 incoming/5d/jmg_0830.jpg
- create mode 120000 incoming/5d/jmg_0842.jpg
- create mode 120000 incoming/5d/jmg_0846.jpg
- create mode 120000 incoming/5d/jmg_0857.cr2
- create mode 120000 incoming/5d/jmg_0863.jpg
- create mode 120000 incoming/5d/jmg_0866.cr2
- create mode 120000 incoming/5d/jmg_0868.cr2
- create mode 120000 incoming/5d/jmg_0868.jpg
- create mode 120000 incoming/5d/jmg_0870.jpg
- create mode 120000 incoming/5d/jmg_0877.jpg
- create mode 120000 incoming/5d/jmg_0882.cr2
- create mode 120000 incoming/5d/jmg_0883.jpg
- create mode 120000 incoming/5d/jmg_0888.jpg
- create mode 120000 incoming/5d/jmg_0891.jpg
- create mode 120000 incoming/5d/jmg_0894.cr2
- create mode 120000 incoming/5d/jmg_0896.cr2
- create mode 120000 incoming/5d/jmg_0897.cr2
- create mode 120000 incoming/5d/jmg_0898.jpg
- create mode 120000 incoming/5d/jmg_0899.cr2
- create mode 120000 incoming/5d/jmg_0900.jpg
- create mode 120000 incoming/5d/jmg_0905.jpg
- create mode 120000 incoming/5d/jmg_0908.jpg
- create mode 120000 incoming/5d/jmg_0914.jpg
- create mode 120000 incoming/5d/jmg_0915.jpg
- create mode 120000 incoming/5d/jmg_0916.jpg
- create mode 120000 incoming/5d/jmg_0923.jpg
- create mode 120000 incoming/5d/jmg_0924.jpg
- create mode 120000 incoming/5d/jmg_0926.jpg
- create mode 120000 incoming/5d/jmg_0928.jpg
- create mode 120000 incoming/5d/jmg_0929.jpg
- create mode 120000 incoming/5d/jmg_0936.jpg
- create mode 120000 incoming/5d/jmg_0942.jpg
- create mode 120000 incoming/5d/jmg_0944.jpg
- create mode 120000 incoming/5d/jmg_0948.jpg
- create mode 120000 incoming/5d/jmg_0960.jpg
- create mode 120000 incoming/5d/jmg_0966.jpg
- create mode 120000 incoming/5d/jmg_0970.cr2
- create mode 120000 incoming/5d/jmg_0970.jpg
- create mode 120000 incoming/5d/jmg_0972.jpg
- create mode 120000 incoming/5d/jmg_0976.jpg
- create mode 120000 incoming/5d/jmg_0983.cr2
- create mode 120000 incoming/5d/jmg_0985.cr2
- create mode 120000 incoming/5d/jmg_0985.jpg
- create mode 120000 incoming/5d/jmg_0994.jpg
- create mode 120000 incoming/5d/jmg_1209.cr2
- create mode 120000 incoming/5d/jmg_1209.jpg
- create mode 120000 incoming/5d/jmg_1211.cr2
- create mode 120000 incoming/5d/jmg_1211.jpg
- create mode 120000 incoming/5d/jmg_1217.cr2
- create mode 120000 incoming/5d/jmg_1467.cr2
- create mode 120000 incoming/5d/jmg_1469.jpg
- create mode 120000 incoming/5d/jmg_1470.cr2
- create mode 120000 incoming/5d/jmg_1471.cr2
- create mode 120000 incoming/5d/jmg_1472.cr2
- create mode 120000 incoming/5d/jmg_1477.cr2
- create mode 120000 incoming/5d/jmg_1477.jpg
- create mode 120000 incoming/5d/jmg_1481.cr2
- create mode 120000 incoming/5d/jmg_1483.cr2
- create mode 120000 incoming/5d/jmg_1485.jpg
- create mode 120000 incoming/5d/jmg_1488.jpg
- create mode 120000 incoming/5d/jmg_1491.jpg
- create mode 120000 incoming/5d/jmg_1496.cr2
- create mode 120000 incoming/5d/jmg_1502.jpg
- create mode 120000 incoming/5d/jmg_1503.cr2
- create mode 120000 incoming/5d/jmg_1504.jpg
- create mode 120000 incoming/5d/jmg_1507.jpg
- create mode 120000 incoming/5d/jmg_1515.jpg
- create mode 120000 incoming/5d/jmg_1520.jpg
- create mode 120000 incoming/5d/jmg_1523.jpg
- create mode 120000 incoming/5d/jmg_1525.jpg
- create mode 120000 incoming/5d/jmg_1539.jpg
- create mode 120000 incoming/5d/jmg_1542.jpg
- create mode 120000 incoming/5d/jmg_1546.jpg
- create mode 120000 incoming/5d/jmg_1547.cr2
- create mode 120000 incoming/5d/jmg_1549.jpg
- create mode 120000 incoming/5d/jmg_1552.jpg
- create mode 120000 incoming/5d/jmg_1554.cr2
- create mode 120000 incoming/5d/jmg_1555.cr2
- create mode 120000 incoming/5d/jmg_1556.cr2
- create mode 120000 incoming/5d/jmg_1559.cr2
- create mode 120000 incoming/5d/jmg_1560.cr2
- create mode 120000 incoming/5d/jmg_1561.cr2
- create mode 120000 incoming/5d/jmg_1562.cr2
- create mode 120000 incoming/5d/jmg_1565.cr2
- create mode 120000 incoming/5d/jmg_1567.cr2
- create mode 120000 incoming/5d/jmg_1572.cr2
- create mode 120000 incoming/5d/jmg_1577.cr2
- create mode 120000 incoming/5d/jmg_1578.jpg
- create mode 120000 incoming/5d/jmg_1583_cut.jpg
- create mode 120000 incoming/5d/jmg_1583_raw.jpg
- create mode 120000 incoming/5d/jmg_1592.cr2
- create mode 120000 incoming/5d/jmg_1593.jpg
- create mode 120000 incoming/5d/jmg_1626.cr2
- create mode 120000 incoming/5d/jmg_1627.jpg
- create mode 120000 incoming/5d/jmg_1628.cr2
- create mode 120000 incoming/5d/jmg_1629.jpg
- create mode 120000 incoming/5d/jmg_1630.cr2
- create mode 120000 incoming/5d/jmg_1631.cr2
- create mode 120000 incoming/5d/jmg_1633.cr2
- create mode 120000 incoming/5d/jmg_1638.jpg
- create mode 120000 incoming/5d/jmg_1639.cr2
- create mode 120000 incoming/5d/jmg_1646.cr2
- create mode 120000 incoming/5d/jmg_1646.jpg
- create mode 120000 incoming/5d/jmg_1650.jpg
- create mode 120000 incoming/5d/jmg_1651.cr2
- create mode 120000 incoming/5d/jmg_1654.cr2
- create mode 120000 incoming/5d/jmg_1656.jpg
- create mode 120000 incoming/5d/jmg_1677.jpg
- create mode 120000 incoming/5d/jmg_1689.jpg
- create mode 120000 incoming/5d/jmg_1701.jpg
- create mode 120000 incoming/5d/jmg_1703.jpg
- create mode 120000 incoming/5d/jmg_1723.jpg
- create mode 120000 incoming/5d/jmg_2039.jpg
- create mode 120000 incoming/5d/jmg_2041.jpg
- create mode 120000 incoming/5d/jmg_2048.cr2
- create mode 120000 incoming/5d/jmg_2052.jpg
- create mode 120000 incoming/5d/jmg_2061.jpg
- delete mode 120000 incoming/5d/jmg_2064_raw.jpg
- delete mode 120000 incoming/5d/jmg_2065_mo.jpg
- delete mode 120000 incoming/5d/jmg_2065_raw.jpg
- delete mode 120000 incoming/5d/jmg_2066_mo.jpg
- delete mode 120000 incoming/5d/jmg_2066_raw.jpg
- create mode 120000 incoming/5d/jmg_2090.jpg
- create mode 120000 incoming/5d/jmg_2093.jpg
- create mode 120000 incoming/5d/jmg_2100.cr2
- create mode 120000 incoming/5d/jmg_2103.jpg
- create mode 120000 incoming/5d/jmg_2107.jpg
- create mode 120000 incoming/5d/jmg_2108.jpg
- create mode 120000 incoming/5d/jmg_2112.jpg
- create mode 120000 incoming/5d/jmg_2118.jpg
- create mode 120000 incoming/5d/jmg_2119.jpg
- create mode 120000 incoming/5d/jmg_2122.jpg
- create mode 120000 incoming/5d/jmg_2125.jpg
- create mode 120000 incoming/5d/jmg_2137.jpg
- create mode 120000 incoming/5d/jmg_2149.jpg
- create mode 120000 incoming/5d/jmg_2150.jpg
- create mode 120000 incoming/5d/jmg_2158.cr2
- create mode 120000 incoming/5d/jmg_2160.jpg
- create mode 120000 incoming/5d/jmg_2165.jpg
- create mode 120000 incoming/5d/jmg_2188.jpg
- create mode 120000 incoming/5d/jmg_2189.jpg
- create mode 120000 incoming/5d/jmg_2193.jpg
- create mode 120000 incoming/5d/jmg_2194.cr2
- create mode 120000 incoming/5d/jmg_2200.jpg
- create mode 120000 incoming/5d/jmg_2201.cr2
- create mode 120000 incoming/5d/jmg_2201.jpg
- create mode 120000 incoming/5d/jmg_2210.jpg
- create mode 120000 incoming/5d/jmg_2215.cr2
- create mode 120000 incoming/5d/jmg_2216.cr2
- create mode 120000 incoming/5d/jmg_2216.jpg
- create mode 120000 incoming/5d/jmg_2224.jpg
- create mode 120000 incoming/5d/jmg_2235.jpg
- create mode 120000 incoming/5d/jmg_2238.jpg
- create mode 120000 incoming/5d/jmg_2239.cr2
- create mode 120000 incoming/5d/jmg_2239.jpg
- create mode 120000 incoming/5d/jmg_2240.jpg
- create mode 120000 incoming/5d/jmg_2244.jpg
- create mode 120000 incoming/5d/jmg_2247.jpg
- create mode 120000 incoming/5d/jmg_7250.cr2
- create mode 120000 incoming/5d/jmg_7250.jpg
- create mode 120000 incoming/5d/jmg_7256.jpg
- create mode 120000 incoming/5d/jmg_7257.cr2
- create mode 120000 incoming/5d/jmg_7259.cr2
- create mode 120000 incoming/5d/jmg_7263.jpg
- create mode 120000 incoming/5d/jmg_7265.cr2
- create mode 120000 incoming/5d/jmg_7269.cr2
- create mode 120000 incoming/5d/jmg_7270.cr2
- create mode 120000 incoming/5d/jmg_7279.cr2
- create mode 120000 incoming/5d/jmg_7286.cr2
- create mode 120000 incoming/5d/jmg_7286.jpg
- create mode 120000 incoming/5d/jmg_7290.cr2
- create mode 120000 incoming/5d/jmg_7290.jpg
- create mode 120000 incoming/5d/jmg_7293.cr2
- create mode 120000 incoming/5d/jmg_7296.cr2
- create mode 120000 incoming/5d/jmg_7299.jpg
- create mode 120000 incoming/5d/jmg_7300.cr2
- create mode 120000 incoming/5d/jmg_7300.jpg
- create mode 120000 incoming/5d/jmg_7305_raw.jpg
- create mode 120000 incoming/5d/jmg_8532.cr2
- create mode 120000 incoming/5d/jmg_8533.cr2
- create mode 120000 incoming/5d/jmg_8534.cr2
- create mode 120000 incoming/5d/jmg_8536.jpg
- create mode 120000 incoming/5d/jmg_8538.cr2
- create mode 120000 incoming/5d/jmg_8549.cr2
- create mode 120000 incoming/5d/jmg_8549.jpg
- create mode 120000 incoming/5d/jmg_8552.cr2
- create mode 120000 incoming/5d/jmg_8557.cr2
- create mode 120000 incoming/5d/jmg_8560.cr2
- create mode 120000 incoming/5d/jmg_8565.cr2
- create mode 120000 incoming/5d/jmg_8566.cr2
- create mode 120000 incoming/5d/jmg_8569.jpg
- create mode 120000 incoming/5d/jmg_8575.jpg
- create mode 120000 incoming/5d/jmg_8576.jpg
- create mode 120000 incoming/5d/jmg_8578.cr2
- create mode 120000 incoming/5d/jmg_8579.cr2
- create mode 120000 incoming/5d/jmg_8580.jpg
- create mode 120000 incoming/5d/jmg_8583.cr2
- create mode 120000 incoming/5d/jmg_8588.cr2
- create mode 120000 incoming/5d/jmg_8589.cr2
- create mode 120000 incoming/5d/jmg_8595.jpg
- create mode 120000 incoming/5d/jmg_8597.jpg
- create mode 120000 incoming/5d/jmg_8599.jpg
- create mode 120000 incoming/5d/jmg_8602.cr2
- create mode 120000 incoming/5d/jmg_8603.cr2
- create mode 120000 incoming/5d/jmg_8606.cr2
- create mode 120000 incoming/5d/jmg_8606.jpg
- create mode 120000 incoming/5d/jmg_8609.jpg
- create mode 120000 incoming/5d/jmg_8613.jpg
- create mode 120000 incoming/5d/jmg_8615.cr2
- create mode 120000 incoming/5d/jmg_8617.jpg
- create mode 120000 incoming/5d/jmg_8619.cr2
- create mode 120000 incoming/5d/jmg_8620.jpg
- create mode 120000 incoming/5d/jmg_8625.jpg
- create mode 120000 incoming/5d/jmg_8627.jpg
- create mode 120000 incoming/5d/jmg_8628.jpg
- create mode 120000 incoming/5d/jmg_8632.cr2
- create mode 120000 incoming/5d/jmg_8636.cr2
- create mode 120000 incoming/5d/jmg_8636.jpg
- create mode 120000 incoming/5d/jmg_8637.cr2
- create mode 120000 incoming/5d/jmg_8639.jpg
- create mode 120000 incoming/5d/jmg_8640.cr2
- create mode 120000 incoming/5d/jmg_8655.jpg
- create mode 120000 incoming/5d/jmg_8657.jpg
- create mode 120000 incoming/5d/jmg_8670.cr2
- create mode 120000 incoming/5d/jmg_8673.jpg
- create mode 120000 incoming/5d/jmg_8674.cr2
- create mode 120000 incoming/5d/jmg_8676.cr2
- create mode 120000 incoming/5d/jmg_8676.jpg
- create mode 120000 incoming/5d/jmg_8677.cr2
- create mode 120000 incoming/5d/jmg_8681.jpg
- create mode 120000 incoming/5d/jmg_8682.cr2
- create mode 120000 incoming/5d/jmg_8702.cr2
- create mode 120000 incoming/5d/jmg_8702.jpg
- create mode 120000 incoming/5d/jmg_8707.jpg
- create mode 120000 incoming/5d/jmg_8714.jpg
- create mode 120000 incoming/5d/jmg_8716.jpg
- create mode 120000 incoming/5d/jmg_8717.cr2
- create mode 120000 incoming/5d/jmg_8719.jpg
- create mode 120000 incoming/5d/jmg_8721.jpg
- create mode 120000 incoming/5d/jmg_8727.cr2
- create mode 120000 incoming/5d/jmg_8730.jpg
- create mode 120000 incoming/5d/jmg_8736.cr2
- create mode 120000 incoming/5d/jmg_8737.cr2
- create mode 120000 incoming/5d/jmg_8742.cr2
- create mode 120000 incoming/5d/jmg_8742.jpg
- create mode 120000 incoming/5d/jmg_8745.jpg
- create mode 120000 incoming/5d/jmg_8748.cr2
- create mode 120000 incoming/5d/jmg_8748.jpg
- create mode 120000 incoming/5d/jmg_8751.cr2
- create mode 120000 incoming/5d/jmg_8755.cr2
- create mode 120000 incoming/5d/jmg_8757.cr2
- create mode 120000 incoming/5d/jmg_8760.cr2
- create mode 120000 incoming/5d/jmg_8760.jpg
- create mode 120000 incoming/5d/jmg_8765.cr2
- create mode 120000 incoming/5d/jmg_8771.jpg
- create mode 120000 incoming/5d/jmg_8801.jpg
- create mode 120000 incoming/5d/jmg_8803.cr2
- create mode 120000 incoming/5d/jmg_8803.jpg
- create mode 120000 incoming/5d/jmg_8804.jpg
- create mode 120000 incoming/5d/jmg_8805.jpg
- create mode 120000 incoming/5d/jmg_8813.jpg
- create mode 120000 incoming/5d/jmg_8816.cr2
- create mode 120000 incoming/5d/jmg_8823.jpg
- create mode 120000 incoming/5d/jmg_8827.cr2
- create mode 120000 incoming/5d/jmg_8829.cr2
- create mode 120000 incoming/5d/jmg_8832.jpg
- create mode 120000 incoming/5d/jmg_8833.cr2
- create mode 120000 incoming/5d/jmg_8837.cr2
- create mode 120000 incoming/5d/jmg_8838.jpg
- create mode 120000 incoming/5d/jmg_8840.jpg
- create mode 120000 incoming/5d/jmg_8842.jpg
- create mode 120000 incoming/5d/jmg_8844.cr2
- create mode 120000 incoming/5d/jmg_8850.cr2
- create mode 120000 incoming/5d/jmg_8850.jpg
- create mode 120000 incoming/5d/jmg_8852.cr2
- create mode 120000 incoming/5d/jmg_8853.cr2
- create mode 120000 incoming/5d/jmg_8853.jpg
- create mode 120000 incoming/5d/jmg_8856.cr2
- create mode 120000 incoming/5d/jmg_8859.jpg
- create mode 120000 incoming/5d/jmg_8863.jpg
- create mode 120000 incoming/5d/jmg_8870.jpg
- create mode 120000 incoming/5d/jmg_8871.cr2
- create mode 120000 incoming/5d/jmg_8871.jpg
- create mode 120000 incoming/5d/jmg_8881.jpg
- create mode 120000 incoming/5d/jmg_8883.jpg
- create mode 120000 incoming/5d/jmg_8886.jpg
- create mode 120000 incoming/5d/jmg_8887.cr2
- create mode 120000 incoming/5d/jmg_8889.cr2
- create mode 120000 incoming/5d/jmg_8894.cr2
- create mode 120000 incoming/5d/jmg_8897.cr2
- create mode 120000 incoming/5d/jmg_8898.cr2
- create mode 120000 incoming/5d/jmg_8900.jpg
- create mode 120000 incoming/5d/jmg_8901.cr2
- create mode 120000 incoming/5d/jmg_8902.cr2
- create mode 120000 incoming/5d/jmg_8904.cr2
- create mode 120000 incoming/5d/jmg_8906.jpg
- create mode 120000 incoming/5d/jmg_8908.cr2
- create mode 120000 incoming/5d/jmg_8920.cr2
- create mode 120000 incoming/5d/jmg_8920.jpg
- create mode 120000 incoming/5d/jmg_8922.cr2
- create mode 120000 incoming/5d/jmg_8922.jpg
- create mode 120000 incoming/5d/jmg_8923.cr2
- create mode 120000 incoming/5d/jmg_8924.jpg
- create mode 120000 incoming/5d/jmg_8925.cr2
- create mode 120000 incoming/5d/jmg_8929.jpg
- create mode 120000 incoming/5d/jmg_8930.jpg
- create mode 120000 incoming/5d/jmg_8937.cr2
- create mode 120000 incoming/5d/jmg_8939.cr2
- create mode 120000 incoming/5d/jmg_8940.jpg
- create mode 120000 incoming/5d/jmg_8941.jpg
- create mode 120000 incoming/5d/jmg_8943.cr2
- create mode 120000 incoming/5d/jmg_8944.jpg
- create mode 120000 incoming/5d/jmg_8950.cr2
- create mode 120000 incoming/5d/jmg_8951.jpg
- create mode 120000 incoming/5d/jmg_8955.jpg
- create mode 120000 incoming/5d/jmg_8959.cr2
- create mode 120000 incoming/5d/jmg_8960.jpg
- create mode 120000 incoming/5d/jmg_8962.cr2
- create mode 120000 incoming/5d/jmg_8964.cr2
- create mode 120000 incoming/5d/jmg_8965.jpg
- create mode 120000 incoming/5d/jmg_8966.jpg
- create mode 120000 incoming/5d/jmg_8971.jpg
- create mode 120000 incoming/5d/jmg_8976.jpg
- create mode 120000 incoming/5d/jmg_8978.cr2
- create mode 120000 incoming/5d/jmg_8981.jpg
- create mode 120000 incoming/5d/jmg_8982.jpg
- create mode 120000 incoming/5d/jmg_8985.jpg
- create mode 120000 incoming/5d/jmg_8988.cr2
- create mode 120000 incoming/5d/jmg_8988.jpg
- create mode 120000 incoming/5d/jmg_8992.cr2
- create mode 120000 incoming/5d/jmg_8995.jpg
- create mode 120000 incoming/5d/jmg_8996.cr2
- create mode 120000 incoming/5d/jmg_8997.cr2
- create mode 120000 incoming/5d/jmg_8999.cr2
- create mode 120000 incoming/5d/jmg_9000.cr2
- create mode 120000 incoming/5d/jmg_9015.cr2
- create mode 120000 incoming/5d/jmg_9017.cr2
- create mode 120000 incoming/5d/jmg_9019.cr2
- create mode 120000 incoming/5d/jmg_9021.cr2
- create mode 120000 incoming/5d/jmg_9021.jpg
- create mode 120000 incoming/5d/jmg_9022.cr2
- create mode 120000 incoming/5d/jmg_9027.cr2
- create mode 120000 incoming/5d/jmg_9028.jpg
- create mode 120000 incoming/5d/jmg_9031.cr2
- create mode 120000 incoming/5d/jmg_9035.cr2
- create mode 120000 incoming/5d/jmg_9043.jpg
- create mode 120000 incoming/5d/jmg_9057.cr2
- create mode 120000 incoming/5d/jmg_9064.cr2
- create mode 120000 incoming/5d/jmg_9077.jpg
- create mode 120000 incoming/5d/jmg_9078.jpg
- create mode 120000 incoming/5d/jmg_9081.jpg
- create mode 120000 incoming/5d/jmg_9082.cr2
- create mode 120000 incoming/5d/jmg_9083.jpg
- create mode 120000 incoming/5d/jmg_9086.cr2
- create mode 120000 incoming/5d/jmg_9088.jpg
- create mode 120000 incoming/5d/jmg_9308.jpg
- create mode 120000 incoming/5d/jmg_9312.cr2
- create mode 120000 incoming/5d/jmg_9313.jpg
- create mode 120000 incoming/5d/jmg_9319.jpg
- create mode 120000 incoming/5d/jmg_9521.cr2
- create mode 120000 incoming/5d/jmg_9522.cr2
- create mode 120000 incoming/5d/jmg_9533.jpg
- create mode 120000 incoming/5d/jmg_9534.jpg
- create mode 120000 incoming/5d/jmg_9535.cr2
- create mode 120000 incoming/5d/jmg_9538.cr2
- create mode 120000 incoming/5d/jmg_9538.jpg
- create mode 120000 incoming/5d/jmg_9540.jpg
- create mode 120000 incoming/5d/jmg_9542.cr2
- create mode 120000 incoming/5d/jmg_9545.jpg
- create mode 120000 incoming/5d/jmg_9554.jpg
- create mode 120000 incoming/5d/jmg_9555.jpg
- create mode 120000 incoming/5d/jmg_9558.jpg
- create mode 120000 incoming/5d/jmg_9561.cr2
- create mode 120000 incoming/5d/jmg_9585.cr2
- create mode 120000 incoming/5d/jmg_9587.jpg
- create mode 120000 incoming/5d/jmg_9591.jpg
- create mode 120000 incoming/5d/jmg_9595.jpg
- create mode 120000 incoming/5d/jmg_9598.cr2
- create mode 120000 incoming/5d/jmg_9600.jpg
- create mode 120000 incoming/5d/jmg_9604.jpg
- create mode 120000 incoming/5d/jmg_9610.jpg
- create mode 120000 incoming/5d/jmg_9613.cr2
- create mode 120000 incoming/5d/jmg_9613.jpg
- create mode 120000 incoming/5d/jmg_9614.cr2
- create mode 120000 incoming/5d/jmg_9618.jpg
- create mode 120000 incoming/5d/jmg_9619.jpg
- create mode 120000 incoming/5d/jmg_9620.jpg
- create mode 120000 incoming/5d/jmg_9621.jpg
- create mode 120000 incoming/5d/jmg_9623.cr2
- create mode 120000 incoming/5d/jmg_9746.jpg
- create mode 120000 incoming/5d/jmg_9763.cr2
- create mode 120000 incoming/5d/jmg_9763.jpg
- create mode 120000 incoming/5d/jmg_9764.cr2
- create mode 120000 incoming/5d/jmg_9772.jpg
- create mode 120000 incoming/5d/jmg_9773.jpg
- create mode 120000 incoming/5d/jmg_9781.jpg
- create mode 120000 incoming/5d/jmg_9790.jpg
- create mode 120000 incoming/5d/jmg_9800.jpg
- create mode 120000 incoming/5d/jmg_9808.jpg
- create mode 120000 incoming/5d/jmg_9830.jpg
- create mode 120000 incoming/5d/jmg_9834.cr2
- create mode 120000 incoming/5d/jmg_9843.jpg
- create mode 120000 incoming/5d/jmg_9848.jpg
- create mode 120000 incoming/5d/jmg_9849.jpg
- create mode 120000 incoming/5d/jmg_9853.cr2
- create mode 120000 incoming/5d/jmg_9856.jpg
- create mode 120000 incoming/5d/jmg_9857.cr2
- create mode 120000 incoming/5d/jmg_9859.cr2
- create mode 120000 incoming/5d/jmg_9860.jpg
- create mode 120000 incoming/5d/jmg_9917.jpg
- create mode 120000 incoming/5d/jmg_9923.jpg
- create mode 120000 incoming/5d/jmg_9926.jpg
- create mode 120000 incoming/5d/jmg_9975.cr2
- create mode 120000 incoming/5d/jmg_9976.cr2
- create mode 120000 incoming/5d/jmg_9978.jpg
- create mode 120000 incoming/5d/jmg_9988.jpg
- create mode 120000 incoming/5d/jmg_9997.cr2
- create mode 120000 incoming/5d/jmg_9998.jpg
- create mode 120000 incoming/5d/jmg_9999.jpg
- delete mode 120000 list_5d_repoB
- create mode 120000 only_on_repoB
- delete mode 120000 dir/2012/dir2/jmg_0128.cr2
- delete mode 120000 dir/2012/dir2/jmg_0128.jpg
- delete mode 120000 dir/2012/dir2/jmg_0129.cr2
- delete mode 120000 dir/2012/dir2/jmg_0129.jpg
- delete mode 120000 dir/2012/dir2/jmg_0353.jpg
- delete mode 120000 dir/2012/dir2/jmg_0354.jpg
- delete mode 120000 dir/2012/dir2/jmg_0375.jpg
- delete mode 120000 dir/2012/dir2/jmg_0376.jpg
- delete mode 120000 dir/2012/dir2/jmg_0378.jpg
- delete mode 120000 dir/2012/dir2/jmg_8707.cr2
- delete mode 120000 dir/2012/dir2/jmg_8707.jpg
- delete mode 120000 dir/2012/dir2/jmg_8727.cr2
- delete mode 120000 dir/2012/dir2/jmg_8727.jpg
- delete mode 120000 dir/2012/dir2/jmg_8728.cr2
- delete mode 120000 dir/2012/dir2/jmg_8728.jpg
- delete mode 120000 dir/2012/dir2/jmg_8729.cr2
- delete mode 120000 dir/2012/dir2/jmg_8729.jpg
- delete mode 120000 dir/2012/dir2/jmg_8740.cr2
- delete mode 120000 dir/2012/dir2/jmg_8740.jpg
- delete mode 120000 dir/2012/dir2/jmg_8742.cr2
- delete mode 120000 dir/2012/dir2/jmg_8742.jpg
- delete mode 120000 dir/2012/dir2/jmg_8825.cr2
- delete mode 120000 dir/2012/dir2/jmg_8825.jpg
- delete mode 120000 dir/2012/dir2/jmg_8991.cr2
- delete mode 120000 dir/2012/dir2/jmg_8991.jpg
- delete mode 120000 dir/2012/dir2/jmg_8992.cr2
- delete mode 120000 dir/2012/dir2/jmg_8992.jpg
- delete mode 120000 dir/2012/dir2/jmg_8993.cr2
- delete mode 120000 dir/2012/dir2/jmg_8993.jpg
- delete mode 120000 dir/2012/dir2/jmg_9059.cr2
- delete mode 120000 dir/2012/dir2/jmg_9059.jpg
- delete mode 120000 dir/2012/dir2/jmg_9060.cr2
- delete mode 120000 dir/2012/dir2/jmg_9060.jpg
- delete mode 120000 dir/2012/dir2/jmg_9064.cr2
- delete mode 120000 dir/2012/dir2/jmg_9064.jpg
- delete mode 120000 dir/2012/dir2/jmg_9065.cr2
- delete mode 120000 dir/2012/dir2/jmg_9065.jpg
- delete mode 120000 dir/2012/dir2/jmg_9081.cr2
- delete mode 120000 dir/2012/dir2/jmg_9081.jpg
- delete mode 120000 dir/2012/dir2/jmg_9082.cr2
- delete mode 120000 dir/2012/dir2/jmg_9082.jpg
- delete mode 120000 dir/2012/dir2/jmg_9083.cr2
- delete mode 120000 dir/2012/dir2/jmg_9083.jpg
- delete mode 120000 dir/2012/dir1/jmg_0132.cr2
- delete mode 120000 dir/2012/dir1/jmg_0132.jpg
- delete mode 120000 dir/2012/dir1/jmg_0133.cr2
- delete mode 120000 dir/2012/dir1/jmg_0133.jpg
- delete mode 120000 dir/2012/dir1/jmg_0347.jpg
- delete mode 120000 dir/2012/dir1/jmg_0351.jpg
- delete mode 120000 dir/2012/dir1/jmg_0352.jpg
- delete mode 120000 dir/2012/dir1/jmg_0374.jpg
- delete mode 120000 dir/2012/dir1/jmg_8714.cr2
- delete mode 120000 dir/2012/dir1/jmg_8714.jpg
- delete mode 120000 dir/2012/dir1/jmg_8716.cr2
- delete mode 120000 dir/2012/dir1/jmg_8716.jpg
- delete mode 120000 dir/2012/dir1/jmg_8734.cr2
- delete mode 120000 dir/2012/dir1/jmg_8734.jpg
- delete mode 120000 dir/2012/dir1/jmg_8735.cr2
- delete mode 120000 dir/2012/dir1/jmg_8735.jpg
- delete mode 120000 dir/2012/dir1/jmg_8736.cr2
- delete mode 120000 dir/2012/dir1/jmg_8736.jpg
- delete mode 120000 dir/2012/dir1/jmg_8743.cr2
- delete mode 120000 dir/2012/dir1/jmg_8743.jpg
- delete mode 120000 dir/2012/dir1/jmg_8746.cr2
- delete mode 120000 dir/2012/dir1/jmg_8746.jpg
- delete mode 120000 dir/2012/dir1/jmg_8828.cr2
- delete mode 120000 dir/2012/dir1/jmg_8828.jpg
- delete mode 120000 dir/2012/dir1/jmg_8984.cr2
- delete mode 120000 dir/2012/dir1/jmg_8984.jpg
- delete mode 120000 dir/2012/dir1/jmg_8985.cr2
- delete mode 120000 dir/2012/dir1/jmg_8985.jpg
- delete mode 120000 dir/2012/dir1/jmg_8986.cr2
- delete mode 120000 dir/2012/dir1/jmg_8986.jpg
- delete mode 120000 dir/2012/dir1/jmg_8988.cr2
- delete mode 120000 dir/2012/dir1/jmg_8988.jpg
- delete mode 120000 dir/2012/dir1/jmg_9057.cr2
- delete mode 120000 dir/2012/dir1/jmg_9057.jpg
- delete mode 120000 dir/2012/dir1/jmg_9058.cr2
- delete mode 120000 dir/2012/dir1/jmg_9058.jpg
- delete mode 120000 dir/2012/dir1/jmg_9086.cr2
- delete mode 120000 dir/2012/dir1/jmg_9086.jpg
- delete mode 120000 dir/2012/dir1/jmg_9087.cr2
- delete mode 120000 dir/2012/dir1/jmg_9087.jpg
- delete mode 120000 dir/2013/dir2/jmg_0477.cr2
- delete mode 120000 dir/2013/dir2/jmg_0477.jpg
- delete mode 120000 dir/2013/dir2/jmg_0478.cr2
- delete mode 120000 dir/2013/dir2/jmg_0478.jpg
- delete mode 120000 dir/2013/dir2/jmg_0479.cr2
- delete mode 120000 dir/2013/dir2/jmg_0479.jpg
- delete mode 120000 dir/2013/dir2/jmg_0604.cr2
- delete mode 120000 dir/2013/dir2/jmg_0604.jpg
- delete mode 120000 dir/2013/dir2/jmg_0605.cr2
- delete mode 120000 dir/2013/dir2/jmg_0605.jpg
- delete mode 120000 dir/2013/dir2/jmg_0606.cr2
- delete mode 120000 dir/2013/dir2/jmg_0606.jpg
- delete mode 120000 dir/2013/dir2/jmg_0607.cr2
- delete mode 120000 dir/2013/dir2/jmg_0607.jpg
- delete mode 120000 dir/2013/dir2/jmg_0608.cr2
- delete mode 120000 dir/2013/dir2/jmg_0608.jpg
- delete mode 120000 dir/2013/dir2/jmg_0708.cr2
- delete mode 120000 dir/2013/dir2/jmg_0708.jpg
- delete mode 120000 dir/2013/dir2/jmg_0709.cr2
- delete mode 120000 dir/2013/dir2/jmg_0709.jpg
- delete mode 120000 dir/2013/dir2/jmg_0710.cr2
- delete mode 120000 dir/2013/dir2/jmg_0710.jpg
- delete mode 120000 dir/2013/dir1/jmg_0475.cr2
- delete mode 120000 dir/2013/dir1/jmg_0475.jpg
- delete mode 120000 dir/2013/dir1/jmg_0476.cr2
- delete mode 120000 dir/2013/dir1/jmg_0476.jpg
- delete mode 120000 dir/2013/dir1/jmg_0718.cr2
- delete mode 120000 dir/2013/dir1/jmg_0718.jpg
- delete mode 120000 dir/2013/dir1/jmg_0719.cr2
- delete mode 120000 dir/2013/dir1/jmg_0719.jpg
-Already up-to-date.
-[2013-10-27 18:36:44 CET] Committer: Committing changes to git
-[2013-10-27 18:36:44 CET] Pusher: Syncing with repoB 
-Already up-to-date.
-fatal: Unable to create '/media/srv/img/.git/refs/heads/synced/git-annex.lock': File exists.
-
-If no other git process is currently running, this probably means a
-git process crashed in this repository earlier. Make sure no other git
-process is running and remove the file manually to continue.
-fatal: The remote end hung up unexpectedly
-fatal: The remote end hung up unexpectedly
-From repoB:/media/srv/img
-   276f659..5eba12c  synced/git-annex -> repoB/synced/git-annex
-Everything up-to-date
-[2013-10-27 18:36:50 CET] Committer: Committing changes to git
-[2013-10-27 18:36:51 CET] Pusher: Syncing with repoB 
-[2013-10-27 18:36:52 CET] Transferrer: Downloaded only_on_repoB
-[2013-10-27 18:36:53 CET] Transferrer: Downloaded jmg_9077.jpg
-[2013-10-27 18:36:58 CET] Committer: Committing changes to git
-[2013-10-27 18:36:58 CET] Transferrer: Downloaded jmg_8676.cr2
-[2013-10-27 18:36:59 CET] Committer: Committing changes to git
-[2013-10-27 18:37:02 CET] Transferrer: Downloaded jmg_0021.jpg
-[2013-10-27 18:37:02 CET] Committer: Committing changes to git
-[2013-10-27 18:37:04 CET] Transferrer: Downloaded jmg_0025.jpg
-[2013-10-27 18:37:04 CET] Committer: Committing changes to git
-[2013-10-27 18:37:06 CET] Transferrer: Downloaded jmg_0026.jpg
-[2013-10-27 18:37:06 CET] Committer: Committing changes to git
-[2013-10-27 18:37:07 CET] Transferrer: Downloaded jmg_0027.jpg
-[2013-10-27 18:37:07 CET] Committer: Committing changes to git
-[2013-10-27 18:37:10 CET] Transferrer: Downloaded jmg_0034.jpg
-[2013-10-27 18:37:10 CET] Committer: Committing changes to git
-[2013-10-27 18:37:12 CET] Transferrer: Downloaded jmg_0035.jpg
-[2013-10-27 18:37:12 CET] Committer: Committing changes to git
-[2013-10-27 18:37:15 CET] Transferrer: Downloaded jmg_0036.jpg
-[2013-10-27 18:37:15 CET] Committer: Committing changes to git
-[2013-10-27 18:37:17 CET] Transferrer: Downloaded jmg_0130.jpg
-[2013-10-27 18:37:17 CET] Committer: Committing changes to git
-[2013-10-27 18:37:18 CET] Transferrer: Downloaded jmg_0131.jpg
-[2013-10-27 18:37:18 CET] Committer: Committing changes to git
-[2013-10-27 18:37:20 CET] Transferrer: Downloaded jmg_0155.jpg
-[2013-10-27 18:37:20 CET] Committer: Committing changes to git
-[2013-10-27 18:37:23 CET] Transferrer: Downloaded jmg_0156.jpg
-[2013-10-27 18:37:23 CET] Committer: Committing changes to git
-[2013-10-27 18:37:27 CET] Transferrer: Downloaded jmg_0158.cr2
-[2013-10-27 18:37:27 CET] Committer: Committing changes to git
-[2013-10-27 18:37:32 CET] Transferrer: Downloaded jmg_0165.cr2
-[2013-10-27 18:37:32 CET] Committer: Committing changes to git
-[2013-10-27 18:37:37 CET] Transferrer: Downloaded jmg_0166.cr2
-[2013-10-27 18:37:37 CET] Committer: Committing changes to git
-To repoB:/media/srv/img/
-   276f659..5eba12c  git-annex -> synced/git-annex
-To repoB:/media/srv/img/
-   5eba12c..f00ee07  git-annex -> synced/git-annex
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(merging repoB/git-annex into git-annex...)
-
-
-(Recording state in git...)
-
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-# End of transcript or log.
-"""]]
-
-> [[done]], seems this was caused by the bug I alread fixed. --[[Joey]]
diff --git a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_1_ae4a13ff121d27f78904eee9bf5e716b._comment b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_1_ae4a13ff121d27f78904eee9bf5e716b._comment
deleted file mode 100644
index 88b293284..000000000
--- a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_1_ae4a13ff121d27f78904eee9bf5e716b._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 1"
- date="2013-10-28T22:02:30Z"
- content="""
-So this sounds like [[bugs/direct_mode_assistant_in_subdir_confusion]], which was fixed in 4.20131024. Is there a possibility that you started the git-annex assistant (or webapp) from within `incoming/5d` ?
-
-I'm not sure if the bug could also cause the removal of directories to happen in the wrong location.
-
-
-----
-
-It should be possible to revert these changes and get your files back.
-
-1. `git annex indirect`
-2. `git log --stat` (find the commit that deleted files)
-3. `git revert $commit`
-4. `git annex direct`
-"""]]
diff --git a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_2_32e360cd7b100ddb9a526e7833fc55e1._comment b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_2_32e360cd7b100ddb9a526e7833fc55e1._comment
deleted file mode 100644
index 1a7e4e16c..000000000
--- a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_2_32e360cd7b100ddb9a526e7833fc55e1._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnh6wz0pMA3NLPFg2j_I3S5JeinaOVqnng"
- nickname="Felix"
- subject="comment 2"
- date="2013-10-30T22:55:36Z"
- content="""
-It's quite possible that I have started the assistant (on the armhf machine) or the webapp (on the amd64 machine) in one of the subfolders, so yes it looks like that specific bug hit me.
-
-Having looked at the logs, I'm pretty sure that the removal of the original directory was caused by removing the suddenly occuring \"mirror\" folders in a subdirectory.
-***
-Reverting proves to be difficult. I created a full copy of the git-annex repo and switched to indirect mode. There are around 500 commits that need to be reverted and about 6 of them are merges which I haven't been able to revert. I have only reverted the non-merge commits and after going back to direct mode there are now around 200 broken symlinks. I'm now assuming that those 200 are the ones that are lost and I need to restore from a backup. Can I rely on that? It's extremely difficult for me to do a full check.
-***
-How should I proceed to get this repo (after further repairs) again in sync with the second repo and have the second repo adopt the \"repaired\" state?
-
-"""]]
diff --git a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_3_650dc9ede4e16ef668d96840f63dad47._comment b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_3_650dc9ede4e16ef668d96840f63dad47._comment
deleted file mode 100644
index 4e7d6491c..000000000
--- a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_3_650dc9ede4e16ef668d96840f63dad47._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 3"
- date="2013-11-02T20:03:33Z"
- content="""
-I don't understand why there are so many commits that need to be reverted. I'd have thought that it would have only made one bad commit due to the bug, and reverting that would do. Or even just adding back any symlinks removed by any of the bad commits, without an explicit revert would accomplish the same.
-
-You should be able to check with `git annex whereis --not --in .` what git-annex thinks about the 200 broken symlinks. Clearly their content is not in the local repisitory; it may be present elsewhere, or you might have to restore those files from backup.
-
-Once you have the git tree of the repository back in good shape, assuming you did it by committing changes, and possibly committing git reverts, you should be able to just use normal git annex syncing to sync those changes to the second repo. Ie, `git annex sync` in both, or running the assistant.
-"""]]
diff --git a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_4_721cf184fb5a5244ec5c15de3302ebf7._comment b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_4_721cf184fb5a5244ec5c15de3302ebf7._comment
deleted file mode 100644
index 3876444cd..000000000
--- a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_4_721cf184fb5a5244ec5c15de3302ebf7._comment
+++ /dev/null
@@ -1,33 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnh6wz0pMA3NLPFg2j_I3S5JeinaOVqnng"
- nickname="Felix"
- subject="Number of commits"
- date="2013-11-21T20:26:46Z"
- content="""
-I have no idea where this large number of commits come from, but maybe the sheer number of files explains it:
-
-Files appearing in the wrong place (probably due to me starting the assistant in a subdirectory of the repo):
-
-    $ git log --stat | grep \"5d/20.*+$\" |wc -l
-    1148
-
-Me wondering where they come from and deleting them manually step by step when I found them:
-
-    $ git log --stat | grep \"5d/20.*-$\" |wc -l
-    1095
-
-git-annex removing the original files that have been mirrored in the wrong place (and maybe a few more as I was working on stuff there as well):
-
-    $ git log --stat | grep \"^ 20.*-$\" | wc -l
-    1152
-
-Maybe this explains the large number (approx. 500) of commits?
-
----
-
-The missing 200 files have not been in a different repo, so apart from 3 that were not available they have been restored from the backup.
-
----
-
-As my setup needs some changes anyway I'm going to start from scratch. 
-"""]]
diff --git a/doc/bugs/Error___39__get__39__ting_files_from_rsync_remote__44___versions_3.20120315_and_3.20120430.mdwn b/doc/bugs/Error___39__get__39__ting_files_from_rsync_remote__44___versions_3.20120315_and_3.20120430.mdwn
deleted file mode 100644
index 85e243382..000000000
--- a/doc/bugs/Error___39__get__39__ting_files_from_rsync_remote__44___versions_3.20120315_and_3.20120430.mdwn
+++ /dev/null
@@ -1,79 +0,0 @@
-What steps will reproduce the problem?
-
-	$ git annex initremote rsyncremote type=rsync rsyncurl=myuser@rsync.hidrive.strato.com:/users/myuser/git-annex/Music/ encryption=0xC597DECC177AFD7C
-	$ git annex get --from rsyncremote "file"
-
-What is the expected output? What do you see instead?
-
-I expect that the requested file is copied as for every other remote, but instead I get this error:
-
-----------------------------------------
-	get <file> (from rsyncremote...) (gpg) 
-	rsync: change_dir "/users/myuser/git-annex/Music/0e5/a5b/'GPGHMACSHA1--3afd32ab8e70ac329262adeb770c330b0845b1e0" failed: No such file or directory (2)
-
-	sent 8 bytes  received 10 bytes  7.20 bytes/sec
-	total size is 0  speedup is 0.00
-	rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [Receiver=3.0.9]
-
-	  rsync failed -- run git annex again to resume file transfer
-
-	rsync: change_dir "/users/myuser/git-annex/Music/8k/QZ/'GPGHMACSHA1--3afd32ab8e70ac329262adeb770c330b0845b1e0" failed: No such file or directory (2)
-
-	sent 8 bytes  received 10 bytes  36.00 bytes/sec
-	total size is 0  speedup is 0.00
-	rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [Receiver=3.0.9]
-
-	  rsync failed -- run git annex again to resume file transfer
-failed
-	git-annex: get: 1 failed
-----------------------------------------
-
-I can verify that the directory /users/myuser/git-annex/Music/0e5/a5b/GPGHMACSHA1--3afd32ab8e70ac329262adeb770c330b0845b1e0 exists in the rsync remote, without the ' character.
-
-What version of git-annex are you using? On what operating system?
-
-I tried versions 3.20120315 and 3.20120430 on Gentoo linux.
-
-	$ uname -a
-	Linux odin 3.3.1-gentoo-odin #1 SMP Sat Apr 7 21:18:11 CEST 2012 x86_64 Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz GenuineIntel GNU/Linux
-
-	$ ghc --version
-	The Glorious Glasgow Haskell Compilation System, version 7.4.1
-
-Please provide any additional information below.
-
-The rsync remote config in .git/config:
-
-	[remote "rsyncremote"]
-		annex-rsyncurl = myuser@rsync.hidrive.strato.com:/users/myuser/git-annex/Music/
-		annex-uuid = "UUID"
-
-> Here's what the --debug flag shows is being run: --[[Joey]] 
-
-	Running: rsync ["--progress","--inplace","joey@localhost:/tmp/Music/d98/a3c/'GPGHMACSHA1--878c3a3f59965bd87b4738ab29562efd215b954c/GPGHMACSHA1--878c3a3f59965bd87b4738ab29562efd215b954c'","/home/joey/tmp/x/.git/annex/tmp/GPGHMACSHA1--878c3a3f59965bd87b4738ab29562efd215b954c"] 
-
-> But, this works for me, here, despite containing the quoting!
-> That's because here it's using rsync over ssh, which actually requires
-> that quoting. Are you using rsync
-> over the rsync protocol? If so, the workaround is to explicitly make
-> the rsyncurl start with `rsync://`
-> 
-> And if this is the case, I need
-> to adjust the code in git-annex that determines if it's using ssh or
-> the rsync protocol. It assumes that (and this is what the rsync man 
-> says AFAICS) that the rsync protocol is only used if the url starts
-> with `rsync://` or contains `::`.
-> 
->> Nope, it is indeed using rsync over ssh as git-annex thought.
-> 
-> Hmm, I see that `hidrive.strato.com` is some kind of rsync provider?
-> Perhaps they do something with rsync over ssh that
-> avoids the need for shell quoting. For example, they might pass incoming
-> ssh connections directly into rsync, bypassing the shell
-> -- which avoids the need for this quoting. Any details you can provide
-> about them would probably be useful then. Ie, do they really use rsync
-> over ssh, is it really a `rsync.net` type rsync provider? 
->  --[[Joey]]
-> 
->> This was the case, and the shellescape=no config option has been added
->> to rsync special remotes to deal with it. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__.mdwn b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__.mdwn
deleted file mode 100644
index a44ecc82e..000000000
--- a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-When I try to add a box.com cloud repository with the encryption option selected, I get an error that says "internal server error". 
-
-### What steps will reproduce the problem?
-Anytime I try to set up a cloud repository with box.com (and presumably others, since this seems to be a problem with gpg (see log)) that is encrypted, I get this error.
-
-
-### What version of git-annex are you using? On what operating system?
-The operating system is Mac OS X 10.8.4, and the version of git-annex is 4.20130801-gc88bbc4.
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-(encryption setup) gpg: /Users/adamliter/.gnupg/gpg.conf:233: invalid auto-key-locate list
-30/Aug/2013:02:27:11 -0400 [Error#yesod-core] user error (gpg ["--quiet","--trust-model","always","--gen-random","--armor","1","512"] exited 2) @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5)
-
-# End of transcript or log.
-"""]]
-
-[[!meta title="OSX bundled gpg does not work with gpg.conf created by MacGPG"]]
-
-> [[done]]; I have updated the gpg to version 1.4.14 which
-> manages to build with the missing features.
-> --[[Joey]]
diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_1_9be1b577fa4d5fe9754845073fdf5d32._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_1_9be1b577fa4d5fe9754845073fdf5d32._comment
deleted file mode 100644
index ec0234c2d..000000000
--- a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_1_9be1b577fa4d5fe9754845073fdf5d32._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.209"
- subject="comment 1"
- date="2013-08-30T11:39:51Z"
- content="""
-gpg complains about an invalid parameter for the `auto-key-locate` option, which is not passed by git-annex but found in your gpg.conf.
-
-What is on line 233 of `/Users/adamliter/.gnupg/gpg.conf`?
-"""]]
diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_2_0da0d68b646f2b38be6ecf7c0fe13743._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_2_0da0d68b646f2b38be6ecf7c0fe13743._comment
deleted file mode 100644
index c8a1db228..000000000
--- a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_2_0da0d68b646f2b38be6ecf7c0fe13743._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkgH7oNEqNbh3g-N1-UHXuqleXaRYDgj1U"
- nickname="Adam"
- subject="comment 2"
- date="2013-08-30T15:39:16Z"
- content="""
-\"auto-key-locate cert pka ldap hkp://keys.gnupg.net\" is on line 233
-"""]]
diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_3_09c56f5574931f2ebe903069f0731160._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_3_09c56f5574931f2ebe903069f0731160._comment
deleted file mode 100644
index 3cfa9a829..000000000
--- a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_3_09c56f5574931f2ebe903069f0731160._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.209"
- subject="comment 3"
- date="2013-08-30T16:09:58Z"
- content="""
-Hmm, it looks like a perfectly valid list. Interesting.
-But regardless, gpg doesn't seem to like that line; what gpg version
-are you using? Also, does it work directly on the command-line
-(`gpg -a --gen-random 1 1`)?
-
-Have you tried to setup the remote without that line in the gpg.conf? Of
-course it wouldn't solve the core of the issue, but it's irrelevant for
-random data generation anyway (the same goes for `--trust-model`);
-perhaps this very command should be run with `--no-options`.
-"""]]
diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_4_0c127396e682ca6ced43aec7deeb0335._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_4_0c127396e682ca6ced43aec7deeb0335._comment
deleted file mode 100644
index 6d2bb451a..000000000
--- a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_4_0c127396e682ca6ced43aec7deeb0335._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkgH7oNEqNbh3g-N1-UHXuqleXaRYDgj1U"
- nickname="Adam"
- subject="comment 4"
- date="2013-08-30T21:39:26Z"
- content="""
-`gpg -a --gen-random 1 1` on the command line seems to work. At least, when I just ran it it returned `Xg==`. I'm not super familiar with running gpg on the command line, so I'm not sure if that is the desired result when running that.
-
-The version of gpg is GnuPG/MacGPG2 version 2.0.20. 
-
-I just tried deleting that line from the config file, and now it worked. Would I be able to replace the line after setting up the repository, or is that going to create problems? I'm not entirely sure what that line does, and I'm a little wary about messing with it in case it breaks the functionality of any of the other things that I use gpg for, like email encryption.
-"""]]
diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_5_6bc3eadefde4750eec67a55de6651b2d._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_5_6bc3eadefde4750eec67a55de6651b2d._comment
deleted file mode 100644
index 998d67055..000000000
--- a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_5_6bc3eadefde4750eec67a55de6651b2d._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.209"
- subject="comment 5"
- date="2013-08-30T22:51:56Z"
- content="""
-OK (you just generated 1 byte of base64-encoded random data).
-No, I'm afraid git-annex will croak for each operation using gpg on your remote (which includes get, push, fsck, ...).
-
-This lines specifies how gpg automatically retrieves public keys when you get a signed message for instance. If you don't want to mix configurations, it is easy to create a git-annex-specific GnuPG home directory, but it requires you to point the `GNUPGHOME` to this alternative directory before starting git-annex.
-
-That said, other MacOSX users have encountered the same problem, and it was [[reported_to_be_solved_recently|/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/]].
-"""]]
diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_6_263ab9c1483438b1717c8061ac81a2fa._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_6_263ab9c1483438b1717c8061ac81a2fa._comment
deleted file mode 100644
index 65e6275da..000000000
--- a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_6_263ab9c1483438b1717c8061ac81a2fa._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.140"
- subject="comment 6"
- date="2013-09-05T16:30:52Z"
- content="""
-I have verified the gpg build I am currently using on OSX fails with that line. MacGPG doesn't but I had problems including it in the build before.
-If you remove the \"cert\" and the \"pkg\" from the line it will work. It seems I need to update the gpg build to support these DNS based key finding methods.
-"""]]
diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_7_eccc10990dff37584f8e60cd481a7140._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_7_eccc10990dff37584f8e60cd481a7140._comment
deleted file mode 100644
index 35d9c71e8..000000000
--- a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_7_eccc10990dff37584f8e60cd481a7140._comment
+++ /dev/null
@@ -1,26 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.140"
- subject="comment 7"
- date="2013-09-05T16:54:36Z"
- content="""
-./configure says:
-
-<pre>
-checking whether the resolver is usable... no
-checking whether I can make the resolver usable with BIND_8_COMPAT... no
-
-configure:7918: gcc -o conftest -g -O2   conftest.c  >&5
-Undefined symbols for architecture x86_64:
-  \"_res_9_dn_expand\", referenced from:
-      _main in ccsJFrZc.o
-  \"_res_9_dn_skipname\", referenced from:
-      _main in ccsJFrZc.o
-  \"_res_9_query\", referenced from:
-      _main in ccsJFrZc.o
-ld: symbol(s) not found for architecture x86_64
-collect2: ld returned 1 exit status
-</pre>
-
-So no DNS stuff until I can find a way to build a gpg for OSX that supports it.
-"""]]
diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_8_f897d20cbe5e0f3f58ce1a0bacad3d71._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_8_f897d20cbe5e0f3f58ce1a0bacad3d71._comment
deleted file mode 100644
index 741c5342f..000000000
--- a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_8_f897d20cbe5e0f3f58ce1a0bacad3d71._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkgH7oNEqNbh3g-N1-UHXuqleXaRYDgj1U"
- nickname="Adam"
- subject="comment 8"
- date="2013-09-05T17:30:07Z"
- content="""
-Hmm, thanks for looking into it. I appreciate it.
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__.mdwn b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__.mdwn
deleted file mode 100644
index d0b2c1538..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-Running 3.20121112 on Debian Squeeze.
-
-Since adding a certain directory of files (just a bunch of PDFs) yesterday I am getting errors when I try to use `git annex drop .` when the files aren't present, rather doing nothing or saying 'ok', as it used to do/should do.  The errors are of the form `git-annex: fd:10: hGetLine: end of file` and sometimes of the form `git-annex: fd:17: hFlush: resource vanished (Broken pipe)`.  In my `daemon.log`, I have the errors
-
-    (scanning...) Already up-to-date.
-    Already up-to-date.
-    TransferScanner crashed: fd:26: hGetLine: end of file
-    Already up-to-date.
-    (started...) git-annex: fd:25: hGetLine: end of file
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    git-annex: fd:24: hFlush: resource vanished (Broken pipe)
-    [many more repetitions]
-
-If I `git annex get` the files and then drop them again, a further attempt at a drop gives all these errors again.
-
-> So in summary, a git-annex built against the old version of git in
-> debian stable fails to work with a newer version of git, and rebuilding
-> fixes it. FWIW, the git-annex backport to stable does not have this
-> problem, because it checks git version at runtime. But I want to avoid
-> the overhead of that check in git-annex mainline, because this old git
-> version is well, very old and increasingly unlikely to be used. So,
-> I don't think any changes to git-annex are warrented. [[done]] --[[Joey]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_10_8742f7ac27b5f4ad6261d04a174a691c._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_10_8742f7ac27b5f4ad6261d04a174a691c._comment
deleted file mode 100644
index 921a20024..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_10_8742f7ac27b5f4ad6261d04a174a691c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.14.162"
- subject="comment 10"
- date="2012-12-06T22:00:45Z"
- content="""
-Can you show me a transcript of git-check-attr? This is sounding like a git bug.
-
-(The build error is due to too old a version of yesod.)
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_11_b8e720340000537de6713c49b7733b2f._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_11_b8e720340000537de6713c49b7733b2f._comment
deleted file mode 100644
index db964e58c..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_11_b8e720340000537de6713c49b7733b2f._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="spwhitton"
- ip="163.1.167.50"
- subject="comment 11"
- date="2012-12-06T22:17:37Z"
- content="""
-Upgrading yesod then git-annex removes the problem I was seeing.  Thanks for your help with that.  Here is a `git-check-attr` session:
-
-    backups $ git check-attr --stdin annex.backend annex.numcopies --
-    athena-etc.tar.gz
-    athena-etc.tar.gz: annex.backend: unspecified
-    athena-etc.tar.gz: annex.numcopies: 2
-    athena-mail.gz
-    athena-mail.gz: annex.backend: unspecified
-    athena-mail.gz: annex.numcopies: 2
-    athena-web.tar.gz
-    athena-web.tar.gz: annex.backend: unspecified
-    athena-web.tar.gz: annex.numcopies: 2
-    [^D pressed]
-    backups $ 
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_1_489fa3a717519cd5d8b4c1a9d143d8c6._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_1_489fa3a717519cd5d8b4c1a9d143d8c6._comment
deleted file mode 100644
index 902464317..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_1_489fa3a717519cd5d8b4c1a9d143d8c6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.253.113"
- subject="comment 1"
- date="2012-12-06T15:04:12Z"
- content="""
-Can you run it with --debug ?
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_2_b0796d3b1913e1b6f7b34d75a591be42._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_2_b0796d3b1913e1b6f7b34d75a591be42._comment
deleted file mode 100644
index 696bdb5aa..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_2_b0796d3b1913e1b6f7b34d75a591be42._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="spwhitton"
- ip="163.1.167.50"
- subject="comment 2"
- date="2012-12-06T15:13:02Z"
- content="""
-Sure, I've added --debug to the assistant autostart file and am running `git annex --debug drop`.  For the first type of error given above I get output like
-
-    [2012-12-06 15:08:50 GMT] read: git [\"--git-dir=/home/swhitton/var/.git\",\"--work-tree=/home/swhitton/var\",\"ls-files\",\"--cached\",\"-z\",\"--\",\".\"]
-    [2012-12-06 15:08:50 GMT] chat: git [\"--git-dir=/home/swhitton/var/.git\",\"--work-tree=/home/swhitton/var\",\"check-attr\",\"-z\",\"--stdin\",\"annex.backend\",\"annex.numcopies\",\"--\"]
-    
-    git-annex: fd:10: hGetLine: end of file
-    failed
-
-and for the \"resource vanished\" errors I get no further output.  There is also nothing further in `daemon.log`.
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_3_d8ca17ccaa5ee48d590736af8e77d88a._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_3_d8ca17ccaa5ee48d590736af8e77d88a._comment
deleted file mode 100644
index c59d60047..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_3_d8ca17ccaa5ee48d590736af8e77d88a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.253.113"
- subject="comment 3"
- date="2012-12-06T15:21:25Z"
- content="""
-If you run `git annex find` instead of `git annex drop`, does it have any errors?
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_4_aa7a690aaf75d21f52051a31d7fce70e._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_4_aa7a690aaf75d21f52051a31d7fce70e._comment
deleted file mode 100644
index a1baa47cd..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_4_aa7a690aaf75d21f52051a31d7fce70e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="spwhitton"
- ip="163.1.167.50"
- subject="comment 4"
- date="2012-12-06T15:23:02Z"
- content="""
-No, `git annex find --debug .` outputs just `[2012-12-06 15:22:14 GMT] read: git [\"--git-dir=/home/swhitton/var/.git\",\"--work-tree=/home/swhitton/var\",\"ls-files\",\"--cached\",\"-z\",\"--\",\".\"]`.
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_5_dc235dc2d024b7f340721bb578630e00._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_5_dc235dc2d024b7f340721bb578630e00._comment
deleted file mode 100644
index af7750771..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_5_dc235dc2d024b7f340721bb578630e00._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.253.113"
- subject="comment 5"
- date="2012-12-06T15:26:27Z"
- content="""
-What version of git do you have installed?
-
-How did you install this version of git-annex on squeeze?
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_6_5d1e6ea5b5725c773acc6e288add812c._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_6_5d1e6ea5b5725c773acc6e288add812c._comment
deleted file mode 100644
index e208b3169..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_6_5d1e6ea5b5725c773acc6e288add812c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="spwhitton"
- ip="163.1.167.50"
- subject="comment 6"
- date="2012-12-06T15:29:46Z"
- content="""
-git is at 1.7.10.4 which I got from backports.  I only upgraded a couple of days ago (to solve a strange error I was having with cloning to a removable drive); sorry for not mentioning that.  I installed git-annex using cabal run as root.
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_7_6389b4f03ebc916358bc6674398d70c4._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_7_6389b4f03ebc916358bc6674398d70c4._comment
deleted file mode 100644
index 9d61f4ac0..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_7_6389b4f03ebc916358bc6674398d70c4._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.253.113"
- subject="comment 7"
- date="2012-12-06T15:39:26Z"
- content="""
-The problem seems to involve git check-attr exiting unexpectedly. Does this happen only in a specific directory of files, or can you reproduce it elsewhere?
-
-You may be able to reproduce it exiting by running:
-
-`git check-attr --stdin annex.backend annex.numcopies --`
-
-And then entering filenames, pressing enter, and it should answer back with two attribute values and keep running.
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_8_bcacc9fb3751042968118ebe33802e27._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_8_bcacc9fb3751042968118ebe33802e27._comment
deleted file mode 100644
index 8e4e5cf91..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_8_bcacc9fb3751042968118ebe33802e27._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.253.113"
- subject="comment 8"
- date="2012-12-06T15:41:31Z"
- content="""
-Have you rebuilt git-annex since you upgraded git? 
-
-This seems most likely to be the problem; the version of git in squeeze requires git-annex behave differently when using git check-attr, and if you have a version of git-annex built for it, it will do things the new git dislikes.
-"""]]
diff --git a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_9_6d4c9f0e133ebd94fc11346df446402e._comment b/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_9_6d4c9f0e133ebd94fc11346df446402e._comment
deleted file mode 100644
index a48e98ebc..000000000
--- a/doc/bugs/Error_when_dropping___34__hGetLine:_end_of_file__34__/comment_9_6d4c9f0e133ebd94fc11346df446402e._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="spwhitton"
- ip="163.1.167.50"
- subject="comment 9"
- date="2012-12-06T21:37:52Z"
- content="""
-Yes, running git-attr like that does indeed produce the problem.  I attempted to rebuild git-annex using cabal, but the build failed with the following error:
-
-    [273 of 290] Compiling Assistant.WebApp.Configurators.Local ( Assistant/WebApp/Configurators/Local.hs, dist/build/git-annex/git-annex-tmp/Assistant/WebApp/Configurators/Local.o )
-    
-    Assistant/WebApp/Configurators/Local.hs:55:11:
-        `fieldEnctype' is not a (visible) field of constructor `Field'
-    cabal: Error: some packages failed to install:
-    git-annex-3.20121127.1 failed during the building phase. The exception was:
-    ExitFailure 1
-"""]]
diff --git a/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location.mdwn b/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location.mdwn
deleted file mode 100644
index 34d05c0b1..000000000
--- a/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-I just noticed that if you move a git-annex symlink to a location ignored by git, it simply works.  Upon committing that change, however, part of git-annex's `fix` function apparently tries to `git-add` the symlink.  This fails because the new, ignored location requires a `git-add --force`.
-
-Considering that git proper doesn't fail or warn, I think git-annex shouldn't either.
-
-This is the error message:
-
-	$ git mv annexed-file ignored-dir/
-	$ git commit
-	fix ignored-dir/annexed-file ok
-	(Recording state in git...)
-	The following paths are ignored by one of your .gitignore files:
-	ignored-dir
-	Use -f if you really want to add them.
-	fatal: no files added
-	Command xargs ["-0","git","--git-dir=/home/[...]/repo/.git","--work-tree=/home/[...]/repo","add","--"] failed; exit code 123
-
-	git-annex: user error (Command xargs ["-0","git","--git-dir=/home/[...]/repo/.git","--work-tree=/home/[...]/repo","add","--"] failed; exit code 123)
-	failed
-	git-annex: 1 failed
-
-> Weird edge case.. ok, fixed. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_1_b524e70156e8bc1219d5c6741974ad99._comment b/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_1_b524e70156e8bc1219d5c6741974ad99._comment
deleted file mode 100644
index 6b741e85e..000000000
--- a/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_1_b524e70156e8bc1219d5c6741974ad99._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlq4ClC5EMN1Vq1DpWXAqP5TiDnCK1mSfk"
- nickname="Jonas"
- subject="Happens with import, too"
- date="2013-11-24T23:24:09Z"
- content="""
-This happens to me when using git annex import, too (on version 4.20131106)
-
-    (Recording state in git...)
-    The following paths are ignored by one of your .gitignore files:
-    path/to/some/directory/.svn
-    Use -f if you really want to add them.
-    fatal: no files added
-
-    git-annex: user error (xargs [\"-0\",\"git\",\"--git-dir=/path/to/annex/.git\",\"--work-tree=/path/to/annex\",\"add\",\"--\"] exited 123)
-failed
-
-"""]]
diff --git a/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_2_ff7349c396d1249204d621e71f6a7a52._comment b/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_2_ff7349c396d1249204d621e71f6a7a52._comment
deleted file mode 100644
index 2ee7f79b6..000000000
--- a/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_2_ff7349c396d1249204d621e71f6a7a52._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 2"
- date="2013-11-26T20:04:23Z"
- content="""
-This bug was fixed, and closed 2 years ago. Posting a comment about another, related problem is not very useful. 
-
-Yes, git annex import does not finish importing files if you've configured .gititnore to not allow those files to be added. If you need to do that, you could use `git annex import --force`, which will add the files despite the gitignore. 
-"""]]
diff --git a/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_4_4bc7d4c51faea3fdafc977cb66b7f73a._comment b/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_4_4bc7d4c51faea3fdafc977cb66b7f73a._comment
deleted file mode 100644
index a3a6fc10a..000000000
--- a/doc/bugs/Error_when_moving_annexed_file_to_a_.gitignored_location/comment_4_4bc7d4c51faea3fdafc977cb66b7f73a._comment
+++ /dev/null
@@ -1,26 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlq4ClC5EMN1Vq1DpWXAqP5TiDnCK1mSfk"
- nickname="Jonas"
- subject="comment 4"
- date="2013-11-27T17:36:39Z"
- content="""
-Sorry, my bug triaging skills are limited. This one happened to have exactly the same error message...
-
-This might again be the wrong thread, but... how does git annex decide which files to ignore? In particular, it seems not always to agree with git:
-
-    $ cd /tmp
-    $ mkdir annex
-    $ cd annex
-    $ git init
-    $ git annex init \"Testing annex in /tmp\"
-    $ echo \"This file is hidden\" > .hidden_file
-    $ git status
-    shows .hidden_file as \"untracked\"
-    $ git annex add .
-    does nothing
-    $ git annex add --force .
-    does nothing, either
-    $ git add .
-    adds the file as expected
-
-"""]]
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
deleted file mode 100644
index 21293af54..000000000
--- a/doc/bugs/Error_while_adding_a_file___34__createSymbolicLink:_already_exists__34__.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-I'm importing a directory where some files are hard links of each other.
-
-This is confusing git-annex. Here's a small test of that:
-
-<pre>
-paulproteus@pathi:/tmp$ mkdir annex-test
-paulproteus@pathi:/tmp$ cd annex-test
-paulproteus@pathi:/tmp/annex-test$ git init
-Initialized empty Git repository in /tmp/annex-test/.git/
-paulproteus@pathi:/tmp/annex-test$ git annex init testing
-init testing ok
-paulproteus@pathi:/tmp/annex-test$ echo '* annex.backend=SHA1' >> .gitattributes 
-paulproteus@pathi:/tmp/annex-test$ git commit .gitattributes -m 'Default to sha1'
-[master dd54b41] Default to sha1
- 1 files changed, 1 insertions(+), 0 deletions(-)
-paulproteus@pathi:/tmp/annex-test$ echo "Look at me" > file1
-paulproteus@pathi:/tmp/annex-test$ cp -l file1 file2
-paulproteus@pathi:/tmp/annex-test$ git annex add file1
-add file1 (checksum...) ok
-(Recording state in git...)
-paulproteus@pathi:/tmp/annex-test$ git commit -m 'So far, so good'
-[master eb43084] So far, so good
- 2 files changed, 2 insertions(+), 0 deletions(-)
- create mode 100644 .git-annex/9a3/f1f/SHA1-s11--b9c599d64212934582d676c722cf3ec61f60e09c.log
- create mode 120000 file1
-paulproteus@pathi:/tmp/annex-test$ git annex add file2
-add file2 (checksum...) 
-  git-annex: .git/annex/objects/PM/7p/SHA1-s11--b9c599d64212934582d676c722cf3ec61f60e09c/SHA1-s11--b9c599d64212934582d676c722cf3ec61f60e09c: createSymbolicLink: already exists (File exists)
-git-annex: 1 failed
-paulproteus@pathi:/tmp/annex-test$ 
-</pre>
-
-When trying to make a small test case for this bug, I noticed that if file1 and file2 have the same contents but are not hard links of each other, they both get annexed just fine.
-
-I think the right behavior here is to annex file2 just fine, as if they weren't hard links before.
-
-
--- 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... 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
-> in this situation. [[done]] --[[Joey]]
diff --git a/doc/bugs/Every_new_file_gets_symlinked_to_a_git_object.mdwn b/doc/bugs/Every_new_file_gets_symlinked_to_a_git_object.mdwn
deleted file mode 100644
index 9788c8767..000000000
--- a/doc/bugs/Every_new_file_gets_symlinked_to_a_git_object.mdwn
+++ /dev/null
@@ -1,78 +0,0 @@
-### Please describe the problem.
-Every file I add to a watched repository (by git-annex assistant) becomes symlinked, and sub-subsequently write protected.
-
-Sorry if I'm missing something obvious.
-
-### What steps will reproduce the problem?
-1) Fresh install
-2) create directory, init repo and git-annex
-3) git annex assistant
-4) add a file
-5) ls -lsa to see the symlinked file
-6) trying to write to the file throws a write-protected error
-
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20130725-g8140f7c  
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP  
-local repository version: 3  
-default repository version: 3  
-supported repository versions: 3 4  
-upgrade supported from repository versions: 0 1 2
-
-Using the generic linux distribution with ./runshell on Ubuntu 13.04 (I saw this same behaviour from the ubuntu package, i.e. apt-get install git-annex)
-
-
-### Please provide any additional information below.
-
-Here is the output from my ls -lsa
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
- 4 drwxrwxr-x  3 jetaggart jetaggart  4096 Jul 27 20:38 .
-16 drwx------ 60 jetaggart jetaggart 16384 Jul 27 20:44 ..
- 4 drwxrwxr-x  7 jetaggart jetaggart  4096 Jul 27 20:38 .git
- 4 lrwxrwxrwx  1 jetaggart jetaggart   188 Jul 27 20:38 another.org -> .git/annex/objects/Qm/j7/SHA256E-s11--9484d4be897ca66ad4c9bbf299d12adfe37e089bbca1daecbbb49c375a9cf1e9.org/SHA256E-s11--9484d4be897ca66ad4c9bbf299d12adfe37e089bbca1daecbbb49c375a9cf1e9.org
- 4 lrwxrwxrwx  1 jetaggart jetaggart   186 Jul 27 20:33 blah.org -> .git/annex/objects/kj/q5/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.org/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.org
-12 -rw-rw-r--  1 jetaggart jetaggart   119 Jul 27 20:37 todo.org
-
-
-# End of transcript or log.
-"""]]
-
-Here is the daemon.log
-
-[[!format sh """
-
-[2013-07-27 20:32:55 BST] main: starting assistant version 4.20130725-g8140f7c
-(scanning...) [2013-07-27 20:32:55 BST] Watcher: Performing startup scan
-(started...) 
-[2013-07-27 20:33:52 BST] Committer: Adding blah.org
-add blah.org (checksum...) ok
-[2013-07-27 20:33:52 BST] Committer: Committing changes to git
-(Recording state in git...)
-(Recording state in git...)
-[2013-07-27 20:35:59 BST] Committer: Committing changes to git
-(Recording state in git...)
-[2013-07-27 20:36:01 BST] Committer: Committing changes to git
-(Recording state in git...)
-[2013-07-27 20:37:52 BST] Committer: Committing changes to git
-(Recording state in git...)
-[2013-07-27 20:37:55 BST] Committer: Committing changes to git
-(Recording state in git...)
-[2013-07-27 20:38:44 BST] Committer: Committing changes to git
-(Recording state in git...)
-[2013-07-27 20:38:46 BST] Committer: Adding another.org
-add another.org (checksum...) ok
-[2013-07-27 20:38:46 BST] Committer: Committing changes to git
-(Recording state in git...)
-(Recording state in git...)
-[2013-07-27 20:38:51 BST] Committer: Committing changes to git
-(Recording state in git...)
-[2013-07-27 20:38:56 BST] Committer: Committing changes to git
-(Recording state in git...)
-
-# End of transcript or log.
-"""]]
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Every_new_file_gets_symlinked_to_a_git_object/comment_1_d4e7ed56b16494a95e6c904c746cc91f._comment b/doc/bugs/Every_new_file_gets_symlinked_to_a_git_object/comment_1_d4e7ed56b16494a95e6c904c746cc91f._comment
deleted file mode 100644
index e9dfda6fc..000000000
--- a/doc/bugs/Every_new_file_gets_symlinked_to_a_git_object/comment_1_d4e7ed56b16494a95e6c904c746cc91f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.110"
- subject="comment 1"
- date="2013-07-27T19:55:38Z"
- content="""
-This is how git-annex is intended to work in indirect mode. You must have created your repository by hand, and not enabled [[direct_mode]]. Stop the assistant and run `git annex direct`
-"""]]
diff --git a/doc/bugs/Every_new_file_gets_symlinked_to_a_git_object/comment_2_656b2a2cc44e9102c86bdd57045549d5._comment b/doc/bugs/Every_new_file_gets_symlinked_to_a_git_object/comment_2_656b2a2cc44e9102c86bdd57045549d5._comment
deleted file mode 100644
index 81323b16f..000000000
--- a/doc/bugs/Every_new_file_gets_symlinked_to_a_git_object/comment_2_656b2a2cc44e9102c86bdd57045549d5._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhGq_ii5HaDkp9nx2m9qIMe-xxI4HV5wo"
- nickname="Jeff"
- subject="comment 2"
- date="2013-07-27T20:05:57Z"
- content="""
-I did create it by hand, thanks for the quick feedback, sorry to waste your time.
-
-I'll stick to the forum unless I'm sure it's a bug :)
-"""]]
diff --git a/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__.mdwn b/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__.mdwn
deleted file mode 100644
index 634f3e501..000000000
--- a/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-
-I get this error message:
-
- Failed to make repository
-
-Something went wrong setting up the repository on the remote server.
-
-Transcript:
-
-/opt/git-annex.linux/runshell: line 73: /home/annex/sh -c 'mkdir -p '"'"'annex'"'"'&&cd '"'"'annex'"'"'&&if [ ! -d .git ]; then git init --bare --shared; fi&&git annex init&&mkdir -p ~/.ssh&&if [ ! -e ~/.ssh/git-annex-shell ]; then (echo '"'"'#!/bin/sh'"'"';echo '"'"'set -e'"'"';echo '"'"'if [ "x$SSH_ORIGINAL_COMMAND" != "x" ]; then'"'"';echo '"'"'exec git-annex-shell -c "$SSH_ORIGINAL_COMMAND"'"'"';echo '"'"'else'"'"';echo '"'"'exec git-annex-shell -c "$@"'"'"';echo '"'"'fi'"'"') > ~/.ssh/git-annex-shell; fi&&chmod 700 ~/.ssh/git-annex-shell&&touch ~/.ssh/authorized_keys&&chmod 600 ~/.ssh/authorized_keys&&echo '"'"'command="GIT_ANNEX_SHELL_DIRECTORY='"'"'"'"'"'"'"'"'annex'"'"'"'"'"'"'"'"' ~/.ssh/git-annex-shell",no-agent-forwarding,no-port-forwarding,no-X11-forwarding ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1RQLCJP/gY62xxTOHa4PlZSlSWD2kWBC2+o27SBpBaCVibFfxNKP+1CAgzbyzVygpE0XUXxDOA8dnrq7vPHkkdIlYUZ8JQxTO/zaVVRlzryhWb8QOjEE3ZG0CF+ZQVu14q/M/T4qZm1mtXBCIZMs1wpwTr9dRdf7e/5q5hHROd5sRj+v0PhdiyZ8e6egoq1gFAvspUF1VC74PvZwZ2NKd1s0iGOGGYvoD/nWGCeBUQzMcGk56243zI54tOcDePdZJnd7iIn8FHGprr9yGhc3KYKppWmG7vQU+DhO607FiVnW5aMWjz/msmQidCceIFvnmLFWSDQ5ZNdGVUvHlT9kQQ== p264360@pales
-'"'"' >>~/.ssh/authorized_keys': No such file or directory
-
-### What steps will reproduce the problem?
-
-I made a user annex on my server and set its shell to /opt/git-annex.linux/runshell, then used the webapp on my desktop PC to try and add a remote git repository on my server.
-
-### What version of git-annex are you using? On what operating system?
-
-The latest tarball: git-annex-standalone-amd64.tar.gz	2013-07-09 14:24 	19M	 
-
-Ubuntu 10.04 on both desktop and server.
-
-### Please provide any additional information below.
-
-The problem seems to be runshell trying to call /home/annex/sh, which does not exist. Why would it do that?
-
-> [[done]]
diff --git a/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__/comment_1_fb8a379ed7f4b88bd55245ce5b18042c._comment b/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__/comment_1_fb8a379ed7f4b88bd55245ce5b18042c._comment
deleted file mode 100644
index 3a225a074..000000000
--- a/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__/comment_1_fb8a379ed7f4b88bd55245ce5b18042c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.90"
- subject="comment 1"
- date="2013-07-16T19:30:55Z"
- content="""
-That's not really how you're meant to use the standalone tarball. Just untar it somewhere, and add that directory to PATH (eg, in `~/.bash_profile`).
-"""]]
diff --git a/doc/bugs/Fails_to_create_remote_repo_if_no_global_email_set.mdwn b/doc/bugs/Fails_to_create_remote_repo_if_no_global_email_set.mdwn
deleted file mode 100644
index ce9f5c3da..000000000
--- a/doc/bugs/Fails_to_create_remote_repo_if_no_global_email_set.mdwn
+++ /dev/null
@@ -1,55 +0,0 @@
-### Please describe the problem.
-Trying to create repo on ssh server failed because git didn't know my email.
-
-There were other issues I encountered:
-
- - While connecting to the server assistant says that there will be a password prompt, but doesn't tell that one should expect it to appear in the terminal.
-
- - When creating keys it says that I will be prompted for key password again, but it asks for password to remote server (I understood it wanted a password for its new key pair).. there is no telling for what those password prompts in terminal are for
-
- - It actually requires password for remote server multiple times before it starts to use its own keys
-
- - When failed to test the server or create the repo there the "Retry" button doesn't work (does nothing)
-
- - Maybe it should strip leading ~ from repo name?
-
- - Local pairing with annex 3.20121112ubuntu4 from Ubuntu 13.04  sort of works, but not quite.. it syncs the files, but assistant on Ubuntu doesn't show the name for repo on Gentoo (matching versions are important?)
-
- - When pairing it doesn't check if localhost has running sshd
-
- - I think that was the reason why progress bars were showing pending transfers even after the status message about syncing was green after starting sshd (synced, already up-to-date)
-
-### What steps will reproduce the problem?
-Create repo on remote ssh server without global git settings.
-
-### What version of git-annex are you using? On what operating system?
-git-annex-4.20130601, Gentoo amd64
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-Initialized empty shared Git repository in /home/reinis/~/Annex/Lit/
-init  
-*** Please tell me who you are.
-
-Run
-
-  git config --global user.email "you@example.com"
-  git config --global user.name "Your Name"
-
-to set your account's default identity.
-Omit --global to set the identity only in this repository.
-
-fatal: unable to auto-detect email address (got 'reinis@RD-HC.(none)')
-
-git-annex: user error (git ["--git-dir=/home/me/~/Annex/Lit","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] efailed
-xited 128)
-git-annex: init: 1 failed
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; I've made git-annex detect such broken systems and configure them so git will work. (sigh!) --[[Joey]]
diff --git a/doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles.mdwn b/doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles.mdwn
deleted file mode 100644
index 686bf1887..000000000
--- a/doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-When using git annex as part of an automated backup system, it's sometimes important that we archive all files, including dotfiles.
-
-AFAICT there's no way to tell git annex add to add all dotfiles in a given directory; the only way to do it is to list every dotfile individually.  (git annex add --force doesn't seem to do it.)
-
-This can be worked around with find and xargs, but this is more work than it should be, I think.
-
-It might also be nice if git annex add displayed a warning when adding a directory with dotfiles; something like "Warning, N files ignored; pass --whatever to add them."
-
-> [[!commit 34abd7bca80a8cc012f92d64116014449b1b2392]] explains
-> the rationalle for dotfiles to be skipped. Such as it was. 
-> 
-> I don't think it makes sense for --force to be the flag to override
-> this, because you may want to add dotfiles, but not .gitignored
-> files. So, made a new --include-dotfiles option. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles/comment_1_c258016dd545b0426e75a7c0132154d8._comment b/doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles/comment_1_c258016dd545b0426e75a7c0132154d8._comment
deleted file mode 100644
index c591e7643..000000000
--- a/doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles/comment_1_c258016dd545b0426e75a7c0132154d8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c"
- nickname="Justin"
- subject="comment 1"
- date="2014-03-24T07:03:42Z"
- content="""
-Maybe the right solution is to make --force not ignore dotfiles, although perhaps that would break people who rely on its current behavior.
-"""]]
diff --git a/doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles/comment_2_c506f609390f8bf46433b67fc2a9ddf8._comment b/doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles/comment_2_c506f609390f8bf46433b67fc2a9ddf8._comment
deleted file mode 100644
index e170fcb19..000000000
--- a/doc/bugs/Feature_request:_Flag_to_make_git_annex_add_not_ignore_dotfiles/comment_2_c506f609390f8bf46433b67fc2a9ddf8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c"
- nickname="Justin"
- subject="comment 2"
- date="2014-04-03T01:44:58Z"
- content="""
-Thanks a lot for adding this flag!
-"""]]
diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag.mdwn b/doc/bugs/Feature_request:___34__quvi__34___flag.mdwn
deleted file mode 100644
index 950aad0fc..000000000
--- a/doc/bugs/Feature_request:___34__quvi__34___flag.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-### Please describe the problem.
-git-annex v4.20130827 can't be built on ARM. Technically it's vector that can't be built due to a lack of Template Haskell compilers for this architecture. Vector is a dependency of aeson, which is a dependency of git-annex, which therefore fails to compile.
-
-The only functionality that relies on aeson is, to my knowledge, quvi. Thus my feature request: If you were to introduce a flag to switch quvi support on or off, ARM users like me could circumvent the aeson dependency at build time. In this case we weren't stuck with 4.20130815 (the latest version to not depend on aeson) and could use current and future versions of git-annex. I would appreciate it.
-
-
-### What steps will reproduce the problem?
-See above.
-
-
-### What version of git-annex are you using? On what operating system?
-I'm running Raspbian Wheezy on a Raspberry Pi. The git-annex version to be built is 4.20130827. 
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_1_908c38024fd252328566034608c2dec3._comment b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_1_908c38024fd252328566034608c2dec3._comment
deleted file mode 100644
index a5668f664..000000000
--- a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_1_908c38024fd252328566034608c2dec3._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.255.110"
- subject="comment 1"
- date="2013-09-09T05:25:39Z"
- content="""
-Sorry, I didn't consider this dependency chain.
-
-FWIW, it is possible to build aeson without TH. See `standalone/android/haskell-patches/aeson_0.6.1.0_0001-disable-TH.patch` in the git-annex source tree.
-
-However, I will add a flag.
-"""]]
diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_2_4b6822fe91aa865f2ac1297a3daa3fca._comment b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_2_4b6822fe91aa865f2ac1297a3daa3fca._comment
deleted file mode 100644
index ab4494c19..000000000
--- a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_2_4b6822fe91aa865f2ac1297a3daa3fca._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.255.110"
- subject="comment 2"
- date="2013-09-09T05:44:48Z"
- content="""
-Also, note that libghc-aeson-dev is available for arm in Debian.
-"""]]
diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_3_c72ef77e76b1c99b5e0c78d0742080e7._comment b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_3_c72ef77e76b1c99b5e0c78d0742080e7._comment
deleted file mode 100644
index bbbd5b597..000000000
--- a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_3_c72ef77e76b1c99b5e0c78d0742080e7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="RaspberryPie"
- ip="91.213.8.236"
- subject="comment 3"
- date="2013-09-09T05:52:48Z"
- content="""
-Thanks for the quick answer, I will give these two options a try. A flag will be even better, though. 
-"""]]
diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_4_6092695d6afb1608447afe6f86e6fb83._comment b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_4_6092695d6afb1608447afe6f86e6fb83._comment
deleted file mode 100644
index 10a84afda..000000000
--- a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_4_6092695d6afb1608447afe6f86e6fb83._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="RaspberryPie"
- ip="96.44.189.102"
- subject="comment 4"
- date="2013-09-09T19:31:44Z"
- content="""
-That was fast!
-"""]]
diff --git a/doc/bugs/Finding_an_Unused_file.mdwn b/doc/bugs/Finding_an_Unused_file.mdwn
deleted file mode 100644
index c0e613163..000000000
--- a/doc/bugs/Finding_an_Unused_file.mdwn
+++ /dev/null
@@ -1,152 +0,0 @@
-### Please describe the problem.
-
-SHA256E makes it difficult or impossible to find the original filename
-
-### What steps will reproduce the problem?
-
-I have these unused files:
-
-    $ git annex unused
-    unused . (checking for unused data...) (checking master...) (checking backupbook/HEAD...) (checking b
-    aster...) (checking lang/a-...) (checking lang/master...) 
-      Some annexed data is no longer used by any files:
-        NUMBER  KEY
-        1       SHA256-s9107031--2611c08c9822179c443f001f0bd7ecadf29adcd28edfa4cd1d8938d289cd3950
-        2       SHA256E-s31131336--58c48adad8e5f091981549dfbb2d9ec1003c8c46d1a660673fabefe722358f9b.flac
-        3       SHA256-s9941549--db12950459ba039e6e6f6102a0811213c11a717d140d6e2f169049b958a5e047
-        4       SHA256-s11544438--174514684e03035cc741fa397a1b46f925899bd29189a98173f8f2a136d95ace
-        5       SHA256E-s23445007--4659fae3eda6db7c528af6439fafab1496c740d02bdb67892450a8a2208fb29b.flac
-        6       SHA256E-s47080709--7d331788ae7fee16bccce060c62cafa3cdafc9e0a2b387c0843cfe5871f51fa6.flac
-        7       SHA256E-s33262563--3280607d6d397f84a02542c5ab2e5a9c44d60256b330e3d075078694f0c7f709.flac
-        8       SHA256-s6522640--a1fa374afd62e8c85a115f18f78e679722f63980191c1e11ef84a49ae86f5b4f
-        9       SHA256E-s29266138--27e792d64b6d4a4d44bdafe6867ca25ba79480d1b650cf385e67ff28a1fc5c31.flac
-        10      SHA256-s14568326--023eb9fcefc063ee3ea495f4d382a8feac795d0e1a81c585781f5d369db2e00c
-        11      SHA256-s11907175--73b66220bdbf0ca92209605b93d95d5f9e8247745f9c4367ff20cb53e11c24ac
-        12      SHA256-s9193267--e159038b78c1b239d4cb8eeb892c7acf0e7b82feac7f5b5808dad477605e8478
-        13      SHA256E-s39329047--880ffab99c4b4c48224f409acb0cd797737e4ee70eacdba9bc7d7628ba3d05d7.flac
-        14      SHA256E-s31400468--17ad7b13757d4e4d6e5d193d8295a30f566e00eea82bc19f50dc14b2bbf79ef3.flac
-        15      SHA256E-s51514687--f83eb092ddcdf35e7f729bfa2cc0914b404de60f0b42f69f207cf01766061f16.flac
-        16      SHA256E-s36235648--54e3f893b498b205b0b96bd87d5f14c71712e891c518070a0e1c730d92b3b0ac.flac
-        17      SHA256-s10001177--35afb0b91c8b9f711b2d3b0fe7433ecc3bb13aece78c6170a47323c94233133d
-        18      SHA256-s11830142--3dabe97ccbb68045d9ea82036ddf7211a3925a1bf682e05a32bcdf9b07bec676
-        19      SHA256E-s23102994--f848ed216e6ba17e6b539f31caa5af36266c367ed55dcff243445848b01fbeef.flac
-        20      SHA256E-s38505547--967763ddd42daf782afa9299e67cb5c834153cb20242b50115dda566b24a68c4.flac
-        21      SHA256-s11874975--14774a404526c4b68ede146f527202c59a4bee88376707c93df7da3bdb5345f2
-        22      SHA256-s10188700--18fd4ee62c2b3b1d8944eae528b59de2a45d493a291440edc9b30881ba10ece3
-        23      SHA256E-s53024109--eba924a26f7c602b60a83f208b2204ef3b570fd92ff39fbc067eeaec7c443ab6.flac
-        24      SHA256-s11315225--0a8d2165166995e819e8c78302c45b1eeca9b79a5d77a3574885cbf8e18f265a
-        25      SHA256-s12249573--79b9e551051232079f24902078e1fe5b7daed684e8acaa7cf29c191404a7c3c7
-        26      SHA256E-s47991289--79cfd8db5b3cbe7f50c335bfe0d148c38ff36dbc97b17ea3aff23d642bd5d167.flac
-        27      SHA256E-s76961343--80e91f73e2f3ae6790d752d380118b3fadc223f9f1449354daa0095b5713986c.flac
-        28      SHA256E-s44706648--ce782096aa5c0d58a12f7cbd6dbfe032fa7b0b4810219e23f906bd7fa0d96336.flac
-        29      SHA256-s9393784--1e0e0190030352b3583ce515cd6dfb0db9f2ae39809a462099482947193bfd0f
-        30      SHA256E-s11534608--bfcc0fdcb1ed112b1737d4fe7d2aa88511187d4c1c132bf1b7ab2cda9a7d90ad.flac
-        31      SHA256E-s27916580--1f196e1b6312421f9d9bcd227a3885a5dec299fc47748cd34d5e59fe26374187.flac
-        32      SHA256-s12099941--0a33af0293acb7cffa1727cc04efa4d7abb29a39e8f2165bfd565e2b18879430
-        33      SHA256E-s35578262--01d6f6022161bcaa825cb353012f85bacf3dcb930337ba506fc94b663b0d8043.flac
-        34      SHA256E-s38880984--fa326bd0db5c9e400a4256e77acd488fede23ec714aeab7deb6952091a09e318.flac
-        35      SHA256E-s27784704--a426f885d79d88d8b42b8a23ce267fb1c1855e8f7ff6833ec9ea61860b3c6819.flac
-        36      SHA256-s11827390--17c1e84815805ea7e01555fdfa038a643a97621b84073679d5c649c020750652
-        37      SHA256E-s16632423--9735e37261624360f6a54fd1bc8a893cb5344afdc910e6b9e00c5791036759b0.flac
-        38      SHA256-s10809006--7dd7ff078bdf4571bee6ab06213df970f427a8a2af476d4511a9c08ed0fb814d
-        39      SHA256E-s33043364--3603942143fa4b1c0082ab7ba1db9b536621402eea3ac94e08ef0197062a2ef6.flac
-        40      SHA256E-s33278052--62e1038e26894c6c014af4e77d2d9f79074ff4fc1ca9ca8c16fcc98eee5277c7.flac
-        41      SHA256E-s47299134--0b604bff3ce12d077691d6e6428648da879c021537c094c72633209d5302fd97.flac
-        42      SHA256E-s14882445--16c6aa4aaf8e60da617701281dfdfa372cb049636ae0f10f5aefcd8ce6c472af.flac
-        43      SHA256E-s18168736--dfd7bfe9a433daef89f6f0015dfddaf7ac3611dd31813b0aed049171ac008323.flac
-        44      SHA256-s10060170--9e3b638c4f397d8dbaa2fa9fc2bfacf6f9e93f00c80ee1fdd26971d25aff86ce
-        45      SHA256E-s25630107--26fedc816dee58cb999cd2be8a58f3e8726ff056ba9c2abfbb9d149e7a92a230.flac
-        46      SHA256-s9148609--3f29a2ae1ebd2e4857bb5c92aefb2f50f39a5a984e14645f658d15795a7c72a5
-        47      SHA256-s10576861--7d95469441ef205616ed795012d8a4c59acc00be00aca66bcacd8b041c2499c5
-        48      SHA256E-s23806802--8725d04f04925f4cd456bdb2108a48682cf51a498d97af9f71c58a412b8db9ab.flac
-        49      SHA256E-s43187837--e83648296fa4553556596464efd4ab313529c0062071c9a40113fecede7a5de6.flac
-        50      SHA256-s10384945--055a01b7e06f3165dddd10beb3e98ba4ca47b35abf9d5b2f26187bf07b9aa401
-        51      SHA256E-s54253300--b011eea8ec7ea51f22e0fe09645ffe83183e9589a9784ebc2d6dd0c559f07322.flac
-        52      SHA256-s10335583--008c17c1a994884c6b9c52e10d17373b9160136ffab940992ef0f9d08eac45c1
-        53      SHA256-s9769970--b36fcb01d9df7627106e3a3c283944457f3e282ab62878c186162d465530cfbc
-        54      SHA256-s10329964--dc4d82e085af3ade48d33cf828f8e7eecc27d4c33c448965e1b8bb59832ec473
-        55      SHA256-s10625243--2494e2ef2c64fc77dcb063f7b58079ad668cf46862b7f11eb28943d45f21b8dd
-        56      SHA256E-s44585111--e35b0774729ccf547cd62e652425579781e3cbd76b33a17a0127bdbedb90606a.flac
-        57      SHA256E-s42060728--9e0a533e640086fadefad7167d37d5b3c5de899e1ac5890bfd7a88524701ff14.flac
-        58      SHA256E-s30013479--ae34a897e2f0e1124f04396e75dd41749511ce9930a2891ae3a066597ad518c5.flac
-        59      SHA256E-s38896704--ca6211442c33d9c44b997bef8f1079f07cdd2eb0e9e3c1de1eda9ae8a705f137.flac
-        60      SHA256-s13044938--8714a1db8781daa9f3993128dcda5a5ca904e075723cf38a11bc5e3695cf126f
-        61      SHA256-s8814622--ba374e92c53ddb83605e2b500647117a00e4c6c463653cb0dd0311b76627c2ec
-        62      SHA256E-s14900839--e94089b89629561ebf771543236f31439af1e6fcdce7ff56b9a183041e95e7ea.flac
-        63      SHA256E-s27370218--a4717cf0615cda099ea5740194da8b4e349f2f38f6ebbf5f6111ced7f56d1736.flac
-        64      SHA256E-s57686070--6d02689ccf91317bdfa4d8694ccbf7a9ccf00a7e00b92733769194908b4087d9.flac
-        65      SHA256-s8707306--7f05e3e3dc4336eb7012d5bbb6d3d65047552901858ee4967e4a70d100fd1deb
-        66      SHA256E-s42482194--bb7a968ec9bc0a8813974af9173c38cb39a43aa7d0c2aec203ddb358119e1f25.flac
-        67      SHA256E-s31951334--b19789a9bbb98cb25df7b8a1b6d8856256bc2851cd892c91dddba7cf736542c5.flac
-        68      SHA256E-s35901187--8eae2684aa3566b632a1797bd09d112dd5f438c98b649c000d71640983a549f2.flac
-        69      SHA256E-s40659631--f6ca3227b14c7c050877ce4cc1218fea7582426649cd68fc82a74cae5d6962b4.flac
-        70      SHA256E-s41415180--9c6f0000da119bd70422fe9529c41efb3103ca943697bdfb685f119f6b5ae6fd.flac
-        71      SHA256E-s52313976--e4a59c65e05bd9450ef595b3c08365810205731952e45a68ee0c89bc76fbd9fc.flac
-        72      SHA256E-s44925214--eabc5f7172d5c2e094ff84a5ecce784c172b175c8eeca861aa3996749668ea42.flac
-      (To see where data was previously used, try: git log --stat -S'KEY')
-      
-      To remove unwanted data: git-annex dropunused NUMBER
-      
-    ok
-
-And running:
-
-    $ git log --stat -S'SHA256-s13044938--8714a1db8781daa9f3993128dcda5a5ca904e075723cf38a11bc5e3695cf126f'
-    commit 767a63a54784139f13d69d12fcfbee8f6ca3df41
-    Author: Matthew Forrester <matt@keyboardwritescode.com>
-    Date:   Fri Aug 23 21:38:31 2013 +0100
-    
-        Remove Roger Shah - Openminded! as there is another copy in Unsorted with correct? filenames
-    
-     Amazon/Roger Shah/Openminded!/1114 - Shine (Album Mix).mp3 | 1 -
-     1 file changed, 1 deletion(-)
-    
-    commit 6b04002c03287fb8918bdcdeaae393e862bebd4e
-    Author: Matthew Forrester <matt@keyboardwritescode.com>
-    Date:   Thu Aug 8 21:30:14 2013 +0100
-    
-        Initial checkin
-    
-     Amazon/Roger Shah/Openminded!/1114 - Shine (Album Mix).mp3 | 1 +
-     1 file changed, 1 insertion(+)
-
-Works but I cannot find out how to get the `.flac` files working:
-
-
-`$ git log --stat -S'SHA256E-s38896704--ca6211442c33d9c44b997bef8f1079f07cdd2eb0e9e3c1de1eda9ae8a705f137.flac'`
-
-`$ git log --stat -S'SHA256E-s38896704--ca6211442c33d9c44b997bef8f1079f07cdd2eb0e9e3c1de1eda9ae8a705f137'`
-
-`$ git log --stat -S'SHA256-s38896704--ca6211442c33d9c44b997bef8f1079f07cdd2eb0e9e3c1de1eda9ae8a705f137'`
-
-
-None of which give answers. I don't know if I'm doing it wrong (though I __think__ I'm doing what the instructions say), but I can't make it work.
-
-
-### What version of git-annex are you using? On what operating system?
-
-$ uname -a
-Linux fozz-desktop 3.8.0-31-generic #46-Ubuntu SMP Tue Sep 10 19:56:49 UTC 2013 i686 i686 i686 GNU/Linux
-
-$ git annex version
-git-annex version: 3.20121112ubuntu2
-local repository version: 3
-default repository version: 3
-supported repository versions: 3
-upgrade supported from repository versions: 0 1 2
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> If `git log -S` does not find the key, then it was not used for any
-> commit currently in the git repository. Which is certainly possible;
-> for example `git annex add file; git rm file`.
-> 
-> This is a dup of [[todo/wishlist: option to print more info with 'unused']]; [[done]] --[[Joey]] 
diff --git a/doc/bugs/Fix_for_opening_a_browser_on_a_mac___40__or_xdg-open_on_linux__47__bsd__63____41__.mdwn b/doc/bugs/Fix_for_opening_a_browser_on_a_mac___40__or_xdg-open_on_linux__47__bsd__63____41__.mdwn
deleted file mode 100644
index 428d62ab1..000000000
--- a/doc/bugs/Fix_for_opening_a_browser_on_a_mac___40__or_xdg-open_on_linux__47__bsd__63____41__.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-Utility/WebApp.hs, didn't quite have the right definition to use 'open' instead of 'xdg-open' on OSX, the follow fixes that
-
-<pre>
-diff --git a/Utility/WebApp.hs b/Utility/WebApp.hs
-index 6936c66..0593dda 100644
---- a/Utility/WebApp.hs
-+++ b/Utility/WebApp.hs
-@@ -42,7 +42,7 @@ localhost = "localhost"
- runBrowser :: String -> IO Bool
- runBrowser url = boolSystem cmd [Param url]
-        where
--#if MAC
-+#if OSX
-                cmd = "open"
- #else
-                cmd = "xdg-open"
-</pre>
-
-> [[done]], thanks
-
-I guess I should really clone the repo and submit a stream of minor changes
-:P, @joeyh please let me know if you're getting annoyed with copy and
-pasting the small fixes from the bug/forums section.
-
-> If you're going to be writing some patches, a git repo I can pull from
-> would make my life easier. --[[Joey]]
diff --git a/doc/bugs/Fix_to_thaoe_remote_to_work_with_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn b/doc/bugs/Fix_to_thaoe_remote_to_work_with_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn
deleted file mode 100644
index d4392ff6a..000000000
--- a/doc/bugs/Fix_to_thaoe_remote_to_work_with_latest_tahoe-lafs___40__v._1.10.0__41__.mdwn
+++ /dev/null
@@ -1,62 +0,0 @@
-### Please describe the problem.
-Just a small patch to Tahoe.hs which fixes "initremote repo
-type=thaoe" when using the latest tahoe-lafs release available for
-download.
-
-I'm trying to add an attachment here but the UI says "prohibited by 
-allowed_attachments (user is not an admin)" so please have a look also 
-here: <https://github.com/joeyh/git-annex/pull/21>
-
-### What steps will reproduce the problem?
-
-1. Install latest tahoe-lafs
-2. run "TAHOE_FURL=... git annex initremote repo type=tahoe"
-
-### What version of git-annex are you using? On what operating system?
-
-OS: Debian Sid updated to latest packages
-git-annex: version 5.20140306 
-
-> Thanks, I've fixed this. [[done]] --[[Joey]]
-
-### Please provide any additional information below.
-
-I would like to add few things if i'm able (it's my first time for
-haskell, and I'm a bit lost as now):
-
-1. add an optional parameter or envvar for a root dir cap and switch
-from storing anonymous files to saving a tree of dirs and files
-(much like the webdav back-end) so that i can later renew the
-leases on the files to prevent tahoe's garbage collection process
-expiration (for details see
-<https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/garbage-collection.rst#client-side-renewal>)
-
-The poor man way to that without touching git-annex is to in some
-way collect the caps of the files from annex metadatas and to link
-them to a directory, which where i can then run "tahoe deep-check
---add-lease" on;
-
-> When I talked this over with Zooko before, he 
-> thought it was better for git-annex to not use tahoe's directories,
-> which is why it doesn't. See [[todo/tahoe_lfs_for_reals]].
-> 
-> This is the first I have heard about tahoe garbage collection. 
-> It sounds like it's an optional process.
-> 
-> It would certainly be possible to pull the caps for files out of
-> git-annex's remote state log.
-> --[[Joey]]
-
-2. add convergence as an optional parameter. As of now many of the
-files that i'm willing to manage with git-annex are already on my
-grid, mostly because i've used tahoe's backup command to upload
-them in the past. By using the same convergence value that i've
-already setup on my other tahoe client installation i would be able
-to save much time and space by avoiding duplicates.
-
-Do you have any good pointers to pieces code of git-annex that i can
-read and hack to try to implement this or any other suggestion?
-
-> It was not documented, but you can already pass
-> `shared-convergence-secret=xxx` to `initremote`.
-> I have documented it. --[[Joey]]
diff --git a/doc/bugs/GPG_can__39__t_handle_some_files.mdwn b/doc/bugs/GPG_can__39__t_handle_some_files.mdwn
deleted file mode 100644
index 6c29a95b8..000000000
--- a/doc/bugs/GPG_can__39__t_handle_some_files.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-### Please describe the problem.
-
-It looks like GPG is being used in text mode, or at least isn't overriding the GPG config.
-
-### What steps will reproduce the problem?
-
-Have a binary file with long lines, and attempt to copy it into git-annex.
-
-This will happen:
-
-    $ git-annex copy 09\ Into\ The\ Dissonance.mp3 -t rsync.net_annex
-    copy 09 Into The Dissonance.mp3 (gpg) (checking rsync.net_annex...) (to rsync.net_annex...) gpg: can't handle text lines longer than 19995 characters
-    failed
-    git-annex: copy: 1 failed
-
-A workaround is to remove "textmode" from your gpg.conf, but git-annex should force this.
-
-### What version of git-annex are you using? On what operating system?
-
-7ae625363bcb6e1fc8b3733c1d7814aca05a2368 on Ubuntu 13.04 x86_64
-
-> The sheer number of ways gpg offers of shooting yourself in the foot..
-> Ok [[done]] --[[Joey]] 
diff --git a/doc/bugs/GPG_can__39__t_handle_some_files/comment_1_4388c971e991dbc0326e69c49994df1e._comment b/doc/bugs/GPG_can__39__t_handle_some_files/comment_1_4388c971e991dbc0326e69c49994df1e._comment
deleted file mode 100644
index 60c363fd9..000000000
--- a/doc/bugs/GPG_can__39__t_handle_some_files/comment_1_4388c971e991dbc0326e69c49994df1e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~eythian"
- nickname="eythian"
- subject="comment 1"
- date="2013-09-06T23:37:10Z"
- content="""
-I also had a huge bunch of files come across corrupted, but the one that came after I made this change wasn't. This might be a sign that GPG is corrupting things on the way past.
-"""]]
diff --git a/doc/bugs/GPG_problem_on_Mac.mdwn b/doc/bugs/GPG_problem_on_Mac.mdwn
deleted file mode 100644
index dc4cfaae0..000000000
--- a/doc/bugs/GPG_problem_on_Mac.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-### Please describe the problem.
-Adding a box.com repository fails with an Internal server error and the message "user error (gpg ["--quiet","--trust-model","always","--batch","--passphrase-fd","48","--symmetric","--force-mdc"] exited 2)"
-
-Looking at the logfile it seems like git-annex is looking for gpg (gpg-agent) in /usr/local/MacGPG2/bin/. On my system it is in /usr/local/bin (installed using homebrew). I do not have the directory /usr/local/MacGPG2/.
-
-Not sure if what the git-annex philosophy is: detect the location of such external programs or ship them together with git-annex.
-
-### What steps will reproduce the problem?
-Add a box.com repository (I assume every repository type that uses gpg will fail in the same way) on a Mac.
-
-
-### What version of git-annex are you using? On what operating system?
-* git-annex version 4.20130626-g2dd6f84 (from https://downloads.kitenet.net/git-annex/OSX/current/10.8.2_Mountain_Lion/)
-* Mac OS 10.8.4
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-(Recording state in git...)
-
-(encryption setup) (shared cipher) (testing WebDAV server...)
-(gpg) gpg: error running `/usr/local/MacGPG2/bin/gpg-agent': probably not installed
-gpg: DBG: running `/usr/local/MacGPG2/bin/gpg-agent' for testing failed: Configuration error
-gpg: can't connect to the agent: IPC connect call failed
-gpg: problem with the agent: No agent running
-27/Jun/2013:13:41:37 +0200 [Error#yesod-core] user error (gpg ["--quiet","--trust-model","always","--batch","--passphrase-fd","21","--symmetric","--force-mdc"] exited 2) @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5)
-# End of transcript or log.
-"""]]
-
-> [[done]]; I've updated the OSX autobuild to 
-> use a gpg that doesn't fail when gpg-agent is missing. --[[Joey]]
diff --git a/doc/bugs/GPG_problem_on_Mac/comment_1_9ccfa12e7a9569a7ae9a3b819917c275._comment b/doc/bugs/GPG_problem_on_Mac/comment_1_9ccfa12e7a9569a7ae9a3b819917c275._comment
deleted file mode 100644
index ce04c73e1..000000000
--- a/doc/bugs/GPG_problem_on_Mac/comment_1_9ccfa12e7a9569a7ae9a3b819917c275._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnrFnHRRNUQBB5RCDaIwhVmCcxQp8_yiYw"
- nickname="Oliver"
- subject="comment 1"
- date="2013-06-28T08:42:27Z"
- content="""
-Do you have any form of gpg installed?
-I.e. is it failing to detect your GPG or do you just not have GPG?
-"""]]
diff --git a/doc/bugs/GPG_problem_on_Mac/comment_2_a5e07131e2bc1a646c8439fc2506128b._comment b/doc/bugs/GPG_problem_on_Mac/comment_2_a5e07131e2bc1a646c8439fc2506128b._comment
deleted file mode 100644
index bc81ebaff..000000000
--- a/doc/bugs/GPG_problem_on_Mac/comment_2_a5e07131e2bc1a646c8439fc2506128b._comment
+++ /dev/null
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk7iPiqWr3BVPLWEDvJhSSvcOqheLEbLNo"
- nickname="Dirk"
- subject="comment 2"
- date="2013-06-28T16:45:08Z"
- content="""
-Hi,
-
-I have gpg installed.
-[[!format sh \"\"\"
-$ which gpg
-/usr/local/bin/gpg
-$ which gpg-agent
-/usr/local/bin/gpg-agent
-\"\"\"]]
-(are there other \"programs\" besides gpg and gpg-agent I should check for?)
-
-/usr/local/bin is part of my PATH.
-
-I actually noticed some strange behavior now:
-
- * At some point I was able add the box.com repository to my original annex dir. (I think it was caused by calling gpg-agent on the command line, but I am unsure here.)
- * I created after a reboot then a second annex dir (annex2) (not connected to the first).
- * I was again not able to add a new box.com repository for this new annex (annex2) while the original annex dir is still able to sync to box.com
-
-This seems to indicate that there is some annex specific configuration files influencing this gpg location problem.  
-
-
-"""]]
diff --git a/doc/bugs/GPG_problem_on_Mac/comment_3_388238360f2423f84881e904443efb86._comment b/doc/bugs/GPG_problem_on_Mac/comment_3_388238360f2423f84881e904443efb86._comment
deleted file mode 100644
index 3e8b01d24..000000000
--- a/doc/bugs/GPG_problem_on_Mac/comment_3_388238360f2423f84881e904443efb86._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.254.222"
- subject="comment 3"
- date="2013-07-08T17:10:53Z"
- content="""
-The git-annex dmg includes a copy of gpg.
-
-It seems that the build machine has been switched to having MacGPG2 installed, which hard-codes the location of gpg-agent inside it. This did not used to be the case, and I don't want to use this MacGPG2 build in the dmg.
-
-Guess I'll have to build gpg from source myself on the mac to get a sane version to distribute..
-"""]]
diff --git a/doc/bugs/Git_annex_add_fails_on_read-only_files.mdwn b/doc/bugs/Git_annex_add_fails_on_read-only_files.mdwn
deleted file mode 100644
index 50f005a7e..000000000
--- a/doc/bugs/Git_annex_add_fails_on_read-only_files.mdwn
+++ /dev/null
@@ -1,49 +0,0 @@
-### Please describe the problem.
-
-Git annex cannot add/import files in folders without w or x permission
-
-Note that (as stated in the comments) this might not be a bug. The problem might somewhere within Git, because Git does not manage file permissions very well. I was just hoping that I could import large directory trees into git-annex with a simple call to "git annex import"; now it seems I have to fix their permissions first.
-
-### What steps will reproduce the problem?
-
-    $ cd /tmp
-    $ mkdir -p folder/subfolder
-    $ echo "some text" > folder/subfolder/some_file.txt
-    $ chmod 500 folder/subfolder
-    $ mkdir annex
-    $ cd annex
-    $ git init
-    $ git annex init "Testing git annex"
-    $ git annex import ../folder
-    Fails
-    $ chmod 600 ../folder/subfolder
-    $ git annex import ../folder
-    Fails
-    $ chmod 700 ../folder/subfolder
-    $ git annex import ../folder
-    Works. Subfolder now has 755 permissions
-
-### What version of git-annex are you using? On what operating system?
-
-    git-annex version: 4.20131106
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA CryptoHash
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-    git version 1.8.4.3
-
-> Based on the new example, I don't consider this to be a bug.
-> I don't think that `git annex import` should disregard directory
-> permissions when importing files from them.
-> 
-> One very good reason not to
-> eg, chmod the directory itself is that if it did, running `git annex
-> import` on a git-annex repository would defeat git-annex's own use of
-> directory permissions to prevent deletion of the files in that
-> repository!
-> 
-> So, [[done]] --[[Joey]]
diff --git a/doc/bugs/Git_annex_add_fails_on_read-only_files/comment_1_d31018e8bf31d729ee9fee43a0a07934._comment b/doc/bugs/Git_annex_add_fails_on_read-only_files/comment_1_d31018e8bf31d729ee9fee43a0a07934._comment
deleted file mode 100644
index 0a4e61bc5..000000000
--- a/doc/bugs/Git_annex_add_fails_on_read-only_files/comment_1_d31018e8bf31d729ee9fee43a0a07934._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 1"
- date="2013-11-26T19:47:28Z"
- content="""
-I cannot reproduce this problem on Linux, with version 4.20131106. I tried in both direct and indirect mode, on Linux. 
-
-I was, however, able to exactly reproduce the error message if I made the *directory* be not writable, and used indirect mode. This is because git-annex has to move the file the .git/annex/objects, and put a symlink in place, and so has to be allowed to write to the directory. Interestingly, direct mode does not have this limiation, although I doubt git-annex would ever be very useful when run in a directory you lack write permission to.
-"""]]
diff --git a/doc/bugs/Git_annex_add_fails_on_read-only_files/comment_2_e38e7048749f890169cd0be602be6ee7._comment b/doc/bugs/Git_annex_add_fails_on_read-only_files/comment_2_e38e7048749f890169cd0be602be6ee7._comment
deleted file mode 100644
index 610eea713..000000000
--- a/doc/bugs/Git_annex_add_fails_on_read-only_files/comment_2_e38e7048749f890169cd0be602be6ee7._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlq4ClC5EMN1Vq1DpWXAqP5TiDnCK1mSfk"
- nickname="Jonas"
- subject="comment 2"
- date="2013-11-27T18:05:02Z"
- content="""
-Thank you for looking into this, and sorry about the low quality of the initial bug report. I now replaced the example by a better one.
-
-As you say, this might not be a bug. I was just not aware that migrating files into git-annex would mean forsaking their permissions.
-"""]]
diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android.mdwn b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android.mdwn
deleted file mode 100644
index bf68208da..000000000
--- a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android.mdwn
+++ /dev/null
@@ -1,280 +0,0 @@
-### Please describe the problem.
-git add hangs.
-Maybe because of encrypted sdcard?
-
-
-
-
-
-### What steps will reproduce the problem?
-
-    app_30@android:/sdcard $ mkdir annex;cd annex
-    app_30@android:/sdcard/annex $ git init
-    Initialized empty Git repository in /mnt/sdcard/annex/.git/
-    app_30@android:/sdcard/annex $ git annex init
-    init
-      Detected a crippled filesystem.
-    
-      Enabling direct mode.
-    
-      Detected a filesystem without fifo support.
-    
-      Disabling ssh connection caching.
-    ok
-    (Recording state in git...)
-    app_30@android:/sdcard/annex $ touch lala
-    git annex add lala --debug                                   <
-    [2013-10-13 22:05:17 CEST] read: git ["--git-dir=/mnt/sdcard/annex/.git","--work-tree=/mnt/sdcard/annex","ls-files","--others","--exclude-standard","-z","--","lala"]
-    [2013-10-13 22:05:17 CEST] read: git ["--git-dir=/mnt/sdcard/annex/.git","--work-tree=/mnt/sdcard/annex","ls-files","--modified","-z","--","lala"]
-    [2013-10-13 22:05:17 CEST] chat: git ["--git-dir=/mnt/sdcard/annex/.git","--work-tree=/mnt/sdcard/annex","cat-file","--batch"]
-    add lala [2013-10-13 22:05:17 CEST] chat: git ["--git-dir=/mnt/sdcard/annex/.git","--work-tree=/mnt/sdcard/annex","check-attr","-z","--stdin","annex.backend","annex.numcopies","--"]
-    ** HANGS **
-  
-
-
-The same will happen when just running and asking assistant to create annex for camera.
-
-ps aux | grep -i git:
-
-    app_30    9870  8950  2512   464   c009cd2c 400456a4 S git
-    app_30    9871  9870  64900  7552  ffffffff 40108a38 S git-annex
-    app_30    9876  9871  0      0     ffffffff 00000000 Z git
-    app_30    9877  9871  0      0     ffffffff 00000000 Z git
-    app_30    9878  9871  2512   608   c0114a4c 400b2878 S git
-    app_30    9879  9871  2512   556   c0114a4c 40074878 S git
-
-lsof | grep git:
-
-    1|app_30@android:/sdcard $ lsof | grep git                                     
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/pts/2
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/pts/2
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/pts/2
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/main
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/radio
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/events
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/system
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/__properties__ (deleted)
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/framework-res.apk
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/com.htc.resources.apk
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/framework-htc-res.apk
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/framework.jar
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/etc/system_fonts.xml
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/etc/fallback_fonts.xml
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/fonts/Roboto-Regular.ttf
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/core.jar
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/urandom
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/main
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/radio
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/events
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/system
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/cpuctl/tasks
-    9870	/data/data/ga.androidterm/lib/lib.git.so	socket:[1172354]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172355]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172355]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/cpuctl/bg_non_interactive/tasks
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172358]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172358]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	anon_inode:[eventpoll]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/ashmem
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/ashmem
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/data/app/ga.androidterm-1.apk
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/data/app/ga.androidterm-1.apk
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/app/Aluminum.apk
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172380]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172381]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/data/data/ga.androidterm/fifo
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172382]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/pts/2
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/system/fonts/DroidSansMono.ttf
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172407]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172407]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	anon_inode:[eventpoll]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	/dev/ashmem
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1177783]
-    9870	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1177784]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/pts/2
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/pts/2
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/pts/2
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/log/main
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/log/radio
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/log/events
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/log/system
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	anon_inode:[eventpoll]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1184035]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/__properties__ (deleted)
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1184035]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	anon_inode:[eventfd]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1184036]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1184036]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	anon_inode:[eventfd]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1184039]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1184043]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1184044]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1184046]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1184047]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/framework/framework-res.apk
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/framework/com.htc.resources.apk
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/framework/framework-htc-res.apk
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/framework/framework.jar
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/etc/system_fonts.xml
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/etc/fallback_fonts.xml
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/fonts/Roboto-Regular.ttf
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/framework/core.jar
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/urandom
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/log/main
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/log/radio
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/log/events
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/log/system
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/cpuctl/tasks
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	socket:[1172354]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1172355]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1172355]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/cpuctl/bg_non_interactive/tasks
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1172358]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1172358]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	anon_inode:[eventpoll]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/ashmem
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/ashmem
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/data/app/ga.androidterm-1.apk
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/data/app/ga.androidterm-1.apk
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/app/Aluminum.apk
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1172380]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1172381]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/data/data/ga.androidterm/fifo
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1172382]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/pts/2
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/system/fonts/DroidSansMono.ttf
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1172407]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1172407]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	anon_inode:[eventpoll]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	/dev/ashmem
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1177783]
-    9871	/data/data/ga.androidterm/lib/lib.git-annex.so	pipe:[1177784]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1184043]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1184044]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/pts/2
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/main
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/radio
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/events
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/system
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/__properties__ (deleted)
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/framework-res.apk
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/com.htc.resources.apk
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/framework-htc-res.apk
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/framework.jar
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/etc/system_fonts.xml
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/etc/fallback_fonts.xml
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/fonts/Roboto-Regular.ttf
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/core.jar
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/urandom
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/main
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/radio
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/events
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/system
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/cpuctl/tasks
-    9878	/data/data/ga.androidterm/lib/lib.git.so	socket:[1172354]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172355]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172355]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/cpuctl/bg_non_interactive/tasks
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172358]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172358]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	anon_inode:[eventpoll]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/ashmem
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/ashmem
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/data/app/ga.androidterm-1.apk
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/data/app/ga.androidterm-1.apk
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/app/Aluminum.apk
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172380]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172381]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/data/data/ga.androidterm/fifo
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172382]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/pts/2
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/system/fonts/DroidSansMono.ttf
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172407]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172407]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	anon_inode:[eventpoll]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	/dev/ashmem
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1177783]
-    9878	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1177784]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1184046]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1184047]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/pts/2
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/main
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/radio
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/events
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/system
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/__properties__ (deleted)
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/framework-res.apk
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/com.htc.resources.apk
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/framework-htc-res.apk
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/framework.jar
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/etc/system_fonts.xml
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/etc/fallback_fonts.xml
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/fonts/Roboto-Regular.ttf
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/framework/core.jar
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/urandom
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/main
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/radio
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/events
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/log/system
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/cpuctl/tasks
-    9879	/data/data/ga.androidterm/lib/lib.git.so	socket:[1172354]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172355]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172355]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/cpuctl/bg_non_interactive/tasks
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172358]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172358]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	anon_inode:[eventpoll]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/ashmem
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/ashmem
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/data/app/ga.androidterm-1.apk
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/data/app/ga.androidterm-1.apk
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/app/Aluminum.apk
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172380]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172381]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/data/data/ga.androidterm/fifo
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172382]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/pts/2
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/system/fonts/DroidSansMono.ttf
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172407]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1172407]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	anon_inode:[eventpoll]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	/dev/ashmem
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1177783]
-    9879	/data/data/ga.androidterm/lib/lib.git.so	pipe:[1177784]
-
-
-vfat/sdcard entry:
-    /dev/block/dm-2 /mnt/sdcard vfat     rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702, \ 
-    allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
-    tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
-
-
-
-### What version of git-annex are you using? On what operating system?
-Version from git annex version:
-2a8136b6bd60a17d687eb800594ec7c37b872b3d
-
-I tried both daily build and most recent 'stable' with the same effect.
-
-Android 4.0.3 (Htc One V)
-
-The same happens on my another android device; Samsung tablet with... also 4.0.3.
-Tried to gather strace information on git, but couldn't. If anything more is necessary,
-please let me know.
-
-The same happens when I git annex add in /data/data/ga.androidterm/anntmp - so it's not sdcard nor vfat. 
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> I have updated git-annex to work with the new git, which will be 1.8.5.
-> This fix should appear in the android autobuild within an hour if you
-> want to try it. [[done]] --[[Joey]]
diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_1_2fc435d1c741f9fc422401f682e7c8b7._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_1_2fc435d1c741f9fc422401f682e7c8b7._comment
deleted file mode 100644
index 19b8ae1a6..000000000
--- a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_1_2fc435d1c741f9fc422401f682e7c8b7._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="64.134.31.139"
- subject="I can reproduce this! (with 4.20130923-g78e9013)"
- date="2013-10-15T19:57:19Z"
- content="""
-Comparing straces from Android and Linux, it seems to be due to git check-attr outputting something different:
-
-<pre>
-read(16, \"andro\0annex.backend\0unspecified\0\"..., 8096) = 66
-read(10, \"linux: annex.backend: unspecifie\"..., 8096) = 70
-</pre>
-
-So, this is not actually Android specific, thankfully. It's just a breakage caused by a change in a newish version of git! I think it's not yet released, just Android is building from git head right now.
-
-I have reverted the Android stable build to the last version I think won't be affected by this.
-"""]]
diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_2_b73fb99a75aef912f8286626c5bde66d._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_2_b73fb99a75aef912f8286626c5bde66d._comment
deleted file mode 100644
index 12b0f9f6e..000000000
--- a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_2_b73fb99a75aef912f8286626c5bde66d._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="bla"
- ip="91.121.95.205"
- subject="Testing"
- date="2013-10-15T21:24:35Z"
- content="""
-Last autobuild (installed by replacing existing)
-annex 89345b7  with git 1.8.4.474.g128a96c  - also hangs on add in the same manner (in previously created tmp git in /data/data/ga.androidterm/anntmp). Not sure if I did something wrong.
-
-Current stable release - works just fine (deinstalled, installed again - replace failed somehow)
-
-
-
-"""]]
diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_3_b7115f2c658439ff59a029f500697fc1._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_3_b7115f2c658439ff59a029f500697fc1._comment
deleted file mode 100644
index eb3c993a8..000000000
--- a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_3_b7115f2c658439ff59a029f500697fc1._comment
+++ /dev/null
@@ -1,57 +0,0 @@
-[[!comment format=mdwn
- username="bla"
- ip="91.121.95.205"
- subject="More info on latest autobuild"
- date="2013-10-15T21:42:52Z"
- content="""
-Using adb shell, su app_30, runshell:
-
-     app_30@android:/data/data/ga.androidterm/anntmp $ head -n 3 /sdcard/git-annex.>
-     Installation starting to /data/data/ga.androidterm
-     89345b7108f5c18eba0845f84780a26d069d011d
-     installing busybox
-
-    app_30@android:/data/data/ga.androidterm/anntmp $ git version
-    git version 1.8.4.474.g128a96c
-    app_30@android:/data/data/ga.androidterm/anntmp $ git annex version
-    git-annex version: 4.20131015-g89345b7
-    build flags: Assistant Webapp Testsuite S3 WebDAV Inotify DNS Feeds Quvi TDFA CryptoHash
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-    git init; git annex init; touch lala
-    130|app_30@android:/data/data/ga.androidterm/anntmp $ git annex add lala --deb>
-    [2013-10-15 23:37:20 CEST] read: git [\"--git-dir=/data/data/ga.androidterm/anntmp/.git\",\"--work-tree=/data/data/ga.androidterm/anntmp\",\"ls-files\",\"--others\",\"--exclude-standard\",\"-z\",\"--\",\"lala\"]
-    [2013-10-15 23:37:20 CEST] read: git [\"--git-dir=/data/data/ga.androidterm/anntmp/.git\",\"--work-tree=/data/data/ga.androidterm/anntmp\",\"diff\",\"--name-only\",\"--diff-filter=T\",\"-z\",\"--\",\"lala\"]
-    add lala [2013-10-15 23:37:20 CEST] chat: git [\"--git-dir=/data/data/ga.androidterm/anntmp/.git\",\"--work-tree=/data/data/ga.androidterm/anntmp\",\"check-attr\",\"-z\",\"--stdin\",\"annex.backend\",\"annex.numcopies\",\"--\"]
-    *hangs*
-
-
-
-    echo lala | git check-attr -z --stdin annex.backend annex.numcopies | hexdump -C
-    00000000  6c 61 6c 61 0a 00 61 6e  6e 65 78 2e 62 61 63 6b  |lala..annex.back|
-    00000010  65 6e 64 00 75 6e 73 70  65 63 69 66 69 65 64 00  |end.unspecified.|
-    00000020  6c 61 6c 61 0a 00 61 6e  6e 65 78 2e 6e 75 6d 63  |lala..annex.numc|
-    00000030  6f 70 69 65 73 00 75 6e  73 70 65 63 69 66 69 65  |opies.unspecifie|
-    00000040  64 00                                             |d.|
-    00000042
-
-While on my laptop (git 1.8.4.rc3)
-
-    feather annex % echo lala | git check-attr -z --stdin annex.backend annex.numcopies | hexdump -C
-    00000000  22 6c 61 6c 61 5c 6e 22  3a 20 61 6e 6e 65 78 2e  |\"lala\n\": annex.|
-    00000010  62 61 63 6b 65 6e 64 3a  20 75 6e 73 70 65 63 69  |backend: unspeci|
-    00000020  66 69 65 64 0a 22 6c 61  6c 61 5c 6e 22 3a 20 61  |fied.\"lala\n\": a|
-    00000030  6e 6e 65 78 2e 6e 75 6d  63 6f 70 69 65 73 3a 20  |nnex.numcopies: |
-    00000040  75 6e 73 70 65 63 69 66  69 65 64 0a              |unspecified.|
-    0000004c
-
-So in fact very different indeed.
-
-
-Hope it helps - assuming i didn't do some weird mistake. I'll happily use stable version for now. GREAT THANKS!
-"""]]
diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_4_67de7a56ddb06fc0e31cc011d281c633._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_4_67de7a56ddb06fc0e31cc011d281c633._comment
deleted file mode 100644
index 4456e2cef..000000000
--- a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_4_67de7a56ddb06fc0e31cc011d281c633._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="64.134.31.139"
- subject="comment 4"
- date="2013-10-16T16:16:02Z"
- content="""
-Thanks for testing that. I had a fencepost error, which I've fixed, and actually tested with problimatic git version now.
-"""]]
diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_5_58fdb2a00f1737746cdbc804f831a0e7._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_5_58fdb2a00f1737746cdbc804f831a0e7._comment
deleted file mode 100644
index 7bbef0fdd..000000000
--- a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_5_58fdb2a00f1737746cdbc804f831a0e7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://adamspiers.myopenid.com/"
- nickname="Adam"
- subject="any chance of a new release?"
- date="2013-10-22T13:33:57Z"
- content="""
-I just upgraded via cabal install to 4.20131002, which (unsurprisingly, I guess) still exhibits this issue.  Would be great if a new release could be cut for this ...
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion.mdwn b/doc/bugs/Hanging_on_install_on_Mountain_lion.mdwn
deleted file mode 100644
index f18a0ef40..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-### Please describe the problem.
-
-In trying to install git-annex on my mac OSX Mountain Lion, the program is hanging when I open the program.
-
-### What steps will reproduce the problem?
-
-Open the DMG, drag the app to applications folder, double-click on the application. Web browser opens with a localhost url. The webpage says "Starting webapp..." and doesn't go anywhere. Initialization seems to fail and I need to force quit the application.
-
-### What version of git-annex are you using? On what operating system?
-
-I'm not totally sure (since it hangs and I can't check a version number, but since I just downloaded it now and the homepage says the latest version is "version 4.20130621" which was released 2 days and 13 hours ago, I assume that is it. 
-
-I'm using OSX 10.8.4.
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> Fixed root cause. [[done]] --[[Joey]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_10_f57ff027b19ca16e2ecf1fc6aee9ef4a._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_10_f57ff027b19ca16e2ecf1fc6aee9ef4a._comment
deleted file mode 100644
index 91de599c3..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_10_f57ff027b19ca16e2ecf1fc6aee9ef4a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.193"
- subject="comment 10"
- date="2013-06-26T22:10:39Z"
- content="""
-Seems to be caused by an upgrade of the Mac the autobuilds run on. Particularly, downgrading yesod and warp to older versions seems to avoid the hang, so I've temporarily adjusted the deps so it will build with the old versions.
-
-I have updated the daily autobuild for OSX, as well as the dmg for the current release. Testing appreciated.
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_11_2ff78d2090d0fd3418ab50b27c6028ce._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_11_2ff78d2090d0fd3418ab50b27c6028ce._comment
deleted file mode 100644
index cd67b45c3..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_11_2ff78d2090d0fd3418ab50b27c6028ce._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.193"
- subject="not OSX specific"
- date="2013-06-27T02:36:04Z"
- content="""
-I was able to reproduce the hang on linux after upgrading to the newest version of warp and yesod.
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_1_523d3c0c71f80536850a001b90fd0e9e._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_1_523d3c0c71f80536850a001b90fd0e9e._comment
deleted file mode 100644
index 06ab0f904..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_1_523d3c0c71f80536850a001b90fd0e9e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnGrQBFPptA2GU_Nx8KrxRGtyAS7PIlwjw"
- nickname="Nathan"
- subject="me too."
- date="2013-06-24T07:33:54Z"
- content="""
-I'm having the exact same problem (OSX 10.8.2)
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_2_6c360c64093b016c2150206dc3ad1709._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_2_6c360c64093b016c2150206dc3ad1709._comment
deleted file mode 100644
index 46c53294c..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_2_6c360c64093b016c2150206dc3ad1709._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnrFnHRRNUQBB5RCDaIwhVmCcxQp8_yiYw"
- nickname="Oliver"
- subject="comment 2"
- date="2013-06-25T11:19:34Z"
- content="""
-Had that on snow leopard as well, using both the release and the nightlies. In the end I built it myself using cabal and that was OK.
-
-Possibly using the cli from inside the app to initialize the repo might fix it.
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_3_7b77fd9b7dc236c345f2f6149c8138ee._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_3_7b77fd9b7dc236c345f2f6149c8138ee._comment
deleted file mode 100644
index 823474f95..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_3_7b77fd9b7dc236c345f2f6149c8138ee._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnGrQBFPptA2GU_Nx8KrxRGtyAS7PIlwjw"
- nickname="Nathan"
- subject="comment 3"
- date="2013-06-25T13:39:55Z"
- content="""
-Hi there, I couldn't get it to build with cabal (likely my fault, ie. inexperience).
-
-Can I please confirm something: Theoretically I dont need to do *any* preparation to start using git-annex assistant, right? As in I dont need to first configure git separately, or set up any folder hierarchies or such?  The idea is that the assistant itself does all that's required? I just wonder if through my naivety I am missing a basic step and making a rookie mistake.
-
-A couple of notes:
-
-Running  **/Applications/git-annex.app/Contents/MacOS/git-annex init** 
-
-Returns **git-annex: Not in a git repository.**
-
-Any further assistance you may offer woudl be great, because I'd love to start investigating the potential for using git-annex in a multi-user environment (managing motion design projects).
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_5_08289596445d7588e43d35490fbfe5f4._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_5_08289596445d7588e43d35490fbfe5f4._comment
deleted file mode 100644
index d9700eab0..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_5_08289596445d7588e43d35490fbfe5f4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmxns2UBAMDbTwrwHq_Lx1sNKrVVayq1X4"
- nickname="Darren"
- subject="comment 5"
- date="2013-06-25T14:54:47Z"
- content="""
-same problem here, latest version from the website and running OSX 10.8.4.
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_5_2a336fe7b8aed07cbdaa868bd34078f9._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_5_2a336fe7b8aed07cbdaa868bd34078f9._comment
deleted file mode 100644
index aceafcf9f..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_5_2a336fe7b8aed07cbdaa868bd34078f9._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.193"
- subject="comment 5"
- date="2013-06-25T17:14:02Z"
- content="""
-To get this fixed, someone is going to need to do some investigation of what is happening. I do not have resources to debug OSX problems that cannot be reproduced using the command line.
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_6_ea7a40c3b6748738421aed00a6f7ca10._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_6_ea7a40c3b6748738421aed00a6f7ca10._comment
deleted file mode 100644
index 16ecca625..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_6_ea7a40c3b6748738421aed00a6f7ca10._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkQafKy7hNSEolLs6TvbgUnkklTctUY9LI"
- nickname="Zellyn"
- subject="Happy to debug"
- date="2013-06-26T02:47:35Z"
- content="""
-Hi Joey, I'm having the same problem. I'm currently trying the homebrew route.
-
-I would be happy to debug, but I'm not familiar at all with git annex or the assistant, so I don't even know where to start looking. Let me know what would be useful to try, and I'll try it and post the results.
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_7_00962da9288976f8a48d0cbc08e1d9e2._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_7_00962da9288976f8a48d0cbc08e1d9e2._comment
deleted file mode 100644
index 2bddffc70..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_7_00962da9288976f8a48d0cbc08e1d9e2._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkQafKy7hNSEolLs6TvbgUnkklTctUY9LI"
- nickname="Zellyn"
- subject="More info"
- date="2013-06-26T04:21:47Z"
- content="""
-Looking at what the browser is doing:
-
-1. Open file://localhost/var/folders/00/0wpr8000h01000cxqpysvccm003kv1/T/webapp72069.html
-2. Meta refresh to: http://127.0.0.1:64190/?auth=7b8464a1fe3ed0386520bd2b214dbb963864b345151edc0b5febc0310a7974d89fda2ab6464d5791e6b1a474bebb86026b7c90ebb920c51a8291940c75e7c1f9
-3. Redirect to: http://127.0.0.1:64190/config?auth=7b8464a1fe3ed0386520bd2b214dbb963864b345151edc0b5febc0310a7974d89fda2ab6464d5791e6b1a474bebb86026b7c90ebb920c51a8291940c75e7c1f9
-4. Redirect to: http://127.0.0.1:64190/config/repository/new/first?auth=7b8464a1fe3ed0386520bd2b214dbb963864b345151edc0b5febc0310a7974d89fda2ab6464d5791e6b1a474bebb86026b7c90ebb920c51a8291940c75e7c1f9
-5. hang indefinitely
-
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_8_5d53d23e529f33f6e7deb10643831613._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_8_5d53d23e529f33f6e7deb10643831613._comment
deleted file mode 100644
index 14cc3ec55..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_8_5d53d23e529f33f6e7deb10643831613._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.193"
- subject="comment 8"
- date="2013-06-26T19:06:42Z"
- content="""
-Thanks, I've reproduced the hang using wget at the command line.
-
-Probably something has been broken in the switch to a new version of Yesod.
-
-"""]]
diff --git a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_9_f00c8761e3184975b6645c0c3e241365._comment b/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_9_f00c8761e3184975b6645c0c3e241365._comment
deleted file mode 100644
index 2639fb350..000000000
--- a/doc/bugs/Hanging_on_install_on_Mountain_lion/comment_9_f00c8761e3184975b6645c0c3e241365._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkQafKy7hNSEolLs6TvbgUnkklTctUY9LI"
- nickname="Zellyn"
- subject="Excellent"
- date="2013-06-26T21:01:38Z"
- content="""
-Excellent news. If you need any more help debugging, let me know.
-
-Out of curiosity, what would be the next step of useful information for you? lsof on the process didn't seem to show anything interesting...
-"""]]
diff --git a/doc/bugs/Hangs_on_creating_repository_when_using_--listen.mdwn b/doc/bugs/Hangs_on_creating_repository_when_using_--listen.mdwn
deleted file mode 100644
index fe0fe80f3..000000000
--- a/doc/bugs/Hangs_on_creating_repository_when_using_--listen.mdwn
+++ /dev/null
@@ -1,49 +0,0 @@
-### Please describe the problem.
-When using the git-annex webapp with the --listen paramter it as usual asks one to create a new repository on first startup. Selecting a repository location here and clicking "Make repository" button leads to a never ending loading browser and some git zombies. 
-
-### What steps will reproduce the problem?
-Two machines needed
-
-1. On machine one: git-annex webapp --listen=\<machine1-public-ip\>:34561 (you can choose another port as well)
-2. On machine two: use a browser to go to the url the last step gave you
-3. Click on make repository
-
-
-### What version of git-annex are you using? On what operating system?
-* git-annex version: 4.20130601
-* build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-* built using cabal
-* on Ubuntu 13.04 32bit
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[2013-06-12 21:59:37 CEST] main: starting assistant version 4.20130601
-WebApp crashed: unable to bind to local socket
-[2013-06-12 21:59:37 CEST] WebApp: warning WebApp crashed: unable to bind to local socket
-
-  dbus failed; falling back to mtab polling (ClientError {clientErrorMessage = "runClient: unable to determine DBUS address", clientErrorFatal = True})
-
-  No known network monitor available through dbus; falling back to polling
-(scanning...) [2013-06-12 21:59:37 CEST] Watcher: Performing startup scan
-(started...) 
-
-
-# End of transcript or log.
-"""]]
-
-> The problem is that, when a port is specified, it is used for each web
-> server started, and the process of making a new repository unavoidably
-> requires it to start a second web server instance. This would also affect
-> switching between existing repositories in the webapp. I don't see
-> any way to make it not crash here, except for ignoring the port it was told
-> to use when something else is already listening there. --[[Joey]] 
-
-[[!tag /design/assistant]]
-
->> --listen no longer accepts a port. Use the new HTTPS support instead.
->> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_1_8cbe786de8cf8b407418149b9c811aab._comment b/doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_1_8cbe786de8cf8b407418149b9c811aab._comment
deleted file mode 100644
index b0132de65..000000000
--- a/doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_1_8cbe786de8cf8b407418149b9c811aab._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk7iPiqWr3BVPLWEDvJhSSvcOqheLEbLNo"
- nickname="Dirk"
- subject="comment 1"
- date="2013-06-15T11:39:15Z"
- content="""
-Thanks for looking into this.
-
-Following your explanation there is no easy solution to this. I guess one could potentially grey out all actions in the webapp that lead to problems. But that might be overkill for a rare use case (which I assume the use of --listen with a given port is). Maybe just documenting for which use cases (repository creation, switching, ...?) the provided port will lead to problems (e.g. in the man page under the --listen section) is good enough (it is for me)?
-
- 
-
-
-"""]]
diff --git a/doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_2_dc128eeddeaaf3f84e71aca0fb7d341f._comment b/doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_2_dc128eeddeaaf3f84e71aca0fb7d341f._comment
deleted file mode 100644
index 55d7efa1c..000000000
--- a/doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_2_dc128eeddeaaf3f84e71aca0fb7d341f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 2"
- date="2013-08-24T18:52:11Z"
- content="""
-This also affects creating a second repository in the webapp, not just the repository creation at first startup.
-"""]]
diff --git a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__.mdwn b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__.mdwn
deleted file mode 100644
index 69b0c4116..000000000
--- a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__.mdwn
+++ /dev/null
@@ -1,295 +0,0 @@
-### Please describe the problem.
-
-I use both the assistant and the command line. Unfortunately I often end up
-in a state where I cannot do a "git annex sync" (it fails as described below)
-and I have to use the assistant to synchronize things to make the sync work. I
-would like to know how to do the same thing using only the command line.
-
-### What steps will reproduce the problem?
-
-This problem involves two repos: a local, indirect mode, manual group, repo, and
-a ssh remote archive group bare repo (with full git annex available
-remotely). The local repo is "top" and the remote one is "mini_archive".
-
-I start with the assistant not running, and the two repos in sync. Note that the
-remote server cannot directly contact the local repo.
-
-local:
-
-    schmitta@top ~/D/annex (master)> git annex sync
-    commit
-    ok
-    pull mini_archive 
-    ok
-
-remote:
-
-    schmitta@mini ~/a/archive> git annex sync
-    commit
-    ok
-
-I then add a file locally and try to sync, getting a problem on mini_archive:
-
-    schmitta@top ~/D/annex (master)> git annex add videos/Minecraft/Icy\ and\ FlowerChild\ Play\ -\ Better\ Than\ Wolves\ 3-qg6LVTcDl4Y.mp4 
-    add videos/Minecraft/Icy and FlowerChild Play - Better Than Wolves 3-qg6LVTcDl4Y.mp4 (checksum...) ok
-    (Recording state in git...)
-    schmitta@top ~/D/annex (master)> git annex sync
-    commit
-    ok
-    pull mini_archive 
-    ok
-    push mini_archive 
-    Counting objects: 15, done.
-    Delta compression using up to 4 threads.
-    Compressing objects: 100% (10/10), done.
-    Writing objects: 100% (10/10), 1.01 KiB | 0 bytes/s, done.
-    Total 10 (delta 4), reused 0 (delta 0)
-    remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-    To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
-       a5b002b..dde2626  master -> synced/master
-     ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-    error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-    failed
-    git-annex: sync: 1 failed
-
-I try to merge and sync on the remote (I assume sync also does merge, but I'm
-not sure).
-
-    schmitta@mini ~/a/archive> git annex merge
-    merge git-annex ok
-    schmitta@mini ~/a/archive> git annex sync
-    commit
-    ok
-
-Back on the local machine, I still have the conflict.
-
-    schmitta@top ~/D/annex (master) [1]> git annex sync
-    commit
-    ok
-    pull mini_archive 
-    ok
-    push mini_archive 
-    Counting objects: 7, done.
-    Delta compression using up to 4 threads.
-    Compressing objects: 100% (5/5), done.
-    Writing objects: 100% (5/5), 513 bytes | 0 bytes/s, done.
-    Total 5 (delta 1), reused 0 (delta 0)
-    remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-    To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
-     ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-    error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-    failed
-    git-annex: sync: 1 failed
-
-From this state, the only way to resolve things is to launch the web app. It
-tells me "synced with mini_archive" (and it starts uploading the new file). Then
-on the server there is something to merge. (I haven't waited for the file to
-finish uploading in this case.)
-
-    schmitta@mini ~/a/archive> git annex merge
-    merge git-annex (merging refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/git-annex into git-annex...)
-    ok
-    schmitta@mini ~/a/archive> git annex sync
-    commit
-    ok
-
-and I can then sync on the local repo:
-
-    schmitta@top ~/D/annex (master) [1]> git annex sync
-    commit
-    ok
-    pull mini_archive 
-    From ssh://git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive
-       8f39d4c..cb7f6c3  git-annex  -> mini_archive/git-annex
-    ok
-
-Note that I need to do the remote merge for things to work. After the file has
-finished uploading, I get back in a conflict:
-
-    schmitta@top ~/D/annex (master)> git annex sync
-    commit
-    ok
-    pull mini_archive 
-    ok
-    push mini_archive 
-    Total 0 (delta 0), reused 0 (delta 0)
-    remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-    To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
-     ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-    error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-    failed
-    git-annex: sync: 1 failed
-
-If I disable and re-enable the sync on the server (forcing a sync), I still have
-a conflict locally:
-
-    schmitta@top ~/D/annex (master) [1]> git annex sync
-    commit
-    ok
-    pull mini_archive 
-    ok
-    push mini_archive 
-    Total 0 (delta 0), reused 0 (delta 0)
-    remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-    To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
-     ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-    error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-    failed
-    git-annex: sync: 1 failed
-
-It only get solved by doing a merge on the server:
-
-    schmitta@mini ~/a/archive> git annex merge
-    merge git-annex (merging refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/git-annex into git-annex...)
-    (Recording state in git...)
-    ok
-
-    schmitta@top ~/D/annex (master) [1]> git annex sync
-    commit
-    ok
-    pull mini_archive 
-    remote: Counting objects: 13, done.
-    remote: Compressing objects: 100% (5/5), done.
-    remote: Total 5 (delta 3), reused 0 (delta 0)
-    Unpacking objects: 100% (5/5), done.
-    From ssh://git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive
-       cb7f6c3..d177e1a  git-annex  -> mini_archive/git-annex
-    ok
-    (merging mini_archive/git-annex into git-annex...)
-
-
-### What version of git-annex are you using? On what operating system?
-
-Current version available on cabal:
-
-    schmitta@top ~/D/annex (master)> git annex version
-    git-annex version: 4.20131002
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-    schmitta@mini ~/a/archive> git annex version
-    git-annex version: 4.20131002
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-
-### Please provide any additional information below.
-
-Here is daemon.log. It mentions another repo which is an external
-hard drive not plugged it at the moment. I'm skipping the file transmission
-(...).
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[2013-10-23 14:02:05 CEST] main: starting assistant version 4.20131002
-[2013-10-23 14:02:05 CEST] TransferScanner: Syncing with hole, mini_archive 
-Already up-to-date.
-fatal: '/Volumes/hole/annex/' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-
-(scanning...) [2013-10-23 14:02:06 CEST] Watcher: Performing startup scan
-Already up-to-date.
-Already up-to-date.
-fatal: '/Volumes/hole/annex/' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
- ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-fatal: '/Volumes/hole/annex/' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-fatal: '/Volumes/hole/annex/' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
- ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-fatal: '/Volumes/hole/annex/' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-[2013-10-23 14:02:10 CEST] Committer: Committing changes to git
-[2013-10-23 14:02:10 CEST] Pusher: Syncing with mini_archive 
-
-
-(Recording state in git...)
-(started...) To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
-   8f39d4c..cb7f6c3  git-annex -> refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/git-annex
-   a5b002b..dde2626  master -> refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/master
-remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
- ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
- ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-Everything up-to-date
-(gpg) 
-
-
-SHA256E-s608232213--d4d6e02e651b1d265ff1c041ee8e8c23db9d880140816d62b8cc82cee4db3a54.mp4
-
-...
-
-sent 608306626 bytes  received 42 bytes  5133389.60 bytes/sec
-total size is 608232213  speedup is 1.00
-[2013-10-23 14:04:13 CEST] Transferrer: Uploaded Icy and F..cDl4Y.mp4
-[2013-10-23 14:04:13 CEST] Pusher: Syncing with mini_archive 
-remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
- ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
- ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
-   cb7f6c3..927cc1c  git-annex -> refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/git-annex
-[2013-10-23 14:05:35 CEST] main: Syncing with mini_archive 
-remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
- ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
- ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/'
-Everything up-to-date
-
-
-# End of transcript or log.
-"""]]
-
-> So, receive.denyNonFastforwards was the problem. It turns out that
-> `git init --bare --shared` sets that by default, and the webapp
-> uses that to create repositories on ssh server. I have made the webapp
-> unset receive.denyNonFastforwards when setting up such a repository.
-> 
-> Also added something to the assistant release notes about this
-> to handle existing repositories. [[done]] --[[Joey]]
diff --git a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment
deleted file mode 100644
index ef2399d81..000000000
--- a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="64.134.31.139"
- subject="comment 1"
- date="2013-10-23T15:21:34Z"
- content="""
-<pre>
-To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/
- ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward)
-</pre>
-
-Since version 4.20130909, git-annex is supposed to have avoided this problem by forcing the push of the git-annex branch. If you run `git annex sync --debug`, you should see:
-
-[2013-10-23 11:12:54 EDT] call: git [\"--git-dir=annex/.git\",\"--work-tree=annex\",\"push\",\"foo\",\"+git-annex:synced/git-annex\",\"master:synced/master\"]
-
-The \"+\" flag before the branch name forces git push to update the remote branch even if it's not a fast-forward.
-
-You should be able to verify if git-annex is doing that, and run the same git push command manually to investigate why it might not be working. I have not seen this problem since putting in that fix, and I saw it before. Perhaps your server has an old or broken version of git that ignores this flag, or some git configuration setting I am not aware of that prevents it from working.
-"""]]
diff --git a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment
deleted file mode 100644
index 44ccfe00b..000000000
--- a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="http://alan.petitepomme.net/"
- nickname="Alan Schmitt"
- subject="comment 2"
- date="2013-10-23T16:21:30Z"
- content="""
-I think I found the problem, after much googling.
-
-The command line you suggest is indeed tried, and rejected by the server.
-
-The answer came from [here](http://stackoverflow.com/questions/253055/how-do-i-push-amended-commit-to-the-remote-git-repo) where it says (speaking of a forced push)
-
-> Even this may not work as git allows remote repositories to refuse non-fastforward pushes at the far end by using the config variable 'receive.denynonfastforwards'.
-
-Indeed this is set in my annex repository. Note that this is a local setting, and that repository was created by the assistant.
-
-I removed this setting, and I can now push. Could the setting of this bit be a bug in the assistant?
-
-In any case, thanks a lot for indicating where to look at.
-"""]]
diff --git a/doc/bugs/In_the_assistant__44___add_some_clarifications_near___34__Add_another_local_repository__34___for_the_case_of_adding_an_existing_repository.mdwn b/doc/bugs/In_the_assistant__44___add_some_clarifications_near___34__Add_another_local_repository__34___for_the_case_of_adding_an_existing_repository.mdwn
deleted file mode 100644
index 0e49bc368..000000000
--- a/doc/bugs/In_the_assistant__44___add_some_clarifications_near___34__Add_another_local_repository__34___for_the_case_of_adding_an_existing_repository.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-
-The difference in consequences of `Add another local repository` in the *git-annex assistant* on an existing repository versus on a new directory are unclear.
-
-### What steps will reproduce the problem?
-
-Going to the "Add another local repository" in the *git-annex assistant* will make you confused if you want to add an existing repository.
-
-### What version of git-annex are you using? On what operating system?
-
-[[!format sh """
-$ git annex version
-git-annex version: 5.20140210-gd99db49
-build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external
-"""]]
-
-Ubuntu 13.04
-
-### Please provide any additional information below.
-
-Ain't nobody here but us chickens.
-
-> Ok, I have removed the reference to "new repository" since it can be
-> a new or an existing repository. The webapp already asks followup
-> questions if the repository exists to make sure nothing confusing
-> happens. [[done]] --[[Joey]]
diff --git a/doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case.mdwn b/doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case.mdwn
deleted file mode 100644
index b9cae0176..000000000
--- a/doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case.mdwn
+++ /dev/null
@@ -1,72 +0,0 @@
-### Please describe the problem.
-When creating a simple "parent" git repo, creating another "child" repo with an annexed file, then adding the child repo as a submodule of the parent, the symlink path of the large file contained by the submodule is incorrect.
-
-
-### What steps will reproduce the problem?
-Here are the exact steps for this simple use case (I have removed unrelated output for brevity, and setting up the repos is error-free):
-
-    # Create "parent" repo
-    $ mkdir parent
-    $ cd parent/
-    $ git init
-    $ touch parent_start
-    $ git add parent_start
-    $ git commit -a -m 'New parent repo'
-    $ cd ../
-    
-    # Create "child" repo
-    $ mkdir child
-    $ cd child/
-    $ git init
-    $ touch child_start
-    $ git add child_start
-    $ git commit -a -m 'New child repo'
-    $ git annex init
-    $ cp ~/Desktop/some_big_file child_big_file
-    $ git annex add child_big_file
-    $ git commit -a -m 'Added big file'
-    $ cd ../
-    
-    # Add "child" repo as a submodule of "parent" repo
-    $ cd parent/
-    $ git submodule add ../child ./submodule
-    $ git commit -m 'Added submodule'
-    
-    # Try to get annexed file
-    $ cd submodule/
-    $ git annex init
-    $ git annex get
-    $ ls ./
-    -rw-r--r--	.git
-    lrwxr-xr-x	child_big_file -> .git/annex/objects/F5/f2/SHA256E-s1117253--ce17632dfd9c61a0a8c1384d25fb3a8a197f8056f224e15fbcad89904a82c5fd/SHA256E-s1117253--ce17632dfd9c61a0a8c1384d25fb3a8a197f8056f224e15fbcad89904a82c5fd
-    -rw-r--r--	child_start
-    
-    # As you can see above, the child_big_file symlink path is incorrect (the ".git/annex/..." location is not a directory, and should instead be "../.git/modules/submodule/annex/...")
-    
-    # Show the actual location of the annexed file
-    $ cd ../
-    $ ls .git/modules/submodule/annex/objects/F5/f2/SHA256E-s1117253--ce17632dfd9c61a0a8c1384d25fb3a8a197f8056f224e15fbcad89904a82c5fd
-    -r--r--r--	SHA256E-s1117253--ce17632dfd9c61a0a8c1384d25fb3a8a197f8056f224e15fbcad89904a82c5fd
-
-
-### What version of git-annex are you using? On what operating system?
-Mac OS X Mountain Lion. git-annex files are from within the downloadable git-annex assistant.
-
-    $ sw_vers -productVersion
-    10.8.5
-    $ git --version
-    git version 1.7.12.4 (Apple Git-37)
-    $ git-annex version
-    git-annex version: 4.20131105-g136b030
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-
-Thanks for your help :)
-
-> This is a duplicate of [[Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path]] [[done]] --[[Joey]]   
diff --git a/doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case/comment_1_73b4dc5f90c8ba5634caee35cd31af1a._comment b/doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case/comment_1_73b4dc5f90c8ba5634caee35cd31af1a._comment
deleted file mode 100644
index d8539041d..000000000
--- a/doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case/comment_1_73b4dc5f90c8ba5634caee35cd31af1a._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="206.74.132.139"
- subject="comment 1"
- date="2014-02-06T16:58:54Z"
- content="""
-Since the symlinks are committed to git, they can only point at one location, which is whereever the .git/annex directory was in the repository where they were created in the first place. You can run `git annex fix` in the submodule and it should correct the links. But then they'll point to the wrong location in the non-submodule clone of the repository.
-
-So, it seems you need to pick whether a given repository will be a submodule or not (and where it will be mounted in the parent repository if so), and stick with that choice. You can't have it both ways. 
-
-I cannot imagine any change to git-annex that could change this limitation. Except perhaps using direct mode everywhere, in which case where the symlinks point internally doesn't really matter..
-
-(<http://myrepos.branchable.com> might be a usable alternative to submodules for you, that does not have this problem.)
-"""]]
diff --git a/doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case/comment_2_e84b93062c82453f18308a82ee270585._comment b/doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case/comment_2_e84b93062c82453f18308a82ee270585._comment
deleted file mode 100644
index 29302f0c1..000000000
--- a/doc/bugs/Incorrect_symlink_path_in_simple_submodule_use_case/comment_2_e84b93062c82453f18308a82ee270585._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmYwE2LrTHAgbco1mEa_y8rGVqX7exIoxc"
- nickname="François"
- subject="Replace the gitdir by a symbolic link"
- date="2014-02-11T08:06:53Z"
- content="""
-chadsgilbert proposed to replace the .git file by a symbolic link:
-
- <http://stackoverflow.com/a/18238326/1531323>
-
-What do you think of this possibility? Is it perennial? Can \"git annex init\" do it automatically?
-
-The [commit message](https://github.com/git/git/commit/69c305178) that introduces the change gives the impression that a symbolic link was a possibility.
-
-Thanks a lot for git annex!
-"""]]
diff --git a/doc/bugs/Incorrect_version_on_64_Standalone_Build.mdwn b/doc/bugs/Incorrect_version_on_64_Standalone_Build.mdwn
deleted file mode 100644
index d0f43f5b2..000000000
--- a/doc/bugs/Incorrect_version_on_64_Standalone_Build.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-    $ wget https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz
-    $ tar xvzf git-annex-standalone-amd64.tar.gz
-    $ cd git-annex.linux
-    $ ./git-annex version
-    git-annex version: 4.20130324
-
-Shouldn't that be `4.20130405`?
-
-The md5sum of the build I downloaded is `aabbb3aa2397be206cae86f33db9eef4`.
-
-> [[done]]; new version will look like eg `4.20130410-gc149c67` --[[Joey]] 
diff --git a/doc/bugs/Incorrect_version_on_64_Standalone_Build/comment_1_1964e4cad33a9f98b2eedbf095e899ff._comment b/doc/bugs/Incorrect_version_on_64_Standalone_Build/comment_1_1964e4cad33a9f98b2eedbf095e899ff._comment
deleted file mode 100644
index 03a39b928..000000000
--- a/doc/bugs/Incorrect_version_on_64_Standalone_Build/comment_1_1964e4cad33a9f98b2eedbf095e899ff._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-10T20:38:28Z"
- content="""
-Hmm, I think this is an artifact of my release process. I copy the nightly autobuild to there, and typically do this in the morning, so there are some commits from changes to this wiki. Until I commit a new version to `debian/changelog`, `git annex version` can report wrong information. In particular, in commit c709623ff8e56490bb5802cb53880ae237f9f1d9 I changed the version number from a placeholder 4.20130324 to 4.20130405.
-
-There's a tradeoff between waiting for the next autobuild (only run once a day because the server has other users), taking the time to manually run a build, and getting the new release out to users quickly when I announce it.
-
-I think the thing to do is make it use the date of the *last* commit as the version number for autobuilds, and include the git rev in there too. Then users will know exactly what they've gotten.
-"""]]
diff --git a/doc/bugs/Install_of_git-annex-3.20121112_fails.mdwn b/doc/bugs/Install_of_git-annex-3.20121112_fails.mdwn
deleted file mode 100644
index f4f1c6c7d..000000000
--- a/doc/bugs/Install_of_git-annex-3.20121112_fails.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-What steps will reproduce the problem?
-
-- rm -rf ~/.ghc/ && cabal update && cabal install git-annex --bindir=$HOME/bin
-
-What is the expected output? What do you see instead?
-
-- I would like to have the latest release installed
-
-What version of git-annex are you using? On what operating system?
-
-- git-annex-3.20121112
-- Ubuntu 12.04 LTS
-- The Glorious Glasgow Haskell Compilation System, version 7.4.1
-
-Please provide any additional information below.
-
-I use it heavily on 4 machines since a month and I really like it.
-
-> closing since this is a cabal library problem, and not something that
-> can be fixed by any change to git-annex. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_1_80fc80151d4390bd8a4332f30723962e._comment b/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_1_80fc80151d4390bd8a4332f30723962e._comment
deleted file mode 100644
index b3889eca6..000000000
--- a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_1_80fc80151d4390bd8a4332f30723962e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.252.11.120"
- subject="comment 1"
- date="2012-11-13T17:08:14Z"
- content="""
-You forgot to say how it fails.
-"""]]
diff --git a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_2_2613320a41a74dc757a3277c8c328bd0._comment b/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_2_2613320a41a74dc757a3277c8c328bd0._comment
deleted file mode 100644
index fa2b326e9..000000000
--- a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_2_2613320a41a74dc757a3277c8c328bd0._comment
+++ /dev/null
@@ -1,62 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnldTTAP8PAifJUmqhRar6RAWNWlRcencw"
- nickname="Marco"
- subject="The failure"
- date="2012-11-13T17:24:40Z"
- content="""
-Configuring certificate-1.2.2...
-Building certificate-1.2.2...
-Preprocessing library certificate-1.2.2...
-[1 of 9] Compiling Data.Certificate.KeyRSA ( Data/Certificate/KeyRSA.hs, dist/build/Data/Certificate/KeyRSA.o )
-
-Data/Certificate/KeyRSA.hs:29:27:
-    Constructor `RSA.PrivateKey' does not have field `RSA.private_size'
-    In the expression:
-      RSA.PrivateKey
-        {RSA.private_size = calculate_modulus p_modulus 1,
-         RSA.private_n = p_modulus, RSA.private_d = priv_exp,
-         RSA.private_p = p_p1, RSA.private_q = p_p2,
-         RSA.private_dP = p_exp1, RSA.private_dQ = p_exp2,
-         RSA.private_qinv = p_coef}
-    In an equation for `privkey':
-        privkey
-          = RSA.PrivateKey
-              {RSA.private_size = calculate_modulus p_modulus 1,
-               RSA.private_n = p_modulus, RSA.private_d = priv_exp,
-               RSA.private_p = p_p1, RSA.private_q = p_p2,
-               RSA.private_dP = p_exp1, RSA.private_dQ = p_exp2,
-               RSA.private_qinv = p_coef}
-    In an equation for `parsePrivate':
-        parsePrivate
-          [Start Sequence,
-           IntVal 0,
-           IntVal p_modulus,
-           IntVal pub_exp,
-           IntVal priv_exp,
-           IntVal p_p1,
-           IntVal p_p2,
-           IntVal p_exp1,
-           IntVal p_exp2,
-           IntVal p_coef,
-           End Sequence]
-          = Right (pubkey, privkey)
-          where
-              privkey
-                = RSA.PrivateKey
-                    {RSA.private_size = calculate_modulus p_modulus 1,
-                     RSA.private_n = p_modulus, RSA.private_d = priv_exp,
-                     RSA.private_p = p_p1, RSA.private_q = p_p2,
-                     RSA.private_dP = p_exp1, RSA.private_dQ = p_exp2,
-                     RSA.private_qinv = p_coef}
-              pubkey
-                = RSA.PublicKey
-                    {RSA.public_size = calculate_modulus p_modulus 1,
-                     RSA.public_n = p_modulus, RSA.public_e = pub_exp}
-              calculate_modulus n i
-                = if (2 ^ (i * 8)) > n then i else calculate_modulus n (i + 1)
-cabal: Error: some packages failed to install:
-authenticate-1.3.2 depends on certificate-1.2.2 which failed to install.
-certificate-1.2.2 failed during the building phase. The exception was:
-ExitFailure 1
-git-annex-3.20121112 depends on certificate-1.2.2 which failed to install.
-"""]]
diff --git a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_3_c364764d0c56e8dc3cac276905d99841._comment b/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_3_c364764d0c56e8dc3cac276905d99841._comment
deleted file mode 100644
index e3478d03d..000000000
--- a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_3_c364764d0c56e8dc3cac276905d99841._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.252.11.120"
- subject="comment 3"
- date="2012-11-13T17:54:30Z"
- content="""
-Hmm, the current version of certificate is 1.3.1, and I installed it without trouble just now. I don't know why cabal is installing a much older version there.
-
-In any case, this is not a bug in git annex, but some problem with the library that a library it uses depends on. You can use the pre-built standalone binary until cabal sorts itself out, I suppose.
-"""]]
diff --git a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_4_f1057340dfa978071d3bbc9e2af1e612._comment b/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_4_f1057340dfa978071d3bbc9e2af1e612._comment
deleted file mode 100644
index 2741daacf..000000000
--- a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_4_f1057340dfa978071d3bbc9e2af1e612._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnldTTAP8PAifJUmqhRar6RAWNWlRcencw"
- nickname="Marco"
- subject="Assistant depends on Yesod"
- date="2012-11-13T18:34:19Z"
- content="""
-Thank you Joey. Than I tried a workaround. On one machine I don't need the Webapp.
-
-I was using 
-
-cabal install --only-dependencies -f-Webapp
-cabal configure -f-Webapp
-
-mp/Utility/libdiskfree.o dist/build/git-annex/git-annex-tmp/Utility/libmounts.o ./git-annex.hs
-
-Assistant/Alert.hs:21:8:
-    Could not find module `Yesod'
-    Use -v to see a list of the files searched for.
-"""]]
diff --git a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_5_9007b1a3abd647945604968db19cb841._comment b/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_5_9007b1a3abd647945604968db19cb841._comment
deleted file mode 100644
index 666eef28b..000000000
--- a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_5_9007b1a3abd647945604968db19cb841._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.252.11.120"
- subject="youch!"
- date="2012-11-13T19:37:23Z"
- content="""
-The assistant is indeed supposed to build w/o Yesod. I've fixed that in git!
-"""]]
diff --git a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_6_0bb3ac5375f29ce9d3d0be93879267e3._comment b/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_6_0bb3ac5375f29ce9d3d0be93879267e3._comment
deleted file mode 100644
index 2aaf9cf43..000000000
--- a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_6_0bb3ac5375f29ce9d3d0be93879267e3._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmLB39PC89rfGaA8SwrsnB6tbumezj-aC0"
- nickname="Tobias"
- subject="Bah, i missed this before making my own bug report"
- date="2012-11-13T20:56:50Z"
- content="""
-This line worked for me on ubuntu 12.10: 
-
-cabal install --only-dependencies ./ --constraint=certificate==1.2.2 --constraint=crypto-pubkey-types==0.1.1
-
-"""]]
diff --git a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_7_ae4443b8cd069080d1f77fca16aa8b04._comment b/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_7_ae4443b8cd069080d1f77fca16aa8b04._comment
deleted file mode 100644
index 99124ebe5..000000000
--- a/doc/bugs/Install_of_git-annex-3.20121112_fails/comment_7_ae4443b8cd069080d1f77fca16aa8b04._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnldTTAP8PAifJUmqhRar6RAWNWlRcencw"
- nickname="Marco"
- subject="Works"
- date="2012-11-14T07:01:34Z"
- content="""
-Thanks Joey for fixing this. Now I got a working version.
-
-Btw would it make sense to reference a stable Yesod version in the cabal file? I'm new to the haskell universe so I don't know what problems would come up with it.
-"""]]
diff --git a/doc/bugs/Internal_Server_Error_when_adding_an_uncrypted_box.com_repo_after_deleted_an_encrypted_one..mdwn b/doc/bugs/Internal_Server_Error_when_adding_an_uncrypted_box.com_repo_after_deleted_an_encrypted_one..mdwn
deleted file mode 100644
index 9a838b58f..000000000
--- a/doc/bugs/Internal_Server_Error_when_adding_an_uncrypted_box.com_repo_after_deleted_an_encrypted_one..mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-I got the following error message
-
-    Internal Server Error
-    Cannot change encryption type of existing remote.
-
-after deleted my encrypted box.com remote and tried to add the same box.com account as an uncrypted remote.
-
-### What steps will reproduce the problem?
-* Add a box.com remote with encryption.
-* Delete the remote.
-* Add with the same box.com account a remote without encryption.
-
-### What version of git-annex are you using? On what operating system?
-* 2013.07.09 release
-* Linux 3.9.9-1-ARCH x86_64
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> fixed this [[done]] --[[Joey]] 
diff --git a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X.mdwn b/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X.mdwn
deleted file mode 100644
index 575a63684..000000000
--- a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-What steps will reproduce the problem?
-
-* Start with a clean setup.
-* Allow webapp to start; use it to create annex in ~/Documents/annex That works.
-* Go to add remote repo. Removable drive.
-* Select "/Volumes/G-DRIVE slim". Click next.
-
-What is the expected output? What do you see instead?
-Expected is something like "done". What I see is
-
-Internal Server Error
-
-git config [Param "annex.uuid",Param "6898F314-7817-4CD5-B1C3-588C55522A3B"] failed
-
-What version of git-annex are you using? On what operating system?
-
-git-annex version 3.20130107, OS X Mountain Lion. No MacPorts/homebrew/fink installed. gcc / git are installed.
-
-Please provide any additional information below.
-
-Maybe something to do with the drive name having spaces? "/Volumes/git-annex" worked fine.
-
-> Good thought in the comment. I was able to reproduce the failure
-> if the removable drive already had an "annex" directory that was not
-> a git repo. I've made it handle this case. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_1_b2ef077d87a9da624f20649c21401b5b._comment b/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_1_b2ef077d87a9da624f20649c21401b5b._comment
deleted file mode 100644
index f46292c19..000000000
--- a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_1_b2ef077d87a9da624f20649c21401b5b._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 1"
- date="2013-01-14T16:07:18Z"
- content="""
-Spaces in the name is a good guess, but does not seem to cause the problem. I just successfully set up a USB drive that has spaces in the name. (Also, git-annex is carefully coded to avoid such problems..)
-
-It seems that the repository is created, but then running `git config` in it fails for some reason. One thing you could do is look at `~/Documents/annex/.git/annex/daemon.log`. It should have any error message output by the command.
-
-Or, you could try, in a shell:
-
-cd \"/Volumes/G-DRIVE slim/annex\"
-git config annex.uuid 6898F314-7817-4CD5-B1C3-588C55522A3B
-
-And see how that is failing.
-"""]]
diff --git a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_2_ef849e25b0264808bff800d9d3836119._comment b/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_2_ef849e25b0264808bff800d9d3836119._comment
deleted file mode 100644
index ec7867653..000000000
--- a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_2_ef849e25b0264808bff800d9d3836119._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="arafel"
- ip="94.174.218.177"
- subject="comment 2"
- date="2013-01-14T20:50:50Z"
- content="""
-It did seem unlikely that you hadn't tested that. :-)
-
-Oddly, there doesn't seem to be a daemon.log file in that directory. I don't have the drive handy to test at the moment - when I do I'll try the commands you suggest and see what the output is.
-"""]]
diff --git a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_3_ae3cbd0eb69cbeb9b349e0060d056d43._comment b/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_3_ae3cbd0eb69cbeb9b349e0060d056d43._comment
deleted file mode 100644
index f2e5394ce..000000000
--- a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_3_ae3cbd0eb69cbeb9b349e0060d056d43._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="arafel"
- ip="94.174.218.177"
- subject="comment 3"
- date="2013-01-14T21:19:12Z"
- content="""
-Pauls-MacBook-Pro:annex Paul$ cd /Volumes/G-DRIVE\ slim/annex/
-
-Pauls-MacBook-Pro:annex Paul$ git config annex.uuid 6898F314-7817-4CD5-B1C3-588C55522A3B
-
-error: could not lock config file .git/config: No such file or directory
-
-Pauls-MacBook-Pro:annex Paul$ ls -a
-
-.	..
-
-Looks like it created the directory but never got as far as 'git init'. Is it safe to just run that command, and will that (followed by the config) be enough? Or is there more to it than that? e.g. creating the remotes
-"""]]
diff --git a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_4_0ff2897805928b14829b7b369a3aed91._comment b/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_4_0ff2897805928b14829b7b369a3aed91._comment
deleted file mode 100644
index 7e6b621c8..000000000
--- a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_4_0ff2897805928b14829b7b369a3aed91._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 4"
- date="2013-01-14T22:54:30Z"
- content="""
-Can you do this:
-
-* `rmdir /Volumes/G-DRIVE\ slim/annex/`
-
-* Stop any git-annex assistant you have running. 
-
-* At the console, run \"git annex webapp\", and reproduce the bug again. When it fails you should see some error message at the console where you started it.
-
-(If you're using the git-annex.app built for OSX, you should instead run the `git-annex-webapp` script included in the app.)
-"""]]
diff --git a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_5_414a45573aeb5201f4d80433955669d5._comment b/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_5_414a45573aeb5201f4d80433955669d5._comment
deleted file mode 100644
index f5423f04f..000000000
--- a/doc/bugs/Internal_server_error_adding_USB_drive_on_OS_X/comment_5_414a45573aeb5201f4d80433955669d5._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="arafel"
- ip="94.174.218.177"
- subject="comment 5"
- date="2013-01-14T23:22:19Z"
- content="""
-Hm. After removing the directory, I can't get the problem to happen. I've tried both running the webapp from the CLI, and the git-annex app from Spotlight, and it works.
-
-A thought - does annex check for the existence of .git in the target folder, or does it just assume (if the folder exists) that it's been set up with git? That's the only thing I can think of. From this experience it seems that would be a worthwhile check if it doesn't already do it.
-
-Other than that we may just have to close the bug as unreproducible. I'm not sure what happened there; I'm not aware of doing anything differently the other times. Apologies for wasting your time!
-"""]]
diff --git a/doc/bugs/Interrupted_switch_to_direct_mode_can_cause_all_following_switches_to_fail.mdwn b/doc/bugs/Interrupted_switch_to_direct_mode_can_cause_all_following_switches_to_fail.mdwn
deleted file mode 100644
index 432c72083..000000000
--- a/doc/bugs/Interrupted_switch_to_direct_mode_can_cause_all_following_switches_to_fail.mdwn
+++ /dev/null
@@ -1,50 +0,0 @@
-### What steps will reproduce the problem?
-
-How to reproduce:
-
-1. Check that the files involved are not available in the local repository.
-2. Force a switch to direct mode to fail, for example, due to a 'exotic' filename
-(first bug).
-3. Solve that problem.
-4. Make another switch to direct mode, but call that command in a subdirectory of
-the git-tree. Which will because some annexed file does not exists (second bug).
-Note: all subsequent switches to direct mode will now fail, no matter where started.
-
-
-Example:
-
-mkdir test1 test2 && cd test1 && git init . && git annex init  
-mkdir umlaut something\ else  
-date > umlaut/this_has_a_$'\201'  
-date > something\ else/problem  
-git annex add .  
-git commit -m "Init"  
-cd ../test2/  
-
-git clone ../test1/ . && git annex init  
-git annex move --from origin .  
-
-cd ../test1/  
-git annex direct  #aborts with: commitBuffer: invalid argument (invalid character)  
-cd umlaut  
-git mv this_has_a_$'\201' this_has_a_o  
-git commit -m "fix"  
-git annex direct # fails with getSymbolicLinkStatus: does not exist (No such file or directory)  
-
-### What is the expected output? What do you see instead?
-
-Expected is a repository switched to direct mode.
-The result is a repository which can't be switched to direct mode.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 3.20130114
-OS: Arch Linux (3.7.2-2-ck)
-
-### Please provide any additional information below.
-
-The second bug seams to be very specific about folder- and/or filename.
-I believe that it has something to do with the space in the foldername.
-
-> Fixed both bugs. You should be able to upgrade git-annex and re-run the command
-> and end up with a working direct-mode repository. [[done]] --[[Joey]] 
diff --git a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn b/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn
deleted file mode 100644
index f0809c568..000000000
--- a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-What steps will reproduce the problem?
-
-    $ git annex -j sync | json_reformat
-
-What is the expected output? What do you see instead?
-
-Expecting valid JSON, instead this happens:
-
-    $ git annex -j sync | json_reformat
-    lexical error: invalid char in json text.
-              {"command":"commit","file":""# On branch master nothing to c
-                         (right here) ------^
-    $
-
-
-What version of git-annex are you using? On what operating system?
-
-Newest standalone (3.20121126), Linux i386. The "json_reformat" program is from the "yajl-tools" .deb package.
-
-> [[done]]; I've updated the --json documentation to note that it only
-> works with some query commands. --[[Joey]] 
diff --git a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_1_380a49b3c132f9f529729a1cb5a69621._comment b/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_1_380a49b3c132f9f529729a1cb5a69621._comment
deleted file mode 100644
index d1ad05842..000000000
--- a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_1_380a49b3c132f9f529729a1cb5a69621._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.6.49"
- subject="comment 1"
- date="2012-11-27T21:13:08Z"
- content="""
-Yeah, so git-annex has --json as a option available to any command, but the set of commands where it's actually useful is rather smaller, and certainly does not include this one. In general there are quite a lot of places where third-party program output is allowed to show through to provide necessary progress or debugging output, and that of course makes the json mode invalid.
-"""]]
diff --git a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_2_282f5f89fb4a46e1fad0980e0b2994a0._comment b/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_2_282f5f89fb4a46e1fad0980e0b2994a0._comment
deleted file mode 100644
index b7b4d786e..000000000
--- a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_2_282f5f89fb4a46e1fad0980e0b2994a0._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://sunny256.sunbase.org/"
- nickname="sunny256"
- subject="comment 2"
- date="2012-11-27T21:30:48Z"
- content="""
-Yep, because of that I was in doubt if I should report it as a bug. Maybe it could be closed, as it's not a bug in git-annex, but git output leaking into the JSON. If there's not an easy way for git-annex to encapsulate the output or redirect the git output to stderr.
-"""]]
diff --git a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_3_7ff98958146b7f6396226bdd878ec86e._comment b/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_3_7ff98958146b7f6396226bdd878ec86e._comment
deleted file mode 100644
index e3b27dd0e..000000000
--- a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_3_7ff98958146b7f6396226bdd878ec86e._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.6.49"
- subject="comment 3"
- date="2012-11-27T21:32:26Z"
- content="""
-I'd rather not abuse stderr.
-
-Do you have an actual use case for the json output for git annex sync? If there's a good one, the git output could be suppressed.
-"""]]
diff --git a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_4_f9e460a09e7e5f53c16c20ded2649201._comment b/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_4_f9e460a09e7e5f53c16c20ded2649201._comment
deleted file mode 100644
index d773ef2c7..000000000
--- a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_4_f9e460a09e7e5f53c16c20ded2649201._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://sunny256.sunbase.org/"
- nickname="sunny256"
- subject="comment 4"
- date="2012-11-27T21:40:05Z"
- content="""
-Actually not for the sync command, as I don't parse it in any scripts. Just meant as a heads-up, and not an especially important. Feel free to close it. :)
-"""]]
diff --git a/doc/bugs/Jabber__47__xmpp_not_supported_on_Debian_Wheezy_backport.mdwn b/doc/bugs/Jabber__47__xmpp_not_supported_on_Debian_Wheezy_backport.mdwn
deleted file mode 100644
index 0ea1a96a9..000000000
--- a/doc/bugs/Jabber__47__xmpp_not_supported_on_Debian_Wheezy_backport.mdwn
+++ /dev/null
@@ -1,12 +0,0 @@
-### Please describe the problem.
-I've installed Git-annex via the backport, everything looks fine. But when I go to Configuration>Configure jabber account I've got this message :
-
-[[!format sh """
- Jabber not supported
- This build of git-annex does not support Jabber. Sorry !
-"""]]
-
-### What version of git-annex are you using? On what operating system?
-5.20140117~bpo70+1 and Debian Wheezy with lxde
-
-> Build dependency problem. Fixed and backport updated. [[done]] --[[Joey]]
diff --git a/doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind.mdwn b/doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind.mdwn
deleted file mode 100644
index 12d1d7719..000000000
--- a/doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind.mdwn
+++ /dev/null
@@ -1,38 +0,0 @@
-### Please describe the problem.
-
-If the assistant daemon is killed, ssh mux sessions are left behind. Incidentally there may be a better way to stop the assistant daemon besides "killall git-annex" but I haven't found it in the docs.
-
-### What steps will reproduce the problem?
-
-[[!format sh """
-$ ps aux | grep mux
-$ git-annex assistant
-$ date > fromwintermute # Just causing a change that needs to be pushed, any will do
-$ ps aux | grep mux
-pedrocr  32665  0.0  0.0   6396   948 ?        Ss   11:06   0:00 ssh: /home/pedrocr/testsync/.git/annex/ssh/golias.git-annex [mux]
-$ killall git-annex
-$ ps aux | grep mux
-pedrocr  32665  0.0  0.0   6396   948 ?        Ss   11:06   0:00 ssh: /home/pedrocr/testsync/.git/annex/ssh/golias.git-annex [mux]
-"""]]
-
-### What version of git-annex are you using? On what operating system?
-
-[[!format sh """
-$ git annex version
-git-annex version: 4.20130516.1
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-local repository version: 4
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-$ lsb_release -a
-No LSB modules are available.
-Distributor ID:	Ubuntu
-Description:	Ubuntu 12.04.2 LTS
-Release:	12.04
-Codename:	precise
-"""]]
-
-
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind/comment_1_17879b98a5e79ace03b543064751e46e._comment b/doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind/comment_1_17879b98a5e79ace03b543064751e46e._comment
deleted file mode 100644
index 17c91ca99..000000000
--- a/doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind/comment_1_17879b98a5e79ace03b543064751e46e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-29T15:36:48Z"
- content="""
-There is a --stop option that can be used to stop the assistant. It will clean up ssh sessions. git-annex also automatically cleans up stale ssh sessions whenever it starts a new one.
-"""]]
diff --git a/doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind/comment_2_2dc877e281750004b16619ea7b931160._comment b/doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind/comment_2_2dc877e281750004b16619ea7b931160._comment
deleted file mode 100644
index 7c39be61b..000000000
--- a/doc/bugs/Killing_the_assistant_daemon_leaves_ssh_mux_sessions_behind/comment_2_2dc877e281750004b16619ea7b931160._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkx5V3MTbzCXS3J7Mn9FEq8M9bPPYMkAHY"
- nickname="Pedro"
- subject="comment 2"
- date="2013-05-29T18:08:51Z"
- content="""
-I see the --stop option in the manpage now, it's under watch and not assistant, so that's why I missed it. I had a problem with the mux sessions not being cleaned up when I changed the remote's hostname. Only after killing old mux's and restarting the assistant did I get it to sync properly.
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss.mdwn b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss.mdwn
deleted file mode 100644
index 2629a7d56..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss.mdwn
+++ /dev/null
@@ -1,57 +0,0 @@
-## What steps will reproduce the problem?
-
-Take a large sub-directory in a repository (e.g. `ccash`) with some files within,
-
-     $ tar -xzf ccash.tar.gz
-     $ du -sh ccash
-     59M	ccash
-     $ ls -l ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar 
-     -rw-r--r-- 1 dietz dietz   1748 Jul 27  2011 ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java
-     -rw-r--r-- 1 dietz dietz 313898 May 22 18:36 ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar
-
-Annex it,
-
-     $ git annex add ccash
-     ...
-     $ ls -l ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar 
-     lrwxrwxrwx 1 dietz dietz 215 Jul 27  2011 ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java -> ../../../../../../../../../../../.git/annex/objects/mv/zf/SHA256-s1748--5c0d1cbf104214b6d0ab85c53a85cadb975ec208f42a7b33a76d85e175352486/SHA256-s1748--5c0d1cbf104214b6d0ab85c53a85cadb975ec208f42a7b33a76d85e175352486
-     lrwxrwxrwx 1 dietz dietz 210 Jul 27  2011 ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar -> ../../../../../../../../.git/annex/objects/8G/gQ/SHA256-s313898--593552ffea3c5823c6602478b5002a7c525fd904a3c44f1abe4065c22edfac73/SHA256-s313898--593552ffea3c5823c6602478b5002a7c525fd904a3c44f1abe4065c22edfac73
-
-Unannex it (before or after committing),
-
-     $ git annex unannex ccash
-
-Note that some fraction of the files will still be symbolic links, now pointing to non-existent files. This data has apparently been lost forever.
-
-     $ ls -l ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar 
-     -rw-r--r-- 1 dietz dietz 1748 Jul 27  2011 ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java
-     lrwxrwxrwx 1 dietz dietz  210 Jul 27  2011 ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar -> ../../../../../../../../.git/annex/objects/8G/gQ/SHA256-s313898--593552ffea3c5823c6602478b5002a7c525fd904a3c44f1abe4065c22edfac73/SHA256-s313898--593552ffea3c5823c6602478b5002a7c525fd904a3c44f1abe4065c22edfac73
-
-It is unclear why some files are affected while others are not. That being said, unannexing small numbers of files at a time appears to avoid the issue,
-
-     $ tar -zxf ccash.tar.gz
-     $ git annex add ccash
-     $ ls -l ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar 
-     lrwxrwxrwx 1 dietz dietz 215 Jul 27  2011 ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java -> ../../../../../../../../../../../.git/annex/objects/mv/zf/SHA256-s1748--5c0d1cbf104214b6d0ab85c53a85cadb975ec208f42a7b33a76d85e175352486/SHA256-s1748--5c0d1cbf104214b6d0ab85c53a85cadb975ec208f42a7b33a76d85e175352486
-     lrwxrwxrwx 1 dietz dietz 210 Jul 27  2011 ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar -> ../../../../../../../../.git/annex/objects/8G/gQ/SHA256-s313898--593552ffea3c5823c6602478b5002a7c525fd904a3c44f1abe4065c22edfac73/SHA256-s313898--593552ffea3c5823c6602478b5002a7c525fd904a3c44f1abe4065c22edfac73
-     $ git annex unannex ccash/trunk/DataProvider/WebContent/WEB-INF
-     ...
-     $ ls -l ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar 
-     lrwxrwxrwx 1 dietz dietz    215 Jul 27  2011 ccash/trunk/annotationinterface/src/edu/byu/nlp/annotationinterface/java/BasicAnnotation.java -> ../../../../../../../../../../../.git/annex/objects/mv/zf/SHA256-s1748--5c0d1cbf104214b6d0ab85c53a85cadb975ec208f42a7b33a76d85e175352486/SHA256-s1748--5c0d1cbf104214b6d0ab85c53a85cadb975ec208f42a7b33a76d85e175352486
-     -rw-r--r-- 1 dietz dietz 313898 Jul 27  2011 ccash/trunk/DataProvider/WebContent/WEB-INF/lib/dom4j.jar
-
-For this reason, it seems likely this is due to some sort of race condition.
-
-
-## What version of git-annex are you using? On what operating system?
-
-This is on Ubuntu 12.04 with git-annex revision a1e2bc4.
-
-
-> There was no good soluton to this, so I picked a bad one that 
-> will not have users complainging git-annex ate their data.
-> They will complain that `git annex unannex` is slow since it now copies
-> the file, and  perhaps instead use --fast, and hopefully avoid destroying
-> their own data by editing the resulting hard links.
-> 
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_10_52364dc5b1b43b51748453d1896e35c6._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_10_52364dc5b1b43b51748453d1896e35c6._comment
deleted file mode 100644
index c0b286a2b..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_10_52364dc5b1b43b51748453d1896e35c6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmVV_nBwlsyCv53BXoJt8YpCX_wZPfzpyo"
- nickname="Peter"
- subject="Progress"
- date="2013-10-10T01:17:08Z"
- content="""
-Is there any type of script / tool / patch which does the --fast but with a copy instead of only a hard link?  Can someone point me towards how I'm supposed to do this?  I'm a technical user, however I don't really fancy having try to go learn the source code of git-annex to fix this really bad flaw :-/ 
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_11_99b4db1841f8630a9c5efd08910e87a3._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_11_99b4db1841f8630a9c5efd08910e87a3._comment
deleted file mode 100644
index 4e55bd020..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_11_99b4db1841f8630a9c5efd08910e87a3._comment
+++ /dev/null
@@ -1,104 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmVV_nBwlsyCv53BXoJt8YpCX_wZPfzpyo"
- nickname="Peter"
- subject="Productive Annoyance"
- date="2013-10-10T04:30:47Z"
- content="""
-Ok, so I'm annoyed by this enough (and desperate enough to want to get my data back) that I wrote up a few scripts to help with this.  I make no claims regarding how well these will work, but they seem to work with some minimal testing on a Fedora 17 machine.
-
-READ THROUGH THESE SCRIPTS BEFORE RUNNING THEM TO MAKE SURE YOU ARE OK WITH WHAT THEY ARE DOING!!!
-
-First, a script to create a bad git-annex: one with missing files (with a few corner case names) after a git unannex. Specify the directory you'd like to make the annex at the top of the file.  ALL CONTENTS OF THIS DIRECTORY WILL BE REMOVED!!! 
-
-	#!/bin/bash
-
-	#This is the folder you'd like to create and unannex
-	FOLDERTOUNANNEX='/tmp/badAnnex'
-
-	pushd .
-
-	if [ ! -d \"$FOLDERTOUNANNEX\" ] ; then
-		mkdir \"$FOLDERTOUNANNEX\"
-	fi
-
-	cd \"$FOLDERTOUNANNEX\"
-
-	rm -rf *
-
-	mkdir subdir
-	echo \"hi\" > 1one.txt
-	echo \"hi\" > 2two.txt
-	echo \"hi\" > \"3thr re ee.boo\"
-	echo \"hi\" > \"4f o u r.boo\"
-	echo \"hi\" > 5
-	echo \"hi\" > \"6\"
-	echo \"hi\" > \"subdir/7\"
-	echo \"hi\" > \"subdir/8.cat\"
-	echo \"hi\" > \"subdir/9.cat\"
-
-	echo \"* annex.backend=SHA512E\" > .gitattributes
-
-	chmod g-r 5 6
-	chmod o-r 6
-
-	ls -la
-
-	git init
-	git annex init \"stupid\"
-	git annex add *
-	ls -la
-	git annex unannex *
-	ls -la
-
-	popd
-
-
-Then, a script to recover the files left missing by the above script.  Note this might be very slow as it has to generate SHA512 hashes for all the files in your annex.  Again, change the paths at the top of this file to work in your environment:
-
-	#!/bin/bash
-
-	#Set this to some place outside your annex, where we can store our hashes while we search for them
-	#It will be fastest if this is on a different physical disk than the annexed folder
-	#You can manually delete the file afterwards
-	HASHFILE='/backup3/tmp.sha'
-	#This is the folder you'd like to unannex
-	FOLDERTOUNANNEX='/tmp/badAnnex'
-
-
-
-
-	HASHLEN=128
-
-	pushd .
-	cd \"$FOLDERTOUNANNEX\"
-
-	find \"$FOLDERTOUNANNEX\" ! -path '*.git*' -exec sha512sum \{\} \; > \"$HASHFILE\"
-
-	find -L \"$FOLDERTOUNANNEX\" -type l | while read BROKENFILE; do
-		POINTSTO=`file \"$BROKENFILE\" | sed -r 's/^.*broken symbolic link to .(.*).$/\1/g'`
-		
-		HASH=`echo \"$POINTSTO\" | sed -r \"s/^.*--([^-\/.]{$HASHLEN}).*$/\1/g\"`
-
-		EXT=`echo \"$POINTSTO\" | sed -r \"s/^.*--[^-\/.]{$HASHLEN}(.[^.]+)?$/\1/g\"`
-		
-		echo \"-\"
-		echo \"FILE:$BROKENFILE\"
-		echo \"POINTSTO:$POINTSTO\"
-		echo \"HASH:$HASH\"
-		echo \"EXT:$EXT\"
-		
-		SOURCEFILE=`grep $HASH $HASHFILE | grep -m 1 \"$EXT\" | sed -r \"s/^.{$HASHLEN}  (.*)$/\1/g\"`
-		
-		echo \"SOURCEFILE:$SOURCEFILE\"
-		if [ -f \"$SOURCEFILE\" ];
-		then
-			cp --backup --suffix=\"~GIT_ANNEX_IS_DANGEROUS~\" -a \"$SOURCEFILE\" \"$BROKENFILE\"
-		else
-			echo \"ERROR: Cant find sourcefile\"
-		fi
-	done;
-
-	popd
-
-I have not yet run this repair script on my rather large broken annex.  I cannot seem to figure out how to restore file ownership and permissions which seem to have been lost when the second file is just linked to the matching previously annexed file (note: this is visible after \"fixing\" the bad annex created by the first script above in that after \"fixing\" file \"6\" is readable by other, whereas originally he was NOT readable by other.  The permissions of 6 have been copied from 5.)  Any thoughts or improvements on this are appreciated. 
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_1_fbb410a54bb0bd82d0953ef58a88600e._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_1_fbb410a54bb0bd82d0953ef58a88600e._comment
deleted file mode 100644
index 14172a3e5..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_1_fbb410a54bb0bd82d0953ef58a88600e._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl0"
- nickname="Ben"
- subject="comment 1"
- date="2012-09-06T02:28:00Z"
- content="""
-
-Here is a quick script which reproduces the issue on another Ubuntu 12.04 machine,
-
-     mkdir hi
-     cd hi
-     wget \"http://downloads.sourceforge.net/project/free-cad/FreeCAD%20Source/freecad-0.11.3729.tar.gz\"
-
-     git init
-     git annex init
-     tar -zxf freecad-0.11.3729.tar.gz 
-     git annex add FreeCAD-0.11.3729
-     git annex unannex FreeCAD-0.11.3729
-     echo \"The following links are broken:\"
-     find -L . -type l
-     
-This results in dozens of dead symlinks.
-
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_2_8007c9ba42a951a4426255ec3c37d961._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_2_8007c9ba42a951a4426255ec3c37d961._comment
deleted file mode 100644
index e1f600d88..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_2_8007c9ba42a951a4426255ec3c37d961._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.236"
- subject="comment 2"
- date="2012-09-06T14:55:58Z"
- content="""
-What's going on here is you have multiple files with the same content, so the symlinks point to the same annexed file. When unannex processes the first symlink, it moves the annexed file to replace it. This breaks the other symlink that pointed to it. Notice that if you then re-add the file to the annex, the broken symlink automatically gets fixed -- there's no actual data loss going on here.
-
-This problem can be avoided by using `git annex unannex --fast`, which makes hardlinks to the annexed file.
-But then you are also left with the hard links in `.git/annex/objects`.. `git annex unused` can find and remove them. 
-
-It may make sense to make the current \"--fast\" behavior the default for unannex..
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_3_73ecd4cb8ee58a8dfe7cab0e893dbe5b._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_3_73ecd4cb8ee58a8dfe7cab0e893dbe5b._comment
deleted file mode 100644
index 2a799fac0..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_3_73ecd4cb8ee58a8dfe7cab0e893dbe5b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl0"
- nickname="Ben"
- subject="comment 3"
- date="2012-09-06T16:04:42Z"
- content="""
-Frankly, even the --fast behavior has an element of surprise to it. For example, one might have two files with identical content. Upon annexing and unannex they suddenly become a hard link to the same file, correct? If this is the case, changes to one will result in changes to the other. I would consider this a very nasty sort of surprise.
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_4_e8a10886a564f35414c30a04335d9d32._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_4_e8a10886a564f35414c30a04335d9d32._comment
deleted file mode 100644
index 72b4c5c7f..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_4_e8a10886a564f35414c30a04335d9d32._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.30"
- subject="comment 4"
- date="2012-09-09T16:53:35Z"
- content="""
-Perhaps the solution is to make --fast the default and to make it copy files when the content in the annex already has a hard link to it.
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_5_6a318edfe45c80343d017dc7b4837acb._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_5_6a318edfe45c80343d017dc7b4837acb._comment
deleted file mode 100644
index fbc30f17b..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_5_6a318edfe45c80343d017dc7b4837acb._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl0"
- nickname="Ben"
- subject="comment 5"
- date="2012-09-09T20:47:04Z"
- content="""
-That sounds far more reasonable.
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_6_f7a1d9f9d40aff531d873a95d2196edd._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_6_f7a1d9f9d40aff531d873a95d2196edd._comment
deleted file mode 100644
index 295411d25..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_6_f7a1d9f9d40aff531d873a95d2196edd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl0"
- nickname="Ben"
- subject="comment 6"
- date="2012-09-19T23:32:35Z"
- content="""
-Has any progress been made here? While this issue may not result in data loss, the behavior documented in this bug is certainly surprising and does not instill confidence in new users.
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_7_1724ffdf986301bf37ef7a6d16b6ea8a._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_7_1724ffdf986301bf37ef7a6d16b6ea8a._comment
deleted file mode 100644
index fd235321a..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_7_1724ffdf986301bf37ef7a6d16b6ea8a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.14.141"
- subject="comment 7"
- date="2012-09-23T18:02:45Z"
- content="""
-If unannex makes the file a hard link to the annexed content, it will be mode 444 or so. But if the user changes the permissions and modifys it, that will corrupt the content still in the annex!
-
-So the current --fast behavior seems no worse than the proposed behavior. And it's not at all clear to me that this would be a better default behavior for unannex than the current behavior, which at least ensures that data left in the annex (and referred to by another annexed file) cannot be corrupted.
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_8_5470e2f50e6506139ecb1b342371c509._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_8_5470e2f50e6506139ecb1b342371c509._comment
deleted file mode 100644
index 7ac71b6b8..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_8_5470e2f50e6506139ecb1b342371c509._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="comment 8"
- date="2013-07-31T14:17:19Z"
- content="""
-Filenames are the index which users use to find their data.
-
-Leaving a broken symlink may not result in technical data loss, but can quite possibly result in the user being unable to find the data which was referenced by that filename (symlink), so in that case that data _is_ lost, in the true sense of the word (the user cannot find it). Telling the user their data exists _somewhere_ is not actually making the situation any better.
-"""]]
diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_9_e53148a9efa061a825f668a9492182f7._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_9_e53148a9efa061a825f668a9492182f7._comment
deleted file mode 100644
index 74aaa1e56..000000000
--- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_9_e53148a9efa061a825f668a9492182f7._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 9"
- date="2013-08-30T05:59:28Z"
- content="""
-I'll chime in and say that the non-fast behavior being the default seems wrong, and making hard-link invisibly seems wrong.  What Joey proposed -- copying a file if there are multiple hard-links -- seems like the right solution.
-
-Just recently I tried to unannex a large repository and was bitten by now-dangling symlinks to files that I couldn't locate anymore.  The fact is that the current unannex operation is too dangerous to be useful.
-"""]]
diff --git a/doc/bugs/Last_two_versions_didn__39__t_show_up_on_hackage.mdwn b/doc/bugs/Last_two_versions_didn__39__t_show_up_on_hackage.mdwn
deleted file mode 100644
index f1d4ae2b2..000000000
--- a/doc/bugs/Last_two_versions_didn__39__t_show_up_on_hackage.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-### Please describe the problem.
-I don't know how the packages at hackage are managed, but the last version there is 4.20130601 while in the mean time there have been two other releases.
-
-### What steps will reproduce the problem?
-Check [[http://hackage.haskell.org/packages/archive/git-annex/]]
-
-> Thanks for reporting. Turns out that hackage was rejecting
-> it since it doesn't know about the OS name for the hurd. Since I 
-> am not sure I have the right name either, I have removed those bits
-> and re-uploaded.
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Last_two_versions_didn__39__t_show_up_on_hackage/comment_1_74b56dea2100450e322e726bb55bb310._comment b/doc/bugs/Last_two_versions_didn__39__t_show_up_on_hackage/comment_1_74b56dea2100450e322e726bb55bb310._comment
deleted file mode 100644
index bbb2231dc..000000000
--- a/doc/bugs/Last_two_versions_didn__39__t_show_up_on_hackage/comment_1_74b56dea2100450e322e726bb55bb310._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://dzsino.myopenid.com/"
- nickname="dzsino"
- subject="me2"
- date="2013-06-30T13:16:38Z"
- content="""
-i'm using cabal on my mac to stay on the bleeding edge, but it still picks up version 0601, which it cannot install with yesod-1.1.9.3 failing to build (so it's not a git-annex problem). I hope a new release would fix that too..
-"""]]
diff --git a/doc/bugs/Local_files_not_found.mdwn b/doc/bugs/Local_files_not_found.mdwn
deleted file mode 100644
index b2843e35f..000000000
--- a/doc/bugs/Local_files_not_found.mdwn
+++ /dev/null
@@ -1,50 +0,0 @@
-### Please describe the problem.
-
-I have a git annex repo which cannot find the files with whereis, even though the files and contents are there. I have changed ownership of all the files. I am not sure, but I think that is when the problem was introduced. The current user that is invoking git annex owns and can access all files in the repository/annex)
-
-Creating a new repository from scratch works just fine.
-
-
-### What steps will reproduce the problem?
-
-    # (in my current, somehow corrupt annex)
-    $ echo hello > testfile
-    $ git annex add testfile
-    add testfile (checksum...) ok
-    (Recording state in git...)
-    $ git commit -am testfile
-    [master 73ed120] testfile
-     1 file changed, 1 insertion(+)
-     create mode 120000 testfile
-    $ git annex whereis testfile
-    whereis testfile (0 copies) failed
-    git-annex: whereis: 1 failed
-    
-    
-    # The contents exists though
-    $ ls -l testfile
-    lrwxrwxrwx 1 ftp ftp 176 May 13 09:43 testfile -> .git/annex/objects/P5/4q/SHA256-s6--5891b5b522d5df086d0ff0b110fbd9d21bb4fc7163af34d08286a2e846f6be03/SHA256-s6--5891b5b522d5df086d0ff0b110fbd9d21bb4fc7163af34d08286a2e846f6be03
-    $ cat .git/annex/objects/P5/4q/SHA256-s6--5891b5b522d5df086d0ff0b110fbd9d21bb4fc7163af34d08286a2e846f6be03/SHA256-s6--5891b5b522d5df086d0ff0b110fbd9d21bb4fc7163af34d08286a2e846f6be03
-    hello
-    $ sha256sum testfile
-    5891b5b522d5df086d0ff0b110fbd9d21bb4fc7163af34d08286a2e846f6be03  testfile
-
-
-    # the file can be found when unlocking/locking
-    $ git annex unlock testfile
-    unlock testfile (copying...) ok
-    $ git annex lock testfile
-    lock testfile ok
-    (Recording state in git...)
-
-### What version of git-annex are you using? On what operating system?
-I ran Debian squeeze, with git annex 3.20120629~bpo60+2 when the problem was introduced. I just upgraded to wheezy, but the same problem exists with 3.20120629 from wheezy.
-
-I also manually installed 4.20130501 from unstable, which also showed the same problem.
-
-
-### Please provide any additional information below.
-
-I am not sure what information to supply, please provide pointers on what information might be useful.
-
-> [[done]] per comment --[[Joey]]
diff --git a/doc/bugs/Local_files_not_found/comment_1_5e1fcc0597594fa493ffa28aa32e1df8._comment b/doc/bugs/Local_files_not_found/comment_1_5e1fcc0597594fa493ffa28aa32e1df8._comment
deleted file mode 100644
index 72ed1e42f..000000000
--- a/doc/bugs/Local_files_not_found/comment_1_5e1fcc0597594fa493ffa28aa32e1df8._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawljcHBnBhazpDpk5k_9Wk9S_zA0hnjqdLQ"
- nickname="Andreas"
- subject="comment 1"
- date="2013-05-13T08:24:50Z"
- content="""
-Sorry for the noise - it turned out the local annex repository somehow had been marked as \"dead\" (as shown by git status).
-
-The fix was simply to git annex semitrust <repo uuid> and it went back to life.
-
-I am not sure how this bug tracker works, but this bug report can be closed as invalid. Thanks for git annex!
-"""]]
diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn
deleted file mode 100644
index 63f423e2c..000000000
--- a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn
+++ /dev/null
@@ -1,39 +0,0 @@
-### Please describe the problem.
-Pairing over my local network doesn't work.  The pairing process never finishes.  The log shows that the same PairMsg messages are repeated endlessly.
-
-### What steps will reproduce the problem?
-
-
-### What version of git-annex are you using? On what operating system?
-I'm on Ubuntu Raring 13.04.  I installed git-annex 4.20131024 from the Precise PPA.  It is working fine with a remote ssh repo, just not local pairing.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-[2013-11-01 16:55:21 CDT] main: Pairing in progress
-[2013-11-01 16:55:55 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"Onyx\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBT0Y6TTzTg8nWwonmgUPPwJmPIaJzfEoJl8DbuylpgXqGCQ4doJXuvBODHIehPfyMr1xCWqNlNNLkcWg/a/eHFceyt3IlcD9XaZ1aKPzPmpjYKKf5amiYd6mAssw8zFaZUvwaXkNuHZpXVZyg6C6TkT6kdfln+6fOJZpSGQzksy0jka/Rzx0KXjsp3oqO4tQJbC7AX0nvmD0zvLtyCURzfGV+n2IqQxpPf2nP75Evt8jamcuqm6pWoe+hj9zjGytIXpSKe35wzRwUAUrjgmZ9NweuWfi2uMPJlDv8/n+Q3HyjygA+GzixBGuYXDt1CD8ISZvuoygS+9+jeY9uYH8b me@Onyx\\n\", pairUUID = UUID \"834b4f39-ca66-4baf-9323-57ef7058d7d0\"},IPv4Addr 2281744576), verifiableDigest = \"8d5d380542f7377f09a4584a38b0dbcea9ea215c\"})"
-[2013-11-01 16:55:56 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"kubbie\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCvBEWT+AiAmehOFyTQWlSdwDs7DDbkw7rfZ4W/IeG5awZjMgT5BefIv9cmar8vGIIEFMZLpf8cL3xIargDz0xE2wuqj5CLkdz+DKp5f2FGs11Ax/62DZr+eCiVtPnwijFw0Cz0wMRzkN93uedrvzP/KkNRcczgWh3aZqn8WxlkCia1fyykm/pP3W80MNkiJYX5vXpu1NCV5KLu+UXQzKhM2njOauJ3W5wsMvSl8faZIpEmKVCD3BMDDruxTIxggA3kt9GCGvIbPawy+fGOpp/j6pHqnX3GB2kkT47RIZKYEv99HuLyvea+oY5R11FsC2yYY3ujIdUU0fXnV8pvrqSv me@kubbie\\n\", pairUUID = UUID \"fd6a6858-76c9-4eea-b733-9359c7313e72\"},IPv4Addr 1879091392), verifiableDigest = \"cbd8197c3d78c8c68bb30f63aa974cd88dd0fb13\"})"
-[2013-11-01 16:55:57 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"Onyx\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBT0Y6TTzTg8nWwonmgUPPwJmPIaJzfEoJl8DbuylpgXqGCQ4doJXuvBODHIehPfyMr1xCWqNlNNLkcWg/a/eHFceyt3IlcD9XaZ1aKPzPmpjYKKf5amiYd6mAssw8zFaZUvwaXkNuHZpXVZyg6C6TkT6kdfln+6fOJZpSGQzksy0jka/Rzx0KXjsp3oqO4tQJbC7AX0nvmD0zvLtyCURzfGV+n2IqQxpPf2nP75Evt8jamcuqm6pWoe+hj9zjGytIXpSKe35wzRwUAUrjgmZ9NweuWfi2uMPJlDv8/n+Q3HyjygA+GzixBGuYXDt1CD8ISZvuoygS+9+jeY9uYH8b me@Onyx\\n\", pairUUID = UUID \"834b4f39-ca66-4baf-9323-57ef7058d7d0\"},IPv4Addr 2281744576), verifiableDigest = \"8d5d380542f7377f09a4584a38b0dbcea9ea215c\"})"
-[2013-11-01 16:55:58 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"kubbie\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCvBEWT+AiAmehOFyTQWlSdwDs7DDbkw7rfZ4W/IeG5awZjMgT5BefIv9cmar8vGIIEFMZLpf8cL3xIargDz0xE2wuqj5CLkdz+DKp5f2FGs11Ax/62DZr+eCiVtPnwijFw0Cz0wMRzkN93uedrvzP/KkNRcczgWh3aZqn8WxlkCia1fyykm/pP3W80MNkiJYX5vXpu1NCV5KLu+UXQzKhM2njOauJ3W5wsMvSl8faZIpEmKVCD3BMDDruxTIxggA3kt9GCGvIbPawy+fGOpp/j6pHqnX3GB2kkT47RIZKYEv99HuLyvea+oY5R11FsC2yYY3ujIdUU0fXnV8pvrqSv me@kubbie\\n\", pairUUID = UUID \"fd6a6858-76c9-4eea-b733-9359c7313e72\"},IPv4Addr 1879091392), verifiableDigest = \"cbd8197c3d78c8c68bb30f63aa974cd88dd0fb13\"})"
-[2013-11-01 16:55:59 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"Onyx\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBT0Y6TTzTg8nWwonmgUPPwJmPIaJzfEoJl8DbuylpgXqGCQ4doJXuvBODHIehPfyMr1xCWqNlNNLkcWg/a/eHFceyt3IlcD9XaZ1aKPzPmpjYKKf5amiYd6mAssw8zFaZUvwaXkNuHZpXVZyg6C6TkT6kdfln+6fOJZpSGQzksy0jka/Rzx0KXjsp3oqO4tQJbC7AX0nvmD0zvLtyCURzfGV+n2IqQxpPf2nP75Evt8jamcuqm6pWoe+hj9zjGytIXpSKe35wzRwUAUrjgmZ9NweuWfi2uMPJlDv8/n+Q3HyjygA+GzixBGuYXDt1CD8ISZvuoygS+9+jeY9uYH8b me@Onyx\\n\", pairUUID = UUID \"834b4f39-ca66-4baf-9323-57ef7058d7d0\"},IPv4Addr 2281744576), verifiableDigest = \"8d5d380542f7377f09a4584a38b0dbcea9ea215c\"})"
-[2013-11-01 16:56:00 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"kubbie\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCvBEWT+AiAmehOFyTQWlSdwDs7DDbkw7rfZ4W/IeG5awZjMgT5BefIv9cmar8vGIIEFMZLpf8cL3xIargDz0xE2wuqj5CLkdz+DKp5f2FGs11Ax/62DZr+eCiVtPnwijFw0Cz0wMRzkN93uedrvzP/KkNRcczgWh3aZqn8WxlkCia1fyykm/pP3W80MNkiJYX5vXpu1NCV5KLu+UXQzKhM2njOauJ3W5wsMvSl8faZIpEmKVCD3BMDDruxTIxggA3kt9GCGvIbPawy+fGOpp/j6pHqnX3GB2kkT47RIZKYEv99HuLyvea+oY5R11FsC2yYY3ujIdUU0fXnV8pvrqSv me@kubbie\\n\", pairUUID = UUID \"fd6a6858-76c9-4eea-b733-9359c7313e72\"},IPv4Addr 1879091392), verifiableDigest = \"cbd8197c3d78c8c68bb30f63aa974cd88dd0fb13\"})"
-[2013-11-01 16:56:01 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"Onyx\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBT0Y6TTzTg8nWwonmgUPPwJmPIaJzfEoJl8DbuylpgXqGCQ4doJXuvBODHIehPfyMr1xCWqNlNNLkcWg/a/eHFceyt3IlcD9XaZ1aKPzPmpjYKKf5amiYd6mAssw8zFaZUvwaXkNuHZpXVZyg6C6TkT6kdfln+6fOJZpSGQzksy0jka/Rzx0KXjsp3oqO4tQJbC7AX0nvmD0zvLtyCURzfGV+n2IqQxpPf2nP75Evt8jamcuqm6pWoe+hj9zjGytIXpSKe35wzRwUAUrjgmZ9NweuWfi2uMPJlDv8/n+Q3HyjygA+GzixBGuYXDt1CD8ISZvuoygS+9+jeY9uYH8b me@Onyx\\n\", pairUUID = UUID \"834b4f39-ca66-4baf-9323-57ef7058d7d0\"},IPv4Addr 2281744576), verifiableDigest = \"8d5d380542f7377f09a4584a38b0dbcea9ea215c\"})"
-...and so on and so on...
-# End of transcript or log.
-"""]]
-
-> I was able to reproduce something very like this by starting
-> pairing separately on both computers under poor network conditions (ie,
-> weak wifi on my front porch).
-> 
-> So, I've made a new PairReq message that has not been seen before 
-> always make the alert pop up, even if the assistant thinks it is
-> in the middle of its own pairing process (or even another pairing process
-> with a different box on the LAN).
->
-> (This shouldn't cause a rogue PairAck to disrupt a pairing process part
-> way through.)
-> 
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_1_b8c485bafd98be8c21595597af361255._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_1_b8c485bafd98be8c21595597af361255._comment
deleted file mode 100644
index 39587ee90..000000000
--- a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_1_b8c485bafd98be8c21595597af361255._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="comment 1"
- date="2013-11-01T23:10:12Z"
- content="""
-Also, when I initiate the pairing process on one computer only, I can see the PairMsg being constantly received in the other computer's log, but the prompt to finish pairing never appears.
-"""]]
diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_2_bc63489334f44a423645021415ffe196._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_2_bc63489334f44a423645021415ffe196._comment
deleted file mode 100644
index f10b16f3c..000000000
--- a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_2_bc63489334f44a423645021415ffe196._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="comment 2"
- date="2013-11-01T23:27:24Z"
- content="""
-Well I installed the 1 Nov release from the tarball and then it picked up the pair request from the other system.  I don't know if it was a bug in the previous version or something to do with the PPA.  It's weird that the assistant just wasn't doing anything about the pair request it received.
-
-Thanks for your work on git-annex assistant.
-"""]]
diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_3_6345b174d04b6613c2c55a6ec9e50c21._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_3_6345b174d04b6613c2c55a6ec9e50c21._comment
deleted file mode 100644
index a7eff6744..000000000
--- a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_3_6345b174d04b6613c2c55a6ec9e50c21._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 3"
- date="2013-11-02T19:02:55Z"
- content="""
-There is something a little strange in the logs. It shows both Onyx and kubbie are sending PairReqs. Probably one of those is the local computer, logging its own broadcast messages which loop back to it. But normally in pairing, one side starts the pairing process with a PairReq, and the other side pops up an alert and continues the process with a PairAck. It's not normal for both sides to request that pairing start.
-
-Is it possible that you started pairing on both computers separately?
-
-I tried doing that with gnu and darkstar. First I started pairing on gnu. darkstar saw the pair request, but I ignored the alert message about that, and went  and started a separate pairing process on darkstar. gnu never showed an alert message for that; it ignored darkstar's PairReqs since it was sending its own.
-
-It's unlikely you'd ignore the alert, but the same thing could happen if the two computers were not able to communicate over the network initially, and pairing were started on both separately. So neither gets a chance to see the other's PairReq and show the alert. Even when they came into communication, they'd each ignore the other's PairReq.
-
-So, that seems like a bug..
-"""]]
diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_4_f39ec6c3d5a016b3c5260162c0b42177._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_4_f39ec6c3d5a016b3c5260162c0b42177._comment
deleted file mode 100644
index cacbad03f..000000000
--- a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_4_f39ec6c3d5a016b3c5260162c0b42177._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="comment 4"
- date="2013-11-02T22:52:31Z"
- content="""
-I did indeed try to pair from both systems.  What happened was, after I started the pair request, I went to the other system, and there was no pair request listed.  So I misunderstood the directions and thought I was supposed to go ahead and enter the same password into the other system.  (It says that pairing will complete as soon as the password is entered on the other system, so it seems reasonable to try that.)  Then both systems were constantly issuing pair requests, but neither system was responding to the requests, even though it was receiving them.
-
-Both systems were always on the network and always able to communicate over it.  The bug went away when I upgraded to the 1 Nov release...but then I had some very confusing issues with partially-paired repos from different git-annex versions...I ended up having to start git-annex over from scratch on both systems with the 1 Nov build.
-
-So I'm not sure where to go from here with this bug.  Thanks for your help.
-"""]]
diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_5_ca0c5ef6e6a6d2c4b64430ac68370b6a._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_5_ca0c5ef6e6a6d2c4b64430ac68370b6a._comment
deleted file mode 100644
index 413ca952e..000000000
--- a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_5_ca0c5ef6e6a6d2c4b64430ac68370b6a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="comment 5"
- date="2013-11-02T22:55:42Z"
- content="""
-Oh, now I see your comment up there that you fixed it.  Awesome.  :)
-"""]]
diff --git a/doc/bugs/Log_rotation_loses_large_logs.mdwn b/doc/bugs/Log_rotation_loses_large_logs.mdwn
deleted file mode 100644
index c38c198b6..000000000
--- a/doc/bugs/Log_rotation_loses_large_logs.mdwn
+++ /dev/null
@@ -1,69 +0,0 @@
-### Please describe the problem.
-
-I have a large git-annex repository created using the assistant. It has thousands of files in it and is about 50GB in size.
-Yesterday I added a number of new files, and I also created a new "removable drive" repository for it to sync to.
-
-During these operations I could see a large amount of data being added to the git-annex log files.
-I left my computer on overnight to finish the sync.
-
-Today I went to check the log files but there was no useful information in them.
-
-Looking at the source I suspect I had a single log file > 1 Megabyte in size, which caused the rotation to occur repeatedly until it rolled off the end.
-However, I would have preferred if this large logfile had been kept for more than a couple of hours.
-
-See file contents below
-
-### What steps will reproduce the problem?
-
-See above
-
-### What version of git-annex are you using? On what operating system?
-
-Debian Wheezy, git-annex version: 5.20140210~bpo70+2 from wheezy-backports
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-When I look at the log files now, I see the following:
--rw-r--r--    1 pgl users     443 Mar  5 21:48 daemon.log
--rw-r--r--    1 pgl users     443 Mar  5 21:47 daemon.log.1
--rw-r--r--    1 pgl users      81 Mar  5 01:16 daemon.log.10
--rw-r--r--    1 pgl users      69 Mar  5 07:29 daemon.log.2
--rw-r--r--    1 pgl users      81 Mar  5 01:16 daemon.log.3
--rw-r--r--    1 pgl users      81 Mar  5 01:16 daemon.log.4
--rw-r--r--    1 pgl users      81 Mar  5 01:16 daemon.log.5
--rw-r--r--    1 pgl users      81 Mar  5 01:16 daemon.log.6
--rw-r--r--    1 pgl users      81 Mar  5 01:16 daemon.log.7
--rw-r--r--    1 pgl users      81 Mar  5 01:16 daemon.log.8
--rw-r--r--    1 pgl users      81 Mar  5 01:16 daemon.log.9
-
-Looking at some of these log files.
-
-pgl@....:/....../.git/annex$ cat daemon.log.3
-[2014-03-05 01:16:15 GMT] SanityCheckerHourly: Rotated logs due to size: 1026416
-pgl@....:/....../.git/annex$ cat daemon.log.4
-[2014-03-05 01:16:15 GMT] SanityCheckerHourly: Rotated logs due to size: 1026416
-pgl@....:/....../.git/annex$ cat daemon.log.5
-[2014-03-05 01:16:15 GMT] SanityCheckerHourly: Rotated logs due to size: 1026416
-pgl@....:/....../.git/annex$ cat daemon.log.6
-[2014-03-05 01:16:15 GMT] SanityCheckerHourly: Rotated logs due to size: 1026416
-pgl@....:/....../.git/annex$ cat daemon.log.7
-[2014-03-05 01:16:15 GMT] SanityCheckerHourly: Rotated logs due to size: 1026416
-pgl@....:/....../.git/annex$ cat daemon.log.8
-[2014-03-05 01:16:15 GMT] SanityCheckerHourly: Rotated logs due to size: 1026416
-pgl@....:/....../.git/annex$ cat daemon.log.9
-[2014-03-05 01:16:15 GMT] SanityCheckerHourly: Rotated logs due to size: 1026416
-
-# End of transcript or log.
-"""]]
-
-> Changed log rotation to only rotate 1 log per hour max,
-> unless the total size of the log files is larger than the 
-> free disk space on the filesystem containing them.
-> 
-> This way, runaway log growth will still be contained,
-> but logs will generally rotate slowly enough to give plenty of time
-> to see what's in them. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Lost_S3_Remote.mdwn b/doc/bugs/Lost_S3_Remote.mdwn
deleted file mode 100644
index c359b5210..000000000
--- a/doc/bugs/Lost_S3_Remote.mdwn
+++ /dev/null
@@ -1,59 +0,0 @@
-Somehow I've lost my S3 remote... git-annex knows it's there, but its not associating it with the git remote in .git/config
-
-    $ git-annex whereis pebuilder.iso 
-    whereis pebuilder.iso (3 copies) 
-      	3b6fc6f6-3025-11e1-b496-33bffbc0f3ed -- housebackup (external seagate drive on /mnt/back/RemoteStore)
-   	6b1326d8-2abb-11e1-8f43-979159a7f900 -- synology
-   	9b297772-2ab2-11e1-a86f-2fd669cb2417 -- Amazon S3
-    ok
-
-Amazon S3 is the description from the remote.  My .git/config file contains this block:
-
-    [remote "cloud"]
-      annex-s3 = true
-      annex-uuid = 9b297772-2ab2-11e1-a86f-2fd669cb2417
-      annex-cost = 70
-
-The UUID matches... But I cannot access it... see below:
-
-    [39532:39531 - 0:626] 08:20:38 [vivitron@tronlap:o +3] ~/annex/ISO 
-    $ git-annex get pebuilder.iso --from=cloud
-    git-annex: there is no git remote named "cloud"
-    
-    [39532:39531 - 0:627] 08:20:56 [vivitron@tronlap:o +3] ~/annex/ISO 
-    $ git-annex get pebuilder.iso --from="Amazon S3"
-    git-annex: there is no git remote named "Amazon S3"
-    
-    [39532:39531 - 0:628] 08:21:01 [vivitron@tronlap:o +3] ~/annex/ISO 
-    $ git-annex get pebuilder.iso --from=9b297772-2ab2-11e1-a86f-2fd669cb2417
-    git-annex: there is no git remote named "9b297772-2ab2-11e1-a86f-2fd669cb2417"
-
-    [39532:39531 - 0:629] 08:21:08 [vivitron@tronlap:o +3] ~/annex/ISO 
-    $ 
-
-git remote lists "cloud" as a remote:
-
-    $ git remote
-    all
-    cloud
-    cs
-    es3
-    origin
-
-git-annex status lists S3 support:
-
-    $ git-annex status
-    supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
-    supported remote types: git S3 bup directory rsync web hook
-
-
-
-I appreciate any help....  I've tested versions 3.20111211, 3.20111231, and 3.20120105
-
-    $ git --version
-    git version 1.7.8.1
-
-
-
-> [[done]]; I've fixed the build system so this confusing thing cannot
-> happen anymore. --[[Joey]]
diff --git a/doc/bugs/Lost_S3_Remote/comment_1_6e80e6db6671581d471fc9a54181c04c._comment b/doc/bugs/Lost_S3_Remote/comment_1_6e80e6db6671581d471fc9a54181c04c._comment
deleted file mode 100644
index d6595ad5b..000000000
--- a/doc/bugs/Lost_S3_Remote/comment_1_6e80e6db6671581d471fc9a54181c04c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2012-01-06T03:04:35Z"
- content="""
-Despite `status` listing S3 support, your git-annex is actually built with S3stub, probably because it failed to find the necessary S3 module at build time. Rebuild git-annex and watch closely, you'll see \"** building without S3 support\". Look above that for the error and fix it.
-
-It was certainly a bug that it showed S3 as supported when built without it. I've fixed that.
-"""]]
diff --git a/doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment b/doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment
deleted file mode 100644
index 6112bc089..000000000
--- a/doc/bugs/Lost_S3_Remote/comment_2_c99c65882a3924f4890e500f9492b442._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2012-01-06T03:08:28Z"
- content="""
-BTW, you'll want to \"make clean\", since the S3stub hack symlinks a file into place and it will continue building with S3stub even if you fix the problem until you clean.
-"""]]
diff --git a/doc/bugs/Lost_S3_Remote/comment_3_1e434d5a20a692cd9dc7f6f8f20f30dd._comment b/doc/bugs/Lost_S3_Remote/comment_3_1e434d5a20a692cd9dc7f6f8f20f30dd._comment
deleted file mode 100644
index 69063966c..000000000
--- a/doc/bugs/Lost_S3_Remote/comment_3_1e434d5a20a692cd9dc7f6f8f20f30dd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkey8WuXUh_x5JC2c9_it1CYRnVTgdGu1M"
- nickname="Dustin"
- subject="Thank you!"
- date="2012-01-06T03:38:27Z"
- content="""
-make clean and rebuild worked...  Thank you
-"""]]
diff --git a/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__.mdwn b/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__.mdwn
deleted file mode 100644
index 9a474af7b..000000000
--- a/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__.mdwn
+++ /dev/null
@@ -1,37 +0,0 @@
-### Please describe the problem.
-[2014-05-13 00:01:18 SAST] Cronner: Consistency check in progress
-[2014-05-13 00:29:49 SAST] NetWatcherFallback: Syncing with box.com, gitannexbackup 
-[2014-05-13 08:42:48 SAST] main: starting assistant version 5.20140420-ga25b8bb
-Already up-to-date.
-
-(scanning...) [2014-05-13 08:42:49 SAST] Watcher: Performing startup scan
-[2014-05-13 08:42:50 SAST] Upgrader: An upgrade of git-annex is available.  (version 5.20140421)
-(started...) [2014-05-13 13:31:46 SAST] NetWatcherFallback: Syncing with box.com, gitannexbackup 
-
-git-annex: /etc/resolv.conf: openFile: does not exist (No such file or directory)
-[2014-05-13 18:34:12 SAST] NetWatcherFallback: Syncing with box.com, gitannexbackup 
-[2014-05-13 19:34:12 SAST] NetWatcherFallback: Syncing with box.com, gitannexbackup 
-[2014-05-13 19:46:48 SAST] main: starting assistant version 5.20140420-ga25b8bb
-Already up-to-date.
-
-(scanning...) [2014-05-13 19:50:06 SAST] Watcher: Performing startup scan
-
-### What steps will reproduce the problem?
-I don't know, simply saw the error in my logs.
-
-### What version of git-annex are you using? On what operating system?
-Version: 5.20140420-ga25b8bb 
-Build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-Maac OSX 10.9.2
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; does not seem to be a problem. --[[Joey]]
diff --git a/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_1_6e50d721c624ad82e94c8e5e93b38783._comment b/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_1_6e50d721c624ad82e94c8e5e93b38783._comment
deleted file mode 100644
index be0c21eee..000000000
--- a/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_1_6e50d721c624ad82e94c8e5e93b38783._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 1"
- date="2014-05-16T18:00:53Z"
- content="""
-Based on the comments in <http://git-annex.branchable.com/bugs/Android:_no___34____47__etc__47__resolv.conf__34___when_submitting_jabber_user_and_password./>
-it seems that this system does have a /etc/resolv.conf.
-
-I'm left wondering if perhaps the file was briefly missing. For example, perhaps when moving between networks.
-
-Did git-annex break in some way? Is it working now with the file present?
-"""]]
diff --git a/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_2_07a22d9e9010a04ae0088ebfd4bbf4df._comment b/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_2_07a22d9e9010a04ae0088ebfd4bbf4df._comment
deleted file mode 100644
index c578d3c03..000000000
--- a/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_2_07a22d9e9010a04ae0088ebfd4bbf4df._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkAUMhKOSkh9JaBA6xst3XxQIIsDEq5Zd4"
- nickname="Ovidiu"
- subject="comment 2"
- date="2014-05-16T18:11:02Z"
- content="""
-Ah, that theory was right. I unplugged my iphone thus cutting my internet off, and the file is gone indeed.
-Does that mean we can ignore this problem? I'm only sporadically online via internet cafes and to check emails at night via iphone.
-
-Can't say whether git annex is working or not, still trying to figure out how it all works so I have only put a relatively small folder into the local repo and created a full backup S3 repo as well as an archive one on box.com
-"""]]
diff --git a/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_3_0b64e2dada87cd79fa584e86a00529ea._comment b/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_3_0b64e2dada87cd79fa584e86a00529ea._comment
deleted file mode 100644
index c27132892..000000000
--- a/doc/bugs/MAC_OSX_git-annex:___47__etc__47__resolv.conf:_openFile:_does_not_exist___40__No_such_file_or_directory__41__/comment_3_0b64e2dada87cd79fa584e86a00529ea._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 3"
- date="2014-05-16T18:25:29Z"
- content="""
-Yes, that makes sense. /etc/resolv.conf is only used when trying to access the network, so if the network is not up, nothing is going to fail that wouldn't fail anyway. And git-annex should retry everything at a later point, when the network is up.
-"""]]
diff --git a/doc/bugs/Makefile_is_missing_dependancies.mdwn b/doc/bugs/Makefile_is_missing_dependancies.mdwn
deleted file mode 100644
index 3e9d6e903..000000000
--- a/doc/bugs/Makefile_is_missing_dependancies.mdwn
+++ /dev/null
@@ -1,47 +0,0 @@
-<pre>
-From e45c73e66fc18d27bdf5797876fbeb07786a4af1 Mon Sep 17 00:00:00 2001
-From: Jimmy Tang <jtang@tchpc.tcd.ie>
-Date: Tue, 22 Mar 2011 22:24:07 +0000
-Subject: [PATCH] Touch up Makefile to depend on StatFS.hs
-
----
- Makefile |    2 +-
- 1 files changed, 1 insertions(+), 1 deletions(-)
-
-diff --git a/Makefile b/Makefile
-index 08e2f59..4ae8392 100644
---- a/Makefile
-+++ b/Makefile
-@@ -15,7 +15,7 @@ SysConfig.hs: configure.hs TestConfig.hs
-        hsc2hs $<
-        perl -i -pe 's/^{-# INCLUDE.*//' $@
- 
--$(bins): SysConfig.hs Touch.hs
-+$(bins): SysConfig.hs Touch.hs StatFS.hs
-        $(GHCMAKE) $@
- 
- git-annex.1: doc/git-annex.mdwn
--- 
-1.7.4.1
-
-</pre>
-
-
-StatFS.hs never gets depended on and compiled, the makefile was just missing something
-
-> Thanks, [[done]]! Interested to hear if StatFS.hs works on OSX (no warning) or
-> is a no-op (with warning). --[[Joey]] 
-
->> 
->> for now it gives a warning, it looks like it should be easy enough to add OSX
->> support, I guess it's a case of just digging around documentation to find the equivalent
->> calls/headers. I'll give it a go at making this feature work on OSX and get back to you.
->> 
-
-<pre>
-jtang@exia:~/develop/git-annex $ make
-hsc2hs StatFS.hsc
-StatFS.hsc:85:2: warning: #warning free space checking code not available for this OS
-StatFS.hsc:85:2: warning: #warning free space checking code not available for this OS
-StatFS.hsc:85:2: warning: #warning free space checking code not available for this OS
-</pre>
diff --git a/doc/bugs/Makefile_is_missing_dependancies/comment_1_5a3da5f79c8563c7a450aa29728abe7c._comment b/doc/bugs/Makefile_is_missing_dependancies/comment_1_5a3da5f79c8563c7a450aa29728abe7c._comment
deleted file mode 100644
index ab8493a7a..000000000
--- a/doc/bugs/Makefile_is_missing_dependancies/comment_1_5a3da5f79c8563c7a450aa29728abe7c._comment
+++ /dev/null
@@ -1,47 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 1"
- date="2011-03-23T08:21:30Z"
- content="""
-Just did some minor digging around and checking, this seems to satisfy the compilers etc... I have yet to confirm that it *really* is working as expected. Also it might be better to check for a darwin operating system instead of apple I think, though I don't know of any one really using a pure darwin OS. But for now it works (I think)
-
-<pre>
-From fbfe27c2e19906ac02e3673b91bffa920f6dae5d Mon Sep 17 00:00:00 2001
-From: Jimmy Tang <jtang@tchpc.tcd.ie>
-Date: Wed, 23 Mar 2011 08:15:39 +0000
-Subject: [PATCH] Define (__APPLE__) in StatFS
-
-At least on OSX 10.6.6 it appears to have the same defintions as
-FreeBSD. The build process doesn't complain and the code is enabled,
-this needs to be tested and checked more.
----
- StatFS.hsc |    4 ++--
- 1 files changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/StatFS.hsc b/StatFS.hsc
-index 8b453dc..45fd7e4 100644
---- a/StatFS.hsc
-+++ b/StatFS.hsc
-@@ -53,7 +53,7 @@ import Foreign.C.String
- import Data.ByteString (useAsCString)
- import Data.ByteString.Char8 (pack)
- 
--#if defined (__FreeBSD__)
-+#if defined (__FreeBSD__) || defined(__APPLE__)
- # include <sys/param.h>
- # include <sys/mount.h>
- #else
-@@ -84,7 +84,7 @@ data CStatfs
- #ifdef UNKNOWN
- #warning free space checking code not available for this OS
- #else
--#if defined(__FreeBSD__)
-+#if defined(__FreeBSD__) || defined(__APPLE__)
- foreign import ccall unsafe \"sys/mount.h statfs\"
- #else
- foreign import ccall unsafe \"sys/vfs.h statfs64\"
--- 
-1.7.4.1
-</pre>
-"""]]
diff --git a/doc/bugs/Makefile_is_missing_dependancies/comment_2_416f12dbd0c2b841fac8164645b81df5._comment b/doc/bugs/Makefile_is_missing_dependancies/comment_2_416f12dbd0c2b841fac8164645b81df5._comment
deleted file mode 100644
index d355514a3..000000000
--- a/doc/bugs/Makefile_is_missing_dependancies/comment_2_416f12dbd0c2b841fac8164645b81df5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-03-23T15:05:12Z"
- content="""
-There's a simple test -- just configure annex.diskreserve to be say, 10 megabytes less than the total free space on your disk. Then try to git annex get a 11 mb file, and a 9 mb file. :)
-"""]]
diff --git a/doc/bugs/Makefile_is_missing_dependancies/comment_3_c38b6f4abc9b9ad413c3b83ca04386c3._comment b/doc/bugs/Makefile_is_missing_dependancies/comment_3_c38b6f4abc9b9ad413c3b83ca04386c3._comment
deleted file mode 100644
index 6b4cf5789..000000000
--- a/doc/bugs/Makefile_is_missing_dependancies/comment_3_c38b6f4abc9b9ad413c3b83ca04386c3._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 3"
- date="2011-03-23T15:13:33Z"
- content="""
-Alternatively, you can just load it up in ghci and see if it reports numbers that make sense:
-
-<pre>
-joey@gnu:~/src/git-annex>make StatFS.hs
-hsc2hs StatFS.hsc
-perl -i -pe 's/^{-# INCLUDE.*//' StatFS.hs
-joey@gnu:~/src/git-annex>ghci StatFS.hs
-GHCi, version 6.12.1: http://www.haskell.org/ghc/  :? for help
-Loading package ghc-prim ... linking ... done.
-Loading package integer-gmp ... linking ... done.
-Loading package base ... linking ... done.
-[1 of 1] Compiling StatFS           ( StatFS.hs, interpreted )
-Ok, modules loaded: StatFS.
-*StatFS> s <- getFileSystemStats \".\"
-Loading package bytestring-0.9.1.5 ... linking ... done.
-*StatFS> s
-Just (FileSystemStats {fsStatBlockSize = 4096, fsStatBlockCount = 7427989, fsStatByteCount = 30425042944, fsStatBytesFree = 2528489472, fsStatBytesAvailable = 2219384832, fsStatBytesUsed = 27896553472})
-</pre>
-"""]]
diff --git a/doc/bugs/Makefile_is_missing_dependancies/comment_4_cc13873175edf191047282700315beee._comment b/doc/bugs/Makefile_is_missing_dependancies/comment_4_cc13873175edf191047282700315beee._comment
deleted file mode 100644
index c3ad2dafd..000000000
--- a/doc/bugs/Makefile_is_missing_dependancies/comment_4_cc13873175edf191047282700315beee._comment
+++ /dev/null
@@ -1,30 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 4"
- date="2011-03-23T16:02:34Z"
- content="""
-Ok, well it looks like it isn't doing anything useful at all.
-
-<pre>
-jtang@x00:~/develop/git-annex $ make StatFS.hs                                                                                                                                    
-hsc2hs StatFS.hsc
-perl -i -pe 's/^{-# INCLUDE.*//' StatFS.hs
-jtang@x00:~/develop/git-annex $ ghci StatFS.hs                                                                                                                                    
-GHCi, version 6.12.3: http://www.haskell.org/ghc/  :? for help
-Loading package ghc-prim ... linking ... done.
-Loading package integer-gmp ... linking ... done.
-Loading package base ... linking ... done.
-Loading package ffi-1.0 ... linking ... done.
-[1 of 1] Compiling StatFS           ( StatFS.hs, interpreted )
-Ok, modules loaded: StatFS.
-*StatFS> s <- getFileSystemStats \".\"
-Loading package bytestring-0.9.1.7 ... linking ... done.
-*StatFS> s
-Just (FileSystemStats {fsStatBlockSize = 0, fsStatBlockCount = 1048576, fsStatByteCount = 0, fsStatBytesFree = 0, fsStatBytesAvailable = 0, fsStatBytesUsed = 0})
-*StatFS> s <- getFileSystemStats \"/\"
-*StatFS> s
-Just (FileSystemStats {fsStatBlockSize = 0, fsStatBlockCount = 1048576, fsStatByteCount = 0, fsStatBytesFree = 0, fsStatBytesAvailable = 0, fsStatBytesUsed = 0})
-*StatFS> 
-</pre>
-"""]]
diff --git a/doc/bugs/Makefile_is_missing_dependancies/comment_5_0a1c52e2c96d19b9c3eb7e99b8c2434f._comment b/doc/bugs/Makefile_is_missing_dependancies/comment_5_0a1c52e2c96d19b9c3eb7e99b8c2434f._comment
deleted file mode 100644
index 149aeeb75..000000000
--- a/doc/bugs/Makefile_is_missing_dependancies/comment_5_0a1c52e2c96d19b9c3eb7e99b8c2434f._comment
+++ /dev/null
@@ -1,59 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 5"
- date="2011-03-23T16:14:22Z"
- content="""
-Actually I may have just been stupid and should have read the man page on statfs...
-
-<pre>
-jtang@x00:~/develop/git-annex $ git diff
-diff --git a/StatFS.hsc b/StatFS.hsc
-index 8b453dc..e10b2dd 100644
---- a/StatFS.hsc
-+++ b/StatFS.hsc
-@@ -53,7 +53,7 @@ import Foreign.C.String
- import Data.ByteString (useAsCString)
- import Data.ByteString.Char8 (pack)
- 
--#if defined (__FreeBSD__)
-+#if defined (__FreeBSD__) || defined (__APPLE__)
- # include <sys/param.h>
- # include <sys/mount.h>
- #else
-@@ -84,8 +84,8 @@ data CStatfs
- #ifdef UNKNOWN
- #warning free space checking code not available for this OS
- #else
--#if defined(__FreeBSD__)
--foreign import ccall unsafe \"sys/mount.h statfs\"
-+#if defined(__FreeBSD__) || defined (__APPLE__)
-+foreign import ccall unsafe \"sys/mount.h statfs64\"
- #else
- foreign import ccall unsafe \"sys/vfs.h statfs64\"
- #endif
-</pre>
-
-yields this...
-
-<pre>
-jtang@x00:~/develop/git-annex $ ghci StatFS.hs                                                                                                                                    
-GHCi, version 6.12.3: http://www.haskell.org/ghc/  :? for help
-Loading package ghc-prim ... linking ... done.
-Loading package integer-gmp ... linking ... done.
-Loading package base ... linking ... done.
-Loading package ffi-1.0 ... linking ... done.
-[1 of 1] Compiling StatFS           ( StatFS.hs, interpreted )
-Ok, modules loaded: StatFS.
-*StatFS> s <- getFileSystemStats \".\"
-Loading package bytestring-0.9.1.7 ... linking ... done.
-*StatFS> s
-Just (FileSystemStats {fsStatBlockSize = 4096, fsStatBlockCount = 244106668, fsStatByteCount = 999860912128, fsStatBytesFree = 423097798656, fsStatBytesAvailable = 422835654656, fsStatBytesUsed = 576763113472})
-*StatFS> 
-</pre>
-
-
-we could just stick another if defined (__APPLE__) instead of what I previously had and it looks like it will do the right thing on OSX.
-
-
-"""]]
diff --git a/doc/bugs/Makefile_is_missing_dependancies/comment_6_24119fc5d5963ce9dd669f7dcf006859._comment b/doc/bugs/Makefile_is_missing_dependancies/comment_6_24119fc5d5963ce9dd669f7dcf006859._comment
deleted file mode 100644
index 714459fbe..000000000
--- a/doc/bugs/Makefile_is_missing_dependancies/comment_6_24119fc5d5963ce9dd669f7dcf006859._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 6"
- date="2011-03-23T16:23:56Z"
- content="""
-I forgot to mention that the statfs64 stuff in OSX seems to be deprecated, see http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man2/statfs64.2.html
-
-on a slightly different note, is anonymous pushing to the \"wiki\" over git allowed? I'd prefer to be able to edit stuff inline for updating some of my own comments if I can :P
-"""]]
diff --git a/doc/bugs/Makefile_is_missing_dependancies/comment_7_96fd4725df4b54e670077a18d3ac4943._comment b/doc/bugs/Makefile_is_missing_dependancies/comment_7_96fd4725df4b54e670077a18d3ac4943._comment
deleted file mode 100644
index 8ba8e8d1f..000000000
--- a/doc/bugs/Makefile_is_missing_dependancies/comment_7_96fd4725df4b54e670077a18d3ac4943._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 7"
- date="2011-03-23T16:57:56Z"
- content="""
-Try the changes I've pushed to use statfs64 on apple.
-
-There is actually a standardized statvfs that I'd rather use, but after the last time that I tried going with the POSIX option first only to find it was not broadly implemented, I was happy to find some already existing code that worked for some OSs.
-
-(While ikiwiki supports anonymous git push, it's a feature we have not rolled out on Branchable.com yet, and anyway, ikiwiki disallows editing existing comments that way. I would, however, be happy to git pull changes from somewhere.)
-"""]]
diff --git a/doc/bugs/Makefile_is_missing_dependancies/comment_8_a3555e3286cdc2bfeb9cde0ff727ba74._comment b/doc/bugs/Makefile_is_missing_dependancies/comment_8_a3555e3286cdc2bfeb9cde0ff727ba74._comment
deleted file mode 100644
index 63d188bcc..000000000
--- a/doc/bugs/Makefile_is_missing_dependancies/comment_8_a3555e3286cdc2bfeb9cde0ff727ba74._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 8"
- date="2011-03-23T17:03:51Z"
- content="""
-The latest change looks good, it seems to be returning sensible numbers for me. Just tried it out on a few different mount points and it appears to be working.
-"""]]
diff --git a/doc/bugs/Manual_mode_weirdness.mdwn b/doc/bugs/Manual_mode_weirdness.mdwn
deleted file mode 100644
index efc88df2f..000000000
--- a/doc/bugs/Manual_mode_weirdness.mdwn
+++ /dev/null
@@ -1,37 +0,0 @@
-### Please describe the problem.
-
-I have an annex which contains all my photos. There are repositories on my laptop and my home server as well as an s3 backup (for which syncing is currently disabled). I switched the copy on my laptop to manual mode via 'git annex vicfg' (this correctly shows up in the webapp). I then proceeded to drop several folders (each containing a year's worth of photos). This works fine, however the assistant immediately starts downloading the dropped files from the server! Numcopies is set to 1 and the problem exists with the server in both the 'transfer' and 'backup' groups (haven't tried others).
-
-### What steps will reproduce the problem?
-
-1. Create a repo with some files.
-2. Create a bare-git remote on another machine.
-3. Make sure the assistant is running for the repo in question. 
-4. Switch your local copy to manual mode.
-5. Drop some files.
-6. Watch as the assistant re-downloads them!
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130501
-local repository version: unknown
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-
-Debian Testing/Sid.
-
-### Please provide any additional information below.
-
-If it's relevant I switched the local repository to indirect mode by manually shutting down the assistant and running 'git annex indirect' before restarting the assistant. This was done before any of the steps above.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Manual_mode_weirdness/comment_1_f8ab3bac9e9a6768e5fd5a052f0d920f._comment b/doc/bugs/Manual_mode_weirdness/comment_1_f8ab3bac9e9a6768e5fd5a052f0d920f._comment
deleted file mode 100644
index fcacc3b33..000000000
--- a/doc/bugs/Manual_mode_weirdness/comment_1_f8ab3bac9e9a6768e5fd5a052f0d920f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-29T16:13:10Z"
- content="""
-Yes,  4.20130501 is broken WRT manual mode. This has been fixed for a while in the current git master branch and autobuilds and there will be a new release soon with the fix.
-"""]]
diff --git a/doc/bugs/Manual_mode_weirdness/comment_2_e810daa488fad32ca8bdaae620051da8._comment b/doc/bugs/Manual_mode_weirdness/comment_2_e810daa488fad32ca8bdaae620051da8._comment
deleted file mode 100644
index 3a4cd9881..000000000
--- a/doc/bugs/Manual_mode_weirdness/comment_2_e810daa488fad32ca8bdaae620051da8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="robconnolly"
- ip="203.167.218.84"
- subject="comment 2"
- date="2013-05-29T23:18:23Z"
- content="""
-Excellent, Thank you!
-"""]]
diff --git a/doc/bugs/Matching_oddity_in_SafeCommand.hs.mdwn b/doc/bugs/Matching_oddity_in_SafeCommand.hs.mdwn
deleted file mode 100644
index 53bba4a9b..000000000
--- a/doc/bugs/Matching_oddity_in_SafeCommand.hs.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-In SafeCommand.hs, the code to unwrap a File looks like:
-
-[[!format haskell """
-toCommand :: [CommandParam] -> [String]
-toCommand = concatMap unwrap
-  where
-        [...]
-        -- Files that start with a non-alphanumeric that is not a path
-        -- separator are modified to avoid the command interpreting them as
-        -- options or other special constructs.
-        unwrap (File s@(h:_))
-                | isAlphaNum h || h `elem` pathseps = [s]
-                | otherwise = ["./" ++ s]
-        unwrap (File s) = [s]
-        [...]
-"""]]
-
-I am not sure I understand which case would be caught in the last clause "unwrap (File s)". Is that the empty file? Because all non-empty file names seem to have been caught earlier, at least in the "otherwise" if they do not match the condition. In this case, wouldn't it be an error to use an empty file name and wouldn't it be better to throw an exception instead of returning [[]]?
-
-I would use:
-
-[[!format haskell """
-        unwrap (File []) = throw "Empty file name in SafeCommand.toCommand"
-"""]]
-
-or something similar instead.
-
-> [[done]]
diff --git a/doc/bugs/Matching_oddity_in_SafeCommand.hs/comment_1_1a51630c0791547a7e0b68eea5d81e4c._comment b/doc/bugs/Matching_oddity_in_SafeCommand.hs/comment_1_1a51630c0791547a7e0b68eea5d81e4c._comment
deleted file mode 100644
index d52dfed43..000000000
--- a/doc/bugs/Matching_oddity_in_SafeCommand.hs/comment_1_1a51630c0791547a7e0b68eea5d81e4c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.172"
- subject="comment 1"
- date="2014-02-12T16:27:10Z"
- content="""
-You're right that line only matches empty filenames. I think that the Hurd actually does support empty filenames. It seems that the command being run would otherwise complain that it was given an empty parameter. So I do not think it's worth throwing an error here. Also, I prefer to keep toCommand a total function. 
-"""]]
diff --git a/doc/bugs/Missing_dependancy_in_commit_6cecc26206c4a539999b04664136c6f785211a41.mdwn b/doc/bugs/Missing_dependancy_in_commit_6cecc26206c4a539999b04664136c6f785211a41.mdwn
deleted file mode 100644
index 2253c0f52..000000000
--- a/doc/bugs/Missing_dependancy_in_commit_6cecc26206c4a539999b04664136c6f785211a41.mdwn
+++ /dev/null
@@ -1,35 +0,0 @@
-Seems commit 6cecc26206c4a539999b04664136c6f785211a41 missed on dependancy, that is blaze-markup
-
-<pre>
-Assistant/Threads/WebApp.hs:25:8:
-    Could not find module `Text.Blaze.Renderer.String'
-    It is a member of the hidden package `blaze-markup-0.5.1.0'.
-    Perhaps you need to add `blaze-markup' to the build-depends in your .cabal file.
-    Use -v to see a list of the files searched for.
-cabal: Error: some packages failed to install:
-git-annex-3.20120721 failed during the building phase. The exception was:
-ExitFailure 1
-</pre>
-
-This should fix it
-
-<pre>
-x00:git-annex jtang$ git diff
-diff --git a/git-annex.cabal b/git-annex.cabal
-index c7d9bf5..4f98d2a 100644
---- a/git-annex.cabal
-+++ b/git-annex.cabal
-@@ -76,7 +76,7 @@ Executable git-annex
-   if flag(Webapp)
-     Build-Depends: yesod, yesod-static, case-insensitive, http-types,
-      transformers, wai, wai-logger, warp, blaze-builder, blaze-html,
--     crypto-api, hamlet
-+     blaze-markup, crypto-api, hamlet
-     CPP-Options: -DWITH_WEBAPP
- 
-   if (os(darwin))
-</pre>
-
-> [[done]].. interestingly, cabal had not complained about there here,
-> as in my version, it's in blaze, not blaze-markup. Added it anyway.
-> --[[Joey]] 
diff --git a/doc/bugs/More_sync__39__ing_weirdness_with_the_assistant_branch_on_OSX.mdwn b/doc/bugs/More_sync__39__ing_weirdness_with_the_assistant_branch_on_OSX.mdwn
deleted file mode 100644
index 00f425307..000000000
--- a/doc/bugs/More_sync__39__ing_weirdness_with_the_assistant_branch_on_OSX.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-Running the 'assistant' branch, I occassionally get
-
-To myhost1:/Users/jtang/annex
- ! [rejected]        master -> synced/master (non-fast-forward)
-error: failed to push some refs to 'myhost1:/Users/jtang/annex'
-hint: Updates were rejected because a pushed branch tip is behind its remote
-hint: counterpart. Check out this branch and merge the remote changes
-hint: (e.g. 'git pull') before pushing again.
-hint: See the 'Note about fast-forwards' in 'git push --help' for details.
-(Recording state in git...)
-
-manually running a 'git annex sync' usually fixes it, I guess once the sync command runs periodically this problem will go away, is this even OSX specific? I don't quite get the behaviour that is described in [[design/assistant/blog/day_15__its_aliiive]].
-
-> With my changes today, I've seen it successfully recover from this
-> situation. [[done]] --[[Joey]] 
diff --git a/doc/bugs/More_sync__39__ing_weirdness_with_the_assistant_branch_on_OSX/comment_1_377525e70640751e1ead445aeed15efa._comment b/doc/bugs/More_sync__39__ing_weirdness_with_the_assistant_branch_on_OSX/comment_1_377525e70640751e1ead445aeed15efa._comment
deleted file mode 100644
index 77481789c..000000000
--- a/doc/bugs/More_sync__39__ing_weirdness_with_the_assistant_branch_on_OSX/comment_1_377525e70640751e1ead445aeed15efa._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.25"
- subject="comment 1"
- date="2012-06-25T15:45:18Z"
- content="""
-This is indeed the problem I've planned to work on today, as I see it too when things don't start off perfectly in sync.
-"""]]
diff --git a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana.mdwn b/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana.mdwn
deleted file mode 100644
index ee188eb2e..000000000
--- a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-Version 3.20120825 built on my OpenIndiana system just fine, but the latest release gives me this during setup:
-
-    Linking /tmp/git-annex-3.20121017-13013/git-annex-3.20121017/dist/setup/setup ...
-      checking version... 3.20121017
-      checking git... yes
-      checking git version... 1.7.8.2
-      checking cp -a... yes
-      checking cp -p... yes
-      checking cp --reflink=auto... yes
-      checking uuid generator... uuid -m
-      checking xargs -0... yes
-      checking rsync... yes
-      checking curl... yes
-      checking wget... yes
-      checking bup... no
-      checking gpg... no
-      checking lsof... no
-      checking ssh connection caching... yes
-      checking sha1... sha1sum
-      checking sha256... sha256sum
-      checking sha512... sha512sum
-      checking sha224... sha224sum
-      checking sha384... sha384sum
-    Configuring git-annex-3.20121017...
-    Building git-annex-3.20121017...
-    Preprocessing executable 'git-annex' for git-annex-3.20121017...
-    In file included from Mounts.hsc:25:0:
-    Utility/libmounts.h:13:3: warning: #warning mounts listing code not available for this OS [-Wcpp]
-
-    Utility/libkqueue.c:13:23:
-         fatal error: sys/event.h: No such file or directory
-    compilation terminated.
-
-Is it possible to remove the new requirement?  Thanks!
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_1_f3c336ecfee51e074ea3a9fc95301de5._comment b/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_1_f3c336ecfee51e074ea3a9fc95301de5._comment
deleted file mode 100644
index bb1dc688f..000000000
--- a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_1_f3c336ecfee51e074ea3a9fc95301de5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 1"
- date="2012-10-17T17:42:30Z"
- content="""
-kqueue is used by the new assistant and watch features. It seems something else would need to be used for Solaris. I have modified the Makefile to (try to) detect Solaris and disable these features. I assumed your uname would be \"Solaris\", so you may need to modify it slightly.
-"""]]
diff --git a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_2_102c0e998934e84deca92fd1c90145fa._comment b/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_2_102c0e998934e84deca92fd1c90145fa._comment
deleted file mode 100644
index 0a2a2641c..000000000
--- a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_2_102c0e998934e84deca92fd1c90145fa._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="uname on OpenIndiana"
- date="2012-10-17T22:19:04Z"
- content="""
-The uname is actually SunOS, surprisingly enough.  I'll give it a try!
-"""]]
diff --git a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_3_1449dd796ce9f2209f085d4b017a5f33._comment b/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_3_1449dd796ce9f2209f085d4b017a5f33._comment
deleted file mode 100644
index 8feff78d9..000000000
--- a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_3_1449dd796ce9f2209f085d4b017a5f33._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="Doesn't quite work"
- date="2012-10-17T22:23:16Z"
- content="""
-Your Makefile change, even with the uname corrected, had no impact at all.  I'm running \"cabal install\".  When I try just \"make\", I get this error:
-
-
-    Annex.hs:69:28:
-        No instance for (MonadBase IO (StateT AnnexState IO))
-          arising from a use of `liftBase'
-        Possible fix:
-          add an instance declaration for
-          (MonadBase IO (StateT AnnexState IO))
-        In the second argument of `(.)', namely `liftBase'
-        In the expression: Annex . liftBase
-        In an equation for `liftBase': liftBase = Annex . liftBase
-"""]]
diff --git a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_4_c4aa8a4379b2c056ca9b7afcff412bbc._comment b/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_4_c4aa8a4379b2c056ca9b7afcff412bbc._comment
deleted file mode 100644
index eb64afee2..000000000
--- a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_4_c4aa8a4379b2c056ca9b7afcff412bbc._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.23"
- subject="comment 4"
- date="2012-10-18T02:04:47Z"
- content="""
-You might be able to use the cabal file now. (Not sure.. the OS name used there is different from uname.)
-
-cabal may have better luck, the make error suggests that you have too old a version of the haskell transformers-base library installed.
-"""]]
diff --git a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_5_6ca4dd2ad51182edf7198f38b336b9b6._comment b/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_5_6ca4dd2ad51182edf7198f38b336b9b6._comment
deleted file mode 100644
index f37b1d227..000000000
--- a/doc/bugs/Most_recent_git-annex_will_not_build_on_OpenIndiana/comment_5_6ca4dd2ad51182edf7198f38b336b9b6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="Works great!"
- date="2012-10-18T05:34:06Z"
- content="""
-This can be moved to done.
-"""]]
diff --git a/doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn b/doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn
deleted file mode 100644
index 722dac50b..000000000
--- a/doc/bugs/Name_scheme_does_not_follow_git__39__s_rules.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-I can create an annex remote named 'test:/test'. git itself does not allow colons in names, though. The name scheme for an annex should be the same as for git repos themselves.
-
-> What do you mean by "an annex remote"? git-annex uses the same
-> remotes configuration as does git. If you put invalid
-> stuff in .git/config it might handle it slightly different than 
-> git, I don't know. Examples needed. --[[Joey]] 
-
->> What I mean is this:
-
-    % cd 1
-    % git init
-    % git annex init "my:colon"
-    % [...]
-    % cd ../2
-    % git init
-    % git annex init "second"
-    % git remote add "my:colon" ../1
-    fatal: 'my:colon' is not a valid remote name
-
->> -- RichiH
-
->>> I see.. Git annex init does not specifiy a remote's name, it specifies
->>> an arbitrary human-readable description of the repository, which will
->>> be displayed when there is no configured remote corresponding to the
->>> repository. So this is not a bug unless some documentation of that is
->>> unclear. --[[Joey]] 
-
->>>> Nobody spoke up to say it's unclear, so closing as PEBKAC :)
->>>> [[done]] --[[Joey]] 
-
->>>>> I still think git-annex should follow the same rules as git in this regard, but if your design decision is different, I won't try to argue the point :) -- RichiH
diff --git a/doc/bugs/Need_to_manually_install_c2hs_-_3.20121127_and_previous.mdwn b/doc/bugs/Need_to_manually_install_c2hs_-_3.20121127_and_previous.mdwn
deleted file mode 100644
index 924ce06c7..000000000
--- a/doc/bugs/Need_to_manually_install_c2hs_-_3.20121127_and_previous.mdwn
+++ /dev/null
@@ -1,37 +0,0 @@
-What steps will reproduce the problem?
-
-Install git-annex via cabal - either from Hackage or as a manual install. (i.e. <http://git-annex.branchable.com/install/cabal/>)
-
-What is the expected output? What do you see instead?
-
-Expect a clean install.
-
-However, get the following error:
-
-      Configuring gnuidn-0.2...
-      cabal: The program c2hs is required but it could not be found.
-      Failed to install gnuidn-0.2
-      cabal: Error: some packages failed to install:
-      git-annex-3.20121127 depends on gnuidn-0.2 which failed to install.
-      gnuidn-0.2 failed during the configure step. The exception was:
-      ExitFailure 1
-      network-protocol-xmpp-0.4.4 depends on gnuidn-0.2 which failed to install.
-
-What version of git-annex are you using? On what operating system?
-
-git-annex: 3.20121127 (and previous versions)
-
-OS: Mac OSX 10.6.8
-
-
-Please provide any additional information below.
-
-The fix seems as easy as
-
-    cabal install c2hs
-
-Should c2hs be included as a dep got git-annex or is this a bug in gnuidn?
-
-> Apparently cabal does not support automatically installing programs
-> needed for the build. I've updated the cabal installation instructions
-> to document the need to install c2hs. [[done]] --[[Joey]]
diff --git a/doc/bugs/No_progress_bars_with_S3.mdwn b/doc/bugs/No_progress_bars_with_S3.mdwn
deleted file mode 100644
index afa7ba5ee..000000000
--- a/doc/bugs/No_progress_bars_with_S3.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-## What steps will reproduce the problem?
-
-Add new data to a repository with an S3 special remote. Monitor the repository with the web app.
-
-
-## What is the expected output? What do you see instead?
-
-I expect a changing status bar and percentage. Instead I see no changes when an upload becomes active.
-
-
-## What version of git-annex are you using? On what operating system?
-
-3.20130102 on Arch 64-bit.
-
-
-## Please provide any additional information below.
-
-
-When uploading local data to an S3 remote, I see no progress bars. The progress bar area on active uploads stays the same grey as the bar on queued uploads. The status does not change from "0% of...". The uploads are completing, but this makes it very difficult to judge their activity.
-
-The only remotes I currently have setup are S3 special remotes, so I cannot say whether progress bars are working for uploads to other remote types.
-
-> [[done]], this turned out to be a confusion in the progress code;
-> parts were expecting a full number of bytes since the start, while
-> other parts were sending the number of bytes in a chunk. Result was
-> progress bars stuck at 0% often. --[[Joey]]
diff --git a/doc/bugs/No_progress_bars_with_S3/comment_1_33a601201a9fdd2357f1c03e32fa6b9c._comment b/doc/bugs/No_progress_bars_with_S3/comment_1_33a601201a9fdd2357f1c03e32fa6b9c._comment
deleted file mode 100644
index 90d00807d..000000000
--- a/doc/bugs/No_progress_bars_with_S3/comment_1_33a601201a9fdd2357f1c03e32fa6b9c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 1"
- date="2013-01-14T16:31:06Z"
- content="""
-How large are your files? IIRC the S3 progress bar updated with a rather large granularity.
-"""]]
diff --git a/doc/bugs/No_progress_bars_with_S3/comment_2_52361805ced99c22d663b3b1e8a5b221._comment b/doc/bugs/No_progress_bars_with_S3/comment_2_52361805ced99c22d663b3b1e8a5b221._comment
deleted file mode 100644
index 04f823e0b..000000000
--- a/doc/bugs/No_progress_bars_with_S3/comment_2_52361805ced99c22d663b3b1e8a5b221._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="annexuser"
- ip="24.16.193.140"
- subject="comment 2"
- date="2013-01-14T21:26:18Z"
- content="""
-4MB to 8MB
-"""]]
diff --git a/doc/bugs/No_progress_bars_with_S3/comment_3_5903c1c40c4562f4fbaccd1640fedb18._comment b/doc/bugs/No_progress_bars_with_S3/comment_3_5903c1c40c4562f4fbaccd1640fedb18._comment
deleted file mode 100644
index c5ed8246f..000000000
--- a/doc/bugs/No_progress_bars_with_S3/comment_3_5903c1c40c4562f4fbaccd1640fedb18._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="annexuser"
- ip="50.125.41.100"
- subject="comment 3"
- date="2013-01-19T20:40:27Z"
- content="""
-Progress bars do work with a USB remote.
-"""]]
diff --git a/doc/bugs/No_progress_bars_with_S3/comment_4_80799c33e513384894b390fe34ab312a._comment b/doc/bugs/No_progress_bars_with_S3/comment_4_80799c33e513384894b390fe34ab312a._comment
deleted file mode 100644
index 6c00c43d3..000000000
--- a/doc/bugs/No_progress_bars_with_S3/comment_4_80799c33e513384894b390fe34ab312a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="annexuser"
- ip="50.125.41.100"
- subject="comment 4"
- date="2013-01-19T20:41:48Z"
- content="""
-I should also mention that I've uploaded a handful of 30MB files, and I've seen no progress bars on them.
-"""]]
diff --git a/doc/bugs/No_version_information_from_cli.mdwn b/doc/bugs/No_version_information_from_cli.mdwn
deleted file mode 100644
index a0d30db41..000000000
--- a/doc/bugs/No_version_information_from_cli.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-git-annex does not listen to -v, --version or version.
-
-At the very least, it should return both the version of the binary and the version of the object store it supports.
-If it supports several annex versions, they should be listed in a comma-separated fashion.
-If git-annex is called from within an annex, it should print the version of the local object store.
-
-Sample:
-
-    % git annex version
-    git-annex version               : 0.24
-    default object store version    : 3
-    supported object store versions : 2,3
-    local object store version      : 2
-    % 
-
-The above might look like overkill, but it's in a form that will, most likely, never need to be extended.
-
-> Great idea, [[done]] --[[Joey]] 
diff --git a/doc/bugs/OSX_.dmg_unnecessarily_large_and_not_inherently_compressed.mdwn b/doc/bugs/OSX_.dmg_unnecessarily_large_and_not_inherently_compressed.mdwn
deleted file mode 100644
index bf74aebe6..000000000
--- a/doc/bugs/OSX_.dmg_unnecessarily_large_and_not_inherently_compressed.mdwn
+++ /dev/null
@@ -1,68 +0,0 @@
-### Please describe the problem.
-
-The .dmg the OSX build is distributed in  is unnecessarily large (fixed size) and is externally compressed.
-
-I did a quick survey of .dmg images used for distributing other pieces of software which I had downloaded to my Mac, and most of them seem to be the UDBZ or the (older) UDZO formats which are internally compressed with bzip2 or zlib.  According to "man hdiutil", the UDBZ format is supported since 10.4 (Tiger).
-
-Below are a pair of patches: first to enable "make clean" to work on OSX, second to build the .dmg in the UDBZ format and without an explicit size (it seems to infer a correct size).  When I tested building it, it results in a .dmg which is slightly smaller than the old .dmg.bz2
-
-(This will also require a change to remove the .bz2 from the download links elsewhere in the wiki.)
-
-<pre>
-From 251e23bbe66cc63e98089554f91b2528a097e818 Mon Sep 17 00:00:00 2001
-From: Mike Magin <git@mike.magin.org>
-Date: Sun, 17 Nov 2013 08:11:05 -0800
-Subject: [PATCH 1/2] Add explicit path to find invocation in "make clean" target.
-
----
- Makefile | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/Makefile b/Makefile
-index 3f3ed35..5a0cebb 100644
---- a/Makefile
-+++ b/Makefile
-@@ -83,8 +83,8 @@ clean:
- 		Setup Build/InstallDesktopFile Build/EvilSplicer \
- 		Build/Standalone Build/OSXMkLibs \
- 		git-union-merge git-recover-repository
--	find -name \*.o -exec rm {} \;
--	find -name \*.hi -exec rm {} \;
-+	find . -name \*.o -exec rm {} \;
-+	find . -name \*.hi -exec rm {} \;
- 
- Build/InstallDesktopFile: Build/InstallDesktopFile.hs
- 	$(GHC) --make $@
--- 
-1.8.4.3
-
-From e66f767893b5ef70cbf69d420cb589071f88c784 Mon Sep 17 00:00:00 2001
-From: Mike Magin <git@mike.magin.org>
-Date: Sun, 17 Nov 2013 08:40:07 -0800
-Subject: [PATCH 2/2] Change .dmg build to include compression and not be fixed size.
-
----
- Makefile | 3 +--
- 1 file changed, 1 insertion(+), 2 deletions(-)
-
-diff --git a/Makefile b/Makefile
-index 5a0cebb..b6ac549 100644
---- a/Makefile
-+++ b/Makefile
-@@ -162,10 +162,9 @@ osxapp: Build/Standalone Build/OSXMkLibs
- 
- 	./Build/OSXMkLibs $(OSXAPP_BASE)
- 	rm -f tmp/git-annex.dmg
--	hdiutil create -size 640m -format UDRW -srcfolder tmp/build-dmg \
-+	hdiutil create -format UDBZ -srcfolder tmp/build-dmg \
- 		-volname git-annex -o tmp/git-annex.dmg
- 	rm -f tmp/git-annex.dmg.bz2
--	bzip2 --fast tmp/git-annex.dmg
- 
- ANDROID_FLAGS?=-f-XMPP
- # Cross compile for Android.
--- 
-1.8.4.3
-</pre>
-
-> Ah, that never seemed optimal. [[done]] --[[Joey]]
diff --git a/doc/bugs/OSX_alias_permissions_and_versions_problem.mdwn b/doc/bugs/OSX_alias_permissions_and_versions_problem.mdwn
deleted file mode 100644
index f4ebc9d1e..000000000
--- a/doc/bugs/OSX_alias_permissions_and_versions_problem.mdwn
+++ /dev/null
@@ -1,37 +0,0 @@
-What steps will reproduce the problem?
-
-Use assistant and create repository the a folder in home dir.
-Use textedit and save a new txt to the repository folder. 
-
-What is the expected output? What do you see instead?
-
-The alias solution is broken. It should work more like Dropbox.
-Textedit saves the file initially, but it is immediately locked.
-Since it autosaves, it asks to unlock or duplicate.
-Then gives the error:
-"The file “Untitled 16.txt” cannot be unlocked."
-
-If the file exists:
-The document “Untitled 14” could not be saved as “Untitled 14.txt”. You don’t have permission.
-
-If you open a file from the repository (now replaced by a symlink) with textedit, there are other problems:
-- The filename will not be correct (will show the sha hash). 
-- It will ask to unlock, then give the error "You don’t have permission to write to the folder that the file “SHA256E-s8--8985d9832de2e28b5e1af64258c391a34d7528709ef916bac496e698c139020c.txt” is in."
-
-What version of git-annex are you using? On what operating system?
-
-OSX Lion
-git-annex version: 3.20120924
-
-Please provide any additional information below.
-
-Even if you fix these problems, automatic versioning in lion will probably don't work, and the symlinks seem a hackish solution and don't seem intuitive or easy to the end user. 
-The sync should be transparent but it's not, and it's error prone. It would even be best to keep file copies in the git repo and sync them with the original folder than make symlinks.
-
-Dropbox even allows to put a symlink in the dropbox directory, and it will sync the file. 
-
-[[!tag /design/assistant/OSX]]
-
-> Now the assistant creates new repositories using direct mode on OSX.
-> In direct mode, there is no locking of files; they can be modified
-> directly. [[done]] --[[Joey]]
diff --git a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_1_4fabe32e7e626e6ca23aa0b6f449c4c6._comment b/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_1_4fabe32e7e626e6ca23aa0b6f449c4c6._comment
deleted file mode 100644
index 74a20d08e..000000000
--- a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_1_4fabe32e7e626e6ca23aa0b6f449c4c6._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlatTbI0K-qydpeYHl37iseqPNvERcdIMk"
- nickname="Tiago"
- subject="comment 1"
- date="2012-09-26T23:38:51Z"
- content="""
-After looking more into the git annex working, I understand the use of symlinks, but they are not always correctly handled by OSX. 
-
-
-Apple's Timemachine uses hardlinks for example... 
-
-
-Not being able to easily edit files that are in the repo without problems or quirks makes it unusable as a dropbox replacement and version control, which is a shame.
-"""]]
diff --git a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_2_064d60fcc8366a70958540bc145e611a._comment b/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_2_064d60fcc8366a70958540bc145e611a._comment
deleted file mode 100644
index 78125262e..000000000
--- a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_2_064d60fcc8366a70958540bc145e611a._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlatTbI0K-qydpeYHl37iseqPNvERcdIMk"
- nickname="Tiago"
- subject="comment 2"
- date="2012-09-26T23:50:55Z"
- content="""
-It seems many people complain about symlink behavior in Lion and Mountain Lion.
-I never used symlinks to files often, only to folders.
-I hope you can solve this problems and make it work correctly in OSX, or use hardlinks instead.
-Git annex sound awesome, but the people using the assistant will want KISS behavior, and don't even know what a symbolic link is.
-"""]]
diff --git a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_3_6c72d4f40ea0a9566a1185901beff5ba._comment b/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_3_6c72d4f40ea0a9566a1185901beff5ba._comment
deleted file mode 100644
index 8ef5e6cc5..000000000
--- a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_3_6c72d4f40ea0a9566a1185901beff5ba._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlatTbI0K-qydpeYHl37iseqPNvERcdIMk"
- nickname="Tiago"
- subject="comment 3"
- date="2012-09-26T23:57:18Z"
- content="""
-Ok, so it seems  Sharebox solves all this problems...you might want to integrate sharebox into the assistant, so non-techie people can treat the repos as mutable.
-Maybe make a mutable/unmutable toggle in the gui or somethink like that?
-
-What I don't understand is the need for kqueue, if the files are not supposed to be written to without unlocking, why not use FSEvents and only monitor the folders for new files.
-
-http://git-annex.branchable.com/news/sharebox_a_FUSE_filesystem_for_git-annex
-
-"""]]
diff --git a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_4_8a11f404bb72a1aeb2290744cce2d00d._comment b/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_4_8a11f404bb72a1aeb2290744cce2d00d._comment
deleted file mode 100644
index aeacce31e..000000000
--- a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_4_8a11f404bb72a1aeb2290744cce2d00d._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlatTbI0K-qydpeYHl37iseqPNvERcdIMk"
- nickname="Tiago"
- subject="comment 4"
- date="2012-09-27T00:06:31Z"
- content="""
-Seems sharebox development stopped a year ago...now that you are working on the assistant, which sound awesome, I think you really should consider pick up the sharebox development and integrate it.
-
-Too bad I missed kickstarter, but I might donate now. 
-I just find it wierd that it said \"Like Dropbox\" on the title, but sharebox-like functionality is not on the roadmap, and being able to easily edit the files is a big feature of dropbox.
-
-"""]]
diff --git a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_5_30888607199d6a48b76d0c48f5aa4f64._comment b/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_5_30888607199d6a48b76d0c48f5aa4f64._comment
deleted file mode 100644
index d95d8f149..000000000
--- a/doc/bugs/OSX_alias_permissions_and_versions_problem/comment_5_30888607199d6a48b76d0c48f5aa4f64._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="I agree"
- date="2012-10-18T07:11:20Z"
- content="""
-I really can't think of any way that Git annex + the assistant is like Dropbox.  The Annex is not usable for even a single of the uses cases for which I also use Dropbox.  I think this \"branding\" of annex should be dropped, or else it actually needs to acquire the features of Dropbox.
-"""]]
diff --git a/doc/bugs/OSX_build_broken.mdwn b/doc/bugs/OSX_build_broken.mdwn
deleted file mode 100644
index a68531bec..000000000
--- a/doc/bugs/OSX_build_broken.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-### Please describe the problem.
-
-The OSX webapp doesn't start on the current OSX 10.7.5 builds. 
-
-### What steps will reproduce the problem?
-
-Download git-annex from http://downloads.kitenet.net/git-annex/OSX/current/10.7.5_Lion/git-annex.dmg and install it by copying it to Application. Try to launch it then. The result is a message in the system log saying "git-annex unknown command webapp" and then the usage information.
-
-### What version of git-annex are you using? On what operating system?
-
-The current version as downloaded from http://downloads.kitenet.net/git-annex/OSX/current/10.7.5_Lion/git-annex.dmg on OSX 10.7.5
-
-> OS Lion builds are no longer being made. [[done]] --[[Joey]]
diff --git a/doc/bugs/OSX_build_broken/comment_1_0b570aa6c58effeace2a989184c9c601._comment b/doc/bugs/OSX_build_broken/comment_1_0b570aa6c58effeace2a989184c9c601._comment
deleted file mode 100644
index 05079b2ae..000000000
--- a/doc/bugs/OSX_build_broken/comment_1_0b570aa6c58effeace2a989184c9c601._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 1"
- date="2013-12-15T19:31:39Z"
- content="""
-This should only affect Lion. Jimmy will need to install missing dependencies.
-
-In the meantime, I have reverted the lion build to the previous release, which I assume didn't have this problem. (Currently downloading that release my my archive, which git-annex says will take around 5 more minutes.)
-"""]]
diff --git a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__.mdwn b/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__.mdwn
deleted file mode 100644
index ac5c66951..000000000
--- a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-**What steps will reproduce the problem?**
-
-Either double click on the app or from the terminal
-
-    $ open /Applications/git-annex.app
-
-**What is the expected output? What do you see instead?**
-
-I'd expect to see git-annex run.  "git-annex" doesn't run and what I see (in the terminal) is:
-
-    LSOpenURLsWithRole() failed with error -10810 for the file /Applications/git-annex.app.
-
-**What version of git-annex are you using? On what operating system?**
-
-*git-annex*: 3.20121017
-
-*git-annex.app*: ???
-
-*OS*: OSX 10.6.8 64 bit
-
-
-**Please provide any additional information below.**
-
-[[!tag /design/assistant/OSX]]
-
-> This was fixed a while ago. [[done]] --[[Joey]] 
diff --git a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_1_0dfa839f1ba689b23f811787515b8cff._comment b/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_1_0dfa839f1ba689b23f811787515b8cff._comment
deleted file mode 100644
index 896ae26ce..000000000
--- a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_1_0dfa839f1ba689b23f811787515b8cff._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://a-or-b.myopenid.com/"
- ip="220.244.41.108"
- subject="comment 1"
- date="2012-10-28T06:46:40Z"
- content="""
-My best advice to anyone running into this is simply install using cabal.  It works.  :-)
-"""]]
diff --git a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_2_612b947eb5474f6d792a833e33105665._comment b/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_2_612b947eb5474f6d792a833e33105665._comment
deleted file mode 100644
index 0732cbfcf..000000000
--- a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_2_612b947eb5474f6d792a833e33105665._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 2"
- date="2012-10-28T20:11:43Z"
- content="""
-I sort of got a feeling that this build might have issues on OSX 10.6, I create the OSX builds on 10.7.
-"""]]
diff --git a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_3_549b8bcae6f1f8b21932b734e32fbdd1._comment b/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_3_549b8bcae6f1f8b21932b734e32fbdd1._comment
deleted file mode 100644
index c5ada3d1d..000000000
--- a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_3_549b8bcae6f1f8b21932b734e32fbdd1._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnKgoTWEDuAqxBT7LnQVNJBmI0wajSgORA"
- nickname="Martin"
- subject="Same on 10.8.2"
- date="2012-10-31T20:17:17Z"
- content="""
-I get the same error on OSX 10.8.2.
-"""]]
diff --git a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_4_23078dfea127fa3ef20696eb10ce964c._comment b/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_4_23078dfea127fa3ef20696eb10ce964c._comment
deleted file mode 100644
index 6b0278fe8..000000000
--- a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_4_23078dfea127fa3ef20696eb10ce964c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlfvsw_0TFUvMcHVBRw1D1UmAaOJ3VsNSU"
- nickname="chee"
- subject="comment 4"
- date="2012-11-16T03:14:50Z"
- content="""
-Same error here, 10.8.2
-
-https://snaek.org/resources/ff40b1c2fd9486614c7df72aaeca9755fb43d6ff.png
-"""]]
diff --git a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_5_7da5ef8325b8787bbf1c6e2c17b1142e._comment b/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_5_7da5ef8325b8787bbf1c6e2c17b1142e._comment
deleted file mode 100644
index 2f7c1184b..000000000
--- a/doc/bugs/OSX_git-annex.app_error:__LSOpenURLsWithRole__40____41__/comment_5_7da5ef8325b8787bbf1c6e2c17b1142e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.6.49"
- subject="comment 5"
- date="2012-11-26T23:52:52Z"
- content="""
-The OSX app has been updated for today's release, and includes a lot of missing libraries. I don't understand this error message, but on the off chance it was caused by some of the missing libraries, it could conceviably be fixed. Your testing of it would be appreciated.
-"""]]
diff --git a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp.mdwn b/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp.mdwn
deleted file mode 100644
index 3a93c3881..000000000
--- a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-### Please describe the problem.
-
-If the assistant is not running, I can successfully open the git-annex application, which will trigger my browser to open a new tab with the assistant interface.
-
-However, once that has been done one time, there appears to be no way to get back to the assistant if the tab is closed.  Attempting to open the application again while the assistant is running in the background results in nothing happening at all. 
-
-### What steps will reproduce the problem?
-
-1. Open git-annex.app
-2. See assistant and then close the browser tab
-3. Open git-annex.app again
-4. Nothing happens
-
-### What version of git-annex are you using? On what operating system?
-
-Version 4.20130723-ge023649 on OS X 10.8.4.
-
-### Please provide any additional information below.
-
-From .git/annex/daemon.log:
-
-[[!format sh """
-[2013-07-28 00:01:08 CDT] main: starting assistant version 4.20130723-ge023649
-
-(scanning...) [2013-07-28 00:01:08 CDT] Watcher: Performing startup scan
-(started...)
-"""]]
-
-> [[done]]; I added the `&` to git-annex-shell.
-> Hopefully that does not cause any other unwanted behavior..
-> --[[Joey]]
diff --git a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_1_2653fe701a1bb20254f3d6b90f10a43b._comment b/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_1_2653fe701a1bb20254f3d6b90f10a43b._comment
deleted file mode 100644
index 7982f30f2..000000000
--- a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_1_2653fe701a1bb20254f3d6b90f10a43b._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkfHTPsiAcHEEN7Xl7WxiZmYq-vX7azxFY"
- nickname="Vincent"
- subject="Having trouble reproducing"
- date="2013-07-29T11:14:46Z"
- content="""
-I have the same platform (os/x 10.8.4) and git-annex revision (4.20130723-ge023649) but am unable to reproduce this.
-I may have seen it in the last couple of months (http://git-annex.branchable.com/bugs/wishlist:_simple_url_for_webapp/) but it now does not seem to be affecting me; joey's prescription works.
-
-Additional info:
-
-If I stop the daemon via the webapp menu, close the tab and start again via the app icon (in the Dock), I get the tab opening as expected.
-
-Sometimes, if I have the assistant in an open tab and doubleclick the app icon again, I get another tab with the assistant in it and the same auth= string.
-Other times, I don't. It's unclear to me what the difference is. Possibly relevant - the time that I saw the second tab appear was when the existing tab was left over from the machine being in sleep mode, but it was definitely responding to mouse clicks etc (ie not a 'dead' page) and the daemon was still running in the background. After stopping and starting, I never saw the second tab instance appear again.
-
-Browser is chrome 28.0.1500.71.
-"""]]
diff --git a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_2_d9ce701d077e40f39b142ce2cc570a3b._comment b/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_2_d9ce701d077e40f39b142ce2cc570a3b._comment
deleted file mode 100644
index 9f31c76d5..000000000
--- a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_2_d9ce701d077e40f39b142ce2cc570a3b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnaH44G3QbxBAYyDwy0PbvL0ls60XoaR3Y"
- nickname="Nigel"
- subject=".git/annex/webapp.html"
- date="2013-07-29T12:08:04Z"
- content="""
-after accidentally closing the webapp tab, I reopened the link from the above file and it seemed to work
-"""]]
diff --git a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_3_14964ab68253dc1a8903d14a821b8b40._comment b/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_3_14964ab68253dc1a8903d14a821b8b40._comment
deleted file mode 100644
index 6f66fdb70..000000000
--- a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_3_14964ab68253dc1a8903d14a821b8b40._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl-BU4KfFktO2-bqaFmlArHta0Oy7zJrCs"
- nickname="J. Ryan"
- subject="Thanks!"
- date="2013-07-29T14:44:42Z"
- content="""
-I was unaware of both `git-annex-webapp` command as well as the `webapp.html` file it appears to open, so now I have two approaches to get back into the webapp.
-
-It does seem like it would be nice if future double-clicks on the app itself triggered the page to open, but at least now I have some way to get there.
-"""]]
diff --git a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_4_4a579e9a13305ab4157f4b3eba46b92d._comment b/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_4_4a579e9a13305ab4157f4b3eba46b92d._comment
deleted file mode 100644
index e8337926f..000000000
--- a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_4_4a579e9a13305ab4157f4b3eba46b92d._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.21"
- subject="comment 4"
- date="2013-07-30T18:06:05Z"
- content="""
-There's clearly something not quite right with how the program is started on OSX. I've had reports about the app icon \"bouncing\" for a long time, and now this. 
-
-Since I do not own a Mac, and only have VNC access to a Mac desktop one for about 1 hour a week (and that's pretty slow), doing anything to improve this is quite a low priority background task for me.
-
-It seems that, as a non-Cocoa application, there are only a couple of behaviors that git-annex could have that play into this. 
-
-Perhaps the problem is that if the git-annex assistant daemon is not already running (it's supposed to autostart on login, but this may not be working, or perhaps git-annex has only just been installed and has not started yet), git-annex-webapp runs the daemon, and keeps it running, in the foreground. Perhaps this is interpreted by the GUI as an app that has not finished starting up, or as an app that is already running so it does not re-run it when the icon is clicked on again (which would run git-annex webapp and have it open a new browser window). This should be easy to play around with, by just editing the `git-annex-webapp` shell script. For example, adding a \"&\" at the end of the last line in the file would make it instead run in the background.
-
-Or, the problem might be with the .plist file for the app. Perhaps there's some change that could be made to it that would clue OSX in on how git-annex works.
-"""]]
diff --git a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_5_2a710960dc3a177ce62ef92f8546c496._comment b/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_5_2a710960dc3a177ce62ef92f8546c496._comment
deleted file mode 100644
index f3505ba60..000000000
--- a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_5_2a710960dc3a177ce62ef92f8546c496._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl-BU4KfFktO2-bqaFmlArHta0Oy7zJrCs"
- nickname="J. Ryan"
- subject="comment 5"
- date="2013-07-30T18:44:00Z"
- content="""
-Joey: Success!  I was able to get things working properly by backgrounding the app by adding `&` at the end of `git-annex-webapp` like you suggested.
-
-After doing that, I am able to relaunch the OS X app as many times as I want, and each time I get a new tab in my browser as desired.
-
-I guess if it's left in the foreground, OS X thinks \"there's already an instance of that app running\" and does nothing.  If it were a GUI app, it would focus the GUI app in that case, but with a shell script there's nothing really for it to do, so that sort of explains the behavior.  
-"""]]
diff --git a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_6_a4ad73530cd0f6621bcc6394d5f39af7._comment b/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_6_a4ad73530cd0f6621bcc6394d5f39af7._comment
deleted file mode 100644
index a5f2d4fb1..000000000
--- a/doc/bugs/OS_X_10.8:_Can__39__t_reopen_webapp/comment_6_a4ad73530cd0f6621bcc6394d5f39af7._comment
+++ /dev/null
@@ -1,41 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkfHTPsiAcHEEN7Xl7WxiZmYq-vX7azxFY"
- nickname="Vincent"
- subject="seems to work"
- date="2013-07-31T09:37:36Z"
- content="""
-I tried this as well.
-
-    % diff -u /Applications/git-annex.app/Contents/MacOS/git-annex-shell{.old,}
-    --- /Applications/git-annex.app/Contents/MacOS/git-annex-shell.old	2013-07-31 19:32:28.000000000 +1000
-    +++ /Applications/git-annex.app/Contents/MacOS/git-annex-shell	2013-07-23 14:12:36.000000000 +1000
-    @@ -22,4 +22,4 @@
-     	export GIT_ANNEX_APP_BASE
-     fi
-     
-    -\"$base/runshell\" git-annex-shell
-    +\"$base/runshell\" git-annex-shell \"$@\"
-
-    % ps ax|grep git|grep -v grep |wc
-    0    0     0
-
-    <click the gui app icon>
-    <a new browser tab opens, running the assistant>
-    % ps ax|grep git |grep -v grep
-    33124   ??  S      0:00.40 git-annex webapp -psn_0_31972988
-    33133   ??  S      0:00.00 git --git-dir=/Users/me/annex/.git --work-tree=/Users/me/annex cat-file --batch
-    33162   ??  S      0:00.00 git --git-dir=/Users/me/annex/.git --work-tree=/Users/me/annex cat-file --batch
-    33174   ??  S      0:00.00 git --git-dir=/Users/me/annex/.git --work-tree=/Users/me/annex cat-file --batch
-    33177   ??  S      0:00.00 git --git-dir=/Users/me/annex/.git --work-tree=/Users/me/annex check-attr -z --stdin annex.backend annex.numcopies --
-
-    <click the gui app icon again>
-    <a new browser tab opens, running the assistant. the original remains.>
-    % ps ax|grep git |grep -v grep
-    33124   ??  S      0:00.46 git-annex webapp -psn_0_31972988
-    33133   ??  S      0:00.00 git --git-dir=/Users/me/annex/.git --work-tree=/Users/me/annex cat-file --batch
-    33162   ??  S      0:00.00 git --git-dir=/Users/me/annex/.git --work-tree=/Users/me/annex cat-file --batch
-    33174   ??  S      0:00.00 git --git-dir=/Users/me/annex/.git --work-tree=/Users/me/annex cat-file --batch
-    33177   ??  S      0:00.00 git --git-dir=/Users/me/annex/.git --work-tree=/Users/me/annex check-attr -z --stdin annex.backend annex.numcopies --
-
-HTH
-"""]]
diff --git a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple.mdwn b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple.mdwn
deleted file mode 100644
index 6d6df52a5..000000000
--- a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple.mdwn
+++ /dev/null
@@ -1,67 +0,0 @@
-### Please describe the problem.
-Internal Server Error when setting up new annex and git push.default set to simple.
-
-### What steps will reproduce the problem?
-git v1.8.2.1 installed on mac os x 10.8.3 via brew
-
-Set push.default = simple (for 2.0-style push handling)
-Point git-annex-assistant at a directory.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version 4.20130422-gb9341fd (from annex-assistant's footer)
-git version 1.8.2.1
-Mac OS X 10.8.3
-
-### Please provide any additional information below.
-
-Changing the push.default to "matching" 
-
-The error message as shown was:
-
-Internal Server Error
-git init failed!
-Output:
-error: Malformed value for push.default: simple
-error: Must be one of nothing, matching, tracking or current.
-fatal: bad config file line 22 in /Users/nhyde/.gitconfig
-
-My .gitconfig is as follows:
-
-[user]
-    email = nhyde@example.com
-    #email = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-    name = Nathan Hyde
-[alias]
-    st = status
-    ci = commit
-    br = branch
-    co = checkout
-    df = diff
-    lg = log -p
-    who = shortlog -s --
-    fs = flow feature start
-    ff = flow feature finish
-[color]
-    ui = true
-[core]
-    excludesfile = /Users/nhyde/.gitignore_global
-    ignorecase = false
-    editor = vim
-[push]
-    default = matching
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/debug.log
-
-
-# End of transcript or log.
-"""]]
-
-> Closing this because all autobuilders have been upgraded
-> to a more recent version of git. done --[[Joey]] 
->> Reopened, because the Linux autobuilds have been downgraded to Debian
->> stable and have this problem again. --[[Joey]]
-
->>> Closing again! Autobuilders all run unstable and will have a current
->>> git. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_1_971224d2c0c0ce8d4530b1991508f849._comment b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_1_971224d2c0c0ce8d4530b1991508f849._comment
deleted file mode 100644
index 2d5bb923b..000000000
--- a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_1_971224d2c0c0ce8d4530b1991508f849._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-13T19:02:38Z"
- content="""
-I can't think of a way to make the assistant detect that `~/.gitconfig` contains settings not supported by the version of git bundled with git-annex. Even if I could detect it, what could it do? It could perhaps prevent the config file being used by git-annex, but that could have other unwanted consequences. 
-
-An error message like this seems about as good as this situation can be handled. However, the version of git bundled with git-annex should be kept up-to-date to prevent this kind of problem as much as possible. I don't currently have a good way to ensure that happens; it takes whatever version of git is installed on the build system.
-
-I'm going to try to get the autobuilders all updated to git 1.8.2, at least.
-"""]]
diff --git a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_2_6866f96277dbe83a8aadcdeb426b6750._comment b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_2_6866f96277dbe83a8aadcdeb426b6750._comment
deleted file mode 100644
index fc4f16500..000000000
--- a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_2_6866f96277dbe83a8aadcdeb426b6750._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-05-13T19:08:09Z"
- content="""
-Done for both Linux autobuilds. OSX still needs updating; emailed the owners of those builds.
-"""]]
diff --git a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_3_eaed9b5532e30e401f50193a72b98310._comment b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_3_eaed9b5532e30e401f50193a72b98310._comment
deleted file mode 100644
index bee277aa6..000000000
--- a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_3_eaed9b5532e30e401f50193a72b98310._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmTNrhkVQ26GBLaLD5-zNuEiR8syTj4mI8"
- nickname="Juan"
- subject="Still happening in the linux autobuild (08/22/2013)"
- date="2013-08-23T02:04:42Z"
- content="""
-I've seen that git-annex for linux is still coming with git 1.7, which causes problems with my installed git (1.8.1.2).
-Wasn't that corrected in autobuilds?
-Thanks in advance.
-Keep up the good work.
-Regards,
-       Juan
-"""]]
diff --git a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_4_1fab407f3823ce8cec87f5df55e49f8c._comment b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_4_1fab407f3823ce8cec87f5df55e49f8c._comment
deleted file mode 100644
index 2c9c33c8e..000000000
--- a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_4_1fab407f3823ce8cec87f5df55e49f8c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 4"
- date="2013-08-23T17:41:32Z"
- content="""
-It was done for the autobuilds, but then I switched them to build using Debian stable, which still has git 1.7, and there is not currently a backport of a newer git to stable for me to use.
-"""]]
diff --git a/doc/bugs/On_Windows__44___annex_get_fails_with_HTTP_Remote__44___but_believes_it_has_succeeded..mdwn b/doc/bugs/On_Windows__44___annex_get_fails_with_HTTP_Remote__44___but_believes_it_has_succeeded..mdwn
deleted file mode 100644
index b34befcc0..000000000
--- a/doc/bugs/On_Windows__44___annex_get_fails_with_HTTP_Remote__44___but_believes_it_has_succeeded..mdwn
+++ /dev/null
@@ -1,180 +0,0 @@
-### Please describe the problem.
-On Windows, with a remote annex configured for HTTP access, attempting to annex get a file will not result in the content being downloaded, but will download a 404 error page as the file.
-
-### What steps will reproduce the problem?
-1. Create an annex (A1) on a Linux system.
-2. "git update-server-info"
-3. run an HTTP server with, a directory up. python -m SimpleHTTPServer
-4. on a Windows system, clone the annex with 'git clone http://remote_host/annex_dir/.git'
-5. "git annex get <file>"
-
-the resulting file will not have the correct content, but rather a 404 error page. In addition, subsequent attempts to "git annex get <file>" will fail, unless you "git annex drop <file>" first. (it appears to believe it correctly retrieved the file).
-
-
-### What version of git-annex are you using? On what operating system?
-Windows 7: 4.20140627-g8a36ec5 (from the git-annex download page)
-
-Debian Linux: 3.20120629 (from the package manager)
-
-### Please provide any additional information below.
-After some debugging, I believe the issue is related to the way git-annex uses curl. it appears that git-annex uses the return code of curl or wget to determine if a download was successful, but curl by default will return status code 0 on a 404, unless the -f option is used (which it is not).
-
-getting git-annex on windows to use wget works around the issue.
-
-
-
-###Full Transcript
-
-#### 1. setup of linux repo
-[[!format sh """
-test-git-annex@linux_host:~/test_annex$ git version
-git version 1.7.10.4
-test-git-annex@linux_host:~/test_annex$ git annex version
-git-annex version: 3.20120629
-local repository version: 3
-default repository version: 3
-supported repository versions: 3
-upgrade supported from repository versions: 0 1 2
-test-git-annex@linux_host: ~test-git-annex@linux_host:~$ mkdir test_annex
-test-git-annex@linux_host: ~test-git-annex@linux_host:~$ cd test_annex/
-test-git-annex@linux_host:~/test_annex$ git init .
-Initialized empty Git repository in /home/test-git-annex/test_annex/.git/
-test-git-annex@linux_host:~/test_annex$ annex init laptop
-init laptop ok
-(Recording state in git...)
-~/test_annextest-git-annex@linux_host:~/test_annex$ echo "this is some content" > file1.txt
-test-git-annex@linux_host:~/test_annex$ git annex add file1.txt
-add file1.txt (checksum...) ok
-(Recording state in git...)
-test-git-annex@linux_host:~/test_annex$ git commit -a -m "initial commit"
-[master (root-commit) 821c6c1] initial commit
- 1 file changed, 1 insertion(+)
- create mode 120000 file1.txt
-test-git-annex@linux_host:~/test_annex$ ls -l
-total 4
-lrwxrwxrwx 1 test-git-annex test-git-annex 178 Jul  6 11:33 file1.txt -> .git/annex/objects/J9/m6/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729
-test-git-annex@linux_host:~/test_annex$ cat file1.txt 
-this is some content
-"""]]
-
-#### 2. set up and run http server
-[[!format sh """
-test-git-annex@MrLinuxTablet:~/test_annex$ git update-server-info
-cd ..
-test-git-annex@MrLinuxTablet:~$ python -m SimpleHTTPServer
-Serving HTTP on 0.0.0.0 port 8000 ...
-
-"""]]
-
-#### 3. Set up Windows, clone repo, init annex
-
-[[!format sh """
-
-#Windows 7
-#download and install git from git-scm.com/download/win
-#Git-1.8.3-preview20130601.exe
-#on install, selecting "Run Git from the Windows Command Prompt"
-#on install, selecting "checkout as-is, commit as-is"
-#installs to C:\Program Files (x86)\Git
-#download and install git-annex from http://git-annex.branchable.com/install/
-#git-annex-installer.exe
-#need to right-click 'run as administrator', per reported bug (link here)
-#installs to C:\Program Files (x86)\Git\cmd
-#also installs some utilities, including wget.exe
-
-C:\Users\test-git-annex>git clone http://192.168.0.8:8000/test_annex/.git
-Cloning into 'test_annex'...
-
-C:\Users\test-git-annex>cd test_annex
-
-C:\Users\test-git-annex\test_annex>dir
- Volume in drive C has no label.
-
- Directory of C:\Users\test-git-annex\test_annex
-
-<DIR>          .
-<DIR>          ..
-              178 file1.txt
-               1 File(s)            178 bytes
-
-C:\Users\test-git-annex\test_annex>type file1.txt
-.git/annex/objects/J9/m6/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729
-
-C:\Users\test-git-annex\test_annex>git annex init windows
-init windows
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-ok
-(Recording state in git...)
-
-"""]]
-
-####4. annex get
-
-[[!format sh """
-#copy Git\bin\libcurl.dll to Git\bin\libcurl-4.dll
-
-C:\Users\test-git-annex\test_annex>git annex -vd get file1.txt
-[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","ls-files","--cached","-z","--","file1.txt"]
-get file1.txt [<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","show-ref","git-annex"]
-[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","show-ref","--hash","refs/heads/git-annex"]
-[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","log","refs/heads/git-annex..36508d74a05fd93daee965f2f73c977852e4b626","--oneline","-n1"]
-[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","log","refs/heads/git-annex..304263841906c0b4dda39d0fdbe54e4af4307cb8","--oneline","-n1"]
-(merging origin/git-annex into git-annex...)
-[<datetime>] chat: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","cat-file","--batch"]
-[<datetime>] feed: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","update-index","-z","--index-info"]
-[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","304263841906c0b4dda39d0fdbe54e4af4307cb8"]
-[<datetime>] chat: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","hash-object","-t","blob","-w","--stdin","--no-filters"]
-[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","log","304263841906c0b4dda39d0fdbe54e4af4307cb8..refs/heads/git-annex","--oneline","-n1"]
-(Recording state in git...)
-[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","write-tree"]
-[<datetime>] chat: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","commit-tree","103a0273cf24deec587295845f761b172a63ea19","-p","refs/heads/git-annex","-p","304263841906c0b4dda39d0fdbe54e4af4307cb8"]
-[<datetime>] call: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","update-ref","refs/heads/git-annex","538f6b44a762be415ec6fef2b6644c10bc1f3780"]
-[<datetime>] call: curl ["-s","-L","-C","-","-#","-o","C:\\Users\\test-git-annex\\AppData\\Local\\Temp\\git-annex8156.tmp","http://192.168.0.8:8000/test_annex/.git/config"]
-[<datetime>] read: git ["config","--null","--list","--file","C:\\Users\\test-git-annex\\AppData\\Local\\Temp\\git-annex8156.tmp"]
-[<datetime>] call: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","config","remote.origin.annex-uuid","64000156-e66a-11e2-aa76-131bb0a453f3"]
-[<datetime>] read: git ["config","--null","--list"]
-(from origin...) [<datetime>] call: curl ["-L","-C","-","-#","-o","C:\\Users\\test-git-annex\\test_annex\\.git\\annex\\tmp\\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729","http://192.168.0.8:8000/test_annex/.git/annex\\objects\\c96\\53e\\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729\\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729"]
-######################################################################## 100.0%
-ok
-[<datetime>] chat: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","hash-object","-w","--stdin-paths","--no-filters"]
-[<datetime>] feed: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","update-index","-z","--index-info"]
-[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","show-ref","--hash","refs/heads/git-annex"]
-(Recording state in git...)
-[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","write-tree"]
-[<datetime>] chat: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","commit-tree","b81dc8e53f4c02d433288d7f073be501d27c3648","-p","refs/heads/git-annex"]
-[<datetime>] call: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","update-ref","refs/heads/git-annex","949181f4978c2654e156f1e4250f67135ddc2774"]
-
-C:\Users\test-git-annex\test_annex>git annex find .
-file1.txt
-
-C:\Users\test-git-annex\test_annex>type file1.txt
-<head>
-<title>Error response</title>
-</head>
-<body>
-<h1>Error response</h1>
-<p>Error code 404.
-<p>Message: File not found.
-<p>Error code explanation: 404 = Nothing matches the given URI.
-</body>
-"""]]
-
-#### http server output from above
-
-[[!format sh """
-192.168.0.2 - - [<datetime>] "GET /test_annex/.git/annex\objects\c96\53e\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 HTTP/1.1" 404 -
-192.168.0.2 - - [<datetime>] code 404, message File not found
-"""]]
-
-> This seems to be two distinct bugs. First, curl was not propigating the exit
-> status. I already fixed that. 
-> 
-> Second, it's using DOS style path separators when constructing the url.
-> `http://192.168.0.8:8000/test_annex/.git/annex\\objects\\c96`
-> I've put in an (ugly) fix for that. [[done]] --[[Joey]]
diff --git a/doc/bugs/On_Windows__44___wget_is_not_used__44___even_if_available.mdwn b/doc/bugs/On_Windows__44___wget_is_not_used__44___even_if_available.mdwn
deleted file mode 100644
index 5420b986c..000000000
--- a/doc/bugs/On_Windows__44___wget_is_not_used__44___even_if_available.mdwn
+++ /dev/null
@@ -1,67 +0,0 @@
-### Please describe the problem.
-On Windows, with a remote repository configured for HTTP access, wget is never used, even if it's available in the system. curl is always used.
-
-### What steps will reproduce the problem?
-1. Set up an annex on a remote system, configure it for HTTP access, run an HTTP server.
-2. over HTTP, clone it to Windows
-3. "annex get -vd <file>"
-4. note that curl is used.
-
-
-### What version of git-annex are you using? On what operating system?
-Windows 7: 4.20140627-g8a36ec5 (from the git-annex download page)
-
-### Additional Info
-After some debugging, it appears the issue is that git-annex looks to see if the file 'wget' is available in any directory on the PATH. on windows, wget is installed as 'wget.exe', and the file 'wget' does not exist anywhere. creating a file named 'wget' works around the issue. (wget.exe appears to still be the file used)
-
-###Full Transcript
-1. remote annex is created on host 192.168.0.8, with file "file1.txt"
-[[!format sh """
-#Windows 7
-#download and install git from git-scm.com/download/win
-#Git-1.8.3-preview20130601.exe
-#on install, selecting "Run Git from the Windows Command Prompt"
-#on install, selecting "checkout as-is, commit as-is"
-#installs to C:\Program Files (x86)\Git
-#download and install git-annex from http://git-annex.branchable.com/install/
-#git-annex-installer.exe
-#need to right-click 'run as administrator', per reported bug (link here)
-#installs to C:\Program Files (x86)\Git\cmd
-#also installs some utilities, including wget.exe
-
-C:\Users\test-git-annex>git clone http://192.168.0.8:8000/test_annex/.git
-Cloning into 'test_annex'...
-
-C:\Users\test-git-annex>cd test_annex
-
-C:\Users\test-git-annex\test_annex>dir
- Volume in drive C has no label.
-
- Directory of C:\Users\test-git-annex\test_annex
-
-<DIR>          .
-<DIR>          ..
-              178 file1.txt
-               1 File(s)            178 bytes
-
-C:\Users\test-git-annex\test_annex>type file1.txt
-.git/annex/objects/J9/m6/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729
-
-C:\Users\test-git-annex\test_annex>git annex init windows
-init windows
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-ok
-(Recording state in git...)
-
-C:\Users\test-git-annex\test_annex> git annex get file.txt
-#fails, with error dialog box, indicating libcurl-4.dll is missing, indicating git-annex is trying to use curl.
-
-"""]]
-
-> I fixed this immediately after it was mentioned on IRC. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Partial_direct__47__indirect_repo.mdwn b/doc/bugs/Partial_direct__47__indirect_repo.mdwn
deleted file mode 100644
index 11cf7a1e8..000000000
--- a/doc/bugs/Partial_direct__47__indirect_repo.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-Setup:
-
-* Fresh install of Debian Wheezy on machines A & B, git-annex 4.20130227 pulled in from unstable
-* On both machines, clone old repository which contains both annexed files and a three small files checked straight into git
-
-Steps:
-
-* On both machines, use webapp to create `~/.config/git-annex/autostart` by just firing it up and typing in location of existing repository
-* Move a new file into B's annex, in a subdirectory that is preferred on both A & B
-
-Expected:
-
-* The new file is copied over to A and everything remains in indirect mode
-* Three files checked straight into git remain checked straight into git (see below for why this is a variant on [[bugs/Switching_between_direct_and_indirect_stomps_on___39__regular__39___git_files/]])
-
-Actual:
-
-* New file copied over but seems to be in direct mode, while all the other content that is present is still symlinked
-* Files checked into git converted to direct mode files too (can tell this has happened by following step:)
-* Typing `git annex indirect` on A & B shows conversion of precisely four files (three files originally checked into git and new file added to B ) back to indirect
-
-Thanks.
-
-> [[done]], webapp now avoids changing existing repos here. --[[Joey]]
diff --git a/doc/bugs/Partial_direct__47__indirect_repo/comment_1_42344fce051d759f95215c985e9d1135._comment b/doc/bugs/Partial_direct__47__indirect_repo/comment_1_42344fce051d759f95215c985e9d1135._comment
deleted file mode 100644
index 0d903a13d..000000000
--- a/doc/bugs/Partial_direct__47__indirect_repo/comment_1_42344fce051d759f95215c985e9d1135._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-12T11:23:47Z"
- content="""
-This can happen if your repository gets annex.direct=true set in its .git/config, without `git annex direct` having been run to truely put it into direct mode.
-
-The proof that this was the case is that `git annex indirect` did anything at all. The first thing `git annex indirect` does is check if it's in a direct mode repository. If not, it steps without doing anything, and without outputting anything.
-
-I think this was user error.
-"""]]
diff --git a/doc/bugs/Partial_direct__47__indirect_repo/comment_2_8ba64f2750d0ef4adf595674c723bc65._comment b/doc/bugs/Partial_direct__47__indirect_repo/comment_2_8ba64f2750d0ef4adf595674c723bc65._comment
deleted file mode 100644
index 96a12e96d..000000000
--- a/doc/bugs/Partial_direct__47__indirect_repo/comment_2_8ba64f2750d0ef4adf595674c723bc65._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-03-12T11:27:30Z"
- content="""
-Oh, I see, you started up the webapp, and told it to make a repo that already existed. So it helpfully set its annex.direct, thinking it was a new repository.
-"""]]
diff --git a/doc/bugs/Partial_direct__47__indirect_repo/comment_3_bd4985864b7dcd70a609ca7bc2617e4a._comment b/doc/bugs/Partial_direct__47__indirect_repo/comment_3_bd4985864b7dcd70a609ca7bc2617e4a._comment
deleted file mode 100644
index 1a9e187cc..000000000
--- a/doc/bugs/Partial_direct__47__indirect_repo/comment_3_bd4985864b7dcd70a609ca7bc2617e4a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="spwhitton"
- ip="82.36.235.9"
- subject="comment 3"
- date="2013-03-12T11:37:50Z"
- content="""
-That's right--I don't think it should do that for existing respositories.  I didn't realise it wasn't standard to use the webapp to recreate the autostart file.
-"""]]
diff --git a/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn b/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn
deleted file mode 100644
index 4a3329326..000000000
--- a/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-#### What steps will reproduce the problem?
-
-When moving to direct mode files get flagged in git as 'typechange'.
-
-    md test-directmode; cd test-directmode ; git init; git annex init
-    date > test.file ; git annex add test.file
-    git commit -m "Initial commit"
-    git status   # All fine
-    git annex direct
-    git status   # typechange: test.file
-    git add test.file && git commit -m "looks like I should commit this"
-    # And the symlink is now broken...
-
-#### What is the expected output? What do you see instead?
-
-Surprised to see the typechange status in git.  Would not expect to see anything, however, if you `git add` and then commit you can get data loss.  :-(
-
-
-#### What version of git-annex are you using? On what operating system?
-
-git-annex version: 3.20130114
-
-OS: OSX 10.6.8
-
-#### Please provide any additional information below.
-
-> This was the pre-commit hook, made it not run in direct mode. [[done]]
-> 
-> However, it's normal to see typechanged files in direct mode, and many
-> git commands that manipulate files in the working tree *can* result in
-> data loss. This is documented on [[direct_mode]].
-> --[[Joey]]
diff --git a/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode/comment_1_84cb8c651584ec2887f6e1b7dc107190._comment b/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode/comment_1_84cb8c651584ec2887f6e1b7dc107190._comment
deleted file mode 100644
index b06706374..000000000
--- a/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode/comment_1_84cb8c651584ec2887f6e1b7dc107190._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://a-or-b.myopenid.com/"
- ip="203.45.2.230"
- subject="comment 1"
- date="2013-01-17T02:13:03Z"
- content="""
-Should g-a encourage users to *not* `git add` files with the typechange attribute?
-"""]]
diff --git a/doc/bugs/Possible_issues_with_git_1.7.10_and_newer___40__merge_command_now_asks_for_a_commit_message__34__.mdwn b/doc/bugs/Possible_issues_with_git_1.7.10_and_newer___40__merge_command_now_asks_for_a_commit_message__34__.mdwn
deleted file mode 100644
index 05024ffe9..000000000
--- a/doc/bugs/Possible_issues_with_git_1.7.10_and_newer___40__merge_command_now_asks_for_a_commit_message__34__.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-running 'git annex sync' doesn't merge the branches as expected (from the
-limited testing I have done) with git 1.7.10, the behaviour of merge has
-changed, it now asks for a commit message. I would expect setting
-_GIT_MERGE_AUTOEDIT=no_ should resolve this issue.
-
-I had to manually do a merge (or set that variable) to get the branches
-back in sync again, this confused me a bit when git-annex watch was running
-in the background on a remote and it did not pick up the changes.
-
-> Yeah, I tend to miss these since the first thing I did when this
-> misfeature was being posted was to write a mail discouraging them from
-> doing it (sadly ignored), and then set in ~/.environment:
-
-	# My time is more valuable than git's new, bad default
-	GIT_MERGE_AUTOEDIT=no
-	export GIT_MERGE_AUTOEDIT
-
-> Anyway, I've made sync run merge with --no-edit now. [[done]] --[[Joey]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files.mdwn b/doc/bugs/Problem_when_dropping_unused_files.mdwn
deleted file mode 100644
index 2c15680b8..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-### Please describe the problem.
-
-While dropping 19 unused files from an annex, I got this error:
-
-    error: invalid object 100644 c873416e78db4dd94b6ab40470d6fe99b2ecb8bd for '002/0a6/SHA256E-s427690--03aeabcde841b66168b72de80098d74e047f3ffc832d4bbefa1f2f70ee6c92f8.jpg.log'
-    fatal: git-write-tree: error building trees
-    git-annex: failed to read sha from git write-tree
-
-I've actually seen this before, a few months ago.
-
-### What steps will reproduce the problem?
-
-I have no idea, but once it happens I can't interact with unused files anymore.  Also, `git annex fsck` now reports this same problem as well.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130815, OS X 10.8.4
-
-> [[done]]; no indication this is anything other than a corrupt git
-> repository, which can be caused by system crash, disk data loss, 
-> cosmic rays, etc. This is why we keep backups... --[[Joey]] 
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_10_d4f6bfe8e04560fc661a47b09ed8a5f4._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_10_d4f6bfe8e04560fc661a47b09ed8a5f4._comment
deleted file mode 100644
index 9c0e25528..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_10_d4f6bfe8e04560fc661a47b09ed8a5f4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.251.174"
- subject="comment 10"
- date="2013-09-07T17:14:36Z"
- content="""
-Again this error message has nothing to do with git-annex beyond it being a file in the git-annex branch that is corrupt. Your system seems to be repeatedly corrupting git repositories. You need to run `git fsck`, get the git repository in a clean state, and probably check the drive it's on, and run a memory test or otherwise deal with whatever is causing your system to corrupt files in the git repository.
-"""]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_1_e1a99bd3eb8b3186653b52a52b1836de._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_1_e1a99bd3eb8b3186653b52a52b1836de._comment
deleted file mode 100644
index 0e39a96fc..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_1_e1a99bd3eb8b3186653b52a52b1836de._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 1"
- date="2013-08-24T05:01:37Z"
- content="""
-The following command restored some sanity:
-
-    find .git/annex/ -name '*.log' -delete
-"""]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_2_dec3e5ffe5cfdc439f418ee00d7d9810._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_2_dec3e5ffe5cfdc439f418ee00d7d9810._comment
deleted file mode 100644
index e0c5a2882..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_2_dec3e5ffe5cfdc439f418ee00d7d9810._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="arand"
- ip="130.243.226.21"
- subject="comment 2"
- date="2013-08-24T11:40:54Z"
- content="""
-If I recall, such files being stored in the annex object store is a result of using direct mode?
-"""]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_3_d106a87101db52f957da84d90dafcdbb._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_3_d106a87101db52f957da84d90dafcdbb._comment
deleted file mode 100644
index 8c739552d..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_3_d106a87101db52f957da84d90dafcdbb._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 3"
- date="2013-08-24T16:04:21Z"
- content="""
-Unfortunately, the git error message you pasted suggests very strongly that your git repository has gotten corrupted. You can probably verify that by running `git annex fsck`. Assuming it is corrupted, the best thing to do is to make a new clone and move .git/annex and .git/config over from the corrupted repository to it, and finally run `git annex fsck`
-
-You then seem to have some reason decided to go delete git-annex's .git/annex/journal/*.log files, which are just files that have not yet been committed to the git-annex branch. The only reason this \"restored some sanity\" is that git-annex was trying to commit that data to git, and failing because your git repository is corrupted.
-
-(This has nothing at all to do with direct mode.)
-"""]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_4_f28ed0635612693e437e64d872af5c37._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_4_f28ed0635612693e437e64d872af5c37._comment
deleted file mode 100644
index ba2e693ee..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_4_f28ed0635612693e437e64d872af5c37._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 4"
- date="2013-08-25T05:27:57Z"
- content="""
-Do you have any thoughts on why it may have gotten corrupted, or why it seems to happen so commonly with large git-annex repositories?  I've seen this exact same sort of error while processing log files maybe 5 or 6 times now.
-"""]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_5_f0237075653768c84deb702442645f28._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_5_f0237075653768c84deb702442645f28._comment
deleted file mode 100644
index 4ad874c08..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_5_f0237075653768c84deb702442645f28._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 5"
- date="2013-08-25T05:50:35Z"
- content="""
-I meant to say, in 5 or 6 different repositories.  Further, when I see it happen the next time, how do you recommend I track down the real problem, instead of always just cloning and starting over?
-"""]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_6_b509006e1590480a104627369bc910f2._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_6_b509006e1590480a104627369bc910f2._comment
deleted file mode 100644
index 60f2165e2..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_6_b509006e1590480a104627369bc910f2._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 6"
- date="2013-08-30T04:19:57Z"
- content="""
-Just saw it happen again today, in a repository that passed \"fsck -A\" multiple times just yesterday.  What is going on?
-"""]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_7_fe261c074211ccb94bbcb32cfd8ee654._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_7_fe261c074211ccb94bbcb32cfd8ee654._comment
deleted file mode 100644
index 6f3e42f5c..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_7_fe261c074211ccb94bbcb32cfd8ee654._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 7"
- date="2013-08-30T04:25:45Z"
- content="""
-I tried your suggestion of cloning the repository and moving `.git/config` and `.git/annex`, and got this:
-
-    fsck Astronomy/12_ATM_2.jpg error: invalid object 100644 06f8fe222f052100101e5c2e77640f2ec3efff98 for '002/0a6/SHA256E-s427690--03aeabcde841b66168b72de80098d74e047f3ffc832d4bbefa1f2f70ee6c92f8.jpg.log'
-    fatal: git-write-tree: error building trees
-    git-annex: failed to read sha from git write-tree
-
-What else can I try?  Note that I can't even find this `.log` anywhere under my `.git` directory for this repository.
-"""]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_8_bc8e4dc7e0d6577ba5fcc98f56627b1f._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_8_bc8e4dc7e0d6577ba5fcc98f56627b1f._comment
deleted file mode 100644
index 0b82af2f1..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_8_bc8e4dc7e0d6577ba5fcc98f56627b1f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 8"
- date="2013-08-30T04:30:14Z"
- content="""
-The only thing that worked was nuking `.git/annex/index` and letting `git-annex sync` rebuild it.
-"""]]
diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_9_e9a22aa2ebcde5f6595b49dba9375761._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_9_e9a22aa2ebcde5f6595b49dba9375761._comment
deleted file mode 100644
index b75b3f61b..000000000
--- a/doc/bugs/Problem_when_dropping_unused_files/comment_9_e9a22aa2ebcde5f6595b49dba9375761._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 9"
- date="2013-08-30T06:20:58Z"
- content="""
-And yet again it happens:
-
-    error: invalid object 100644 3edb1d4a44ffba1ea1491693ae7d9faa82aad717 for '000/4ce/SHA256E-s175006724--a0edc4f880223028b3fa3a27b142c8e027ddf66db973b8272ca845a4a9e01d3e.mp4.log'  fatal: git-write-tree: error building trees
-
-This was in a repository that was working perfectly well until I tried to `git-annex get`.  The weird thing is that I don't even have any `SHA256E` files anymore.
-
-I think that after my recent migration, none of my repositories can be trusted.  This is just happening too often (more than 10 times in the last week, across many repositories on many machines).  I will just rebuild them all.  But I do wish git-annex was more resilient about this.
-"""]]
diff --git a/doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn b/doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn
deleted file mode 100644
index f8df1f082..000000000
--- a/doc/bugs/Problem_with_bup:_cannot_lock_refs.mdwn
+++ /dev/null
@@ -1,52 +0,0 @@
-Hi!
-
-Using bup for storing seems a good idea to save space, but I still have a problem when trying to copy files to my local git repo.
-I have two partitions:
-
-- /Data (NTFS)
-
-- / (ext4)
-
-I turned the directory /Data/Audio into a git-annex repo, and cloned it into /home/me/AudioClone.
-I added the remote bup to AudioClone by doing:
-
-    git annex initremote mybup type=bup encryption=none buprepo=
-
-But when I try to copy some files that I have previously got by "git annex get" by doing:
-
-    [~/AudioClone]$ git annex copy someartist/somealbum --to mybup
-
-it fails and tells me:
-
-    copy Order To Die/01 Morituri Te Salutant.flac (to mybup...) 
-    fatal: Cannot lock the ref 'refs/heads/WORM-s7351771-m1318841909--01 Morituri Te Salutant.flac'.
-    Traceback (most recent call last):
-      File "/usr/lib/bup/cmd/bup-split", line 170, in <module>
-        git.update_ref(refname, commit, oldref)
-      File "/usr/lib/bup/bup/git.py", line 835, in update_ref
-        _git_wait('git update-ref', p)
-      File "/usr/lib/bup/bup/git.py", line 930, in _git_wait
-        raise GitError('%s returned %d' % (cmd, rv))
-    bup.git.GitError: git update-ref returned 128
-
-for each file, **except for the album cover file**, which is a simple JPG that bup doesn't try to split. This one gets copied nicely but the big FLAC files don't.
-
-I tried to restart my session, in case bup adds my username to a group or something.
-
-(I'm using Ubuntu 11.10)
-
-> Apparently bup-split does not allow storing data using filenames with
-> spaces in them. I can reproduce the same bug using the same filename;
-> if I remove the spaces all is well.
-> 
-> Since bup-split -n uses git branches, I guess git-annex needs to avoid
-> giving it any names containing spaces, or anything else not allowed
-> in a git branch name. The rules for legal git branch names are quite complex
-> (see git-check-ref-format(1)) so it will take me some times to code
-> this up.
-> 
-> A workaround is to switch to the SHA256 backend
-> (`git annex migrate --backend=SHA256`), which avoids spaces in its keys.
-> --[[Joey]]
-
->> Now fixed in git. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Problems_building_on_Mac_OS_X.mdwn b/doc/bugs/Problems_building_on_Mac_OS_X.mdwn
deleted file mode 100644
index 39594773f..000000000
--- a/doc/bugs/Problems_building_on_Mac_OS_X.mdwn
+++ /dev/null
@@ -1,62 +0,0 @@
-### Please describe the problem.
-
-Installing via Cabal fails due to dependency conflicts with yesod. If I build without the webapp flag, the problem disappears.
-
-### What steps will reproduce the problem?
-Running `cabal install c2hs git-annex --bindir=$HOME/bin`.
-
-### What version of git-annex are you using? On what operating system?
-I was attempting to install 4.20130521 from Hackage. My operating system is Mac OS X 10.6.8. Cabal-install is at 0.14.0.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/debug.log
-Resolving dependencies...
-cabal: Could not resolve dependencies:
-trying: git-annex-4.20130521 (user goal)
-trying: git-annex-4.20130521:+webapp
-trying: yesod-default-1.2.0 (dependency of git-annex-4.20130521:+webapp)
-trying: yesod-core-1.2.1 (dependency of yesod-default-1.2.0)
-trying: cookie-0.4.0.1/installed-9d9... (dependency of yesod-core-1.2.1)
-next goal: yesod (dependency of git-annex-4.20130521:+webapp)
-rejecting: yesod-1.2.0.1, 1.2.0 (conflict: git-annex-4.20130521:webapp =>
-yesod(<1.2))
-rejecting: yesod-1.1.9.3, 1.1.9.2, 1.1.9.1, 1.1.9, 1.1.8.2, 1.1.8.1, 1.1.8,
-1.1.7.2, 1.1.7.1, 1.1.7, 1.1.6, 1.1.5, 1.1.4.1, 1.1.4 (conflict:
-yesod-core==1.2.1, yesod => yesod-core>=1.1.5 && <1.2)
-rejecting: yesod-1.1.3.1, 1.1.3, 1.1.2, 1.1.1.2, 1.1.1, 1.1.0.3, 1.1.0.2,
-1.1.0.1, 1.1.0 (conflict: yesod-core==1.2.1, yesod => yesod-core>=1.1 && <1.2)
-rejecting: yesod-1.0.1.6, 1.0.1.5, 1.0.1.4, 1.0.1.3, 1.0.1.2, 1.0.1.1, 1.0.1,
-1.0.0.2, 1.0.0.1, 1.0.0 (conflict: yesod-core==1.2.1, yesod => yesod-core>=1.0
-&& <1.1)
-rejecting: yesod-0.10.2, 0.10.1.4, 0.10.1.3, 0.10.1.2, 0.10.1.1, 0.10.1
-(conflict: yesod-core==1.2.1, yesod => yesod-core>=0.10.1 && <0.11)
-rejecting: yesod-0.9.4.1, 0.9.4, 0.9.3.4, 0.9.3.3, 0.9.3.2 (conflict:
-yesod-core==1.2.1, yesod => yesod-core>=0.9.3.4 && <0.10)
-rejecting: yesod-0.9.3.1, 0.9.3, 0.9.2.2, 0.9.2.1, 0.9.2, 0.9.1.1 (conflict:
-yesod-core==1.2.1, yesod => yesod-core>=0.9.1.1 && <0.10)
-rejecting: yesod-0.9.1 (conflict: yesod-core==1.2.1, yesod => yesod-core>=0.9
-&& <0.10)
-rejecting: yesod-0.8.2.1, 0.8.2, 0.8.1 (conflict: yesod-core==1.2.1, yesod =>
-yesod-core>=0.8.1 && <0.9)
-rejecting: yesod-0.8.0 (conflict: yesod-core==1.2.1, yesod => yesod-core>=0.8
-&& <0.9)
-rejecting: yesod-0.7.3, 0.7.2 (conflict: yesod-core==1.2.1, yesod =>
-yesod-core>=0.7.0.2 && <0.8)
-rejecting: yesod-0.7.1 (conflict: yesod-core==1.2.1, yesod =>
-yesod-core>=0.7.0.1 && <0.8)
-rejecting: yesod-0.7.0 (conflict: yesod-core==1.2.1, yesod => yesod-core>=0.7
-&& <0.8)
-rejecting: yesod-0.6.7, 0.6.6, 0.6.5, 0.6.4, 0.6.3, 0.6.2, 0.6.1.2, 0.6.1.1,
-0.6.1, 0.6.0.2, 0.6.0.1, 0.6.0, 0.5.4.2, 0.5.4.1, 0.5.4, 0.5.3, 0.5.2, 0.5.1,
-0.5.0.3, 0.5.0.2, 0.5.0.1, 0.5.0, 0.4.1, 0.4.0.3, 0.4.0.2, 0.4.0.1, 0.4.0
-(conflict: cookie => time==1.4/installed-d61..., yesod => time>=1.1.4 && <1.3)
-rejecting: yesod-0.3.1.1, 0.3.1, 0.3.0, 0.2.0, 0.0.0.2, 0.0.0.1, 0.0.0
-(conflict: cookie => time==1.4/installed-d61..., yesod => time>=1.1.3 && <1.2)
-# End of transcript or log.
-"""]]
-
-> Not OSX specific. I have added a version hint that makes cabal work and uploaded
-> a point release with this fix. [[done]] --[[Joey]]
diff --git a/doc/bugs/Problems_building_on_Mac_OS_X/comment_1_1c199b826fdd84b5184b1466ad03a9a4._comment b/doc/bugs/Problems_building_on_Mac_OS_X/comment_1_1c199b826fdd84b5184b1466ad03a9a4._comment
deleted file mode 100644
index f73808014..000000000
--- a/doc/bugs/Problems_building_on_Mac_OS_X/comment_1_1c199b826fdd84b5184b1466ad03a9a4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmu416zAYgYzbXVZAe30MiXoOWO4z6nGX8"
- nickname="Johannes"
- subject="comment 1"
- date="2013-05-23T10:02:55Z"
- content="""
-Same problem on archlinux with cabal-install 1.16.0.2
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx.mdwn b/doc/bugs/Problems_running_make_on_osx.mdwn
deleted file mode 100644
index 83b75fb54..000000000
--- a/doc/bugs/Problems_running_make_on_osx.mdwn
+++ /dev/null
@@ -1,49 +0,0 @@
-Followed the instructions over here: http://git-annex.branchable.com/forum/git-annex_on_OSX/
-
-and had to install the following extra packages to be able to get make to start:
-
-[realizes pcre-light is needed but pcre not installed on my mac]  
-sudo port install pcre  
-sudo cabal install pcre-light  
-
-> Ah right, that is a new dependency. I've updated the forum page
-> with this info.
-> --[[Joey]] 
-
-But then I got the following error:  
-
-<pre>
-ghc -O2 -Wall --make git-annex  
-[ 7 of 52] Compiling BackendTypes     ( BackendTypes.hs, BackendTypes.o   
-
-BackendTypes.hs:71:17:  
-    No instance for (Arbitrary Char)  
-      arising from a use of `arbitrary' at BackendTypes.hs:71:17-25  
-    Possible fix: add an instance declaration for (Arbitrary Char)  
-    In a stmt of a 'do' expression: backendname <- arbitrary  
-    In the expression:  
-        do backendname <- arbitrary  
-           keyname <- arbitrary  
-             return $ Key (backendname, keyname)  
-    In the definition of `arbitrary':  
-        arbitrary = do backendname <- arbitrary  
-                       keyname <- arbitrary  
-                         return $ Key (backendname, keyname)  
-make: *** [git-annex] Error 1  
-</pre>
-
-My knowledge of Haskell (had to lookup the spelling...) is more than rudimentary so any help would be appreciated.
-
-> Hmm, it seems you may be missing part of the quickcheck haskell
-> library, or have a different version than me.
-> 
-> The easy fix is probably to just edit BackendTypes.hs and delete the
-> entire end of the file from line 68, "for quickcheck" down. This code
-> is only used by the test suite (so "make test" will fail), 
-> but it should get it to build. --[[Joey]]
-
----
-
-Closing this bug because the above problem now has a solution documented on
-the install page, and the below test suite failure problems should all be
-resolved on OSX. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_10_94e4ac430140042a2d0fb5a16d86b4e5._comment b/doc/bugs/Problems_running_make_on_osx/comment_10_94e4ac430140042a2d0fb5a16d86b4e5._comment
deleted file mode 100644
index 95a9773e2..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_10_94e4ac430140042a2d0fb5a16d86b4e5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 10"
- date="2011-02-09T15:04:50Z"
- content="""
-I don't know what these problems forking could be. Can you strace it?
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_11_56f1143fa191361d63b441741699e17f._comment b/doc/bugs/Problems_running_make_on_osx/comment_11_56f1143fa191361d63b441741699e17f._comment
deleted file mode 100644
index 3fbe57ecd..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_11_56f1143fa191361d63b441741699e17f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 11"
- date="2011-02-09T19:35:47Z"
- content="""
-I got dtruss to give me a trace, the output is quite big to post here (~560kb gzip'd), do you mind if I emailed it or posted it somewhere else for you?
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_12_ec5131624d0d2285d3b6880e47033f97._comment b/doc/bugs/Problems_running_make_on_osx/comment_12_ec5131624d0d2285d3b6880e47033f97._comment
deleted file mode 100644
index beba5dc42..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_12_ec5131624d0d2285d3b6880e47033f97._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 12"
- date="2011-02-09T19:47:30Z"
- content="""
-joey@kitenet.net (hope I can make sense of dtruss output)
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_13_88ed095a448096bf8a69015a04e64df1._comment b/doc/bugs/Problems_running_make_on_osx/comment_13_88ed095a448096bf8a69015a04e64df1._comment
deleted file mode 100644
index dd25c3d0c..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_13_88ed095a448096bf8a69015a04e64df1._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 13"
- date="2011-02-09T21:59:47Z"
- content="""
-The dtrace puzzlingly does not have the same errors shown above, but a set of mostly new errors. I don't know what to make of that.
-
-> git-annex: git-annex/.t/repo/.git/hooks/pre-commit: fileAccess: permission denied (Operation not permitted)
-
-This seems to be caused by it setting the execute bit on the file. I don't know why that would fail; it's just written the file and renamed it into place so clearly should be able to write to it.
-
-> was able to modify annexed file's sha1foo content
-
-This also suggests something breaking with permissions.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_14_89a960b6706ed703b390a81a8bc4e311._comment b/doc/bugs/Problems_running_make_on_osx/comment_14_89a960b6706ed703b390a81a8bc4e311._comment
deleted file mode 100644
index 724fe5505..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_14_89a960b6706ed703b390a81a8bc4e311._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 14"
- date="2011-02-12T21:19:24Z"
- content="""
-I've been trying to dig around the trace and code, and used google to see if the forkProcess issue was a haskell thing or an OSX thing. It seems that <http://hackage.haskell.org/trac/ghc/ticket/4493> someone may have ran into a similar issue, though I am not sure if its related.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_15_6b8867b8e48bf807c955779c9f8f0909._comment b/doc/bugs/Problems_running_make_on_osx/comment_15_6b8867b8e48bf807c955779c9f8f0909._comment
deleted file mode 100644
index 733ec997a..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_15_6b8867b8e48bf807c955779c9f8f0909._comment
+++ /dev/null
@@ -1,71 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 15"
- date="2011-02-13T02:45:51Z"
- content="""
-It may be possible that OSX has some low resource limits, for user processes (266 per user I think) doing a 
-
-    sudo sysctl -w kern.maxproc=2048
-    sudo sysctl -w kern.maxprocperuid=1024
-    sudo echo \"limit maxfiles 1024 unlimited\" >> /etc/launchd.conf
-    sudo echo \"limit maxproc 1024 2048\" >> /etc/launchd.conf
-
-seems to change the behaviour of the tests abit...
-
-<pre>
-Testing 1:blackbox:3:git-annex unannex:1:with content                         
-### Failure in: 1:blackbox:3:git-annex unannex:1:with content
-foo is not a symlink
-Testing 1:blackbox:4:git-annex drop:0:no remotes                              
-### Failure in: 1:blackbox:4:git-annex drop:0:no remotes
-drop wrongly succeeded with no known copy of file
-Testing 1:blackbox:4:git-annex drop:1:with remote                             
-Testing 1:blackbox:4:git-annex drop:2:untrusted remote                        
-Testing 1:blackbox:5:git-annex get                                            
-Testing 1:blackbox:6:git-annex move                                           
-Testing 1:blackbox:7:git-annex copy                                           
-Testing 1:blackbox:8:git-annex unlock/lock                                    
-Testing 1:blackbox:9:git-annex edit/commit:0                                  
-Cases: 30  Tried: 20  Errors: 0  Failures: 2add foo ok
-ok
-Testing 1:blackbox:9:git-annex edit/commit:1                                  
-Testing 1:blackbox:10:git-annex fix                                           
-Testing 1:blackbox:11:git-annex trust/untrust/semitrust                       
-Testing 1:blackbox:12:git-annex fsck:0                                        
-Cases: 30  Tried: 24  Errors: 0  Failures: 2  Only 1 of 2 trustworthy copies of foo exist.
-  Back it up with git-annex copy.
-  Only 1 of 2 trustworthy copies of sha1foo exist.
-  Back it up with git-annex copy.
-  Bad file size; moved to /Users/jtang/develop/git-annex/.t/tmprepo/.git/annex/bad/WORM:1297565141:20:foo
-  Bad file content; moved to /Users/jtang/develop/git-annex/.t/tmprepo/.git/annex/bad/SHA1:ee80d2cec57a3810db83b80e1b320df3a3721ffa
-Testing 1:blackbox:12:git-annex fsck:1                                        
-### Failure in: 1:blackbox:12:git-annex fsck:1
-fsck failed to fail with content only available in untrusted (current) repository
-Testing 1:blackbox:12:git-annex fsck:2                                        
-Cases: 30  Tried: 26  Errors: 0  Failures: 3  Only 1 of 2 trustworthy copies of foo exist.
-  Back it up with git-annex copy.
-  The following untrusted locations may also have copies: 
-  	58e831c2-371b-11e0-bc1f-47d738dc52ee  -- test repo
-  Only 1 of 2 trustworthy copies of sha1foo exist.
-  Back it up with git-annex copy.
-  The following untrusted locations may also have copies: 
-  	58e831c2-371b-11e0-bc1f-47d738dc52ee  -- test repo
-Testing 1:blackbox:13:git-annex migrate:0                                     
-Cases: 30  Tried: 27  Errors: 0  Failures: 3  git-annex: user error (Error in fork: forkProcess: resource exhausted (Resource temporarily unavailable))
-### Failure in: 1:blackbox:13:git-annex migrate:0
-migrate annexedfile failed
-Testing 1:blackbox:13:git-annex migrate:1                                     
-### Error in:   1:blackbox:13:git-annex migrate:1
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:14:git-annex unused/dropunused                             
-### Error in:   1:blackbox:14:git-annex unused/dropunused
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Cases: 30  Tried: 30  Errors: 2  Failures: 4
-test: failed
-</pre>
-
-
-the number of failures vary as I change the values of the maxprocs, I think I  have narrowed it down to OSX just being stupid with limits thus causing the tests to fail.
-
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_16_5c2dd6002aadaab30841b77a5f5aed34._comment b/doc/bugs/Problems_running_make_on_osx/comment_16_5c2dd6002aadaab30841b77a5f5aed34._comment
deleted file mode 100644
index ca1b8e8cd..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_16_5c2dd6002aadaab30841b77a5f5aed34._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 16"
- date="2011-02-13T04:52:26Z"
- content="""
-I've fixed the test suite to not accumulate all those zombie processes. Now only 2 or 3 processes should run max. Am curious to see if that clears up all the problems.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_17_62fccb04b0e4b695312f7a3f32fb96ee._comment b/doc/bugs/Problems_running_make_on_osx/comment_17_62fccb04b0e4b695312f7a3f32fb96ee._comment
deleted file mode 100644
index 7c7200fb9..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_17_62fccb04b0e4b695312f7a3f32fb96ee._comment
+++ /dev/null
@@ -1,43 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 17"
- date="2011-02-13T10:46:54Z"
- content="""
-Yeap, that did the trick. I just tested a few separate OSX 10.6.6 systems and the tests are better behaved now, only 3 failures now.
-
-So the tests behave better (at least we don't get resource fork errors any more)
- 
- * after the commit c319a3 without modifying the system limits (of 266 procs per user)
- * without the commit c319a3 and when I increase the system process limits to as much as OSX allows
-
-On all the systems I tested on, I'm down to 3 failures now.
-
-<pre>
-### Failure in: 1:blackbox:3:git-annex unannex:1:with content
-foo is not a symlink
-### Failure in: 1:blackbox:4:git-annex drop:0:no remotes
-drop wrongly succeeded with no known copy of file
-Cases: 30  Tried: 20  Errors: 0  Failures: 2add foo ok
-ok
-Cases: 30  Tried: 24  Errors: 0  Failures: 2  Only 1 of 2 trustworthy copies of foo exist.
-  Back it up with git-annex copy.
-  Only 1 of 2 trustworthy copies of sha1foo exist.
-  Back it up with git-annex copy.
-  Bad file size; moved to /Users/jtang/develop/git-annex/.t/tmprepo/.git/annex/bad/WORM:1297594011:20:foo
-  Bad file content; moved to /Users/jtang/develop/git-annex/.t/tmprepo/.git/annex/bad/SHA1:ee80d2cec57a3810db83b80e1b320df3a3721ffa
-### Failure in: 1:blackbox:12:git-annex fsck:1
-fsck failed to fail with content only available in untrusted (current) repository
-Cases: 30  Tried: 26  Errors: 0  Failures: 3  Only 1 of 2 trustworthy copies of foo exist.
-  Back it up with git-annex copy.
-  The following untrusted locations may also have copies: 
-  	90d63906-375e-11e0-8867-abb8a6368269  -- test repo
-  Only 1 of 2 trustworthy copies of sha1foo exist.
-  Back it up with git-annex copy.
-  The following untrusted locations may also have copies: 
-  	90d63906-375e-11e0-8867-abb8a6368269  -- test repo
-Cases: 30  Tried: 30  Errors: 0  Failures: 3
-</pre>
-
-It's the same set of failures across all the OSX systems that I have tested on. Now I just need to figure out why there are still these three failures.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_18_64fab50d95de619eb2e8f08f90237de1._comment b/doc/bugs/Problems_running_make_on_osx/comment_18_64fab50d95de619eb2e8f08f90237de1._comment
deleted file mode 100644
index df76bb301..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_18_64fab50d95de619eb2e8f08f90237de1._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="maybe killed another osx bug in the test."
- date="2011-02-13T15:12:10Z"
- content="""
-I think I have figured out why 
-
-    ### Failure in: 1:blackbox:3:git-annex unannex:1:with content
-    foo is not a symlink
-
-It goes back to the this piece of code (in test.hs)
-
-    copyrepo :: FilePath -> FilePath -> IO FilePath
-    copyrepo old new = do
-            cleanup new
-            ensuretmpdir
-            Utility.boolSystem \"cp\" [\"-pr\", old, new] @? \"cp -pr failed\"
-
-It seems that on OSX it does not preserve the symbolic link information, basically cp is not gnu cp on OSX, doing a \"cp -a SOURCE DEST\" seem's to the right thing on OSX. I tried it out on my archlinux workstation by replacing *-pr* with just *-a* and all the tests passed on archlinux.
-
-I'm not sure what the implications would be with changing the test with changing the cp command.
-
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_19_4253988ed178054c8b6400beeed68a29._comment b/doc/bugs/Problems_running_make_on_osx/comment_19_4253988ed178054c8b6400beeed68a29._comment
deleted file mode 100644
index 090c991c3..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_19_4253988ed178054c8b6400beeed68a29._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 19"
- date="2011-02-13T15:55:47Z"
- content="""
-On second thought and after some messing (trying most of the options and combinations of options on OSX for).... I tried replacing cp with gnu cp from coreutils on my OSX install, and all the tests passed. *sigh* cp -a is preserving some permissions and attributes but not all, its not behaving in the same way as the gnu cp does... the closet thing that I have found on OSX that behaves in the same way as gnu \"cp -pr\" is to use \"ditto\".
-
-Just doing a \"ditto SOURCE DEST\" in the tests passes everything. I'm not sure if its a good idea to use this even though it works. Though this is just the tests, does it affect CopyFile.hs where \"cp\" is called?
-
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_1_34120e82331ace01a6a4960862d38f2d._comment b/doc/bugs/Problems_running_make_on_osx/comment_1_34120e82331ace01a6a4960862d38f2d._comment
deleted file mode 100644
index a33fef7d9..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_1_34120e82331ace01a6a4960862d38f2d._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmd3qri1pXEYktlxYGwj37wCnrM4FMEJCc"
- nickname="Antoine"
- subject="Got it going!"
- date="2011-02-06T06:02:57Z"
- content="""
-Thanks to your feedback, I got it going.  
-
-Maybe those two should be added to the 'OSX how-to' in the forum   
-
-[realizes pcre-light is needed but pcre not installed on my mac]  
-sudo port install pcre  
-sudo cabal install pcre-light  
-
-[tests are failing, need haskell's quickcheck]  
-sudo cabal install quickcheck  
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_20_7db27d1a22666c831848bc6c06d66a84._comment b/doc/bugs/Problems_running_make_on_osx/comment_20_7db27d1a22666c831848bc6c06d66a84._comment
deleted file mode 100644
index b617da926..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_20_7db27d1a22666c831848bc6c06d66a84._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 20"
- date="2011-02-13T17:54:09Z"
- content="""
-Outside the test suite, git-annex's actual use of cp puts fairly low demands on it. It tries to use cp -a or cp -p if available just to preserve whatever attributes it can preserve, but the worst case if that you have a symlink pointing to a file that doesn't have the original timestamp or whatever. And there's little expectation git preserves that stuff anyway.
-
-I will probably try to make the test suite entirely use git clone rather than cp.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_2_cc53d1681d576186dbc868dd9801d551._comment b/doc/bugs/Problems_running_make_on_osx/comment_2_cc53d1681d576186dbc868dd9801d551._comment
deleted file mode 100644
index 91d3e89f0..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_2_cc53d1681d576186dbc868dd9801d551._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-02-06T17:39:52Z"
- content="""
-Yes, I've moved it to [[install/OSX]] page where anyone can update it in this wiki, and added your improvements.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_3_68f0f8ae953589ae26d57310b40c878d._comment b/doc/bugs/Problems_running_make_on_osx/comment_3_68f0f8ae953589ae26d57310b40c878d._comment
deleted file mode 100644
index 39f32c244..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_3_68f0f8ae953589ae26d57310b40c878d._comment
+++ /dev/null
@@ -1,57 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="tests fail with more recent installs of haskell platform"
- date="2011-02-07T12:43:43Z"
- content="""
-I'm running ghc 6.12.3 with the corresponding haskell-platform package from the HP site which I installed in preference to the macports version of haskell-platform (it's quite old). it seems when you install quickcheck, the version that is installed is of version 2.4.0.1 and not 1.2.0 which git-annex depends on for its tests.
-
-<pre>
-jtang@x00:~ $ cabal install quickcheck --reinstall               
-Resolving dependencies...
-Configuring QuickCheck-2.4.0.1...
-Preprocessing library QuickCheck-2.4.0.1...
-
-..
-and so on..
-..
-
-</pre>
-
-it fails with this
-
-<pre>
-[54 of 54] Compiling Main             ( test.hs, test.o )
-
-test.hs:56:3:
-    No instance for (QuickCheck-1.2.0.1:Test.QuickCheck.Arbitrary Char)
-      arising from a use of `qctest' at test.hs:56:3-64
-    Possible fix:
-      add an instance declaration for
-      (QuickCheck-1.2.0.1:Test.QuickCheck.Arbitrary Char)
-    In the expression:
-        qctest \"prop_idempotent_deencode\" Git.prop_idempotent_deencode
-    In the first argument of `TestList', namely
-        `[qctest \"prop_idempotent_deencode\" Git.prop_idempotent_deencode,
-          qctest \"prop_idempotent_fileKey\" Locations.prop_idempotent_fileKey,
-          qctest
-            \"prop_idempotent_key_read_show\"
-            BackendTypes.prop_idempotent_key_read_show,
-          qctest
-            \"prop_idempotent_shellEscape\" Utility.prop_idempotent_shellEscape,
-          ....]'
-    In the second argument of `($)', namely
-        `TestList
-           [qctest \"prop_idempotent_deencode\" Git.prop_idempotent_deencode,
-            qctest \"prop_idempotent_fileKey\" Locations.prop_idempotent_fileKey,
-            qctest
-              \"prop_idempotent_key_read_show\"
-              BackendTypes.prop_idempotent_key_read_show,
-            qctest
-              \"prop_idempotent_shellEscape\" Utility.prop_idempotent_shellEscape,
-            ....]'
-</pre>
-
-I'd imagine if I could downgrade, it would compile and pass the tests (I hope)
-
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_4_c52be386f79f14c8570a8f1397c68581._comment b/doc/bugs/Problems_running_make_on_osx/comment_4_c52be386f79f14c8570a8f1397c68581._comment
deleted file mode 100644
index e245e139f..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_4_c52be386f79f14c8570a8f1397c68581._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 4"
- date="2011-02-08T19:00:14Z"
- content="""
-I doubt that git-annex can be used with QuickCheck 1.2.0. The QuickCheck I've tested it with is 2.1.0.3 actually.
-
-I suspect you have an old version of the TestPack haskell library on your system, that is linked against QuickCheck 1.2.0. Git-annex has been tested with TestPack 2.0.0, which uses QuickCheck 2.x.
-
-In any case, you don't have to run 'make test' to build git-annex, and my comments above should make the main program compile, I expect.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_5_7f1330a1e541b0f3e2192e596d7f7bee._comment b/doc/bugs/Problems_running_make_on_osx/comment_5_7f1330a1e541b0f3e2192e596d7f7bee._comment
deleted file mode 100644
index 9c83feb32..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_5_7f1330a1e541b0f3e2192e596d7f7bee._comment
+++ /dev/null
@@ -1,107 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 5"
- date="2011-02-08T19:56:55Z"
- content="""
-Ah, that gave me a good clue, my system just got pretty confused with a mixture of quickcheck and testpack installs. Would it be possible to put up a list of versions of the software you are using on your development environment? (at least the minimum tested version) 
-
-I guess it shouldn't matter to most users who are going to rely on packagers to sort these dependancy issues, but it's nice to know. 
-
-Anyway, the tests build now, and they seem to fail on my (rather messy) install of haskell platform + ghc 6.12 on osx 10.6.6.
-
-<pre>
-< output that passed some tests >
-Testing 1:blackbox:0:git-annex init
-Testing 1:blackbox:1:git-annex add:0
-Testing 1:blackbox:1:git-annex add:1
-Cases: 30  Tried: 9  Errors: 0  Failures: 0test: sha1sum: executeFile: does not exist (No such file or directory)
-  git-annex: <file descriptor: 6>: hGetLine: end of file
-### Failure in: 1:blackbox:1:git-annex add:1
-add with SHA1 failed
-Testing 1:blackbox:2:git-annex setkey/fromkey
-Cases: 30  Tried: 10  Errors: 0  Failures: 1(checksum...) test: sha1sum: executeFile: does not exist (No such file or directory)
-### Error in:   1:blackbox:2:git-annex setkey/fromkey
-<file descriptor: 3>: hGetLine: end of file
-Testing 1:blackbox:3:git-annex unannex:0:no content
-Cases: 30  Tried: 11  Errors: 1  Failures: 1chmod: -R: No such file or directory
-chmod: -R: No such file or directory
-Testing 1:blackbox:3:git-annex unannex:1:with content
-### Failure in: 1:blackbox:3:git-annex unannex:1:with content
-foo is not a symlink
-Testing 1:blackbox:4:git-annex drop:0:no remotes
-Cases: 30  Tried: 13  Errors: 1  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:4:git-annex drop:0:no remotes
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:4:git-annex drop:1:with remote
-Cases: 30  Tried: 14  Errors: 2  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:4:git-annex drop:1:with remote
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:4:git-annex drop:2:untrusted remote
-Cases: 30  Tried: 15  Errors: 3  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:4:git-annex drop:2:untrusted remote
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:5:git-annex get
-Cases: 30  Tried: 16  Errors: 4  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:5:git-annex get
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:6:git-annex move
-Cases: 30  Tried: 17  Errors: 5  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:6:git-annex move
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:7:git-annex copy
-Cases: 30  Tried: 18  Errors: 6  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:7:git-annex copy
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:8:git-annex unlock/lock
-Cases: 30  Tried: 19  Errors: 7  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:8:git-annex unlock/lock
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:9:git-annex edit/commit:0
-Cases: 30  Tried: 20  Errors: 8  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:9:git-annex edit/commit:0
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:9:git-annex edit/commit:1
-Cases: 30  Tried: 21  Errors: 9  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:9:git-annex edit/commit:1
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:10:git-annex fix
-Cases: 30  Tried: 22  Errors: 10  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:10:git-annex fix
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:11:git-annex trust/untrust/semitrust
-Cases: 30  Tried: 23  Errors: 11  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:11:git-annex trust/untrust/semitrust
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:12:git-annex fsck:0
-Cases: 30  Tried: 24  Errors: 12  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:12:git-annex fsck:0
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:12:git-annex fsck:1
-Cases: 30  Tried: 25  Errors: 13  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:12:git-annex fsck:1
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:12:git-annex fsck:2
-Cases: 30  Tried: 26  Errors: 14  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:12:git-annex fsck:2
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:13:git-annex migrate:0
-Cases: 30  Tried: 27  Errors: 15  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:13:git-annex migrate:0
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:13:git-annex migrate:1
-Cases: 30  Tried: 28  Errors: 16  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:13:git-annex migrate:1
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:14:git-annex unused/dropunused
-Cases: 30  Tried: 29  Errors: 17  Failures: 2chmod: -R: No such file or directory
-### Error in:   1:blackbox:14:git-annex unused/dropunused
-.t/tmprepo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-Cases: 30  Tried: 30  Errors: 18  Failures: 2
-chmod: -R: No such file or directory
-test: .t/repo/.git/annex/objects/WORM:1297194705:20:foo/WORM:1297194705:20:foo: removeLink: permission denied (Permission denied)
-make: *** [test] Error 1
-</pre>
-
-I assumed that since the tests built, then running them shouldn't be a problem. It looks like some argument isn't being passed about for the location of the .t directory that gets created. I will check the dependancies on my system again.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_6_0c46f5165ceb5a7b9ea9689c33b3a4f8._comment b/doc/bugs/Problems_running_make_on_osx/comment_6_0c46f5165ceb5a7b9ea9689c33b3a4f8._comment
deleted file mode 100644
index afc3088d4..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_6_0c46f5165ceb5a7b9ea9689c33b3a4f8._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 6"
- date="2011-02-08T23:20:08Z"
- content="""
-You're missing the sha1sum command, everything else is a followon error from that. Added a hint about this to [[install]],
-and in the next version configure will check for sha1sum.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_7_237a137cce58a28abcc736cbf2c420b0._comment b/doc/bugs/Problems_running_make_on_osx/comment_7_237a137cce58a28abcc736cbf2c420b0._comment
deleted file mode 100644
index 8d8aefcb2..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_7_237a137cce58a28abcc736cbf2c420b0._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 7"
- date="2011-02-09T00:45:31Z"
- content="""
-That's odd, I have the md5sha1sum package installed and it still fails with pretty much the same error
-
-<pre>
-Testing 1:blackbox:0:git-annex init
-Cases: 30  Tried: 7  Errors: 0  Failures: 0chmod: -R: No such file or directory
-### Error in:   1:blackbox:0:git-annex init
-.t/repo/.git/annex/objects/SHA1:ee80d2cec57a3810db83b80e1b320df3a3721ffa/SHA1:ee80d2cec57a3810db83b80e1b320df3a3721ffa: removeLink: permission denied (Permission denied)
-Testing 1:blackbox:1:git-annex add:0
-### Error in:   1:blackbox:1:git-annex add:0
-foo: openFile: permission denied (Permission denied)
-
-< and so on >
-</pre>
-
-the configure script finds sha1sum, builds and starts to run.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_8_efafa203addf8fa79e33e21a87fb5a2b._comment b/doc/bugs/Problems_running_make_on_osx/comment_8_efafa203addf8fa79e33e21a87fb5a2b._comment
deleted file mode 100644
index 9401bd453..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_8_efafa203addf8fa79e33e21a87fb5a2b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 8"
- date="2011-02-09T04:10:27Z"
- content="""
-The chmod errors are because your chmod does not understand the -R argument. Only the test suite uses chmod -R. I've fixed it to modify modes manually.
-"""]]
diff --git a/doc/bugs/Problems_running_make_on_osx/comment_9_cc283b485b3c95ba7eebc8f0c96969b3._comment b/doc/bugs/Problems_running_make_on_osx/comment_9_cc283b485b3c95ba7eebc8f0c96969b3._comment
deleted file mode 100644
index da6d7ca17..000000000
--- a/doc/bugs/Problems_running_make_on_osx/comment_9_cc283b485b3c95ba7eebc8f0c96969b3._comment
+++ /dev/null
@@ -1,66 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 9"
- date="2011-02-09T09:12:52Z"
- content="""
-[a0826293][] fixed the last problem, there is coreutils available in macports, if they are installed you get the gnu equivalents but they are prefixed with a g (e.g. gchmod instead of chmod), I guess not everyone will have these install or prefer these on [[install/OSX]]
-
-Some more tests fail now...
-
-<pre>
-Testing 1:blackbox:3:git-annex unannex:1:with content
-### Failure in: 1:blackbox:3:git-annex unannex:1:with content
-foo is not a symlink
-Testing 1:blackbox:4:git-annex drop:0:no remotes
-### Failure in: 1:blackbox:4:git-annex drop:0:no remotes
-drop wrongly succeeded with no known copy of file
-Testing 1:blackbox:4:git-annex drop:1:with remote
-Testing 1:blackbox:4:git-annex drop:2:untrusted remote
-Testing 1:blackbox:5:git-annex get
-Testing 1:blackbox:6:git-annex move
-Testing 1:blackbox:7:git-annex copy
-### Failure in: 1:blackbox:7:git-annex copy
-move --to of file already there failed
-Testing 1:blackbox:8:git-annex unlock/lock
-### Error in:   1:blackbox:8:git-annex unlock/lock
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:9:git-annex edit/commit:0
-### Error in:   1:blackbox:9:git-annex edit/commit:0
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:9:git-annex edit/commit:1
-### Error in:   1:blackbox:9:git-annex edit/commit:1
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:10:git-annex fix
-### Error in:   1:blackbox:10:git-annex fix
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:11:git-annex trust/untrust/semitrust
-### Error in:   1:blackbox:11:git-annex trust/untrust/semitrust
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:12:git-annex fsck:0
-### Error in:   1:blackbox:12:git-annex fsck:0
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:12:git-annex fsck:1
-### Error in:   1:blackbox:12:git-annex fsck:1
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:12:git-annex fsck:2
-### Error in:   1:blackbox:12:git-annex fsck:2
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:13:git-annex migrate:0
-### Error in:   1:blackbox:13:git-annex migrate:0
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:13:git-annex migrate:1
-### Error in:   1:blackbox:13:git-annex migrate:1
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Testing 1:blackbox:14:git-annex unused/dropunused
-### Error in:   1:blackbox:14:git-annex unused/dropunused
-forkProcess: resource exhausted (Resource temporarily unavailable)
-Cases: 30  Tried: 30  Errors: 11  Failures: 3
-test: failed
-make: *** [test] Error 1
-</pre>
-
-On a side note, I think I found another bug in the testing. I had tested in a virtual machine in archlinux (a very recent updated version) Please see the report here [[tests fail when there is no global .gitconfig for the user]]
-
-[a0826293]: http://git.kitenet.net/?p=git-annex;a=commit;h=7a0826293e0ac6c0000f49a1618c1c613b909aa1
-"""]]
diff --git a/doc/bugs/Problems_with_syncing_gnucash.mdwn b/doc/bugs/Problems_with_syncing_gnucash.mdwn
deleted file mode 100644
index 6a1f96a9f..000000000
--- a/doc/bugs/Problems_with_syncing_gnucash.mdwn
+++ /dev/null
@@ -1,568 +0,0 @@
-### Please describe the problem.
-I am trying to sync gnucash between my server and my notebook. Both devices are connected via VPN to provide bidirectional SSH connectivity. After adding some data in gnucash the logfiles get synced properly but the changes to the gnucash.gnucash file are not recognized. Touching the file afterwards causes git-annex to immediately transfer the file.
-
-### What steps will reproduce the problem?
-
-Store your gnucash configuration in a git-annex repository. Add some transactions and wait for git-annex to sync your *.gnucash file.
-
-### What version of git-annex are you using? On what operating system?
-
-server and notebook -> Ubuntu 12.04.2 LTS:
-[[!format sh """
-florz@server:~$ git-annex version
-git-annex version: 4.20130601
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-"""]]
-
-### Please provide any additional information below.
-
-before opening gnucash:
-[[!format sh """
-florz@notebook:~$ stat annex-sync/gnucash/gnucash.gnucash
-  Datei: »annex-sync/gnucash/gnucash.gnucash“
-  Größe: 113902         Blöcke: 240        EA Block: 4096   Normale Datei
-Gerät: 15h/21d  Inode: 2974371     Verknüpfungen: 1
-Zugriff: (0600/-rw-------)  Uid: ( 1000/   florz)   Gid: ( 1000/   florz)
-Zugriff    : 2013-06-22 19:32:37.974073365 +0200
-Modifiziert: 2013-06-22 19:32:37.846073367 +0200
-Geändert   : 2013-06-22 19:32:37.970073365 +0200
- Geburt    : -
-
-florz@server:~$ stat annex-sync/gnucash/gnucash.gnucash
-  Datei: »annex-sync/gnucash/gnucash.gnucash“
-  Größe: 113902         Blöcke: 224        EA Block: 4096   Normale Datei
-Gerät: fc00h/64512d     Inode: 401737579   Verknüpfungen: 1
-Zugriff: (0600/-rw-------)  Uid: ( 1000/   florz)   Gid: ( 1000/   florz)
-Zugriff    : 2013-06-22 19:40:24.148876398 +0200
-Modifiziert: 2013-06-22 19:24:18.000000000 +0200
-Geändert   : 2013-06-22 19:24:26.817865369 +0200
- Geburt    : -
-"""]]
-
-after doing some changes in gnucash:
-[[!format sh """
-florz@notebook:~$ stat annex-sync/gnucash/gnucash.gnucash
-  Datei: »annex-sync/gnucash/gnucash.gnucash“
-  Größe: 114039         Blöcke: 240        EA Block: 4096   Normale Datei
-Gerät: 15h/21d  Inode: 2974990     Verknüpfungen: 1
-Zugriff: (0600/-rw-------)  Uid: ( 1000/   florz)   Gid: ( 1000/   florz)
-Zugriff    : 2013-06-22 19:52:12.226049268 +0200
-Modifiziert: 2013-06-22 19:52:12.342049265 +0200
-Geändert   : 2013-06-22 19:52:12.342049265 +0200
- Geburt    : -
-
-florz@server:~$ stat annex-sync/gnucash/gnucash.gnucash
-  Datei: »annex-sync/gnucash/gnucash.gnucash“
-  Größe: 113902         Blöcke: 224        EA Block: 4096   Normale Datei
-Gerät: fc00h/64512d     Inode: 401737579   Verknüpfungen: 1
-Zugriff: (0600/-rw-------)  Uid: ( 1000/   florz)   Gid: ( 1000/   florz)
-Zugriff    : 2013-06-22 19:40:24.148876398 +0200
-Modifiziert: 2013-06-22 19:24:18.000000000 +0200
-Geändert   : 2013-06-22 19:24:26.817865369 +0200
- Geburt    : -
-
-# after some time -> still no transfer
-
-florz@server:~$ stat annex-sync/gnucash/gnucash.gnucash
-  Datei: »annex-sync/gnucash/gnucash.gnucash“
-  Größe: 113902         Blöcke: 224        EA Block: 4096   Normale Datei
-Gerät: fc00h/64512d     Inode: 401737579   Verknüpfungen: 1
-Zugriff: (0600/-rw-------)  Uid: ( 1000/   florz)   Gid: ( 1000/   florz)
-Zugriff    : 2013-06-22 19:40:24.148876398 +0200
-Modifiziert: 2013-06-22 19:24:18.000000000 +0200
-Geändert   : 2013-06-22 19:24:26.817865369 +0200
- Geburt    : -
-"""]]
-
-doing a touch on the file:
-[[!format sh """
-florz@notebook:~$ touch annex-sync/gnucash/gnucash.gnucash
-florz@notebook:~$ stat annex-sync/gnucash/gnucash.gnucash
-  Datei: »annex-sync/gnucash/gnucash.gnucash“
-  Größe: 114039         Blöcke: 240        EA Block: 4096   Normale Datei
-Gerät: 15h/21d  Inode: 2974990     Verknüpfungen: 1
-Zugriff: (0600/-rw-------)  Uid: ( 1000/   florz)   Gid: ( 1000/   florz)
-Zugriff    : 2013-06-22 19:54:27.222046497 +0200
-Modifiziert: 2013-06-22 19:54:27.070046501 +0200
-Geändert   : 2013-06-22 19:54:27.214046498 +0200
- Geburt    : -
-
-#it syncs immediately
-
-florz@server:~$ stat annex-sync/gnucash/gnucash.gnucash
-  Datei: »annex-sync/gnucash/gnucash.gnucash“
-  Größe: 114039         Blöcke: 224        EA Block: 4096   Normale Datei
-Gerät: fc00h/64512d     Inode: 401737638   Verknüpfungen: 1
-Zugriff: (0600/-rw-------)  Uid: ( 1000/   florz)   Gid: ( 1000/   florz)
-Zugriff    : 2013-06-22 19:54:35.307056482 +0200
-Modifiziert: 2013-06-22 19:54:27.000000000 +0200
-Geändert   : 2013-06-22 19:54:34.787072264 +0200
- Geburt    : -
-"""]]
-
-on my notebook:
-[[!format sh """
-Everything up-to-date
-Everything up-to-date
-Everything up-to-date
-[2013-06-22 19:52:12 CEST] Watcher: file deleted gnucash/gnucash.gnucash.tmp-rFzA3U
-[2013-06-22 19:52:12 CEST] Committer: committing 1 changes
-[2013-06-22 19:52:12 CEST] Committer: Committing changes to git
-[2013-06-22 19:52:12 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-[2013-06-22 19:52:12 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"]
-[2013-06-22 19:52:12 CEST] Pusher: Syncing with server192.168.2.2, home192.168.1.3 
-[2013-06-22 19:52:12 CEST] Watcher: add direct gnucash/gnucash.gnucash.20130622195200.log
-[2013-06-22 19:52:12 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:12 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:12 CEST] Pusher: pushing to [Remote { name ="server192.168.2.2" },Remote { name ="home192.168.1.3" }]
-[2013-06-22 19:52:12 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","branch","-f","synced/master"]
-[2013-06-22 19:52:12 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","home192.168.1.3","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:52:12 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","server192.168.2.2","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:52:13 CEST] read: lsof ["-F0can","+d","/home/florz/annex-sync/.git/annex/tmp/"]
-[2013-06-22 19:52:13 CEST] Committer: Adding gnucash.g..95200.log
-ok
-(Recording state in git...)
-(Recording state in git...)
-
-
-
-(Recording state in git...)
-add gnucash/gnucash.gnucash.20130622195200.log (checksum...) [2013-06-22 19:52:13 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-t","blob","-w","--stdin"]
-[2013-06-22 19:52:13 CEST] Committer: committing 1 changes
-[2013-06-22 19:52:13 CEST] Committer: Committing changes to git
-[2013-06-22 19:52:13 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-[2013-06-22 19:52:13 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"]
-[2013-06-22 19:52:13 CEST] Committer: queued Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash.20130622195200.log Nothing : new file created
-[2013-06-22 19:52:13 CEST] Transferrer: Transferring: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash.20130622195200.log Nothing
-[2013-06-22 19:52:13 CEST] Committer: queued Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash.20130622195200.log Nothing : new file created
-[2013-06-22 19:52:13 CEST] call: /home/florz/bin/git-annex ["transferkeys","--readfd","29","--writefd","27"]
-[2013-06-22 19:52:13 CEST] TransferWatcher: transfer starting: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash.20130622195200.log Nothing
-[2013-06-22 19:52:14 CEST] Watcher: changed direct .gnucash/books/gnucash.gnucash.gcm
-[2013-06-22 19:52:14 CEST] Watcher: file deleted gnucash/gnucash.gnucash.7f0101.29284.LNK
-[2013-06-22 19:52:14 CEST] Watcher: file deleted gnucash/gnucash.gnucash.LCK
-[2013-06-22 19:52:14 CEST] Watcher: changed direct .gnucash/accelerator-map
-[2013-06-22 19:52:14 CEST] Watcher: changed direct .gnucash/expressions-2.0
-[2013-06-22 19:52:14 CEST] Watcher: changed direct .gnucash/stylesheets-2.0
-[2013-06-22 19:52:14 CEST] Watcher: add direct gnucash/gnucash.gnucash.20130622195212.log
-[2013-06-22 19:52:14 CEST] read: lsof ["-F0can","+d","/home/florz/annex-sync/.git/annex/tmp/"]
-[2013-06-22 19:52:14 CEST] Committer: Adding 5 files
-ok
-(Recording state in git...)
-add .gnucash/books/gnucash.gnucash.gcm (checksum...) [2013-06-22 19:52:15 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-t","blob","-w","--stdin"]
-ok
-add .gnucash/accelerator-map (checksum...) [2013-06-22 19:52:15 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-t","blob","-w","--stdin"]
-ok
-add .gnucash/expressions-2.0 (checksum...) [2013-06-22 19:52:15 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-t","blob","-w","--stdin"]
-ok
-add .gnucash/stylesheets-2.0 (checksum...) [2013-06-22 19:52:15 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-t","blob","-w","--stdin"]
-ok
-add gnucash/gnucash.gnucash.20130622195212.log (checksum...) [2013-06-22 19:52:15 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-t","blob","-w","--stdin"]
-[2013-06-22 19:52:15 CEST] Committer: committing 7 changes
-[2013-06-22 19:52:15 CEST] Committer: Committing changes to git
-[2013-06-22 19:52:15 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-To ssh://florz@192.168.1.3/home/florz/annex-sync/
-   7d4c30d..1954c7f  master -> synced/master
-[2013-06-22 19:52:15 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"]
-[2013-06-22 19:52:15 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:15 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:15 CEST] Merger: merging refs/remotes/home192.168.1.3/synced/master into refs/heads/master
-[2013-06-22 19:52:15 CEST] Committer: queued Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash.20130622195212.log Nothing : new file created
-[2013-06-22 19:52:15 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:15 CEST] Committer: queued Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash.20130622195212.log Nothing : new file created
-[2013-06-22 19:52:15 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:15 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:52:15 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync/.git/annex/merge/","merge","--no-edit","refs/remotes/home192.168.1.3/synced/master"]
-Already up-to-date.
-[2013-06-22 19:52:15 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:52:15 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","diff-tree","-z","--raw","--no-renames","-l0","-r","e1cb6c3b8bc0c851e6dab51271a4cde04815c50c","e1cb6c3b8bc0c851e6dab51271a4cde04815c50c"]
-To ssh://florz@192.168.2.2/home/florz/annex-sync/
-   7d4c30d..e1cb6c3  master -> synced/master
-[2013-06-22 19:52:16 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:16 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:16 CEST] Merger: merging refs/remotes/server192.168.2.2/synced/master into refs/heads/master
-[2013-06-22 19:52:16 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:16 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:16 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:52:16 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync/.git/annex/merge/","merge","--no-edit","refs/remotes/server192.168.2.2/synced/master"]
-Already up-to-date.
-[2013-06-22 19:52:16 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:52:16 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","diff-tree","-z","--raw","--no-renames","-l0","-r","e1cb6c3b8bc0c851e6dab51271a4cde04815c50c","e1cb6c3b8bc0c851e6dab51271a4cde04815c50c"]
-
-gnucash.gnucash.20130622195200.log
-
-         778 100%    0.00kB/s    0:00:00  
-         778 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-[2013-06-22 19:52:17 CEST] TransferWatcher: transfer starting: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash.20130622195200.log Just 778
-
-sent 876 bytes  received 31 bytes  201.56 bytes/sec
-total size is 778  speedup is 0.86
-[2013-06-22 19:52:17 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512", transferKey = Key {keyName = "8b8aa5c2cfe4466c6b897f7987246021468033301a696e2db0070386f7d0f3fd.log", keyBackendName = "SHA256E", keySize = Just 778, keyMtime = Nothing}}
-[2013-06-22 19:52:17 CEST] Transferrer: Uploaded gnucash.g..95200.log
-[2013-06-22 19:52:17 CEST] Transferrer: Transferring: Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash.20130622195212.log Nothing
-[2013-06-22 19:52:17 CEST] TransferWatcher: transfer starting: Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash.20130622195212.log Nothing
-[2013-06-22 19:52:18 CEST] Pusher: Syncing with server192.168.2.2, home192.168.1.3 
-[2013-06-22 19:52:18 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-w","--stdin-paths"]
-[2013-06-22 19:52:18 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","write-tree"]
-[2013-06-22 19:52:18 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit-tree","f2463d30e73fec86e14c9df4bcae5e568398a503","-p","refs/heads/git-annex"]
-[2013-06-22 19:52:18 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-ref","refs/heads/git-annex","776258f91d4245ffe13117a771dc8c7723867c1a"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:18 CEST] Pusher: pushing to [Remote { name ="server192.168.2.2" },Remote { name ="home192.168.1.3" }]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:52:18 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","branch","-f","synced/master"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:18 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","server192.168.2.2","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:52:18 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","home192.168.1.3","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..776258f91d4245ffe13117a771dc8c7723867c1a","--oneline","-n1"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e7d4504abea59b0b59659908ba771783acc6cd55","--oneline","-n1"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:18 CEST] Merger: merging refs/heads/synced/master into refs/heads/master
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:52:18 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync/.git/annex/merge/","merge","--no-edit","refs/heads/synced/master"]
-Already up-to-date.
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:52:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","diff-tree","-z","--raw","--no-renames","-l0","-r","e1cb6c3b8bc0c851e6dab51271a4cde04815c50c","e1cb6c3b8bc0c851e6dab51271a4cde04815c50c"]
-
-gnucash.gnucash.20130622195212.log
-
-         411 100%    0.00kB/s    0:00:00  
-         411 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-[2013-06-22 19:52:20 CEST] TransferWatcher: transfer starting: Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash.20130622195212.log Just 411
-
-sent 509 bytes  received 31 bytes  154.29 bytes/sec
-total size is 411  speedup is 0.76
-[2013-06-22 19:52:20 CEST] Transferrer: Uploaded gnucash.g..95212.log
-[2013-06-22 19:52:20 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "84bab1ab-238f-4602-953a-a297aab6da44", transferKey = Key {keyName = "36e8842e91f7577d12992724c8f52586e9ea7cb0234312dc5544ea4dc6f6c39a.log", keyBackendName = "SHA256E", keySize = Just 411, keyMtime = Nothing}}
-[2013-06-22 19:52:20 CEST] Transferrer: Transferring: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash.20130622195212.log Nothing
-[2013-06-22 19:52:20 CEST] TransferWatcher: transfer starting: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash.20130622195212.log Nothing
-To ssh://florz@192.168.1.3/home/florz/annex-sync/
-   e7d4504..776258f  git-annex -> synced/git-annex
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..776258f91d4245ffe13117a771dc8c7723867c1a","--oneline","-n1"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e7d4504abea59b0b59659908ba771783acc6cd55","--oneline","-n1"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:21 CEST] Merger: merging refs/remotes/home192.168.1.3/synced/master into refs/heads/master
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:52:21 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync/.git/annex/merge/","merge","--no-edit","refs/remotes/home192.168.1.3/synced/master"]
-Already up-to-date.
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:52:21 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","diff-tree","-z","--raw","--no-renames","-l0","-r","e1cb6c3b8bc0c851e6dab51271a4cde04815c50c","e1cb6c3b8bc0c851e6dab51271a4cde04815c50c"]
-
-gnucash.gnucash.20130622195212.log
-
-         411 100%    0.00kB/s    0:00:00  
-         411 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-[2013-06-22 19:52:21 CEST] TransferWatcher: transfer starting: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash.20130622195212.log Just 411
-
-sent 509 bytes  received 31 bytes  360.00 bytes/sec
-total size is 411  speedup is 0.76
-[2013-06-22 19:52:22 CEST] Transferrer: Uploaded gnucash.g..95212.log
-[2013-06-22 19:52:22 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512", transferKey = Key {keyName = "36e8842e91f7577d12992724c8f52586e9ea7cb0234312dc5544ea4dc6f6c39a.log", keyBackendName = "SHA256E", keySize = Just 411, keyMtime = Nothing}}
-[2013-06-22 19:52:22 CEST] Transferrer: Transferring: Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash.20130622195200.log Nothing
-[2013-06-22 19:52:22 CEST] TransferWatcher: transfer starting: Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash.20130622195200.log Nothing
-To ssh://florz@192.168.2.2/home/florz/annex-sync/
-   e7d4504..776258f  git-annex -> synced/git-annex
-[2013-06-22 19:52:22 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:52:22 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:22 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..776258f91d4245ffe13117a771dc8c7723867c1a","--oneline","-n1"]
-[2013-06-22 19:52:22 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e7d4504abea59b0b59659908ba771783acc6cd55","--oneline","-n1"]
-[2013-06-22 19:52:22 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:52:22 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-git-annex-shell: key is already present in annex
-rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
-[2013-06-22 19:52:22 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "84bab1ab-238f-4602-953a-a297aab6da44", transferKey = Key {keyName = "8b8aa5c2cfe4466c6b897f7987246021468033301a696e2db0070386f7d0f3fd.log", keyBackendName = "SHA256E", keySize = Just 778, keyMtime = Nothing}}
-git-annex-shell: key is already present in annex
-rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
-[2013-06-22 19:52:24 CEST] Pusher: Syncing with server192.168.2.2, home192.168.1.3 
-[2013-06-22 19:52:24 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-w","--stdin-paths"]
-[2013-06-22 19:52:24 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","write-tree"]
-[2013-06-22 19:52:24 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit-tree","1641422d48162f533f80693486d7c5a1208b9fcf","-p","refs/heads/git-annex"]
-[2013-06-22 19:52:24 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-ref","refs/heads/git-annex","48cfe2eb07d63d4a59c237994eb07896c92ef1c4"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:52:24 CEST] Pusher: pushing to [Remote { name ="server192.168.2.2" },Remote { name ="home192.168.1.3" }]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:52:24 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","branch","-f","synced/master"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:24 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","server192.168.2.2","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:52:24 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","home192.168.1.3","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..48cfe2eb07d63d4a59c237994eb07896c92ef1c4","--oneline","-n1"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e7d4504abea59b0b59659908ba771783acc6cd55","--oneline","-n1"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..776258f91d4245ffe13117a771dc8c7723867c1a","--oneline","-n1"]
-[2013-06-22 19:52:24 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..48cfe2eb07d63d4a59c237994eb07896c92ef1c4","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..df87e3bef80902abc6d48ce0fbfe3432c790cd21","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..776258f91d4245ffe13117a771dc8c7723867c1a","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","df87e3bef80902abc6d48ce0fbfe3432c790cd21"]
-[2013-06-22 19:52:25 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-t","blob","-w","--stdin"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","df87e3bef80902abc6d48ce0fbfe3432c790cd21..refs/heads/git-annex","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","write-tree"]
-[2013-06-22 19:52:25 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit-tree","5bf44cd143b2c35a44e609e083af23093eb02028","-p","refs/heads/git-annex","-p","df87e3bef80902abc6d48ce0fbfe3432c790cd21"]
-[2013-06-22 19:52:25 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-ref","refs/heads/git-annex","4cd264f192611f5a0d76e54d31329921a650f896"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..4cd264f192611f5a0d76e54d31329921a650f896","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..df87e3bef80902abc6d48ce0fbfe3432c790cd21","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..776258f91d4245ffe13117a771dc8c7723867c1a","--oneline","-n1"]
-[2013-06-22 19:52:25 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-To ssh://florz@192.168.1.3/home/florz/annex-sync/
-   df87e3b..4cd264f  git-annex -> synced/git-annex
-[2013-06-22 19:52:26 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:52:26 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..4cd264f192611f5a0d76e54d31329921a650f896","--oneline","-n1"]
-[2013-06-22 19:52:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..df87e3bef80902abc6d48ce0fbfe3432c790cd21","--oneline","-n1"]
-[2013-06-22 19:52:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:52:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..776258f91d4245ffe13117a771dc8c7723867c1a","--oneline","-n1"]
-[2013-06-22 19:52:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-To ssh://florz@192.168.2.2/home/florz/annex-sync/
-   776258f..4cd264f  git-annex -> synced/git-annex
-[2013-06-22 19:52:28 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:52:28 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:52:28 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..4cd264f192611f5a0d76e54d31329921a650f896","--oneline","-n1"]
-[2013-06-22 19:52:28 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..df87e3bef80902abc6d48ce0fbfe3432c790cd21","--oneline","-n1"]
-[2013-06-22 19:52:28 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:52:28 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:53:18 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-[2013-06-22 19:54:27 CEST] Watcher: changed direct gnucash/gnucash.gnucash
-[2013-06-22 19:54:27 CEST] read: lsof ["-F0can","+d","/home/florz/annex-sync/.git/annex/tmp/"]
-[2013-06-22 19:54:27 CEST] Committer: Adding gnucash.gnucash
-ok
-(Recording state in git...)
-
-
-(Recording state in git...)
-
-
-(Recording state in git...)
-(merging synced/git-annex into git-annex...)
-(Recording state in git...)
-add gnucash/gnucash.gnucash (checksum...) [2013-06-22 19:54:27 CEST] read: sha256sum ["/home/florz/annex-sync/.git/annex/tmp/gnucash25536.gnucash"]
-[2013-06-22 19:54:27 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-t","blob","-w","--stdin"]
-[2013-06-22 19:54:27 CEST] Committer: committing 1 changes
-[2013-06-22 19:54:27 CEST] Committer: Committing changes to git
-[2013-06-22 19:54:27 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"]
-[2013-06-22 19:54:27 CEST] Committer: queued Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash Nothing : new file created
-[2013-06-22 19:54:27 CEST] Pusher: Syncing with server192.168.2.2, home192.168.1.3 
-[2013-06-22 19:54:27 CEST] Transferrer: Transferring: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash Nothing
-[2013-06-22 19:54:27 CEST] Committer: queued Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash Nothing : new file created
-[2013-06-22 19:54:27 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-w","--stdin-paths"]
-[2013-06-22 19:54:27 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","write-tree"]
-[2013-06-22 19:54:27 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit-tree","4c81716cf1a0e0df472ffb43770ac8a27ca45420","-p","refs/heads/git-annex"]
-[2013-06-22 19:54:27 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-ref","refs/heads/git-annex","e9e2f951a5c1c645447ccc565bc3def9caeff93c"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:54:27 CEST] Pusher: pushing to [Remote { name ="server192.168.2.2" },Remote { name ="home192.168.1.3" }]
-[2013-06-22 19:54:27 CEST] TransferWatcher: transfer starting: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash Nothing
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:27 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","branch","-f","synced/master"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:27 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","server192.168.2.2","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:54:27 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","home192.168.1.3","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e9e2f951a5c1c645447ccc565bc3def9caeff93c","--oneline","-n1"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..df87e3bef80902abc6d48ce0fbfe3432c790cd21","--oneline","-n1"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..4cd264f192611f5a0d76e54d31329921a650f896","--oneline","-n1"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:54:27 CEST] Merger: merging refs/heads/synced/master into refs/heads/master
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:54:27 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync/.git/annex/merge/","merge","--no-edit","refs/heads/synced/master"]
-Already up-to-date.
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:54:27 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","diff-tree","-z","--raw","--no-renames","-l0","-r","e41ffae310ed2a50058b2f963decde4f9bc10a14","e41ffae310ed2a50058b2f963decde4f9bc10a14"]
-
-
-
-gnucash.gnucash
-
-       32768  28%    0.00kB/s    0:00:00  [2
-      114039 100%   15.50MB/s    0:00:00 (xfer#1, to-check=0/1)
-013-06-22 19:54:28 CEST] TransferWatcher: transfer starting: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash Just 32768
-[2013-06-22 19:54:28 CEST] TransferWatcher: transfer starting: Upload UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512" gnucash/gnucash.gnucash Just 114039
-To ssh://florz@192.168.1.3/home/florz/annex-sync/
-   4cd264f..e9e2f95  git-annex -> synced/git-annex
-   e1cb6c3..e41ffae  master -> synced/master
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e9e2f951a5c1c645447ccc565bc3def9caeff93c","--oneline","-n1"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..df87e3bef80902abc6d48ce0fbfe3432c790cd21","--oneline","-n1"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..4cd264f192611f5a0d76e54d31329921a650f896","--oneline","-n1"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:54:33 CEST] Merger: merging refs/remotes/home192.168.1.3/synced/master into refs/heads/master
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:54:33 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync/.git/annex/merge/","merge","--no-edit","refs/remotes/home192.168.1.3/synced/master"]
-Already up-to-date.
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/ann
-sent 114130 bytes  received 31 bytes  20756.55 bytes/sec
-total size is 114039  espeedup is 1.00
-x-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:54:33 CEST] Transferrer: Uploaded gnucash.gnucash
-[2013-06-22 19:54:33 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "dc591dd7-2446-45c6-84dc-55bdf79e7512", transferKey = Key {keyName = "91ec950e4004863219ea33f1398ea4308e0969267c207272e046858ede8bf9d9", keyBackendName = "SHA256E", keySize = Just 114039, keyMtime = Nothing}}
-[2013-06-22 19:54:33 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","diff-tree","-z","--raw","--no-renames","-l0","-r","e41ffae310ed2a50058b2f963decde4f9bc10a14","e41ffae310ed2a50058b2f963decde4f9bc10a14"]
-[2013-06-22 19:54:33 CEST] Transferrer: Transferring: Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash Nothing
-[2013-06-22 19:54:33 CEST] TransferWatcher: transfer starting: Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash Nothing
-
-gnucash.gnucash
-
-       32768  28%    0.00kB/s    0:00:00  
-      114039 100%   19.38MB/s    0:00:00 (xfer#1, to-check=0/1)
-[2013-06-22 19:54:33 CEST] TransferWatcher: transfer starting: Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash Just 32768
-[2013-06-22 19:54:33 CEST] TransferWatcher: transfer starting: Upload UUID "84bab1ab-238f-4602-953a-a297aab6da44" gnucash/gnucash.gnucash Just 114039
-To ssh://florz@192.168.2.2/home/florz/annex-sync/
-   4cd264f..e9e2f95  git-annex -> synced/git-annex
-   e1cb6c3..e41ffae  master -> synced/master
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e9e2f951a5c1c645447ccc565bc3def9caeff93c","--oneline","-n1"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..df87e3bef80902abc6d48ce0fbfe3432c790cd21","--oneline","-n1"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:54:34 CEST] Merger: merging refs/remotes/server192.168.2.2/synced/master into refs/heads/master
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:54:34 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync/.git/annex/merge/","merge","--no-edit","refs/remotes/server192.168.2.2/synced/master"]
-Already up-to-date.
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/master"]
-[2013-06-22 19:54:34 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","diff-tree","-z","--raw","--no-renames","-l0","-r","e41ffae310ed2a50058b2f963decde4f9bc10a14","e41ffae310ed2a50058b2f963decde4f9bc10a14"]
-
-sent 114130 bytes  received 31 bytes  45664.40 bytes/sec
-total size is 114039  speedup is 1.00
-[2013-06-22 19:54:35 CEST] Transferrer: Uploaded gnucash.gnucash
-[2013-06-22 19:54:35 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "84bab1ab-238f-4602-953a-a297aab6da44", transferKey = Key {keyName = "91ec950e4004863219ea33f1398ea4308e0969267c207272e046858ede8bf9d9", keyBackendName = "SHA256E", keySize = Just 114039, keyMtime = Nothing}}
-[2013-06-22 19:54:36 CEST] Pusher: Syncing with server192.168.2.2, home192.168.1.3 
-[2013-06-22 19:54:36 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-w","--stdin-paths"]
-[2013-06-22 19:54:36 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","write-tree"]
-[2013-06-22 19:54:36 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit-tree","fb43dcef4baa4b928faec6622a4f7889125c6c0a","-p","refs/heads/git-annex"]
-[2013-06-22 19:54:36 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-ref","refs/heads/git-annex","b74b3402e31d7394815733811b9668b00cc51aa9"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","symbolic-ref","HEAD"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","refs/heads/master"]
-[2013-06-22 19:54:36 CEST] Pusher: pushing to [Remote { name ="server192.168.2.2" },Remote { name ="home192.168.1.3" }]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:36 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","branch","-f","synced/master"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:36 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","server192.168.2.2","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:54:36 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","home192.168.1.3","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..b74b3402e31d7394815733811b9668b00cc51aa9","--oneline","-n1"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..df87e3bef80902abc6d48ce0fbfe3432c790cd21","--oneline","-n1"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e9e2f951a5c1c645447ccc565bc3def9caeff93c","--oneline","-n1"]
-[2013-06-22 19:54:36 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:39 CEST] read: git ["--gitTo ssh://florz@192.168.1.3/home/florz/annex-sync/
-- ! [rejected]        dgit-annex -> synced/git-annexi (r=/non-fast-forwardh)o
-me/florz/aerror: failed to push some refs to 'ssh://florz@192.168.1.3/home/florz/annex-sync/'
-nTo prevent you from losing history, non-fast-forward updates were rejected
-Merge the remote changes (e.g. 'git pull') before pushing again.  See the
-'Note about fast-forwards' section of 'git push --help' for details.
-nex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..b74b3402e31d7394815733811b9668b00cc51aa9","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..89e2137442dfdb06facbaba3079873d90c7af281","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e9e2f951a5c1c645447ccc565bc3def9caeff93c","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] feed: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-index","-z","--index-info"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","89e2137442dfdb06facbaba3079873d90c7af281"]
-[2013-06-22 19:54:39 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","hash-object","-t","blob","-w","--stdin"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","89e2137442dfdb06facbaba3079873d90c7af281..refs/heads/git-annex","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","write-tree"]
-[2013-06-22 19:54:39 CEST] chat: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","commit-tree","f175a05b82160942363f46bf1af3e7af1660dfa1","-p","refs/heads/git-annex","-p","89e2137442dfdb06facbaba3079873d90c7af281"]
-[2013-06-22 19:54:39 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","update-ref","refs/heads/git-annex","fabac4b203dce9e812b4637f7e95375b15a3f739"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..fabac4b203dce9e812b4637f7e95375b15a3f739","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..89e2137442dfdb06facbaba3079873d90c7af281","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e9e2f951a5c1c645447ccc565bc3def9caeff93c","--oneline","-n1"]
-[2013-06-22 19:54:39 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-To ssh://florz@192.168.2.2/home/florz/annex-sync/
-   e9e2f95..fabac4b  git-annex -> synced/git-annex
-[2013-06-22 19:54:40 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:40 CEST] Pusher: trying manual pull to resolve failed pushes
-[2013-06-22 19:54:40 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:40 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..fabac4b203dce9e812b4637f7e95375b15a3f739","--oneline","-n1"]
-[2013-06-22 19:54:40 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..89e2137442dfdb06facbaba3079873d90c7af281","--oneline","-n1"]
-[2013-06-22 19:54:40 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:40 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..e9e2f951a5c1c645447ccc565bc3def9caeff93c","--oneline","-n1"]
-[2013-06-22 19:54:40 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:54:40 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","fetch","home192.168.1.3"]
-From ssh://192.168.1.3/home/florz/annex-sync
-   e9e2f95..89e2137  synced/git-annex -> home192.168.1.3/synced/git-annex
-[2013-06-22 19:54:42 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:42 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:42 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..fabac4b203dce9e812b4637f7e95375b15a3f739","--oneline","-n1"]
-[2013-06-22 19:54:42 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..89e2137442dfdb06facbaba3079873d90c7af281","--oneline","-n1"]
-[2013-06-22 19:54:42 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:43 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:54:43 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:43 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:43 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..fabac4b203dce9e812b4637f7e95375b15a3f739","--oneline","-n1"]
-[2013-06-22 19:54:43 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..89e2137442dfdb06facbaba3079873d90c7af281","--oneline","-n1"]
-[2013-06-22 19:54:43 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:43 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-[2013-06-22 19:54:43 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--verify","-q","refs/remotes/home192.168.1.3/master"]
-[2013-06-22 19:54:43 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/master..refs/remotes/home192.168.1.3/master","--oneline","-n1"]
-[2013-06-22 19:54:43 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--verify","-q","refs/remotes/home192.168.1.3/synced/master"]
-[2013-06-22 19:54:43 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/synced/master..refs/remotes/home192.168.1.3/synced/master","--oneline","-n1"]
-[2013-06-22 19:54:43 CEST] Pusher: pushing to [Remote { name ="home192.168.1.3" }]
-[2013-06-22 19:54:43 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","branch","-f","synced/master"]
-[2013-06-22 19:54:43 CEST] call: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","push","home192.168.1.3","git-annex:synced/git-annex","master:synced/master"]
-[2013-06-22 19:54:45 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:45 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:45 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..fabac4b203dce9e812b4637f7e95375b15a3f739","--oneline","-n1"]
-[2013-06-22 19:54:45 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:45 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..89e2137442dfdb06facbaba3079873d90c7af281","--oneline","-n1"]
-[2013-06-22 19:54:45 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-Everything up-to-date
-[2013-06-22 19:54:46 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","git-annex"]
-[2013-06-22 19:54:46 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","show-ref","--hash","refs/heads/git-annex"]
-[2013-06-22 19:54:47 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..fabac4b203dce9e812b4637f7e95375b15a3f739","--oneline","-n1"]
-[2013-06-22 19:54:47 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..69a00fc4a2079b3a87725cc0e3e8b8a1e3a9ae20","--oneline","-n1"]
-[2013-06-22 19:54:47 CEST] read: git ["--git-dir=/home/florz/annex-sync/.git","--work-tree=/home/florz/annex-sync","log","refs/heads/git-annex..3c87a082e3b5340597dc59b9d5963b191f24a936","--oneline","-n1"]
-"""]]
-
-[[!tag /design/assistant]]
-[[!meta title="hard link to open file which is then deleted"]]
-
-> I have fixed this bug. [[done]] --[[Joey]]
diff --git a/doc/bugs/Problems_with_syncing_gnucash/comment_1_ca195af3ba4a286eb5ab687634192fa4._comment b/doc/bugs/Problems_with_syncing_gnucash/comment_1_ca195af3ba4a286eb5ab687634192fa4._comment
deleted file mode 100644
index 481f65d5b..000000000
--- a/doc/bugs/Problems_with_syncing_gnucash/comment_1_ca195af3ba4a286eb5ab687634192fa4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.193"
- subject="comment 1"
- date="2013-06-25T17:30:05Z"
- content="""
-First of all, are you sure that git-annex is even the right tool for this job? gnucash files tend to be pretty small, and are easy to check into git directly. What happens if two machines make conflicting edits, and the git-annex assistant automatically resolves the merge conflict by moving files around and making .variant copies of gnucash log files?
-"""]]
diff --git a/doc/bugs/Problems_with_syncing_gnucash/comment_2_754fb430381ad88e6248ecb902b32118._comment b/doc/bugs/Problems_with_syncing_gnucash/comment_2_754fb430381ad88e6248ecb902b32118._comment
deleted file mode 100644
index ff81b4d98..000000000
--- a/doc/bugs/Problems_with_syncing_gnucash/comment_2_754fb430381ad88e6248ecb902b32118._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.193"
- subject="comment 2"
- date="2013-06-25T17:49:08Z"
- content="""
-I was able to reproduce this with gnucash, and came up with a small test case:
-
-[[!format perl \"\"\"
-my $foo=\"foo\";
-open(OUT, \">$foo.new\");
-link(\"$foo.new\", \"$foo\");
-unlink(\"$foo.new\");
-close OUT;
-\"\"\"]]
-
-This defeats the watcher, which sees the file be opened for write, and then deleted before it's closed. To fix this it would need to correlate the hard link with the original file, to know that when the original file is closed, the hard link can now be safely added to the annex.
-
-The daily sanity checker will find and eventually add these files, or the assistant will see them the next time it's started.
-"""]]
diff --git a/doc/bugs/Problems_with_syncing_gnucash/comment_4_25881998c6f149c70b1358f37b7c66ba._comment b/doc/bugs/Problems_with_syncing_gnucash/comment_4_25881998c6f149c70b1358f37b7c66ba._comment
deleted file mode 100644
index 509ef4a5c..000000000
--- a/doc/bugs/Problems_with_syncing_gnucash/comment_4_25881998c6f149c70b1358f37b7c66ba._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl99Gxq3NPNvwZHp3PDufaknQH4rZb_KKY"
- nickname="Florian"
- subject="comment 4"
- date="2013-06-27T01:52:03Z"
- content="""
-Thanks for the quick fix! I'm always amazed how fasts you find fixes for such problems. This qualified you for a flattr subscription (I know it's not much but if more people did this...). I didn't test the fix but I'm nearly sure it will work with the next release :-)
-
-I know that my expectations in this project are a little bit high and I see how much work it was to get where we are now. Once again thank you for the excellent work done so far. I don't fear to synchronize important data with git-annex. I even use git-annex to backup and synchronize the member database for our club (wannabe hackerspace). As soon as cabal downloads an compiles your latest release my last problems will be gone (the locking problem).
-
-I know about the remaining problems and thus use git-annex with care. Of course you didn't imagine all use cases in the beginning and maybe some are impossible to realise but as I already said, we are on a very good way! :-)
-
-My vision is to get rid of any centralized service (even the XMPP part -> maybe you could add add a global polling/watchdog/keepalive option for SSH only setups (in case one node died/wasn't started) ). At the moment this already works as long as git-annex runs on all machines. I already synced several thousands of private photos just by using SSH so thanks again! :-)
-
-An other vision (I know I'm not speaking for the majority and this is still utopic...) is to decentralize my home directory and to enable collaboration (e.g. on our club database (of course not simultaneously)). At my university AFS is used to store home and project directories. This filesystem also suffers from race conditions and file locking is only as good as each application implemented it but we still use it because it is sufficient. I am sure that git-annex is not far from this state and it could even do more (-> lock files as long as they are opened on one machine).
-
-One last thing I can imagine for now is to improve the synchronization speed. At least for me git-annex seems quite slow in syncing smaller files over high latency connections. Do you close ssh connections after each file and do you use something like the the fuzzy option in rsync (for moved/renamed logfiles/backups (once again one of these little problem with the management tool for our club))?
-
-I hope you don't get me wrong for this. I never before wrote any bug reports so take this as an other success of your project. ;-) I really hope it will get to the point I described above and I can assure you that it is already way better than what I tried to use before. Keep up the good work!
-"""]]
diff --git a/doc/bugs/Provide_64-bit_standalone_build.mdwn b/doc/bugs/Provide_64-bit_standalone_build.mdwn
deleted file mode 100644
index 7f24e0055..000000000
--- a/doc/bugs/Provide_64-bit_standalone_build.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-The 32-bit standalone build appears to require two libraries (lib32-libyaml and lib32-gsasl) that are not available on Arch Linux. [See the comments on the AUR package](https://aur.archlinux.org/packages/git-annex-bin/). I'd appreciate it if you could bring back the 64-bit build.
-
-> [[done]], based on <https://aur.archlinux.org/packages/git-annex-bin/>
-> they are managing with what I am providing. Also, Arch Linux has a
-> proper build of git-annex from source, so I'm not going to worry about
-> git-annex-bin, the rationalle for which I don't even understand. --[[Joey]]
diff --git a/doc/bugs/Provide_64-bit_standalone_build/comment_1_1850bb3eb464f1d3c122cfeb4ccaf265._comment b/doc/bugs/Provide_64-bit_standalone_build/comment_1_1850bb3eb464f1d3c122cfeb4ccaf265._comment
deleted file mode 100644
index 76e8d0d5c..000000000
--- a/doc/bugs/Provide_64-bit_standalone_build/comment_1_1850bb3eb464f1d3c122cfeb4ccaf265._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-03T21:32:39Z"
- content="""
-Thanks for the heads up. 
-
-As far as I can see, the necessary libraries are included in the standalone build. So it should work when used as intended via `runshell`.
-
-But that's not what the AUR is doing. It's binary editing (!!) the git-annex binary to use different library sonames, and taking the git-annex binary and dropping it unprotected into a system it was not built for to fend for itself. 
-That strikes me as a technique that is unlikely to continue working, and one that I cannot commit to support.
-
-I don't want to cause you Arch people unnecessary work, but building a 64 bit standalone build every time I release git-annex is unnecessary work on my part, as long as the 32 bit one works everywhere when used as designed. If someone has to do this 64 bit build, why not you? This would also avoid any further breakage, since you could build it against the actual library sonames it's going to be used with on Arch.
-"""]]
diff --git a/doc/bugs/Remote_repo_and_set_operation_with_find.mdwn b/doc/bugs/Remote_repo_and_set_operation_with_find.mdwn
deleted file mode 100644
index 3e1acd4a8..000000000
--- a/doc/bugs/Remote_repo_and_set_operation_with_find.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-Currently, git annex find lists files that are present in the current repository, possibly restricted to a subdirectory. But it does not easily seem possible to get this information about a remote repository.
-
-I would find it useful if this command understood flags that makes it tell me what is present somewhere else (maybe "--on remote") and combinations of the flags ("--on remote1 --and --not-on remote2" or "--on disk1 --or --on disk2").
-
-> Almost. You're looking for `--in remote`, which was added 2 months ago.
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository.mdwn b/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository.mdwn
deleted file mode 100644
index a051a8170..000000000
--- a/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository.mdwn
+++ /dev/null
@@ -1,70 +0,0 @@
-### Please describe the problem.
-
-I've setup two (actually more) direct mode repositories pointing at each other with ssh keys allowing them to talk to each other. I run the assistant in both repositories. Once I add a file to one repository I can see in the assistant log that it's been sent to the other side but it doesn't show up. Once I add a file to the other repository both repositories get both files.
-
-### What steps will reproduce the problem?
-
-In the first host:
-[[!format sh """
-$ ls -l
-total 0
-$ date | tee fromhostA
-Fri May 31 19:25:12 WEST 2013
-"""]]
-
-And then in the second host
-
-[[!format sh """
-$ ls
-$ date | tee fromhostB
-Fri May 31 19:25:27 WEST 2013
-$ ls
-fromhostB
-$ ls # After a little while
-fromhostA  fromhostB
-"""]]
-
-Back at hostA
-
-[[!format sh """
-$ ls -l
-total 8
--rw-r--r-- 1 pedrocr pedrocr 30 May 31 19:25 fromhostA
--rw-r--r-- 1 pedrocr pedrocr 30 May 31 19:25 fromhostB
-"""]]
-
-I looked at the logs for hostA and it seemed like it was pushing the changes right away. In hostB this is the moment where fromhostB gets added:
-
-[[!format sh """
-[2013-05-31 19:22:04 WEST] Pusher: Syncing with zeus, wintermute, ulisses 
-[2013-05-31 19:25:27 WEST] Committer: Adding fromhostB
-
-(merging zeus/git-annex into git-annex...)
-(Recording state in git...)
-(merging wintermute/git-annex into git-annex...)
-(Recording state in git...)
-(merging ulisses/git-annex into git-annex...)
-(Recording state in git...)
-"""]]
-
-It seems to be that merging in the remotes only gets done when there's an added file and that's why fromhostA didn't show up until fromhostB was there. I don't think this is the correct behavior. I want to be able to setup a new repository with other repositories as remotes and have it automatically pull in all the contents without having to create content itself.
-
-### What version of git-annex are you using? On what operating system?
-
-[[!format sh """
-$ git annex version
-git-annex version: 4.20130516.1
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-local repository version: 4
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-$ lsb_release -a
-No LSB modules are available.
-Distributor ID:	Ubuntu
-Description:	Ubuntu 12.04.2 LTS
-Release:	12.04
-Codename:	precise
-"""]]
-
-> [[done]]; see comment --[[Joey]] 
diff --git a/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_1_92211091daf9827a4ec7e5b5a6769d59._comment b/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_1_92211091daf9827a4ec7e5b5a6769d59._comment
deleted file mode 100644
index 0daa25b7f..000000000
--- a/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_1_92211091daf9827a4ec7e5b5a6769d59._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-31T21:12:52Z"
- content="""
-How are you creating the repositories? git cannot merge origin/master into master when master does not exist yet. The assistant, when it creates a repository, makes an empty commit, to create the master branch, which should avoid this problem.
-"""]]
diff --git a/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_2_f0fa97a9eba1c624f6f8720ba8a160b7._comment b/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_2_f0fa97a9eba1c624f6f8720ba8a160b7._comment
deleted file mode 100644
index cee6bce0d..000000000
--- a/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_2_f0fa97a9eba1c624f6f8720ba8a160b7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkx5V3MTbzCXS3J7Mn9FEq8M9bPPYMkAHY"
- nickname="Pedro"
- subject="comment 2"
- date="2013-05-31T21:48:43Z"
- content="""
-I'm doing everything by hand. I just do \"git init\" and \"git annex init\" in an empty directory, and then do \"git remote add ...\" to add the ssh remotes to each other. After that I launch \"git annex assistant\".
-"""]]
diff --git a/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_3_e3d677ea4170c07cd31efe6dc85fa5f3._comment b/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_3_e3d677ea4170c07cd31efe6dc85fa5f3._comment
deleted file mode 100644
index 1e563d409..000000000
--- a/doc/bugs/Remotes_only_start_showing_changes_after_both_sides_have_written_to_the_repository/comment_3_e3d677ea4170c07cd31efe6dc85fa5f3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-06-11T14:23:31Z"
- content="""
-This then explains your problem. If you're going to set things up by hand you need to do the same setup that the assistant does of making an initial commit, which can be empty.
-"""]]
diff --git a/doc/bugs/Repository_deletion_error.mdwn b/doc/bugs/Repository_deletion_error.mdwn
deleted file mode 100644
index 33142d8dd..000000000
--- a/doc/bugs/Repository_deletion_error.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-**What steps will reproduce the problem?**
-
-On the dashboard, click settings > Delete on the repo you want to remove.
-Wait for the dropping to finish.
-Start final deletion when the message "The repository "repo" has been emptied, and can now be removed." pops up.
-
-**What is the expected output? What do you see instead?**
-
-The repository should be deleted, but I only see "Internal Server Error: git [Param "remote",Param "remove",Param "repo"] failed".
-
-**What version of git-annex are you using? On what operating system?**
-
-Standalone build, git-annex version 4.20130417-g4bb97d5
-
-**Please provide any additional information below.**
-
-The log shows:
-
-     [2013-04-22 22:17:22 CEST] TransferScanner: The repository "repo" has been emptied, and can now be removed. 
-     error: Unknown subcommand: remove
-     usage: git remote [-v | --verbose]
-       or: git remote add [-t <branch>] [-m <master>] [-f] [--mirror=<fetch|push>] <name> <url>
-       or: git remote rename <old> <new>
-       or: git remote rm <name>
-       or: git remote set-head <name> (-a | -d | <branch>)
-       or: git remote [-v | --verbose] show [-n] <name>
-       or: git remote prune [-n | --dry-run] <name>
-       or: git remote [-v | --verbose] update [-p | --prune] [(<group> | <remote>)...]
-       or: git remote set-branches [--add] <name> <branch>...
-       or: git remote set-url <name> <newurl> [<oldurl>]
-       or: git remote set-url --add <name> <newurl>
-       or: git remote set-url --delete <name> <url>
-
-        -v, --verbose         be verbose; must be placed before a subcommand
-
-
-
-> Seems that `git remote remove` is new as of git 1.8.0 or so.
-> Older gits only support `git remote rm`. Which newer gits
-> support as well. but it seems to be in the process
-> of being deprecated so I'd rather not use it.
-> 
-> So, I've made the version of git it's
-> built for determine which subcommand it uses. [[done]] --[[Joey]]
-> 
-> (You can run `git remote rm repo` by hand to clean up from this BTW.)
diff --git a/doc/bugs/Repository_deletion_error/comment_1_31673d0300986b6098d1af2cc4b180c6._comment b/doc/bugs/Repository_deletion_error/comment_1_31673d0300986b6098d1af2cc4b180c6._comment
deleted file mode 100644
index 1ed723d12..000000000
--- a/doc/bugs/Repository_deletion_error/comment_1_31673d0300986b6098d1af2cc4b180c6._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-22T20:43:26Z"
- content="""
-It's running `git remote remove` to remove it. Your git appears not to support this, but mine (1.8.2) does. 
-
-What version of git do you have installed?
-"""]]
diff --git a/doc/bugs/Repository_in_manual_mode_does_not_hold_files.mdwn b/doc/bugs/Repository_in_manual_mode_does_not_hold_files.mdwn
deleted file mode 100644
index 9572487dd..000000000
--- a/doc/bugs/Repository_in_manual_mode_does_not_hold_files.mdwn
+++ /dev/null
@@ -1,305 +0,0 @@
-### Please describe the problem.
-
-I have two repositories in my local network which are locally paired and synced using git-annex assistant (setup using webapp, both in direct mode). The one (master) has all files and is in mode "full backup". The second one (slave) is in "manual" mode and should therefore only contain the file content it already has. But it also should not loose any content it has until I explicitely drop it but this is exactly what happens! Files are getting dropped (I think it happens during git-annex startup of the slave repository, but I am not sure).
-
-### What steps will reproduce the problem?
-
-1. Setup two repositories using git-annex webapp in local network
-2. Set one to "full backup" mode, the second to "manual" mode
-3. Add files to the master repository
-4. Pair both repositories over webapp
-5. Call git-annex get folderA on slave system to transfer some file contents to it.
-
-=> After some time the file contents from folderA seem to disappear on slave system.
-
-### What version of git-annex are you using? On what operating system?
-
-* Master (full backup) repository is running on Ubuntu Server 12.04 and git-annex 5.20140117.1 from PPA. Git version 1.7.9.5
-* Slave (manual) repository is running on Gentoo Linux with 5.20140116, created from own ebuild. Git version 1.8.4.5
-
-### Please provide any additional information below.
-
-[[!format sh """
-[2014-01-29 09:14:15 CET] main: starting assistant version 5.20140116
-[2014-01-29 09:19:33 CET] TransferScanner: Syncing with Eifel.fritz.box__mnt_raid_Media 
-Already up-to-date.
-
-(scanning...) [2014-01-29 09:19:34 CET] Watcher: Performing startup scan
-Already up-to-date.
-Already up-to-date.
-[2014-01-29 09:35:31 CET] Committer: Committing changes to git
-[2014-01-29 09:35:31 CET] Pusher: Syncing with Eifel.fritz.box__mnt_raid_Media 
-[2014-01-29 09:40:37 CET] Committer: Committing changes to git
-[2014-01-29 09:44:15 CET] Committer: Committing changes to git
-Von ssh://git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media
-   390c764..7775ce1  annex/direct/master -> Eifel.fritz.box__mnt_raid_Media/annex/direct/master
-   eca59d1..59db343  git-annex  -> Eifel.fritz.box__mnt_raid_Media/git-annex
- + a1f3176...7775ce1 synced/master -> Eifel.fritz.box__mnt_raid_Media/synced/master  (Aktualisierung erzwungen)
-Already up-to-date.
-error: Ref refs/heads/synced/master is at a1f3176ff3821cdd9aa74bfa310dfdccb8452247 but expected 7775ce196da4561367ee231ce116fe5849827c51
-remote: error: failed to lock refs/heads/synced/master        
-To ssh://fabian@git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media/
-   98219eb..3d2b713  git-annex -> synced/git-annex
- ! [remote rejected] annex/direct/master -> synced/master (failed to lock)
-error: Fehler beim Versenden einiger Referenzen nach 'ssh://fabian@git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media/'
-Von ssh://git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media
-   7775ce1..a1f3176  annex/direct/master -> Eifel.fritz.box__mnt_raid_Media/annex/direct/master
-   59db343..6e39b5b  git-annex  -> Eifel.fritz.box__mnt_raid_Media/git-annex
-   7775ce1..a1f3176  synced/master -> Eifel.fritz.box__mnt_raid_Media/synced/master
-Already up-to-date.
-[2014-01-29 09:51:41 CET] Committer: Committing changes to git
-error: Ref refs/heads/synced/git-annex is at 3d2b7131d39c78fc56f67e29617e72b177807449 but expected 98219eb545d5dc51da9984ede4b4c5c41ec188d0
-remote: error: failed to lock refs/heads/synced/git-annex        
-To ssh://fabian@git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media/
- ! [remote rejected] git-annex -> synced/git-annex (failed to lock)
-error: Fehler beim Versenden einiger Referenzen nach 'ssh://fabian@git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media/'
-To ssh://fabian@git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media/
-   3d2b713..5bd0d7e  git-annex -> synced/git-annex
-[2014-01-29 09:51:51 CET] Pusher: Syncing with Eifel.fritz.box__mnt_raid_Media 
-Everything up-to-date
-Everything up-to-date
-[2014-01-29 09:53:01 CET] Committer: Committing changes to git
-[2014-01-29 09:53:01 CET] Pusher: Syncing with Eifel.fritz.box__mnt_raid_Media 
-Everything up-to-date
-
-
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(merging synced/git-annex into git-annex...)
-(Recording state in git...)
-(merging synced/git-annex into git-annex...)
-(Recording state in git...)
-
-
-(Recording state in git...)
-(Recording state in git...)
-(started...) [2014-01-29 09:53:48 CET] Committer: Committing changes to git
-[2014-01-29 09:53:48 CET] Pusher: Syncing with Eifel.fritz.box__mnt_raid_Media 
-Everything up-to-date
-[2014-01-29 10:19:33 CET] NetWatcherFallback: Syncing with Eifel.fritz.box__mnt_raid_Media 
-Von ssh://git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media
-   6e39b5b..5bd0d7e  git-annex  -> Eifel.fritz.box__mnt_raid_Media/git-annex
-Everything up-to-date
-[2014-01-29 10:39:49 CET] Committer: Committing changes to git
-[2014-01-29 10:39:49 CET] Pusher: Syncing with Eifel.fritz.box__mnt_raid_Media 
-[2014-01-29 10:39:50 CET] Committer: Committing changes to git
-[2014-01-29 10:39:51 CET] Committer: Committing changes to git
-[2014-01-29 10:39:53 CET] Committer: Committing changes to git
-[2014-01-29 10:39:54 CET] Committer: Committing changes to git
-[2014-01-29 10:39:55 CET] Committer: Committing changes to git
-[2014-01-29 10:39:56 CET] Committer: Committing changes to git
-[2014-01-29 10:39:57 CET] Committer: Committing changes to git
-[2014-01-29 10:39:59 CET] Committer: Committing changes to git
-[2014-01-29 10:40:00 CET] Committer: Committing changes to git
-[2014-01-29 10:40:01 CET] Committer: Committing changes to git
-[2014-01-29 10:40:02 CET] Committer: Committing changes to git
-[2014-01-29 10:40:03 CET] Committer: Committing changes to git
-[2014-01-29 10:40:05 CET] Committer: Committing changes to git
-[2014-01-29 10:40:07 CET] Committer: Adding AlbumArtSmall.jpg Folder.jpg
-
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-add Audio/Musik/2raumwohnung/2002 - In Wirklich/AlbumArtSmall.jpg ok
-add Audio/Musik/2raumwohnung/2002 - In Wirklich/Folder.jpg [2014-01-29 10:40:07 CET] Committer: Committing changes to git
-[2014-01-29 10:40:08 CET] Committer: Committing changes to git
-[2014-01-29 10:40:09 CET] Committer: Committing changes to git
-[2014-01-29 10:40:11 CET] Committer: Committing changes to git
-[2014-01-29 10:40:12 CET] Committer: Committing changes to git
-[2014-01-29 10:40:13 CET] Committer: Committing changes to git
-[2014-01-29 10:40:14 CET] Committer: Committing changes to git
-[2014-01-29 10:40:16 CET] Committer: Committing changes to git
-[2014-01-29 10:40:17 CET] Committer: Committing changes to git
-[2014-01-29 10:40:18 CET] Committer: Committing changes to git
-[2014-01-29 10:40:19 CET] Committer: Committing changes to git
-[2014-01-29 10:40:20 CET] Committer: Committing changes to git
-[2014-01-29 10:40:21 CET] Committer: Committing changes to git
-[2014-01-29 10:40:23 CET] Committer: Committing changes to git
-[2014-01-29 10:40:24 CET] Committer: Committing changes to git
-[2014-01-29 10:40:26 CET] Committer: Committing changes to git
-[2014-01-29 10:40:27 CET] Committer: Committing changes to git
-[2014-01-29 10:40:28 CET] Committer: Committing changes to git
-[2014-01-29 10:40:29 CET] Committer: Committing changes to git
-[2014-01-29 10:40:30 CET] Committer: Committing changes to git
-[2014-01-29 10:40:31 CET] Committer: Committing changes to git
-[2014-01-29 10:40:32 CET] Committer: Committing changes to git
-[2014-01-29 10:40:34 CET] Committer: Committing changes to git
-[2014-01-29 10:40:35 CET] Committer: Committing changes to git
-[2014-01-29 10:40:36 CET] Committer: Committing changes to git
-[2014-01-29 10:40:37 CET] Committer: Committing changes to git
-[2014-01-29 10:40:39 CET] Committer: Committing changes to git
-[2014-01-29 10:40:40 CET] Committer: Committing changes to git
-[2014-01-29 10:40:41 CET] Committer: Committing changes to git
-[2014-01-29 10:40:42 CET] Committer: Committing changes to git
-[2014-01-29 10:40:44 CET] Committer: Committing changes to git
-[2014-01-29 10:40:45 CET] Committer: Committing changes to git
-[2014-01-29 10:40:46 CET] Committer: Committing changes to git
-[2014-01-29 10:40:47 CET] Committer: Committing changes to git
-[2014-01-29 10:40:48 CET] Committer: Committing changes to git
-[2014-01-29 10:40:50 CET] Committer: Committing changes to git
-[2014-01-29 10:40:51 CET] Committer: Committing changes to git
-[2014-01-29 10:40:52 CET] Committer: Committing changes to git
-[2014-01-29 10:40:53 CET] Committer: Committing changes to git
-[2014-01-29 10:40:54 CET] Committer: Committing changes to git
-[2014-01-29 10:40:55 CET] Committer: Committing changes to git
-[2014-01-29 10:40:57 CET] Committer: Committing changes to git
-[2014-01-29 10:40:58 CET] Committer: Committing changes to git
-[2014-01-29 10:40:59 CET] Committer: Committing changes to git
-[2014-01-29 10:41:00 CET] Committer: Committing changes to git
-[2014-01-29 10:41:02 CET] Committer: Committing changes to git
-[2014-01-29 10:41:03 CET] Committer: Committing changes to git
-[2014-01-29 10:41:04 CET] Committer: Committing changes to git
-[2014-01-29 10:41:05 CET] Committer: Committing changes to git
-[2014-01-29 10:41:06 CET] Committer: Committing changes to git
-[2014-01-29 10:41:07 CET] Committer: Committing changes to git
-[2014-01-29 10:41:09 CET] Committer: Committing changes to git
-[2014-01-29 10:41:10 CET] Committer: Committing changes to git
-[2014-01-29 10:41:11 CET] Committer: Committing changes to git
-[2014-01-29 10:41:12 CET] Committer: Committing changes to git
-[2014-01-29 10:41:23 CET] Committer: Committing changes to git
-[2014-01-29 10:41:24 CET] Committer: Committing changes to git
-[2014-01-29 10:41:29 CET] Committer: Committing changes to git
-[2014-01-29 10:41:30 CET] Committer: Committing changes to git
-[2014-01-29 10:41:32 CET] Committer: Committing changes to git
-[2014-01-29 10:41:33 CET] Committer: Committing changes to git
-[2014-01-29 10:41:34 CET] Committer: Committing changes to git
-[2014-01-29 10:41:35 CET] Committer: Committing changes to git
-[2014-01-29 10:41:36 CET] Committer: Committing changes to git
-[2014-01-29 10:41:38 CET] Committer: Adding AlbumArt_..Small.jpg Folder.jpg
-ok
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-add Audio/Musik/Alanis Morissette/1995 - Jagged Little Pill/AlbumArt_{79951A99-BD71-4029-80F6-C3705D930871}_Small.jpg ok
-add Audio/Musik/Alanis Morissette/1995 - Jagged Little Pill/Folder.jpg [2014-01-29 10:41:38 CET] Committer: Committing changes to git
-[2014-01-29 10:41:39 CET] Committer: Committing changes to git
-[2014-01-29 10:41:41 CET] Committer: Committing changes to git
-[2014-01-29 10:41:42 CET] Committer: Committing changes to git
-[2014-01-29 10:41:44 CET] Committer: Committing changes to git
-[2014-01-29 10:41:45 CET] Committer: Committing changes to git
-[2014-01-29 10:41:46 CET] Committer: Committing changes to git
-[2014-01-29 10:41:47 CET] Committer: Committing changes to git
-[2014-01-29 10:41:48 CET] Committer: Committing changes to git
-[2014-01-29 10:41:49 CET] Committer: Committing changes to git
-[2014-01-29 10:41:51 CET] Committer: Committing changes to git
-[2014-01-29 10:41:52 CET] Committer: Committing changes to git
-[2014-01-29 10:41:54 CET] Committer: Committing changes to git
-[2014-01-29 10:41:55 CET] Committer: Committing changes to git
-[2014-01-29 10:41:56 CET] Committer: Committing changes to git
-[2014-01-29 10:41:58 CET] Committer: Committing changes to git
-[2014-01-29 10:41:59 CET] Committer: Committing changes to git
-[2014-01-29 10:42:00 CET] Committer: Committing changes to git
-[2014-01-29 10:42:01 CET] Committer: Committing changes to git
-[2014-01-29 10:42:02 CET] Committer: Committing changes to git
-[2014-01-29 10:42:04 CET] Committer: Committing changes to git
-[2014-01-29 10:42:05 CET] Committer: Committing changes to git
-[2014-01-29 10:42:06 CET] Committer: Committing changes to git
-[2014-01-29 10:42:07 CET] Committer: Committing changes to git
-[2014-01-29 10:42:08 CET] Committer: Committing changes to git
-[2014-01-29 10:42:10 CET] Committer: Committing changes to git
-[2014-01-29 10:42:11 CET] Committer: Committing changes to git
-[2014-01-29 10:42:12 CET] Committer: Committing changes to git
-[2014-01-29 10:42:13 CET] Committer: Committing changes to git
-[2014-01-29 10:42:14 CET] Committer: Committing changes to git
-[2014-01-29 10:42:15 CET] Committer: Committing changes to git
-[2014-01-29 10:42:17 CET] Committer: Committing changes to git
-[2014-01-29 10:42:18 CET] Committer: Committing changes to git
-[2014-01-29 10:42:19 CET] Committer: Committing changes to git
-[2014-01-29 10:42:20 CET] Committer: Committing changes to git
-[2014-01-29 10:42:21 CET] Committer: Committing changes to git
-[2014-01-29 10:42:23 CET] Committer: Committing changes to git
-[2014-01-29 10:42:24 CET] Committer: Committing changes to git
-[2014-01-29 10:42:25 CET] Committer: Committing changes to git
-[2014-01-29 10:42:26 CET] Committer: Committing changes to git
-[2014-01-29 10:42:27 CET] Committer: Committing changes to git
-[2014-01-29 10:42:28 CET] Committer: Committing changes to git
-To ssh://fabian@git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media/
-   5bd0d7e..1eda3be  git-annex -> synced/git-annex
-[2014-01-29 10:43:43 CET] Pusher: Syncing with Eifel.fritz.box__mnt_raid_Media 
-To ssh://fabian@git-annex-Eifel.fritz.box-fabian_.2Fmnt.2Fraid.2FMedia/mnt/raid/Media/
-   1eda3be..4c70ad2  git-annex -> synced/git-annex
-"""]]
-
-> The only way a repository can become "unwanted" is if you
-> tell git-annex to start deleting it (or perhaps set its group to unwanted
-> manually). This will cause git-annex to try to move all files away from
-> that repository. 
-> 
-> So, AFAICS, this must have been a case of operator error. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/Repository_in_manual_mode_does_not_hold_files/comment_1_86e8a4e546610e8e265806eb245d8aba._comment b/doc/bugs/Repository_in_manual_mode_does_not_hold_files/comment_1_86e8a4e546610e8e265806eb245d8aba._comment
deleted file mode 100644
index 855f3bf85..000000000
--- a/doc/bugs/Repository_in_manual_mode_does_not_hold_files/comment_1_86e8a4e546610e8e265806eb245d8aba._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.199"
- subject="comment 1"
- date="2014-01-29T17:49:18Z"
- content="""
-The preferred content setting for manual mode will try to clear out files that are in archive directories (once they reach an archive repository), but not other locations. I've re-tested it, and it still works that way. Perhaps your files are located inside archive directories; you don't say. If not, you will need to enable debug mode and show debug output.
-"""]]
diff --git a/doc/bugs/Repository_in_manual_mode_does_not_hold_files/comment_2_17d5775a38b67ba4f0e73f6b89cff2d0._comment b/doc/bugs/Repository_in_manual_mode_does_not_hold_files/comment_2_17d5775a38b67ba4f0e73f6b89cff2d0._comment
deleted file mode 100644
index f715db458..000000000
--- a/doc/bugs/Repository_in_manual_mode_does_not_hold_files/comment_2_17d5775a38b67ba4f0e73f6b89cff2d0._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~maestro-alubia"
- nickname="maestro-alubia"
- subject="comment 2"
- date="2014-01-30T20:50:32Z"
- content="""
-I did not configure any archive repositories or directories. But I just noticed my repository changed to \"unwanted\" in webapp. I am pretty sure I did not set this... I will set it back to manual now and see if this problem occurs again. But anyway, thanks for your help so far!
-"""]]
diff --git a/doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code.mdwn b/doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code.mdwn
deleted file mode 100644
index 2746ade5c..000000000
--- a/doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-What steps will reproduce the problem?
-
-I have an Annex with about 18k files in it.  If I clone it and then run `git annex get .`, it gets a few thousand files and then starts reporting:
-
-    get 2004-2012/Originals/110414_0362.jpg (from titan...) 
-    rsync: fork: Resource temporarily unavailable (35)
-    rsync error: error in IPC code (code 14) at pipe.c(63) [Receiver=3.0.9]
-
-I have to abort and re-run `git annex get .` several times to finally get all of the files.
-
-What is the expected output? What do you see instead?
-
-I didn't expect what I saw!  I think there's a resource not being released in the `get` code.
-
-What version of git-annex are you using? On what operating system?
-
-master branch, d430fb1.
-
-Please provide any additional information below.
-
-OS X 10.8.2.  The machine has tons of RAM and tons of process handles free.  It's really not doing anything else but this git-annex at the time of my tests.
-
-> [[done]], this is a bug introduced in 3.20121009, and I've reverted the
-> buggy change. --[[Joey]]
diff --git a/doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code/comment_1_66b21720cd1b2a4f66ef24252d3e6305._comment b/doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code/comment_1_66b21720cd1b2a4f66ef24252d3e6305._comment
deleted file mode 100644
index 4bdc7943b..000000000
--- a/doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code/comment_1_66b21720cd1b2a4f66ef24252d3e6305._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 1"
- date="2012-10-17T00:41:03Z"
- content="""
-The resource in question appears to be processes. Do you get a lot of zombies or something?
-"""]]
diff --git a/doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code/comment_2_18c9f55c5af1f4f690a7727df71ab561._comment b/doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code/comment_2_18c9f55c5af1f4f690a7727df71ab561._comment
deleted file mode 100644
index 29214814b..000000000
--- a/doc/bugs/Resource_leak_somewhere_in_the___39__get__39___code/comment_2_18c9f55c5af1f4f690a7727df71ab561._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 2"
- date="2012-10-17T01:07:00Z"
- content="""
-Urk. Seems I was making some recent changes lately to clean up zombies and I accidentually let them accumulate here. Fixed that.
-"""]]
diff --git a/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file.mdwn b/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file.mdwn
deleted file mode 100644
index 8239ae708..000000000
--- a/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-What steps will reproduce the problem?
-
-Add an encrypted rsync remote by it's 'Host' value in ~/.ssh/config.
-
-eg.:
-
-cat ~/.ssh/config | grep Host
-
-    Host serverNick
-
-git annex initremote rsyncRemote type=rsync rsyncurl=serverNick:/home/USER/Music encryption=USER@gmail.com
-
-git annex copy some\ artist --to serverNick
-
-
-What is the expected output? What do you see instead?
-
-I'd expect it to remember the key password like a normal ssh remote.  Instead I get asked for the key password 3 times for each file in the folder.
-
-What version of git-annex are you using? On what operating system?
-
-3.20130216.  Arch x64 (up to date as of 2013-03-07)
-
-Please provide any additional information below.
-
-
-[[!meta title="rsync special remote does not use ssh connection caching"]]
-
-> [[done]]; ssh connection caching is now done for these remotes.
-> --[[Joey]]
diff --git a/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file/comment_1_fd95e0bb61e80a72b4ac1304ef6c2e77._comment b/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file/comment_1_fd95e0bb61e80a72b4ac1304ef6c2e77._comment
deleted file mode 100644
index 5f55f356b..000000000
--- a/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file/comment_1_fd95e0bb61e80a72b4ac1304ef6c2e77._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-08T18:59:27Z"
- content="""
-git-annex does not use ssh connection caching for rsync special remotes, and so if you've configured ssh such that it needs to prompt for a password when making a connection, you'll be prompted twice for each file when using `git annex copy`: Once when it checks if the file is present, once when it rsyncs it. (One of those can be avoided by passing --fast)
-
-I don't see where a third password prompt can come from, other than gpg. But that would only prompt once per git-annex command, since git-annex caches the remote's encryption key.
-
-Of course, you can use a ssh-agent to avoid repeated ssh password prompts.
-
-----
-
-There's certainly a valid wishlist todo item that the rsync special remote should support ssh connection caching. It could be implemented using rsync -e. Although it would need to parse all valid rsync urls to determine which use ssh and which not, and what the user and hostname are.
-"""]]
diff --git a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn b/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn
deleted file mode 100644
index 2c0037c90..000000000
--- a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn
+++ /dev/null
@@ -1,10 +0,0 @@
-While using HMAC instead of "plain" hash functions is inherently more secure, it's still a bad idea to re-use keys for different purposes.
-
-Also, ttbomk, HMAC needs two keys, not one. Are you re-using the same key twice?
-
-Compability for old buckets and support for different ones can be maintained by introducing a new option and simply copying over the encryption key's identifier into this new option should it be missing.
-
-> Bug was filed prematurely, but was a good bit of paranoia, and gpg and
-> hmac are given different secret keys [[done]] --[[Joey]] 
-
->> Thanks :) -- RIchiH
diff --git a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_1_dc5ae7af499203cfd903e866595b8fea._comment b/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_1_dc5ae7af499203cfd903e866595b8fea._comment
deleted file mode 100644
index 320fb5ef0..000000000
--- a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_1_dc5ae7af499203cfd903e866595b8fea._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-03-30T14:32:34Z"
- content="""
-S3 doesn't support encryption at all, yet.
-
-It certainly makes sense to use a different portion of the encrypted secret key for HMAC than is uses as the gpg symmetric encryption key.
-
-The two keys used in HMAC would be the secret key and the key/value key for the content being stored.
-
-There is a difficult problem with encrypting filenames in S3 buckets, and that is determining when some data in the bucket is unused for dropunused. I've considered two choices:
-
-1. gpg encrypt the filenames. This would allow dropunused to recover the original filenames, and is probably more robust encryption. But it would double the number of times gpg is run when moving content in/out, and to check for unused content, gpg would have to be run once for every item in the bucket, which just feels way excessive, even though it would not be prompting for a passphrase. Still, haven't ruled this out.
-
-2. HMAC or other hash. To determine what data was unused the same hash and secret key would have to be used to hash all filenames currently used, and then that set of hashes could be interested with the set in the bucket. But then git-annex could only say \"here are some opaque hashes of content that appears unused by anything in your current git repository, but there's no way, short of downloading it and examining it to tell what it is\". (This could be improved by keeping a local mapping between filenames and S3 keys, but maintaining and committing that would bring pain of its own.)
-"""]]
diff --git a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_2_c62daf5b3bfcd2f684262c96ef6628c1._comment b/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_2_c62daf5b3bfcd2f684262c96ef6628c1._comment
deleted file mode 100644
index dec06c89f..000000000
--- a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_2_c62daf5b3bfcd2f684262c96ef6628c1._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2011-03-30T17:01:40Z"
- content="""
-After mulling this over, I think actually encrypting the filenames is preferable.
-
-Did you consider encrypting the symmetric key with an asymmetric one? That's what TrueCrypt etc are using to allow different people access to a shared volume. This has the added benefit that you could, potentially, add new keys for data that new people should have access to while making access to old data impossible. Or keys per subdirectory, or, or, or.
-
-As an aside, could the same mechanism be extended to transparently encrypt data for a remote annex repo? A friend of mine is interested to host his data with me, but he wants to encrypt his data for obvious reasons.
-"""]]
diff --git a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_3_e1f39c4af5bdb0daabf000da80858cd9._comment b/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_3_e1f39c4af5bdb0daabf000da80858cd9._comment
deleted file mode 100644
index c5bb26f59..000000000
--- a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_3_e1f39c4af5bdb0daabf000da80858cd9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 3"
- date="2011-03-30T18:15:18Z"
- content="""
-Yes, encrypting the symmetric key with users' regular gpg keys is the plan.
-
-I don't think that encryption of content in a git annex remote makes much sense; the filenames obviously cannot be encrypted there. It's more likely that the same encryption would get used for a bup remote, or with the [[special_remotes/directory]] remote I threw in today.
-"""]]
diff --git a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_4_bb6b814ab961818d514f6553455d2bf3._comment b/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_4_bb6b814ab961818d514f6553455d2bf3._comment
deleted file mode 100644
index 09b7a8b1a..000000000
--- a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_4_bb6b814ab961818d514f6553455d2bf3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 4"
- date="2011-03-30T18:20:56Z"
- content="""
-Picking up the automagic encryption idea for annex remotes, this would allow you to host a branchable-esque git-annex hosting service. (Nexenta with ZFS is a cheap and reliable option until btrfs becomes stable in a year or five).
-"""]]
diff --git a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_5_5bb128f6d2ca4b5e4d881fae297fa1f8._comment b/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_5_5bb128f6d2ca4b5e4d881fae297fa1f8._comment
deleted file mode 100644
index 49d43ffc6..000000000
--- a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_5_5bb128f6d2ca4b5e4d881fae297fa1f8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 5"
- date="2011-03-30T18:59:19Z"
- content="""
-This is brain-storming only so the idea might be crap, but a branch could keep encrypted filenames while master keeps the real deal. This might fit into the whole scheme just nicely or break future stuff in a dozen places, I am not really sure yet. But at least I can't forget the idea, now.
-"""]]
diff --git a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_6_63fb74da342751fc35e1850409c506f6._comment b/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_6_63fb74da342751fc35e1850409c506f6._comment
deleted file mode 100644
index d994ca77f..000000000
--- a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing/comment_6_63fb74da342751fc35e1850409c506f6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 6"
- date="2011-03-30T19:02:20Z"
- content="""
-OTOH, if encryption makes a bup backend more likely disregard the idea above ;)
-"""]]
diff --git a/doc/bugs/SSH:_command-line:_line_0:_Bad_configuration_option:_ControlPersist___40__SSH_too_old_on_OS_X_10.6.8__63____41__.mdwn b/doc/bugs/SSH:_command-line:_line_0:_Bad_configuration_option:_ControlPersist___40__SSH_too_old_on_OS_X_10.6.8__63____41__.mdwn
deleted file mode 100644
index a3d27e404..000000000
--- a/doc/bugs/SSH:_command-line:_line_0:_Bad_configuration_option:_ControlPersist___40__SSH_too_old_on_OS_X_10.6.8__63____41__.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-What steps will reproduce the problem?
-
-Try to get any file from a remote ssh repository on OS X 10.6.8
-
-What is the expected output? What do you see instead?
-
-Instead of retrieving the files, I get:
-
-    % git annex get . 
-    get <filename> command-line: line 0: Bad configuration option: ControlPersist
-    command-line: line 0: Bad configuration option: ControlPersist
-    (not available) 
-      Try making some of these repositories available:
-      	2efd46d2-0e32-11e2-95fe-f72f09c6615e -- office
-
-What version of git-annex are you using? On what operating system?
-     % git annex version
-    git-annex version: 3.20120925
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3
-    upgrade supported from repository versions: 0 1 2
-
-I seems that this option is passed to SSH, but SSH is too old: OpenSSH_5.2p1, OpenSSL 0.9.8r 8 Feb 
-
-> Future builds of the standalone binary will default annex.sshcaching to
-> false. [[done]] --[[Joey]]
diff --git a/doc/bugs/SSH:_command-line:_line_0:_Bad_configuration_option:_ControlPersist___40__SSH_too_old_on_OS_X_10.6.8__63____41__/comment_1_0c57a2196d35eb1ecfb0c51273bba05c._comment b/doc/bugs/SSH:_command-line:_line_0:_Bad_configuration_option:_ControlPersist___40__SSH_too_old_on_OS_X_10.6.8__63____41__/comment_1_0c57a2196d35eb1ecfb0c51273bba05c._comment
deleted file mode 100644
index ec510ae30..000000000
--- a/doc/bugs/SSH:_command-line:_line_0:_Bad_configuration_option:_ControlPersist___40__SSH_too_old_on_OS_X_10.6.8__63____41__/comment_1_0c57a2196d35eb1ecfb0c51273bba05c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.8"
- subject="comment 1"
- date="2012-10-15T18:16:58Z"
- content="""
-Here's a workaround, which you can run in the local repository:
-
-git config annex.sshcaching false
-"""]]
diff --git a/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled.mdwn b/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled.mdwn
deleted file mode 100644
index 39b860e7c..000000000
--- a/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled.mdwn
+++ /dev/null
@@ -1,65 +0,0 @@
-git-annex version: 4.20130323
-
-Running the webapp with SELinux enabled:
-
-    [0 zerodogg@browncoats annexed]$ git annex webapp --debug
-    Launching web browser on file:///home/zerodogg/Documents/annexed/.git/annex/webapp.html
-    /home/zerodogg/bin/git-annex: line 25:  5801 Segmentation fault      (core dumped) "$base/runshell" git-annex "$@"
-
-After disabling SELinux it works just fine. This is on a freshly installed (default settings) Fedora 18 on x86-64.
-
-Running the assistant also works, but segfaults when attempting to open the webapp:
-
-    [0 zerodogg@browncoats annexed]$ git annex assistant &
-    [1] 6241
-    [0 zerodogg@browncoats annexed]$ 
-    [0 zerodogg@browncoats annexed]$ git annex webapp --debug
-    Launching web browser on file:///home/zerodogg/Documents/annexed/.git/annex/webapp.html
-    /home/zerodogg/bin/git-annex: line 25:  6322 Segmentation fault      (core dumped) "$base/runshell" git-annex "$@"
-    [139 zerodogg@browncoats annexed]$ Created new window in existing browser session.
-
-Here's what `dmesg` says:
-
-    [   71.488843] SELinux: initialized (dev proc, type proc), uses genfs_contexts
-    [  115.443932] git-annex[3985]: segfault at e6e62984 ip 0000000009b8085a sp 00000000f4bfd028 error 4 in git-annex[8048000+1c75000]
-    [  125.148819] SELinux: initialized (dev proc, type proc), uses genfs_contexts
-    [  125.230155] git-annex[4043]: segfault at e6eda984 ip 0000000009b8085a sp 00000000f63fd028 error 4 in git-annex[8048000+1c75000]
-    [  406.855659] SELinux: initialized (dev proc, type proc), uses genfs_contexts
-    [  407.033966] git-annex[5806]: segfault at e6faa984 ip 0000000009b8085a sp 00000000f6dfd028 error 4 in git-annex[8048000+1c75000]
-    [  462.368045] git-annex[6279]: segfault at e6f76984 ip 0000000009b8085a sp 00000000f49fd028 error 4 in git-annex[8048000+1c75000]
-    [  465.714636] SELinux: initialized (dev proc, type proc), uses genfs_contexts
-    [  465.930434] git-annex[6329]: segfault at e6e7a984 ip 0000000009b8085a sp 00000000f63fd028 error 4 in git-annex[8048000+1c75000]
-    [  560.570480] git-annex[7050]: segfault at e7022984 ip 0000000009b8085a sp 00000000f54fd028 error 4 in git-annex[8048000+1c75000]
-    [  565.510664] SELinux: initialized (dev proc, type proc), uses genfs_contexts
-    [  565.688681] git-annex[7108]: segfault at e7196984 ip 0000000009b8085a sp 00000000f54fd028 error 4 in git-annex[8048000+1c75000]
-
-Running the whole thing with --debug doesn't appear to provide anything useful:
-
-    [0 zerodogg@browncoats annexed]$ git annex assistant --debug &
-    [1] 7018
-    [0 zerodogg@browncoats annexed]$ [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","show-ref","git-annex"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","show-ref","--hash","refs/heads/git-annex"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","log","refs/heads/git-annex..f2260840bd9563f3d9face53dddd6807813860cd","--oneline","-n1"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","log","refs/heads/git-annex..798526ef1315811296b1ac95d4cf97c72141ad29","--oneline","-n1"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","log","refs/heads/git-annex..0d827b1ef545a88e94ee8cc973e54a1b74d216f4","--oneline","-n1"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","log","refs/heads/git-annex..1d8f91411b827c4d59735dbc572e7f278e870e43","--oneline","-n1"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","log","refs/heads/git-annex..cc442416b325866139db6dbe374bddacda6fef91","--oneline","-n1"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","log","refs/heads/git-annex..3c2f44ffd82df1a0ae8858bdf2610e933b105a09","--oneline","-n1"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","log","refs/heads/git-annex..fb8819ca92d9a2ed39e6d329160b5f8da60df83f","--oneline","-n1"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","log","refs/heads/git-annex..68d0f936ee044b0ca34cf4029bcd6274fed88499","--oneline","-n1"]
-    [2013-03-24 16:27:02 CET] read: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","log","refs/heads/git-annex..3ba3dfef6340196126f4fc630b5048188230d1ff","--oneline","-n1"]
-    [2013-03-24 16:27:02 CET] chat: git ["--git-dir=/home/zerodogg/Documents/annexed/.git","--work-tree=/home/zerodogg/Documents/annexed","cat-file","--batch"]
-    
-    [1]  + done       GITWRAP annex assistant --debug
-    [0 zerodogg@browncoats annexed]$ git annex webapp --debug &
-    [1] 7082
-    [0 zerodogg@browncoats annexed]$ Launching web browser on file:///home/zerodogg/Documents/annexed/.git/annex/webapp.html
-    /home/zerodogg/bin/git-annex: line 25:  7088 Segmentation fault      (core dumped) "$base/runshell" git-annex "$@"
-    
-    [1]  + exit 139   GITWRAP annex webapp --debug
-    [0 zerodogg@browncoats annexed]$ Created new window in existing browser session.
-
-> On IRC it developed that it segfaulted at other times, and gdb complained
-> of a library mismatch. Seems something changed in Fedora libc, and 
-> the 32 bit binary is not working on 64 bit. I've brought back the 64 bit
-> standalone builds, which work. [[done]] --[[Joey]]
diff --git a/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_1_f708d87aa65cd38c20087859d3ab2dc7._comment b/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_1_f708d87aa65cd38c20087859d3ab2dc7._comment
deleted file mode 100644
index 458e31327..000000000
--- a/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_1_f708d87aa65cd38c20087859d3ab2dc7._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-27T16:18:14Z"
- content="""
-What is this GITWRAP? That is not part of git-annex, I suspect it's a locally set up wrapper around git of some sort.
-
---debug causes the assistant to log to `.git/annex/daemon.log`, there may be useful information in there. In particular it's not at all clear whether the web browser is segfaulting, or whether the crash occurs before the web browser is started.
-
-Does your SE linux policy allow git-annex to run your web browser? What happens if you start the assistant and then manually open file:///home/zerodogg/Documents/annexed/.git/annex/webapp.html in your web browser?
-"""]]
diff --git a/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_2_fb7188db031147992f3c906783ebbee0._comment b/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_2_fb7188db031147992f3c906783ebbee0._comment
deleted file mode 100644
index 6b7e7ccc8..000000000
--- a/doc/bugs/Segfaults_on_Fedora_18_with_SELinux_enabled/comment_2_fb7188db031147992f3c906783ebbee0._comment
+++ /dev/null
@@ -1,59 +0,0 @@
-[[!comment format=mdwn
- username="EskildHustvedt"
- ip="84.48.83.221"
- subject="comment 2"
- date="2013-03-31T18:13:53Z"
- content="""
-GITWRAP is just my shell function that sets GIT_PAGER to different values depending on the command.
-
-SELinux lets git-annex run the browser. Browser opens on the file, redirects to the git-annex localhost URL (which fails to connect at that point, since git-annex has crashed). So the crash is 1) in git-annex, and 2) after it has started the browser. The segfault also occurs if I directly start the browser on `/home/zerodogg/Documents/annexed/.git/annex/webapp.html`, so it would appear that the crash occurs when something tries to connect to the http server.
-
-There's nothing from --debug in `.git/annex/daemon.log`:
-
-    [2013-03-31 19:58:09 CEST] main: starting assistant version 4.20130323
-    [2013-03-31 19:58:09 CEST] read: host [\"-t\",\"SRV\",\"--\",\"_xmpp-client._tcp.dukgo.com\"]
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"symbolic-ref\",\"HEAD\"]
-    [2013-03-31 19:58:09 CEST] TransferScanner: Syncing with serenity, river, hufsa, browncoats 
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"show-ref\",\"refs/heads/master\"]
-    [2013-03-31 19:58:09 CEST] NetWatcher: Using running DBUS service org.freedesktop.NetworkManager to monitor network connection events.
-    [2013-03-31 19:58:09 CEST] MountWatcher: Using running DBUS service org.gtk.Private.UDisks2VolumeMonitor to monitor mount events.
-    [2013-03-31 19:58:09 CEST] Merger: merging refs/remotes/browncoats/synced/master into refs/heads/master
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"]
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"symbolic-ref\",\"HEAD\"]
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"show-ref\",\"refs/heads/master\"]
-
-    [2013-03-31 19:58:09 CEST] call: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"merge\",\"--no-edit\",\"refs/remotes/browncoats/synced/master\"]
-    Already up-to-date.
-    [2013-03-31 19:58:09 CEST] call: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"fetch\",\"serenity\"]
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"show-ref\",\"git-annex\"]
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..d5e18a083c7d0caeddc3da78f18b53fac0d56a7f\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..f2260840bd9563f3d9face53dddd6807813860cd\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:09 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..798526ef1315811296b1ac95d4cf97c72141ad29\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..21a6361e598efd80e851276c17249e5c3284713f\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..3c2f44ffd82df1a0ae8858bdf2610e933b105a09\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..3b4fcc605fd4787084afe47e82eac6821cb2cd37\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"]
-    (scanning...) [2013-03-31 19:58:10 CEST] Watcher: Performing startup scan
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"show-ref\",\"git-annex\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..d5e18a083c7d0caeddc3da78f18b53fac0d56a7f\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..f2260840bd9563f3d9face53dddd6807813860cd\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..798526ef1315811296b1ac95d4cf97c72141ad29\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..21a6361e598efd80e851276c17249e5c3284713f\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..3c2f44ffd82df1a0ae8858bdf2610e933b105a09\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..3b4fcc605fd4787084afe47e82eac6821cb2cd37\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"symbolic-ref\",\"HEAD\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"show-ref\",\"refs/heads/master\"]
-    [2013-03-31 19:58:10 CEST] Merger: merging refs/remotes/serenity/synced/master into refs/heads/master
-
-    [2013-03-31 19:58:10 CEST] call: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"merge\",\"--no-edit\",\"refs/remotes/serenity/synced/master\"]
-    Already up-to-date.
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"show-ref\",\"git-annex\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..d5e18a083c7d0caeddc3da78f18b53fac0d56a7f\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..f2260840bd9563f3d9face53dddd6807813860cd\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..798526ef1315811296b1ac95d4cf97c72141ad29\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..21a6361e598efd80e851276c17249e5c3284713f\",\"--oneline\",\"-n1\"]
-    [2013-03-31 19:58:10 CEST] read: git [\"--git-dir=/home/zerodogg/Documents/annexed/.git\",\"--work-tree=/home/zerodogg/Documents/annexed\",\"log\",\"refs/heads/git-annex..3c2f44ffd82df1a0ae8858bdf2610e933b105a09\",\"--oneline\",\"-n1\"]
-"""]]
diff --git a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.mdwn b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.mdwn
deleted file mode 100644
index 7eaf2a71b..000000000
--- a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-> git annex status
-supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-supported remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-repository mode: indirect
-trusted repositories: 0
-semitrusted repositories: 8
-	00000000-0000-0000-0000-000000000001 -- web
- 	44AF00F1-511F-4902-8235-DFF741B09400 -- here
- 	44af00f1-511f-4902-8235-dff741b09400 -- chrissy
- 	53499200-CA18-4B51-B6B3-651C18208349 -- stevedave
- 	56C56658-0995-4613-8A1B-B2FA534A834C -- olaf
- 	8FE9B19F-4FC8-4CFA-AD89-4B70EB432EDC -- passport
- 	AFC75641-B34A-4644-B566-C8D3127823F7 -- glacier
- 	B3238A12-D81B-40EA-BE89-3BDB318AE2B7 -- brodie
-untrusted repositories: 0
-transfers in progress: none
-available local disk space: 78.8 gigabytes (+1 gigabyte reserved)
-local annex keys: 3915
-local annex size: 81.37 gigabytes
-known annex keys: 5728
-known annex size: 641.36 gigabytes
-bloom filter size: 16 mebibytes (0.8% full)
-backend usage:
-	SHA256E: 8716
-	URL: 927
-
-> git annex version
-git-annex version: 4.20130909
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-
-> git-annex intentionally treats UUIDs as opaque strings,
-> so it is not going to go to any bother to consider 
-> different byte sequences to be the same UUID, sorry.
-> (The standard may be arbitrarily complicated, but I have arbitrarily
-> decided to ignore it.)
-> 
-> Since git-annex only ever generates each UUID once, and copies
-> the exact sequence of bytes as necessary, the only way the situation
-> you show above can happen is if you have manually gone in and entered
-> UUIDs in two different cases.
-> 
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment
deleted file mode 100644
index b1417816f..000000000
--- a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2013-09-12T09:44:54Z"
- content="""
-There does not seem to be an actual bug description in here. Can you provide more info?
-
-To answer the actual question: RFC 4122 clearly answers no:
-
-      Each field is treated as an integer and has its value printed as a
-      zero-filled hexadecimal digit string with the most significant
-      digit first.  The hexadecimal values \"a\" through \"f\" are output as
-      lower case characters and are case insensitive on input.
-
-Yes, that means that git-annex prints them wrongly as that's upper case.
-"""]]
diff --git a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_2_8f5fa659c2ab91b1757bac31cd3b15eb._comment b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_2_8f5fa659c2ab91b1757bac31cd3b15eb._comment
deleted file mode 100644
index f07a7bf9d..000000000
--- a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_2_8f5fa659c2ab91b1757bac31cd3b15eb._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2013-09-12T09:49:56Z"
- content="""
-What OS are you using?
-
-versions 4.20130827 and 4.20130911 on Debian Sid print UUIDs which are lower case, as should be expected.
-"""]]
diff --git a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_3_ccf9623d60c58d036d8bf24757e50de3._comment b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_3_ccf9623d60c58d036d8bf24757e50de3._comment
deleted file mode 100644
index 76f6c0742..000000000
--- a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_3_ccf9623d60c58d036d8bf24757e50de3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q"
- nickname="Andrew"
- subject="comment 3"
- date="2013-09-12T16:24:30Z"
- content="""
-This is on OSX 10.8.4
-
-If you look at the remote \"chrissy\" and \"here\" they are the same uuid, but with different case.
-"""]]
diff --git a/doc/bugs/Should_ignore_.thumbnails__47___on_android.mdwn b/doc/bugs/Should_ignore_.thumbnails__47___on_android.mdwn
deleted file mode 100644
index 30dc5caee..000000000
--- a/doc/bugs/Should_ignore_.thumbnails__47___on_android.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-
-When creating a Camera repository on android, the .thumbnails/ directory (containing useless crushed JPGs and even more useless oodles of thumbnail metadata databases) is annexed. This leads to confusion (assistant tries to annex database and thumbnails in modification) and waste (uploading/annexing unusable/unneeded metadata).
-
-### What steps will reproduce the problem?
-
-Install git-annex on Android and choose the defaults for a camera repository.
-
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130601, Android 4.2.2
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> I've [[done]] this, however the .gitignore file it writes will
-> not actually be used by the assistant until it gets support
-> for querying gitignore settings from git. There is already a
-> bug tracking that, and it's in process. --[[Joey]] 
diff --git a/doc/bugs/Specifying_a_filename_starting_with___34__-c__34___instead_applies_it_to_all_files.mdwn b/doc/bugs/Specifying_a_filename_starting_with___34__-c__34___instead_applies_it_to_all_files.mdwn
deleted file mode 100644
index 52db9e0ae..000000000
--- a/doc/bugs/Specifying_a_filename_starting_with___34__-c__34___instead_applies_it_to_all_files.mdwn
+++ /dev/null
@@ -1,75 +0,0 @@
-### Please describe the problem.
-Trying to apply certain commands - such as 'drop' - to a filename which starts with "-c" instead applies it to all files.  In the instance where I found this, I was using "drop --force" and it caused it to indiscriminately get rid of everything in the directory instead of a single file.
-
-### What steps will reproduce the problem?
-1. Make a repository.
-2. Create several files and add them.
-3. Create a file whose name begins with "-c" and add it as well.
-4. Run "git annex drop <fname>" where 'fname' is the file from that last step. 
-
-### What version of git-annex are you using? On what operating system?
-4.20130516-gedc4ccd on Arch Linux
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[user@host ~]$ mkdir annex_test
-[user@host ~]$ cd annex_test/
-[user@host annex_test]$ ls
-[user@host annex_test]$ git init
-Initialized empty Git repository in /home/user/annex_test/.git/
-[user@host annex_test]$ git annex init "test"
-init test ok
-(Recording state in git...)
-[user@host annex_test]$ 
-[user@host annex_test]$ echo foo > foo
-[user@host annex_test]$ echo bar > bar
-[user@host annex_test]$ echo baz > baz
-[user@host annex_test]$ echo test > "-c-test"
-[user@host annex_test]$ git annex add *
-add bar (checksum...) ok
-add baz (checksum...) ok
-add foo (checksum...) ok
-(Recording state in git...)
-[user@host annex_test]$ git annex add -c-test 
-add -c-test (checksum...) ok
-(Recording state in git...)
-[user@host annex_test]$ git annex drop -c-test 
-drop -c-test (unsafe) 
-  Could only verify the existence of 0 out of 1 necessary copies
-
-  Rather than dropping this file, try using: git annex move
-
-  (Use --force to override this check, or adjust annex.numcopies.)
-failed
-drop bar (unsafe) 
-  Could only verify the existence of 0 out of 1 necessary copies
-
-  Rather than dropping this file, try using: git annex move
-
-  (Use --force to override this check, or adjust annex.numcopies.)
-failed
-drop baz (unsafe) 
-  Could only verify the existence of 0 out of 1 necessary copies
-
-  Rather than dropping this file, try using: git annex move
-
-  (Use --force to override this check, or adjust annex.numcopies.)
-failed
-drop foo (unsafe) 
-  Could only verify the existence of 0 out of 1 necessary copies
-
-  Rather than dropping this file, try using: git annex move
-
-  (Use --force to override this check, or adjust annex.numcopies.)
-failed
-git-annex: drop: 4 failed
-
-
-# End of transcript or log.
-"""]]
-
-> Closing, as this is basically user error. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Specifying_a_filename_starting_with___34__-c__34___instead_applies_it_to_all_files/comment_1_2fe6d735bc075275a6b8890fac48ee58._comment b/doc/bugs/Specifying_a_filename_starting_with___34__-c__34___instead_applies_it_to_all_files/comment_1_2fe6d735bc075275a6b8890fac48ee58._comment
deleted file mode 100644
index 39a469933..000000000
--- a/doc/bugs/Specifying_a_filename_starting_with___34__-c__34___instead_applies_it_to_all_files/comment_1_2fe6d735bc075275a6b8890fac48ee58._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-06-10T20:30:27Z"
- content="""
-This is the same as trying to rm a file named `-rf`
-
-In git-annex, as in git, -c sets a git configuration option. The text after the -c is supposed to be the option name and value. So -c-test is a valid command-line option.
-
-This leaves `git annex drop`, with no files specified to drop. As documented, git-annex commands default to acting on all relevant files in the current directory and subdirectories.
-
-Luckily, drop does check that numcopies other remotes have the file, so unless you also have a file named --force, you're not going to lose data doing this.
-
-I don't see any change I could make to prevent this kind of mistake. I checked and git also treats \"-c -test\" as valid input, despite \"-test\" not being a likely git config key (and no value being specified). I could make git-annex's option parser require the space between option and value (which git does require), which would perhaps reduce the set of files whose names are valid options.
-
-Fundamentally, this is a type of mistake that the design of unix command options allows to happen, if people use filenames starting with dashes -- so people generally don't do that. It's worth noting that git-annex is *very* careful itself, whenever passing a filename to a unix command, to check if it starts with a dash, and use \"./-file\" instead!
-"""]]
diff --git a/doc/bugs/Stale_lock_files_on_Android.mdwn b/doc/bugs/Stale_lock_files_on_Android.mdwn
deleted file mode 100644
index b3451a153..000000000
--- a/doc/bugs/Stale_lock_files_on_Android.mdwn
+++ /dev/null
@@ -1,44 +0,0 @@
-### Please describe the problem.
-
-Both my Android devices where not processing git-annex updates due to stale lock files. While the lock files are different, I've reported them both together as they are related. 
-
-### What steps will reproduce the problem?
-
-Unknown, perhaps the assistant crashed, or the battery ran flat on them.
-
-To resolve the issue I had to manually remove the lock files.
-
-### What version of git-annex are you using? On what operating system?
-
-On my Android phone, daily build 4.20130614-g221aea4
-On my Android tablet, daily build 4.20130621-g36258de
-
-### Please provide any additional information below.
-
-It seems to me that it'd be useful to have the assistant check to see if the lock files are still valid and remove them if they're stale.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-My phone:
-
-From ssh://git-annex-flick-andrewannex_phonecamera/~/phone-camera
-   987dc25..682cdd1  git-annex  -> flick_phonecamera/git-annex
-fatal: Unable to create '/storage/emulated/legacy/DCIM/.git/refs/remotes/flick_phonecamera/synced/git-annex.lock': File exists.
-
-My tablet:
-
-Committer: Adding Coleman-C..eedom.pdf
-Committer: Committing changes to git
-fatal: Unable to create '/mnt/sdcard/reference/.git/index.lock': File exists.
-
-# End of transcript or log.
-"""]]
-
-> The '/mnt/sdcard/reference/.git/index.lock' lock file will now be
-> automatically dealt with. Have not done anything about the refs/remotes
-> lock files yet. --[[Joey]]
-> 
-> Now the assistant deals with all stale git lock files on startup. 
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Switching_between_direct_and_indirect_stomps_on___39__regular__39___git_files.mdwn b/doc/bugs/Switching_between_direct_and_indirect_stomps_on___39__regular__39___git_files.mdwn
deleted file mode 100644
index db1889f81..000000000
--- a/doc/bugs/Switching_between_direct_and_indirect_stomps_on___39__regular__39___git_files.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-# What steps will reproduce the problem?
-
-    git add file
-    git annex add file2
-    git annex direct
-    git annex indirect
-
-file and file2 are now both in the annex.
-
-# What is the expected output? What do you see instead?
-
-file should remain in the main repo, file2 should remain in the annex
-
-# What version of git-annex are you using? On what operating system?
-
-    git-annex version: 4.20130228
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-    git version 1.8.1.5
-
-Mac OSX 10.8.2 Build 12C60
-
-> Closing this bug, as I cannot reproduce it and the bug reporter is
-> not responding. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Switching_between_direct_and_indirect_stomps_on___39__regular__39___git_files/comment_1_0d2cb3b8509cd0eba50aafa14afefc02._comment b/doc/bugs/Switching_between_direct_and_indirect_stomps_on___39__regular__39___git_files/comment_1_0d2cb3b8509cd0eba50aafa14afefc02._comment
deleted file mode 100644
index d4afd95c4..000000000
--- a/doc/bugs/Switching_between_direct_and_indirect_stomps_on___39__regular__39___git_files/comment_1_0d2cb3b8509cd0eba50aafa14afefc02._comment
+++ /dev/null
@@ -1,63 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-08T19:44:29Z"
- content="""
-I cannot reproduce this using the steps given. Transcript:
-
-<pre>
-joey@gnu:~/tmp>mkdir test
-joey@gnu:~/tmp>cd test
-joey@gnu:~/tmp/test>git init
-Initialized empty Git repository in /home/joey/tmp/test/.git/
-joey@gnu:~/tmp/test>git annex init
-init  ok
-(Recording state in git...)
-joey@gnu:~/tmp/test>echo file > file
-joey@gnu:~/tmp/test>echo file2 > file2
-joey@gnu:~/tmp/test>git add file
-joey@gnu:~/tmp/test>git annex add file2
-add file2 (checksum...) ok
-(Recording state in git...)
-joey@gnu:~/tmp/test>git annex direct
-commit  
-[master (root-commit) 8d49cac] commit before switching to direct mode
- 2 files changed, 2 insertions(+)
- create mode 100644 file
- create mode 120000 file2
-ok
-direct file2 ok
-direct  ok
-joey@gnu:~/tmp/test>git annex indirect
-commit  (Recording state in git...)
-
-ok
-# On branch master
-# Changes not staged for commit:
-#   (use \"git add <file>...\" to update what will be committed)
-#   (use \"git checkout -- <file>...\" to discard changes in working directory)
-#
-#	typechange: file2
-#
-no changes added to commit (use \"git add\" and/or \"git commit -a\")
-ok
-indirect file2 ok
-indirect  ok
-ok
-joey@gnu:~/tmp/test>ls
-file  file2@
-joey@gnu:~/tmp/test>file file
-file: ASCII text
-joey@gnu:~/tmp/test>file file2
-file2: symbolic link to `.git/annex/objects/ZV/w4/SHA256E-s6--67ee5478eaadb034ba59944eb977797b49ca6aa8d3574587f36ebcbeeb65f70e/SHA256E-s6--67ee5478eaadb034ba59944eb977797b49ca6aa8d3574587f36ebcbeeb65f70e'
-joey@gnu:~/tmp/test>git log --oneline file 
-8d49cac commit before switching to direct mode
-</pre>
-
-I even tried to reproduce the bug on a mac in case it was somehow only happening on that OS, but still, no go. `file` remains checked into git as a normal file, it is not annexed.
-
-`git annex indirect` does not touch files unless they have a symlink committed to git. The code is pretty clear about that.
-
-Please post a complete transcript that goes all the way from repository creation to the bug happening.
-"""]]
diff --git a/doc/bugs/Switching_from_indirect_mode_to_direct_mode_breaks_duplicates.mdwn b/doc/bugs/Switching_from_indirect_mode_to_direct_mode_breaks_duplicates.mdwn
deleted file mode 100644
index 55d2b13b9..000000000
--- a/doc/bugs/Switching_from_indirect_mode_to_direct_mode_breaks_duplicates.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-#What steps will reproduce the problem?
-
-1. Create a new repository in indirect mode.
-
-2. Add the same file twice under a different name. Now you have two symlinks pointing to the same file under .git/annex/objects/
-
-3. Switch to direct mode. The first symlink gets replaced by the actual file. The second stays unchanged, pointing to nowhere. But git annex whereis still reports it has a copy.
-
-4. Delete the first file. Git annex whereis still thinks it has a copy of file 2, which is not true -> data loss.
-
-#What is the expected output? What do you see instead?
-
-When switching to direct mode, both symlinks should be replaced by a copy (or at least a hardlink) of the actual file.
-
-> The typo that caused this bug is fixed. --[[Joey]] 
-
-#What version of git-annex are you using? On what operating system?
-
-3.20130107 on Arch Linux x64
-
-#Please provide any additional information below.
-
-The deduplication performed by git-annex is very dangerous in itself
-because files with identical content become replaced by references to the
-same file without the user necessarily being aware. Think of the user
-making a copy of a file, than modifying it. He would expect to end up with
-two files, the unchanged original and the modified copy. But what he really
-gets is two symlinks pointing to the same modified file.
-
-> I agree, it now copies rather than hard linking.  [[done]] --[[Joey]] 
diff --git a/doc/bugs/Switching_repositories_in_webapp_on_a_remote_server_is_not_honoring_--listen_parameter.mdwn b/doc/bugs/Switching_repositories_in_webapp_on_a_remote_server_is_not_honoring_--listen_parameter.mdwn
deleted file mode 100644
index faa7a36de..000000000
--- a/doc/bugs/Switching_repositories_in_webapp_on_a_remote_server_is_not_honoring_--listen_parameter.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-### Please describe the problem.
-I am running my "origin" repositories on a headless server. Managing these with webapp --listen=<server IP>:<port> is a very conveniant way. Now I am creating more repositories for different content on the same server. When I try to switch the webapp between these repositories webapp gives me a link with 127.0.0.1:<random port> in the URL.
-
-### What steps will reproduce the problem?
-1. Start webapp on a remote system with --listen parameter.
-2. Add an existing (did not try for a new repository) manually created annex to the webapp using "add another local repository" (btw. file select dialog is also not working remotely)
-3. You get asked if you want to combine the new annex with the current or to keep them separate (--> keep them separate)
-4. You get forwarded to the new webapp instance but with a localhost address (127.0.0.1). The same address is also used when you manually try to swich between repositories using the repository menu.
-
-### What version of git-annex are you using? On what operating system?
-4.20130501 on Ubuntu precise from the rubiojr PPA repository
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/debug.log
-
-
-# End of transcript or log.
-"""]]
-
->> --listen no longer accepts a port. Use the new HTTPS support instead.
->> [[done]] --[[Joey]] 
diff --git a/doc/bugs/Switching_repositories_in_webapp_on_a_remote_server_is_not_honoring_--listen_parameter/comment_1_4dd773372979dd95538bfba6516a11eb._comment b/doc/bugs/Switching_repositories_in_webapp_on_a_remote_server_is_not_honoring_--listen_parameter/comment_1_4dd773372979dd95538bfba6516a11eb._comment
deleted file mode 100644
index 37b43d548..000000000
--- a/doc/bugs/Switching_repositories_in_webapp_on_a_remote_server_is_not_honoring_--listen_parameter/comment_1_4dd773372979dd95538bfba6516a11eb._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="marvin"
- ip="91.152.75.65"
- subject="Comfirm"
- date="2013-07-28T19:42:38Z"
- content="""
-I'm seeing this too. Debian sid package 4.20130723
-
-"""]]
diff --git a/doc/bugs/Syncing_creates_broken_links_instead_of_proper_files.mdwn b/doc/bugs/Syncing_creates_broken_links_instead_of_proper_files.mdwn
deleted file mode 100644
index b10df810c..000000000
--- a/doc/bugs/Syncing_creates_broken_links_instead_of_proper_files.mdwn
+++ /dev/null
@@ -1,51 +0,0 @@
-What steps will reproduce the problem?
-
-Create two repositories by running git annex webapp. Sync them by linking them to the same xmpp account. Add files on both sides.
-
-What is the expected output? What do you see instead?
-
-I expect the same file to show up on both sides with the same contents. Instead adding a file on any side creates a broken link with the same name on the other side. For example:
-
-Side A:
-
-    $ ls -la
-    total 20
-    drwxrwxr-x  3 pedrocr pedrocr 4096 Jan  3 19:24 .
-    drwxr-xr-x 55 pedrocr pedrocr 4096 Jan  3 19:19 ..
-    lrwxrwxrwx  1 pedrocr pedrocr  178 Jan  3 19:22 bar -> .git/annex/objects/FQ/vV/SHA256E-s8--12a61f4e173fb3a11c05d6471f74728f76231b4a5fcd9667cef3af87a3ae4dc2/SHA256E-s8--12a61f4e173fb3a11c05d6471f74728f76231b4a5fcd9667cef3af87a3ae4dc2
-    lrwxrwxrwx  1 pedrocr pedrocr  178 Jan  3 19:20 foo -> .git/annex/objects/g7/9v/SHA256E-s4--7d865e959b2466918c9863afca942d0fb89d7c9ac0c99bafc3749504ded97730/SHA256E-s4--7d865e959b2466918c9863afca942d0fb89d7c9ac0c99bafc3749504ded97730
-    drwxrwxr-x  7 pedrocr pedrocr 4096 Jan  3 19:24 .git
-    -rw-r--r--  1 pedrocr pedrocr    0 Jan  3 19:24 testing
-
-"foo" and "bar" are broken links that were created on Side B
-
-Side B:
-
-    $ ls -la
-    total 24
-    drwxrwxr-x  3 pedrocr pedrocr 4096 Jan  3 19:24 .
-    drwx------ 42 pedrocr pedrocr 4096 Jan  3 19:18 ..
-    -rw-r--r--  1 pedrocr pedrocr    8 Jan  3 19:22 bar
-    -rw-r--r--  1 pedrocr pedrocr    4 Jan  3 19:20 foo
-    drwxrwxr-x  7 pedrocr pedrocr 4096 Jan  3 19:24 .git
-    lrwxrwxrwx  1 pedrocr pedrocr  178 Jan  3 19:24 testing -> .git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
-
-In this case "testing" is a broken link and was created on Side A.
-
-What version of git-annex are you using? On what operating system?
-
-    $ ./git-annex version
-    git-annex version: 3.20130102
-
-    $ uname -a
-    Linux wintermute 3.2.0-35-generic #55-Ubuntu SMP Wed Dec 5 17:45:18 UTC 2012 i686 i686 i386 GNU/Linux
-
-    $ lsb_release -a
-    Distributor ID:	Ubuntu
-    Description:	Ubuntu 12.04.1 LTS
-    Release:	12.04
-    Codename:	precise
-
-> [[done]]; the webapp now detects when XMPP pairing has been used but no
-> transfer remote is available, and prompts the user to create one.
-> --[[Joey]]
diff --git a/doc/bugs/Syncing_creates_broken_links_instead_of_proper_files/comment_1_a2bedb2e77451b02fc66fc9ef5c4405c._comment b/doc/bugs/Syncing_creates_broken_links_instead_of_proper_files/comment_1_a2bedb2e77451b02fc66fc9ef5c4405c._comment
deleted file mode 100644
index 146a9b1d6..000000000
--- a/doc/bugs/Syncing_creates_broken_links_instead_of_proper_files/comment_1_a2bedb2e77451b02fc66fc9ef5c4405c._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.211"
- subject="comment 1"
- date="2013-01-03T19:38:07Z"
- content="""
-The broken links represent files whose contents have not yet arrived in the local repository.
-
-If you linked your repos by XMPP, they cannot ssh from one to the other to transfer file contents. 
-In this case, you need to set up a transfer repository, that both your repositories can access.
-"""]]
diff --git a/doc/bugs/Test_failure_on_debian_dropunused.mdwn b/doc/bugs/Test_failure_on_debian_dropunused.mdwn
deleted file mode 100644
index 459c5f55b..000000000
--- a/doc/bugs/Test_failure_on_debian_dropunused.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-### Please describe the problem.
-./git-annex test fails:
-                                          
-    ### Failure in: git-annex unused/dropunused                                                                                                     
-    dropunused failed
-    Cases: 1  Tried: 1  Errors: 0  Failures: 1   
-
-### What steps will reproduce the problem?
-./git-annex test
-
-### What version of git-annex are you using? On what operating system?
-4.20130723-206-g1647361
-
-
-debian 7.1 i686
-
-### Please provide any additional information below.
-
-I'm not sure if there is a way to get extra information out of the test harness. I had a quick look at the code and couldn't see anything obvious.
-I've tried a clean and rebuild and it reappears, so if there is more information you need just let me know what.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> Forgot to update the test suite for this behavior change.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/The_assistant_hangs_forever.mdwn b/doc/bugs/The_assistant_hangs_forever.mdwn
deleted file mode 100644
index be8968ff8..000000000
--- a/doc/bugs/The_assistant_hangs_forever.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-What steps will reproduce the problem?
-
-1. Open the assistant with git-annex webapp
-2. Click add another repository
-3. Choose "add another repository"
-4. Use "/home/pierre/testme" (try and get the problem with a new directory or an existing directory)
-5. Press "Make Repository"
-5. Choose "Keep the repository separate" 
-
-What is the expected output? What do you see instead?
-
-Go to the created repository but the interface hangs forever
-I have 4 git-annex processes that use no CPUs.
-I can still use the UI by clicking around with success or even shutdown the daemon.
-If I shutdown the daemon, all git-annex process gets killed.
-
-What version of git-annex are you using? On what operating system?
-
-It is said to be git-annex version: 4.20130324 but it is actually 4.20130405 (known bug)
-
-Please provide any additional information below.
-
-
-OS: Arch linux, bin package (not installed from source)
-All tests are OK
-Nothing happens on the log pages
-
-This is so weird that I would like to see the log file but I cannot find it. I have looked at /var/log without success.
-I have tried other available version on Arch linux (AUR git-annex-bin, AUR git-annex-standalone, haskell-web git-annex) and they all exhibit the same problem.
-At that stage, what I would like to be able is to try to figure out what is going on using the log file.
-Thanks
-
-> This could happen when using the amd64 standalone build, because I 
-> forgot to install curl into its chroot, so it was not included in the
-> bundle. If the host system also lacked curl, or something prevented
-> curl from working, it would fail like this.
-> 
-> I've included curl into the amd64 standalone build. I've also made the
-> assistant fall back to using a built-in http client if it is built
-> without curl.
-> 
-> None of which helps at all with the Arch git-annex-bin hack, since
-> that binary will be built with a working curl (when my amd64 standalone
-> builder builds it), and then installed onto a system, that,
-> apparently, has a broken curl. Which is one of many reasons I cannot
-> support that hack. [[done]] --[[Joey]]
diff --git a/doc/bugs/The_assistant_hangs_forever/comment_1_b0291e32860e0da0b66837d14ed5aab6._comment b/doc/bugs/The_assistant_hangs_forever/comment_1_b0291e32860e0da0b66837d14ed5aab6._comment
deleted file mode 100644
index b22711b65..000000000
--- a/doc/bugs/The_assistant_hangs_forever/comment_1_b0291e32860e0da0b66837d14ed5aab6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="81.244.190.181"
- subject="comment 1"
- date="2013-04-14T09:45:35Z"
- content="""
-Forgot to mention that this is my first attempt to work with the assistant on 64 bits (previous binary package were 32 bits only)
-"""]]
diff --git a/doc/bugs/The_assistant_hangs_forever/comment_2_a2950cf91b8a4e4f2951f5522ef0e9c4._comment b/doc/bugs/The_assistant_hangs_forever/comment_2_a2950cf91b8a4e4f2951f5522ef0e9c4._comment
deleted file mode 100644
index 90b93f0bb..000000000
--- a/doc/bugs/The_assistant_hangs_forever/comment_2_a2950cf91b8a4e4f2951f5522ef0e9c4._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="saironiq"
- ip="147.251.209.29"
- subject="comment 2"
- date="2013-04-14T12:09:11Z"
- content="""
-Not sure if this is the real reason, but I get a bunch of
-
->curl: symbol lookup error: /usr/lib/libssl.so.1.0.0: undefined symbol: EVP_idea_cbc
-
-errors in the git-annex log. Running nm on the lib produces the following:
-
->$ nm /usr/lib/libssl.so.1.0.0 | grep EVP_idea_cbc<br>
->&nbsp;&nbsp;&nbsp;&nbsp;U EVP_idea_cbc
-
-...where \"U\" means undefined. I think the reason 64-bit does not work is that there is no curl (and lsof) binaries and libs included.
-
-"""]]
diff --git a/doc/bugs/The_assistant_hangs_forever/comment_3_db95f78519d5ffbad793906028730dab._comment b/doc/bugs/The_assistant_hangs_forever/comment_3_db95f78519d5ffbad793906028730dab._comment
deleted file mode 100644
index e9e76f5b2..000000000
--- a/doc/bugs/The_assistant_hangs_forever/comment_3_db95f78519d5ffbad793906028730dab._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-14T17:57:47Z"
- content="""
-The assistant's log file is stored in `.git/annex/daemon.log` within the git repository.
-
-I have to say I don't really understand the bug report. In one sentence you say the \"interface hangs forever\", and then in the next sentence you say you can \"still use the UI by clicking around\". These statements contradict one-another.
-
-(@saironiq, I don't see any connection between what you're saying and pradermecker's bug report. If you have a bug to report, you should file a separate bug report.)
-"""]]
diff --git a/doc/bugs/The_assistant_hangs_forever/comment_4_28b13fd3165b38a2fbc9e1a461c38921._comment b/doc/bugs/The_assistant_hangs_forever/comment_4_28b13fd3165b38a2fbc9e1a461c38921._comment
deleted file mode 100644
index 3bec70a7f..000000000
--- a/doc/bugs/The_assistant_hangs_forever/comment_4_28b13fd3165b38a2fbc9e1a461c38921._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="saironiq"
- ip="147.251.209.29"
- subject="comment 4"
- date="2013-04-15T10:35:36Z"
- content="""
-These symbol lookup errors appear right after i click 'keep the repositories separate', so I think there indeed is a connection. There's nothing else in the log, except this one line repeating over and over again.
-
->[2013-04-15 11:14:30 CEST] main: starting assistant version 4.20130324<br/>
->Already up-to-date.</br>
->
->(scanning...) [2013-04-15 11:14:31 CEST] Watcher: Performing startup scan<br/>
->Already up-to-date.<br/>
->
->(started...) [2013-04-15 12:14:30 CEST] NetWatcherFallback: Syncing with wolf, zyzyx<br/>
->(Recording state in git...)<br/>
->git-annex: Daemon is already running.<br/>
->curl: symbol lookup error: /usr/lib/libssl.so.1.0.0: undefined symbol: EVP_idea_cbc<br/>
->curl: symbol lookup error: /usr/lib/libssl.so.1.0.0: undefined symbol: EVP_idea_cbc<br/>
->curl: symbol lookup error: /usr/lib/libssl.so.1.0.0: undefined symbol: EVP_idea_cbc<br/>
->...
-"""]]
diff --git a/doc/bugs/The_assistant_hangs_forever/comment_5_81a79c8840ff26307a9c6edad5b850f9._comment b/doc/bugs/The_assistant_hangs_forever/comment_5_81a79c8840ff26307a9c6edad5b850f9._comment
deleted file mode 100644
index f8b6a61bc..000000000
--- a/doc/bugs/The_assistant_hangs_forever/comment_5_81a79c8840ff26307a9c6edad5b850f9._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="saironiq"
- ip="147.251.209.29"
- subject="comment 5"
- date="2013-04-15T11:01:32Z"
- content="""
-Here's a full strace output (first symbol lookup error is on line #102681):<br/>
-[[https://dl.dropboxusercontent.com/u/62238161/webapp.log]]
-"""]]
diff --git a/doc/bugs/The_assistant_hangs_forever/comment_6_b739719b14705f4d7e1d412b3cab090c._comment b/doc/bugs/The_assistant_hangs_forever/comment_6_b739719b14705f4d7e1d412b3cab090c._comment
deleted file mode 100644
index 0e05b5090..000000000
--- a/doc/bugs/The_assistant_hangs_forever/comment_6_b739719b14705f4d7e1d412b3cab090c._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="81.244.149.180"
- subject="comment 6"
- date="2013-04-15T19:59:00Z"
- content="""
-I can confirm I also get the error: 
-curl: symbol lookup error: /usr/lib/libssl.so.1.0.0: undefined symbol: EVP_idea_cbc
-
-What I mean by the UI is hanging is that after the last action, I can see that the page is never fully re-loaded. So to be more precise the reloading of the page never stops.
-
-When I am bored waiting for the page to reload ;-) I can still use the UI in the situation I describe (left to assume the operation fails :-)
-
-I believe @saironiq is right: the problem is related to the 64 bits version.
-
-
-"""]]
diff --git a/doc/bugs/The_assistant_hangs_forever/comment_7_2b300d960697c5b967c1f109dfd6dfbf._comment b/doc/bugs/The_assistant_hangs_forever/comment_7_2b300d960697c5b967c1f109dfd6dfbf._comment
deleted file mode 100644
index 8203bbb66..000000000
--- a/doc/bugs/The_assistant_hangs_forever/comment_7_2b300d960697c5b967c1f109dfd6dfbf._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="81.244.149.180"
- subject="comment 7"
- date="2013-04-15T20:39:20Z"
- content="""
-@joey just to make the connection clear, both @saironiq and I use the same git-annex package (bin package) from Arch linux AUR (@saironiq is the maintainer of the package)
-
-I suspect all 64bits binary packages on Arch linux to exhibit problems. 
-
-The package is fetching the bin archive from your repo: so I actually dare to suspect that all recent 64bits versions have similar problems.
-
-I have describe one problem but they are many, so it does not take long to realize that the apps is not working properly.
-
-I guess it is a packaging problem (something is missing in <http://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz>), not an application bug ?
-"""]]
diff --git a/doc/bugs/The_assistant_hangs_forever/comment_8_8623220d08b1a72ed8b669a2d9cc0f75._comment b/doc/bugs/The_assistant_hangs_forever/comment_8_8623220d08b1a72ed8b669a2d9cc0f75._comment
deleted file mode 100644
index cc275eb2c..000000000
--- a/doc/bugs/The_assistant_hangs_forever/comment_8_8623220d08b1a72ed8b669a2d9cc0f75._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 8"
- date="2013-04-16T18:39:30Z"
- content="""
-Switching repositories uses curl to discover when the other daemon has started. If you installed <https://aur.archlinux.org/packages/git-annex-bin/> , it will use the curl binary provided by your distribution. It looks like yours is broken.
-
-> \"I have describe one problem but they are many, so it does not take long to realize that the apps is not working properly.\"
-
-Yes, that's the real problem, isn't it? <https://aur.archlinux.org/packages/git-annex-bin/> 
-takes the binary built for the standalone tarball and dumps it into a filesystem without any of its support libraries, and just hopes it works. It's not at all surpising that it continually fails to work. Which is causing bug report noise that takes away from my time working on actual improvements to git-annex.
-
-I'm sorry, but I cannot support that package. Use <https://aur.archlinux.org/packages.php?ID=44272> or install using cabal or use the standalone tarball.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible.mdwn b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible.mdwn
deleted file mode 100644
index b98e09b32..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-**What steps will reproduce the problem?**
-
-On my work computer I created a new repository and then added a directory on my home server to backup some of my files. The assistant created a new key pair which then made password login quite hard.
-On the commandline I could still login via ssh -o PreferredAuthentications=keyboard-interactive ... but all gui tools (e.g. gigolo) stop after connecting to the restricted shell.
-I don't want to allow full passwordless access to my server from this computer.
-
-**What is the expected output? What do you see instead?**
-
-It should be possible to use this private key with git-annex exclusively. Maybe a line like this in the [remote] block in .git/config would solve the problem:
-
-    IdentityFile = /home/user/.ssh/annex/id_rsa_annex
-
-I think it should be the default behaviour that git-annex uses its own key pair with restricted access. For portability the keys could be stored somewhere in the repository itself.
-
-**What version of git-annex are you using? On what operating system?**
-
-git-annex version: 4.20130324, Ubuntu 11.04
-
-**Please provide any additional information below.**
-
-> [[done]]. Although I have not 100% reproduced this, I have seen 
-> enough of the source code to gnome-keyring to be pretty sure it's at
-> fault, and that my fix works.
-> 
-> If this is happening to you, you can fix it by making a `~/.ssh/annex/`
-> directory and moving `~/.ssh/key.annex*` to it. Then you'll need to edit
-> `~/.ssh/config` to use the new path to the key. And you'll need to run
-> `ssh-add -D` to clear out the bogus keys from the ssh agent (or log out
-> and back in). --[[Joey]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_10_8305becdc6e70abdaf17e42f263173fc._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_10_8305becdc6e70abdaf17e42f263173fc._comment
deleted file mode 100644
index 09c4802f7..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_10_8305becdc6e70abdaf17e42f263173fc._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="marvin"
- ip="91.152.75.65"
- subject="comment 10"
- date="2013-04-14T02:34:50Z"
- content="""
-Hopefully I haven't done anything stupid, wouldn't be the first time :)
-Retried with a different setup, same result.
-Pasted into pastebin as I wasn't sure about the formatting..
-
-<http://pastebin.com/vnnmiBeE>
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_11_d75896a6e204d1abdda04923aa668d04._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_11_d75896a6e204d1abdda04923aa668d04._comment
deleted file mode 100644
index 31460ae5b..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_11_d75896a6e204d1abdda04923aa668d04._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 11"
- date="2013-04-14T02:58:05Z"
- content="""
-Thanks for that.. It's not verbose enough for me to see it choose the key to use. Can you add one more `v`? ssh -vvv , 3 v's..
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_12_a36a4a64a04c01c2db467b09300e6ebd._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_12_a36a4a64a04c01c2db467b09300e6ebd._comment
deleted file mode 100644
index 428d5a43c..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_12_a36a4a64a04c01c2db467b09300e6ebd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="marvin"
- ip="91.152.75.65"
- subject="comment 12"
- date="2013-04-14T09:51:27Z"
- content="""
-hmm.. I did use -vvv, even tried with 4 which doesen't change anything. Is there a ceartain version of ssh or debian live image I could test with? There shouldn't be anything extraordinary about my setup.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_13_c9d6631c304acb289e485fb901e1f274._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_13_c9d6631c304acb289e485fb901e1f274._comment
deleted file mode 100644
index 083c1e5a2..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_13_c9d6631c304acb289e485fb901e1f274._comment
+++ /dev/null
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 13"
- date="2013-04-14T18:27:35Z"
- content="""
-This should not be a hard problem to debug. 
-
-* You have a local client, and a remote server.
-* The remote server has a `~/.ssh/authorized_keys` file that contains a public key that git-annex set up, which is restricted to only run \"command=git-annex-shell\".
-* The local client has that key in `~/.ssh/key.git-annex-$hostname-$username`
-* The local client is configured in `~/.ssh/config` to only use that key when sshing to the special hostname \"git-annex-$hostname-$username\"
-* The problem is either on the client, or on the server.
-* If the problem is on the client, then it must be, somehow, incorrectly sending the git-annex key to the server when you \"ssh $hostname\". You can see what keys it decides to send by looking at the messages it prints with -vvv :
- 
-<pre>
-joey@gnu:~>ssh -vvv git-annex-kitenet.net-joey
-OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1e 11 Feb 2013
-debug1: Reading configuration data /home/joey/.ssh/config
-debug1: /home/joey/.ssh/config line 3: Applying options for git-annex-kitenet.net-joey
-debug1: Reading configuration data /etc/ssh/ssh_config
-debug1: /etc/ssh/ssh_config line 19: Applying options for *
-debug2: ssh_connect: needpriv 0
-debug1: Connecting to kitenet.net [80.68.85.49] port 22.
-debug1: Connection established.
-debug3: Incorrect RSA1 identifier
-debug3: Could not load \"/home/joey/.ssh/key.git-annex-kitenet.net-joey\" as a RSA1 public key
-debug1: identity file /home/joey/.ssh/key.git-annex-kitenet.net-joey type 1
-</pre>
-
-* If the problem is on the server, then it must be for some reason deciding to run `git-annex-shell` when you ssh in,
-  despite the client not sending it the special git-annex key. If this were the case, no change you made on the client could fix   
-  the problem, but deleting `.ssh/authorized_keys` on the server probably would.
-
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_14_10282c4352075c8d148b8674973b7b16._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_14_10282c4352075c8d148b8674973b7b16._comment
deleted file mode 100644
index 0b1da9029..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_14_10282c4352075c8d148b8674973b7b16._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="ssh agent?"
- date="2013-04-14T18:34:45Z"
- content="""
-The only other thing I can think of is that if you have a ssh-agent, it might somehow be caching the git-annex key and incorrectly sending it to ssh. If this were the case, then unsetting `SSH_AUTH_SOCK` or stopping the agent would presumably make the problem go away.
-
-In @marvin's log, I see:
-
-<pre>
-debug1: Offering RSA public key: marvin@marvin-U-100
-</pre>
-
-This is different from what I see when ssh is using a regular key in `.ssh/`:
-
-<pre>
-debug1: Offering RSA public key: /home/joey/.ssh/id_rsa
-</pre>
-
-Marvin's log does not show where it gets this \"marvin@marvin-U-100\".. which makes me suspect it comes from a ssh agent.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_15_ceb68da01d9e2fe9a70fab6244116da0._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_15_ceb68da01d9e2fe9a70fab6244116da0._comment
deleted file mode 100644
index bbf5a45b5..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_15_ceb68da01d9e2fe9a70fab6244116da0._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 15"
- date="2013-04-14T18:46:54Z"
- content="""
-I tried the following experiment:
-
-1. Manually ran `ssh-add .ssh/key.git-annex-kitenet.net-joey`
-2. `ssh -vvv kitenet.net` did run git-annex-shell
-
-Guys, please paste the output of `ssh-add -l`
-
-Also, if you run `ssh-add -D`, the problem should go away, and the server should not run git-annex-shell. If that's the case, we've confirmed this is somehow a ssh agent problem. However, I still don't know what could be scanning `~/.ssh` for random keys and loading them into the agent.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_16_cca4abde86a8be5e2919c4738f5bdd0c._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_16_cca4abde86a8be5e2919c4738f5bdd0c._comment
deleted file mode 100644
index 2260917b3..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_16_cca4abde86a8be5e2919c4738f5bdd0c._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 16"
- date="2013-04-14T19:04:11Z"
- content="""
-Are you guys running Gnome? Using gnome-keyring?
-
-I found the following highly suspicious code inside gnome-keyring:
-
-[[!format C \"\"\"
-        if (!self->directory)
-                self->directory = g_strdup (\"~/.ssh\");
-        self->tracker = gkm_file_tracker_new (self->directory, \"*.pub\", NULL);
-\"\"\"]]
-
-This seems to load *all* keys, as described. Not keys in subdirectories of ~/.ssh/ either.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_17_2fa5d7d9110c91b0a3a833cb3d9f53fd._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_17_2fa5d7d9110c91b0a3a833cb3d9f53fd._comment
deleted file mode 100644
index 2b760bb55..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_17_2fa5d7d9110c91b0a3a833cb3d9f53fd._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="marvin"
- ip="91.152.75.65"
- subject="comment 17"
- date="2013-04-14T20:07:33Z"
- content="""
-YES! Straight from the tty console it works correctly. Seems this project unearths lots of bugs all over the place.
-
-Thank you!
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_18_bf21d28142e4c304aa0bc740955ddea0._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_18_bf21d28142e4c304aa0bc740955ddea0._comment
deleted file mode 100644
index 67021d180..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_18_bf21d28142e4c304aa0bc740955ddea0._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 18"
- date="2013-04-14T20:13:54Z"
- content="""
-@Marvin, just to be clear, it was `ssh-add -D` that fixed it for you?
-
-To make the fix stick, you need to make a ~/.ssh/annex/ directory, and move the keys to there, and then edit ~/.ssh/config to use the new path to the key file. This should prevent gnome-keyring from seeing them.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_19_45537758fa937f16fc82120bf8b234e8._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_19_45537758fa937f16fc82120bf8b234e8._comment
deleted file mode 100644
index 3d0d4a45e..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_19_45537758fa937f16fc82120bf8b234e8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="marvin"
- ip="91.152.75.65"
- subject="comment 19"
- date="2013-04-14T20:47:37Z"
- content="""
-nope, ssh-add -D doesn't seem to help. Killing gnome-keyring-daemon does.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_1_a38497772834a4b12137390b461ce70b._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_1_a38497772834a4b12137390b461ce70b._comment
deleted file mode 100644
index fb7bd7420..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_1_a38497772834a4b12137390b461ce70b._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-09T17:29:00Z"
- content="""
-The key pair that the assistant sets up is limited, in ~/.ssh/config to only be used when a mangled version of the hostname is used. That is, you have to \"ssh git-annex-hostname\" to use that key. So it should not be possible for this to impact your normal use of ssh to that host.
-
-(`.git/config` does not support an `IdentityFile` option TTBOMK.)
-
-You need to provide more details about the problem you have encountered.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_20_b685050ee6fbb1a685e33f9656a10e84._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_20_b685050ee6fbb1a685e33f9656a10e84._comment
deleted file mode 100644
index 83ab46051..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_20_b685050ee6fbb1a685e33f9656a10e84._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 20"
- date="2013-04-14T20:59:26Z"
- content="""
-Ok, I don't know how gnome-keyring communicates with ssh, but that's good enough evidence for me: It was certainly gnome-keyring that got us into this mess!
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_3_17bc0220c20553c848875475c5fd4ae6._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_3_17bc0220c20553c848875475c5fd4ae6._comment
deleted file mode 100644
index f8e07dd4a..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_3_17bc0220c20553c848875475c5fd4ae6._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-11T16:26:26Z"
- content="""
-When git-annex uses an existing key (which is done automatically if it detects you have already set up passwordless login to the server using the default key), it does not configure the server to further restrict use of that key.
-
-I have just verified this to be sure. That would be a bad bug. Doesn't happen.
-
-So, I still don't understand what this bug report is about.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_4_76472bc58bb790f773c46ec2c39fcf88._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_4_76472bc58bb790f773c46ec2c39fcf88._comment
deleted file mode 100644
index 54bfc750b..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_4_76472bc58bb790f773c46ec2c39fcf88._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl99Gxq3NPNvwZHp3PDufaknQH4rZb_KKY"
- nickname="Florian"
- subject="comment 4"
- date="2013-04-12T15:01:16Z"
- content="""
-I think I found a part of the problem. I still don't know why there was this strange key setup in the beginning. Maybe i did this manually and forgot about it instantly...
-
-However, today I again had the problem with ending up in git-annex-shell on the commandline. To debug this I called ssh -vvv ... and found out that ssh somehow found the private key in ~/.ssh/key.git-annex-servername-username and ofcourse tried to use it.
-Moving the key to a subdirectory in ~/.ssh/ and fixing the path in ~/.ssh/config solved my problem again.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_4_dcd9286e314779c25764484beff40561._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_4_dcd9286e314779c25764484beff40561._comment
deleted file mode 100644
index 44df43339..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_4_dcd9286e314779c25764484beff40561._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl99Gxq3NPNvwZHp3PDufaknQH4rZb_KKY"
- nickname="Florian"
- subject="comment 4"
- date="2013-04-10T12:39:49Z"
- content="""
-OK, problem solved. I deleted the key on the server and then readded the repository. Now I have a separate git-annex key pair and the config is as you described. I don't know why an existing key pair was used in the setup before. I log into my home server frequently and don't remember that I added the public key manually (especially regarding the restriction to git-annex-shell that was applied).
-
-However, thanks for the great work so far!
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_5_2146eec77b87b615100d0d003e8dce75._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_5_2146eec77b87b615100d0d003e8dce75._comment
deleted file mode 100644
index 8889c3adb..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_5_2146eec77b87b615100d0d003e8dce75._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="marvin"
- ip="91.152.75.65"
- subject="Seeing the same thing"
- date="2013-04-13T22:36:00Z"
- content="""
-So what I did on a clean ubuntu install was
-
-1. start git-annex-webapp Version: ( 4.20130413-g5747bf4 )
-2. set up local repository and remote ssh repository
-3. sync some files
-4. trying to ssh from the console to the remote now fails with error message \"git-annex-shell: bad parameters\"
-
-I do believe it has always done this (also on wheezy). Is this supposed to work this way? Hope to get a webdav / owncloud / some own hosted system not relying on ssh. Just want to sync files to a headless server. I'll gladly help if I can.
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_6_2bd6f4e04903ee251d43d0a97bd40b6e._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_6_2bd6f4e04903ee251d43d0a97bd40b6e._comment
deleted file mode 100644
index 901798fe8..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_6_2bd6f4e04903ee251d43d0a97bd40b6e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 6"
- date="2013-04-13T22:40:02Z"
- content="""
-No, it is not supposed to do that. Can you take a look at the `.ssh/authorized_keys` file on the remote and see what key it has configured to run git-annex-shell? This should not be your main ssh key..
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_7_7db8ed002eb6313b07f09bd1a34019e3._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_7_7db8ed002eb6313b07f09bd1a34019e3._comment
deleted file mode 100644
index cf1e30824..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_7_7db8ed002eb6313b07f09bd1a34019e3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 7"
- date="2013-04-13T22:48:55Z"
- content="""
-@Florian, it seems very unlikely that ssh would go off and pick a **utterly random file** to use as the key. ssh generally tries to be consistent, and secure, and that would be neither. 
-
-Can you paste the `ssh -vv` output when it does it?
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_8_1bcb2a238006044bc78849e56cb21a01._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_8_1bcb2a238006044bc78849e56cb21a01._comment
deleted file mode 100644
index 9cc054b39..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_8_1bcb2a238006044bc78849e56cb21a01._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="marvin"
- ip="91.152.75.65"
- subject="comment 8"
- date="2013-04-14T00:37:21Z"
- content="""
-The key in authorized file is the same as git-annex pub key ( key.git-annex-192.168.1.43-marvin.pub )
-Which is also the only ssh key in the authorized file. Is it assumed keys are always used instead of only passwords?
-"""]]
diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_9_26c6937cf78e7141e0e3b20f25ed8f7a._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_9_26c6937cf78e7141e0e3b20f25ed8f7a._comment
deleted file mode 100644
index 7f36e3c43..000000000
--- a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_9_26c6937cf78e7141e0e3b20f25ed8f7a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 9"
- date="2013-04-14T00:46:32Z"
- content="""
-Can you please paste the output of `ssh -vvv host
-"""]]
diff --git a/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories.mdwn b/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories.mdwn
deleted file mode 100644
index 88e39efe9..000000000
--- a/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories.mdwn
+++ /dev/null
@@ -1,33 +0,0 @@
-What steps will reproduce the problem?
-
-After creating new remote repositories in the webapp there's no option to delete them
-
-What is the expected output? What do you see instead?
-
-Some option to delete a repository, just like I can disable sync or change the config of a remote
-
-What version of git-annex are you using? On what operating system?
-
-    $ ./git-annex version
-    git-annex version: 3.20130102
-
-    $ uname -a
-    Linux wintermute 3.2.0-35-generic #55-Ubuntu SMP Wed Dec 5 17:45:18 UTC 2012 i686 i686 i386 GNU/Linux
-
-    $ lsb_release -a
-    Distributor ID:	Ubuntu
-    Description:	Ubuntu 12.04.1 LTS
-    Release:	12.04
-    Codename:	precise
-
-[[!tag /design/assistant]]
-
-> Status: You can delete the current repository. You can also remove
-> repositories from the list of remotes (without deleting their content)
-> and you can tell it you want to stop using a remote, and it will
-> suck all content off that remote until it's empty.
-> 
-> Still todo: Detect when a remote has been sucked dry, and actually delete
-> it. --[[Joey]]
-
->> [[done]] --[[Joey]]
diff --git a/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_1_1b80f9cfedd25e34997fa07e08d15012._comment b/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_1_1b80f9cfedd25e34997fa07e08d15012._comment
deleted file mode 100644
index 5087b5f4e..000000000
--- a/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_1_1b80f9cfedd25e34997fa07e08d15012._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.211"
- subject="comment 1"
- date="2013-01-03T19:48:46Z"
- content="""
-Something I would like to support, although complicated by what \"delete\" means. At its simplest it can mean removing the git remote configuration, but leaving the remote's data as-is, so it can be added back, or other repositories can continue to access it. More complicated, it could mean completely deleting the repository, and its data -- which would probably first need to move any data that was solely in that repository off to elsewhere.
-"""]]
diff --git a/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_2_53499da1185c56d8fd25f86ba41d96ce._comment b/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_2_53499da1185c56d8fd25f86ba41d96ce._comment
deleted file mode 100644
index e84094738..000000000
--- a/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_2_53499da1185c56d8fd25f86ba41d96ce._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="it also doesn't recognize when a local repository has been deleted manually"
- date="2013-01-09T16:13:41Z"
- content="""
-I created a new local repository to play with the new Direct Mode features.  I ended up deleting it (deleting the directory), but when I launched the assistant, I was still given the option of \"switching repository\" to the now-deleted one.  It threw the error Internal Server Error (user error (git [\"config\",\"--null\",\"--list\"] exited 126)).
-
-> Fixed this. --[[Joey]]
-
-"""]]
diff --git a/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_3_3e07b8386d2c7afce2a78d24b9c260b9._comment b/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_3_3e07b8386d2c7afce2a78d24b9c260b9._comment
deleted file mode 100644
index 76342ec63..000000000
--- a/doc/bugs/The_webapp_doesn__39__t_allow_deleting_repositories/comment_3_3e07b8386d2c7afce2a78d24b9c260b9._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://piotr.ozarowski.pl/"
- nickname="p1otr"
- subject="Re: comment 1"
- date="2013-01-15T09:26:21Z"
- content="""
-How about asking the user? Something like:
-
-Do you want to...
-
-* only remove configuration from annex
-* make sure there's a copy of all files from this repository somewhere and remove it (including remote files)
-* remove remote files (and remove them from annex if there's no other copy)
-"""]]
diff --git a/doc/bugs/Too_many_open_files.mdwn b/doc/bugs/Too_many_open_files.mdwn
deleted file mode 100644
index 53c9bb690..000000000
--- a/doc/bugs/Too_many_open_files.mdwn
+++ /dev/null
@@ -1,59 +0,0 @@
-### Please describe the problem.
-
-The transferrer crashes after a while due to too many open files
-
-### What steps will reproduce the problem?
-
-Have a huge annex. Connect two local machines, one with the huge annex, the other one without. Let them copy files…
-
-### What version of git-annex are you using? On what operating system?
-
-latest version
-git-annex version: 5.20131117-gbd514dc
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-
-on Mac OS X 10.9
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[2013-11-22 10:49:19 CET] Transferrer: Downloaded oktaeder.png
-[2013-11-22 10:49:19 CET] Transferrer: Downloaded oktaeder.png
-[2013-11-22 10:49:19 CET] Transferrer: Downloaded oktaeder.png
-[2013-11-22 10:49:20 CET] Transferrer: Downloaded klett-cover-neu.jpg
-[2013-11-22 10:49:20 CET] Transferrer: Downloaded klett-cover-neu.jpg
-[2013-11-22 10:49:20 CET] Transferrer: Downloaded kara-worl..ditor.gif
-git-annex: runInteractiveProcess: pipe: Too many open files
-Committer crashed: lsof: createProcess: resource exhausted (Too many open files)
-[2013-11-22 10:49:20 CET] Committer: warning Committer crashed: lsof: createProcess: resource exhausted (Too many open files)
-[2013-11-22 10:49:20 CET] Transferrer: Downloaded kara-worl..ditor.gif
-[2013-11-22 10:49:20 CET] Transferrer: Downloaded kara-worl..ditor.gif
-[2013-11-22 10:49:20 CET] Transferrer: Downloaded image1.png
-[2013-11-22 10:49:21 CET] Transferrer: Downloaded image1.png
-[2013-11-22 10:49:21 CET] Transferrer: Downloaded image.png
-[2013-11-22 10:49:21 CET] Transferrer: Downloaded image.png
-[2013-11-22 10:49:21 CET] Transferrer: Downloaded ikoseder.png
-[2013-11-22 10:49:21 CET] Transferrer: Downloaded ikoseder.png
-[2013-11-22 10:49:22 CET] Transferrer: Downloaded ikoseder.png
-[2013-11-22 10:49:22 CET] Transferrer: Downloaded ikosaeder.jpg
-git-annex: runInteractiveProcess: pipe: Too many open files
-ok
-(Recording state in git...)
-git-annex: socket: resource exhausted (Too many open files)
-[2013-11-22 10:49:22 CET] Transferrer: Downloaded ikosaeder.jpg
-Transferrer crashed: getCurrentDirectory: resource exhausted (Too many open files)
-[2013-11-22 10:49:22 CET] Transferrer: warning Transferrer crashed: getCurrentDirectory: resource exhausted (Too many open files)
-git-annex: runInteractiveProcess: pipe: Too many open files
-git-annex: runInteractiveProcess: pipe: Too many open files
-
-# End of transcript or log.
-"""]]
-
-> This appears to be the same problem as [[Resource_exhausted]],
-> so closing as duplicate; please follow up to the other bug report if
-> possible. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Too_many_open_files/comment_1_d5d509b9b431d2ea6000ebc0aed62857._comment b/doc/bugs/Too_many_open_files/comment_1_d5d509b9b431d2ea6000ebc0aed62857._comment
deleted file mode 100644
index 477192692..000000000
--- a/doc/bugs/Too_many_open_files/comment_1_d5d509b9b431d2ea6000ebc0aed62857._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 1"
- date="2013-11-26T16:28:25Z"
- content="""
-You can use `lsof -c git-annex` to find out what files git-annex has open. (lsof is included in the git-annex.app bundle on OSX) That would be very helpful in tracking this down.
-"""]]
diff --git a/doc/bugs/Too_much_system_load_on_startup.mdwn b/doc/bugs/Too_much_system_load_on_startup.mdwn
deleted file mode 100644
index fc514ca73..000000000
--- a/doc/bugs/Too_much_system_load_on_startup.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-### Please describe the problem.
-When I log in, if git annex is monitoring a large repo, my desktop is very sluggish getting started. Git-annex causes moderate CPU load, but keeps the disk IO very busy -delaying the opening of desktop applications.
-
-### What steps will reproduce the problem?
-On Linux, with git-annex set to autostart and monitoring a folder with more than a few hundred files (I have a pdf library of a few thousand journal articles).
-
-### What version of git-annex are you using? On what operating system?
-4.20131002 Ubuntu, from Hess's PPA.
-
-### Please provide any additional information below.
-
-I solved this problem by changing the call to git-annex in /etc/xdg/autostart/git-annex.desktop from:
-
-Exec=/usr/bin/git-annex assistant --autostart
-
-to
-
-Exec=sleep 5 ionice -c 3 /usr/bin/git-annex assistant --autostart
-
-This delays the start of git-annex for 5 seconds, letting the desktop get started, and forces git-annex to yield IO to other programs -preventing it from slowing them down by forcing them to wait for disk access. Since this is a background daemon with potentially high IO usage, but no need for quick responsiveness, perhaps that would make a decent default?
-
-> Added 5 second delay to existing ionice. Provisionally [[done]],
-> although it does occur to me that the startup scan could add some delays
-> in between actions to run more as a batch job. --[[Joey]]
diff --git a/doc/bugs/Too_much_system_load_on_startup/comment_1_4470cddc0965062588acff1bc77285e9._comment b/doc/bugs/Too_much_system_load_on_startup/comment_1_4470cddc0965062588acff1bc77285e9._comment
deleted file mode 100644
index 31e735985..000000000
--- a/doc/bugs/Too_much_system_load_on_startup/comment_1_4470cddc0965062588acff1bc77285e9._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 1"
- date="2013-10-26T16:44:59Z"
- content="""
-git-annex version 4.20131002 *already* ionices itself on startup, assuming it detects a system it can do that on. So the only relevant change you made is delaying it from starting. I have made the assistant wait 5 seconds before running the startup scan when autostarted.
-"""]]
diff --git a/doc/bugs/TransferScanner_crash_on_Android.mdwn b/doc/bugs/TransferScanner_crash_on_Android.mdwn
deleted file mode 100644
index 56d869537..000000000
--- a/doc/bugs/TransferScanner_crash_on_Android.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-
-TransferScanner crashes trying to add a file.
-
-### What steps will reproduce the problem?
-
-Start the web app.
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130709-g339d1e0 on Android.
-
-### Please provide any additional information below.
-
-There was a whole stack of nulls in some of those log lines as well. I've 
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-TransferScanner crashed: unknown response from git cat-file ("refs/heads/git-annex:289/20f/SHA256E-s85883241--3bf01cfd6a422f9b661ed335e6142bbdaf899cd71587bb3cc812256064c7071e missing",refs/heads/git-annex:289/20f/SHA256E-s85883241--3bf01cfd6a422f9b661ed335e6142bbdaf899cd71587bb3cc812256064c7071e\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00(7981 more elided)\00.log)
-[2013-07-16 15:19:26 NZST] TransferScanner: warning TransferScanner crashed: unknown response from git cat-file ("refs/heads/git-annex:289/20f/SHA256E-s85883241--3bf01cfd6a422f9b661ed335e6142bbdaf899cd71587bb3cc812256064c7071e missing",refs/heads/git-annex:289/20f/SHA256E-s85883241--3bf01cfd6a422f9b661ed335e6142bbdaf899cd71587bb3cc812256064c7071e\00\00\00\00\00(7991 more elided)\00.log)
-# End of transcript or log.
-"""]]
-
-> Lacking other information about this problem, and with the assistant
-> able to detect problems and run `git annex repair` to fix up corrupt git
-> repos, I suppose this is [[done]] --[[Joey]]
diff --git a/doc/bugs/TransferScanner_crash_on_Android/comment_1_6c3584ade1ee6cccddddeaa8e1697945._comment b/doc/bugs/TransferScanner_crash_on_Android/comment_1_6c3584ade1ee6cccddddeaa8e1697945._comment
deleted file mode 100644
index c7622955b..000000000
--- a/doc/bugs/TransferScanner_crash_on_Android/comment_1_6c3584ade1ee6cccddddeaa8e1697945._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.90"
- subject="comment 1"
- date="2013-07-16T18:16:52Z"
- content="""
-Wow, that's a lot of NULs!
-
-Can you drop to a shell and run `git fsck` in the repository?
-
-I'm guessing that `git annex fsck` is going to fail with some of the same type errors, but you could also try it.
-
-It seems pretty clear there's damage somewhere. Like something (perhaps a compact flash glitch?) inserted a ton of NULs into the git repository, or corrupted a filename's length field or something.
-
----
-
-Probably the best thing to do, to get back to a working repository is to move the current repo out of the way, re-setup the assistant on your Android from one of your other repositories (assuming you have another one). Or if this is your only clone of this git repository, you may be able to run `git annex uninit` in it.
-
-Then if necessary the contents of files can be rescued from `.git/annex/objects/` in the corrupt repository, by running `git annex import` in the new repository and passing it that directory. And finish up with a `git annex fsck`.
-"""]]
diff --git a/doc/bugs/TransferScanner_crash_on_Android/comment_2_06574e05149a677d666a722061586658._comment b/doc/bugs/TransferScanner_crash_on_Android/comment_2_06574e05149a677d666a722061586658._comment
deleted file mode 100644
index 12105342c..000000000
--- a/doc/bugs/TransferScanner_crash_on_Android/comment_2_06574e05149a677d666a722061586658._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkF8_uQjLYm5Mf5F_JuVW-BxlvzpWjvR_o"
- nickname="Andrew"
- subject="git annex fsck"
- date="2013-07-16T22:22:25Z"
- content="""
-Running git annex fsck appears to have resolved the corruption, but it removed all the content and the assistant hasn't refetched them.
-
-I'm running git annex get . now to refetch all the content.
-"""]]
diff --git a/doc/bugs/TransferScanner_crash_on_Android/comment_3_54ae097d30bb7a49fe151f38c9bac033._comment b/doc/bugs/TransferScanner_crash_on_Android/comment_3_54ae097d30bb7a49fe151f38c9bac033._comment
deleted file mode 100644
index bb31e7f86..000000000
--- a/doc/bugs/TransferScanner_crash_on_Android/comment_3_54ae097d30bb7a49fe151f38c9bac033._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.90"
- subject="comment 3"
- date="2013-07-17T19:12:49Z"
- content="""
-I don't see how git annex fsck could resolve the corruption, which appeared to be of data from the git repository, not the git-annex content store. Did you try `git fsck`?
-"""]]
diff --git a/doc/bugs/Trouble_initializing_git_annex_on_NFS.mdwn b/doc/bugs/Trouble_initializing_git_annex_on_NFS.mdwn
deleted file mode 100644
index 8eb20baf9..000000000
--- a/doc/bugs/Trouble_initializing_git_annex_on_NFS.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-The following occurs in a directory that is shared on an NFS server:
-
-    /media/mybook/movies $ git init
-    Initialized empty Git repository in /media/mybook/movies/.git/
-    /media/mybook/movies $ git annex init mybook-movies
-    init mybook-movies 
-    git-annex: waitToSetLock: resource exhausted (No locks available)
-    failed
-    git-annex: init: 1 failed
-    /media/mybook/movies $
-
-This happens reliably.  Is there any way around it?  I have shell
-access on the NFS server, but it is a NAS, so I don't think it is
-capable of running git-annex.
-
-[[done]]
diff --git a/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_1_e26952373150d63b8a5d3643a2762de1._comment b/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_1_e26952373150d63b8a5d3643a2762de1._comment
deleted file mode 100644
index 8e951ab7c..000000000
--- a/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_1_e26952373150d63b8a5d3643a2762de1._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-11-15T04:40:35Z"
- content="""
-git-annex uses locking to avoid problems if multiple processes are run at the same time.
-
-I just tested on NFS, with Linux on the server and client, and it works ok. It seems your NFS client (or server) must not support fncl locking. What OS is your NAS running?
-"""]]
diff --git a/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_2_f80b10ed395738e50e345fc22c708ae5._comment b/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_2_f80b10ed395738e50e345fc22c708ae5._comment
deleted file mode 100644
index bd302e6be..000000000
--- a/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_2_f80b10ed395738e50e345fc22c708ae5._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-11-15T04:46:13Z"
- content="""
-You might try mounting your NAS with the mount option `local_lock=all`
-
-This will keep the lock files on your (I assume linux) client. If you do this make sure you don't have another client using git-annex in the same NFS directory.
-"""]]
diff --git a/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_3_f99e0f05950fc2fc80fdecd35e17012c._comment b/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_3_f99e0f05950fc2fc80fdecd35e17012c._comment
deleted file mode 100644
index b95c795ea..000000000
--- a/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_3_f99e0f05950fc2fc80fdecd35e17012c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://cgray.myopenid.com/"
- nickname="cgray"
- subject="comment 3"
- date="2011-11-15T05:14:03Z"
- content="""
-I did a bit of research and my NAS had ancient NFS software on it.  I upgraded that and things are now working as expected. Sorry for the noise.
-"""]]
diff --git a/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_4_e42146d2dcc4052266dd61d204aeb551._comment b/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_4_e42146d2dcc4052266dd61d204aeb551._comment
deleted file mode 100644
index 59919789e..000000000
--- a/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_4_e42146d2dcc4052266dd61d204aeb551._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmnG4EuvZWse5hvgrl0XAK-U61e-0iGaao"
- nickname="David"
- subject="nolock option worked"
- date="2012-10-01T20:31:18Z"
- content="""
-I had the same problem on my NAS, updated the firmware but it didn't solve it.  The remedy was to mount the NAS with the 'nolock' option.
-"""]]
diff --git a/doc/bugs/True_backup_support.mdwn b/doc/bugs/True_backup_support.mdwn
deleted file mode 100644
index 72fd9fb1f..000000000
--- a/doc/bugs/True_backup_support.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-I'd like to be able to restore my data from S3/Glacier following a catastrophic loss of information.
-
-As I understand it, git-annex doesn't solve this problem for me because it only stores file *contents* in S3/Glacier.  A restore-from-nothing requires both the file contents and also the file names and metadata, which git-annex doesn't store in S3.
-
-I'm still feeling my way around git-annex, but I think it will probably be sufficient for my purposes to set up a cron job to push my annex to github.  But I think it would be helpful if git-annex could take care of this automatically.
-
-> Based on the comments, this is [[done]] --[[Joey]]
diff --git a/doc/bugs/True_backup_support/comment_1_50aa0bc1e2502622585682cb703e0b85._comment b/doc/bugs/True_backup_support/comment_1_50aa0bc1e2502622585682cb703e0b85._comment
deleted file mode 100644
index 33ad32eaa..000000000
--- a/doc/bugs/True_backup_support/comment_1_50aa0bc1e2502622585682cb703e0b85._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ"
- nickname="Walter"
- subject="I think this already works"
- date="2013-05-01T03:09:13Z"
- content="""
-I think this should already work in the latest git version, I have been using this feature for the last week or so.
-
-This change was described in [[/design/assistant/blog/day_245__misc/]], and I asked for it [[here|/forum/Automatically_syncronise_centralised_repository/]].
-"""]]
diff --git a/doc/bugs/True_backup_support/comment_2_d6030c6c49b227e022f05d590746d4ca._comment b/doc/bugs/True_backup_support/comment_2_d6030c6c49b227e022f05d590746d4ca._comment
deleted file mode 100644
index f8059d5a7..000000000
--- a/doc/bugs/True_backup_support/comment_2_d6030c6c49b227e022f05d590746d4ca._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c"
- nickname="Justin"
- subject="comment 2"
- date="2013-05-01T03:12:23Z"
- content="""
-Indeed, this looks like what I'm after.  Thanks!
-"""]]
diff --git a/doc/bugs/USB_drive_not_syncing.mdwn b/doc/bugs/USB_drive_not_syncing.mdwn
deleted file mode 100644
index c933222a5..000000000
--- a/doc/bugs/USB_drive_not_syncing.mdwn
+++ /dev/null
@@ -1,519 +0,0 @@
-### Please describe the problem.
-A USB drive could not be synced, whether as a client or transfer repository. The misbehaving part appears to be at this point in the logs:
-
-error: Ref refs/heads/synced/git-annex is at ff94266684335f9b152282fe620ef086e067afba but expected 0000000000000000000000000000000000000000
-
-"git annex get" also fails as shown in the (full) log message pasted below.
-
-### What steps will reproduce the problem?
-Not sure. Re-inserting the same drive gives the same problem. As the very first time using git annex (and not knowing git that well too), I need guidance in narrowing down this problem. If this bug has been fixed in the mean time, that is also fine.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20131106~bpo70+1
-build flags: Assistant Webapp Pairing Testsuite S3 Inotify DBus XMPP Feeds Quvi TDFA
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-remote types: git gcrypt S3 bup directory rsync web glacier hook
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-
-
-apg-get installed from Debian wheezy backports. uname -a gives:
-
-Linux im1 3.2.0-4-686-pae #1 SMP Debian 3.2.51-1 i686 GNU/Linux
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-[2014-01-05 21:01:40 CST] main: starting assistant version 4.20131106~bpo70+1
-[2014-01-05 21:01:40 CST] Cronner: You should enable consistency checking to protect your data. 
-(Recording state in git...)
-(scanning...) [2014-01-05 21:01:40 CST] Watcher: Performing startup scan
-(started...) [2014-01-05 21:03:56 CST] Committer: Adding README.txt cassandra-env.sh cassandra..roperties cassandra..roperties cassandra.yaml
-
-add conf/README.txt (checksum...) ok
-add conf/README.txt (checksum...) ok
-add conf/cassandra-env.sh (checksum...) ok
-add conf/cassandra-env.sh (checksum...) ok
-add conf/cassandra-rackdc.properties (checksum...) ok
-add conf/cassandra-rackdc.properties (checksum...) ok
-add conf/cassandra-topology.properties (checksum...) ok
-add conf/cassandra-topology.properties (checksum...) ok
-add conf/cassandra.yaml (checksum...) ok
-add conf/cassandra.yaml (checksum...) [2014-01-05 21:03:57 CST] Committer: Adding commitlog..roperties cqlshrc.sample log4j-ser..roperties log4j-too..roperties
-ok
-add conf/commitlog_archiving.properties (checksum...) ok
-add conf/commitlog_archiving.properties (checksum...) ok
-add conf/cqlshrc.sample (checksum...) ok
-add conf/cqlshrc.sample (checksum...) ok
-add conf/log4j-server.properties (checksum...) ok
-add conf/log4j-server.properties (checksum...) ok
-add conf/log4j-tools.properties (checksum...) ok
-add conf/log4j-tools.properties (checksum...) [2014-01-05 21:03:58 CST] Committer: Committing changes to git
-[2014-01-05 21:09:46 CST] Committer: Committing changes to git
-ok
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-Launching web browser on file:///home/tyc20/Desktop/annex/.git/annex/webapp.html
-[2014-01-05 21:11:46 CST] main: starting assistant version 4.20131106~bpo70+1
-[2014-01-05 21:11:46 CST] Cronner: You should enable consistency checking to protect your data. 
-(scanning...) [2014-01-05 21:11:46 CST] Watcher: Performing startup scan
-(started...) 
-(scanning...) [2014-01-05 21:13:17 CST] Watcher: Performing startup scan
-[2014-01-05 21:13:17 CST] Committer: Committing changes to git
-(Recording state in git...)
-(started...) [2014-01-05 21:13:18 CST] Committer: Committing changes to git
-[2014-01-05 21:16:19 CST] Committer: Adding cassandra.thrift
-
-(Recording state in git...)
-add conf/cassandra.thrift (checksum...) [2014-01-05 21:16:19 CST] Committer: Committing changes to git
-[2014-01-05 21:16:20 CST] Committer: Adding cassandra.thrift
-ok
-(Recording state in git...)
-(Recording state in git...)
-add conf/cassandra.thrift (checksum...) [2014-01-05 21:16:20 CST] Committer: Committing changes to git
-[2014-01-05 21:16:29 CST] Committer: Committing changes to git
-[2014-01-05 21:16:40 CST] Committer: Committing changes to git
-[2014-01-05 21:17:56 CST] Committer: Adding new-name.properties
-[2014-01-05 21:17:56 CST] Committer: Committing changes to git
-ok
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-ok
-(Recording state in git...)
-(Recording state in git...)
-
-  conf/Smalltalk-80 The language and its implementation (Bluebook).pdf still has writers, not adding
-
-  conf/Smalltalk-80 The language and its implementation (Bluebook).pdf still has writers, not adding
-[2014-01-05 21:27:34 CST] Committer: Committing changes to git
-[2014-01-05 21:28:09 CST] Committer: Adding The Essen..tions.pdf
-(Recording state in git...)
-(Recording state in git...)
-add conf/The Essence of Compiling with Continuations.pdf (checksum...) ok
-add conf/The Essence of Compiling with Continuations.pdf (checksum...) [2014-01-05 21:28:09 CST] Committer: Committing changes to git
-[2014-01-05 21:28:49 CST] Committer: Committing changes to git
-gpg: new configuration file \`/home/tyc20/.gnupg/gpg.conf\' created
-gpg: WARNING: options in \`/home/tyc20/.gnupg/gpg.conf\' are not yet active during this run
-ok
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-
-  Detected a crippled filesystem.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-[2014-01-05 21:35:09 CST] main: Syncing with ADATAUFD 
-warning: no common commits
-From /media/A-DATA UFD/annex
- * [new branch]      git-annex  -> ADATAUFD/git-annex
-[2014-01-05 21:35:09 CST] Pusher: Syncing with ADATAUFD 
-Already up-to-date.
-error: Ref refs/heads/synced/git-annex is at ff94266684335f9b152282fe620ef086e067afba but expected 0000000000000000000000000000000000000000
-error: Ref refs/heads/synced/master is at 745c01118e8684b4826f2fb53368faf0568fcafc but expected 0000000000000000000000000000000000000000
-remote: error: failed to lock refs/heads/synced/git-annex        
-To /media/A-DATA UFD/annex
- * [new branch]      git-annex -> synced/git-annex
- * [new branch]      master -> synced/master
-remote: error: failed to lock refs/heads/synced/master        
-To /media/A-DATA UFD/annex
- ! [remote rejected] git-annex -> synced/git-annex (failed to lock)
- ! [remote rejected] master -> synced/master (failed to lock)
-error: failed to push some refs to '/media/A-DATA UFD/annex'
-Already up-to-date.
-Everything up-to-date
-
-cassandra-rackdc.properties
-
-        1199 100%    0.00kB/s    0:00:00  
-        1199 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 1290 bytes  received 31 bytes  2642.00 bytes/sec
-total size is 1199  speedup is 0.91
-[2014-01-05 21:35:13 CST] Transferrer: Uploaded cassandra..roperties
-[2014-01-05 21:35:13 CST] Pusher: Syncing with ADATAUFD 
-
-cassandra-topology.properties
-
-        1358 100%    0.00kB/s    0:00:00  
-        1358 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 1451 bytes  received 31 bytes  2964.00 bytes/sec
-total size is 1358  speedup is 0.92
-[2014-01-05 21:35:13 CST] Transferrer: Uploaded cassandra..roperties
-
-cassandra.thrift
-
-       32768  93%    0.00kB/s    0:00:00  
-       35216 100%    2.33MB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 35300 bytes  received 31 bytes  70662.00 bytes/sec
-total size is 35216  speedup is 1.00
-[2014-01-05 21:35:14 CST] Transferrer: Uploaded cassandra.thrift
-
-commitlog_archiving.properties
-
-        2328 100%    0.00kB/s    0:00:00  
-        2328 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 2422 bytes  received 31 bytes  4906.00 bytes/sec
-total size is 2328  speedup is 0.95
-[2014-01-05 21:35:15 CST] Transferrer: Uploaded commitlog..roperties
-
-cqlshrc.sample
-
-        1324 100%    0.00kB/s    0:00:00  
-        1324 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 1402 bytes  received 31 bytes  2866.00 bytes/sec
-total size is 1324  speedup is 0.92
-[2014-01-05 21:35:15 CST] Transferrer: Uploaded cqlshrc.sample
-
-new-name.properties
-
-        1850 100%    0.00kB/s    0:00:00  
-        1850 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 1933 bytes  received 31 bytes  3928.00 bytes/sec
-total size is 1850  speedup is 0.94
-[2014-01-05 21:35:16 CST] Transferrer: Uploaded new-name.properties
-To /media/A-DATA UFD/annex
-   ff94266..d2dcc21  git-annex -> synced/git-annex
-[2014-01-05 21:35:19 CST] Pusher: Syncing with ADATAUFD 
-To /media/A-DATA UFD/annex
-   d2dcc21..c9f93f8  git-annex -> synced/git-annex
-[2014-01-05 21:42:39 CST] Committer: Adding Smalltalk..book).pdf
-(Recording state in git...)
-(merging ADATAUFD/git-annex into git-annex...)
-(Recording state in git...)
-
-
-(Recording state in git...)
-(Recording state in git...)
-add Smalltalk-80 The language and its implementation (Bluebook).pdf (checksum...) [2014-01-05 21:42:40 CST] Committer: Committing changes to git
-[2014-01-05 21:42:40 CST] Pusher: Syncing with ADATAUFD 
-
-Smalltalk-80 The language and its implementation (Bluebook).pdf
-
-       32768   0%    0.00kB/s    0:00:00  Already up-to-date.
-
-     8847360  26%    8.39MB/s    0:00:02  
-    21037056  62%   10.01MB/s    0:00:01  To /media/A-DATA UFD/annex
-   c9f93f8..1f1bfe9  git-annex -> synced/git-annex
-   745c011..6c6149b  master -> synced/master
-Already up-to-date.
-
-    31129600  92%    9.88MB/s    0:00:00  
-    33558574 100%    9.85MB/s    0:00:03 (xfer#1, to-check=0/1)
-[2014-01-05 21:42:45 CST] Pusher: Syncing with ADATAUFD 
-Everything up-to-date
-
-sent 33562798 bytes  received 31 bytes  3196459.90 bytes/sec
-total size is 33558574  speedup is 1.00
-[2014-01-05 21:42:51 CST] Transferrer: Uploaded Smalltalk..book).pdf
-[2014-01-05 21:42:51 CST] Pusher: Syncing with ADATAUFD 
-To /media/A-DATA UFD/annex
-   1f1bfe9..07ac8cf  git-annex -> synced/git-annex
-[2014-01-05 21:46:18 CST] main: Syncing with annex2 
-warning: no common commits
-From /home/tyc20/Desktop/annex2
- * [new branch]      git-annex  -> annex2/git-annex
- * [new branch]      master     -> annex2/master
-Already up-to-date!
-Merge made by the 'recursive' strategy.
-[2014-01-05 21:46:19 CST] Pusher: Syncing with annex2, ADATAUFD 
-Already up-to-date.
-To /home/tyc20/Desktop/annex2
- * [new branch]      git-annex -> synced/git-annex
- * [new branch]      master -> synced/master
-error: Ref refs/heads/synced/git-annex is at cf8e5160f57d8279770613851ee75fb6b7c1d381 but expected 0000000000000000000000000000000000000000
-remote: error: failed to lock refs/heads/synced/git-annex        
-error: Ref refs/heads/synced/master is at 8de8929c1e6712613f9e81faba88c2e464c809a7 but expected 0000000000000000000000000000000000000000
-remote: error: failed to lock refs/heads/synced/master        
-To /home/tyc20/Desktop/annex2
- ! [remote rejected] git-annex -> synced/git-annex (failed to lock)
- ! [remote rejected] master -> synced/master (failed to lock)
-error: failed to push some refs to '/home/tyc20/Desktop/annex2'
-Already up-to-date.
-[2014-01-05 21:46:20 CST] Transferrer: Uploaded Smalltalk..book).pdf
-ok
-(Recording state in git...)
-(Recording state in git...)
-
-
-(Recording state in git...)
-(Recording state in git...)
-(merging annex2/git-annex into git-annex...)
-(Recording state in git...)
-
-
-
-drop ADATAUFD Smalltalk-80 The language and its implementation (Bluebook).pdf [2014-01-05 21:46:20 CST] Transferrer: Uploaded cassandra..roperties
-ok
-drop ADATAUFD conf/cassandra-rackdc.properties [2014-01-05 21:46:21 CST] Transferrer: Uploaded cassandra..roperties
-ok
-drop ADATAUFD conf/cassandra-topology.properties To /media/A-DATA UFD/annex
-   07ac8cf..cf8e516  git-annex -> synced/git-annex
-   6c6149b..8de8929  master -> synced/master
-From /home/tyc20/Desktop/annex2
-   0f740b9..47ed905  git-annex  -> annex2/git-annex
-[2014-01-05 21:46:23 CST] Transferrer: Uploaded cassandra.thrift
-Already up-to-date.
-ok
-
-(merging annex2/git-annex into git-annex...)
-(Recording state in git...)
-drop ADATAUFD conf/cassandra.thrift To /home/tyc20/Desktop/annex2
-   cf8e516..859a06b  git-annex -> synced/git-annex
-[2014-01-05 21:46:25 CST] Transferrer: Uploaded commitlog..roperties
-ok
-drop ADATAUFD conf/commitlog_archiving.properties [2014-01-05 21:46:25 CST] Transferrer: Uploaded cqlshrc.sample
-ok
-drop ADATAUFD conf/cqlshrc.sample [2014-01-05 21:46:26 CST] Transferrer: Uploaded new-name.properties
-ok
-drop ADATAUFD conf/new-name.properties [2014-01-05 21:46:27 CST] Pusher: Syncing with annex2, ADATAUFD 
-To /home/tyc20/Desktop/annex2
-   859a06b..da020f9  git-annex -> synced/git-annex
-To /media/A-DATA UFD/annex
-   cf8e516..da020f9  git-annex -> synced/git-annex
-Updating 8de8929..2bfeaab
-Fast-forward
- conf/{new-name.properties => new-name2.properties} | 0
- 1 file changed, 0 insertions(+), 0 deletions(-)
- rename conf/{new-name.properties => new-name2.properties} (100%)
-[2014-01-05 21:47:23 CST] Committer: Committing changes to git
-[2014-01-05 21:47:23 CST] Pusher: Syncing with annex2, ADATAUFD 
-To /home/tyc20/Desktop/annex2
-   da020f9..1649bb6  git-annex -> synced/git-annex
-Already up-to-date.
-[2014-01-05 21:47:24 CST] Committer: Committing changes to git
-To /media/A-DATA UFD/annex
-   da020f9..1649bb6  git-annex -> synced/git-annex
-   8de8929..2bfeaab  master -> synced/master
-Already up-to-date.
-[2014-01-05 21:47:37 CST] Pusher: Syncing with annex2, ADATAUFD 
-Everything up-to-date
-Everything up-to-date
-
-Smalltalk-80 The language and its implementation (Bluebook).pdf
-
-       32768   0%    0.00kB/s    0:00:00  
-    10354688  30%    9.84MB/s    0:00:02  
-    20709376  61%    9.86MB/s    0:00:01  
-    29851648  88%    9.48MB/s    0:00:00  
-    33558574 100%    9.33MB/s    0:00:03 (xfer#1, to-check=0/1)
-
-sent 33562798 bytes  received 31 bytes  3532929.37 bytes/sec
-total size is 33558574  speedup is 1.00
-[2014-01-05 21:52:09 CST] Transferrer: Uploaded Smalltalk..book).pdf
-[2014-01-05 21:52:09 CST] Pusher: Syncing with annex2, ADATAUFD 
-
-cassandra-rackdc.properties
-
-        1199 100%    0.00kB/s    0:00:00  
-        1199 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 1290 bytes  received 31 bytes  2642.00 bytes/sec
-total size is 1199  speedup is 0.91
-To /home/tyc20/Desktop/annex2
-   1649bb6..7329695  git-annex -> synced/git-annex
-[2014-01-05 21:52:13 CST] Transferrer: Uploaded cassandra..roperties
-
-cassandra-topology.properties
-
-        1358 100%    0.00kB/s    0:00:00  
-        1358 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 1451 bytes  received 31 bytes  2964.00 bytes/sec
-total size is 1358  speedup is 0.92
-[2014-01-05 21:52:13 CST] Transferrer: Uploaded cassandra..roperties
-
-cassandra.thrift
-
-       32768  93%    0.00kB/s    0:00:00  
-       35216 100%    2.33MB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 35300 bytes  received 31 bytes  23554.00 bytes/sec
-total size is 35216  speedup is 1.00
-[2014-01-05 21:52:14 CST] Transferrer: Uploaded cassandra.thrift
-
-commitlog_archiving.properties
-
-        2328 100%    0.00kB/s    0:00:00  
-        2328 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 2422 bytes  received 31 bytes  4906.00 bytes/sec
-total size is 2328  speedup is 0.95
-[2014-01-05 21:52:15 CST] Transferrer: Uploaded commitlog..roperties
-
-cqlshrc.sample
-
-        1324 100%    0.00kB/s    0:00:00  
-        1324 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 1402 bytes  received 31 bytes  2866.00 bytes/sec
-total size is 1324  speedup is 0.92
-[2014-01-05 21:52:15 CST] Transferrer: Uploaded cqlshrc.sample
-
-new-name2.properties
-
-        1850 100%    0.00kB/s    0:00:00  
-        1850 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 1934 bytes  received 31 bytes  3930.00 bytes/sec
-total size is 1850  speedup is 0.94
-[2014-01-05 21:52:17 CST] Transferrer: Uploaded new-name2..roperties
-To /media/A-DATA UFD/annex
-   1649bb6..7329695  git-annex -> synced/git-annex
-[2014-01-05 21:52:21 CST] Pusher: Syncing with annex2, ADATAUFD 
-To /home/tyc20/Desktop/annex2
-   7329695..a7286da  git-annex -> synced/git-annex
-To /media/A-DATA UFD/annex
-   7329695..a7286da  git-annex -> synced/git-annex
-Updating 2bfeaab..40ceb79
-Fast-forward
- conf/commitlog_archiving.properties | 1 -
- 1 file changed, 1 deletion(-)
- delete mode 120000 conf/commitlog_archiving.properties
-[2014-01-05 21:55:05 CST] Pusher: Syncing with annex2 
-[2014-01-05 21:55:05 CST] Committer: Committing changes to git
-To /home/tyc20/Desktop/annex2
-   a7286da..688d27e  git-annex -> synced/git-annex
-Already up-to-date.
-[2014-01-05 21:55:07 CST] Pusher: Syncing with annex2 
-Everything up-to-date
-[2014-01-05 21:55:58 CST] MountWatcher: You should enable consistency checking to protect your data in ADATAUFD. 
-[2014-01-05 21:55:58 CST] MountWatcher: Syncing with ADATAUFD 
-To /media/A-DATA UFD/annex
-   a7286da..688d27e  git-annex -> synced/git-annex
-   2bfeaab..40ceb79  master -> synced/master
-Already up-to-date.
-
-
-
-
-In addition, this is what the drive looks like from the console.
-
-tyc20@im1:/media/A-DATA UFD/annex$ git annex get
-(merging synced/git-annex into git-annex...)
-(Recording state in git...)
-get SHA256E-s9400--8dce230c548a40fe9722ef1cf9444a54ae726a7420391a8eae937c8beaff6d96.sh (not available) 
-  No other repository is known to contain the file.
-failed
-get SHA256E-s1228--7e4190c2da12aa55c0f2598688d38723716bc11809ade1e594eae000ca40742c (not available) 
-  No other repository is known to contain the file.
-failed
-get SHA256E-s298--d60cff88544f63e6da177d98ef18a593268df6d4fcfd1247443ce3656cb185ba.txt (not available) 
-  No other repository is known to contain the file.
-failed
-get SHA256E-s26331--69bbae153239fa57b752bc931345275f36b608b26a3e9542ab4fabf21e05e57c.pdf (not available) 
-  No other repository is known to contain the file.
-failed
-get SHA256E-s31688--fea8690cf82baea3365ff692108742fdec308638bf6d66a8765bdc582e6ebb2c.yaml (not available) 
-  No other repository is known to contain the file.
-failed
-git-annex: get: 5 failed
-tyc20@im1:/media/A-DATA UFD/annex$ ls
-annex  branches  config  description  HEAD  hooks  info  objects  refs
-tyc20@im1:/media/A-DATA UFD/annex$ git annex sync
-commit  
-ok
-pull im1 
-From /home/tyc20/Desktop/annex
- * [new branch]      git-annex  -> im1/git-annex
- * [new branch]      master     -> im1/master
- * [new branch]      synced/git-annex -> im1/synced/git-annex
- * [new branch]      synced/master -> im1/synced/master
-ok
-push im1 
-Counting objects: 73, done.
-Delta compression using up to 2 threads.
-Compressing objects: 100% (17/17), done.
-Writing objects: 100% (24/24), 1.54 KiB | 0 bytes/s, done.
-Total 24 (delta 16), reused 0 (delta 0)
-To /home/tyc20/Desktop/annex
-   688d27e..2819176  git-annex -> synced/git-annex
-ok
-tyc20@im1:/media/A-DATA UFD/annex$ git annex sync
-commit  
-ok
-pull im1 
-remote: Counting objects: 10, done.
-remote: Compressing objects: 100% (4/4), done.
-remote: Total 5 (delta 3), reused 0 (delta 0)
-Unpacking objects: 100% (5/5), done.
-From /home/tyc20/Desktop/annex
-   688d27e..c28d1a4  git-annex  -> im1/git-annex
-   2819176..c28d1a4  synced/git-annex -> im1/synced/git-annex
-ok
-(merging im1/git-annex into git-annex...)
-tyc20@im1:/media/A-DATA UFD/annex$ git annex get
-get SHA256E-s9400--8dce230c548a40fe9722ef1cf9444a54ae726a7420391a8eae937c8beaff6d96.sh (not available) 
-  No other repository is known to contain the file.
-failed
-get SHA256E-s1228--7e4190c2da12aa55c0f2598688d38723716bc11809ade1e594eae000ca40742c (not available) 
-  No other repository is known to contain the file.
-failed
-get SHA256E-s298--d60cff88544f63e6da177d98ef18a593268df6d4fcfd1247443ce3656cb185ba.txt (not available) 
-  No other repository is known to contain the file.
-failed
-get SHA256E-s26331--69bbae153239fa57b752bc931345275f36b608b26a3e9542ab4fabf21e05e57c.pdf (not available) 
-  No other repository is known to contain the file.
-failed
-get SHA256E-s31688--fea8690cf82baea3365ff692108742fdec308638bf6d66a8765bdc582e6ebb2c.yaml (not available) 
-  No other repository is known to contain the file.
-failed
-git-annex: get: 5 failed
-tyc20@im1:/media/A-DATA UFD/annex$ mount -l
-sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
-proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
-udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=128012,mode=755)
-devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
-tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=103412k,mode=755)
-/dev/disk/by-uuid/25f084fb-c946-4c0d-bf0b-65ae4b68a7c6 on / type ext3 (rw,relatime,errors=remount-ro,barrier=1,data=ordered)
-tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
-tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=285260k)
-none on /mnt/share type vboxsf (rw,nodev,relatime)
-rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
-/dev/sr0 on /media/VBOXADDITIONS_4.3.6_91406 type iso9660 (ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500,uhelper=udisks) [VBOXADDITIONS_4.3.6_91406]
-/dev/sdb1 on /media/A-DATA UFD type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=cp437,iocharset=utf8,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks) [A-DATA UFD]
-
-
-tyc20@im1:/media/A-DATA UFD/annex$ ls -la ~/Desktop/annex/conf/
-total 60
-drwxr-xr-x 2 tyc20 tyc20  4096 Jan  5 21:55 .
-drwxr-xr-x 4 tyc20 tyc20  4096 Jan  5 21:42 ..
--rw-r--r-- 1 tyc20 tyc20  1199 Jul 28 09:14 cassandra-rackdc.properties
--rw-r--r-- 1 tyc20 tyc20 35216 Jul 28 09:14 cassandra.thrift
--rw-r--r-- 1 tyc20 tyc20  1358 Jul 28 09:14 cassandra-topology.properties
--rw-r--r-- 1 tyc20 tyc20  1324 Jul 28 09:14 cqlshrc.sample
--rw-r--r-- 1 tyc20 tyc20  1850 Jul 28 09:14 new-name2.properties
-tyc20@im1:/media/A-DATA UFD/annex$ ls -la ~/Desktop/annex/
-total 32828
-drwxr-xr-x 4 tyc20 tyc20     4096 Jan  5 21:42 .
-drwxr-xr-x 4 tyc20 tyc20     4096 Jan  5 21:45 ..
-drwxr-xr-x 2 tyc20 tyc20     4096 Jan  5 21:55 conf
-drwxr-xr-x 9 tyc20 tyc20     4096 Jan  5 22:01 .git
--rwxrwxrwx 1 tyc20 tyc20 33558574 Aug 27  2007 Smalltalk-80 The language and its implementation (Bluebook).pdf
-tyc20@im1:/media/A-DATA UFD/annex$ 
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; seems to be some badly set up repository. Happy to help with
-> fixing it, if you reply.. --[[Joey]]
diff --git a/doc/bugs/USB_drive_not_syncing/comment_1_de76bd6b9f8eb2489d4854a4c8ddd308._comment b/doc/bugs/USB_drive_not_syncing/comment_1_de76bd6b9f8eb2489d4854a4c8ddd308._comment
deleted file mode 100644
index afa3b3b6c..000000000
--- a/doc/bugs/USB_drive_not_syncing/comment_1_de76bd6b9f8eb2489d4854a4c8ddd308._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.35"
- subject="comment 1"
- date="2014-01-05T18:52:08Z"
- content="""
-You seem to have already had a regular bare git repository on the drive at `/media/A-DATA UFD/annex`, and then used the webapp or command line to make an encrypted gcrypt repository in the same location. This is the only way I can explain you being able to run \"git annex get in `/media/A-DATA UFD/annex` and it do anything at all, and it also explains the \"warning: no common commits\" and the failure to sync.
-
-So, you have some unholy mix of two different types of repositories in one location. The best way to untangle this is probably to go into the webapp and 
-in the settings menu next to that repository, choose Delete. This will get back the files that were stored in the gcrypt repository. (Or stop the assistant, and in `~/annex/` run `git annex get` to hopefully retrieve the files that it stored in the gcrypt repository, and then remove the gcrypt repository from .git/config).
-
-You may then need to edit `/media/A-DATA UFD/annex/config` to remove the gcrypt-id setting. At that point, it should be possible to use the webapp to add the removable drive, which will see the git repository on there and use it.
-
-I have re-tested that the webapp does not allow creating a gcrypt repository when a regular bare git repository already exists on a removable drive. IIRC there were some bugs in this area initially, but they've all been fixed for a while. It *is* possible to manually use `git annex initremote` at the command line to turn a regular bare git repository into a gcrypt repository. 
-"""]]
diff --git a/doc/bugs/Unable_to_copy_from_Android.mdwn b/doc/bugs/Unable_to_copy_from_Android.mdwn
deleted file mode 100644
index 405e227d6..000000000
--- a/doc/bugs/Unable_to_copy_from_Android.mdwn
+++ /dev/null
@@ -1,148 +0,0 @@
-### Please describe the problem.
-
-I am unable to copy files from my Android git annex repository into a remote repository on a Ubuntu machine.
-It was previously working fine, but after recent upgrades, it throws odd errors and refuses to copy the files.
-
-### What steps will reproduce the problem?
-
-Run this command:
-
-`git annex copy --to remote Path/To/File.txt`
-
-### What version of git-annex are you using? On what operating system?
-
-Souce Android Tablet
-
-[[!format sh """
-git-annex version: 5.20131221-gf8c928d  
-build flags: Assistant Webapp Testsuite S3 WebDAV Inotify XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-local repository version: 5
-default repository version: 3
-supported repository versions: 3 5
-upgrade supported from repository versions: 0 1 2 4
-"""]]
-
-Destination Ubuntu server
-
-[[!format sh """
-git-annex version: 5.20131224-g692aa01
-build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-"""]]
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-git annex copy --to gimli Books/Laravel/laravel.mobi
-copy Books/Laravel/laravel.mobi (checking gimli...) git-annex: Not in a git repository.
-(to gimli...) git-annex: unknown command recvkey
-
-Usage: git-annex command [option ...]
-
-Commonly used commands:
-
-add          [PATH ...]      add files to annex
-addurl       URL ...         add urls to annex
-assistant                    automatically handle changes
-copy         [PATH ...]      copy content of files to/from another repository
-drop         [PATH ...]      indicate content of files not currently wanted
-edit         [PATH ...]      same as unlock
-get          [PATH ...]      make content of annexed files available
-import       [PATH ...]      move and add files from outside git working copy
-importfeed   URL ...         import files from podcast feeds
-lock         [PATH ...]      undo unlock command
-mirror       [PATH ...]      mirror content of files to/from another repository
-move         [PATH ...]      move content of files to/from another repository
-rmurl        FILE URL        record file is not available at url
-status       [PATH ...]      show the working tree status
-sync         [REMOTE ...]    synchronize local repository with remotes
-unlock       [PATH ...]      unlock files for modification
-watch                        watch for changes
-webapp                       launch webapp
-
-Repository setup commands:
-
-dead         REMOTE ...      hide a lost repository
-describe     REMOTE DESC     change description of a repository
-direct                       switch repository to direct mode
-enableremote NAME [K=V ...]  enables use of an existing special remote
-group        REMOTE DESC     add a repository to a group
-indirect                     switch repository to indirect mode
-init         DESC            initialize git-annex
-initremote   NAME [K=V ...]  creates a special (non-git) remote
-schedule     REMOTE [EXPR]   get or set scheduled jobs
-semitrust    REMOTE ...      return repository to default trust level
-trust        REMOTE ...      trust a repository
-ungroup      REMOTE DESC     remove a repository from a group
-untrust      REMOTE ...      do not trust a repository
-vicfg                        edit git-annex's configuration
-wanted       REMOTE [EXPR]   get or set preferred content expression
-
-Repository maintenance commands:
-
-addunused    NUM|RANGE ...   add back unused files
-dropunused   NUM|RANGE ...   drop unused file content
-fix          [PATH ...]      fix up symlinks to point to annexed content
-forget                       prune git-annex branch history
-fsck         [PATH ...]      check for problems
-merge                        automatically merge changes from remotes
-repair                       recover broken git repository
-unused                       look for unused file content
-upgrade                      upgrade repository layout
-
-Query commands:
-
-find         [PATH ...]      lists available files
-help                         display help
-info         [PATH ...]      shows general information about the annex
-list         [PATH ...]      show which remotes contain files
-log          [PATH ...]      shows location log
-map                          generate map of repositories
-version                      show version info
-whereis      [PATH ...]      lists repositories that have file content
-
-Utility commands:
-
-migrate      [PATH ...]      switch data to different backend
-reinject     SRC DEST        sets content of annexed file
-unannex      [PATH ...]      undo accidential add command
-uninit       [PATH ...]      de-initialize git-annex and clean out repository
-
-Plumbing commands:
-
-dropkey      KEY ...         drops annexed content for specified keys
-examinekey   KEY ...         prints information from a key
-fromkey      KEY PATH        adds a file using a specific key
-lookupkey    FILE ...        looks up key used for file
-pre-commit   [PATH ...]      run by git pre-commit hook
-rekey        [PATH KEY ...]  change keys used for files
-transferkey  KEY             transfers a key from or to a remote
-transferkeys                 transfers keys
-xmppgit                      git to XMPP relay
-
-rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-rsync error: error in rsync protocol data stream (code 12) at io.c(224) [sender=3.1.0dev]
-
-
-rsync failed -- run git annex again to resume file transfer
-failed
-git-annex: copy: 1 failed
-
-# End of transcript or log.
-"""]]
-
-> There was a bug in the linux standalone tarball distributed
-> with 5.20131221 that made the `git-annex-shell` wrapper accidentially run
-> `git-annex` instead of `git-annex-shell`. Which results in 
-> this error about recvkey, which is a git-annex-shell command, not a
-> git-annex command.
-> 
-> I think your ubuntu system must have git-annex installed from that tarball.
-> This bug is fixed in the daily builds, and I have updated the
-> tarballs for the release too, now. [[done]] --[[Joey]]
diff --git a/doc/bugs/Unable_to_copy_from_Android/comment_1_3bb70c44b6b8d451687591fcab5c1506._comment b/doc/bugs/Unable_to_copy_from_Android/comment_1_3bb70c44b6b8d451687591fcab5c1506._comment
deleted file mode 100644
index 44e8beed6..000000000
--- a/doc/bugs/Unable_to_copy_from_Android/comment_1_3bb70c44b6b8d451687591fcab5c1506._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://id.clacke.se/"
- nickname="clacke"
- subject="dup"
- date="2013-12-27T04:18:16Z"
- content="""
-Looks like a duplicate of [[android_cannot_get_from_5.20131221]].
-"""]]
diff --git a/doc/bugs/Unable_to_import_feed.mdwn b/doc/bugs/Unable_to_import_feed.mdwn
deleted file mode 100644
index 49dc21bfe..000000000
--- a/doc/bugs/Unable_to_import_feed.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-Using `git-annex version: 4.20130802` on Debian unstable, when trying to add the feed at <http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml>, I get:
-
-[[!format sh """
-importfeed http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml 
---2013-08-16 09:14:13--  http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml
-Auflösen des Hostnamen »www.ndr.de (www.ndr.de)«... 212.201.100.171, 212.201.100.187
-Verbindungsaufbau zu www.ndr.de (www.ndr.de)|212.201.100.171|:80... verbunden.
-HTTP-Anforderung gesendet, warte auf Antwort... 200 OK
-Länge: 61809 (60K) [application/xml]
-In »»/tmp/feed4404«« speichern.
-
-100%[============================================>] 61.809      --.-K/s   in 0,03s   
-
-2013-08-16 09:14:13 (2,20 MB/s) - »»/tmp/feed4404«« gespeichert [61809/61809]
-
-failed
-git-annex: importfeed: 1 failed
-"""]]
-
-(Oh, and using `format` with nono-ASCII seems to break down., at least in the preview.)
-
-> I'm going to close this since I've narrowed it down to a bug in the
-> upstream feed library. [[done]]. Of course, if we get a lot of reports of
-> the library not working, I may need to revisit using it, but for now this
-> seems an isolated problem. Also, I tried validating the feed, and it is
-> not 100% valid, and one of the validity problems is a missing enclosure
-> length. --[[Joey]] 
diff --git a/doc/bugs/Unable_to_import_feed/comment_1_16230fbbb996e165b84787ed4d5f72ea._comment b/doc/bugs/Unable_to_import_feed/comment_1_16230fbbb996e165b84787ed4d5f72ea._comment
deleted file mode 100644
index 7c9c1e129..000000000
--- a/doc/bugs/Unable_to_import_feed/comment_1_16230fbbb996e165b84787ed4d5f72ea._comment
+++ /dev/null
@@ -1,45 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 1"
- date="2013-08-23T18:09:27Z"
- content="""
-When I try this, without the German translation, I get:
-
-<pre>
-joey@gnu:~/tmp/newrepo>git annex importfeed 'http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml'
-(checking known urls...)
-importfeed http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml 
---2013-08-23 13:58:19--  http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml
-Resolving www.ndr.de (www.ndr.de)... 23.73.180.154, 23.73.180.115
-Connecting to www.ndr.de (www.ndr.de)|23.73.180.154|:80... connected.
-HTTP request sent, awaiting response... 200 OK
-Length: 61865 (60K) [application/xml]
-Saving to: ‘/home/joey/tmp/feed31120’
-
-100%[======================================>] 61,865       151KB/s   in 0.4s   
-
-2013-08-23 13:58:25 (151 KB/s) - ‘/home/joey/tmp/feed31120’ saved [61865/61865]
-
-
-  warning: bad feed content
-</pre>
-
-It seems you left out the last line of the error.
-
-The feed library seems to fail to find any of the enclosures in this feed, although it is able to parse it as far as finding the individual items in the feed:
-
-<pre>
-Prelude Text.Feed.Query Text.Feed.Import> f <- parseFeedFromFile \"extradrei196_version-hq.xml\" 
-Prelude Text.Feed.Query Text.Feed.Import> map getItemEnclosure $ feedItems f
-[Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing]
-</pre>
-
-The feed *appears* to contain enclosures, for example:
-
-<pre>
-<enclosure url=\"http://media.ndr.de/progressive/2013/0821/TV-20130821-2329-5942.hq.mp4\" type=\"video/mp4\"/>
-</pre>
-
-It may not be well-formed, or the feed library may have a bug. Assuming the latter, I have filed a bug report on the feed library: https://github.com/sof/feed/issues/3
-"""]]
diff --git a/doc/bugs/Unable_to_switch_back_to_direct_mode.mdwn b/doc/bugs/Unable_to_switch_back_to_direct_mode.mdwn
deleted file mode 100644
index 8144dfe4d..000000000
--- a/doc/bugs/Unable_to_switch_back_to_direct_mode.mdwn
+++ /dev/null
@@ -1,55 +0,0 @@
-### Please describe the problem.
-
-I seem to be unable to switch back and forth between git annex direct and git annex indirect mode in one of my repositories.  I can in others just fine.
-
-### What steps will reproduce the problem?
-
-In the broken repository I can do:
-
-    cwebber@earlgrey:~/gfx-proj/mediagoblin_vid$ git annex direct
-    commit  
-    add audio/part2.aup (checksum...) ok
-    ok
-    add images/campaign.png (checksum...) ok
-    ok
-    add images/transifex.png (checksum...) ok
-    ok
-    add script-lines.txt (checksum...) ok
-    ok
-    add vid_pitch.blend (checksum...) ok
-    ok
-    (Recording state in git...)
-    [master 9f13dc0] commit before switching to direct mode
-     1 file changed, 145 insertions(+), 1 deletion(-)
-     rewrite audio/part2.aup (100%)
-     mode change 120000 => 100644
-    ok
-    direct gavroche-vid-shot.blend 
-    git-annex: /home/cwebber/gfx-proj/mediagoblin_vid/.git/annex/objects/3M/mx/SHA256E-s2935980--3a1c838333a4a0ee1eaa837c3f08a910d3f29fc60baf41affd936fbefe11111f/SHA256E-s2935980--3a1c838333a4a0ee1eaa837c3f08a910d3f29fc60baf41affd936fbefe11111f: rename: permission denied (Permission denied)
-    failed
-    git-annex: direct: 1 failed
-
-looking at the files:
-
-    cwebber@earlgrey:~/gfx-proj/mediagoblin_vid$ ls -l gavroche-vid-shot.blend
-    lrwxrwxrwx 1 cwebber cwebber 190 Apr 28 18:27 gavroche-vid-shot.blend -> .git/annex/objects/3M/mx/SHA256E-s2935980--3a1c838333a4a0ee1eaa837c3f08a910d3f29fc60baf41affd936fbefe11111f/SHA256E-s2935980--3a1c838333a4a0ee1eaa837c3f08a910d3f29fc60baf41affd936fbefe11111f
-    cwebber@earlgrey:~/gfx-proj/mediagoblin_vid$ ls -l .git/annex/objects/3M/mx/SHA256E-s2935980--3a1c838333a4a0ee1eaa837c3f08a910d3f29fc60baf41affd936fbefe11111f/SHA256E-s2935980--3a1c838333a4a0ee1eaa837c3f08a910d3f29fc60baf41affd936fbefe11111f
-    -rw-r--r-- 1 cwebber cwebber 2935980 Apr 28 18:27 .git/annex/objects/3M/mx/SHA256E-s2935980--3a1c838333a4a0ee1eaa837c3f08a910d3f29fc60baf41affd936fbefe11111f/SHA256E-s2935980--3a1c838333a4a0ee1eaa837c3f08a910d3f29fc60baf41affd936fbefe11111f
-    cwebber@earlgrey:~/gfx-proj/mediagoblin_vid$
-
-... it looks like these permissions should be fine!
-
-Some notable things:
-
-* I believe Blender wrote directly to a file that was in "locked" somehow, despite it being in that state.  It may have actually followed the symlink and overwritten that file, I'm not sure.
-* However, the file that git-annex is now reporting with "permission denied" is not the one it did previously... I did git checkout -- on all the files, switched them over, and it's a different set of broken things now!
-* It's actually easy enough to fix... in fact, I did fix it!  I just did a fresh clone of the git repository and a git annex get and everything is fine now.  However, it seemed like possibly a bug that might hit other people, hence my reporting it.
-
-### What version of git-annex are you using? On what operating system?
-
-git annex version 4.20130417 on debian wheezy
-
-### Please provide any additional information below.
-
-
-> [[done]]; see comments. --[[Joey]]
diff --git a/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_1_4585b251f011a153c62f377c324cf963._comment b/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_1_4585b251f011a153c62f377c324cf963._comment
deleted file mode 100644
index 6ba0111a7..000000000
--- a/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_1_4585b251f011a153c62f377c324cf963._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q"
- nickname="Andrew"
- subject="comment 1"
- date="2013-04-30T02:31:31Z"
- content="""
-I've had the same thing happen in reverse. I can not switch from direct to indirect mode. After receiving a similar error:
-
-    git-annex: /Users/akraut/Desktop/annexes/home/.git/annex/objects/ZV/kq/SHA256E-s207--4b4fa180ac4c16fe83eb2a5fed4c217c1d26195c876a4e0e700ae63605348d75.mp3/SHA256E-s207--4b4fa180ac4c16fe83eb2a5fed4c217c1d26195c876a4e0e700ae63605348d75.mp3.cache: removeLink: permission denied (Permission denied)
-    failed
-    git-annex: indirect: 1 failed
-    
-    %  > ls -la /Users/akraut/Desktop/annexes/home/.git/annex/objects/ZV/kq/SHA256E-s207--4b4fa180ac4c16fe83eb2a5fed4c217c1d26195c876a4e0e700ae63605348d75.mp3/SHA256E-s207--4b4fa180ac4c16fe83eb2a5fed4c217c1d26195c876a4e0e700ae63605348d75.mp3.cache
-    -rw-r--r-- 1 akraut staff 23 Mar 23 21:10 /Users/akraut/Desktop/annexes/home/.git/annex/objects/ZV/kq/SHA256E-s207--4b4fa180ac4c16fe83eb2a5fed4c217c1d26195c876a4e0e700ae63605348d75.mp3/SHA256E-s207--4b4fa180ac4c16fe83eb2a5fed4c217c1d26195c876a4e0e700ae63605348d75.mp3.cache
-
-After this error, annex things I'm in indirect mode:
-
-    %  > git annex status
-    supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-    supported remote types: git S3 bup directory rsync web webdav glacier hook
-    repository mode: indirect
-
-And git things that my repo has many uncommitted typechanges.
-"""]]
diff --git a/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_2_5848ebbab38d1244347f7e7351b3a30d._comment b/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_2_5848ebbab38d1244347f7e7351b3a30d._comment
deleted file mode 100644
index 2b13674a7..000000000
--- a/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_2_5848ebbab38d1244347f7e7351b3a30d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-04-30T23:36:12Z"
- content="""
-@andrew I've reproduced and fixed this problem. It does not seem to be related to cwebber's problem.
-
-Waiting on a test case from cwebber. His permissions seem ok, so I don't know what's causing that.
-"""]]
diff --git a/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_3_1c5c7b0c7bc336e00f43e257b87a6208._comment b/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_3_1c5c7b0c7bc336e00f43e257b87a6208._comment
deleted file mode 100644
index b23697942..000000000
--- a/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_3_1c5c7b0c7bc336e00f43e257b87a6208._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q"
- nickname="Andrew"
- subject="comment 3"
- date="2013-04-30T23:38:52Z"
- content="""
-Ah, cool. What's the recommended way to recover from it?
-"""]]
diff --git a/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_4_b0bfd68998bc3e11d8e089646b8292a6._comment b/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_4_b0bfd68998bc3e11d8e089646b8292a6._comment
deleted file mode 100644
index af406b1d2..000000000
--- a/doc/bugs/Unable_to_switch_back_to_direct_mode/comment_4_b0bfd68998bc3e11d8e089646b8292a6._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 4"
- date="2013-05-06T16:41:42Z"
- content="""
-cwebber sent me a test case, and it turns out that while his problem was different, I fixed it in the same commit I fixed the problem described in the comment above. Both problems involved cases where the object storage directory was left with frozen permissions, and they needed to be unlocked before moving files in/out of it.
-
-Also, it seems that blender did not misbehave as thought. It only replaces the git-annex symlink with a new .blend file. Which is fine.
-
-Finally, there was an unrelated bug in `git annex direct` that chris's test case repo happened to have, which caused it to not convert 2 files to direct mode. I've fixed that bug as well.
-"""]]
diff --git a/doc/bugs/Unable_to_sync_a_second_machine_through_Box.mdwn b/doc/bugs/Unable_to_sync_a_second_machine_through_Box.mdwn
deleted file mode 100644
index a4cac6ace..000000000
--- a/doc/bugs/Unable_to_sync_a_second_machine_through_Box.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-What steps will reproduce the problem?
-
-Install 4.20130417 as packaged in Debian unstable.
-Using "git annex webapp", setup on first machine adding repository ~/annex.  Add a Box.com repository in directory "annex", encrypted.  Add a jabber account (apparently successful).
-Add test file to ~/annex.  Login via website to box.com, notice that the "annex" directory is created and contains encrypted file.
-On second (remote machine), follow the same steps (add repository in ~/annex, Add a Box.com repository in directory "annex", encrypted, Add same jabber account).
-
-What is the expected output? What do you see instead?
-
-Expected the file to appear in the second machine's ~/annex.  The webapp indicates: Synced with box.com
-Log file says:
-
-[2013-04-23 06:50:16 EDT] main: starting assistant version 4.20130417
-(scanning...) [2013-04-23 06:50:16 EDT] Watcher: Performing startup scan
-(started...) 
-(encryption setup shared cipher) (testing WebDAV server...)
-(gpg) [2013-04-23 06:50:50 EDT] main: Syncing with box.com 
-[2013-04-23 06:50:50 EDT] main: Share with friends, and keep your devices in sync across the cloud. 
-[2013-04-23 06:51:03 EDT] main: Share with friends, and keep your devices in sync across the cloud. 
-warning: Not updating non-default fetch respec
-	
-	Please update the configuration manually if necessary.
-Initializing nautilus-gdu extension
-Shutting down nautilus-gdu extension
-git-annex: Daemon is already running.
-
-What version of git-annex are you using? On what operating system?
-
-4.20130417, debian testing with apt-pinning to unstable on both systems.
-
-Please provide any additional information below.
-
-When editing the Box.com repository, the option to select a directory no longer appears (and the configuration doesn't show the one selected at creation).
-There's no indication if the jabber communication is working successfully.  It could be that signalling isn't working for some reason, but the user has no information to determine that.
-It would be helpful if there were some indication in the Dashboard as to the number of files/directories/objects that git annex believes exists in each location.  It could be that it's not accessing the Box.com server successfully, but again, this is difficult to determine.
-
-It's great to see that git annex might make a box.com account useful for automatic upload and sync... looking forward to getting it to work on both sides! Thanks for making this!
-
-[[!tag /design/assistant moreinfo]]
-
-> The robustness of the XMPP support has massively improved since this bug
-> report was filed. Since no more information is forthcoming, I consider
-> this bug [[done]].
->
-> (Incidentially, this bug got me to santize all information logged about
-> XMPP protocol, including the names/emails of buddies..) --[[Joey]]
diff --git a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_1_cb43a2bc976e3eb1cfc3ee9d4d34e78e._comment b/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_1_cb43a2bc976e3eb1cfc3ee9d4d34e78e._comment
deleted file mode 100644
index ae117f36f..000000000
--- a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_1_cb43a2bc976e3eb1cfc3ee9d4d34e78e._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-23T17:54:14Z"
- content="""
-Are files that you add in machine A showing up in machine B as broken symlinks? If so, jabber sync is working and the problem is with the Box.com remore. If not, the problem must be with the jabber sync.
-
-The log includes something like this when git is pulling over jabber:
-
-<pre>
-[2013-04-22 14:08:05 JEST] XMPPClient: Syncing with youraccount
-To xmpp::youraccount@gmail.com
-   385f85c..3aae8b7  git-annex -> refs/synced/8ff0aa10-0a9d-4184-b16f-27b32ef87372/ZmFtaWx5QGtpdGVuZXQubmV0/git-annex
-</pre>
-
-You can turn on debugging (--debug at startup or Enable debug logging in Configuration -> Preferences) to get full XMPP protocol dumps in the log. If you do not see something like the above, please do so, and paste them, so I can debug why it's not working.
-
-> When editing the Box.com repository, the option to select a directory no longer appears
-
-This is normal; it doesn't make sense to change the directory the remote uses once the remote is in use.
-"""]]
diff --git a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_2_3375e9bfab3fed271413bd9bb5fa0121._comment b/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_2_3375e9bfab3fed271413bd9bb5fa0121._comment
deleted file mode 100644
index f3a39ef2f..000000000
--- a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_2_3375e9bfab3fed271413bd9bb5fa0121._comment
+++ /dev/null
@@ -1,30 +0,0 @@
-[[!comment format=mdwn
- username="http://keverets.livejournal.com/"
- ip="108.170.138.61"
- subject="comment 2"
- date="2013-04-23T19:04:15Z"
- content="""
-I do see XMPP connecting after I enable logging (could the XMPP status be shown in the webapp directly?)
-
-It shows long, long lists of PresenceMessages:
-
-    [2013-04-23 14:55:56 EDT] XMPPClient: connected JID \"...\"
-    [2013-04-23 14:55:56 EDT] XMPPClient: received: [PresenceMessage (Presence {presenceType = PresenceAvailable, presenceTo = Just (JID ...
-
-Still no files gets transferred from Box.com to the second machine.  I see:
-
-    [2013-04-23 14:53:41 EDT] main: Syncing with box.com
-
-but no:
-
-    XMPPClient: Syncing
-
-anywhere in the log.
-
->> When editing the Box.com repository, the option to select a directory no longer appears
-> This is normal; it doesn't make sense to change the directory the remote uses once the remote is in use.
-
-It might not make sense to change it, but it would be useful to still see it (if disabled), especially when there are a few different Box.com directories that are shared with different repositories.
-
-Thanks again for any hints.
-"""]]
diff --git a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_3_c4420e1a3db321b4135b1626d3582adb._comment b/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_3_c4420e1a3db321b4135b1626d3582adb._comment
deleted file mode 100644
index 1b66d12e9..000000000
--- a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_3_c4420e1a3db321b4135b1626d3582adb._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="I am not a horse"
- date="2013-04-23T20:05:25Z"
- content="""
-A horse, when put in harness, is equipped with blinders, to prevent it from seeing scary things out of the corner of its eye, and panicing.
-
-I am not a horse. The more information I am presented with, the more likely I am to see and understand and fix a problem. ;)
-
-So, please paste the whole XMPP output, not 2 edited lines of it.
-"""]]
diff --git a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_4_f4b2c88bb5938dacdd04dfe9a68560de._comment b/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_4_f4b2c88bb5938dacdd04dfe9a68560de._comment
deleted file mode 100644
index 32ceea2c0..000000000
--- a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_4_f4b2c88bb5938dacdd04dfe9a68560de._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://keverets.livejournal.com/"
- ip="108.170.138.61"
- subject="Your users aren't horses, either"
- date="2013-04-24T23:42:45Z"
- content="""
-I appreciate the difficulty in responding to bug reports with incomplete logs.
-
-Please consider that the log file includes lists of email addresses (as XMPP contacts in the Presence messages) that are those of my contacts and not my own.  In addition, these bug reports seem to be posted publicly in this wiki.  As such, providing some other means of submitting logs would likely be a good idea (ideally from inside the webapp where they're being collected, so the user is less likely to miss some with a copy & paste through the browser; they should be sent to a more private destination such as an email address).
-
-I really do not want to be bothering you with bug reports if I could gather the information I need to solve the issue myself.  That's why I suggested adding better notification in the webapp of the status of XMPP (there's just a brief \"Testing, this might take a minute\" message, and then never any indication afterwards as to the state), along with better information about the status of each repository as git annex sees them.  If it's something that's tripping me up, and I'm willing to jump through the hoops (perhaps I am a horse) of hunting down and dealing with the bug reporting system, then there are likely others who will have the same issue but just give up.
-
-We're both left trying to sort out the problem partially blind, which is about as much fun for me as it is for you.
-
-I see a few ways to reduce the effort on both sides going forward.  One (my preferred) is to give the users more information in the webapp as to what's going on with the sync so that the user can determine if it's the local git annex, the remote shared repository, the remote system, or the signalling in between.  Another is to provide a more private means of submitting complete log data to help get quickly to the root of the problem without greatly compromising user's (and their contacts') privacy.  And the last (my least preferred) is that you respond to bug reports in the manner above, resulting in the alienation of those who are trying to help, who are interested in what you're doing and trying to aid in improving the project so that it will be useful and pleasant-to-use for all.  In doing so I'm fairly certain you'll get many fewer bug reports.
-
-That last one seems like less effort, but I really would prefer one of the two former solutions.
-"""]]
diff --git a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_5_6dcc95ffb3fc7bbbedd6be5df0111c85._comment b/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_5_6dcc95ffb3fc7bbbedd6be5df0111c85._comment
deleted file mode 100644
index 5919a7206..000000000
--- a/doc/bugs/Unable_to_sync_a_second_machine_through_Box/comment_5_6dcc95ffb3fc7bbbedd6be5df0111c85._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-04-24T23:46:11Z"
- content="""
-<mailto:id@joeyh.name>
-"""]]
diff --git a/doc/bugs/Unable_to_use_remotes_with_space_in_the_path.mdwn b/doc/bugs/Unable_to_use_remotes_with_space_in_the_path.mdwn
deleted file mode 100644
index 6bb6c0782..000000000
--- a/doc/bugs/Unable_to_use_remotes_with_space_in_the_path.mdwn
+++ /dev/null
@@ -1,35 +0,0 @@
-### Please describe the problem.
-
-Git annex can't use remotes with the type "file://" if the path contains spaces
-
-### What steps will reproduce the problem?
-
-- Create one repository with a space in the path (and initialize annex in it)
-- Clone that repo to an other directory (and initialize annex also in that)
-- add a file to the first repository in the annex way
-- chdir to the second repository and try to get that file, it won't work (also after git pull or git sync pull)
-
-Check this typescripts for a more detailed description
-
-<http://uz.sns.it/~enrico/git-annex-bugreport.txt>
-
-<http://pastebin.com/f8wkDNrG> (thanks mhameed for that data)
-
-
-### What version of git-annex are you using? On what operating system?
-
-I'm using debian testing (jessie) on a i386 machine.
-
-`git-annex` version: 4.20130521 (according to apt data and `git annex version`)
-
-`git-annex` build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-
-`git` version: 1.7.10.4
-
-
-### Please provide any additional information below.
-
-I don't use git annex assistant nor the webapp
-
-> Tested and only file:// and not other urls have this problem.
-> guilhem provided a fix. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Unfortunate_interaction_with_Calibre.mdwn b/doc/bugs/Unfortunate_interaction_with_Calibre.mdwn
deleted file mode 100644
index 16921a06e..000000000
--- a/doc/bugs/Unfortunate_interaction_with_Calibre.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-# Calibre 
-
-Calibre is a somewhat popular eBook management package that's also free software.  <http://calibre-ebook.com/>  
-
-Install via
-    # apt-get install calibre
-
-There is a somewhat unfortunate interaction between Calibre and git-annex...
-
-* git-annex makes its files become read-only.  By the way, that's not quite obvious from the documentation; I suggest making that more prominent.
-* Calibre modifies files (not quite sure of semantics, how, or why) when doing various operations, notably such as when copying a book from one's library to one's portable reading device.
-
-These don't play well together, sadly.
-
-I'd expect most of the issue to sit on the Calibre side, and have reported it as a bug.
-[Calibre bug #739045](https://bugs.launchpad.net/calibre/+bug/739045)
-Preliminary indication is that they're treating it as a functionality change they'll decline to fix.  Which isn't entirely unreasonable - I anticipated as much, and I don't want to treat that as a bad/wrong decision.
-
-However, I think it's:
-* Unfortunate, as fitting Calibre together with git-annex seems like a neat idea.
-* Useful to make sure that this kind of "doesn't play well together" condition is documented, even if only as a bug report.
-
-> [[done]]; the assistant uses direct mode by default now to avoid
-> this kind of thing. --[[Joey]] 
diff --git a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_1_7cb5561f11dfc7726a537ddde2477489._comment b/doc/bugs/Unfortunate_interaction_with_Calibre/comment_1_7cb5561f11dfc7726a537ddde2477489._comment
deleted file mode 100644
index 35a2cdb3f..000000000
--- a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_1_7cb5561f11dfc7726a537ddde2477489._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-03-21T13:15:03Z"
- content="""
-Maybe I will run into issues myself somewhere down the road, but generally speaking, I really really like the fact that files are immutable by default.
-"""]]
diff --git a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_2_b8ae4bc589c787dacc08ab2ee5491d6e._comment b/doc/bugs/Unfortunate_interaction_with_Calibre/comment_2_b8ae4bc589c787dacc08ab2ee5491d6e._comment
deleted file mode 100644
index 719451976..000000000
--- a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_2_b8ae4bc589c787dacc08ab2ee5491d6e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-03-31T19:32:25Z"
- content="""
-One option would be to use the new [[news/sharebox_a_FUSE_filesystem_for_git-annex]], which would hide the immutable file details from Calibre, and proxy any changes it made through to git-annex as a series of `git annex unlock; modify; git-annex lock`
-"""]]
diff --git a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_3_977c5f6b82f9e18cdd81d57005bb8b89._comment b/doc/bugs/Unfortunate_interaction_with_Calibre/comment_3_977c5f6b82f9e18cdd81d57005bb8b89._comment
deleted file mode 100644
index e23490ac4..000000000
--- a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_3_977c5f6b82f9e18cdd81d57005bb8b89._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 3"
- date="2013-01-17T20:59:03Z"
- content="""
-I'd say that the best option now is to use [[direct_mode]] for repositories with files that you want to let programs modify directly.
-"""]]
diff --git a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_4_ff7d2e9a39dfe12b975d04650ac57cc4._comment b/doc/bugs/Unfortunate_interaction_with_Calibre/comment_4_ff7d2e9a39dfe12b975d04650ac57cc4._comment
deleted file mode 100644
index 750ba8474..000000000
--- a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_4_ff7d2e9a39dfe12b975d04650ac57cc4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkvSZ1AFJdY_1FeutZr_KWeqtzjZta1PNE"
- nickname="Thedward"
- subject="comment 4"
- date="2013-01-18T16:30:59Z"
- content="""
-I couldn't get calibre to work with sharebox either, but I can confirm it works fine when I use git-annex in direct mode.
-"""]]
diff --git a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_5_fc4d5301797589e92cc9a24697b2155d._comment b/doc/bugs/Unfortunate_interaction_with_Calibre/comment_5_fc4d5301797589e92cc9a24697b2155d._comment
deleted file mode 100644
index a54d53c58..000000000
--- a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_5_fc4d5301797589e92cc9a24697b2155d._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://lot-of-stuff.info/"
- nickname="__DL__"
- subject="Another solution."
- date="2013-08-13T16:39:17Z"
- content="""
-calibre store all the metadata for safekeeping of the metadata
-(author, title...).
-
-If like me you do not like much direct mode (because of its not so
-cool interaction with plain git), you could use the largfiles config
-to let those files in plain git. You will then also need something for
-the database. See [[tips/Git_annex_and_Calibre]] for a full solution.
-
-"""]]
diff --git a/doc/bugs/Unknown_command___39__list__39__.mdwn b/doc/bugs/Unknown_command___39__list__39__.mdwn
deleted file mode 100644
index f08fc6eef..000000000
--- a/doc/bugs/Unknown_command___39__list__39__.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-### Please describe the problem.
-
-The man page claims there exists a query command 'list' but:
-
-    % git annex list somefile
-    git-annex: Unknown command 'list'
-
-### What version of git-annex are you using? On what operating system?
-
-man page online and git-annex version 4.20130909.
-
-> Your last line explains the problem. The online man page
-> documents the latest release, or in some cases
-> unrelased git version. You have a version 2 releases old installed.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/Unknown_command___39__list__39__/comment_1_c625d03d1ed2019141ac9202f933466d._comment b/doc/bugs/Unknown_command___39__list__39__/comment_1_c625d03d1ed2019141ac9202f933466d._comment
deleted file mode 100644
index 7566dc1ef..000000000
--- a/doc/bugs/Unknown_command___39__list__39__/comment_1_c625d03d1ed2019141ac9202f933466d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://cstork.org/"
- nickname="Chris Stork"
- subject="News page stopped listing latest releases?"
- date="2013-09-30T16:08:18Z"
- content="""
-Ah, cabal tells me that 4.20130927 is out now.  I missed that because I thought that the [News](http://git-annex.branchable.com/news/) page is 'authoritative' :-)  and it's still advertising 4.20130909.  Sorry about that.
-"""]]
diff --git a/doc/bugs/Unknown_command___39__list__39__/comment_2_800e1b6417768bdadda311ebfb5df637._comment b/doc/bugs/Unknown_command___39__list__39__/comment_2_800e1b6417768bdadda311ebfb5df637._comment
deleted file mode 100644
index f8592b571..000000000
--- a/doc/bugs/Unknown_command___39__list__39__/comment_2_800e1b6417768bdadda311ebfb5df637._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.80"
- subject="comment 2"
- date="2013-09-30T16:23:31Z"
- content="""
-I've had a bit of a mess with cabal. First my release scripts apparently broke and didn't upload the last 2 releases there. Then when I manually fixed that, hackage has been upgraded to a new version, which  is broken and will not accept tarballs > 1 mb. So I had to re-upload git-annex hacked to fit in 1 mb (removing all documentation), and I did so from a current git snapshot. Meh.
-"""]]
diff --git a/doc/bugs/Unknown_command___39__list__39__/comment_3_35dfc75ce9efffff139f8929dc311e29._comment b/doc/bugs/Unknown_command___39__list__39__/comment_3_35dfc75ce9efffff139f8929dc311e29._comment
deleted file mode 100644
index 1899029ad..000000000
--- a/doc/bugs/Unknown_command___39__list__39__/comment_3_35dfc75ce9efffff139f8929dc311e29._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://cstork.org/"
- nickname="Chris Stork"
- subject="comment 3"
- date="2013-10-04T11:17:42Z"
- content="""
-Ah, I could have sworn that I also tried to update via cabal but didn't see a new version and this explains why...
-
-Your release script might also have a problem with updating the [[News]] page...
-"""]]
diff --git a/doc/bugs/Unknown_remote_type_webdav.mdwn b/doc/bugs/Unknown_remote_type_webdav.mdwn
deleted file mode 100644
index 7c6f1ae36..000000000
--- a/doc/bugs/Unknown_remote_type_webdav.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-When I attempt to setup a [box.com special remote](http://git-annex.branchable.com/tips/using_box.com_as_a_special_remote/) I get the following error:
-
-    git-annex: Unknown remote type webdav
-
-I'm using the Linux prebuilt tarball. Does it not include webdav support?
-
-> The amd64 standalone tarball was indeed built without it for the last
-> release. Fixed that. [[done]] --[[Joey]]
diff --git a/doc/bugs/Unnecessary_remote_transfers.mdwn b/doc/bugs/Unnecessary_remote_transfers.mdwn
deleted file mode 100644
index 04ede7a02..000000000
--- a/doc/bugs/Unnecessary_remote_transfers.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-### Please describe the problem.
-This is related to [[http://git-annex.branchable.com/bugs/assistant_does_not_always_use_repo_cost_info_when_queueing_downloads/]]
-
-### What steps will reproduce the problem?
-1.  Make a client repo on two machines on the local network.
-2.  Pair them.
-3.  Make a remote transfer repo.
-4.  Set up Jabber on both local machines.
-5.  Put a large file into the annex on one of the local machines.
-6.  Watch as the source client repo copies the file directly to the local paired machine, but also copies it to the remote transfer repo.
-7.  Wait for the local paired transfer to finish.
-8.  Manually disable syncing to the remote transfer repo.
-9.  Manually reenable it.
-10.  Watch as the remote transfer is not resumed.
-
-### What version of git-annex are you using? On what operating system?
-Using the 1 Nov Linux tarball, Ubuntu Raring.
-
-### Please provide any additional information below.
-This is a problem because unless I manually disable the remote repo, it will continue uploading the large file until it finishes, which uses the limited upstream bandwidth on my Internet connection--and this could take hours depending on the size of the file.
-
-The remote transfer wasn't even necessary to begin with, because it already had a direct connection to the local paired repo.  But even so, it should at least abort the remote transfer when the local transfer finishes.
-
-Thanks for your work on git-annex assistant.
-
-> From a re-read of the comments, this was resolved satisfactorily,
-> and I don't need to make any changes. [[done]] --[[Joey]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_10_b778fbb1386f0f51bf057ffacd590ebb._comment b/doc/bugs/Unnecessary_remote_transfers/comment_10_b778fbb1386f0f51bf057ffacd590ebb._comment
deleted file mode 100644
index 8c985243a..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_10_b778fbb1386f0f51bf057ffacd590ebb._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="comment 10"
- date="2013-11-03T02:19:04Z"
- content="""
-Thanks, Joey.  I didn't realize that there were two instances of the assistant running.
-
-Forgive my ignorance, but if I disable the assistant running in the backup repo, will the other assistant still backup files to it?
-
-Also, from a UI perspective, does the webapp currently not seem to support secondary internal drives, at least in a useful way?
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_11_55430eac842d0a192dc7f41d7730e4d5._comment b/doc/bugs/Unnecessary_remote_transfers/comment_11_55430eac842d0a192dc7f41d7730e4d5._comment
deleted file mode 100644
index 808c5bca6..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_11_55430eac842d0a192dc7f41d7730e4d5._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 11"
- date="2013-11-03T02:32:47Z"
- content="""
-Yes, either of the assistants will still back up files to it, as long as they have it configured as a git remote. The same way that your transfer repository is (probably) not running the git-annex assistant.
-
-It does sound like using the removable drive UI would have saved you some trouble. I'm not sure why the webapp would not list a llvm device as a removable drive -- from inspecting the code, it seems like it would not be filtered out, as long as /proc/mounts shows the decive as /dev/something (I don't have a llvm device handy to check what it looks like).
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_1_00c18e07678dc513a02d974fe059df73._comment b/doc/bugs/Unnecessary_remote_transfers/comment_1_00c18e07678dc513a02d974fe059df73._comment
deleted file mode 100644
index 7baa58489..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_1_00c18e07678dc513a02d974fe059df73._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 1"
- date="2013-11-02T19:54:44Z"
- content="""
-In what order does the webapp list your repositories? 
-
-When a new file appears, it will always go through the list of repositories in order, and try to transfer the file to each in turn, unless the configuration indicates it shouldn't. So, if the remote transfer repo is listed before the local repo, it will first upload the file to the transfer repo, and then upload it to the local repo. (And then later on, remove it from the transfer repo, since the file has reached all clients, probably.) OTOH, if the local repo comes first, it will upload the file to it over the LAN, and then when it comes to the transfer repo, if the file has successfully been sent to all clients, the transfer repo will no longer want it, and so no expensive upload is done over the internet.
-
-You can re-order the repository list in the webapp by dragging them up and down. It should default to having your locally paired repos first, unless you've changed it. If you think it came up with the wrong order, paste in your .git/config before you re-order the repositories..
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_2_2e9992dbfceabd6df535a2770626de16._comment b/doc/bugs/Unnecessary_remote_transfers/comment_2_2e9992dbfceabd6df535a2770626de16._comment
deleted file mode 100644
index cc0cb067e..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_2_2e9992dbfceabd6df535a2770626de16._comment
+++ /dev/null
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="comment 2"
- date="2013-11-02T22:48:18Z"
- content="""
-The webapp has the remote repo at the bottom of the list.  But here's .git/config.  It has a high repo cost for the local paired repo, and no cost listed for the remote one:
-
-[[!format sh \"\"\"
-[core]
-        repositoryformatversion = 0
-        filemode = true
-        bare = false
-        logallrefupdates = true
-[annex]
-        uuid = 946f9095-588b-4421-b66a-4a1e5632ff6b
-        version = 3
-        direct = true
-        diskreserve = 1 megabyte
-        numcopies = 1
-        debug = false
-[gc]
-        auto = 0
-[remote \"Onyx\"]
-        url = ssh://me@git-annex-Onyx.local-me_annex/~/annex/
-        annex-uuid = 80709bc2-3cbe-434b-b7b9-306278b9a4e9
-        annex-cost = 125.0
-        fetch = +refs/heads/*:refs/remotes/Onyx/*
-[remote \"Remote\"]
-        annex-rsyncurl = username@git-annex-example.net-username_annex:annex/
-        annex-uuid = 33930bae-63d2-4a52-b330-58872aaeb1bf
-        fetch = 
-        annex-sync = true
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_3_a98f3091a6a658919f0562cf396439c2._comment b/doc/bugs/Unnecessary_remote_transfers/comment_3_a98f3091a6a658919f0562cf396439c2._comment
deleted file mode 100644
index b6900f339..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_3_a98f3091a6a658919f0562cf396439c2._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="comment 3"
- date="2013-11-02T22:59:18Z"
- content="""
-Also, I just realized that it's uploading two large files to my remote transfer repo, even though I already have both files in my local paired repo on both systems; i.e. there's no need to send it to the transfer repo at all.  And it was yesterday when the two files were transferred.  So I have no idea why today it thinks it needs to upload them to the transfer repo.  :/
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_4_417c1e8e27ee1a1f9ebf9160560605c5._comment b/doc/bugs/Unnecessary_remote_transfers/comment_4_417c1e8e27ee1a1f9ebf9160560605c5._comment
deleted file mode 100644
index b0d4c1146..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_4_417c1e8e27ee1a1f9ebf9160560605c5._comment
+++ /dev/null
@@ -1,96 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="Super confused"
- date="2013-11-02T23:30:41Z"
- content="""
-I think now I'm double- or triple-confused.  Here is me@desktop:~/annex/.git/config:
-
-[[!format sh \"\"\"
-[core]
-        repositoryformatversion = 0
-        filemode = true
-        bare = false
-        logallrefupdates = true
-[annex]
-        uuid = 80709bc2-3cbe-434b-b7b9-306278b9a4e9
-        version = 3
-        direct = true
-        fscknudge = true
-[gc]
-        auto = 0
-[remote \"laptop\"]
-        url = ssh://me@git-annex-laptop-me_annex/~/annex/
-        annex-uuid = 946f9095-588b-4421-b66a-4a1e5632ff6b
-        annex-cost = 175.0
-        fetch = +refs/heads/*:refs/remotes/laptop/*
-[remote \"Remote\"]
-        annex-rsyncurl = username@example.net:annex/
-        annex-uuid = 33930bae-63d2-4a52-b330-58872aaeb1bf
-        fetch = 
-        annex-sync = false
-[remote \"backupOndesktop\"]
-        url = /mnt/debian/home/me/annex-backup
-        annex-uuid = 86535965-6ca7-4bf3-89af-bca3a07f96f9
-        fetch = +refs/heads/*:refs/remotes/backupOndesktop/*
-\"\"\"]]
-
-What I have set up (or intended to set up) is:
-
-* Client: me@laptop:~/annex
-* Client: me@desktop:~/annex
-* Transfer: username@example.net:~/annex
-* Full Backup: me@desktop:/mnt/debian/home/me/annex-backup
-
-What I expected was that:
-
-1.  The two Client repos would sync directly over the LAN whenever possible.
-2.  The transfer repo would be used only to sync the laptop and desktop, and then only if my laptop were not on the LAN with my desktop.
-3.  The Full Backup repo would be synced directly with the me@desktop Client repo, within the same system, from one hard disk to the other.
-
-But what I'm seeing is...not quite that.
-
-1.  It's very confusing (to me, at least) that on my desktop system I can look at my annex setup from the \"perspective\" of both local repos.  When I \"switch\" to the other repo, the setup looks different: even the same repos can have different names and descriptions, and can be enabled and disabled independently depending on the \"perspective\"...but their Type is still the same.
-
-2.  Looking from the \"perspective\" of the Full Backup repo, I'm seeing files being transferred to the Transfer repo, even though those files are already present in both Client repos, and even though the webapp says that the Full Backup repo has been synced.  When I disable and reenable the Transfer repo, it starts those transfers over again, even though they aren't necessary.  For example, here is the log from disabling and reenabling the Transfer repo from the \"perspective\" of the Full Backup repo:
-
-[[!format sh \"\"\"
-[2013-11-02 18:24:35 CDT] main: Syncing with example.net_annex 
-(gpg) 
-gpg: Terminated caught ... exiting
-[2013-11-02 18:24:49 CDT] call: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"config\",\"remote.example.net_annex.annex-sync\",\"true\"]
-[2013-11-02 18:24:49 CDT] read: git [\"config\",\"--null\",\"--list\"]
-[2013-11-02 18:24:49 CDT] read: git [\"config\",\"--null\",\"--list\"]
-[2013-11-02 18:24:49 CDT] read: git [\"config\",\"--null\",\"--list\"]
-[2013-11-02 18:24:49 CDT] main: Syncing with example.net_annex 
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"symbolic-ref\",\"HEAD\"]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"refs/heads/master\"]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"git-annex\"]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"log\",\"refs/heads/git-annex..2c42d607c099b6ec4a20603b809f44d161e42489\",\"--oneline\",\"-n1\"]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"symbolic-ref\",\"HEAD\"]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"refs/heads/master\"]
-[2013-11-02 18:24:49 CDT] TransferScanner: starting scan of [Remote { name =\"example.net_annex\" }]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"ls-files\",\"--cached\",\"-z\",\"--\"]
-[2013-11-02 18:24:49 CDT] TransferScanner: queued Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" video.flv Nothing : expensive scan found missing object
-[2013-11-02 18:24:49 CDT] Transferrer: Transferring: Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" video.flv Nothing
-[2013-11-02 18:24:49 CDT] TransferScanner: queued Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" image.jpg Nothing : expensive scan found missing object
-[2013-11-02 18:24:49 CDT] call: /home/me/.bin/git-annex.linux/git-annex [\"transferkeys\",\"--readfd\",\"35\",\"--writefd\",\"34\"]
-[2013-11-02 18:24:49 CDT] TransferScanner: queued Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" linux-image-3.8.0-29-generic_3.8.0-29.42_i386.deb Nothing : expensive scan found missing object
-[2013-11-02 18:24:49 CDT] TransferScanner: finished scan of [Remote { name =\"example.net_annex\" }]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"git-annex\"]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"log\",\"refs/heads/git-annex..2c42d607c099b6ec4a20603b809f44d161e42489\",\"--oneline\",\"-n1\"]
-[2013-11-02 18:24:49 CDT] chat: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"cat-file\",\"--batch\"]
-[2013-11-02 18:24:49 CDT] read: git [\"config\",\"--null\",\"--list\"]
-[2013-11-02 18:24:49 CDT] TransferWatcher: transfer starting: Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" video.flv Nothing
-(gpg) [2013-11-02 18:24:49 CDT] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--batch\",\"--passphrase-fd\",\"20\",\"--symmetric\",\"--force-mdc\",\"--no-textmode\"]
-[2013-11-02 18:24:50 CDT] call: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"config\",\"remote.example.net_annex.annex-sync\",\"false\"]
-[2013-11-02 18:24:50 CDT] read: git [\"config\",\"--null\",\"--list\"]
-[2013-11-02 18:24:50 CDT] read: git [\"config\",\"--null\",\"--list\"]
-[2013-11-02 18:24:50 CDT] read: git [\"config\",\"--null\",\"--list\"]
-
-gpg: Terminated caught ... exiting\"\"\"]]
-
-I have no idea why it's doing that, because all three of those files are already in both Client repos and the Full Backup repo.
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_5_eb5a2717a1f0c7bb761d2a7866b23def._comment b/doc/bugs/Unnecessary_remote_transfers/comment_5_eb5a2717a1f0c7bb761d2a7866b23def._comment
deleted file mode 100644
index 0e2ec4ec8..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_5_eb5a2717a1f0c7bb761d2a7866b23def._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="Deleting repos from different perspectives"
- date="2013-11-02T23:33:48Z"
- content="""
-One other thing, sorry, but I think this is important:  From the perspective of the Full Backup repo, I set the Transfer repo to be deleted, thinking that would prevent the desktop's Client and Full Backup repos from syncing through the Transfer repo.  But then when I switch to the perspective of the desktop's Client repo, it is \"cleaning out\" the Transfer repo--but I wanted the Transfer repo to be used for syncing the two Client repos!  So I set it back to Transfer instead of Unwanted...but then when I switch back to the Full Backup perspective, the Transfer repo is no longer Unwanted.
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_6_89f756db1f3f2e60a3bd1f35f55fee43._comment b/doc/bugs/Unnecessary_remote_transfers/comment_6_89f756db1f3f2e60a3bd1f35f55fee43._comment
deleted file mode 100644
index 509cc3f3f..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_6_89f756db1f3f2e60a3bd1f35f55fee43._comment
+++ /dev/null
@@ -1,40 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="config from backup repo"
- date="2013-11-03T00:20:11Z"
- content="""
-Sorry for posting over and over again, just trying to provide info when I discover it.
-
-Here's **/mnt/debian/home/me/annex-backup/.git/config**
-
-[[!format sh \"\"\"
-[core]
-        repositoryformatversion = 0
-        filemode = true
-        bare = false
-        logallrefupdates = true
-[annex]
-        uuid = 86535965-6ca7-4bf3-89af-bca3a07f96f9
-        version = 3
-        direct = true
-        fscknudge = true
-        diskreserve = 100 megabyte
-        numcopies = 1
-        debug = false
-[gc]
-        auto = 0
-[remote \"desktop\"]
-        url = /home/me/annex
-        fetch = +refs/heads/*:refs/remotes/desktop/*
-        annex-uuid = 80709bc2-3cbe-434b-b7b9-306278b9a4e9
-[remote \"Remote\"]
-        annex-rsyncurl = username@example.net:annex/
-        annex-uuid = 33930bae-63d2-4a52-b330-58872aaeb1bf
-        annex-sync = false
-        fetch =\"\"\"]]
-
-1.  Should I remove the \"Remote\" Transfer repo from this config file to prevent it from using the Transfer repo?  I only want this repo to sync directly with the other internal hard disk.
-
-2.  Is it correct for git-annex to add this Transfer repo to this config file in the first place?
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_7_5aaf8766a7ba05c4f92715e5d5175a8f._comment b/doc/bugs/Unnecessary_remote_transfers/comment_7_5aaf8766a7ba05c4f92715e5d5175a8f._comment
deleted file mode 100644
index f117f15c1..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_7_5aaf8766a7ba05c4f92715e5d5175a8f._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 7"
- date="2013-11-03T00:45:09Z"
- content="""
-* The costs you show look fine.
-* Yes, deleting a repository in the webapp actually deletes it. It doesn't just remove the remote from .git/config. Most people using the webapp don't want to draw such a fine distinction, I think.
-* It's not a very usual configuration to have 2 repositories on the same machine with the git-annex assistant running in both. You might just want to configure the assistant to not run in the backup repository.
-
-Some of the things you've said suggest that the backup repository might not be immediately noticing when changes are pushed to it. Since its location is shown as /mnt/debian/home/me, I have to wonder if that's some NFS mount or other network filesystem causing problems.
-
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_8_e856b350632cc865d16d1995a6cdf065._comment b/doc/bugs/Unnecessary_remote_transfers/comment_8_e856b350632cc865d16d1995a6cdf065._comment
deleted file mode 100644
index 1177205e3..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_8_e856b350632cc865d16d1995a6cdf065._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU"
- nickname="Adam"
- subject="comment 8"
- date="2013-11-03T01:07:31Z"
- content="""
-> It's not a very usual configuration to have 2 repositories on the same machine with the git-annex assistant running in both. You might just want to configure the assistant to not run in the backup repository.
-
-Maybe that's the crux of the problem.  But I'm not sure what I did wrong to make that happen.  I have a second internal hard disk in my desktop system, and I wanted to put a Full Backup repo on it.  I tried to add a \"Removable drive\" repo (since I sometimes unplug it to swap cables with a DVD drive), but since the assistant didn't detect any actual removable drives, that didn't work.  So I used \"Add another repository\" and set it to a Full Backup repo.  Is that the wrong way to do it?  :)
-
-> Some of the things you've said suggest that the backup repository might not be immediately noticing when changes are pushed to it. Since its location is shown as /mnt/debian/home/me, I have to wonder if that's some NFS mount or other network filesystem causing problems.
-
-/mnt/debian is /dev/mapper/lvm-root, another internal disk.  The disk is working fine.  :)
-"""]]
diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_9_64f831545b34b78452952cf49b5f5b05._comment b/doc/bugs/Unnecessary_remote_transfers/comment_9_64f831545b34b78452952cf49b5f5b05._comment
deleted file mode 100644
index 03127c4ad..000000000
--- a/doc/bugs/Unnecessary_remote_transfers/comment_9_64f831545b34b78452952cf49b5f5b05._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 9"
- date="2013-11-03T01:52:56Z"
- content="""
-Ok, since we don't have NFS craziness, I'm going to put theories about it not noticing incoming syncs on hold. (I think I probably misunderstood [this comment](http://git-annex.branchable.com/bugs/Unnecessary_remote_transfers/#comment-39490c318620c141e7557b7bcba0e5c8) and anyway the assistant has some throttling so won't always immediately load config changes that have been synced to it if some other config changes were loaded a minute before.)
-
-I think this behavior can probably be explained without resorting to any bugs, now that I have, I think, a full picture of the repository network:
-
-<pre>
-laptop <-> desktop <-> backup
-    |         |       |
-    v         v       v
-      transfer (cloud)
-</pre>
-
-Now when a file is added to desktop, it immediately copies it to backup, which is on the same machine, so that happens quite quickly. Then it starts sending it across the LAN to laptop.
-
-Meanwhile, the assistant daemon running on backup wakes up, notices it's just received an object, and sees that this object is currently located on only desktop and backup, but not yet on laptop or transfer. Which means that it should send the object to transfer, from which it will eventually reach laptop.
-
-The only ways I can think of to avoid such an unnecessary transfer would be a) for desktop could somehow tell backup that it's in the process of sending the file to laptop or b) for a map of current state of the network to be constructed and maintained and analyzed automatically, so it it could conclude backup does not need to send files to transfer if they're already present on desktop. There is some discussion about this in [[design/assistant/syncing]]. Hard problem in general I think, although slightly less hard in this specific case since desktop and backup know they're in the same machine.
-
-But it should be easy to configure it so this doesn't happen. Just make backup not have the transfer repository configured as a remote (or just pause it syncing to there in the webapp). Or, don't run the assistant at all on backup (see `~/.config/git-annex/autostart`).
-"""]]
diff --git a/doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__.mdwn b/doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__.mdwn
deleted file mode 100644
index 99043aa25..000000000
--- a/doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-### Please describe the problem.
-After branching from master/HEAD^ and deleting the master branch, I was surprised that content introduced in master/HEAD is not reported as unused. Instead, one first has to delete the synced/master branch, and also the remote-tracking branches for master.
-
-Would it make sense to discount synced/* and the remote tracking branches when gathering unused files? If the remote-tracking branch always reflects the state of the remote, tracking a branch should not cause annex to think that the local annex is somehow using all the files on the remote. Or would that be unsafe? As for the synced/* branches I'm not so sure.
-
-### What steps will reproduce the problem?
-Clone annex A to B.
-Branch off of master^ in B.
-Delete master.
-Issue git annex unused. --> Content introduced in master is still not reported as unused.
-Delete synced/master --> Cf. above.
-Delete origin/master and origin/synced/master --> Content is now reported as unused.
-
-### What version of git-annex are you using? On what operating system?
-
-5.20131230
-
-> Behaving as designed; [[done]] --[[Joey]]
diff --git a/doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__/comment_1_8fe44da0581d9b8c6ab5fe6aea8d83d1._comment b/doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__/comment_1_8fe44da0581d9b8c6ab5fe6aea8d83d1._comment
deleted file mode 100644
index a89f761a4..000000000
--- a/doc/bugs/Unused_files_not_being_reported:_Do_not_take_remote_tracking_branches_into_account__63__/comment_1_8fe44da0581d9b8c6ab5fe6aea8d83d1._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.46"
- subject="comment 1"
- date="2014-01-26T18:08:21Z"
- content="""
-I'd rather that people not lose the content of annexed files that are in either their current local branch, or the current branch of any other clones of the repository that they might be working on. This is why `unused` looks at the remote tracking branches, and the various sync branches. 
-"""]]
diff --git a/doc/bugs/Update_dependency_on_certificate___62____61___1.3.3.mdwn b/doc/bugs/Update_dependency_on_certificate___62____61___1.3.3.mdwn
deleted file mode 100644
index 2a2a1469d..000000000
--- a/doc/bugs/Update_dependency_on_certificate___62____61___1.3.3.mdwn
+++ /dev/null
@@ -1,64 +0,0 @@
-What steps will reproduce the problem?
-
-Run:
-
-    cabal install git-annex
-
-What is the expected output? What do you see instead?
-
-The current output is the following:
-
-    $ cabal install git-annex        
-    Resolving dependencies...    
-    Configuring certificate-1.3.2...
-    Building certificate-1.3.2...
-    Preprocessing library certificate-1.3.2...
-    [ 1 of 10] Compiling Data.Certificate.KeyDSA ( Data/Certificate/KeyDSA.hs, dist/build/Data/Certificate/KeyDSA.o )
-    [ 2 of 10] Compiling Data.Certificate.KeyRSA ( Data/Certificate/KeyRSA.hs, dist/build/Data/Certificate/KeyRSA.o )
-    
-    Data/Certificate/KeyRSA.hs:64:27:
-        `RSA.private_pub' is not a (visible) field of constructor `RSA.PrivateKey'
-    cabal: Error: some packages failed to install:
-    DAV-0.3 depends on certificate-1.3.2 which failed to install.
-    authenticate-1.3.2 depends on certificate-1.3.2 which failed to install.
-    certificate-1.3.2 failed during the building phase. The exception was:
-    ExitFailure 1
-    git-annex-3.20130107 depends on certificate-1.3.2 which failed to install.
-    http-conduit-1.8.6.3 depends on certificate-1.3.2 which failed to install.
-    http-reverse-proxy-0.1.1.1 depends on certificate-1.3.2 which failed to install.
-    tls-1.0.3 depends on certificate-1.3.2 which failed to install.
-    tls-extra-0.5.1 depends on certificate-1.3.2 which failed to install.
-    yesod-1.1.7.2 depends on certificate-1.3.2 which failed to install.
-    yesod-auth-1.1.3 depends on certificate-1.3.2 which failed to install.
-
-I'd rather get a message stating how awesome the software I just installed is. :)
-
-What version of git-annex are you using? On what operating system?
-
-  * Debian (testing)
-  * GHC 7.4.1
-  * Cabal 1.14.0, cabal-install 0.14.0
-  * cabal list git-annex says the installing version is: 3.20130107
-
-Please provide any additional information below.
-
-The certificate package version 1.3.2 does not seem to install properly with
-this version of GHC (I think).
-
-Version 1.3.3 solves the issue. I don't know if there is a way for me to
-override the dependency tree to try to force the version update with
-cabal-install, so maybe it's worth filing a bug.
-
-Thanks a lot for git-annex.
-
-> Welcome to cabal hell! This problem is why haskell's cabal system is not
-> a sufficient way for users to install git-annex, and we have to provide
-> prebuilt builds.
-> 
-> No change to git-annex can fix this problem. The problem is that
-> the old version of certificate got busted by some change to one of its
-> dependencies, and several libraries that git-annex depends on have not
-> yet been updated to use the new version of certificate. Once those
-> libraries get updated, it'll fix itself.
-> 
-> [[done]]; not git-annex bug. --[[Joey]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work.mdwn b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work.mdwn
deleted file mode 100644
index 1bb985891..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work.mdwn
+++ /dev/null
@@ -1,49 +0,0 @@
-What steps will reproduce the problem?
-1. Create a Repository
-2. Add a Remote Server
-
-What is the expected output? What do you see instead?
-The option "Use a git repository on the server" is marked as not available
-
-What version of git-annex are you using? On what operating system?
-Version: 4.20130405 but on Webapp ist shows: Version: 4.20130324
-Linux 64bit
-
-Please provide any additional information below.
-git and git-annex are available on the Remote Server
-
-> While this bug report was about a server that did not get git-annex-shell
-> installed in PATH (something trivially fixed by `apt-get install
-> git-annex`), the comments below would like to turn this into a bug report about 
-> the error message "unknown UUID; cannot modify". All right then..
-> --[[Joey]]
-> 
-> This can occur if a ssh key is locked down to use directory A, and a
-> new repo is added in directory B which uses the same ssh key. Things will
-> then fail when git-annex-shell rejects the attept to use directory B, and
-> this results in the webapp displaying an internal server error of
-> "unknown UUID; cannot modify" since NoUUID is retreived for the repo.
-> 
-> In fact, I already dealt with this
-> once in 79561774450c8abf7c2cb42b08575a3ca27010dc; it used to not use 
-> the directory name at all as part of the mangled hostname. Most of the 
-> "me too" responses" predate that fix.
-> 
-> Now, this can only happen
-> if the mangled hostname for directory A and B is the same. One way this can
-> happen is if the directories are "annex" and "~/annex". In other words,
-> I suspect that users are entering "annex" once, and "~/annex" another
-> time, when setting up what they intend to be the same repo. Perhaps the
-> first time something else fails (like the original problem of
-> git-annex-shell not being in path), or they want to set it up again,
-> and the next time the subtly different directory is entered.
-> 
-> To fix this,
-> `mangleSshHostName` would need to be changed to generate different mangled
-> hostnames in all cases. Currently, it skips non-alpha-numeric
-> characters in the directory. [[done]] --[[Joey]]
-> --[[Joey]] 
-> 
-> Additionally, just entering a path starting with "~/" would cause this
-> error, since the webapp tacks on "/~/" to make a relative path absolute.
-> I've also fixed that. [[done]] --[[Joey]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment
deleted file mode 100644
index aa8237c17..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-06T16:38:46Z"
- content="""
-Well, it works here. It checks that all of `git`, `rsync`, and `git-annex` are in the path on the remote server using `which`.
-
-I think the most likely reason would be if you've installed git-annex on the remote server but not in the PATH. If you're using the standalone tarball, for example, it's \"installed\", but it has no way to find it.
-
-Or, you could have installed from cabal, which puts it in ~/.cabal/bin or ~/bin or something like that, and perhaps you configured your shell to put that directory in the PATH, but you did it in a way that only works for login shells. If you set the PATH in `~/.bashrc`, for example, that would not work for a noninteractive shell.
-"""]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_2_bca95245b457631d08b47591da6163ad._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_2_bca95245b457631d08b47591da6163ad._comment
deleted file mode 100644
index f93285611..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_2_bca95245b457631d08b47591da6163ad._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="modules"
- ip="31.150.97.85"
- subject="comment 2"
- date="2013-04-06T20:49:20Z"
- content="""
-I have the same issue here and it seems to be the PATH problem with standalone tarball for noniteractive shell on remote server. Is there an easy way to setup right PATH or workaround for prebuilt tarballs?
-
-"""]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_3_f54bb003096752dae0442660267a1e37._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_3_f54bb003096752dae0442660267a1e37._comment
deleted file mode 100644
index 3a7158b80..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_3_f54bb003096752dae0442660267a1e37._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-06T20:59:10Z"
- content="""
-You can run this script as root, and it will install it to /usr/local/bin, which should always be in your path:
-<https://github.com/zerodogg/scriptbucket/blob/master/gitannex-install>
-
-However, I'd hope most people do not need to use the standalone tarball to install git-annex on a server. Most major linux distributions have their own way to install git-annex by now, and while most of them are too old versions to use the git annex assistant with, those old versions work fine on a server. The assistant will interoperate with them just fine.
-"""]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_4_38bb916ed5b90b92ffa91a452ff052a9._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_4_38bb916ed5b90b92ffa91a452ff052a9._comment
deleted file mode 100644
index c9742b6e1..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_4_38bb916ed5b90b92ffa91a452ff052a9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnq5niDqUBoGE7cQ8MDQKtGYIfYtg3_MvY"
- nickname="Tobias"
- subject="comment 4"
- date="2013-04-06T23:03:37Z"
- content="""
-One Step forward. But now I get the error message \"Internal Server Error unknown UUID; cannot modify\" after click on the \"Use a git repository on the server\"-Button
-
-Thanks a lot for the link to the install-script. It works very well.
-"""]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_5_5b6ef464ab1ad061f27122db40191e26._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_5_5b6ef464ab1ad061f27122db40191e26._comment
deleted file mode 100644
index f818a023e..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_5_5b6ef464ab1ad061f27122db40191e26._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="EskildHustvedt"
- ip="84.48.83.221"
- subject="comment 5"
- date="2013-04-08T07:41:38Z"
- content="""
-Tobias, you may want to download the latest version of the install script and then run it as \"gitannex-install --force\", as its version of \"git-annex-shell\" was broken (linked to a missing file, fixed now).
-"""]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_6_3727bda5082cb1f2b1f746f9f80ced7d._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_6_3727bda5082cb1f2b1f746f9f80ced7d._comment
deleted file mode 100644
index 350139350..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_6_3727bda5082cb1f2b1f746f9f80ced7d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnq5niDqUBoGE7cQ8MDQKtGYIfYtg3_MvY"
- nickname="Tobias"
- subject="comment 6"
- date="2013-04-09T17:52:14Z"
- content="""
-After update the script local and on the remote Server and run it on both with --force, I still get the same error.
-"""]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_7_a7139f19f0b73c024cd9218eb01e6104._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_7_a7139f19f0b73c024cd9218eb01e6104._comment
deleted file mode 100644
index 36547245e..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_7_a7139f19f0b73c024cd9218eb01e6104._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnu1NYw8UF-NoDbKu8YKVGxi8FoZLH7JPs"
- nickname="Chris"
- subject="Same error with Android"
- date="2013-05-21T02:15:25Z"
- content="""
-I'm using git-annex version 4.20130516-g3240006 on Android, and when I attempt to add a cloud repo with SSH & git, I get that same error - \"unknown UUID: cannot modify\". My Linux box running 4.20130516-gedc4ccd handles the same server as a cloud repo without any problems.
-"""]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_8_35c949aca52de83af4881a9da6340185._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_8_35c949aca52de83af4881a9da6340185._comment
deleted file mode 100644
index 7a59e296b..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_8_35c949aca52de83af4881a9da6340185._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk_QeJTzgCJj2ZC8EAJEODsLvxJ7dCOCVM"
- nickname="Sindre"
- subject="Non-ASCII Hostname fails"
- date="2014-04-02T05:36:54Z"
- content="""
-This bug still persists when specifying non-ascii hostnames.
-"""]]
diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_9_9100031689eaa460791191d9bfb746d8._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_9_9100031689eaa460791191d9bfb746d8._comment
deleted file mode 100644
index 6fa440f23..000000000
--- a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_9_9100031689eaa460791191d9bfb746d8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.244"
- subject="comment 9"
- date="2014-04-02T19:46:36Z"
- content="""
-Sorry, but this bug report is closed. If you think you have a bug in git-annex, file a *new* bug report with full details for how I can reproduce it.
-"""]]
diff --git a/doc/bugs/Using_Github_as_remote_throws_proxy_errors.mdwn b/doc/bugs/Using_Github_as_remote_throws_proxy_errors.mdwn
deleted file mode 100644
index 34d9eafb4..000000000
--- a/doc/bugs/Using_Github_as_remote_throws_proxy_errors.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-What steps will reproduce the problem?
-
-1. cd to an already existing git repository that uses Github as a remote, with the remote format similar to git@github.com:user/repo.git
-2. git annex init
-3. git annex status
-
-What is the expected output? What do you see instead?
-
-    $ git annex status
-    supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
-    supported remote types: git S3 bup directory rsync web hook
-    trusted repositories: Invalid command: 'git-annex-shell 'configlist' '/~/dlo/objectifier.git''
-      You appear to be using ssh to clone a git:// URL.
-      Make sure your core.gitProxy config option and the
-      GIT_PROXY_COMMAND environment variable are NOT set.
-    Command ssh ["-S","/Users/dan/Documents/Web/objectifier/.git/annex/ssh/git@github.com","-o","ControlMaster=auto","-o","ControlPersist=yes","git@github.com","git-annex-shell 'configlist' '/~/dlo/objectifier.git'"] failed; exit code 1
-    0
-    # ... other stuff that isn't relevant
-
-
-What version of git-annex are you using? On what operating system?
-
-git-annex-3.20120825
-
-Max OS X 10.8.1
-
-> [[done]]; see comments --[[Joey]] 
diff --git a/doc/bugs/Using_Github_as_remote_throws_proxy_errors/comment_1_10616b17c3fb8286fdc64c841023f8a1._comment b/doc/bugs/Using_Github_as_remote_throws_proxy_errors/comment_1_10616b17c3fb8286fdc64c841023f8a1._comment
deleted file mode 100644
index 77ebcaa1a..000000000
--- a/doc/bugs/Using_Github_as_remote_throws_proxy_errors/comment_1_10616b17c3fb8286fdc64c841023f8a1._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.14.141"
- subject="comment 1"
- date="2012-09-24T17:24:47Z"
- content="""
-The proxy message is sent from github, so I can't do anything about that. `git@github.com:user/repo.git` is a ssh url, so git-annex tries to use it as a full git-annex remote. If you use a git:// url, git-annex will
-skip it. Or you can set `git config remote.origin.annex-ignore true` (replace origin with the name of the github remote).
-"""]]
diff --git a/doc/bugs/Using_Github_as_remote_throws_proxy_errors/comment_2_8a72887d33e492a041f8246d93d0c778._comment b/doc/bugs/Using_Github_as_remote_throws_proxy_errors/comment_2_8a72887d33e492a041f8246d93d0c778._comment
deleted file mode 100644
index 5fe4e6b5a..000000000
--- a/doc/bugs/Using_Github_as_remote_throws_proxy_errors/comment_2_8a72887d33e492a041f8246d93d0c778._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmG8L2pP-i6QATf6pK9WCSGpl0O9twwh8Q"
- nickname="Dan"
- subject="comment 2"
- date="2012-09-24T18:00:17Z"
- content="""
-Ah, so with the full ssh URL, git annex thinks it's a \"real\" server and can run commands on it. Makes sense. Thanks!
-"""]]
diff --git a/doc/bugs/Using_a_revoked_GPG_key.mdwn b/doc/bugs/Using_a_revoked_GPG_key.mdwn
deleted file mode 100644
index 4e522ab78..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-### Please describe the problem.
-git-annex refuses to use revoked GPG keys. This may be understandable for the initial remote setup, but it hit me when I tried to add a new key to a remote. The previous key has been revoked (because it has been superseded by the new one), and git-annex refused to reinvoke the shared key with both keys because one of them was revoked.
-
-Given the encryption model does not allow key replacement, it should not refuse to reencrypt using a revoked key. Maybe using `--expert` would help.
-
-### What steps will reproduce the problem?
-Encrypt a special remote with a key K1. Revoke key K1. Try to add key K2 with enableremote. git-annex will refuse to encrypt the shared key with the revoked one.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20130802-g1452ac3
-
-### Please provide any additional information below.
-
-[[!format sh """
-% git annex enableremote zoidberg-crypted encryption=42B8F7C2 
-enableremote zoidberg-crypted (encryption update) 
-You need a passphrase to unlock the secret key for
-user: "Samuel Tardieu <sam@rfc1149.net>"
-2048-bit ELG key, ID F0D70BAF, created 2002-05-31 (main key ID 1B80ADE6)
-
-gpg: NOTE: key has been revoked
-gpg: reason for revocation: Key is superseded
-gpg: revocation comment: Key superseded by 42B8F7C2
-gpg: revocation comment: (fingerprint 1D36 D924 8B33 DCAB 7BA5  BA44 7A30 BCF4 42B8 F7C2)
-gpg: F13322411B80ADE6: skipped: Unusable public key
-gpg: [stdin]: encryption failed: Unusable public key
-
-git-annex: user error (gpg ["--quiet","--trust-model","always","--encrypt","--no-encrypt-to","--no-default-recipient","--recipient","7A30BCF442B8F7C2","--recipient","F13322411B80ADE6"] exited 2)
-failed
-git-annex: enableremote: 1 failed
-"""]]
-
-> [[done]]; can now use: `git annex enableremote foo keyid-=REVOKEDKEY
-> keyid+=NEWKEY` to remove it, and add a new key. --[[Joey]]  
diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_1_7bb01d081282e5b02b7720b2953fe5be._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_1_7bb01d081282e5b02b7720b2953fe5be._comment
deleted file mode 100644
index baddbbf49..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key/comment_1_7bb01d081282e5b02b7720b2953fe5be._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmWg4VvDTer9f49Y3z-R0AH16P4d1ygotA"
- nickname="Tobias"
- subject="comment 1"
- date="2013-08-12T11:47:28Z"
- content="""
-I'd be very unhappy indeed if I couldn't revoke access to my annex.
-"""]]
diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_2_9c0c40360f0058a4bd346c1362e302b6._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_2_9c0c40360f0058a4bd346c1362e302b6._comment
deleted file mode 100644
index 003f9a34a..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key/comment_2_9c0c40360f0058a4bd346c1362e302b6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://www.rfc1149.net/"
- nickname="Sam"
- subject="comment 2"
- date="2013-08-13T07:28:30Z"
- content="""
-Tobias: I don't understand what you mean. The issue here is that once an existing key is revoked, git-annex will refuse to add *another non-revoked* key.
-"""]]
diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_3_8f69f58107246595f5603f35c4aa7395._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_3_8f69f58107246595f5603f35c4aa7395._comment
deleted file mode 100644
index 7f18cfe39..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key/comment_3_8f69f58107246595f5603f35c4aa7395._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmWg4VvDTer9f49Y3z-R0AH16P4d1ygotA"
- nickname="Tobias"
- subject="comment 3"
- date="2013-08-13T08:47:45Z"
- content="""
-Ah, sorry, i'm uncomprehending :)
-"""]]
diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_4_78b3c52ba85edfa6ee6e273bec3bea5c._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_4_78b3c52ba85edfa6ee6e273bec3bea5c._comment
deleted file mode 100644
index 61b03c109..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key/comment_4_78b3c52ba85edfa6ee6e273bec3bea5c._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.209"
- subject="comment 4"
- date="2013-08-16T07:14:12Z"
- content="""
-The [[OpenPGP standard|https://tools.ietf.org/html/rfc4880]] specifies that revoked keys/subkeys \"are not to be used\". AFIK GnuPG, as any RFC-compliant implementation, will not let you encrypt to a revoked key no matter what. An extremely dirty workaround is to set up your system clock prior to the revocation date (but that might put your whole system at risk since other applications may rely synced clocks to work properly).
-
-That said, what you really wanted to do was to revoke access to K1 and add K2 instead. That seems to be a perfectly valid use-case, and it shouldn't be hard to add to git-annex; stay tunned ;-)
-
-
-Tobias: Not sure what you meant by \"revoke access to my annex\", but if you were thinking of the key owner, note that with the current [[encryption design|http://git-annex.branchable.com/design/encryption]], since that person may simply grab from the git repo and then at any time decrypt the passphrase for the symmetric cipher, it makes little sense to revoke access for that person unless you change that passphrase, and reencrypt all annexed files on the remote, which of course needs to be done locally for the encryption to make sense at all.
-"""]]
diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_5_a85ccf2f09ebe87147f8761b81a02326._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_5_a85ccf2f09ebe87147f8761b81a02326._comment
deleted file mode 100644
index ff441671f..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key/comment_5_a85ccf2f09ebe87147f8761b81a02326._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://www.rfc1149.net/"
- nickname="Sam"
- subject="comment 5"
- date="2013-08-19T11:35:52Z"
- content="""
-Indeed, removing the revoked key and putting the new one would be acceptable, there is no reason to keep the revoked one around.
-"""]]
diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_6_8b89eb5e6386acd0a922310c04f863ac._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_6_8b89eb5e6386acd0a922310c04f863ac._comment
deleted file mode 100644
index eb9cd0f54..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key/comment_6_8b89eb5e6386acd0a922310c04f863ac._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.209"
- subject="comment 6"
- date="2013-08-19T13:22:59Z"
- content="""
-All right, what would be a nice user interface, compatible with the current commands? I was thinking of something along the lines of `git annex enableremote +encryption=newKey -encryption=oldKey`, with an alias `+encryption=encryption` to be backward compatible. It's probably not optimal though, feel free to comment :-)
-
-Of course, `git-annex` should ensure that at any point in time the passphrase is always encrypted using an OpenPGP key. (Otherwise it might be stored clear in the git repository, which would void the encryption.) Also, anyone who can decrypt the passphrase can revoke all existing keys and reencrypt it using another key; this not really a big deal since the cipher is version-controlled anyway, so loosing access to the repo is unlikely.
-
-By the way, since we're about to amend the arguments for `enableremote`, it'd be nice to take advantage of the situation to allow pure asymmetric encryption. I propose `git annex initremote ... encryption=myKey crypto={none,hybrid,pubkey}` to use respectively no-encryption, an asymmetrically encrypted passphrase (the current design, default), and OpenPGP keys only.
-"""]]
diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_7_20dc5a7ce7cb6ca97ccdfb923c3b24bb._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_7_20dc5a7ce7cb6ca97ccdfb923c3b24bb._comment
deleted file mode 100644
index 02be72e36..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key/comment_7_20dc5a7ce7cb6ca97ccdfb923c3b24bb._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.209"
- subject="comment 7"
- date="2013-08-19T16:08:49Z"
- content="""
-On second thought, I think it makes more sense to have something like `git annex initremote ... encryption={none,shared,hybrid,pubkey} keyid=whatever` and `git annex enableremote ... [+keyid=newkey] [-keyid=oldkey]`, where `keyid` can only be used when `encryption` is either `hybrid` (default) or `pubkey`.
-
-This would break compatibility with the current interpretation of `encryption`, but I believe it's not so invasive: People are not creating new remotes every day, and an error message could clarify the new behavior. It's also clearer, since key IDs can be added and deleted at will, whereas the encryption scheme cannot.
-"""]]
diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_8_9dc921dc6077f828454a4444088b9a43._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_8_9dc921dc6077f828454a4444088b9a43._comment
deleted file mode 100644
index a63ce1262..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key/comment_8_9dc921dc6077f828454a4444088b9a43._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 8"
- date="2013-08-22T17:05:49Z"
- content="""
-Note that the assistant generates initremote parameters so code there also needs to be changed if the syntax changes.
-
-I think I am ok with changing the syntax. However, it seems that `encryption=-oldkey encryption=newkey` could be used to remove the old revoked key and add a new one. Using `-keyid` as a parameter to initremote is a bit tricky since git-annex's regular option parser would see it, before the parameter could get to initremote. (Unless -keyid was defined as a regular option specific to initremote.) OR, git-annex could just try to detect when a key is revoked and automatically remove it when a new encryption key is specified.
-
-Hmm, it would be possible to have it just notice, when adding a new key, if one of the existing keys is revoked, and
-remove the revoked key automatically.
-
-The above doesn't deal with the case of wanting to add pure asymmetric encryption. It seems to me that from a user's point of view, what they really need to know about asymmetric encryption is that they can't easily give additional keyids access after the fact (without reencrypting and reuploading everything). So I think it would be good if the syntax made that obvious. Perhaps `encryptiononly=key`
-"""]]
diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_9_f50c802d78041fd1522f0e7599ce6a45._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_9_f50c802d78041fd1522f0e7599ce6a45._comment
deleted file mode 100644
index d86de4e1b..000000000
--- a/doc/bugs/Using_a_revoked_GPG_key/comment_9_f50c802d78041fd1522f0e7599ce6a45._comment
+++ /dev/null
@@ -1,42 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.209"
- subject="comment 9"
- date="2013-08-22T18:42:28Z"
- content="""
-Hehe, I ran into the option parser issue when implementing that change
-;-) So I moved to `git annex enableremote ... [keyid+=newkey]
-[keyid-=oldkey]` (where `+` is optional, for consistency) which doesn't
-prevent users from specifying a key by something starting with a sign.
-
-While it's certainly possible to tell git-annex to manage the authorized
-keys itself, users may have other reasons to remove a key so I'm not 
-sure it's a good idea. Also, what if someone forgets to add his/her new 
-key after revocation (it's still possible to decrypt after all)? If 
-another person updates the keyring afterwards, the first user will be
-denied further access, and will have to retrieve and reencrypt the
-\"cipher\" manually, which is not so trivial.
-
-
-I understand that asymmetric encryption needs special care, but Sam's 
-use case could be reproduced with that scheme I believe. For instance a
-user may superseed and revoke his/her old key; then new files would be 
-uploaded with the new one, but as long as the old key is not 
-compromised, I don't see why s/he should reupload everything instead of
-using the old key when pulling from the remote. Of course one may argue
-that the key shouldn't be revoked at the first place, but if it's used
-for other purposes (e.g., it's publicly available on a key server) it's
-good practice to revoke it IMHO.
-
-As for the removal of keys with pure asymmetric encryption, it is just
-required I think: Otherwise revoking a key would prevent any further 
-content to be encrypted. There I can't see any problem with git-annex 
-managing the keyring itself (beside the extra code to write :-P).
-
-All in all if we are to allow deletion/addition of keyIDs (and I think 
-we should!), I think it should be done for both `hybrid` and `pubkey` 
-schemes. Do you really want another syntax? I'd say clarify the manage 
-(plus maybe a warning when running the CLI) is enough, but true it's 
-easy to shoot oneself in the foot there...
-
-"""]]
diff --git a/doc/bugs/WEBDAV_443.mdwn b/doc/bugs/WEBDAV_443.mdwn
deleted file mode 100644
index cfde1a1a7..000000000
--- a/doc/bugs/WEBDAV_443.mdwn
+++ /dev/null
@@ -1,307 +0,0 @@
-What steps will reproduce the problem?
-
-```
-WEBDAV_USERNAME=pradermecker@yahoo.ca WEBDAV_PASSWORD=xxxxxx git annex initremote box.com type=webdav url=https://www.box.com/dav/git-annex chunksize=75mb encryption=none
-```
-
-What is the expected output? What do you see instead?
-
-I have: 
-```
-git-annex: WebDAV failed to write file: FailedConnectionException "www.box.com" 443: user error
-```
-# What version of git-annex are you using? On what operating system?
-
-```
-git-annex version: 4.20130314
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-```
-Archlinux 64: https://aur.archlinux.org/packages/git-annex/
-
-# Please provide any additional information below.
-
-1. Try my password a couple of time. It works with Chrome, Firefox or cadaver
-2. I am using a zsh shell and try exporting both env. variables
-3. git-annex test has errors
-
-### Error in:   git-annex add:1           
-sha1foodup: openFile: does not exist (No such file or directory)
-Cases: 3  Tried: 2  Errors: 2  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: dir/foo: getFileStatus: does not exist (No such file or directory)
-### Failure in: git-annex add:2           
-add of subdir failed
-Cases: 3  Tried: 3  Errors: 2  Failures: 1
-----------------------------------------------------------------------
-reinject
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: sha1foo not found
-### Failure in: git-annex reinject/fromkey
-reinject failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-----------------------------------------------------------------------
-unannex
-Cases: 2  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex unannex:0:no content
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 2  Tried: 1  Errors: 1  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Error in:   git-annex unannex:1:with content
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 2  Tried: 2  Errors: 2  Failures: 0
-----------------------------------------------------------------------
-drop
-Cases: 3  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-git-annex: foo not found
-### Failure in: git-annex drop:0:no remotes
-drop wrongly succeeded with no known copy of file
-Cases: 3  Tried: 1  Errors: 0  Failures: 1warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Error in:   git-annex drop:1:with remote
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 3  Tried: 2  Errors: 1  Failures: 1warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Error in:   git-annex drop:2:untrusted remote
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 3  Tried: 3  Errors: 2  Failures: 1
-----------------------------------------------------------------------
-get
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex get             
-foo: openFile: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-move
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex move            
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-copy
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex copy            
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-lock
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex unlock/lock     
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-edit
-Cases: 2  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Error in:   git-annex edit/commit:0   
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 2  Tried: 1  Errors: 1  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Error in:   git-annex edit/commit:1   
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 2  Tried: 2  Errors: 2  Failures: 0
-----------------------------------------------------------------------
-fix
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex fix             
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-trust
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-Cases: 1  Tried: 1  Errors: 0  Failures: 0
-----------------------------------------------------------------------
-fsck
-Cases: 4  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Failure in: git-annex fsck:0          
-fsck failed to fail with numcopies unsatisfied
-Cases: 4  Tried: 2  Errors: 0  Failures: 1warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Failure in: git-annex fsck:2          
-fsck failed to fail with content only available in untrusted (current) repository
-Cases: 4  Tried: 3  Errors: 0  Failures: 2warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-git-annex: sha1foo not found
-### Failure in: git-annex fsck:3          
-fsck failed to fail with content not replicated to enough non-untrusted repositories
-Cases: 4  Tried: 4  Errors: 0  Failures: 3
-----------------------------------------------------------------------
-migrate
-Cases: 2  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex migrate:0       
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 2  Tried: 1  Errors: 1  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex migrate:1       
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 2  Tried: 2  Errors: 2  Failures: 0
-----------------------------------------------------------------------
- unused
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-git-annex: sha1foo not found
-fatal: pathspec 'foo' did not match any files
-### Failure in: git-annex unused/dropunused
-git rm failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-----------------------------------------------------------------------
-describe
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-Cases: 1  Tried: 1  Errors: 0  Failures: 0
-----------------------------------------------------------------------
-find
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex find            
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-merge
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-Cases: 1  Tried: 1  Errors: 0  Failures: 0
-----------------------------------------------------------------------
-status
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-{"command":"status","supported backends":["SHA256E","SHA1E","SHA512E","SHA224E","SHA384E","SHA256","SHA1","SHA512","SHA224","SHA384","WORM","URL"],"supported remote types":["git","S3","bup","directory","rsync","web","webdav","glacier","hook"],"repository mode":"indirect","trusted repositories":[],"semitrusted repositories":[{"uuid":"00000000-0000-0000-0000-000000000001","description":"web","here":false},{"uuid":"80db3ccc-8c73-4279-b803-1b02c91dd158","description":".t/tmprepo0","here":true},{"uuid":"c01ef662-caa7-46d1-95de-544bee8b08f1","description":"origin (test repo)","here":false}],"untrusted repositories":[],"dead repositories":[],"available local disk space":"75 gigabytes (+1 megabyte reserved)","local annex keys":0,"local annex size":"0 bytes","known annex keys":0,"known annex size":"0 bytes","bloom filter size":"16 mebibytes (0% full)","success":true}
-Cases: 1  Tried: 1  Errors: 0  Failures: 0
-----------------------------------------------------------------------
-version
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex version: 4.20130314
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-Cases: 1  Tried: 1  Errors: 0  Failures: 0
-----------------------------------------------------------------------
-sync
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-# On branch master
-#
-# Initial commit
-#
-nothing to commit (create/copy files and use "git add" to track)
-### Failure in: git-annex sync            
-sync failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-----------------------------------------------------------------------
-sync regression
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-git-annex: foo not found
-git-annex: foo not found
-# On branch master
-#
-# Initial commit
-#
-nothing to commit (create/copy files and use "git add" to track)
-### Failure in: git-annex sync_regression 
-sync failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-----------------------------------------------------------------------
-map
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-Cases: 1  Tried: 1  Errors: 0  Failures: 0
-----------------------------------------------------------------------
-uninit
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex uninit          
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-upgrade
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-Cases: 1  Tried: 1  Errors: 0  Failures: 0
-----------------------------------------------------------------------
-whereis
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-### Error in:   git-annex whereis         
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-hook remote
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Error in:   git-annex hook remote     
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-directory remote
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Error in:   git-annex directory remote
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-rsync remote
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Error in:   git-annex rsync remote    
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-bup remote
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-Cases: 1  Tried: 1  Errors: 0  Failures: 0
-----------------------------------------------------------------------
-crypto
-Cases: 1  Tried: 0  Errors: 0  Failures: 0warning: remote HEAD refers to nonexistent ref, unable to checkout.
-
-git-annex: foo not found
-### Error in:   git-annex crypto          
-foo: getSymbolicLinkStatus: does not exist (No such file or directory)
-Cases: 1  Tried: 1  Errors: 1  Failures: 0
-----------------------------------------------------------------------
-Some tests failed!
-  (This could be due to a bug in git-annex, or an incompatability
-   with utilities, such as git, installed on this system.)
-
-> (The test suite output suggests to me that it was run on a system
-> that does not support symlinks, and may be broken in some other way
-> as well, but is not relevant to this bug report.)
-> --[[Joey]] 
-
-> Closing this bug since the bug submitter cannot reproduce it and
-> had many problems that seems to point at a bad build. [[done]] --[[Joey]]
diff --git a/doc/bugs/WEBDAV_443/comment_10_9ee2c5ed44295455af890caee7b06f1a._comment b/doc/bugs/WEBDAV_443/comment_10_9ee2c5ed44295455af890caee7b06f1a._comment
deleted file mode 100644
index 38c38e019..000000000
--- a/doc/bugs/WEBDAV_443/comment_10_9ee2c5ed44295455af890caee7b06f1a._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="195.244.162.7"
- subject="comment 10"
- date="2013-03-18T15:47:19Z"
- content="""
-Ok, I will try that.
-
-For your information, I have rebuild the aur package inside a VM using the latest master. All tests passed.
-
-Now I get a new error message with WEBDAV saying:
-
-```
-git-annex: WebDAV failed to write file: \"Conflict\": user error
-```
-
-As a note the current aur build is rather cumbersome because it needs to rebuild a lot of packages using cabal. I believe this is due to a few missing dependencies in the Arch repos [haskell-core] and [haskell-web] such as uuid, SafeSemaphore or c2hs.
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_11_863a7d315212c9a8ab8f6fafa5d1b7f5._comment b/doc/bugs/WEBDAV_443/comment_11_863a7d315212c9a8ab8f6fafa5d1b7f5._comment
deleted file mode 100644
index c58c70c21..000000000
--- a/doc/bugs/WEBDAV_443/comment_11_863a7d315212c9a8ab8f6fafa5d1b7f5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="195.244.162.7"
- subject="comment 11"
- date="2013-03-18T16:24:52Z"
- content="""
-FYI, it is a bit heavy for me to try the standalone version as it is 32 bits only (I am on 64-bits)
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_12_c17a4e23011e0a917dbe0ecf7e9f0cb5._comment b/doc/bugs/WEBDAV_443/comment_12_c17a4e23011e0a917dbe0ecf7e9f0cb5._comment
deleted file mode 100644
index be045c407..000000000
--- a/doc/bugs/WEBDAV_443/comment_12_c17a4e23011e0a917dbe0ecf7e9f0cb5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 12"
- date="2013-03-18T16:33:31Z"
- content="""
-The standalone version works on either architecture, it does not depend on any system libraries, thus the name \"standalone\".
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_13_3414416ff455d2fd1a7c7e7c4554b54d._comment b/doc/bugs/WEBDAV_443/comment_13_3414416ff455d2fd1a7c7e7c4554b54d._comment
deleted file mode 100644
index 0a3297f71..000000000
--- a/doc/bugs/WEBDAV_443/comment_13_3414416ff455d2fd1a7c7e7c4554b54d._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="195.244.162.7"
- subject="comment 13"
- date="2013-03-18T16:39:58Z"
- content="""
-I actually don't know if it has something to do with 32 or 64 bits but with the standalone I have got:
-/opt/git-annex.linux/runshell: line 69: /opt/git-annex.linux/bin/git-annex-shell: No such file or directory
-
-I have tried both the aur standalone and directly downloading the tarball.
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_14_e1da141eefb0445c217e5f5c119356da._comment b/doc/bugs/WEBDAV_443/comment_14_e1da141eefb0445c217e5f5c119356da._comment
deleted file mode 100644
index 5097df183..000000000
--- a/doc/bugs/WEBDAV_443/comment_14_e1da141eefb0445c217e5f5c119356da._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 14"
- date="2013-03-18T16:54:02Z"
- content="""
-Given that line 69 of runshell is a newline, and that runshell does not ever try to run git-annex-shell, I wonder what you downloaded exactly...
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_15_41c3134bcc222b97bf183559723713d9._comment b/doc/bugs/WEBDAV_443/comment_15_41c3134bcc222b97bf183559723713d9._comment
deleted file mode 100644
index 5bf5bafe4..000000000
--- a/doc/bugs/WEBDAV_443/comment_15_41c3134bcc222b97bf183559723713d9._comment
+++ /dev/null
@@ -1,27 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="195.244.162.7"
- subject="comment 15"
- date="2013-03-18T19:07:31Z"
- content="""
-Euh. I actually feel stupid enough with this but ...
-
-I have try first with your link and it gives me:
-
-```
-./runshell: line 75: /home/vagrant/programs/git-annex.linux/bin/sh: No such file or directory
-```
-
-As I told you I then try the AUR package : https://aur.archlinux.org/packages/git-annex-standalone/
-
-And it does give me the same error on line 69.
-
-It is the same line (3 lines before the end):
-
-```
-exec \"$cmd\" \"$@\"
-```
-
-I really don't get it because the file is there ... and the first sanity checks of the script have pass.
-
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_16_89621b526065b5bef753ce75db1af7b5._comment b/doc/bugs/WEBDAV_443/comment_16_89621b526065b5bef753ce75db1af7b5._comment
deleted file mode 100644
index 059a8ee00..000000000
--- a/doc/bugs/WEBDAV_443/comment_16_89621b526065b5bef753ce75db1af7b5._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="195.244.162.7"
- subject="comment 16"
- date="2013-03-18T19:31:42Z"
- content="""
-Actually it is even worse ...
-
-With your link, line 75 is actually 2 lines below (sh).
-
-So same command (runshell), same error, different places (I guess it is always the last line executed) ...
-
-Is it supposed to work fine in 64 bits also ?
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_17_131a1b65c8008cf9f02c93d4fb75720b._comment b/doc/bugs/WEBDAV_443/comment_17_131a1b65c8008cf9f02c93d4fb75720b._comment
deleted file mode 100644
index 515976b85..000000000
--- a/doc/bugs/WEBDAV_443/comment_17_131a1b65c8008cf9f02c93d4fb75720b._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 7"
- date="2013-03-18T23:05:26Z"
- content="""
-The standalone linux tarball will work on 64 or 32 bit systems, as long as they are capable of linking 32 bit elf executables. I cannot test if Arch Linux is incapable of this.
-
-I'm getting a bit tired of wild tangents, can we you just find someplace, be it a Debian chroot or whatever, to run the standalone linux tarball and test if DAV works there?
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_18_b4f894a0b9ebb84ab73f6ffcf0778090._comment b/doc/bugs/WEBDAV_443/comment_18_b4f894a0b9ebb84ab73f6ffcf0778090._comment
deleted file mode 100644
index fe25b98e6..000000000
--- a/doc/bugs/WEBDAV_443/comment_18_b4f894a0b9ebb84ab73f6ffcf0778090._comment
+++ /dev/null
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="195.244.162.7"
- subject="It works !"
- date="2013-03-19T10:40:31Z"
- content="""
-Sorry for the wild tangents.
-
-It is now working. I am not sure what went wrong.
-
-For the record here are the steps I took (all using the Git annex UI):
-
-* Set up removable media -> OK
-* Set up remote SSH -> missing lsof -> install it -> everything OK
-* Set up S3  -> had issue with time -> solve it with ntp -> everything OK
-* Try again WebDav -> \"Conflict\" message -> try using another dir -> everything OK
-
-There might be a \"cleanup after error problem\" somewhere that would explain the conflict message I have received.
-
-Again for the record, I made it works inside a VM using the AUR \"git-annex 4.20130314-1\" (not the standalone). The only change I made on the PKGBUILD was to install everything with cabal except for the packages in the [haskell-core] Arch repo. I know you are not aware with Arch but basically I choose not to rely on the [haskell-web] Arch repo.
-
-I will try again at home on my laptop and I will try the standalone as well.
-
-Thanks you so much for the wonderful product !
-
-Cheers
-
-
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_1_c6572ca1eaaf89b01c0ed99a4058412f._comment b/doc/bugs/WEBDAV_443/comment_1_c6572ca1eaaf89b01c0ed99a4058412f._comment
deleted file mode 100644
index f474fe488..000000000
--- a/doc/bugs/WEBDAV_443/comment_1_c6572ca1eaaf89b01c0ed99a4058412f._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-16T15:35:05Z"
- content="""
-The i386 standalone build for 4.20130314, which is IIRC repackaged by Arch linux, was made using a known broken webdav library. I've since updated that build to use a new version of webdav. Since it only affected that one build, I do not plan to do a full re-release with a new version number.
-
-Probably Arch needs to update their package.
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_2_a357969cde382a91e13920ee1e9f711c._comment b/doc/bugs/WEBDAV_443/comment_2_a357969cde382a91e13920ee1e9f711c._comment
deleted file mode 100644
index 522685670..000000000
--- a/doc/bugs/WEBDAV_443/comment_2_a357969cde382a91e13920ee1e9f711c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="81.244.205.197"
- subject="Thanks"
- date="2013-03-16T15:46:45Z"
- content="""
-Thanks for your quick comment ! I was about to get crazy trying my password again and again ;-)
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_3_213815d6b827d467c60f3e8af925813b._comment b/doc/bugs/WEBDAV_443/comment_3_213815d6b827d467c60f3e8af925813b._comment
deleted file mode 100644
index 60f7ef9d3..000000000
--- a/doc/bugs/WEBDAV_443/comment_3_213815d6b827d467c60f3e8af925813b._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-03-17T21:07:50Z"
- content="""
-Seems that I misdiagnosed this. The error message from the bad TLS library was about a had certificate, not \"user error\" (which, confusingly, does not mean what user error normally means!).
-
-Also, I see you reported this at <https://aur.archlinux.org/packages/git-annex/>, so you're using that build and not the \"git-annex-bin\" build at <https://aur.archlinux.org/packages.php?ID=63503>. The Arch Linux build that's done from source couldn't be affected by the Debian-spefific TLS bug anyway.
-
-I am reopening this bug report. 
-
-Now, FailedConnectionException could be any of several things, but I noticed that someone else (perhaps cooindidentially using Arch Linux) reported the same error message here: [[Proxy_support]]. I wonder if you perhaps also have a http proxy that could be causing trouble.
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_4_b775be4b722fc7124d9fbe2d5d01cc9f._comment b/doc/bugs/WEBDAV_443/comment_4_b775be4b722fc7124d9fbe2d5d01cc9f._comment
deleted file mode 100644
index 12767d961..000000000
--- a/doc/bugs/WEBDAV_443/comment_4_b775be4b722fc7124d9fbe2d5d01cc9f._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 4"
- date="2013-03-17T21:19:20Z"
- content="""
-Digging into your error message a bit more, it looks like this is not a http proxy (or if it is, it's letting some connections through). 
-
-git-annex is testing the box.com WebDAV server, by performing 3 actions:
-
-1. Creating the requested subdirectory on it, in your case \"git-annex\". 
-2. Creating an empty file to that directory, named \"git-annex-test\"
-3. Deleting the file.
-
-Step 2 is failing. Which sort of suggests step 1 succeeded, but who knows..
-
-So, if you go look at your files on box.com, do you have a git-annex directory?
-
-Does git-annex/git-annex-test exist?
-
-Does it also fail if you use a different directory, like https://www.box.com/dav/git-annex2 ?
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_5_c4ea745da437e56b2426d1c2c00dfcec._comment b/doc/bugs/WEBDAV_443/comment_5_c4ea745da437e56b2426d1c2c00dfcec._comment
deleted file mode 100644
index e99f36524..000000000
--- a/doc/bugs/WEBDAV_443/comment_5_c4ea745da437e56b2426d1c2c00dfcec._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="81.244.157.3"
- subject="comment 5"
- date="2013-03-17T22:03:22Z"
- content="""
-No there is no directory created on box.com. I have actually tried with other names without success. I did even try to create the directory myself and use this one but it makes no difference.
-
-I am not sure to understand what 443 means.
-
-To be sure it is not a local config problem on my computer, I have tried to put a file to box using cadaver: cadaver works just fine (create dir, upload, delete file).
-
-After your comment, I actually rebuild the package using master. I still have the same error with WebDav but now all tests pass (git annex test)
-
-Let me know if you need me to do further investigation. Thanks.
-
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_6_ef05c0ae88fee9c626922c6064ffdf1e._comment b/doc/bugs/WEBDAV_443/comment_6_ef05c0ae88fee9c626922c6064ffdf1e._comment
deleted file mode 100644
index 0d3261646..000000000
--- a/doc/bugs/WEBDAV_443/comment_6_ef05c0ae88fee9c626922c6064ffdf1e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="81.244.157.3"
- subject="comment 6"
- date="2013-03-17T22:07:06Z"
- content="""
-I have also tried with the gui and got the same error.
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_7_eecabe8d5ed564cb540450770ca7d0b6._comment b/doc/bugs/WEBDAV_443/comment_7_eecabe8d5ed564cb540450770ca7d0b6._comment
deleted file mode 100644
index d6d3241bf..000000000
--- a/doc/bugs/WEBDAV_443/comment_7_eecabe8d5ed564cb540450770ca7d0b6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 7"
- date="2013-03-18T00:18:52Z"
- content="""
-443 is the port used for https.
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_8_7f77ba8ebd90186d3b3949ae529ba393._comment b/doc/bugs/WEBDAV_443/comment_8_7f77ba8ebd90186d3b3949ae529ba393._comment
deleted file mode 100644
index 68d6d5b83..000000000
--- a/doc/bugs/WEBDAV_443/comment_8_7f77ba8ebd90186d3b3949ae529ba393._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://pradermecker.myopenid.com/"
- ip="195.244.162.7"
- subject="comment 8"
- date="2013-03-18T08:33:04Z"
- content="""
-Yes, of course, I know about 443.
-
-I was just surprised to see it in the error message (where as a code my mind was expecting a http error code).
-
-What I meant is that I don't really see how it fits in the current error message.
-"""]]
diff --git a/doc/bugs/WEBDAV_443/comment_9_87ebdc92b48d672964fb3f248c53600f._comment b/doc/bugs/WEBDAV_443/comment_9_87ebdc92b48d672964fb3f248c53600f._comment
deleted file mode 100644
index eb51fe641..000000000
--- a/doc/bugs/WEBDAV_443/comment_9_87ebdc92b48d672964fb3f248c53600f._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 9"
- date="2013-03-18T15:04:00Z"
- content="""
-I think what you need to do is try installing the [Linux standalone tarball](http://downloads.kitenet.net/git-annex/linux/current/) and see if it works with WebDAV. We need to rule out this being a bad build on the Arch side. The Linux standalone tarball works with box.com for me.
-
-"""]]
diff --git a/doc/bugs/WORM:_Handle_long_filenames_correctly.mdwn b/doc/bugs/WORM:_Handle_long_filenames_correctly.mdwn
deleted file mode 100644
index 3c9374100..000000000
--- a/doc/bugs/WORM:_Handle_long_filenames_correctly.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-I have files with very long filenames on an xfs at home. On my laptop the annex should have been checked out on an encfs, but there filenames can't be as long as on the xfs. So perhaps it would be good to limit the keysize to a sane substring of the filename e.g. use only the first 120 characters.
-
-> Since there seems no strong argument for a WORM100, and better options
-> exist, closing. [[done]] --[[Joey]] 
diff --git a/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_1_77aa9cafbe20367a41377f3edccc9ddb._comment b/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_1_77aa9cafbe20367a41377f3edccc9ddb._comment
deleted file mode 100644
index 41d3afb3e..000000000
--- a/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_1_77aa9cafbe20367a41377f3edccc9ddb._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-04-08T17:14:25Z"
- content="""
-Seems like you probably have files in git with nearly as long filenames as the key files. Course, you can rename those yourself.
-
-This couldn't be changed directly in WORM without some ugly transition, but it would be possible to implement it as a WORM100 or so. OTOH, if you're going to git annex migrate, you might as well use SHA1.
-"""]]
diff --git a/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_2_fe735d728878d889ccd34ec12b3a7dea._comment b/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_2_fe735d728878d889ccd34ec12b3a7dea._comment
deleted file mode 100644
index d00191f9d..000000000
--- a/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_2_fe735d728878d889ccd34ec12b3a7dea._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2011-04-08T22:02:41Z"
- content="""
-What if your files have the same prefix and it happens to be 100 chars long? This can not be solved within WORM, but as Joey pointed out, SHA* exists.
-"""]]
diff --git a/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_3_2bf0f02d27190578e8f4a32ddb195a0a._comment b/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_3_2bf0f02d27190578e8f4a32ddb195a0a._comment
deleted file mode 100644
index d9c291b17..000000000
--- a/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_3_2bf0f02d27190578e8f4a32ddb195a0a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 3"
- date="2011-04-09T20:11:59Z"
- content="""
-I wouldn't say it's completly impossible for a WORM100 to work. It would just have the contract that the pair of mtime+100chars has to be unique for each unique piece of data.
-
-But, I have yet to be convinced there's any point, since SHA1 exists.
-"""]]
diff --git a/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_4_8f7ba9372463863dda5aae13205861bf._comment b/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_4_8f7ba9372463863dda5aae13205861bf._comment
deleted file mode 100644
index 5c08cad6e..000000000
--- a/doc/bugs/WORM:_Handle_long_filenames_correctly/comment_4_8f7ba9372463863dda5aae13205861bf._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 4"
- date="2011-04-09T23:45:28Z"
- content="""
-mtime+100chars can still get collisions and a _lot_ easier than even SHA1. This introduces more problems that it solves, imo.
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults.mdwn b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults.mdwn
deleted file mode 100644
index f3833b3b3..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-After fixing a few things - see [[bugs/the tip at commit 6cecc26206c4a539999b04664136c6f785211a41 disables the watch command on OSX]], [[bugs/Missing dependancy in commit 6cecc26206c4a539999b04664136c6f785211a41]] and [[bugs/Fix for opening a browser on a mac (or xdg-open on linux/bsd?)]] I tried the watch command on my ~180gig annex of stuff. This might be yet again related to the issue of [[bugs/Issue on OSX with some system limits]]
-
-the watch command segfaults
-
-<pre>
-x00:annex jtang$ git annex watch --foreground -d
-watch . [2012-07-26 12:27:16 IST] read: git ["--git-dir=/Users/jtang/annex/.git","--work-tree=/Users/jtang/annex","show-ref","git-annex"] 
-[2012-07-26 12:27:16 IST] read: git ["--git-dir=/Users/jtang/annex/.git","--work-tree=/Users/jtang/annex","show-ref","--hash","refs/heads/git-annex"] 
-[2012-07-26 12:27:16 IST] read: git ["--git-dir=/Users/jtang/annex/.git","--work-tree=/Users/jtang/annex","log","refs/heads/git-annex..38d3f769ef004b96b6d640cfb59a45f7b4edf5f6","--oneline","-n1"] 
-[2012-07-26 12:27:16 IST] read: git ["--git-dir=/Users/jtang/annex/.git","--work-tree=/Users/jtang/annex","log","refs/heads/git-annex..ebabe9c92516c350a30126037173080648f5930b","--oneline","-n1"] 
-[2012-07-26 12:27:16 IST] read: git ["--git-dir=/Users/jtang/annex/.git","--work-tree=/Users/jtang/annex","log","refs/heads/git-annex..d36d8d88847decc2320f0be22892ad94a8abe594","--oneline","-n1"] 
-[2012-07-26 12:27:16 IST] read: git ["--git-dir=/Users/jtang/annex/.git","--work-tree=/Users/jtang/annex","log","refs/heads/git-annex..aaa62a8191b3c964fdf546077049f626e8561b22","--oneline","-n1"] 
-[2012-07-26 12:27:16 IST] chat: git ["--git-dir=/Users/jtang/annex/.git","--work-tree=/Users/jtang/annex","cat-file","--batch"] 
-(scanning...) error: git-annex died of signal 11
-</pre>
-
-The above was done on the usual OSX 10.7 system that I have.
-
----
-
-I'll try and bisect it and find out where the problem first appeared, does the tests currently test the watch command? (also my comments seem to get moderated whether i use my openid account with google or with the native ikiwiki account, so some comments might be hidden)
-
-> The test suite does not currently test the watch command, unfortunatly.
->
-> Wow, I had not noticed the 30 pending moderated comments.. Let them all
-> thru, and I guess I'll turn off comment spam filtering for now, since
-> there has apparently been none. --[[Joey]] 
-
----
-
-> Seems this segfault is fixed. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_10_6c872dff4fcc63c16bf69d1e96891c89._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_10_6c872dff4fcc63c16bf69d1e96891c89._comment
deleted file mode 100644
index 952ffadc4..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_10_6c872dff4fcc63c16bf69d1e96891c89._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="jtang"
- ip="79.97.135.214"
- subject="comment 10"
- date="2012-07-29T10:49:05Z"
- content="""
-This is looking good, no more segfaulting.
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_1_5cad24007f819e4be193123dab0d511a._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_1_5cad24007f819e4be193123dab0d511a._comment
deleted file mode 100644
index 23a4165a4..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_1_5cad24007f819e4be193123dab0d511a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.189"
- subject="not good.."
- date="2012-07-26T17:09:16Z"
- content="""
-Do you see the segfault in a repo with fewer files?
-
-
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_2_d449bf656a59d424833f9ab5a7fb4e82._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_2_d449bf656a59d424833f9ab5a7fb4e82._comment
deleted file mode 100644
index 04b7ed1ae..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_2_d449bf656a59d424833f9ab5a7fb4e82._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.189"
- subject="comment 2"
- date="2012-07-26T17:09:59Z"
- content="""
-Also, you might try bisecting to find whatever commit it first started segfaulting on.
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_3_ffb1ce41477ad60840abd7a89a133067._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_3_ffb1ce41477ad60840abd7a89a133067._comment
deleted file mode 100644
index 42f59d1bc..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_3_ffb1ce41477ad60840abd7a89a133067._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="jtang"
- ip="79.97.135.214"
- subject="comment 3"
- date="2012-07-26T17:11:55Z"
- content="""
-It fails on repos with either no files or smaller repos.
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_4_cebbc138c6861c086bb7937b54f5adbc._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_4_cebbc138c6861c086bb7937b54f5adbc._comment
deleted file mode 100644
index 71e810291..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_4_cebbc138c6861c086bb7937b54f5adbc._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="jtang"
- ip="79.97.135.214"
- subject="comment 4"
- date="2012-07-26T17:50:42Z"
- content="""
-It just occurred to me that bisecting won't help much, as the watch command was disabled accidentally in earlier commits and doing a script for bisecting is going to be as much work as just stepping through and debugging the issue with a debugger (i might need to fire up gdb on a mac (this wont be fun))
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_5_5e27737a5bb0e9e46c98708700318e67._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_5_5e27737a5bb0e9e46c98708700318e67._comment
deleted file mode 100644
index 8f781ed97..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_5_5e27737a5bb0e9e46c98708700318e67._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 5"
- date="2012-07-27T12:20:07Z"
- content="""
-After some debugging, I looked at the Utility/libkqueue.c and used it as a test, it seems to be hanging/segfaulting around the call to that library. Annoyingly I get segfaults from the library every so often on OSX, it's pretty a random event.
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_6_1f92da712232d050e085a4f39063d7a6._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_6_1f92da712232d050e085a4f39063d7a6._comment
deleted file mode 100644
index 2aa866410..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_6_1f92da712232d050e085a4f39063d7a6._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.20"
- subject="comment 6"
- date="2012-07-27T16:34:45Z"
- content="""
-Are you seeing libkqueue crash when it's called from a debugger or C program, rather than from Haskell?
-
-Are you building for 32 or 64 bit? You might try getting the 32 bit version of GCC (or The Haskell Platform) and see if it does better. There is a known GCC crashes on 64 bit OSX involving C libraries,
-although this bug report doesn't seem to apply, since we're not using ghci <http://hackage.haskell.org/trac/ghc/ticket/7040>.
-
-Are you building with cabal, or using the Makefile?
-
-You might try reverting git commit da4c506d61115236f3e43dd0bd17f30cd54df950
-
-You might try disabling the -threaded option in the cabal file or Makefile.
-
-I ssh'd to the OSX box I have an account on, and confirmed that git-annex watch still works there as of the current head of the `assistant` branch. That's a 64 bit GHC system, FWIW.
-
-Do you see the crash when building from the `master` branch, or only `assistant`? Master has the watch command, but it's much out of date, so this will tell if the problem was introduced recently... and you might still have to bisect it since I can't reproduce it. :(
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_7_4153dc8029c545f8e86584a38bd536fb._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_7_4153dc8029c545f8e86584a38bd536fb._comment
deleted file mode 100644
index ccb4593ec..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_7_4153dc8029c545f8e86584a38bd536fb._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 7"
- date="2012-07-27T17:23:24Z"
- content="""
-I'm using make and a 64bit version of haskell-platform, it's fine on the master branch. It's just crashing on the assistant branch, I'm just thinking out loud, but could I share the binaries that I have with you (I'd like to grab your binaries too) to see see if its just some silly problem with my build environment.
-
-I'm seeing the crash when I'm running git-annex (in haskell), when I run libkqueue in a debugger it behaves randomly, is mostly succeeds, but every so often it fails. A back trace reveals nothing so I am a bit at a loss.
-
-I've tried disabling the threaded option, but it still crashes, I will give it another try later when I get home. The problem seems to occur on my desktop mac in work and my home mac, however it is fine on my linux machines.
-
-Could I ask which version of OSX do you have access to? is it 10.6 or 10.7 ?
-
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_8_f85b6eb5bfd28ffc6973fb4ab0fe4337._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_8_f85b6eb5bfd28ffc6973fb4ab0fe4337._comment
deleted file mode 100644
index cbbd2933c..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_8_f85b6eb5bfd28ffc6973fb4ab0fe4337._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.20"
- subject="comment 8"
- date="2012-07-27T18:10:06Z"
- content="""
-I've reproduced a crash on OSX, involving not kqueue, but the WebApp's use of getaddrinfo. I've fixed that, but several things you've said in this bug report don't 100% add up to this being the same crash you've been seeing (for one thing, this can't affect `git annex watch`), so I'll wait for you to confirm.
-"""]]
diff --git a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_9_c747c488461c98cd285b51d3afc2c3eb._comment b/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_9_c747c488461c98cd285b51d3afc2c3eb._comment
deleted file mode 100644
index b23ae0125..000000000
--- a/doc/bugs/Watch_command_as_of_commit_6cecc26206c4a539999b04664136c6f785211a41_segfaults/comment_9_c747c488461c98cd285b51d3afc2c3eb._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="jtang"
- ip="79.97.135.214"
- subject="comment 9"
- date="2012-07-27T18:17:45Z"
- content="""
-Ah, it's alive, I'm testing on my home machine right now and it's functioning as expected. I've tested on my work machine as well and the watch command works as expected! (short of the existing system limits which fails for my bigger annexes).
-
-Apologies for sending you on the wrong path with the kqueue path. I reckon if I give this a good testing over the weekend is a good idea before closing this bug, I will report back in a few days on this after giving a thrashing of files!
-"""]]
diff --git a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist.mdwn b/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist.mdwn
deleted file mode 100644
index f798fe2ea..000000000
--- a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-### Please describe the problem.
-
-When starting an git annex webapp in my documents repository, i get the error message, that the watcher thread has died. The error message seems to be arising from the fact, that a watcher thread for an empty string should be started, which does not work.
-
-### What steps will reproduce the problem?
-
-I've no idea, how to reproduce this in another repostory.
-
-### What version of git-annex are you using? On what operating system?
-
-ii  git-annex  4.20130709   i386   manage files with git, without checking their contents into git
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-Watcher crashed: addWatch: does not exist (No such file or directory)
-[2013-07-14 10:30:35 CEST] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory)
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; see my comment --[[Joey]]
diff --git a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_1_24f511a8103727894c6e96798a559870._comment b/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_1_24f511a8103727894c6e96798a559870._comment
deleted file mode 100644
index 54808de57..000000000
--- a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_1_24f511a8103727894c6e96798a559870._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.90"
- subject="comment 1"
- date="2013-07-17T19:33:43Z"
- content="""
-Are you seeing this every time you start the webapp? Because I see a way it could crash, but only if, for example, a directory gets moved or deleted right when it's starting up. That would look just like the crash you've reported, but would seem to be an unusual case that would be unlikely to happen repeatedly.
-
-I've put in a fix for that crash.
-"""]]
diff --git a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_2_e14eddbc09cadbf1e4dbbb0c07e0e5b0._comment b/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_2_e14eddbc09cadbf1e4dbbb0c07e0e5b0._comment
deleted file mode 100644
index 9f3dd80f5..000000000
--- a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_2_e14eddbc09cadbf1e4dbbb0c07e0e5b0._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkptNW1PzrVjYlJWP_9e499uH0mjnBV6GQ"
- nickname="Christian"
- subject="comment 2"
- date="2013-07-19T06:14:05Z"
- content="""
-I see the problem always i start the assistant. Even when i don't touch the repository otherwise. But there is a funny observation: I have multiple seperate repositories: there are two old ones, that were created some months ago (upper bound: one year). Those two (seperate) repositories show the addWatch problem (on multiple machines). A newly created repository does not show the problem.
-
-So i suspect that those old repositories behave in some direction differently. Is this possible? I could also give you a clone of one repository.
-"""]]
diff --git a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_3_513fae4d379008f954a307be8df34976._comment b/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_3_513fae4d379008f954a307be8df34976._comment
deleted file mode 100644
index a85470f68..000000000
--- a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_3_513fae4d379008f954a307be8df34976._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkptNW1PzrVjYlJWP_9e499uH0mjnBV6GQ"
- nickname="Christian"
- subject="comment 3"
- date="2013-07-19T06:57:39Z"
- content="""
-Oh, I think i found a problem with the inotify_add_watch. I checked the strace and:
-
-    [pid 19346] inotify_add_watch(63, \"./Perry Rhodan - Atlan\", IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE) = 137
-    [pid 19346] inotify_add_watch(63, \"./Perry Rhodan - Atlan/Atlan Blaue- Silberbnde\", IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE) = -1 ENOENT (No such file or directory)
-
-The problem is that there seems to be an encoding problem. There should be a german Umlaut in Silberb[ae]nde. The directory name is not valid encoded.
-"""]]
diff --git a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_4_172eaeb3bb8b502379695aba35f96120._comment b/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_4_172eaeb3bb8b502379695aba35f96120._comment
deleted file mode 100644
index 84a84dfb8..000000000
--- a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_4_172eaeb3bb8b502379695aba35f96120._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkptNW1PzrVjYlJWP_9e499uH0mjnBV6GQ"
- nickname="Christian"
- subject="comment 4"
- date="2013-07-19T19:00:23Z"
- content="""
-So it is probably not only an assumption. After fixing the filenames with a script from
-
-http://askubuntu.com/questions/113188/character-encoding-problem-with-filenames-find-broken-filenames
-
-The watcher thread did survive, and the assistant is syncing just fine.
-"""]]
diff --git a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_5_8adb9de82cc8581422734acc66dd094c._comment b/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_5_8adb9de82cc8581422734acc66dd094c._comment
deleted file mode 100644
index cb95ab913..000000000
--- a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_5_8adb9de82cc8581422734acc66dd094c._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 5"
- date="2013-07-20T17:39:48Z"
- content="""
-Ok, I was able to reproduce this problem, although only when using LANG=C. 
-
-With a utf8 locale, it doesn't mind the Umlaut, and even works on directories containing invalid unicode characters 
-(0xd801 and 0xffff)
-"""]]
diff --git a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_6_02f0beef1188bfa336bf4220eb5c6286._comment b/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_6_02f0beef1188bfa336bf4220eb5c6286._comment
deleted file mode 100644
index a21352693..000000000
--- a/doc/bugs/Watcher_crashed:_addWatch:_does_not_exist/comment_6_02f0beef1188bfa336bf4220eb5c6286._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 6"
- date="2013-07-20T22:31:02Z"
- content="""
-Isolated the bug to a problem with the upstream inotify library.
-<https://github.com/kolmodin/hinotify/issues/5> I've sent in a patch to that library that fixes the problem.
-
-Unfortunately, I cannot work around it in git-annex more than I already have. It'll no longer crash, but will skip over files or directories that contain characters not valid in the current locale.
-
-I have applied my patch to the haskell-hinotify package in Debian unstable, and have deployed fixed versions to all my linux autobuilds, including Android. (An Android user had mentioned also seeing this bug.)
-"""]]
diff --git a/doc/bugs/WebDAV_HandshakeFailed_.mdwn b/doc/bugs/WebDAV_HandshakeFailed_.mdwn
deleted file mode 100644
index 69be0c4b5..000000000
--- a/doc/bugs/WebDAV_HandshakeFailed_.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-When I attempt to add a Box.com special remote to my annex I get the following error:
-
-    git-annex: HandshakeFailed (Error_Protocol ("certificate rejected: certificate is not allowed to sign another certificate",True,CertificateUnknown))
-
-Running git-annex version: 3.20130207
-
-> Got that bug fixed in Debian and all builds updated. [[done]] --[[Joey]]
diff --git a/doc/bugs/WebDAV_HandshakeFailed_/comment_1_40499110ea43bc99ad9dd9f642da434c._comment b/doc/bugs/WebDAV_HandshakeFailed_/comment_1_40499110ea43bc99ad9dd9f642da434c._comment
deleted file mode 100644
index 9bcc489ee..000000000
--- a/doc/bugs/WebDAV_HandshakeFailed_/comment_1_40499110ea43bc99ad9dd9f642da434c._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlqOu7P4tb4D-Xo2pYrjln2NsAObtErliM"
- nickname="Alexander"
- subject="Same problem"
- date="2013-02-24T16:51:52Z"
- content="""
-Hello,
-
-same problem with box.com and german telekom (https://webdav.mediencenter.t-online.de).
-I'm using git-annex (3.20130216) from debian/unstable on amd64.
-git annex --debug is not helpful I think. Any other trace I can help with?
-
-Regards,
-Alexander
-"""]]
diff --git a/doc/bugs/WebDAV_HandshakeFailed_/comment_2_506712e8cc5b47b9bd69edf67ae54da7._comment b/doc/bugs/WebDAV_HandshakeFailed_/comment_2_506712e8cc5b47b9bd69edf67ae54da7._comment
deleted file mode 100644
index 53642bce4..000000000
--- a/doc/bugs/WebDAV_HandshakeFailed_/comment_2_506712e8cc5b47b9bd69edf67ae54da7._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.210"
- subject="comment 2"
- date="2013-02-24T19:09:14Z"
- content="""
-This is a reversion in version haskell-tls-extra-0.4.6.1. 
-
-Opened a bug about this: <https://github.com/vincenthz/hs-tls/issues/32>
-"""]]
diff --git a/doc/bugs/WebDAV_HandshakeFailed_/comment_3_5641481d9e9ed2b711b1516f1abc5c30._comment b/doc/bugs/WebDAV_HandshakeFailed_/comment_3_5641481d9e9ed2b711b1516f1abc5c30._comment
deleted file mode 100644
index 02bb0db11..000000000
--- a/doc/bugs/WebDAV_HandshakeFailed_/comment_3_5641481d9e9ed2b711b1516f1abc5c30._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="annexuser"
- ip="50.125.41.24"
- subject="comment 3"
- date="2013-03-15T18:45:49Z"
- content="""
-The [day 210 update](http://git-annex.branchable.com/design/assistant/blog/day_210__spring/) said that WebDAV should be working in the next release. I just tried it in 4.20130314 (standalone) and get the same `HandshakeFailed` failed error.
-"""]]
diff --git a/doc/bugs/WebDAV_HandshakeFailed_/comment_4_1d609de93fa66ce9dc802e67b5922243._comment b/doc/bugs/WebDAV_HandshakeFailed_/comment_4_1d609de93fa66ce9dc802e67b5922243._comment
deleted file mode 100644
index 5b91e1d5e..000000000
--- a/doc/bugs/WebDAV_HandshakeFailed_/comment_4_1d609de93fa66ce9dc802e67b5922243._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="which build?"
- date="2013-03-15T21:47:34Z"
- content="""
-Can you be more specific which build you are using?
-"""]]
diff --git a/doc/bugs/WebDAV_HandshakeFailed_/comment_5_62761882d30c1b02930c938cb8e30ed4._comment b/doc/bugs/WebDAV_HandshakeFailed_/comment_5_62761882d30c1b02930c938cb8e30ed4._comment
deleted file mode 100644
index dbb1a7e80..000000000
--- a/doc/bugs/WebDAV_HandshakeFailed_/comment_5_62761882d30c1b02930c938cb8e30ed4._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="annexuser"
- ip="50.125.41.24"
- subject="comment 5"
- date="2013-03-15T22:23:44Z"
- content="""
-    git-annex version: 4.20130314
-
-Linux i386 standalone build on Arch 64-bit.
-"""]]
diff --git a/doc/bugs/WebDAV_HandshakeFailed_/comment_6_acda8fae848ec486ce2a0b3dff3bd0a5._comment b/doc/bugs/WebDAV_HandshakeFailed_/comment_6_acda8fae848ec486ce2a0b3dff3bd0a5._comment
deleted file mode 100644
index 85678f1ac..000000000
--- a/doc/bugs/WebDAV_HandshakeFailed_/comment_6_acda8fae848ec486ce2a0b3dff3bd0a5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 6"
- date="2013-03-15T23:49:27Z"
- content="""
-Indeed, I forgot to upgrade that one. Did so and have replaced the autobuild.
-"""]]
diff --git a/doc/bugs/WebDAV_HandshakeFailed_/comment_7_6c51b6c7dd477d8911dd9a7a5c41ea2e._comment b/doc/bugs/WebDAV_HandshakeFailed_/comment_7_6c51b6c7dd477d8911dd9a7a5c41ea2e._comment
deleted file mode 100644
index 9a7036ff0..000000000
--- a/doc/bugs/WebDAV_HandshakeFailed_/comment_7_6c51b6c7dd477d8911dd9a7a5c41ea2e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="annexuser"
- ip="50.46.189.77"
- subject="comment 7"
- date="2013-03-17T01:29:48Z"
- content="""
-It's working now! Thanks!
-"""]]
diff --git a/doc/bugs/WebDAV_HandshakeFailed_/comment_8_e834f791d3000669fab25732a7c72ab3._comment b/doc/bugs/WebDAV_HandshakeFailed_/comment_8_e834f791d3000669fab25732a7c72ab3._comment
deleted file mode 100644
index 8858c8c49..000000000
--- a/doc/bugs/WebDAV_HandshakeFailed_/comment_8_e834f791d3000669fab25732a7c72ab3._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlqOu7P4tb4D-Xo2pYrjln2NsAObtErliM"
- nickname="Alexander"
- subject="box.com fixed"
- date="2013-03-29T15:15:31Z"
- content="""
-yes, box.com is now working. thanks.
-
-german telekom still doesn't work though, due to the lock/unlock issue; see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698379
-
-best regards,
-alexander
-"""]]
diff --git a/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn b/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn
deleted file mode 100644
index b3b0eea64..000000000
--- a/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn
+++ /dev/null
@@ -1,57 +0,0 @@
-## What steps will reproduce the problem?
-
-    ~$ git annex webapp
-
-
-* Add Another Local Repository (~/Direct) "Direct", keep separate (from existing repo) no repo type
-* Add Repository, ~/Indirect "Indirect", combine (with Direct) , repo type client
-* Syncing enabled on both
-
-Then
-
-    ~/Indirect$ git annex indirect
-    commit  ok
-    indirect  ok
-    ok
-    ~/Indirect$ touch ../Direct/Test.File
-    
-
-## What is the expected output? What do you see instead?
-
-That ~/Indirect/Test.File be a symlink into .git/annex/objects/.......
-
-Instead, it is not a symlink. However, doing
-
-    ~/Indirect$ git annex direct
-    ~/Indirect$ git annex indirect
-
-results in what I would expect (until the content of Direct/Test.File is changed, when it ceases to be a symlink in ~/Indirect once more)
-
-
-
-## What version of git-annex are you using? On what operating system?
-git-annex version: 4.20130405
-
-Ubuntu 12.10
-
-
-## Please provide any additional information below.
-
-Reading [[direct_mode]], I thought that I could have two repos on my computer, one direct, and one indirect, and if running the assistant, that I could gain the security of retaining old versions, as well as the convenience of direct mode. (I think I understand that correctly; if a direct-mode file only exists in one repository, and is edited, the old version is lost, but if it is in multiple repos, then the old versions will be retained).
-
-It seems to me that if I do
-
-    ~/Direct$ echo Content > Test.File
-    ~/Direct$ echo More Content > Test.File
-    ~/Direct$ echo Even More Content > Test.File
-
-that all three copies are stored in ~/Indirect, so the functionality I'm after seems to work. However, ~/Indirect/Test.File ends up not being a symlink, which I think is odd/unexpected.
-
-
-**Edit:  Doing a git annex sync in ~/Indirect results in the continuing behaviour to be correct, so there's some issue telling Direct that Indirect is no longer in direct-mode?**
-This appears to fix it, but I guess shouldn't be necessary.
-
-> AFAICS, the entire problem is that the assistant does not notice when the
-> repository it's running in is changed from direct to indirect mode. Since this
-> has also been reported to cause problems with the assistant, I have added
-> a check to prevent it from being done. [[done]] --[[Joey]] 
diff --git a/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes/comment_1_56474a69c2f174d83be9137d3c045a47._comment b/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes/comment_1_56474a69c2f174d83be9137d3c045a47._comment
deleted file mode 100644
index d2a261b83..000000000
--- a/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes/comment_1_56474a69c2f174d83be9137d3c045a47._comment
+++ /dev/null
@@ -1,33 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ"
- nickname="Walter"
- subject="Commands to accomplish same"
- date="2013-04-13T04:43:41Z"
- content="""
-I feel that the following commands should do essentially the same (ie they do what I intend to do).
-More, they even display the correct (expected) behaviour, it seems the strangeness is introduced by the webapp (which, by the way, is really cool).
-
-	cd ~
-	mkdir Direct Indirect
-	git init Direct/
-	git init Indirect/
-	cd Direct/
-	git annex init Direct
-	git annex direct
-	cd ../Indirect
-	git annex init Indirect
-	git annex indirect
-    touch Indirect
-    git annex add Indirect
-    git commit -m 'Initial commit'
-	git remote add Direct ..//Direct/
-	git annex assistant
-	cd ../Direct/
-    touch Direct
-    git annex add Direct
-    git commit -m 'Initial commit'
-	git remote add Indirect ../Indirect
-	git annex assistant
-    touch Test
-    echo Test > Test 
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace.mdwn b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace.mdwn
deleted file mode 100644
index d345cf4da..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace.mdwn
+++ /dev/null
@@ -1,49 +0,0 @@
-What steps will reproduce the problem?
-Created a repository (working directory), then an another one on the same computer, 
-in a different folder for backup repository.
-
-The initial folder, what I imported, contained:
-741MB, 23381 files, most of the files are 30-150kB in sizes.
-
-After 18 hours of continous work 
-(I started 28 hours ago, but the laptop died one time, 
-and I needed to restart git-annex 4 times in total, and the laptop overheated once):
-The initial directory (/home/user/down) contains at this point (still not finished):
-8.1GB
-
-The target directory(/mnt/dat/annex2) contains:
-975MB
-
-
-What is the expected output? What do you see instead?
-I expect maximum three times the usefull data size. So I can calculate with (rule of thumb). 
-(Ie. if I want to put 1GB data into annex, it would need maximum (at any point of time 3GB of data)
-
-Currently it uses 11x(!) times the original size, and still growing.
-
-I also expect to stop syncing, when it used up all the available disk space 
-(ie. it should leave at least 200MB on the original partition, 
-none of the other programs like to have 0 bytes left).
-The machine just freeze, ie. takes almost 10 minutes to kill process, 
-and delete something to get back to life again.
-
-Also some kind of feedback how many files has been synchronized, 
-because currently the dashboard does not indicate any useful info. 
-Also the log page seems only growing, making firefox crashes.
-
-Self-controlled resource hogging. Ie. dont use more then 50% processor, 
-or dont make heavy disk usage for 3-4 hours, because the laptop can overheat.
-
-What version of git-annex are you using? On what operating system?
-https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-i386.tar.gz
-Version: 4.20130227
-Ubuntu 10.04, laptop Toshiba L300, Intel Core2Duo T5800@2.0Ghz, 3GB ram
-
-Please provide any additional information below.
-The syncing is still not finished. 
-I hope it will finish within additional 24hours.
-
-Best,
- Laszlo
-
-> [[done]] per comments
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_0._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_0._comment
deleted file mode 100644
index 87bec8530..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_0._comment
+++ /dev/null
@@ -1,34 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="Tried to add a bug, but website fails"
- date="2013-03-01T14:40:18Z"
- content="""
-@joeyh: I tried to add a comment to my bugreport:
-http://git-annex.branchable.com/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace.Makefile/
-
-I get this error:
-Error: failed to create directory /home/b-git-annex/source/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace.Makefile/: File exists
-
-The comment I tried to add:
-Seems like the logging is the culprit:
-
-user@usermachine:~/down/annex$ du -ak . | sort -nr | cut -f2 | xargs -d '\n' du -sh |head -n 30 -
-8,2G	.
-7,5G	./.git
-6,5G	./.git/annex
-2,7G	./.git/annex/daemon.log
-1,8G	./.git/annex/daemon.log.1
-1,5G	./.git/annex/daemon.log.5
-980M	./.git/objects
-742M	./mydir
-640M	./mydir/wp
-616M	./mydir/wp/wd
-314M	./mydir/wp/wd/2012
-278M	./.git/annex/daemon.log.4
-226M	./mydir/wp/wd/2011
-154M	./.git/annex/daemon.log.6
-109M	./.git/annex/objects
-
-
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_10_037a6dd6e15ef5f789a1f364f7507b53._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_10_037a6dd6e15ef5f789a1f364f7507b53._comment
deleted file mode 100644
index f973238d8..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_10_037a6dd6e15ef5f789a1f364f7507b53._comment
+++ /dev/null
@@ -1,45 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="comment 10"
- date="2013-03-03T18:31:24Z"
- content="""
-The problem with restarting, that it seems, it puts everything one more time into .git.
-(if we ignore the logging problem).
-
-Right now, here is the:
-    $ du -ak . | sort -nr | cut -f2 | xargs -d '\n' du -sh |head -n 30 -
-output:
-    8,7G	.
-    8,0G	./.git
-    6,3G	./.git/annex
-    3,5G	./.git/annex/daemon.log.2
-    2,5G	./.git/annex/daemon.log
-    1,7G	./.git/objects
-    742M	./mydir
-    640M	./mydir/wp
-    616M	./mydir/wp/wd
-    314M	./mydir/wp/wd/2012
-    226M	./mydir/wp/wd/2011
-    227M	./.git/annex/daemon.log.1
-    109M	./.git/annex/objects
-
-If you observe ./.git/objects dir, is 1,7G, 
-while yesterday it was 742M (see my first comment).
-
-Other problem, that once it runs out of space, threads crashes:
-    Pusher crashed: user error (git [\"--git-dir=/home/user/down/annex/.git\",\"--work-tree=/home/user/down/annex\",\"update-index\",\"-z\",\"--index-info\"] exited 128)
-    NetWatcherFallback crashed: fd:28: hGetLine: end of file
-    DaemonStatus crashed: /home/user/down/annex/.git/annex/daemon.status.tmp7564: hClose: resource exhausted (No space left on device)
-
-Right now, I think I tested everything I could. 
-
-Where is the autobuild? This one still is 2013 feb 27:
-http://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-i386.tar.gz
-
-Anyway, once the new version is out, I will retest this experiment.
-
-Best, 
- Laszlo
-
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_11_614e4110188fc6474e7da50fc4281e13._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_11_614e4110188fc6474e7da50fc4281e13._comment
deleted file mode 100644
index 38d9bb621..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_11_614e4110188fc6474e7da50fc4281e13._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 11"
- date="2013-03-03T18:36:31Z"
- content="""
-The autobuild is linked to on [[install/Linux_standalone]]
-
-I don't understand how you're \"restarting\" and not deleting the old .git repository. The right way would be to stop the assistant, run \"git annex uninit\", and then remove \".git\"
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_12_dcb74fb91e1c2f0db4efd68c8bcbc96c._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_12_dcb74fb91e1c2f0db4efd68c8bcbc96c._comment
deleted file mode 100644
index 8bf20fc18..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_12_dcb74fb91e1c2f0db4efd68c8bcbc96c._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="comment 12"
- date="2013-03-03T21:24:18Z"
- content="""
-restarting == Stop git-annex using the gui (Confirm shutdown daemon). Then check if there are running git process (ps -e |grep git), 
-if there are kill it, if (defunct) process present, then restart computer. Then launch git-annex using \"git-annex-webapp\" script).
-
-So its a normal program usage (start-stop cycle).
-
-The .git directory is growing. Without a single file moving/deleting/renaming/editing in the working directory.
-
-So the .git directory just grows, and I think it is a bug, and a bad one. (if we ignore the logging problem, the slow startup, the failing of disk full).
-
-I'll give it a spin to the autobuild (http://downloads.kitenet.net/git-annex/autobuild/i386/git-annex-standalone-i386.tar.gz), and report back. It will take at least 2 day, to repeat my whole experience. So expect update from me wednesday the soonest.
-
-Best, Laszlo
-
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_38671ba8d302f4d32460d1478abd2111._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_38671ba8d302f4d32460d1478abd2111._comment
deleted file mode 100644
index cb9abcf72..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_38671ba8d302f4d32460d1478abd2111._comment
+++ /dev/null
@@ -1,45 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="version 20130314, still not improved"
- date="2013-03-16T10:01:27Z"
- content="""
-Hi,
-
-I promised you a feedback, once a newer version comes out.
-
-I started fresh (from the gui), created a new directory, and copied my files over it, 
-deleted the old one (git-annex-webapp just silently quite, when I tried to use the old directory).
-
-Problems:
-> 1. each starts costs me an hour at least
-
-> 2. when computer starts git-annex starts too, and try to eat all the resources. 
-   Resulting a 10 minute bootup. Would be nice to kick in, when computer idle, 
-and others already finished booting up. (ie. I had a chance to start a webbrowser)
-
-> 3. .git objects still going. 
-find `pwd` >../gitannexstartup[TIME].txt
-
-Some results:
-gitannexstartup1034.txt
-91179
-gitannexstartup1035.txt
-91566
-gitannexstartup1040.txt
-91938
-
-    diff between 1034 and 1035 (only 1 minute difference when the file created), 
-    shows many entries like this:
-    /home/user/Desktop/down/annexnew/.git/objects/52/1ba05331f99585923f1724bb97c18a8f22837444843a45232
-    /home/user/Desktop/down/annexnew/.git/objects/52/7457c478a19f8f85c73b9f17c5640378cf307044868a45258
-
-So git objects keeps still adding. 
-As I have many duplicates in my directory 
-(backup of backups, I'm kind of paranoid, when comes to daily job), so it may be related to this bug:
-
-http://git-annex.branchable.com/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/
-
-It is just a hunch. Please tell me what else to test.
-
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_483244b1ed5744308022465f45c091fd._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_483244b1ed5744308022465f45c091fd._comment
deleted file mode 100644
index 8594e5d75..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_483244b1ed5744308022465f45c091fd._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="comment 14"
- date="2013-04-18T05:54:09Z"
- content="""
-Hi, these bugs (too detailed logging) and duplicated files issues are both solved in the latest (2013.04.17) release.
-
-Thank you very much, you can close this issue.
-
-Best, 
- Laszlo
-
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_1_d2c63723fa4bf828873770a42ffaab20._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_1_d2c63723fa4bf828873770a42ffaab20._comment
deleted file mode 100644
index 3096e596a..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_1_d2c63723fa4bf828873770a42ffaab20._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-01T16:44:17Z"
- content="""
-Can you please post a representative sample of the logs?
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_3_52f0db73dc38c3e3a73f6c7a420bf016._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_3_52f0db73dc38c3e3a73f6c7a420bf016._comment
deleted file mode 100644
index b7b866dc6..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_3_52f0db73dc38c3e3a73f6c7a420bf016._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-03-01T17:31:31Z"
- content="""
-I have made the assistant check hourly if its logs are larger than one megabyte, and trim old logs.
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_4_93596b4d5a48ffcf4bc11ba9c83cf7ca._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_4_93596b4d5a48ffcf4bc11ba9c83cf7ca._comment
deleted file mode 100644
index 7efe77303..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_4_93596b4d5a48ffcf4bc11ba9c83cf7ca._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="comment 4"
- date="2013-03-01T19:52:13Z"
- content="""
-Here is the last 300 lines of a 3.3GB daemon.log file:
-http://pastebin.com/TF35H5gu
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_5_de94e80dde6d12485140bb079d74d775._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_5_de94e80dde6d12485140bb079d74d775._comment
deleted file mode 100644
index 16f8cf65a..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_5_de94e80dde6d12485140bb079d74d775._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-03-01T20:20:21Z"
- content="""
-Aha, so it's a direct mode repository and all this \"typechange\" stuff git outputs in such repositories is presumably the main culprit for log bloat. I have made it suppress that output.
-
-Excessive repacking may also explain a lot of the CPU usage and slowness. What does this say?
-
-`grep \"Auto packing the repository for optimum performance.\" .git/annex/*.log |wc -l`
-
-It may make sense for the assistant to tune `gc.auto` to avoid repacks. You might try disabling repacking altogether and see if it helps: `git config gc.auto 0`
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_6_5f34c3d449247b4bce4665b3ea4d054c._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_6_5f34c3d449247b4bce4665b3ea4d054c._comment
deleted file mode 100644
index 8da24d60f..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_6_5f34c3d449247b4bce4665b3ea4d054c._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="comment 6"
- date="2013-03-02T10:05:38Z"
- content="""
-    $ ls -lah daemon.log
-    -rw-r--r-- 1 user user 3,3G 2013-03-02 10:54 daemon.log
-
-    $ cat daemon.log |wc -l
-    30746274
-
-    $ grep \"Auto packing the repository for optimum performance.\" daemon.log |wc -l
-    568
-
-    $ grep \"typechange: \" daemon.log |wc -l
-    30713158
-
-I'm not sure where should I issue the git command. Inside the annex/.git directory?
-The useful data is also in git repository locally.
-I try to RTFM over the internet, thanks for the pointer!
-
-
-
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_7_b43ae8aec23ba3acaf70edc0de058710._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_7_b43ae8aec23ba3acaf70edc0de058710._comment
deleted file mode 100644
index 4f53dedd1..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_7_b43ae8aec23ba3acaf70edc0de058710._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="comment 7"
- date="2013-03-02T11:03:46Z"
- content="""
-    Ok, quick question: Should I issue git config gc.auto 0, in both repositories? 
-    (it puts variable inside .git/config)
-
-    With this gc.auto 0, should the \"typechange: \" logging change? (because it still in the log)
-
-    I'm testing the whole experience, and report back, 
-    also when new build is available i will switch to it, to report about the logging size.
-
-Thank you for your fast response!
-
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_8_13b8e0a62f6b6d02960687e206a8b016._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_8_13b8e0a62f6b6d02960687e206a8b016._comment
deleted file mode 100644
index 4d3f11f36..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_8_13b8e0a62f6b6d02960687e206a8b016._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
- nickname="Laszlo"
- subject="comment 8"
- date="2013-03-02T12:54:14Z"
- content="""
-The startup time is somewhere between 4-5 hours 
-(dunno exactly, its only running about 3 hours) with this gc.auto 0.
-
-I will try to relaunch git-annex-assistant once it finishes startup, 
-but I can report back only tomorrow because it may take 5 hours/try.
-
-Laszlo
-
-"""]]
diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_9_818b94a74b01a210d1106dd35bc932d8._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_9_818b94a74b01a210d1106dd35bc932d8._comment
deleted file mode 100644
index 11b3efec0..000000000
--- a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_9_818b94a74b01a210d1106dd35bc932d8._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 9"
- date="2013-03-03T17:45:34Z"
- content="""
-Well, that sounds like an improvement for sure with gc.auto=0. I have made that be done by default when committing.
-
-The typechange fix is available in the autobuilds already.
-"""]]
diff --git a/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git.mdwn b/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git.mdwn
deleted file mode 100644
index dd4b6a921..000000000
--- a/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git.mdwn
+++ /dev/null
@@ -1,384 +0,0 @@
-### Please describe the problem.
-I try to share some files between a windows machine and a linux machine in direct mode, with a remote repository between the two. I can't seem to reproduce the problem in indirect mode...
-
-I add a file on the windows machine then copy it to the remote repository. I then get it on the linux machine and edit it there. If I `git annex sync` and copy the file's data to the remote repository, a `git annex sync` on windows will fail like this:
-
-[[!format sh """
-$ git annex sync
-commit
-ok
-pull origin
-remote: Counting objects: 41, done.
-remote: Compressing objects: 100% (24/24), done.
-remote: Total 31 (delta 9), reused 0 (delta 0)
-Unpacking objects: 100% (31/31), done.
-From ssh://192.168.1.29:/home/raz/work/test
-   b23cb44..9073cc3  git-annex  -> origin/git-annex
-   7d4f0e2..87438fc  master     -> origin/master
-   57a661c..b33b025  synced/git-annex -> origin/synced/git-annex
-   7d4f0e2..87438fc  synced/master -> origin/synced/master
-ok
-(merging origin/git-annex origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 17, done.
-Delta compression using up to 8 threads.
-Compressing objects: 100% (4/4), done.
-Writing objects: 100% (5/5), 565 bytes | 0 bytes/s, done.
-Total 5 (delta 2), reused 0 (delta 0)
-To ssh://192.168.1.29:/home/raz/work/test.git
-   b33b025..dcfaf23  git-annex -> synced/git-annex
- ! [rejected]        master -> synced/master (non-fast-forward)
-error: failed to push some refs to 'ssh://192.168.1.29:/home/raz/work/test.git'
-hint: Updates were rejected because a pushed branch tip is behind its remote
-hint: counterpart. Check out this branch and merge the remote changes
-hint: (e.g. 'git pull') before pushing again.
-hint: See the 'Note about fast-forwards' in 'git push --help' for details.
-failed
-git-annex: sync: 1 failed
-"""]]
-
-A `git log` tells me the master branch is not properly merged so I assume the pull failed silently (I paste the log in the transcript).
-
-I can then try to manually fix the windows working copy and sometimes it kind of work, but sometimes I have a hard time recovering and I am better off cloning a new version and moving data's around...
-
-### What steps will reproduce the problem?
-Create a repository on a windows.
-
-Add a file.
-
-`git clone --bare` the repository and put it on a remote machine.
-
-Clone the remote repository to a linux machine.
-
-Get the file's data.
-
-Edit the file on linux.
-
-Commit it and copy the data's to the remote machine.
-
-`git clone sync` on the windows machine --> Error.
-
-### What version of git-annex are you using? On what operating system?
-On Windows:
-[[!format sh """
-git-annex version: 4.20130827-g4f18612
-build flags: Pairing Testsuite S3 WebDAV DNS
-local repository version: 4
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 2
-"""]]
-
-On Linux
-[[!format sh """
-git-annex version: 4.20130815
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-local repository version: 4
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-"""]]
-
-### Please provide any additional information below.
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-### On Windows
-
-$ mkdir test_windows
-
-$ cd test_windows/
-
-$ git init
-Initialized empty Git repository in c:/Users/raz/test_windows/.git/
-
-$ git annex init windows
-init windows
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-ok
-(Recording state in git...)
-
-$ echo "test 1" > test.txt
-
-$ git annex add test.txt
-add test.txt (checksum...) ok
-(Recording state in git...)
-
-$ git annex sync
-commit
-ok
-git-annex: no branch is checked out
-
-$ cd ..
-
-$ git clone --bare test_windows/ test.git
-Cloning into bare repository 'test.git'...
-done.
-
-$ scp -r test.git 192.168.1.29:/home/raz/work/
-config                                        100%  183     0.2KB/s   00:00
-description                                   100%   73     0.1KB/s   00:00
-HEAD                                          100%   23     0.0KB/s   00:00
-applypatch-msg.sample                         100%  452     0.4KB/s   00:00
-commit-msg.sample                             100%  896     0.9KB/s   00:00
-post-commit.sample                            100%  160     0.2KB/s   00:00
-post-receive.sample                           100%  552     0.5KB/s   00:00
-post-update.sample                            100%  189     0.2KB/s   00:00
-pre-applypatch.sample                         100%  398     0.4KB/s   00:00
-pre-commit.sample                             100% 1704     1.7KB/s   00:00
-pre-push.sample                               100% 1348     1.3KB/s   00:00
-pre-rebase.sample                             100% 4951     4.8KB/s   00:00
-prepare-commit-msg.sample                     100% 1239     1.2KB/s   00:00
-update.sample                                 100% 3611     3.5KB/s   00:00
-exclude                                       100%  240     0.2KB/s   00:00
-825dc642cb6eb9a060e54bf8d69288fbee4904        100%   15     0.0KB/s   00:00
-a31b7a55380d79248658d3fffff6d2dc41a726        100%  116     0.1KB/s   00:00
-dcabbf728abe62b6e2bcc06b8306eb3aa9a497        100%  176     0.2KB/s   00:00
-332ecbfe923879df51a7a3f9bb86ebdfb64273        100%   45     0.0KB/s   00:00
-4f0e20d38d6dc757340a8c569270b5a857fc67        100%  160     0.2KB/s   00:00
-62956bcf45c63b24a637b22a742db0d9458248        100%   86     0.1KB/s   00:00
-7ec519eb1b257a85ae8f9373d0835dea9ddc04        100%   82     0.1KB/s   00:00
-1d1559a050b4a2df2e653b1e7ac15bdf7d56b1        100%   51     0.1KB/s   00:00
-b74dbedfac4d6a0a90580cff2088a5d61f6675        100%  130     0.1KB/s   00:00
-0ca042f439ef997f04a25a449aa1f539b93cf4        100%   53     0.1KB/s   00:00
-bbce5e51e5a90ffd26900de3546fc4f9704181        100%  151     0.2KB/s   00:00
-18bd66316298fcc5c06af9865c30a2fe4d2476        100%  176     0.2KB/s   00:00
-edf8b5cc207e16ca0173785a2ba569c5d4208c        100%   71     0.1KB/s   00:00
-packed-refs                                   100%  160     0.2KB/s   00:00
-
-$ cd test_windows/
-
-$ git remote add origin ssh://192.168.1.29:/home/raz/work/test.git
-
-$ git annex copy --to origin
-copy test.txt (checking origin...) (to origin...)
-test.txt
-           7 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 79 bytes  received 31 bytes  220.00 bytes/sec
-total size is 7  speedup is 0.06
-ok
-(Recording state in git...)
-
-$ git annex sync
-commit
-ok
-pull origin
-remote: Counting objects: 11, done.
-remote: Compressing objects: 100% (5/5), done.
-remote: Total 6 (delta 1), reused 0 (delta 0)
-Unpacking objects: 100% (6/6), done.
-From ssh://192.168.1.29:/home/raz/work/test
- * [new branch]      git-annex  -> origin/git-annex
- * [new branch]      master     -> origin/master
-ok
-(merging origin/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 18, done.
-Delta compression using up to 8 threads.
-Compressing objects: 100% (8/8), done.
-Writing objects: 100% (10/10), 874 bytes | 0 bytes/s, done.
-Total 10 (delta 4), reused 0 (delta 0)
-To ssh://192.168.1.29:/home/raz/work/test.git
- * [new branch]      git-annex -> synced/git-annex
- * [new branch]      master -> synced/master
-ok
-
-### On Linux
-
-$ git clone test.git test_linux
-Cloning into 'test_linux'...
-done.
-
-$ cd test_linux 
-
-$ git annex init linux
-init linux ok
-(Recording state in git...)
-
-$ git annex sync
-(merging origin/git-annex origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-commit  
-ok
-pull origin 
-ok
-push origin 
-Counting objects: 11, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (6/6), done.
-Writing objects: 100% (8/8), 775 bytes | 0 bytes/s, done.
-Total 8 (delta 3), reused 0 (delta 0)
-To /home/raz/work/test.git
-   0b4f175..41fba1d  git-annex -> synced/git-annex
-ok
-
-$ git annex get
-get test.txt (from origin...) ok
-(Recording state in git...)
-
-$ git annex direct
-commit  
-# On branch master
-nothing to commit, working directory clean
-ok
-direct test.txt ok
-direct  ok
-
-$ git annex sync
-commit  
-ok
-pull origin 
-ok
-push origin 
-Counting objects: 9, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (4/4), done.
-Writing objects: 100% (5/5), 492 bytes | 0 bytes/s, done.
-Total 5 (delta 1), reused 0 (delta 0)
-To /home/raz/work/test.git
-   41fba1d..57a661c  git-annex -> synced/git-annex
-ok
-
-$ cat test.txt  
-test 1
-
-$ echo "test 2" > test.txt
-
-$ git annex sync
-add test.txt (checksum...) ok
-(Recording state in git...)
-commit  
-(Recording state in git...)
-ok
-pull origin 
-ok
-push origin 
-Counting objects: 22, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (12/12), done.
-Writing objects: 100% (16/16), 1.40 KiB | 0 bytes/s, done.
-Total 16 (delta 4), reused 0 (delta 0)
-To /home/raz/work/test.git
-   57a661c..4883cad  git-annex -> synced/git-annex
-   7d4f0e2..87438fc  master -> synced/master
-ok
-
-$ git annex copy --to origin
-copy test.txt (to origin...) ok
-(Recording state in git...)
-
-$ git annex sync            
-commit  
-ok
-pull origin 
-remote: Counting objects: 6, done.
-remote: Compressing objects: 100% (4/4), done.
-remote: Total 5 (delta 0), reused 0 (delta 0)
-Unpacking objects: 100% (5/5), done.
-From /home/raz/work/test
-   b23cb44..9073cc3  git-annex  -> origin/git-annex
-ok
-(merging origin/git-annex into git-annex...)
-(Recording state in git...)
-push origin 
-Counting objects: 18, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (8/8), done.
-Writing objects: 100% (10/10), 924 bytes | 0 bytes/s, done.
-Total 10 (delta 3), reused 0 (delta 0)
-To /home/raz/work/test.git
-   4883cad..b33b025  git-annex -> synced/git-annex
-ok
-
-$ 
-
-
-### On Windows
-
-$ git annex sync
-commit
-ok
-pull origin
-remote: Counting objects: 41, done.
-remote: Compressing objects: 100% (24/24), done.
-remote: Total 31 (delta 9), reused 0 (delta 0)
-Unpacking objects: 100% (31/31), done.
-From ssh://192.168.1.29:/home/raz/work/test
-   b23cb44..9073cc3  git-annex  -> origin/git-annex
-   7d4f0e2..87438fc  master     -> origin/master
-   57a661c..b33b025  synced/git-annex -> origin/synced/git-annex
-   7d4f0e2..87438fc  synced/master -> origin/synced/master
-ok
-(merging origin/git-annex origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 17, done.
-Delta compression using up to 8 threads.
-Compressing objects: 100% (4/4), done.
-Writing objects: 100% (5/5), 565 bytes | 0 bytes/s, done.
-Total 5 (delta 2), reused 0 (delta 0)
-To ssh://192.168.1.29:/home/raz/work/test.git
-   b33b025..dcfaf23  git-annex -> synced/git-annex
- ! [rejected]        master -> synced/master (non-fast-forward)
-error: failed to push some refs to 'ssh://192.168.1.29:/home/raz/work/test.git'
-hint: Updates were rejected because a pushed branch tip is behind its remote
-hint: counterpart. Check out this branch and merge the remote changes
-hint: (e.g. 'git pull') before pushing again.
-hint: See the 'Note about fast-forwards' in 'git push --help' for details.
-failed
-git-annex: sync: 1 failed
-
-$ git log --graph --oneline --decorate --all
-* 87438fc (origin/synced/master, origin/master) git-annex automatic sync
-* 7d4f0e2 (HEAD, synced/master, master) git-annex automatic sync
-*-.   dcfaf23 (origin/synced/git-annex, git-annex) merging origin/git-annex orig
-|\ \
-| | *   b33b025 merging origin/git-annex into git-annex
-| | |\
-| | |/
-| |/|
-| * | 9073cc3 (origin/git-annex) update
-| | * 73518bc update
-| | * 4883cad update
-| | * 1b447f5 update
-| |/
-|/|
-* | 57a661c update
-| |
-|  \
-*-. \   41fba1d merging origin/git-annex origin/synced/git-annex into git-annex
-|\ \ \
-| | |/
-| |/|
-| | *   0b4f175 merging origin/git-annex into git-annex
-| | |\
-| | |/
-| |/|
-| * | b23cb44 update
-| | * b5755a2 update
-| |/
-| * 6adcabb update
-| * df18bd6 update
-| * dcbbce5 branch created
-* 0d138eb update
-* fe6bccc branch created
-
-$
-
-# End of transcript or log.
-"""]]
-
-> Apparently `test.git` had `receive.denyNonFastForwards`
-> set to true, which prevents the forced pushing `git annex sync`
-> needs to do. I have made it print out a hint about this setting
-> when a push failes. [[done]] --[[Joey]]
diff --git a/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git/comment_1_155e0c4d3aa41eebfe27533ab70a91d3._comment b/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git/comment_1_155e0c4d3aa41eebfe27533ab70a91d3._comment
deleted file mode 100644
index 1a443fb19..000000000
--- a/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git/comment_1_155e0c4d3aa41eebfe27533ab70a91d3._comment
+++ /dev/null
@@ -1,68 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawknruiCHUcOh2mmpkh7OFJ4iNfAOOamRVs"
- nickname="Renaud"
- subject="comment 1"
- date="2013-08-29T06:38:44Z"
- content="""
-I wonder if it isn't related to the fact that even if I do `git annex drop` on windows, the file is still marked as modified in git.
-What is in repository is the path to the file's data using unix style folder separator but what is in my working directory is a file containing the path using windows style folder separator.
-
-I paste a transcript to describe what I mean:
-
-[[!format sh \"\"\"
-$ mkdir tmp
-
-$ cd tmp
-
-$ git init
-Initialized empty Git repository in c:/Users/raz/tmp/tmp/.git/
-
-$ git annex init test
-init test
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-ok
-(Recording state in git...)
-
-$ echo test > test
-
-$ git annex add
-add test (checksum...) ok
-(Recording state in git...)
-
-$ git annex sync
-commit
-ok
-git-annex: no branch is checked out
-
-$ git annex drop --force
-drop test ok
-(Recording state in git...)
-
-$ git status
-# On branch master
-# Changes not staged for commit:
-#   (use \"git add <file>...\" to update what will be committed)
-#   (use \"git checkout -- <file>...\" to discard changes in working directory)
-#
-#       modified:   test
-#
-no changes added to commit (use \"git add\" and/or \"git commit -a\")
-
-$ git diff
-diff --git a/test b/test
-index a9dd439..62343b2 120000
---- a/test
-+++ b/test
-@@ -1 +1 @@
--.git/annex/objects/w8/pv/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93
-\ No newline at end of file
-+.git\annex\objects\w8\pv\SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93
-\ No newline at end of file
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn b/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn
deleted file mode 100644
index e6f3524b2..000000000
--- a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-I'm using S3 special remote that I initialized like this:
-
-    git annex initremote s3 type=S3 encryption=EEF2B390 datacenter="EU" storageclass="REDUCED_REDUNDANCY"
-
-Instead of asking me my key passphrase (I have gpg-agent running), it ask me a new passphase an then repeat it. So it's not my passphrase because if I kill gpg-agent, it will ask me three passphrase for each file: one mine and two for the new one. If i don't put anything there it says:
-
-    copy GOPR1672.JPG (checking s3...) (to s3...) gpg: error creating passphrase: Invalid passphrase
-    gpg: symmetric encryption of `[stdin]' failed: Invalid passphrase
-    failed
-    git-annex: fd:13: hPutBuf: resource vanished (Broken pipe)
-    copy GOPR1673.JPG (checking s3...) (to s3...) 
-
-So I create a new passphrase (two times) for each file I tried to upload. The problem is that I have more than 12000 files to upload!
-
-What's this new passphrase for?
-
-BTW: git-annex version: 3.20130102 same precompiled binary on Arch Linux.
-
-> I've reproduced this with gpg 2.0.19. It is a documented incompatability
-> between gpg 1.x and 2.x; the latter needs --batch included in its
-> parameters. I've put in a fix. [[done]]
diff --git a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_1_a4fc30bf7d39cae337286e9e815e6cba._comment b/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_1_a4fc30bf7d39cae337286e9e815e6cba._comment
deleted file mode 100644
index b006b3b44..000000000
--- a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_1_a4fc30bf7d39cae337286e9e815e6cba._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="joksnet"
- ip="193.253.37.245"
- subject="Working now"
- date="2013-01-16T01:36:43Z"
- content="""
-Ok. I don't what happend, but it's working now. I restart gpg-agent a few times with the script found [here](https://wiki.archlinux.org/index.php/GPG#gpg-agent). And now it doesn't ask for any passphrase.
-
-Par contre, I need to export the AWS_* variables if I reboot my pc. I think is because I didn't set embedcreds=yes when initremote. Can I change it now? O I have to remote rm and initremote again?
-
-Thank you,
-Juan
-"""]]
diff --git a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_2_e5d42b623017acedf6a3890ce15680a3._comment b/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_2_e5d42b623017acedf6a3890ce15680a3._comment
deleted file mode 100644
index 7b26ca738..000000000
--- a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_2_e5d42b623017acedf6a3890ce15680a3._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 2"
- date="2013-01-16T02:17:26Z"
- content="""
-Someone else reported what sounds like the same bug at [[encryption_given_a_gpg_keyid_still_uses_symmetric_encryption]]. It sounds like this is somehow an agent bug. I cannot reproduce it. I can hypothesise that, if this bug is occurring, you'll be prompted for a passphrase when running this command.. which if it happens would certainly be a bug in gpg or its agent
-
-touch foo; echo foo| gpg --symmetric --passphrase-fd=0 foo
-
-(You can run `git annex initremote $yourremote embedcreds=yes`  and it'll modify the existing configuration.)
-"""]]
diff --git a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_3_e5150b65b514896e14b9ad3d951963f7._comment b/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_3_e5150b65b514896e14b9ad3d951963f7._comment
deleted file mode 100644
index 4764dcd5d..000000000
--- a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_3_e5150b65b514896e14b9ad3d951963f7._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="joksnet"
- ip="193.253.37.245"
- subject="comment 3"
- date="2013-01-16T17:23:26Z"
- content="""
-It's a GPG/GPG-Agent (2.0.19) bug because the command you give me ask me for a new passphrase.
-
-Thank you for the answer.
-"""]]
diff --git a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_4_47c2fc167b0c396edc40468fb7c7bfee._comment b/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_4_47c2fc167b0c396edc40468fb7c7bfee._comment
deleted file mode 100644
index 20f6564c8..000000000
--- a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase/comment_4_47c2fc167b0c396edc40468fb7c7bfee._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 4"
- date="2013-01-16T19:05:38Z"
- content="""
-Does it ask for a passphrase if --batch is included in gpg's parameters? 
-"""]]
diff --git a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error..mdwn b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error..mdwn
deleted file mode 100644
index 94a124b23..000000000
--- a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error..mdwn
+++ /dev/null
@@ -1,42 +0,0 @@
-### Please describe the problem.
-
-After setting the username (xyz@gmail.com) and the password the webapp takes several minutes until eventually an error message is displayed stating that:
-
-    Unable to connect to the Jabber server. Maybe you entered the wrong password? (Error message: host gmail.com:5222 failed: connect: does not exist (Network is unreachable))
-
-Testing with xyz@xmpp.l.gmail.com yields:
-
-    Unable to connect to the Jabber server. Maybe you entered the wrong password? (Error message: host xmpp.l.google.com:5222 failed: AuthenticationFailure)
-
-What's strange about that is that the exact same procedure works on a different (Ubuntu-) system with almost no time spend.
-
-### What steps will reproduce the problem?
-
-Trying to set up the jabber connection.
-
-### What version of git-annex are you using? On what operating system?
-
-    git-annex version: 4.20130922-g7dc188a
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi
-    (actually a zeroinstall feed from here: http://f12n.de/0install/git-annex-webapp.xml which is based on the standalone build)
-
-OS: up-to-date ARCH system
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[2013-09-23 19:24:04 CEST] main: starting assistant version 4.20130922-g7dc188a
-(scanning...) [2013-09-23 19:24:04 CEST] Watcher: Performing startup scan
-(started...) 
-[2013-09-23 20:18:12 CEST] read: host ["-t","SRV","--","_xmpp-client._tcp.gmail.com"]
-.git/annex/daemon.log (END)
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; I have enabled the haskell dns library on all the autobuilds.
-> --[[Joey]]
diff --git a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_1_6d821af99ab3c83a5b0f52d3713ab8e2._comment b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_1_6d821af99ab3c83a5b0f52d3713ab8e2._comment
deleted file mode 100644
index c2dd31f17..000000000
--- a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_1_6d821af99ab3c83a5b0f52d3713ab8e2._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.220"
- subject="comment 1"
- date="2013-09-25T18:27:24Z"
- content="""
-Sounds like the SRV lookup is failing. Does `git-annex version` list either DNS or ADNS in the build flags?
-
-Does `host -t SRV _xmpp-client._tcp.gmail.com` work?
-"""]]
diff --git a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_2_206b6c8cce8350fc088f01c42fc4715b._comment b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_2_206b6c8cce8350fc088f01c42fc4715b._comment
deleted file mode 100644
index 1cb191d8f..000000000
--- a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_2_206b6c8cce8350fc088f01c42fc4715b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawknwkXgi8SnK4QT32ANl3GMKvFLyQGeHqo"
- nickname="Florian"
- subject="comment 2"
- date="2013-09-25T21:19:23Z"
- content="""
-Aaaah ok ... the *host* command is not installed by default on Arch Linux. I've installed it ... now it works ... will report it to the package maintainer.
-"""]]
diff --git a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_3_ed36f503f88611382b50687608b9b7e7._comment b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_3_ed36f503f88611382b50687608b9b7e7._comment
deleted file mode 100644
index a69763af7..000000000
--- a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_3_ed36f503f88611382b50687608b9b7e7._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 3"
- date="2013-11-08T18:42:22Z"
- content="""
-Seems like I should fix the standalone linux tarball to either include the host program, or better, build git-annex with the Haskell [DNS library](https://hackage.haskell.org/package/dns). (I think that the Mac app and other builds are built with DNS by default, since they have dependencies installed using cabal directly).
-
-I need to first get that library included in Debian, so I can install it reliably on my build systems.
-"""]]
diff --git a/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn b/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn
deleted file mode 100644
index bbe37a8d6..000000000
--- a/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-What steps will reproduce the problem?
-
- * Create a symlink to a directory in your annex repository, like e.g. ~/Notes -> ~/annex/Notes
- * cd into ~/Notes
- * execute 'git annex sync <remote>', assuming that <remote> has made some changes
-
-What is the expected output? What do you see instead?
-
-If <remote> has made a change to, say, ~/annex/Documents/test.txt, the sync unexpectedly creates the new test.txt at ~/Notes/Documents/test.txt.
-It should either magically figure out that it has to create the file relative to the repository's root (i.e. ~/annex) or throw an error instead.
-
-What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130323
-OS: Archlinux
-Shell: zsh
-
-
-> I tried to reproduce this, and it doesn't happen any longer. Tested in
-> both direct and indirect mode.
-> 
-> I think this bug was another manifestation of a bug that got fixed a
-> while ago where the direct mode repository updater got confused when run
-> in a subdirectory of the repository, and put files under that subdir that
-> were supposed to go under the root of the repository.
-> 
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content.mdwn b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content.mdwn
deleted file mode 100644
index bdf48760c..000000000
--- a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content.mdwn
+++ /dev/null
@@ -1,49 +0,0 @@
-# What steps will reproduce the problem?
-
-    echo "TEST CONTENT" > fileA
-    cp fileA fileB
-    git annex add file{A,B}
-    git annex drop fileA --force
-    cat fileB
-
-# What is the expected output? What do you see instead?
-
-## expected: 
-
--->   TEST CONTENT
-
-## observed:
-
--->   cat: fileB: No such file or directory
-
-
-# What version of git-annex are you using? On what operating system?
-
-git-annex version: 3.20121017
-
-# Please provide any additional information below.
-
-I really like git annex's feature, to store the same content only once. But as this happens transparently (i.e. the user does not need to no, nor is he told, that contents are identical (which is very comfortable, of course)), the "git annex drop" function is broken. For it effectively deleting (seemingly) random files, WITHOUT notifying the user.
-
-
-# Possible solution?
-
-One simple solution would be to use "git annex find" functionality to see who else uses the file and NOT deleting it.
-
-But this still leaves a problem:
-
-Consider the following variation of the above example and assume, that "drop" does not delete content that is still used (i.e. implementing the above solution). 
-
-    echo "TEST CONTENT" > fileA
-    cp fileA fileB
-    git annex add file{A,B}
-    git rm fileB
-    git annex drop fileA --force
-    git checkout --force
-    cat fileB
--->  cat: fileB: No such file or directory
-
-Here again, the problem is, that the user would probably (correct me if I am wrong) expect that the fileB still exists, because removing a file and checking it out again is expected to not mess with the annex contents (?). He does not know, that the "annex frop fileA" actually drop fileB's contents, because there was no additional file linking to it. It effectively performed a "git annex dropunused".
-
-> We seem to have agreed this is reasonable behavior, and a doc change was done.
-> Do feel free to suggest other doc changes.. [[done]] --[[Joey]]
diff --git a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_1_2eb20b65582fa7f271b1d0bb5560d08c._comment b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_1_2eb20b65582fa7f271b1d0bb5560d08c._comment
deleted file mode 100644
index 712657e82..000000000
--- a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_1_2eb20b65582fa7f271b1d0bb5560d08c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 1"
- date="2012-10-28T17:13:32Z"
- content="""
-You can avoid this by not using a deduplicating backend; for example you can use the WORM backend.
-
-However, the foot shooting actually occurs due to using drop --force, which is explicitly asking git-annex to be unsafe. If you want to be safe, simply don't use --force. If you want to safely delete a file, simply `git rm` it, and then `git annex unused` will come along and find content that can safely be removed.
-"""]]
diff --git a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_2_b14e1d31dd6a8fb930fcc0bec798e194._comment b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_2_b14e1d31dd6a8fb930fcc0bec798e194._comment
deleted file mode 100644
index 005c45be2..000000000
--- a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_2_b14e1d31dd6a8fb930fcc0bec798e194._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlgyVag95OnpvSzQofjyX0WjW__MOMKsl0"
- nickname="Sehr"
- subject="comment 2"
- date="2012-10-28T21:46:08Z"
- content="""
-I onyl used \"--force\" for demonstration purposes. I could also set 
-
-   annex.numcopies = 0
-
-which removes the need \"force\". While this setting can be totally reasonable in certain circumstancing it seems very dangerous, that completely unrelated files might unwillingly be deleted.
-
-I agree with you, that a possible solution could be to not use a deduplicating backend. But my point is, that this needs to be either changed or documented. Because even if the user can \"fix\" this by changing his behavior, he will probably only do so AFTER he lost something.
-
-Instead of changing the program (to include a check), I would at least suggest an addition to \"drop\"'s documentation: 
-
-
-\"drop\": keep in mind, that on dedcupliocating backends, you might end up deleting more than one file. to be perfectly safe, use git-rm and git-annex dropunused.
-"""]]
diff --git a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_3_1892bcfbe3c462aa74552a241d65cad9._comment b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_3_1892bcfbe3c462aa74552a241d65cad9._comment
deleted file mode 100644
index 8dfc30a60..000000000
--- a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_3_1892bcfbe3c462aa74552a241d65cad9._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 3"
- date="2012-10-28T23:29:46Z"
- content="""
-numcopies=0 is inherently unsafe, and unreasonable if you value your data at all. I've added some warnings about it to the man page.
-"""]]
diff --git a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_4_dfa0e31996eaa14e2945c1d11670c4d9._comment b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_4_dfa0e31996eaa14e2945c1d11670c4d9._comment
deleted file mode 100644
index d82a3026d..000000000
--- a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_4_dfa0e31996eaa14e2945c1d11670c4d9._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlgyVag95OnpvSzQofjyX0WjW__MOMKsl0"
- nickname="Sehr"
- subject="comment 4"
- date="2012-10-29T00:00:33Z"
- content="""
-Thanks, that's cool. Admittedly, I cannot think of too many scenarios, where there are two identical files without the user's knowloedge. And an even smaller subset of scenarios, where one would want to issue a \"drop\" on (only) one of these due to storage shortages. 
-
-
-
-By the way, I LOVE git-annex.
-
-
-PS: I just realized, that the same applies to the \"move\" command.
-"""]]
diff --git a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_5_e2a9336cf1080c158765d4adfe72f26b._comment b/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_5_e2a9336cf1080c158765d4adfe72f26b._comment
deleted file mode 100644
index cc93b0f49..000000000
--- a/doc/bugs/__34__drop__34___deletes_all_files_with_identical_content/comment_5_e2a9336cf1080c158765d4adfe72f26b._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 5"
- date="2012-10-29T00:03:40Z"
- content="""
-You're guaranteed to still have at least 1 copy of the file after move though, so you can get it back.
-
-"""]]
diff --git a/doc/bugs/__34__git_annex_watch__34___adds_map.dot.mdwn b/doc/bugs/__34__git_annex_watch__34___adds_map.dot.mdwn
deleted file mode 100644
index 94c495735..000000000
--- a/doc/bugs/__34__git_annex_watch__34___adds_map.dot.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-"git annex watch" will add the file generated by "git annex map", which is
-probably not intended. Shouldn’t this file be created in /tmp or
-.git/annex/ or somewhere else?
-
-> Indeed, so [[done]] --[[Joey]]
-
-    /tmp $ cd test/
-    /tmp/test $ git init
-    Initialized empty Git repository in /tmp/test/.git/
-    /tmp/test $ git annex init
-    init  ok
-    (Recording state in git...)
-    /tmp/test $ git annex watch
-    /tmp/test $ git annex map
-    map /tmp/test ok
-    
-      running: dot -Tx11 map.dot
-    
-    ok
-    /tmp/test $ ls -l
-    insgesamt 4
-    lrwxrwxrwx 1 jojo jojo 180 Jul 15 23:36 map.dot -> .git/annex/objects/P3/76/SHA256-s208--44199582b5948512ff12cf03de0b86fa1bebf09785dba2827fe52afee0afbe3d/SHA256-s208--44199582b5948512ff12cf03de0b86fa1bebf09785dba2827fe52afee0afbe3d
-    
diff --git a/doc/bugs/__34__import__34___generates_a_commit_even_with_autocommit__61__false.mdwn b/doc/bugs/__34__import__34___generates_a_commit_even_with_autocommit__61__false.mdwn
deleted file mode 100644
index 69e36595e..000000000
--- a/doc/bugs/__34__import__34___generates_a_commit_even_with_autocommit__61__false.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-### Please describe the problem.
-
-`git annex import` generates a commit in the `git-annex` branch even if `autocommit` has been disabled.
-
-It happens in direct mode, I haven't tested with indirect mode.
-
-### What steps will reproduce the problem?
-
-    git config --global annex.autocommit false
-    git annex direct
-    git annex import --force ~/Documents/*.pdf
-
-    git log git-annex # see the newly created commit
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex 5.20140421 from the Ubuntu PPA.
-
-> annex.autocommit has nothing to do with commits to the git-annex
-> branch. You want `git config annex.alwayscommit false`
-> 
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/__34__make_test__34___fails_silently.mdwn b/doc/bugs/__34__make_test__34___fails_silently.mdwn
deleted file mode 100644
index 8632f03f5..000000000
--- a/doc/bugs/__34__make_test__34___fails_silently.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-`make test` fails silently when the test program cannot be built. This happens, for example, when attempting to compile git-annex with `QuickCheck-2.4.2`.
-
-> I've made "make test" exit nonzero if the test suite cannot be built.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/__34__make_test__34___fails_silently/comment_1_f868e34f41d828d4571968d1ab07820a._comment b/doc/bugs/__34__make_test__34___fails_silently/comment_1_f868e34f41d828d4571968d1ab07820a._comment
deleted file mode 100644
index 00f67ad11..000000000
--- a/doc/bugs/__34__make_test__34___fails_silently/comment_1_f868e34f41d828d4571968d1ab07820a._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2012-01-03T16:54:19Z"
- content="""
-The code is:
-
-<pre>
-@if ! $(GHCMAKE) -O0 test; then \
-                echo \"** not running test suite\" >&2; \
-else \
-</pre>
-
-The error message from the compiler, followed by the above error message does not seem \"silent\". It does exit 0 without running the test suite if it cannot be built.
-"""]]
diff --git a/doc/bugs/__34__make_test__34___fails_silently/comment_2_fb9e8e2716b0dea15b0d4807ae7cd114._comment b/doc/bugs/__34__make_test__34___fails_silently/comment_2_fb9e8e2716b0dea15b0d4807ae7cd114._comment
deleted file mode 100644
index 3b76e3f14..000000000
--- a/doc/bugs/__34__make_test__34___fails_silently/comment_2_fb9e8e2716b0dea15b0d4807ae7cd114._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://peter-simons.myopenid.com/"
- ip="77.188.44.113"
- subject="comment 2"
- date="2012-01-03T18:09:38Z"
- content="""
-When \"make test\" fails to run any tests at all, it should not return exit code 0. This behavior is quite misleading, and it means that automated build systems are not going to detect the fact that the test suit could not be run.
-"""]]
diff --git a/doc/bugs/__39__Cannot_write_a_repository_there__39___on_Windows.mdwn b/doc/bugs/__39__Cannot_write_a_repository_there__39___on_Windows.mdwn
deleted file mode 100644
index 62ad4a15f..000000000
--- a/doc/bugs/__39__Cannot_write_a_repository_there__39___on_Windows.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-### Please describe the problem.
-When I try to create the repository with the suggested location `C:\Users\bbigras\Desktop\annex\` I get "Cannot write a repository there". I didn't see the program output any errors on the console. [screen capture](http://imgur.com/7ZUqqVQ)
-
-It works if I change the path to `C:\Users\bbigras\annex\`.
-
-### What steps will reproduce the problem?
-* run `git annex webapp`
-* click `Make Repository`
-
-### What version of git-annex are you using? On what operating system?
-[[!format sh """
-git-annex version: 5.20131213-g2893b22
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-
-git version 1.8.4.msysgit.0
-"""]]
-
-Windows 7 64-bit
-
-### Please provide any additional information below.
-
-[[!format sh """
-Launching web browser on file://C:\Users\bbigras\AppData\Local\Temp\webapp9924.html
-"""]]
-
-> It checks if the directory can be written to, and it seems that for some
-> reason Windows is preventing you from writing to your Desktop. That seems
-> really weird to me (and I have not seen that behavior). But, I can easily
-> make it check if that's the case, and fall back to the other path, so
-> have done so. [[done]] --[[Joey]]
diff --git a/doc/bugs/__39__Internal_Server_Error__39___when_creating_repo_on_other_drive_than_C:_on_Windows.mdwn b/doc/bugs/__39__Internal_Server_Error__39___when_creating_repo_on_other_drive_than_C:_on_Windows.mdwn
deleted file mode 100644
index b6f8e3ca4..000000000
--- a/doc/bugs/__39__Internal_Server_Error__39___when_creating_repo_on_other_drive_than_C:_on_Windows.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-### Please describe the problem.
-When I try to create an annex on my `D:\` drive I get the following error:
-
-[[!format sh """
-Internal Server Error
-git [Param "config",Param "annex.uuid",Param "d2277948-4689-41d8-bd55-15c634f38cee"] failed
-"""]]
-
-[screen capture](http://imgur.com/w7uPLDp)
-
-
-### What steps will reproduce the problem?
-* run `git annex webapp`
-* create annex on `d:\annex`
-
-### What version of git-annex are you using? On what operating system?
-[[!format sh """
-git-annex version: 5.20131213-g2893b22
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-
-git version 1.8.4.msysgit.0
-"""]]
-
-Windows 7 64-bit
-
-### Please provide any additional information below.
-[[!format sh """
-Launching web browser on file://C:\Users\bbigras\AppData\Local\Temp\webapp9400.html
-fatal: Not a git repository: '/annex/.git'
-error: could not lock config file /annex/.git/config: No such file or directory
-"""]]
-
-> I've fixed this! [[done]] Yay!! Get the fix from the hourly windows autobuilder.
-> --[[Joey]]
diff --git a/doc/bugs/__39__Internal_Server_Error__39___when_creating_repo_on_other_drive_than_C:_on_Windows/comment_1_ea3b2c0e3bdfb50ac0dce10ba1b6339f._comment b/doc/bugs/__39__Internal_Server_Error__39___when_creating_repo_on_other_drive_than_C:_on_Windows/comment_1_ea3b2c0e3bdfb50ac0dce10ba1b6339f._comment
deleted file mode 100644
index 9b476c598..000000000
--- a/doc/bugs/__39__Internal_Server_Error__39___when_creating_repo_on_other_drive_than_C:_on_Windows/comment_1_ea3b2c0e3bdfb50ac0dce10ba1b6339f._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 1"
- date="2013-12-24T21:36:04Z"
- content="""
-I can reproduce this bug (using drive E:)
-
-It's caused by [[!commit e93206e2945c476c3305a73e41113efd781268cd]], which forced msysgit to use unix-style paths to repositories.
-
-Unless I can find a way to use dos-style paths with msysgit 1.8.4 (or it's fixed in a newer version), I can't pass it drive letters, so it tries to use the default/current drive instead of the one where the repository is really located.
-
-My preferences to fix this:
-
-1. Try a newer msysgit, and perhaps it's fixed there to support --git-dir with a DOS-style path. (For example, in C:\FOO, see if this command work: `git init; git --git-dir=C:\FOO\.git --work-tree=C:\FOO status`)
-2. File a bug on msysgit, get it fixed. 1.8.3.msysgit.0 *did* support that.
-3. Make git-annex not pass --git-dir and --work-tree in Windows. But this would be quite ugly; while normally it is operating in the repository in the CWD, sometimes it's not.
-
-Workaround: if you're at the prompt, this works, because it changes the current drive before using git-annex, and so the unix-style paths just work:
-
-    E:
-    cd annex
-    git annex init
-"""]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content.mdwn b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content.mdwn
deleted file mode 100644
index 6dcb1ec6b..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-What steps will reproduce the problem?
-
-running the assistant on my setup, which is a central 'client' repo, and two 'backup' repos on a USB drive and an ssh connection to another server.  Both of those backup repos are non-bare, and I occasionally manually run 'git annex sync' on them to keep them up to date.  I have 'numcopies' set to 2.
-
-
-What is the expected output? What do you see instead?
-
-I expect everything to be copied to the 'backup' repos and content in the 'archive' subdirectories of the 'client' repo to be dropped.
-
-What happened instead: This morning, I started up the assistant without the USB drive present.  I added one file to my client repo.  The assistant began copying it to the SSH backup repo.  I then plugged in the USB drive, and it began copying it to the USB repo; however, it *also* queued up large amounts of content in 'archive' subdirectories and started copying it down onto my client repo, which is unacceptable because there is not actually enough disk space on the client machine to hold everything in the 'archive' subdirectories!  I stopped the assistant and started it up again.  It started doing the same thing (queueing up archive content to transfer to client), and in addition started dropping content from my USB drive.  This seems very similar to the bug in the previous version, where the globbing was broken.  It's acting as if my usb remote preferred no content at all, and it transfers everything away from it and drops it -- and at the same time, brings in content which is not supposed to be there on my client machine.  Strangely it's not doing the same thing on the ssh remote -- the ssh remote is fine.  No anomalies there -- it has not been trying to drop content from there.
-
-This is just happening this morning -- I compiled 4.20130227 last night and ran the assistant and it behaved correctly, with no bugs at all.  Now when I run it, it's going crazy.
-
-What version of git-annex are you using? On what operating system?
-
-4.20130227 on OS X.
-
-
-Please provide any additional information below.
-
-One thing that would be incredibly helpful with the kinds of bugs I've seen in the assistant is if the daemon.log contained info about *why* it is dropping or transferring content.  "transferring content because there was only 1 copy and we need to fulfill numcopies" "transferring content because it matches such-and-such a preferred content expresson" "dropping content because it does not match this preferred content expression" -- that would remove a lot of mystery about the way the assistant is working.
-
-> The several bugs mentioned here seem to be fixed, so closing this report.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_1_56f9cd5cc2e089b32cb076dc2e2a8ca5._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_1_56f9cd5cc2e089b32cb076dc2e2a8ca5._comment
deleted file mode 100644
index cf309b8b3..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_1_56f9cd5cc2e089b32cb076dc2e2a8ca5._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-01T19:59:23Z"
- content="""
-I've added some debug info to the log for transfers and drops. You have to start the assistant with the --debug flag, then you'll get stuff like:
-
-<pre>
-[2013-03-01 15:23:10 JEST] Committer: queued Upload UUID \"a0cd7cb6-57ee-4551-955f-aa77738135cc\" myfile : newly added file
-[2013-03-01 15:25:00 JEST] Watcher: queued Download UUID \"a0cd7cb6-57ee-4551-955f-aa77738135cc\" ./foo : new or renamed file wanted
-[2013-03-01 15:54:00 JEST] Watcher: dropped ./archive/foo (from: here) (copies now: 1): file renamed
-</pre>
-
-It would take more work to show the preferred content expressions that caused the transfer or drop, but this is simple to determine:
-
-* for Uploads it should always be the preferred content expression of the remote being uploaded to
-* for Downloads it is always the preferred content expression of the local repository
-* for drops it is always the preferred content expression of the repository it is dropped from
-
-Have not managed to reproduce problem yet.
-"""]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_2_21c0f7f328cb51080fbd97e086c47a30._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_2_21c0f7f328cb51080fbd97e086c47a30._comment
deleted file mode 100644
index 5eb511b65..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_2_21c0f7f328cb51080fbd97e086c47a30._comment
+++ /dev/null
@@ -1,37 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 2"
- date="2013-03-03T18:44:35Z"
- content="""
-I rebuilt and ran with --debug, and started up git annex.  It behaved itself. 
-
-I tried restarting it, unplugging and plugging back in my USB drive to see if it provoked any problems -- none.
-
-I decided to try adding something.  I added a music video to my Movies/Music directory.  It uploaded it to my ssh remote but not to the USB drive and, bizarrely, when I use \"git annex whereis\" it doesn't show it as existing *anywhere*:
-
-    annex$ git annex whereis Movies/Music/Tanlines\ -\ All\ Of\ Me.flv
-    annex$ 
-
-It does in fact exist in all three repos!  The link is there:
-
-annex$ ls -l Movies/Music/Tanlines\ -\ All\ Of\ Me.flv 
-lrwxr-xr-x  1 ed  staff  206 Mar  3 13:18 Movies/Music/Tanlines - All Of Me.flv -> ../../.git/annex/objects/0k/j6/SHA256E-s37822147--c9df1d6c9f6d2d72e039de9705ea4673160da32eb0cc9ea87e65003506d9297d.flv/SHA256E-s37822147
-
-the object is there!
-
-annex$ ls -l .git/annex/objects/0k/j6/SHA256E-s37822147--c9df1d6c9f6d2d72e039de9705ea4673160da32eb0cc9ea87e65003506d9297d.flv/SHA256E-s37822147--c9df1d6c9f6d2d72e039de9705ea4673160da32eb0cc9ea87e65003506d9297d.flv
--r--r--r--  1 ed  staff  37822147 Mar  3 13:17 .git/annex/objects/0k/j6/SHA256E-s37822147--c9df1d6c9f6d2d72e039de9705ea4673160da32eb0cc9ea87e65003506d9297d.flv/SHA256E-s37822147--c9df1d6c9f6d2d72e039de9705ea4673160da32eb0cc9ea87e65003506d9297d.flv
-
-The corresponding object also exists in the .git/annex/objects directory of the USB remote and the ssh remote.
-
-here's a pastebin of the daemon.log: http://pastebin.com/BGRBQ6Rx
-
-Shut down the daemon to see if that changed anything; nope.  \"Whereis\" still comes up blank.  Tried a git annex fsck --fast to see if that changed anything; nope.  \"Whereis\" still comes up blank.
-
-Any ideas?  Is the log revealing at all?
-
-
-
-
-"""]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_3_3287b2f25f3b5ae4c27f4748694563ee._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_3_3287b2f25f3b5ae4c27f4748694563ee._comment
deleted file mode 100644
index e108052d7..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_3_3287b2f25f3b5ae4c27f4748694563ee._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-03-03T18:53:23Z"
- content="""
-Are you sure the file in question is checked into git? Because git-annex ignores symlinks that are not checked into git.
-"""]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_4_e515eca68a70d40c522805d7e0d7c0e6._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_4_e515eca68a70d40c522805d7e0d7c0e6._comment
deleted file mode 100644
index 4a533fc92..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_4_e515eca68a70d40c522805d7e0d7c0e6._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 4"
- date="2013-03-03T18:58:42Z"
- content="""
-Just to see what happened, I re-added that same file in another directory manually (not with the assistant).
-
-git annex whereis instantly showed that it was in all the other repositories.
-
-I finally thought to try a \"git status\" -- it showed that with for the original copy of this I added, the actual symlink was never checked into git.
-
-    annex$ git status
-    # On branch master
-    # Untracked files:
-    #   (use \"git add <file>...\" to include in what will be committed)
-    #
-    #	Movies/Music/Tanlines - All Of Me.flv
-    nothing added to commit but untracked files present (use \"git add\" to track)
-    annex$ 
-
-This is probably all unrelated to the original topic of the bug -- I am not seeing the \"client repo starts pulling in archive content, dropping it from backup remote\" issue anymore.
-
-"""]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_5_b27f4c103dda050b6e9cf03ea3157abc._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_5_b27f4c103dda050b6e9cf03ea3157abc._comment
deleted file mode 100644
index 434bcb1dd..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_5_b27f4c103dda050b6e9cf03ea3157abc._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-03-03T19:42:19Z"
- content="""
-A symlink not added to git could happen with the assistant for various reasons. For example, if the assistant was shut down before it got a chance to stage a newly added file. The assistant detects such symlinks when started up and will add them then.
-
-Back to the original bug report..
-"""]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_6_2cc7083dab944705bf91fc00319b75e6._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_6_2cc7083dab944705bf91fc00319b75e6._comment
deleted file mode 100644
index 9f110d30d..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_6_2cc7083dab944705bf91fc00319b75e6._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 6"
- date="2013-03-04T00:20:25Z"
- content="""
-Since I can't reproduce the \"copy archived content to the client repo then drop it from the backup repo\" anymore, I guess we can close.  If I notice anything like that happening again I have the --debug flag available to investigate and open a new bug report.
-
-"""]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_7_1175f9be789d4c1907f0be98e435bd2f._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_7_1175f9be789d4c1907f0be98e435bd2f._comment
deleted file mode 100644
index 1f11f8bed..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_7_1175f9be789d4c1907f0be98e435bd2f._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 7"
- date="2013-03-04T00:57:38Z"
- content="""
-With the new Preferences page I added to the webapp today you can also enable debugging while the assistant is running if it starts to misbehave.
-
-However, I'm in no hurry to close this bug just yet.
-"""]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_8_78e6164ef67a9560a3a9ead1f7a72473._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_8_78e6164ef67a9560a3a9ead1f7a72473._comment
deleted file mode 100644
index c49cbbeef..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_8_78e6164ef67a9560a3a9ead1f7a72473._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 8"
- date="2013-03-08T14:46:55Z"
- content="""
-I've not seen this kind of strange behavior happen again so far.
-
-But I have got another example of a file which I added to git-annex via the assistant not having its symlink added to git.  Again, the content of the file is in git-annex and was even correctly transferred to a couple of remotes, but the symlink is still unstaged.
-
-I tried restarting the assistant to see if that would fix it but that didn't change anything.
-
-I imagine the symlink will be fixed during a daily scan, tomorrow maybe?  Is it problematic for the symlink not to be checked into git for a day?  Is this worth a bug report or is this really harmless behavior?
-
-"""]]
diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_9_1d578fd13022dcd6382b415a7f6e097a._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_9_1d578fd13022dcd6382b415a7f6e097a._comment
deleted file mode 100644
index 9c2cd3c75..000000000
--- a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_9_1d578fd13022dcd6382b415a7f6e097a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 9"
- date="2013-03-18T15:45:19Z"
- content="""
-There turned out to be a bug specific to OSX that prevented symlinks being checked into git. The daily sanity check did eventually add them. I fixed this bug yesterday.
-"""]]
diff --git a/doc/bugs/__91__Installation__93___There_is_no_available_version_of_quickcheck_that_satisfies___62____61__2.1.mdwn b/doc/bugs/__91__Installation__93___There_is_no_available_version_of_quickcheck_that_satisfies___62____61__2.1.mdwn
deleted file mode 100644
index a6e2423a8..000000000
--- a/doc/bugs/__91__Installation__93___There_is_no_available_version_of_quickcheck_that_satisfies___62____61__2.1.mdwn
+++ /dev/null
@@ -1,40 +0,0 @@
-Hi,
-
-I just wanted to install git-annex via cabal, as described in the install document. More specifically, I did this on my Ubuntu Lucid box:
-
-    andreas@antares:~$ sudo aptitude install cabal-install
-    [...]
-    andreas@antares:~$ cabal update
-    andreas@antares:~$ cabal install quickcheck --bindir=$HOME/bin
-    andreas@antares:~$ cabal install git-annex -v --bindir=$HOME/bin
-
-However, I got this error:
-
-    /usr/bin/ghc --numeric-version
-    looking for package tool: ghc-pkg near compiler in /usr/bin
-    found package tool in /usr/bin/ghc-pkg
-    /usr/bin/ghc-pkg --version
-    /usr/bin/ghc --supported-languages
-    Reading installed packages...
-    /usr/bin/ghc-pkg dump --global
-    /usr/bin/ghc-pkg dump --user
-    Reading available packages...
-    Resolving dependencies...
-    selecting
-    cabal: cannot configure git-annex-3.20120113. It requires quickcheck >=2.1
-    There is no available version of quickcheck that satisfies >=2.1
-
-which is really strange, because quickcheck 2.4.2 is installed:
-
-    andreas@antares:~$ ls -a .cabal/lib/
-    .  ..  QuickCheck-2.4.2
-
-Any help is greatly appreciated :)
-Andreas.
-
-> QuickCheck has to be spelled in mixed case. --[[Joey]] 
-
-Sorry to disagree, this doesn't fix my problem. cabal still complains that no version >= 2.1 is available, even though 2.4.2 is installed. This problem already occurred before I explicitly installed QuickCheck. According to [[install]], the `cabal install git-annex -v --bindir=$HOME/bin` should already take care of the dependencies.
-
->> You need to `cabal update` to get the fixed version of git-annex which
->> spells QuickCheck correctly. [[done]] --[[Joey]]
diff --git a/doc/bugs/__91__webapp__93___pause_syncing_with_specific_repository.mdwn b/doc/bugs/__91__webapp__93___pause_syncing_with_specific_repository.mdwn
deleted file mode 100644
index dca16e4d3..000000000
--- a/doc/bugs/__91__webapp__93___pause_syncing_with_specific_repository.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-[Due to some stupid issue on my and AT&T's part] one of my remote repositories is currently unreachable. I would like to tell the webapp/assistant to not attempt to sync with it, or, at least, modify this error message to be more specific (by telling me which repository is unreachable).
-
-In a red bubble it says: "Synced with rose 60justin"
-
-That verbage is the same if they all succeed. The only difference is the red instead of green. Would be nice to know exactly which machine to kick (if I didn't already know, eg I was syncing only with repositories not under my control).
-
-> Fixed alert display. Webapp has allowed pausing syncing with a repository
-> for a while. [[done]] --[[Joey]]
diff --git a/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu.mdwn b/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu.mdwn
deleted file mode 100644
index 97b72c49c..000000000
--- a/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-### Please describe the problem.
-
-quite often is desired to fetch/navigate through the git annex installation under git annex user, e.g. to fetch the log to be provided here for the "additional information".
-Given already big size of the app bundling some lightweight ssh server should not be a major size hit, but would ease troubleshooting and bug reporting
-
-### What steps will reproduce the problem?
-
-
-### What version of git-annex are you using? On what operating system?
-
-Android from Nov 18
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> Not a direction I want to go in with the Android app. [[done]] --[[Joey]] 
diff --git a/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_1_9bb53c45d685b368c7ba1758885f2874._comment b/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_1_9bb53c45d685b368c7ba1758885f2874._comment
deleted file mode 100644
index 36440eac5..000000000
--- a/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_1_9bb53c45d685b368c7ba1758885f2874._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 1"
- date="2013-11-26T16:09:19Z"
- content="""
-This was previously suggested in the forum: [[forum/Suggestion:_Put_ssh_server_back_into_android_version]]
-
-As said there, I feel that `adb` is a better option in these situations. Of course, the git-annex bundle already has a ssh client, so you can rsync files from it to other ssh servers too.
-
-Also, the bundle is too big, I don't want to make it any bigger.
-"""]]
diff --git a/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_2_251311a04f1a610e54ebe8e9b92de72e._comment b/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_2_251311a04f1a610e54ebe8e9b92de72e._comment
deleted file mode 100644
index 48707e82b..000000000
--- a/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_2_251311a04f1a610e54ebe8e9b92de72e._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://yarikoptic.myopenid.com/"
- nickname="site-myopenid"
- subject="comment 2"
- date="2013-11-27T04:30:53Z"
- content="""
-we just shrinked the bundle by 60MB so there could be some space for sshd.
-
-adb might indeed be more powerful but would require usb connection (right?) -- at times not convenient
-
-syncing via ssh from phone: that is what I was trying to avoid -- working in the shell on the phone -- it is possible but a bit \"inconvenient\"
-sshd could be ran on any unprivileged port while letting the user who starts it know the IP and the port, thus making it easy to connect.
-"""]]
diff --git a/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_3_83ac87a01639776a6e519af226bd84d5._comment b/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_3_83ac87a01639776a6e519af226bd84d5._comment
deleted file mode 100644
index c6cccfeb3..000000000
--- a/doc/bugs/__91__wishlistAndroid:_bundle_an_ssh_server___40__dropbear__63____41___and_add_an_option_to_start_it_easily_with_the_terminal_app_menu/comment_3_83ac87a01639776a6e519af226bd84d5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U"
- nickname="Carlo"
- subject="comment 3"
- date="2013-11-28T15:28:36Z"
- content="""
-I made that previous suggestion... I'm using sshelper right now, outstanding server. He seems to have already worked through all kinds of android specific details for running an SSH server. Of course, you don't get all the git goodness. I wonder how hard it would be to get runshell working when logging in through SSHelper, or provide an add an SSHelper style configured OpenSSH binary for the git annex shell.
-"""]]
diff --git a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op.mdwn b/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op.mdwn
deleted file mode 100644
index 54920fa31..000000000
--- a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-### Please describe the problem.
-
-`git annex fix` only works on files that have been annexed, already.
-While that's a safety measure of course, an option like `--force` or similar would be nice if one is shuffling around data by hand.
-
-### What steps will reproduce the problem?
-
-Please see [[bugs/__96__git_annex_add__96___changes_mtime_if_symlinks_are_fixed_in_the_background/]] for details; I didn't want to spam exactly the same output twice.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex 4.20130709 on Debian unstable i386 and x64.
-
-> We've discussed this on IRC and there seems to be nothing more to do here.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_1_9b671e583eec5adf870dccd1e97b5dbc._comment b/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_1_9b671e583eec5adf870dccd1e97b5dbc._comment
deleted file mode 100644
index f2db49dd4..000000000
--- a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_1_9b671e583eec5adf870dccd1e97b5dbc._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.235"
- subject="comment 1"
- date="2013-07-11T15:26:52Z"
- content="""
-I don't understand what you want fix to do when run on files that are not annexed.
-"""]]
diff --git a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_2_d11744202213d6f897f4234bc4c70c18._comment b/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_2_d11744202213d6f897f4234bc4c70c18._comment
deleted file mode 100644
index 20b3a251e..000000000
--- a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_2_d11744202213d6f897f4234bc4c70c18._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2013-07-11T20:18:44Z"
- content="""
-I wanted to use it as a way to prepare the files before running `git annex add`. I like to have everything exactly how I want it before I add anything to git, or git-annex. Does git-annex do anything in the git-annex branch prior to running the pre-commit hook? I.e. is there any penalty, however slight, in running `git annex add` several times while moving stuff around?
-
-"""]]
diff --git a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_3_a729deb465ff44f5a9b87c963cd6235a._comment b/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_3_a729deb465ff44f5a9b87c963cd6235a._comment
deleted file mode 100644
index d4c65308d..000000000
--- a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_3_a729deb465ff44f5a9b87c963cd6235a._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 3"
- date="2013-07-13T15:05:53Z"
- content="""
-With git-annex built from current Git (i.e. the mtime fix for `git annex fix/add` applied), I have imported directory structure and objects (I will write a blog post along with scripts and pitfalls about that once the process is totally finished) and been running `git annex add` and `git mv` repeatedly to keep things up to date.
-
-As I now need to rename a few files with globs (`zmv`/`rename`) where `git mv` does not really cut it, I am in between a rock and a hard place. Most likely, I will `git checkout -- .`, rename, and `git annex add` again. I am pretty sure that `git annex add` does not do anything other than staging in the current branch and does not touch the `git-annex` branch. But I don't _know_.
-
-Long story short, it would make both my workflow easier and give me more peace of mind if there was a `git annex fix --untracked` or similar which does exactly the same, but operates on files that are not checked in and/or staged.
-
-As an aside, `git annex fsck --untracked` which is basically `git annex fsck --numcopies=1` on untracked files would be.... awesome.
-
-"""]]
diff --git a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_4_3f735503df9a08472d42fabd219c2ec5._comment b/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_4_3f735503df9a08472d42fabd219c2ec5._comment
deleted file mode 100644
index 41f4e9db8..000000000
--- a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_4_3f735503df9a08472d42fabd219c2ec5._comment
+++ /dev/null
@@ -1,31 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 4"
- date="2013-07-18T19:27:41Z"
- content="""
-It seems to me that what you're looking for is:
-
-<pre>
-git annex import /dir
-mv foo bar
-...
-git add .
-git annex fix
-git commit
-</pre>
-
-This avoids the minor overhead of `git annex add` when run on a symlink updating the location tracking information.
-
-(Note that the manual call to `git annex fix` there is entirely unnecessary, since the pre-commit hook does the same thing when you commit.)
-
-Alternatively:
-
-<pre>
-git annex import /dir -c annex.alwayscommit=false
-mv foo bar
-...
-git annex add
-git commit
-</pre>
-"""]]
diff --git a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_5_2c61eabbba7fd2a52ba02d59a0a76a42._comment b/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_5_2c61eabbba7fd2a52ba02d59a0a76a42._comment
deleted file mode 100644
index a417dac02..000000000
--- a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_5_2c61eabbba7fd2a52ba02d59a0a76a42._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 5"
- date="2013-07-18T19:29:02Z"
- content="""
-Note that the second option will work in direct mode; first one won't.
-"""]]
diff --git a/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories.mdwn b/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories.mdwn
deleted file mode 100644
index 1027cdd56..000000000
--- a/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories.mdwn
+++ /dev/null
@@ -1,115 +0,0 @@
-### Please describe the problem.
-
-`git annex import otherrepo` does not work.
-
-
-### What steps will reproduce the problem?
-
-    richih@eudyptes  ~ % mcd killme/git-annex-source
-    richih@eudyptes  ~/killme/git-annex-source % git init; git annex init
-    Initialized empty Git repository in /home/richih/killme/git-annex-source/.git/
-    init  ok
-    (Recording state in git...)
-    richih@eudyptes (git)-[master] ~/killme/git-annex-source % dd if=/dev/urandom of=foo bs=1M count=1
-    1+0 records in
-    1+0 records out
-    1048576 bytes (1.0 MB) copied, 0.281043 s, 3.7 MB/s
-    richih@eudyptes (git)-[master] ~/killme/git-annex-source % git annex add .
-    add foo (checksum...) ok
-    (Recording state in git...)
-    richih@eudyptes (git)-[master] ~/killme/git-annex-source % git commit -m files
-    [master (root-commit) 8054eeb] files
-     1 file changed, 1 insertion(+)
-     create mode 120000 foo
-    richih@eudyptes (git)-[master] ~/killme/git-annex-source % mcd ../git-annex-import
-    richih@eudyptes  ~/killme/git-annex-import % git init; git annex init
-    Initialized empty Git repository in /home/richih/killme/git-annex-import/.git/
-    init  ok
-    (Recording state in git...)
-    richih@eudyptes (git)-[master] ~/killme/git-annex-import % git annex import ../git-annex-source/foo
-    richih@eudyptes (git)-[master] ~/killme/git-annex-import % ls
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130920 on Debian Sid
-
-
-### PS:
-
-To add insult to injury, this does "work":
-
-    ih@eudyptes (git)-[master] ~/killme/git-annex-import % mcd bar
-    richih@eudyptes (git)-[master] ~/killme/git-annex-import/bar % git annex import ../../git-annex-source/
-    import .git/description (checksum...) ok
-    import .git/HEAD (checksum...) ok
-    import .git/config (checksum...) ok
-    import .git/index (checksum...) ok
-    import .git/COMMIT_EDITMSG (checksum...) ok
-    import .git/refs/heads/git-annex (checksum...) ok
-    import .git/refs/heads/master (checksum...) ok
-    import .git/hooks/update.sample (checksum...) ok
-    import .git/hooks/applypatch-msg.sample (checksum...) ok
-    import .git/hooks/pre-rebase.sample (checksum...) ok
-    import .git/hooks/pre-commit.sample (checksum...) ok
-    import .git/hooks/pre-applypatch.sample (checksum...) ok
-    import .git/hooks/prepare-commit-msg.sample (checksum...) ok
-    import .git/hooks/commit-msg.sample (checksum...) ok
-    import .git/hooks/post-update.sample (checksum...) ok
-    import .git/hooks/pre-push.sample (checksum...) ok
-    import .git/hooks/pre-commit (checksum...) ok
-    import .git/info/exclude (checksum...) ok
-    import .git/objects/4b/825dc642cb6eb9a060e54bf8d69288fbee4904 (checksum...) ok
-    import .git/objects/a2/6f9bdbe47ada699d537eaa8b6fbfc1e53ef214 (checksum...) ok
-    import .git/objects/30/4b790d132863d54313e2380bed17e557944f08 (checksum...) ok
-    import .git/objects/ab/09feaa1b55080f42ccfad8c8bb5612f2397c5a (checksum...) ok
-    import .git/objects/95/b73ee41ebe8abbd5d8c0c368d1148b5256d4f2 (checksum...) ok
-    import .git/objects/2e/96f9962c1baf83c563aa59dcc67e19f21d4b1f (checksum...) ok
-    import .git/objects/74/6306e594874907246b2300b3af22f2805dde3e (checksum...) ok
-    import .git/objects/5b/11e29d0ef96be4ee73f8dae9b2f525cb808ef1 (checksum...) ok
-    import .git/objects/fc/0c0dc4d0579a15c20be29186a27feb2ee77304 (checksum...) ok
-    import .git/objects/73/c38d817e0a9f1ef4699551ae83130edd166364 (checksum...) ok
-    import .git/objects/c9/80716b5b506515410ca3ad1d88ceae13d8f6f9 (checksum...) ok
-    import .git/objects/e2/6cb10dbce11f4065c249183bb085d0afc1b55d (checksum...) ok
-    import .git/objects/80/54eeb150b094b0d8483c43ccf2ddf182c71bd3 (checksum...) ok
-    import .git/annex/sentinal (checksum...) ok
-    import .git/annex/sentinal.cache (checksum...) ok
-    import .git/annex/index (checksum...) ok
-    import .git/annex/index.lck (checksum...) ok
-    import .git/annex/journal.lck (checksum...) ok
-    import .git/annex/objects/F7/zw/SHA256E-s1048576--74f3a1a65df608d1c8ae575f83c6ee21a5aeb1a914ca73f202a881f8c3ba8f59/SHA256E-s1048576--74f3a1a65df608d1c8ae575f83c6ee21a5aeb1a914ca73f202a881f8c3ba8f59 
-    git-annex: ../../git-annex-source/.git/annex/objects/F7/zw/SHA256E-s1048576--74f3a1a65df608d1c8ae575f83c6ee21a5aeb1a914ca73f202a881f8c3ba8f59/SHA256E-s1048576--74f3a1a65df608d1c8ae575f83c6ee21a5aeb1a914ca73f202a881f8c3ba8f59: rename: permission denied (Permission denied)
-    failed
-    import .git/logs/HEAD (checksum...) ok
-    import .git/logs/refs/heads/git-annex (checksum...) ok
-    import .git/logs/refs/heads/master (checksum...) ok
-    (Recording state in git...)
-    error: Invalid path 'bar/.git/COMMIT_EDITMSG'
-    error: unable to add bar/.git/COMMIT_EDITMSG to index
-    fatal: adding files failed
-    
-    git-annex: user error (xargs ["-0","git","--git-dir=/home/richih/killme/git-annex-import/.git","--work-tree=/home/richih/killme/git-annex-import","add","--"] exited 123)
-    failed
-    git-annex: import: 2 failed
-    richih@eudyptes (git)-[master] ~/killme/git-annex-import/bar % ls -la
-    total 0
-    drwxr-xr-x 3 richih richih  17 Sep 24 01:45 .
-    drwxr-xr-x 4 richih richih  38 Sep 24 01:45 ..
-    drwxr-xr-x 8 richih richih 152 Sep 24 01:45 .git
-    richih@eudyptes (git)-[master] ~/killme/git-annex-import/bar % 
-
-> I have made git-annex import skip .git directories. Of course,
-> running it on *any* directory without the --duplicate option
-> will result in it moving data to git-annex, so is not advisable
-> to do that if you want to keep the data in the directory where it was.
-> 
-> I am doubtful about special-casing git-annex import to do something
-> else when told to import a git-annex repository. It seems a bit of a
-> slippery slope to it getting very complicated, which we seem to already be
-> further down than I would like. If people are this pissed off about
-> git-annex import's behavior,
-> I would be inclined to *remove* it. Then you can use `mv` and `git annex
-> add`. I originally wrote git-annex import just to avoid needing to run
-> those 2 commands myself, and I can make my own local shell script 
-> to do that... --[[Joey]]
-
->> Well, I guess skipping .git is enough. [[done]] --[[Joey]] 
diff --git a/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_1_94ccd548c084286163eeb2af1ddc18e3._comment b/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_1_94ccd548c084286163eeb2af1ddc18e3._comment
deleted file mode 100644
index 4de9cc10d..000000000
--- a/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_1_94ccd548c084286163eeb2af1ddc18e3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.220"
- subject="comment 1"
- date="2013-09-25T18:21:25Z"
- content="""
-Import skips symlinks and other non-regular files. It would work if the source repository was in direct mode.
-"""]]
diff --git a/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_2_befde3ef3d2b171ebb691915ff3af172._comment b/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_2_befde3ef3d2b171ebb691915ff3af172._comment
deleted file mode 100644
index 9996882fc..000000000
--- a/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_2_befde3ef3d2b171ebb691915ff3af172._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://id.koumbit.net/anarcat"
- ip="72.0.72.144"
- subject="it's worse than not working, it kills! :)"
- date="2013-10-07T12:06:22Z"
- content="""
-so yeah, it doesn't really work well, and maybe that is to be expected because of symlinks, but it's much worse than that: the original git annex repo will actually be destroyed because git annex import will [[trash the .git metadata directory|bugs/git_annex_import_destroys_a_fellow_git_annex_repository]]. Recovering from that is... interesting, to say the least. :)
-"""]]
diff --git a/doc/bugs/__96__git_annex_sync__96___ignores_remotes.mdwn b/doc/bugs/__96__git_annex_sync__96___ignores_remotes.mdwn
deleted file mode 100644
index 825d9527b..000000000
--- a/doc/bugs/__96__git_annex_sync__96___ignores_remotes.mdwn
+++ /dev/null
@@ -1,106 +0,0 @@
-### Please describe the problem.
-
-A mere `git annex sync` does not go through the reachable remotes.
-
-### What steps will reproduce the problem?
-
-I do not know what could have put my repository in this state.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130802-g1452ac3
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-local repository version: 4
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-
-Linux dawn 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64 GNU/Linux
-
-### Please provide any additional information below.
-
-[[!format sh """
-% git annex status
-supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-supported remote types: git S3 bup directory rsync web webdav glacier hook
-repository mode: direct
-trusted repositories: 1
-	f3cb4e8f-65f1-4ded-a6a1-abef64ddcff5 -- zoidberg (sam@git-annex:/media/git-annex/Music)
-semitrusted repositories: 5
-	00000000-0000-0000-0000-000000000001 -- web
- 	063a31dc-542d-407f-a9ed-124479fa6354 -- here (dawn)
- 	22b72aa6-058b-4622-8132-27aa2d8950dc -- arrakis (sam@arrakis:~/Music)
- 	5b3a1abf-5e0b-41bc-a141-774d6236ec76 -- backup on old USB disk
- 	6affec3c-fd26-11e2-9ddd-53f02e5ca176 -- music on eeePC
-untrusted repositories: 0
-transfers in progress: none
-available local disk space: 9.83 gigabytes (+1 megabyte reserved)
-local annex keys: 3947
-local annex size: 23.51 gigabytes
-known annex keys: 3965
-known annex size: 23.56 gigabytes
-bloom filter size: 16 mebibytes (0.8% full)
-backend usage: 
-	SHA256E: 7912
-
-% git remote -v
-arrakis	arrakis:Music (fetch)
-arrakis	arrakis:Music (push)
-zoidberg	ssh://git-annex@zoidberg.rfc1149.net:2222/~/Music (fetch)
-zoidberg	ssh://git-annex@zoidberg.rfc1149.net:2222/~/Music (push)
-
-# Note how here it does not seem to sync with any remote
-% git annex sync
-(Recording state in git...)
-commit  
-ok
-
-% git annex sync zoidberg
-(Recording state in git...)
-commit  
-ok
-pull zoidberg 
-ok
-push zoidberg 
-Everything up-to-date
-ok
-
-% git annex sync arrakis
-(Recording state in git...)
-commit  
-ok
-pull arrakis 
-From arrakis:Music
-   c1a24bd..ba060b7  git-annex  -> arrakis/git-annex
-   98b9a8e..be9c146  master     -> arrakis/master
-   e0df2be..be9c146  synced/master -> arrakis/synced/master
-ok
-
-# A nameless sync with debug turned on
-% git annex sync --debug        
-[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","symbolic-ref","HEAD"]
-[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","refs/heads/master"]
-[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","git-annex"]
-[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..ba060b7777413ab687d64771b5d6c2b36a072335","--oneline","-n1"]
-[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..f401f2b7b67567862df7c5b8d304f52c3af43f4b","--oneline","-n1"]
-[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..feaba7c5ea5f4ca73c123e6ea44ffd6333bf383e","--oneline","-n1"]
-[2013-08-06 10:59:57 CEST] chat: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","cat-file","--batch"]
-[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","ls-files","--stage","-z","--others","--exclude-standard","--","/home/sam/Music"]
-[2013-08-06 10:59:57 CEST] chat: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","cat-file","--batch"]
-(Recording state in git...)
-[2013-08-06 11:00:16 CEST] feed: xargs ["-0","git","--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","add","-f"]
-commit  
-[2013-08-06 11:00:16 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","commit","-m","git-annex automatic sync"]
-ok
-[2013-08-06 11:00:17 CEST] call: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","--verify","-q","refs/heads/synced/master"]
-[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/master..refs/heads/synced/master","--oneline","-n1"]
-[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","git-annex"]
-[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..ba060b7777413ab687d64771b5d6c2b36a072335","--oneline","-n1"]
-[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..f401f2b7b67567862df7c5b8d304f52c3af43f4b","--oneline","-n1"]
-[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..feaba7c5ea5f4ca73c123e6ea44ffd6333bf383e","--oneline","-n1"]
-[2013-08-06 11:00:17 CEST] call: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","branch","-f","synced/master"]
-"""]]
-
-[[done]]
diff --git a/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_1_39421e6935233cd8f45949ebdef369fe._comment b/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_1_39421e6935233cd8f45949ebdef369fe._comment
deleted file mode 100644
index a88baa834..000000000
--- a/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_1_39421e6935233cd8f45949ebdef369fe._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 1"
- date="2013-08-07T16:13:31Z"
- content="""
-It seems to me that you must have set `git config remote.zoidberg.annex-sync false`
-(or clicked around in the webapp and caused it to set that). If you set annex-sync back to true, it will sync with all remotes by default.
-"""]]
diff --git a/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_2_53fb15d6fbf96d43564ff7c866239d18._comment b/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_2_53fb15d6fbf96d43564ff7c866239d18._comment
deleted file mode 100644
index 1b870e1f7..000000000
--- a/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_2_53fb15d6fbf96d43564ff7c866239d18._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://www.rfc1149.net/"
- nickname="Sam"
- subject="Indeed"
- date="2013-08-07T16:17:41Z"
- content="""
-You are perfectly right. Every remote had this parameter set to false for a reason I do not know.
-"""]]
diff --git a/doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn b/doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn
deleted file mode 100644
index 471a698a0..000000000
--- a/doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-The command `git annex dropunused` currently takes a number, as referenced in output of last `git annex unused` command.
-
-When you want to drop all, or a range, this may be annoying, as you have to specify each number on the command line. 
-
-A range argument, such as `1-1845`, possibly combined with other argument types (Cf. many print dialogues: `1,3,5-7,9`) would be great.
-
-I work around this lack as I want to drop all unused files anyway by something like this:
-       
-    git annex unused | grep -o -P "^    [0-9]+" | xargs git annex dropunused
-
-> It's designed to be used with `seq`. There's an example in the
-> [[walkthrough|walkthrough/unused_data]], and of course multiple seq calls can be used to
-> specifiy multiple ranges. So:
-
-	git annex dropunused `seq 1 9` `seq 11 1845`
-
-> I don't see adding my own range operations to be an improvement worth
-> making; it'd arguably only be a complication. --[[Joey]] [[done]]
-
->> Actually, this did get implemented, since using seq could fall afoul 
->> of command-line length limits in extreme cases.
diff --git a/doc/bugs/add_script-friendly_output_options.mdwn b/doc/bugs/add_script-friendly_output_options.mdwn
deleted file mode 100644
index 7d7bdfc51..000000000
--- a/doc/bugs/add_script-friendly_output_options.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-I have a need to use git-annex from a larger program. It'd be great if the information output by some of the commands that is descriptive (for example, whereis) could be sent to stdout in a machine-readable format like (preferably) JSON, or XML. That way I can simply read in the output of the command and use the data directly instead of having to parse it via regexes or other such string manipulation.
-
-This could perhaps be triggered by a --json or --xml flag to the relevant commands.
-
-> This is [[done]], --json is supported by all commands, more or less.
-> 
-> Caveats: 
-> 
->  * the version, status, and find commands produce custom output and so
->    no json. This could change for version and status; find needs to just
->    be a simple list of files, I think 
->  * The "note" fields may repeat multiple times per object with different
->    notes and are of course not machine readable, and subject to change.
->  * Output of helper commands like rsync is not diverted away, and
->    could clutter up the json output badly. Should only affect commands
->    that transfer data. And AFAICS, wget and rsync both output their
->    progress displays to stderr, so shouldn't be a problem.
-> 
-> --[[Joey]] 
diff --git a/doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error.mdwn b/doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error.mdwn
deleted file mode 100644
index bb340231f..000000000
--- a/doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-### Please describe the problem.
-adding an rsync.net repo returns an internal server error "user error (gpg ["--quite","--trust-model","always","--gen-random","--armor","1","512"] exited 127)
-
-
-### What steps will reproduce the problem?
-add an rsync.net repo
-
-
-### What version of git-annex are you using? On what operating system?
-4.20130516-g8a26544 for OSX Mountain Lion
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/debug.log
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; the OSX gpg was broken for a while, now fixed. --[[Joey]]
diff --git a/doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error/comment_1_f55cfc133be72ac10cae93c877c487df._comment b/doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error/comment_1_f55cfc133be72ac10cae93c877c487df._comment
deleted file mode 100644
index 7daf6b734..000000000
--- a/doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error/comment_1_f55cfc133be72ac10cae93c877c487df._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-19T21:09:54Z"
- content="""
-I'm seeing some indications (this bug and also the [[git_annex_fork_bombs_on_gpg_file]] bug) that gpg is somehow broken on OSX.
-
-Aha. I just tried on my build box, and:
-
-<pre>
-oberon:~ joeyh$ gpg
-dyld: warning, LC_RPATH @loader_path/../lib in /usr/local/bin/gpg being ignored in restricted program because of @loader_path
-dyld: Library not loaded: @rpath/libz.1.2.7.dylib
-  Referenced from: /usr/local/bin/gpg
-  Reason: image not found
-</pre>
-
-So, I'm packing up a broken gpg. Need to fix that then..
-
-"""]]
diff --git a/doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error/comment_2_24dd024ac4b21a82a781343b8fe3891e._comment b/doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error/comment_2_24dd024ac4b21a82a781343b8fe3891e._comment
deleted file mode 100644
index b1a4114a2..000000000
--- a/doc/bugs/adding_an_rsync.net_repo_give_an_gpg_error/comment_2_24dd024ac4b21a82a781343b8fe3891e._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnmvJtM53ZX9h8OGQoU2t2OfGwrF7rxFX0"
- nickname="Shawn"
- subject="fixed"
- date="2013-05-22T14:37:05Z"
- content="""
-seems to be fix with  4.20130521-g25dba9d.
-
-
-Thanks
-"""]]
diff --git a/doc/bugs/addurl_--relaxed_with_--file_doesn__39__t_actually_relax.mdwn b/doc/bugs/addurl_--relaxed_with_--file_doesn__39__t_actually_relax.mdwn
deleted file mode 100644
index 9118a5041..000000000
--- a/doc/bugs/addurl_--relaxed_with_--file_doesn__39__t_actually_relax.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-It appears like addurl --relaxed if used incombination with --file doesn't actually relax.
-
-(I'm interested in quickly adding links to an extremely large set of files (and for a large set of revisions), and the fact that addurl takes a second or so per file makes this impossible performance-wise.)
-
-What steps will reproduce the problem? (Well, this isn't the problem per see, but it illustrates that it does checking)
-
-    $ echo foo > foo
-    $ git annex add foo
-    $ git annex addurl --relaxed http://lambda.haskell.org/platform/download/2012.4.0.0/haskell-platform-2012.4.0.0.tar.gz --file foo
-    addurl foo 
-      failed to verify url: http://lambda.haskell.org/platform/download/2012.4.0.0/haskell-platform-2012.4.0.0.tar.gz
-    failed
-    git-annex: addurl: 1 failed
-
-What version of git-annex are you using? On what operating system?
-
-Debian Sid
-
-    git-annex version: 4.20130228
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-
-> Missed the case of adding an url to an existing file. [[done]] --[[Joey]] 
diff --git a/doc/bugs/addurl_fails_on_the_internet_archive.mdwn b/doc/bugs/addurl_fails_on_the_internet_archive.mdwn
deleted file mode 100644
index 556575db6..000000000
--- a/doc/bugs/addurl_fails_on_the_internet_archive.mdwn
+++ /dev/null
@@ -1,65 +0,0 @@
-### Please describe the problem.
-
-`addurl` doesn't support the internet archive:
-
-1. it doesn't actually accept the proper URL as a secondary source of content
-2. it doesn't parse the HTML from the video page (the "details page")
-
-### What steps will reproduce the problem?
-
-    # download eben moglen's excellent re:publica presentation from youtube
-    git annex addurl https://www.youtube.com/watch?v=sKOk4Y4inVY
-    # copy that file aside
-    cp -L re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm-bak
-    # drop it so we can try again
-    git annex drop re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
-    # add the IA URL for the same video, failing
-    git annex addurl --file=re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
-    # try again with --relaxed to skip some checks
-    git annex addurl --relaxed --file=re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
-    # observe both files are the same size and checksum
-
-The files should look like this:
-
-[[!format txt """
-anarcat@angela:presentations$ ls -alL re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm*
--r--r--r-- 1 anarcat anarcat 419359123 oct  9 23:41 re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
--r--r--r-- 1 anarcat anarcat 419359123 oct 11 19:40 re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm-bak
-anarcat@angela:presentations$ md5sum re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm*
-7892df24a9e1c40e2587be1035728ef0  re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
-7892df24a9e1c40e2587be1035728ef0  re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm-bak
-"""]]
-
-There are two separate bugs here: one is the above need to use --relaxed even though the file is the same.
-
-The second is probably simply that quvi doesn't support the internet archive, and maybe that one should be moved to a separate [[todo]]/[[wishlist]]. I was expecting this to "do the right thing" (ie. download the video):
-
-    git annex addurl http://archive.org/details/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia
-
-... but instead it downloads the HTML.
-### What version of git-annex are you using? On what operating system?
-
-my good old faithful `4.20130921-g434dc22` i compiled manually some time ago. :)
-
-This is [[done]] in git-annex version: 4.20131011-g2c0badc. Thanks!
-
-### Please provide any additional information below.
-
-[[!format sh """
-anarcat@marcos:presentations$ git annex addurl --file=re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm http://archive.org/download/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
-addurl re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
-  failed to verify url exists: http://archive.org/download/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
-failed
-git-annex: addurl: 1 failed
-anarcat@marcos:presentations$ git annex addurl --debug --file=re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
-[2013-10-09 18:26:30 EDT] call: quvi ["-v","mute","--support","http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm"]
-addurl re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm [2013-10-09 18:26:30 EDT] read: curl ["-s","--head","-L","http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm","-w","%{http_code}"]
-
-  failed to verify url exists: http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm
-failed
-git-annex: addurl: 1 failed
-"""]]
-
-Originally reported in [[tips/Internet_Archive_via_S3]]. --[[anarcat]]
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/addurl_fails_on_the_internet_archive/comment_1_e227aa25eea0b41f1176037a601c5844._comment b/doc/bugs/addurl_fails_on_the_internet_archive/comment_1_e227aa25eea0b41f1176037a601c5844._comment
deleted file mode 100644
index 4754b8366..000000000
--- a/doc/bugs/addurl_fails_on_the_internet_archive/comment_1_e227aa25eea0b41f1176037a601c5844._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.22"
- subject="comment 1"
- date="2013-10-11T18:49:25Z"
- content="""
-Afaik this was fixed in 747f5b123cb3c6b3b87d4e79f8767e69d842b96b.
-
-Probably noone has bothered to add IA support to quvi, but it should be doable.
-"""]]
diff --git a/doc/bugs/addurl_fails_on_the_internet_archive/comment_2_6d4fd58f0caa1f75ee2dd3f0a909cd91._comment b/doc/bugs/addurl_fails_on_the_internet_archive/comment_2_6d4fd58f0caa1f75ee2dd3f0a909cd91._comment
deleted file mode 100644
index f24d0583f..000000000
--- a/doc/bugs/addurl_fails_on_the_internet_archive/comment_2_6d4fd58f0caa1f75ee2dd3f0a909cd91._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://id.koumbit.net/anarcat"
- ip="72.0.72.144"
- subject="awesome, fix confirmed, and IA+quvi forwarded upstream"
- date="2013-10-12T11:23:31Z"
- content="""
-Great! I confirm latest versions work properly.. I have [written the quvi-devel mailing list](http://sourceforge.net/mailarchive/forum.php?thread_name=20131012104904.GA11972%40angela.anarcat.ath.cx&forum_name=quvi-devel) to ask for help for archive.org support, we'll see where it goes...
-"""]]
diff --git a/doc/bugs/addurl_file_doesn__39__t_work_with_spaces_in_filenames_and_--fast.mdwn b/doc/bugs/addurl_file_doesn__39__t_work_with_spaces_in_filenames_and_--fast.mdwn
deleted file mode 100644
index 40a310df4..000000000
--- a/doc/bugs/addurl_file_doesn__39__t_work_with_spaces_in_filenames_and_--fast.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-###What steps will reproduce the problem?
-    $ git annex addurl 'file:///$HOME/space file' --fast
-    addurl _$HOME_space%20file 
-      unable to access url: file:///$HOME/space file
-    failed
-    git-annex: addurl: 1 failed
-
-    $ git annex addurl 'file:///home/arand/space\ file' --fast
-    addurl _home_arand_space%5C%20file 
-      unable to access url: file:///home/arand/space\ file
-    failed
-    git-annex: addurl: 1 failed
-
-###What is the expected output? What do you see instead?
-
-I guess it's semi-expected to fail since spaces aren't supposed to be in urls, but with file:// it would be nice if that restriction was lessened.
-
-###What version of git-annex are you using? On what operating system?
-
-Debian sid/experimental
-
-    git-annex version: 4.20130227
-    local repository version: 4
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-> Relaxed url parsing so this will work, and also in http:// urls etc.
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/addurl_file_doesn__39__t_work_with_spaces_in_filenames_and_--fast/comment_1_eea9477ea1157cb88c8a07d8da5f0dba._comment b/doc/bugs/addurl_file_doesn__39__t_work_with_spaces_in_filenames_and_--fast/comment_1_eea9477ea1157cb88c8a07d8da5f0dba._comment
deleted file mode 100644
index 6e970322c..000000000
--- a/doc/bugs/addurl_file_doesn__39__t_work_with_spaces_in_filenames_and_--fast/comment_1_eea9477ea1157cb88c8a07d8da5f0dba._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~arand"
- nickname="arand"
- subject="comment 1"
- date="2013-03-10T21:56:04Z"
- content="""
-This seems to only occur with the \"--fast\" option.
-
-And the first example above is obviously failing due to '$HOME' as well
-"""]]
diff --git a/doc/bugs/allows_repository_with_the_same_name_twice.mdwn b/doc/bugs/allows_repository_with_the_same_name_twice.mdwn
deleted file mode 100644
index e32bfda61..000000000
--- a/doc/bugs/allows_repository_with_the_same_name_twice.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-What steps will reproduce the problem?
-
-Unsure. I believe:
-
-* Add a git remote
-* Mark it as dead
-* Remove the git remote, re-add with the same name
-
-What is the expected output? What do you see instead?
-
-When I do a `git annex status` I see:
-
- 	04e701b5-8a22-4391-ad74-d75dde715c7b -- bigserver
- 	6ddfda5d-0f17-45a9-b41a-2a626a823101 -- bigserver
-
-What version of git-annex are you using? On what operating system?
-
-4.20130323 on OSX and Linux
-
-Please provide any additional information below.
-
-Trying to get a file from bigserver kept on failing with the message "Try making some of these repositories available". Which led me on a wild goose chases blaming SSH keys and PATH issues.
-
-> [[done]]; not a bug --[[Joey]]
diff --git a/doc/bugs/allows_repository_with_the_same_name_twice/comment_1_ba7801403e7138684704a3471c8bc4a6._comment b/doc/bugs/allows_repository_with_the_same_name_twice/comment_1_ba7801403e7138684704a3471c8bc4a6._comment
deleted file mode 100644
index d307d4af6..000000000
--- a/doc/bugs/allows_repository_with_the_same_name_twice/comment_1_ba7801403e7138684704a3471c8bc4a6._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-04T16:10:38Z"
- content="""
-The \"bigserver\" shown there is not a repository name, it's a repository description. You can change it with `git annex describe 6ddfda5d-0f17-45a9-b41a-2a626a823101 otherbigserver`
-
-git-annex does not use these descriptions in any way, except for to show them to you. It also shows the UUID, so that if you have described two repositories the same way, you can still tell them apart.
-
-I don't see a bug here, unless you can be more specific about a problem.
-"""]]
diff --git a/doc/bugs/allows_repository_with_the_same_name_twice/comment_2_8c19a4ddedbe7ddb8bdcf84acac68cc8._comment b/doc/bugs/allows_repository_with_the_same_name_twice/comment_2_8c19a4ddedbe7ddb8bdcf84acac68cc8._comment
deleted file mode 100644
index 4d6905865..000000000
--- a/doc/bugs/allows_repository_with_the_same_name_twice/comment_2_8c19a4ddedbe7ddb8bdcf84acac68cc8._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://danieroux.com/"
- nickname="danie"
- subject="Having difficulty recreating it"
- date="2013-04-04T17:53:56Z"
- content="""
-I got into a situation where:
-
-git annex get myfile.txt
-
-Would complain that I have to \"make bigserver available\" - even though it had a remote called that already.
-
-Will pay closer attention if I get into that corner next time.
-"""]]
diff --git a/doc/bugs/amd64_i386_standalone:_no_SKEIN.mdwn b/doc/bugs/amd64_i386_standalone:_no_SKEIN.mdwn
deleted file mode 100644
index 628cb13bd..000000000
--- a/doc/bugs/amd64_i386_standalone:_no_SKEIN.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-### Please describe the problem.
-
-git-annex standalone has no SKEIN backends on i386 and amd64. OSX and Android standalones have them, debian package had it in version 4.20131106 and probably still does.
-
-### What steps will reproduce the problem?
-
-1. download git-annex standalone for amd64 or i386
-2. extract
-3. git-annex.linux/git-annex version
-
-Expect key/value backends row to mention SKEIN. It does on other platforms, but not here.
-
-Trying to e.g. get SKEIN-hashed files produces error messages.
-
-### What version of git-annex are you using? On what operating system?
-amd64 and i386 standalones 5.20140103 on Ubuntu Precise/12.04 (Mint 13)
-
-### Please provide any additional information below.
-
-[[!format sh """
-clacke@acozed:~$ /usr/bin/git-annex version
-git-annex version: 4.20131106
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-clacke@acozed:~$ ~/.local/libexec/git-annex.linux-5.20140103/git-annex version
-git-annex version: 5.20131230-g4aa88d8
-build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook external
-clacke@acozed:~$ ~/.local/libexec/git-annex.linux-5.20140103_i386/git-annex version
-git-annex version: 5.20131230-g52a46585
-build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook external
-"""]]
-
--- [[clacke]]
-
-> [[done]] The autobuilds are now running debian unstable, and SKEIN is included
-> now. --[[Joey]] 
diff --git a/doc/bugs/amd64_i386_standalone:_no_SKEIN/comment_1_fcf7e1089b25993378df7574ccee8062._comment b/doc/bugs/amd64_i386_standalone:_no_SKEIN/comment_1_fcf7e1089b25993378df7574ccee8062._comment
deleted file mode 100644
index c725acd62..000000000
--- a/doc/bugs/amd64_i386_standalone:_no_SKEIN/comment_1_fcf7e1089b25993378df7574ccee8062._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.43"
- subject="comment 1"
- date="2014-01-08T22:06:35Z"
- content="""
-Those builds are done on Debian stable for portability reasons, and it has too old a version of haskell-cryptohash for SKEIN.
-"""]]
diff --git a/doc/bugs/amd64_standalone:_ld-linux-x86-64.so.2:_not_found.mdwn b/doc/bugs/amd64_standalone:_ld-linux-x86-64.so.2:_not_found.mdwn
deleted file mode 100644
index 9f6f1e53d..000000000
--- a/doc/bugs/amd64_standalone:_ld-linux-x86-64.so.2:_not_found.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-### Please describe the problem.
-While trying to diagnose [[bugs/armel_standalone:_git-upload-pack_and_-receive-pack_not_shimmed/]] I updated the version of the standalone git-annex on Server A from 3.20121017 to the latest not daily build.
-
-### What steps will reproduce the problem?
-1. download git-annex standalone for amd64 (I did both the normal not-daily build, and the daily build, same thing in both)
-2. extract
-3. ./runshell
-
-### What version of git-annex are you using? On what operating system?
-Debian amd64 (yes... I know, blame asheesh)
-
-### Please provide any additional information below.
-
-[[!format sh """
-greg@rose:~/bin/git-annex.linux$ ./runshell 
-exec: 2: /home/greg/bin/git-annex.linux/lib64/ld-linux-x86-64.so.2: not found
-"""]]
-
-
-### Indeed a dupe ###
-Thanks clacke, [[done]] - Greg
diff --git a/doc/bugs/amd64_standalone:_ld-linux-x86-64.so.2:_not_found/comment_1_5e40f32caf9c1177a5f7b9883cdcc6dd._comment b/doc/bugs/amd64_standalone:_ld-linux-x86-64.so.2:_not_found/comment_1_5e40f32caf9c1177a5f7b9883cdcc6dd._comment
deleted file mode 100644
index 00b1f46e4..000000000
--- a/doc/bugs/amd64_standalone:_ld-linux-x86-64.so.2:_not_found/comment_1_5e40f32caf9c1177a5f7b9883cdcc6dd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://id.clacke.se/"
- nickname="clacke"
- subject="dup"
- date="2013-12-23T12:50:04Z"
- content="""
-Seems to be a duplicate of [[Latest_64_bit_standalone_Linux_build_broken]].
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit.mdwn b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit.mdwn
deleted file mode 100644
index e739b9691..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-
-I installed git-annex on my android device (Nook HD+, with Cyanogenmod 10.1 installed) for the first time today and was excited to get it working.  However, I noticed the device warming alarmingly, and, after installing a CPU usage monitor, it became clear that git annex was the problem, as it was hovering around 30-40% even when idle.
-
-I tried quitting git-annex using the webapp's "Shutdown Daemon" menu option, and it seemed to shut down successfully, but the CPU monitor still showed that process present and taking up high amounts of CPU (sometimes well over 50%).  I used the android app switcher and noticed that the terminal emulator for git annex was still running; I tried to quit this by using the X button and it seemed to close, but the CPU monitor still showed the git-annex process consuming large amounts of CPU.  Finally I had to quit the process forcefully from the monitor.
-
-### What steps will reproduce the problem?
-
-Install & run; observe CPU.  I used a dedicated CPU monitor to stop it the first time; another time, I tried stopping it by going to Preferences, Apps, Running Applications, where it told me it had one process and one service running.  I stopped the service without issue; it said the process could not be safely stopped but I stopped it anyway and that successfully stopped the app.
-
-
-### What version of git-annex are you using? On what operating system?
-
-the current (4.20130826-g46f422) version on Android.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-(I'm not sure how to get a log out of the web app to paste here unfortunately.
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; I fixed the bug which turned out to be a stupid
-> minunderstanding of how a java library worked. --[[Joey]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_1d841ff0b0ffd814efed2449dc1f35f3._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_1d841ff0b0ffd814efed2449dc1f35f3._comment
deleted file mode 100644
index 892894ad4..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_1d841ff0b0ffd814efed2449dc1f35f3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 10"
- date="2013-08-27T01:46:36Z"
- content="""
-This seems to be a reversion instroduced in commit a48d340abdaf3296a2ddacd73c18adc9a13a02ef. With that backed out, I get 0% cpu usage for the terminal app. Even if I run top in the terminal, its CPU sits under 1%.
-
-Clearly the infinite loop in that patch is running faster than expected!
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_cd101e0af45d8f463011fb0d04b3b822._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_cd101e0af45d8f463011fb0d04b3b822._comment
deleted file mode 100644
index d8ca9fb05..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_cd101e0af45d8f463011fb0d04b3b822._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 10"
- date="2013-08-26T20:19:06Z"
- content="""
-Yeah, that would definitely explain both what I'm seeing and why you haven't been seeing it.
-
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_11_8595041cfe703d9bea49e792732dc15f._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_11_8595041cfe703d9bea49e792732dc15f._comment
deleted file mode 100644
index 085f3d108..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_11_8595041cfe703d9bea49e792732dc15f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 11"
- date="2013-08-27T02:27:08Z"
- content="""
-Awesome!  I'll grab a new nightly in a day or two and give it another shot.
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_1_8e7bc6965ea967a8d43240791a30c5bc._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_1_8e7bc6965ea967a8d43240791a30c5bc._comment
deleted file mode 100644
index 756b9d5c6..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_1_8e7bc6965ea967a8d43240791a30c5bc._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 1"
- date="2013-08-26T18:34:44Z"
- content="""
-Just noticed I was using the autobuild instead of the last release version; I'll try the release version and see if that makes any difference.
-
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_2_891c1073f908b204651899d41599f944._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_2_891c1073f908b204651899d41599f944._comment
deleted file mode 100644
index c26c512ea..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_2_891c1073f908b204651899d41599f944._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 2"
- date="2013-08-26T18:42:02Z"
- content="""
-If you shut down the daemon, it seems to me that the process that was still running would probably be `git annex transferkey` which runs in its own process to upload/download file contents. I normally see 0% to 1% cpu use from git-annex when it is running on my android tablet. It's possible that the 1% use is due to it waking up every second, which got fixed in 9dc2373977d583b4c4aa6cf0555dc97309f89991.
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_3_de02b8f1b5928fa1a7078c4aa2124bea._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_3_de02b8f1b5928fa1a7078c4aa2124bea._comment
deleted file mode 100644
index 71ad88d74..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_3_de02b8f1b5928fa1a7078c4aa2124bea._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 3"
- date="2013-08-26T19:03:45Z"
- content="""
-OK, so I might have a rogue transferkey process going on, but one which starts over again when I restart the app?
-
-I've set this all up purely as a \"can I do this\" experiment right now; there is literally zero important data there to lose, either on the tablet or on the laptop, so maybe I could just write this off as a bad result of my first few shaky attempts to get the device paired with my laptop, wipe out both annexes, and start completely from scratch.
-
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_6_506acc4275a81ed9e9b08e8a40fcf96a._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_6_506acc4275a81ed9e9b08e8a40fcf96a._comment
deleted file mode 100644
index 553a135a0..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_6_506acc4275a81ed9e9b08e8a40fcf96a._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 6"
- date="2013-08-26T19:38:12Z"
- content="""
-a final note -- according to the process monitor, the process eating CPU is \"ga.androidterm\".  There are also a small swarm of about 6 git processes none of which are consuming much CPU time at all.
-
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_7_d38d6f40db4c9437764c7b2ddf36b5a9._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_7_d38d6f40db4c9437764c7b2ddf36b5a9._comment
deleted file mode 100644
index 819d31672..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_7_d38d6f40db4c9437764c7b2ddf36b5a9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 7"
- date="2013-08-26T20:00:39Z"
- content="""
-It's certainly possible that the terminal app eats cpu for some reason even when sitting idle. It's hard for me to tell since I've been measuring cpu use by running top inside that terminal, which necessarily seems to use a lot of the CPU just to draw the screen.
-
-If it's the terminal at fault, it would continue after you shutdown the git-annex daemon, since that doesn't close the terminal.
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_8_9bb23e9cbc77ecca4b1209b0f66bc2b0._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_8_9bb23e9cbc77ecca4b1209b0f66bc2b0._comment
deleted file mode 100644
index 3fce2f21f..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_8_9bb23e9cbc77ecca4b1209b0f66bc2b0._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="oh yeah, i can run top in adb.."
- date="2013-08-26T20:14:13Z"
- content="""
-So, I can tell that on my tablet, the terminal app is using 82% cpu while idle.
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_d1ce7fc251db076da61eed5bb9d71b9a._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_d1ce7fc251db076da61eed5bb9d71b9a._comment
deleted file mode 100644
index ffd0a44be..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_d1ce7fc251db076da61eed5bb9d71b9a._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 9"
- date="2013-08-26T20:49:34Z"
- content="""
-(removed my earlier comments with debug info, since it wasn't relevant and I'd just as soon not display my gmail id and home machine's address on the web if I don't need to)
-
-"""]]
diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_feb71c1022ff65d82e66a3958a41dfb2._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_feb71c1022ff65d82e66a3958a41dfb2._comment
deleted file mode 100644
index 8f32df035..000000000
--- a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_feb71c1022ff65d82e66a3958a41dfb2._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 9"
- date="2013-08-26T20:16:05Z"
- content="""
-Strace doesn't show it doing anything. I suppose I should try building the terminal without the several patches I added to it to support git-annex to see if I somehow made it use all this cpu..
-"""]]
diff --git a/doc/bugs/android_cannot_get_from_5.20131221.mdwn b/doc/bugs/android_cannot_get_from_5.20131221.mdwn
deleted file mode 100644
index c2422d853..000000000
--- a/doc/bugs/android_cannot_get_from_5.20131221.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-## Reproduce
-
- - run `git annex get --from mylinuxbox` on git-annex Android 5.20131213 or 5.20131221
- - `mylinuxbox` is running 5.20131221 standalone
-
-## Expected result
-
-The Android box gets the missing file.
-
-## Actual result
-
-    git-annex: unknown command sendkey
-
-## Workaround
-
-Run 5.20131213 on `mylinuxbox`, which does not have this problem.
-
-## Additional
-
-linux standalone 5.20131213 and 5.20131221 are both able to `get` from linux standalone 5.20131221 -- this only affects the Android version.
-
-*Edit:* On second thought, Android is not the only distinguishing factor. Apart from being Android, the box and repo having trouble have the following distinguishing factors from the ones I tried that worked:
-
- - Android
- - Direct mode
- - Remote was set up by the Assistant
-
-> [[clacke]]
-
-> There was a bug in the linux standalone tarball distributed
-> with 5.20131221 that made the `git-annex-shell` wrapper accidentially run
-> `git-annex` instead of `git-annex-shell`. Which results in 
-> this error about recvkey, which is a git-annex-shell command, not a
-> git-annex command.
-> 
-> So, the problem is not in the android build, but in the git-annex
-> installed on the server (or laptop or whatever) that the android is
-> trying to access. 
-
-> This bug is fixed in the daily builds, and I have updated the
-> tarballs for the release too, now. [[done]] --[[Joey]]
diff --git a/doc/bugs/android_cannot_get_from_5.20131221/comment_1_f8eeb67e58bf2a4658dcc32a9f275f19._comment b/doc/bugs/android_cannot_get_from_5.20131221/comment_1_f8eeb67e58bf2a4658dcc32a9f275f19._comment
deleted file mode 100644
index 48f02c785..000000000
--- a/doc/bugs/android_cannot_get_from_5.20131221/comment_1_f8eeb67e58bf2a4658dcc32a9f275f19._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U"
- nickname="Carlo"
- subject="comment 1"
- date="2013-12-22T17:57:24Z"
- content="""
-Same problem on copy --to, but says \"unknown command recvkey\". sender is linux x64, receiver is raspberry pi.
-"""]]
diff --git a/doc/bugs/android_cannot_get_from_5.20131221/comment_2_eba841b1978c70a4c20a8d96c9f71172._comment b/doc/bugs/android_cannot_get_from_5.20131221/comment_2_eba841b1978c70a4c20a8d96c9f71172._comment
deleted file mode 100644
index 73ba6a3ae..000000000
--- a/doc/bugs/android_cannot_get_from_5.20131221/comment_2_eba841b1978c70a4c20a8d96c9f71172._comment
+++ /dev/null
@@ -1,36 +0,0 @@
-[[!comment format=mdwn
- username="etset"
- ip="188.83.117.67"
- subject="comment 2"
- date="2013-12-23T13:35:18Z"
- content="""
-Same problem here: When I try `git annex get $somefile --debug --from $remote` in my laptop with 5.20131221, with the remote being a ssh remote on a server running 5.20131222-g487b01c, the output shows:
-
-    [2013-12-23 13:03:17 WET] read: git [\"--git-dir=/home/etset/annex/.git\",\"--work-tree=/home/etset/annex\",\"ls-   files\",\"--cached\",\"-z\",\"--\",\"running.gnumeric\"]
-    get running.gnumeric [2013-12-23 13:03:17 WET] read: git [\"--git-dir=/home/etset/annex/.git\",\"--work-tree=/home/etset/annex\",\"show-ref\",\"git-annex\"]
-    [2013-12-23 13:03:17 WET] read: git [\"--git-dir=/home/etset/annex/.git\",\"--work-tree=/home/etset/annex\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-12-23 13:03:17 WET] read: git [\"--git-dir=/home/etset/annex/.git\",\"--work-tree=/home/etset/annex\",\"log\",\"refs/heads/git-annex..32bf5294e7fda349e689b40f3e6627d58067a455\",\"--oneline\",\"-n1\"]
-    [2013-12-23 13:03:17 WET] read: git [\"--git-dir=/home/etset/annex/.git\",\"--work-tree=/home/etset/annex\",\"log\",\"refs/heads/git-annex..338e69ac06c3602f8e3a01390dad3be039203935\",\"--oneline\",\"-n1\"]
-    [2013-12-23 13:03:17 WET] read: git [\"--git-dir=/home/etset/annex/.git\",\"--work-tree=/home/etset/annex\",\"log\",\"refs/heads/git-annex..1682681264cd47e1721203485f8f43b09bdf9e61\",\"--oneline\",\"-n1\"]
-    [2013-12-23 13:03:17 WET] chat: git [\"--git-dir=/home/etset/annex/.git\",\"--work-tree=/home/etset/annex\",\"cat-file\",\"--batch\"]
-    (from server...) 
-    [2013-12-23 13:03:17 WET] read: rsync [\"--progress\",\"--inplace\",\"-e\",\"'ssh' '-S' '.git/annex/ssh/47d5752367356bb61361fd5cf9c1ec32' '-o' 'ControlMaster=auto' '-o' 'ControlPersist=yes' '-T' 'etset@server.lan' 'git-annex-shell ''sendkey'' ''/mnt/disk/annex/'' ''SHA256E-s17623--c547d78c210676ba17f418ffa1171094900bb863298c01eb497af8f75f64353f'' --uuid ff21315c-8faa-430c-ae7e-c7bbb468071b ''--'' ''remoteuuid=21141b76-9875-45c2-b5ea-a165ad983a85'' ''direct=1'' ''associatedfile=running.gnumeric'' ''--'''\",\"--\",\"dummy:\",\"/home/etset/annex/.git/annex/tmp/SHA256E-s17623--c547d78c210676ba17f418ffa1171094900bb863298c01eb497af8f75f64353f\"]
-    git-annex: unknown command sendkey
-
-    Usage: git-annex command [option ...]
-
-    [ ...long list of possible commands here... ]
-
-    rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
-    rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.0]
-
-      rsync failed -- run git annex again to resume file transfer
-
-      Unable to access these remotes: server
-
-      Try making some of these repositories available:
-      	ff21315c-8faa-430c-ae7e-c7bbb468071b -- server (etset@server.lan:/mnt/disk/annex)
-       	ff4f4c32-ad94-45f4-8b3f-f7d843d7c496 -- u0_a178@localhost:/sdcard/annex
-    failed
-    git-annex: get: 1 failed
-"""]]
diff --git a/doc/bugs/android_cannot_get_from_5.20131221/comment_3_4ba8208822c7f66e23037564b3501391._comment b/doc/bugs/android_cannot_get_from_5.20131221/comment_3_4ba8208822c7f66e23037564b3501391._comment
deleted file mode 100644
index dbb94a50d..000000000
--- a/doc/bugs/android_cannot_get_from_5.20131221/comment_3_4ba8208822c7f66e23037564b3501391._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl99Gxq3NPNvwZHp3PDufaknQH4rZb_KKY"
- nickname="Florian"
- subject="comment 3"
- date="2013-12-26T00:15:56Z"
- content="""
-I can still confirm the bug for the current version (5.20131224-g692aa01). I see this problem on all my machines.
-"""]]
diff --git a/doc/bugs/annex-rsync-options_shell-split_carelessly.mdwn b/doc/bugs/annex-rsync-options_shell-split_carelessly.mdwn
deleted file mode 100644
index f88bd3354..000000000
--- a/doc/bugs/annex-rsync-options_shell-split_carelessly.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-with rsync, it is sometimes the case that one needs to specify ssh options -- typical examples from the rsync man page are `rsync  -e 'ssh -p 2234'`. as git-annex does the shell splitting of the arguments in `annex-rsync-options` (see [[special remotes/rsync]]) itself by looking for whitespace, these options can't be passed directly. (`annex-rsync-options = -e 'ssh -p 2234'` gets split to `["rsync", "-e", "'ssh", "-p", "2234'"]` instead of `["rsync", "-e", "ssh -p 2234"]`).
-
-git-annex should respect shell splitting rules when looking at annex-rsync-options. (i suppose there is a haskell library or module for that; in python, we have the `shlex` module for that).
-
-## workaround
-
-put this in .git/ssh and mark it as executable:
-
-    #!/bin/sh
-    exec ssh -p 2234 $@
-
-put this in your git annex config in the particular remote's section:
-
-    annex-rsync-options = -e /local/path/to/your/repo/.git/ssh
-
-(typical bug report information: observed with git-annex 3.20121127 on debian)
-
-> [[done]]; see my comment --[[Joey]]
diff --git a/doc/bugs/annex-rsync-options_shell-split_carelessly/comment_1_2636e0d224317f2e6db94658d8a094c4._comment b/doc/bugs/annex-rsync-options_shell-split_carelessly/comment_1_2636e0d224317f2e6db94658d8a094c4._comment
deleted file mode 100644
index 42b92ce28..000000000
--- a/doc/bugs/annex-rsync-options_shell-split_carelessly/comment_1_2636e0d224317f2e6db94658d8a094c4._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.117"
- subject="comment 1"
- date="2012-12-13T17:03:08Z"
- content="""
-Due to the way git-annex runs rsync, which involves a specific -e parameter it constructs that, you cannot pass -e in annex-rsync-options anyway; or if you do you'll bypass use of git-annex-shell, which is not desirable. I have not checked which, but would not recommend use of it.
-
-There is no need for ugly workarounds. Just use ~/.ssh/config to configure the hostname to use the nonstandard port it needs. For example:
-
-<pre>
-Host example.com
-Port 2234
-</pre>
-
-Or, to make a separate example.com-2234 host that can be used to use the nonstandard port:
-
-<pre>
-Host example.com-2234
-Hostname example.com
-Port 2234
-</pre>
-"""]]
diff --git a/doc/bugs/annex.numcopies_not_overriden_by_--numcopies_option.mdwn b/doc/bugs/annex.numcopies_not_overriden_by_--numcopies_option.mdwn
deleted file mode 100644
index ba63897ba..000000000
--- a/doc/bugs/annex.numcopies_not_overriden_by_--numcopies_option.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-### Please describe the problem.
-Using "--numcopies=N" on the command line doesn't overrides (as advertised) the annex.numcopies variable when set via .gitattributes. 
-
-### What steps will reproduce the problem?
-
-$ echo '* annex.numcopies=2' > .gitattributes
-
-$ git annex drop --numcopies=1 somefile.txt
-
-Second line fails if only one other copy exists.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20130627
-
-> I don't think this was ever handled correctly.
-> I've fixed it now. [[done]] --[[Joey]] 
diff --git a/doc/bugs/annex_add_in_annex.mdwn b/doc/bugs/annex_add_in_annex.mdwn
deleted file mode 100644
index e12826f00..000000000
--- a/doc/bugs/annex_add_in_annex.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-I accidentally annexed some files in the .git-annex directory and it cause git-annex/git to be very unhappy when i pulled the repo to somewhere else. It might be worth teaching git-annex to disallow annex'ing of files inside the .git-annex/.git directories.
-
-> There is a guard against `git annex add .git-annex/foo`, but it doesn't
-> notice `cd .git-annex; git annex add foo`. --[[Joey]]
-
-> Now fixed, by removing the .git-annex directory. [[done]] --[[Joey]] 
diff --git a/doc/bugs/annex_get_fails:___34__No_such_file_or_directory__34__.mdwn b/doc/bugs/annex_get_fails:___34__No_such_file_or_directory__34__.mdwn
deleted file mode 100644
index 33ac259d9..000000000
--- a/doc/bugs/annex_get_fails:___34__No_such_file_or_directory__34__.mdwn
+++ /dev/null
@@ -1,68 +0,0 @@
-**What steps will reproduce the problem?**
-
-I did a basic git annex setup with two repositories talking to each other.  They are on the same macine, but I identified them via the hostname, because I intend to set up my production systems on two machines.  Since I am new to annex, I'll reproduce the full sequence of commands to create the repos and sync them.  *I* noticed the trouble at the last step, when `git annex get` failed.
-
-Here is the full sequence of commands:
-
-    >>> cd /scr/wandschn/hackNtest/distributed/nyc/STU_files
-    >>> git init
-    >>> git annex init nyc
-    >>> cd /scr/wandschn/hackNtest/distributed/pdx
-
-    >>> git clone xerxes:/scr/wandschn/hackNtest/distributed/nyc/STU_files
-    >>> git annex init pdx
-    >>> git remote add nyc xerxes:/scr/wandschn/hackNtest/distributed/nyc/STU_files
-
-    >>> cd /scr/wandschn/hackNtest/distributed/nyc/STU_files
-    >>> git remote add pdx xerxes:/scr/wandschn/hackNtest/distributed/pdx/STU_files
-
-    >>> mkdir shared
-    >>> cp ../../../files/shared/* shared/.
-    >>> git annex add shared
-    >>> git commit -a -m "initial add of shared files"
-
-    >>> cd /scr/wandschn/hackNtest/distributed/pdx/STU_files
-    >>> git fetch nyc
-    >>> git merge nyc/master
-    >>> ls shared/135.mae
-    shared/135.mae
-    >>> git annex whereis shared/135.mae
-    whereis shared/135.mae (1 copy)
-            6f0368db-f1b1-4192-9200-3575c16c2ef1 -- origin (nyc)
-    ok
-    >>> git annex get shared/135.mae
-    fatal: Could not switch to '../.git/annex/objects/KV/5f/SHA256-s1499628--4a7e2ba13096ee2d1a6b3c3b314efae623516d200c09d35ff0f695395b6ad47a': No such file or directory
-
-    git-annex: <file descriptor: 4>: hGetLine: end of file
-    failed
-    git-annex: get: 1 failed
-
-**What is the expected output? What do you see instead?**
-
-I expected the file shared/135.mae to be copied from the remote repo to the local repo.  Instead, this command failed, and said that there was a missing file.  This file path is the one that the broken link points to, and it exists on the remote repo.
-
-**What version of git-annex are you using? On what operating system?**
-
-git version 1.7.9.6
-
-git-annex 3.20120523
-
-CentOS 6.3 (kernel 2.6.32)
-
-64bit Xeon processor
-
-
-**Please provide any additional information below.**
-
-> Thanks for the command sequence, which I have tested here is ok with
-> a current version of git-annex (except for one cd you left out..).
-> 
-> You version of git-annex is quite old, and this
-> particular bug was fixed in version 3.20120721.
-> 
-> The bug is that it fails to correctly determine the git version at
-> compile time, and I think it thinks you have an old version of git
-> from before 1.7.7, which changed some behavior of `git check-attr`.
-> 
-> Upgrading git-annex should fix this, please let me know if not. [[done]]
-> --[[Joey]] 
diff --git a/doc/bugs/annex_get_fails:___34__No_such_file_or_directory__34__/comment_1_e44ae9c19796efc8eda5432d3bf1e5a3._comment b/doc/bugs/annex_get_fails:___34__No_such_file_or_directory__34__/comment_1_e44ae9c19796efc8eda5432d3bf1e5a3._comment
deleted file mode 100644
index b2cd64f57..000000000
--- a/doc/bugs/annex_get_fails:___34__No_such_file_or_directory__34__/comment_1_e44ae9c19796efc8eda5432d3bf1e5a3._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmz9DnN5ESPLLRN0Q5a6fpELMFTYSkWTFs"
- nickname="Steve"
- subject="Stock RHEL git-annex is old & buggy"
- date="2014-04-23T17:35:29Z"
- content="""
-The stock git-annex bundled with Red Hat Enterprise Linux server (release 6.5) contains the old, buggy version that throws the \"No such file or directory\" error described above. The RHEL 6.5 version is:
-
-    $ git annex version
-    git-annex version: 3.20120523
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3
-    upgrade supported from repository versions: 0 1 2
-
-Installing a more recent version (such as 5.20140411-gda795e0) solves the problem.
-
-"""]]
diff --git a/doc/bugs/annex_get_over_SSH_is_very_slow.mdwn b/doc/bugs/annex_get_over_SSH_is_very_slow.mdwn
deleted file mode 100644
index 215e725e9..000000000
--- a/doc/bugs/annex_get_over_SSH_is_very_slow.mdwn
+++ /dev/null
@@ -1,33 +0,0 @@
-### Please describe the problem.
-Attempting to populate one annex from another over an SSH connection is very slow.
-
-### What steps will reproduce the problem?
-1. Create an annex on Linux
-2. Clone annex to Windows system
-3. Set up sshd on Linux system, access keys, etc.
-4. "git annex get ."
-5. Checking if an individual file exists takes a few seconds, and downloading it takes a few seconds. on a 100Mbps LAN, transfers at an average of 7Mbps.
-6. By comparison operating over a working HTTP connection transfers between 20~40 Mbps.
-
-
-### What version of git-annex are you using? On what operating system?
-Windows 7: 4.20140627-g8a36ec5 (from the git-annex download page)
-
-Debian Linux: 3.20120629 (from the package manager)
-
-> The problem is that git-annex is designed to be used with ssh connection
-> caching. However, I have not gotten ssh connection caching to work on 
-> Windows. I did try getting this to work with IIRC, cygwin's ssh, but
-> it seems that the Unix sockets it expects to use with `-o ControlMaster`
-> don't work, or it's not been ported to use the Windows equivilant.
->
-> It's not practical to make git-annex reuse a single ssh connection
-> itself, due to the way rsync is run over ssh.
-> 
-> Since this is basically a bug in ssh for Windows, and not in git-annex
-> per se, I am going to close this bug report. However, I do mention
-> this in [[todo/windows_support]].
-> 
-> [[done]] --[[Joey]]
-
-[[!meta title="No ssh connection caching support on Windows"]]
diff --git a/doc/bugs/annex_seems_to_ignore_core.bare_setting.mdwn b/doc/bugs/annex_seems_to_ignore_core.bare_setting.mdwn
deleted file mode 100644
index d5f31ca14..000000000
--- a/doc/bugs/annex_seems_to_ignore_core.bare_setting.mdwn
+++ /dev/null
@@ -1,45 +0,0 @@
-### Please describe the problem.
-I have a transfer repository on a thumbdrive with a FAT file system mounted. It has been working very well for almost a year.
-However, the current annex version overrides the core.bare setting with 'false' and tries to checkout the work tree on my thumbdrive (e.g. on a 'git annex status').
-
-### What version of git-annex are you using? On what operating system?
-
-Broken git-annex versions:
-
- * 5.20131130-gc25be33
- * 5.20131118-gc7e5cde
-
-Working version:
-
- * 4.20131101-gf59a6d1
-
-OS is Linux.
-
-### Please provide any additional information below.
-
-[[!format sh """
-$> git config --list
-core.repositoryformatversion=0
-core.filemode=false
-core.bare=true
-core.symlinks=false
-core.ignorecase=true
-annex.uuid=3fb63b01-40cf-4613-b171-d6cba04028af
-annex.version=4
-annex.crippledfilesystem=true
-annex.direct=true
-"""]]
-
-[[!format sh """
-$> git annex status -d
-[2013-12-05 15:01:30 CET] read: git ["--git-dir=/media/transfer/annex-media.git","--work-tree=/media/transfer","-c","core.bare=false","symbolic-ref","HEAD"]
-[2013-12-05 15:01:30 CET] read: git ["--git-dir=/media/transfer/annex-media.git","--work-tree=/media/transfer","-c","core.bare=false","show-ref","--hash","refs/heads/master"]
-[2013-12-05 15:01:30 CET] call: git ["--git-dir=/media/transfer/annex-media.git","--work-tree=/media/transfer","-c","core.bare=false","update-ref","refs/heads/annex/direct/master","eb688442ea29660e9bc604434a77821b9c0349ad"]
-[2013-12-05 15:01:30 CET] call: git ["--git-dir=/media/transfer/annex-media.git","--work-tree=/media/transfer","-c","core.bare=false","checkout","-q","-B","annex/direct/master"]
-...
-git-annex: git [Param "checkout",Param "-q",Param "-B",Param "annex/direct/master"] failed
-"""]]
-
-> If I understand the followup comment corretcly, it confirms my hypothesis
-> that this is about the bug that has since been fixed. So, [[done]].
-> --[[Joey]] 
diff --git a/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment b/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment
deleted file mode 100644
index 8ee885b5f..000000000
--- a/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_1_beb674205f06310f6a9060bea35fa3fe._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 1"
- date="2013-12-05T20:14:54Z"
- content="""
-There was a bug in 5.20131118 through 5.20131127 that caused git-annex init, when run in a bare repository, to set core.bare=false. This would also happen
-if you had a bare repository that had not been initted, and ran some otherwise innocuous command like git-annex status in it (since git-annex can auto-init).
-
-The most recent version you say is broken, 5.20131130-gc25be33, is right at the commit where I fixed that bug. But before I taught git-annex to automatically fix up a repository that it had done this to. You can get that fix in the current daily builds, or you can just run `git config core.bare true` to fix the setting, and version 5.20131130-gc25be33 shouldn't screw it up again.
-"""]]
diff --git a/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_2_bc5a4be517409f8da2f36299dc4cbbde._comment b/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_2_bc5a4be517409f8da2f36299dc4cbbde._comment
deleted file mode 100644
index 07aeb141a..000000000
--- a/doc/bugs/annex_seems_to_ignore_core.bare_setting/comment_2_bc5a4be517409f8da2f36299dc4cbbde._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmu416zAYgYzbXVZAe30MiXoOWO4z6nGX8"
- nickname="Johannes"
- subject="comment 2"
- date="2013-12-06T13:18:45Z"
- content="""
-I believe this has been caused by the direct mode guart. I already had core.bare=true but also annex.direct=true which is actually incorrect when you really wanna have bare repository.
-"""]]
diff --git a/doc/bugs/another_build_error_in_assistant.mdwn b/doc/bugs/another_build_error_in_assistant.mdwn
deleted file mode 100644
index c21f1ac4e..000000000
--- a/doc/bugs/another_build_error_in_assistant.mdwn
+++ /dev/null
@@ -1,79 +0,0 @@
-What steps will reproduce the problem?
-Just trying to install git-annex last release (20121120) from cabal or from bundled sources
-
-What is the expected output? What do you see instead?
-Build stop like this :
-(doing cabal install or build from the bundle)
-...
-[161 of 284] Compiling Assistant.Alert  ( Assistant/Alert.hs, dist/build/git-annex/git-annex-tmp/Assistant/Alert.o )
-[162 of 284] Compiling Assistant.Types.DaemonStatus ( Assistant/Types/DaemonStatus.hs, dist/build/git-annex/git-annex-tmp/Assistant/Types/DaemonStatus.o )
-[163 of 284] Compiling Assistant.Monad  ( Assistant/Monad.hs, dist/build/git-annex/git-annex-tmp/Assistant/Monad.o )
-
-Assistant/Monad.hs:86:16:
-    Couldn't match expected type `Assistant a'
-                with actual type `Reader AssistantData a'
-    Expected type: (AssistantData -> a) -> Assistant a
-      Actual type: (AssistantData -> a) -> Reader AssistantData a
-    In the expression: reader
-    In an equation for `getAssistant': getAssistant = reader
-
-Assistant/Monad.hs:93:15:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: st <- reader threadState
-    In the expression:
-      do { st <- reader threadState;
-           liftIO $ runThreadState st a }
-
-Assistant/Monad.hs:99:14:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: d <- reader id
-    In the expression:
-      do { d <- reader id;
-           liftIO $ io $ runAssistant d a }
-
-Assistant/Monad.hs:105:14:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: d <- reader id
-    In the expression:
-      do { d <- reader id;
-           return $ runAssistant d a }
-
-Assistant/Monad.hs:110:14:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: d <- reader id
-    In the expression:
-      do { d <- reader id;
-           return $ \ v -> runAssistant d $ a v }
-
-Assistant/Monad.hs:115:14:
-    Couldn't match expected type `Assistant t0'
-                with actual type `Reader r0 a0'
-    In the return type of a call of `reader'
-    In a stmt of a 'do' block: d <- reader id
-    In the expression:
-      do { d <- reader id;
-           return $ \ v1 v2 -> runAssistant d (a v1 v2) }
-
-Assistant/Monad.hs:120:12:
-    Couldn't match expected type `Assistant a0'
-                with actual type `Reader r0 a1'
-    In the return type of a call of `reader'
-    In the first argument of `(>>=)', namely `reader v'
-    In the expression: reader v >>= liftIO . io
-
-
-
-
-What version of git-annex are you using? On what operating system?
-- version 3.20121112
-- Ubuntu 12.04 LTS, 64 bits
-
-> Dup of [[3.20121112_build_fails_on_Ubuntu_12.04]]. --[[Joey]] [[done]]
diff --git a/doc/bugs/archiving_git_repositories.mdwn b/doc/bugs/archiving_git_repositories.mdwn
deleted file mode 100644
index 4c2261eac..000000000
--- a/doc/bugs/archiving_git_repositories.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-In a true dropbox-like fashion, I tried to import my entire homefolder into the git-annex assistant. However, it seems that git-annex breaks on the several git repositories I've got checked out in my "Projects" folder. Is this a possible use case, or should I look at other tools to perform this with?
-
-> [[done]]; use a tarball or see extensive discussion here: 
-> <http://git-annex.branchable.com/bugs/Can__39__t_add_a_git_repo_to_git_annex:___34__Invalid_path_repo__47__.git__47__X__34___for_many_X/>
-> --[[Joey]]
diff --git a/doc/bugs/archiving_git_repositories/comment_1_51f546a571303118446a9e0b3e6482c9._comment b/doc/bugs/archiving_git_repositories/comment_1_51f546a571303118446a9e0b3e6482c9._comment
deleted file mode 100644
index cec1398fc..000000000
--- a/doc/bugs/archiving_git_repositories/comment_1_51f546a571303118446a9e0b3e6482c9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.23"
- subject="comment 1"
- date="2012-10-19T21:01:44Z"
- content="""
-The assistant is not ready to manage whole home directories, and the webapp refuses to allow you to do that.
-
-git doesn't allow checking a git repository into a git repository either. I archive old git repos inside one of my annexes by tarring them up.
-"""]]
diff --git a/doc/bugs/assistant___40__OS_X_Lion__41___-___34__too_many_open_files__34___error.mdwn b/doc/bugs/assistant___40__OS_X_Lion__41___-___34__too_many_open_files__34___error.mdwn
deleted file mode 100644
index 1b3879e63..000000000
--- a/doc/bugs/assistant___40__OS_X_Lion__41___-___34__too_many_open_files__34___error.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-What steps will reproduce the problem?
-
-I downloaded the most recent OS X Lion build of the Git Annex application bundle and ran it.
-
-I wanted to test the direct mode, as my existing annex is in the old style.
-So I set up a new (direct) repository, then added an SSH remote, then dropped a large number of files (170) in there.
-
-
-What is the expected output? What do you see instead?
-
-Expected: the files will be added to the repository in direct mode and stored on the ssh remote.
-Instead: the following error appeared in the webapp: 
- 
-Committer crashed: /Users/ed/directannex/.git/annex/tmp/: openTempFile: resource exhausted (Too many open files)
-
-nothing seems to have been synced to the remote -- I gather this from the fact that the annex directory in the remote git repo is only 70K instead of several hundred megs.
-
-
-What version of git-annex are you using? On what operating system?
-
- Version: 3.20130102  on OS X lion, using the version bundled as an application bundle.
-
-
-Please provide any additional information below.
-
-I imagine I could avoid this error by using the "ulimit -n" command to increase number of files in a shell session and then running assistant manually, so this is really only a bug report about the bundled application.
-
-> This seems to be caused by Command.Add.lockdown not closing the
-> temporary file handle, so when called in a mapM by the committer
-> thread when there are a lot of files, it could build up a lot of
-> open handles before later GC closes them. Added a manual close,
-> so I think this is [[done]]. --[[Joey]]
diff --git a/doc/bugs/assistant___40__OS_X_Lion__41___-___34__too_many_open_files__34___error/comment_1_9904c30a4c24a699d71e90ce5e9b89cf._comment b/doc/bugs/assistant___40__OS_X_Lion__41___-___34__too_many_open_files__34___error/comment_1_9904c30a4c24a699d71e90ce5e9b89cf._comment
deleted file mode 100644
index 4db7bf9a8..000000000
--- a/doc/bugs/assistant___40__OS_X_Lion__41___-___34__too_many_open_files__34___error/comment_1_9904c30a4c24a699d71e90ce5e9b89cf._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 1"
- date="2013-01-05T00:32:44Z"
- content="""
-After I painstakingly killed off the assistant's processes (I didn't see a way to stop it in the web interface, and issuing \"git annex assistant --stop\" did not stop it), and restarted the assistant, it synced successfully, so the error seems to have been transient.
-"""]]
diff --git a/doc/bugs/assistant_always_assumes_port_22__63__.mdwn b/doc/bugs/assistant_always_assumes_port_22__63__.mdwn
deleted file mode 100644
index 27896acd4..000000000
--- a/doc/bugs/assistant_always_assumes_port_22__63__.mdwn
+++ /dev/null
@@ -1,39 +0,0 @@
-### Please describe the problem.
-git-annex assistant always assumes port 22 (I use a different port), despite my editing .ssh/config to correct this.
-
-Also, assistant doesn't give me a port option like it did in the intro screencast.
-
-### What steps will reproduce the problem?
-Using my version of git-annex, I assume.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 3.20121112ubuntu2
-
-xubuntu 13.04
-
-### Please provide any additional information below.
-I don't see any .git/annex/daemon.log.
-
-I click the "remote server" link, sign in just fine [note below]. I click "Use a git repository on the server" (but "Use an encrypted rsync repository on the server" also does this), and eventually I get an error:
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-Failed to make repository
-
-Something went wrong setting up the repository on the remote server.
-
-Transcript: ssh: connect to host <host> port 22: Connection timed out 
-
-# End of transcript or log.
-"""]]
-
-> Your version of git-annex is too old. 
-> Support for setting the port was added in version 3.20121211 --
-> about a month after the version you have installed
-> (ah, the period where everything was 11 and 12.. I don't miss it!)
-> 
-> I don't recommend using such an old version of the assistant,
-> *massive* numbers of bugs have been fixed since then. Upgrade to 
-> the Ubuntu PPA. [[done]] --[[Joey]]
-
-note:  if I use "git-annex webapp" in the terminal it works fine; if I use xfce's "internet -> git annex" menu, it errors trying to use ssh_askpass, which I don't have. I'm going to make a new thread about this.
diff --git a/doc/bugs/assistant_does_not_list_remote___39__origin__39__.mdwn b/doc/bugs/assistant_does_not_list_remote___39__origin__39__.mdwn
deleted file mode 100644
index 2266c5dc4..000000000
--- a/doc/bugs/assistant_does_not_list_remote___39__origin__39__.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-What steps will reproduce the problem?
-
-1. create a git annex repo on a server
-2. clone it on workstation
-3. open the webapp on the workstation
-
-
-What is the expected output? What do you see instead?
-
-The webapp should show the 'origin' remote and the assistant should ensure syncing.
-Instead the remote does not show up in the webapp.
-I checked with `git annex status` and the remote is there.
-
-What version of git-annex are you using? On what operating system?
-
-3.20130207 on latest Ubuntu
-
-Please provide any additional information below.
-
-I tried both with direct and indirect mode for the local annex repo.
-
-I am sorry if I am missing the point. I checked the docs, however without much success.
-
-[[!tag /design/assistant]]
-
-[[done]]
diff --git a/doc/bugs/assistant_does_not_list_remote___39__origin__39__/comment_1_ffa008240c61b50396aa92f467731db6._comment b/doc/bugs/assistant_does_not_list_remote___39__origin__39__/comment_1_ffa008240c61b50396aa92f467731db6._comment
deleted file mode 100644
index 8f6cb5317..000000000
--- a/doc/bugs/assistant_does_not_list_remote___39__origin__39__/comment_1_ffa008240c61b50396aa92f467731db6._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmaMxYm33s0H-nxBo5uzYUzdIECoyR8Ug8"
- nickname="Stefan"
- subject="an update"
- date="2013-02-13T20:33:22Z"
- content="""
-The remotes were not listed because git-annex-shell was not working (found in the path, however necessary *.so files were not found).
-
-Now all remotes are listed. `.git/config` is ok, with the uuid listed. `git annex status` returns all.
-
-However sync is not working. The webapp on the workstation states that it has synced with the server, however `ls` on the server returns empty. The server is set as archive, the workstation as client.
-"""]]
diff --git a/doc/bugs/assistant_does_not_list_remote___39__origin__39__/comment_2_a53f80090bc2a0f32b8d8307cb24b563._comment b/doc/bugs/assistant_does_not_list_remote___39__origin__39__/comment_2_a53f80090bc2a0f32b8d8307cb24b563._comment
deleted file mode 100644
index 5915fd844..000000000
--- a/doc/bugs/assistant_does_not_list_remote___39__origin__39__/comment_2_a53f80090bc2a0f32b8d8307cb24b563._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.210"
- subject="comment 2"
- date="2013-02-26T19:51:47Z"
- content="""
-You are probably not running the assistant on the server. This is fine, but it means that git pushes made to the server when files are added to the client are not merged into its working copy. Which is why you don't see the files. Running `git annex sync` on the server should make all the files that have been sent to it show up.
-"""]]
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add.mdwn b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add.mdwn
deleted file mode 100644
index 6539dc9e8..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-What steps will reproduce the problem?
-
-Unable to reproduce as it seems to happen randomly, to very few files (4/250).
-
-What is the expected output? What do you see instead?
-
-I expect to see the assistant warn if it attempts to add a file which fails to add to the annex.
-Instead, I see no output from the assistant, but lines like this in the log.
-
-daemon.log.2:add Indie Game Stand/Deadly 30/Deadly30_MAC.zip (checksum...) failed
-daemon.log.2:add Indie Game Stand/Wyv and Keep/xnafx40_redist.msi (checksum...) failed
-daemon.log.2:add Indie Game Stand/Blueberry Garden/Blueberry_Garden_1.1.zip (checksum...) failed
-daemon.log.2:add Indie Game Stand/Flatspace Bundle/fsmusicpack3setup.exe (checksum...) failed
-
-There is no reason given for the failure in the log file. The assistant also never tries to add them again in normal running (but did add them when it was started again after a reboot).
-
-What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130314
-OS: Arch Linux
-
-Please provide any additional information below.
-
-The assistant in this case is being used as nothing more than a way for me to see which files have been added (--verbose, --foreground and --debug with 'watch' outputs nothing..). No remotes or anything like that.
-
-> I have made the assistant re-queue any file that it fails to add,
-> so it will retry it later. Typically within a few seconds. [[done]]
-> 
-> I have only been able to think of one scenario in which this could
-> happen. It's pretty unusual:
-> 
-> * Something writes to a file, and closes it.
-> * Assistant sees file has no writers, and locks it down in preparation
->   to add it.
-> * Something then re-opens the file to write to it some more.
->   Note that it would seem to need to bypass permissions that prevent
->   the file from being written to in order to do this. It makes a change
->   to the file.
-> * Assistant is checksumming file, reaches end, and detects it has been
->   tampered with and gives up.
-> 
-> I would still like more information about circumstances that
-> cause this to happen, because while a possible scenario, the 
-> above is too weird to believe anyone could run into it.
-> 
-> --[[Joey]] 
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_1_13b2f93b7d09c8fd6c22829a0dc6428b._comment b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_1_13b2f93b7d09c8fd6c22829a0dc6428b._comment
deleted file mode 100644
index 02db48da7..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_1_13b2f93b7d09c8fd6c22829a0dc6428b._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-06T16:34:00Z"
- content="""
-The assistant runs a daily sanity checker job which will clean up files like these. (`git annex watch` does not, however).
-
-I think the main reason add could fail is if a file gets modified while it's in the process of being added. It could retry right away, although it needs to do it in a way that does not loop if the file continually fails to be added.
-"""]]
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_2_94e46bc0044b8a91a9fd51058825aa8f._comment b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_2_94e46bc0044b8a91a9fd51058825aa8f._comment
deleted file mode 100644
index a8a5aad9a..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_2_94e46bc0044b8a91a9fd51058825aa8f._comment
+++ /dev/null
@@ -1,60 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 2"
- date="2013-04-06T21:50:18Z"
- content="""
-The sanity check never added the failed files:
-
-    daemon.log.2:add Indie Game Stand/Deadly 30/Deadly30_WINDOWS.zip (checksum...) [2013-03-24 20:44:10 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Deadly 30/Deadly30_LINUX.zip (checksum...) [2013-03-24 20:44:34 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Deadly 30/Deadly30_MAC.zip (checksum...) failed
-    daemon.log.2:add Indie Game Stand/Deadly 30/GonzoSSM_YouTube_Videos.zip (checksum...) [2013-03-24 20:51:05 GMT] Committer: Committing changes to git
-
-    daemon.log.2:[2013-03-25 14:48:01 GMT] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/Wyvs_Cartographer.zip (checksum...) [2013-03-25 17:46:19 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/WnK_Level_Pack.zip (checksum...) [2013-03-25 17:46:20 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/SmashBox_OST_Mp3.zip (checksum...) [2013-03-25 17:56:37 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/xnafx40_redist.msi (checksum...) failed
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/WnK091_Win.zip (checksum...) [2013-03-25 18:04:53 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/wyv_and_keep_OST_MP3.zip (checksum...) [2013-03-25 18:08:20 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/SmashBox_OST_FLAC.zip (checksum...) [2013-03-25 18:08:43 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/WnK0907_OSX.zip (checksum...) [2013-03-25 18:10:25 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/dotNetFx40_Full_x86_x64.exe (checksum...) [2013-03-25 18:10:39 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Wyv and Keep/wyv_and_keep_OST_FLAC.zip (checksum...) [2013-03-25 18:45:39 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Blueberry Garden/BlueBerryGarden_Sheet_Music.zip (checksum...) [2013-03-25 19:08:04 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Blueberry Garden/dotNetFx45_Full_setup.exe (checksum...) [2013-03-25 19:08:18 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Blueberry Garden/Eriks_Prototypes.zip (checksum...) [2013-03-25 19:08:25 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Blueberry Garden/xnafx40_redist.msi (checksum...) [2013-03-25 19:09:05 GMT] Committer: Committing changes to git
-
-    daemon.log.2:add Indie Game Stand/Blueberry Garden/Blueberry_Garden_1.1.zip (checksum...) failed
-    daemon.log.2:add Indie Game Stand/Blueberry Garden/daduk_Et_Apres.zip (checksum...) [2013-03-25 19:09:53 GMT] Committer: Committing changes to git
-
-    daemon.log.2:add Indie Game Stand/Flatspace Bundle/fsmusicpack3setup.exe (checksum...) failed
-    daemon.log.2:add Indie Game Stand/Flatspace Bundle/flatspaceiifullsetup.exe (checksum...) [2013-03-25 20:45:17 GMT] Committer: Committing changes to git
-    daemon.log.2:add Indie Game Stand/Flatspace Bundle/flatspacefullsetup.exe (checksum...) [2013-03-25 20:45:24 GMT] Committer: Committing changes to git
-
-    daemon.log.2:[2013-03-26 14:48:04 GMT] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-03-27 14:48:08 GMT] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-03-28 14:48:12 GMT] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-03-29 14:48:15 GMT] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-03-30 14:48:18 GMT] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-03-31 15:48:22 BST] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-04-01 15:48:25 BST] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-04-02 15:48:29 BST] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-04-03 15:48:33 BST] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-04-04 15:48:36 BST] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-    daemon.log.2:[2013-04-05 15:48:40 BST] SanityCheckerDaily: Running daily sanity check to make sure everything is ok.
-
-    daemon.log.1:add Indie Game Stand/Blueberry Garden/Blueberry_Garden_1.1.zip (checksum...) [2013-04-05 21:21:15 BST] Committer: Adding Deadly30_MAC.zip
-    daemon.log.1:add Indie Game Stand/Deadly 30/Deadly30_MAC.zip (checksum...) [2013-04-05 21:21:16 BST] Committer: Adding fsmusicpa..setup.exe
-    daemon.log.1:add Indie Game Stand/Flatspace Bundle/fsmusicpack3setup.exe (checksum...) [2013-04-05 21:21:16 BST] Committer: Adding xnafx40_redist.msi
-    daemon.log.1:add Indie Game Stand/Wyv and Keep/xnafx40_redist.msi (checksum...) [2013-04-05 21:21:16 BST] Committer: Committing changes to git
-
-I just managed to trigger the issue again. The file has been chmod-ed to 440 but not added to the annex. The log, once again, shows that the checksum failed.
-
-    add CG Cookie/Modeling a Female Human Head/couse_female_head_05.zip (checksum...) failed
-
-The files are being downloaded directly into the directory with the DownThemAll. This downloads the file in a temporary name ending in .dtapart, which is ignored through \".gitignore\". I would have thought that there was nothing stopping the file from being checksummed as git-annex would only see it after the rename, where the file is no longer being written to by anything.
-"""]]
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_3_10a38bdbf31dd4071e4bc4ac746d9c56._comment b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_3_10a38bdbf31dd4071e4bc4ac746d9c56._comment
deleted file mode 100644
index 3ad62a251..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_3_10a38bdbf31dd4071e4bc4ac746d9c56._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-08T17:17:54Z"
- content="""
-The assistant does not yet support `.gitignore`
-
-Does `git annex add` work on these files?
-
-"""]]
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_4_b8fdf502c7e80aece5a9544a2078c85c._comment b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_4_b8fdf502c7e80aece5a9544a2078c85c._comment
deleted file mode 100644
index 33b050070..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_4_b8fdf502c7e80aece5a9544a2078c85c._comment
+++ /dev/null
@@ -1,36 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 4"
- date="2013-04-08T18:25:48Z"
- content="""
-Interesting that you say .gitignore doesn't work with assistant because.. it definitely does.
-
-    $ git init /tmp/annex-test
-    $ cd /tmp/annex-test
-    $ git annex init
-    $ echo \"file.test\" > .gitignore
-    $ git annex assistant
-    $ echo \"test1\" > file.test
-    $ echo \"test2\" > file2.test
-
-yields this log file:
-    
-    (scanning...) [2013-04-08 19:17:03 BST] Watcher: Performing startup scan
-    (started...) 
-    [2013-04-08 19:17:10 BST] Committer: Adding file2.test
-    add file2.test (checksum...) [2013-04-08 19:17:10 BST] Committer: Committing changes to git
-    (Recording state in git...)
-    (Recording state in git...)
-    [2013-04-08 19:17:11 BST] Committer: Committing changes to git
-
-git annex find:
-
-    file2.test
-
-On the previous files, the log shows all failed files being added to the annex find after the assistant was restarted (daemon.log.1) so I would imagine 'git annex add' would have worked fine too.
-
-Right now, I'm just running
-    while true; do git annex add; sleep 1; done
-in the annex directory, which gives me (expensive) watch-like behaviour, with fairly clear output for me to confirm everything has been added. 
-"""]]
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_5_a2ff7668f2a0d549b362d7de97fac8a1._comment b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_5_a2ff7668f2a0d549b362d7de97fac8a1._comment
deleted file mode 100644
index 10c068f13..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_5_a2ff7668f2a0d549b362d7de97fac8a1._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-04-08T21:16:33Z"
- content="""
-\"I would imagine\" is not a useful debugging method. I asked you to run `git annex add` so that if it succeeds, I have a verified data point that reduces the problem space to only code inside the assistant, and if it fails, I have an easy way to reproduce the problem to debug further. At the moment, I have neither. :P
-
-`.gitignore` is really, truely, not supported by the assistant. I just ran your test case, and it added `file.test` as soon as I created it. Also, I never wrote support for `.gitignore`; I know right where that support should go, and I have a dozen people who have complained it is not supported.
-"""]]
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_6_60d72f34a6cfd1c081f74aa610f4305a._comment b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_6_60d72f34a6cfd1c081f74aa610f4305a._comment
deleted file mode 100644
index c8a2730c2..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_6_60d72f34a6cfd1c081f74aa610f4305a._comment
+++ /dev/null
@@ -1,33 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 6"
- date="2013-04-08T22:06:35Z"
- content="""
-When you asked me if 'git annex add' worked, I wasn't in the position to test it as I didn't have any files in this failed state. All reported occurrences had been added by the assistant's startup scan on its second running...
-
-I've managed to reproduce the issue again and can confirm 'git annex add'ing the file that failed to checksum through the assistant works successfully. The only difference on this occurrence is that I downloaded the files from a local webserver, sharing the files from my disk as it was taking several gigabytes of download to occur. All other files were added successfully.
-
-daemon.log
-
-    [2013-04-08 22:41:13 BST] Committer: Adding blender_l.eos_04.zip
-    add blender_lowpoly_videos_04.zip (checksum...) failed
-
-git annex add
-
-    $ git annex add blender_lowpoly_videos_04.zip
-    add blender_lowpoly_videos_04.zip (checksum...) ok
-
-In case it matters at all, the workaround I am using below has not demonstrated the issue yet:
-
-    while true; do git annex add; sleep 1; done
-
-Still very interesting that .gitignore is not supposed to work. After running through the test case on my machine:
-Restarting the assistant doesn't add file.test
-'git annex add' doesn't add file.test
-'git annex add file.test' doesn't add file.test
-
-Looks like it works as one would expect from here. Perhaps I'm in some backwards dimension where what should work, doesn't, and what shouldn't work, does! :) Would certainly explain a lot..
-
-Thanks for your help. As you can probably tell, I really want to use git-annex!
-"""]]
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_7_53a73e662c9356b759fbfa1e5a3bd927._comment b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_7_53a73e662c9356b759fbfa1e5a3bd927._comment
deleted file mode 100644
index 578870f0a..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_7_53a73e662c9356b759fbfa1e5a3bd927._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 7"
- date="2013-04-23T22:11:32Z"
- content="""
-I have added some messages when add fails to indicate why it failed. Going through the failure modes while doing this, the most likely reason does seem to be that the file is changed while it's in the process of being checksummed. You can upgrade to tonight's build to get a version with these added messages.
-
-Can you run the assistant with `--debug` and send a complete log of the problem happening?
-
-(The sanity checker not adding the files seems to be a red herring; I was wrong and it only adds any symlinks that failed to get staged.)
-
-(Re the .gitignore red herring, the one place in the assistant that *does* honor .gitignore is the startup scan. However this will not affect the assistant's behavior when files are added to the repository after it's started up and is running. I suspect that if you just look at `git log --stat` you will see that the temp files used by DownThemAll are being added, and then deleted from the git repository. But this is a red herring, so meh.)
-"""]]
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_8_10b65168b6a54d960427966d7e3d05f5._comment b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_8_10b65168b6a54d960427966d7e3d05f5._comment
deleted file mode 100644
index 2cf9790e9..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_8_10b65168b6a54d960427966d7e3d05f5._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 8"
- date="2013-05-12T22:59:37Z"
- content="""
-Just reproduced this issue on 4.20130417-g4bb97d5. Looks like the digesting is the failing part, but no indication as to why.
-
-    [2013-05-12 23:23:21 BST] Watcher: file deleted test/SleepIsDeath_v16_UnixSource.tar.gz-{b8c941eb-baf0-46de-81fa-19d25aca05fb}.dtapart
-    [2013-05-12 23:23:21 BST] read: git [\"--git-dir=/home/xyem/annex/.git\",\"--work-tree=/home/xyem/annex\",\"ls-files\",\"--others\",\"--exclude-standard\",\"-z\",\"--\",\"test/SleepIsDeath_v16_UnixSource.tar.gz-{b8c941eb-baf0-46de-81fa-19d25aca05fb}.dtapart\",\"test/SleepIsDeath_v16_UnixSource.tar.gz\"]
-    [2013-05-12 23:23:21 BST] read: lsof [\"-F0can\",\"+d\",\"/home/xyem/annex/.git/annex/tmp/\"]
-    [2013-05-12 23:23:22 BST] Committer: Adding SleepIsDe..ce.tar.gz
-    add test/SleepIsDeath_v16_UnixSource.tar.gz (checksum...) [2013-05-12 23:23:22 BST] read: sha256sum [\"/home/xyem/annex/.git/annex/tmp/SleepIsDeath_v16_UnixSource.tar6479.gz\"]
-    failed
-    [2013-05-12 23:23:22 BST] Committer: committing 1 changes
-    [2013-05-12 23:23:22 BST] Committer: Committing changes to git
-    (Recording state in git...)
-
-"""]]
diff --git a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_9_b640e8fa6aafb041d66bbf8857a8fa3d._comment b/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_9_b640e8fa6aafb041d66bbf8857a8fa3d._comment
deleted file mode 100644
index 738e1929f..000000000
--- a/doc/bugs/assistant_does_not_warn_on_files_it_failed_to_add/comment_9_b640e8fa6aafb041d66bbf8857a8fa3d._comment
+++ /dev/null
@@ -1,44 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 9"
- date="2013-05-12T23:34:51Z"
- content="""
-Whoops. Upgraded to 4.20130501-g4a5bfb3 and reproduced it again. Looks like the file is being changed between the file being closed and git-annex trying to add it.
-
-Though I'm using DownThemAll, I have it set to \"1 segment\" so the file should only have 1 writer.
-Looks like the file gets retried immediately and is being added okay though.
-
-Would it be worth me trying to log filesystem accesses with a passthrough FUSE filesystem to try and figure out what it going on?
-
-      O'Reilly/Mind Performance Hacks/urn_x-domain_oreilly.com_product_9780596153113.EBOOK-{711cd6ac-12b9-4d4e-92d6-66caa9825cf4}.dtapart still has writers, not adding
-    [2013-05-13 00:18:29 BST] read: git [\"--git-dir=/home/xyem/annex/.git\",\"--work-tree=/home/xyem/annex\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"]
-    [2013-05-13 00:18:33 BST] Watcher: file deleted O'Reilly/Mind Performance Hacks/urn_x-domain_oreilly.com_product_9780596153113.EBOOK-{711cd6ac-12b9-4d4e-92d6-66caa9825cf4}.dtapart
-    [2013-05-13 00:18:33 BST] read: git [\"--git-dir=/home/xyem/annex/.git\",\"--work-tree=/home/xyem/annex\",\"ls-files\",\"--others\",\"--exclude-standard\",\"-z\",\"--\",\"O'Reilly/Mind Performance Hacks/urn_x-domain_oreilly.com_product_9780596153113.EBOOK-{711cd6ac-12b9-4d4e-92d6-66caa9825cf4}.dtapart\",\"O'Reilly/Mind Performance Hacks/Mind_Performance_Hacks.mobi\"]
-    [2013-05-13 00:18:33 BST] read: lsof [\"-F0can\",\"+d\",\"/home/xyem/annex/.git/annex/tmp/\"]
-    [2013-05-13 00:18:33 BST] Committer: Adding Mind_Perf..acks.mobi
-    add O'Reilly/Mind Performance Hacks/Mind_Performance_Hacks.mobi (checksum...) [2013-05-13 00:18:33 BST] read: sha256sum [\"/home/xyem/annex/.git/annex/tmp/Mind_Performance_Hacks13351.mobi\"]
-
-      O'Reilly/Mind Performance Hacks/Mind_Performance_Hacks.mobi changed while it was being added
-    [2013-05-13 00:18:33 BST] Committer: delaying commit of 1 changes
-    failed
-    [2013-05-13 00:18:33 BST] Committer: committing 1 changes
-    [2013-05-13 00:18:33 BST] Committer: Committing changes to git
-    (Recording state in git...)
-    [2013-05-13 00:18:33 BST] feed: git [\"--git-dir=/home/xyem/annex/.git\",\"--work-tree=/home/xyem/annex\",\"update-index\",\"-z\",\"--index-info\"]
-    [2013-05-13 00:18:33 BST] read: git [\"--git-dir=/home/xyem/annex/.git\",\"--work-tree=/home/xyem/annex\",\"commit\",\"--allow-empty-message\",\"--no-edit\",\"-m\",\"\",\"--quiet\",\"--no-verify\"]
-    [2013-05-13 00:18:33 BST] read: git [\"--git-dir=/home/xyem/annex/.git\",\"--work-tree=/home/xyem/annex\",\"symbolic-ref\",\"HEAD\"]
-    [2013-05-13 00:18:33 BST] read: git [\"--git-dir=/home/xyem/annex/.git\",\"--work-tree=/home/xyem/annex\",\"show-ref\",\"refs/heads/master\"]
-    [2013-05-13 00:18:34 BST] read: git [\"--git-dir=/home/xyem/annex/.git\",\"--work-tree=/home/xyem/annex\",\"ls-files\",\"--others\",\"--exclude-standard\",\"-z\",\"--\",\"O'Reilly/Mind Performance Hacks/Mind_Performance_Hacks.mobi\"]
-    [2013-05-13 00:18:34 BST] read: lsof [\"-F0can\",\"+d\",\"/home/xyem/annex/.git/annex/tmp/\"]
-    [2013-05-13 00:18:34 BST] Committer: Adding Mind_Perf..acks.mobi
-    add O'Reilly/Mind Performance Hacks/Mind_Performance_Hacks.mobi (checksum...) [2013-05-13 00:18:34 BST] read: sha256sum [\"/home/xyem/annex/.git/annex/tmp/Mind_Performance_Hacks13351.mobi\"]
-    [2013ok
-    -05-13 00:18:34 BST] Watcher: file deleted O'Reilly/Mind Performance Hacks/Mind_Performance_Hacks.mobi
-    [2013-05-13 00:18:34 BST] Watcher: add symlink O'Reilly/Mind Performance Hacks/Mind_Performance_Hacks.mobi
-    [2013-05-13 00:18:34 BST] Committer: committing 2 changes
-    [2013-05-13 00:18:34 BST] chat: git [\"--git-dir=/home/xyem/annex/.git\",\"--work-tree=/home/xyem/annex\",\"hash-object\",\"-t\",\"blob\",\"-w\",\"--stdin\"]
-    [2013-05-13 00:18:34 BST] Committer: Committing changes to git
-    (Recording state in git...)
-
-"""]]
diff --git a/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__.mdwn b/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__.mdwn
deleted file mode 100644
index 4b826fd6b..000000000
--- a/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__.mdwn
+++ /dev/null
@@ -1,48 +0,0 @@
-### Please describe the problem.
-When i start "git annex assistant" it starts normally without messages and then even syncs one time. But then after a minute or so it stops doing anything. I see it in "ps aux" but it doesn't autoprocess directory anymore. Repo is in "direct" mode.
-
-### What version of git-annex are you using? On what operating system?
-CentOS 6.5, standalone git-annex 5.20140421-g515d251 unpacked in /home/filesync/git-annex.linux/ and in $PATH.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# .git/annex/daemon.log
-
-[2014-05-20 08:56:37 MSK] main: starting assistant version 5.20140421-g515d251
-[2014-05-20 08:56:37 MSK] Cronner: You should enable consistency checking to protect your data. 
-
-  dbus failed; falling back to mtab p[of2la0li1il4ne-gd0  5(t-Co2l 0ia ed0nd8t :Ew5ra6rt:oc3rh8   {oMcnSl Kid]ei nrTterEcartnrosorfryeM re/Sshcsoaamngene/e fr=i: l "eSrsyuynnncCcil/ni.gec nowtni:ft ihug n/oagrbiiltge-i antn on
- edxe t(e/rhmoimnee/ fDiBlUeSs yandcd/r.ecsosn"f,i gc/lgiietn-taEnrnreoxr:F agteatlD i=r eTcrtuoer}y)C
-o
-n t elnotsst:  ddbouess  cnoontn eecxtiisotn ;( Nfoa lsluicnhg  fbialcek  otro  dpiorlelcitnogr y()S)o
-cketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-
-Already up-to-date.
-p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
-(scanning...) [2014-05-20 08:56:38 MSK] Watcher: Performing startup scan
-[2014-05-20 08:56:39 MSK] Upgrader: An upgrade of git-annex is available.  (version 5.20140517)
-Everything up-to-date
-
-  lost dbus connection; falling back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-(started...) 
-
-  lost dbus connection; falling back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-
-  lost dbus connection; falling back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-
-  lost dbus connection; falling back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-
-  lost dbus connection; falling back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-
-  lost dbus connection; falling back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-
-  lost dbus connection; falling back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-
-  lost dbus connection; falling back to polling (SocketError {socketErrorMessage = "connect: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/var/run/dbus/system_bus_socket")})
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_1_a3dccf1db287ea5c1ac1763518d5d9f9._comment b/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_1_a3dccf1db287ea5c1ac1763518d5d9f9._comment
deleted file mode 100644
index bf62d7f6d..000000000
--- a/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_1_a3dccf1db287ea5c1ac1763518d5d9f9._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmaB2n9HFclAvyMyDzvTPaifh5OrlF51Co"
- nickname="VS7"
- subject="DBus wasn't installed"
- date="2014-05-20T11:46:35Z"
- content="""
-    yum install dbus
-    service messagebus restart
-"""]]
diff --git a/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_2_cb85fb3ba0152671568c23d6b95f3b7a._comment b/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_2_cb85fb3ba0152671568c23d6b95f3b7a._comment
deleted file mode 100644
index ff273cae0..000000000
--- a/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_2_cb85fb3ba0152671568c23d6b95f3b7a._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.3"
- subject="comment 2"
- date="2014-05-21T17:18:08Z"
- content="""
-git-annex only uses dbus to detect when drives and networks come and go, this has nothing to do with its core functionality and i would be very surprised if lack of dbus being installed prevented it from working in any way.
-
-It's not clear to me if you think that installing dbus somehow fixed your issue. 
-
-You seem to have filed a second bug report, [[Daemon_stops_working_on_mounted_CIF_share]] about the same symptoms, and in that bug report, it looks rather like your network(?) file system is badly broken and so git-annex cannot access it.
-
-Please follow up with clarifications.
-"""]]
diff --git a/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_3_5d87371fa86ddbbcd31dfc932ab6080f._comment b/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_3_5d87371fa86ddbbcd31dfc932ab6080f._comment
deleted file mode 100644
index 8df8977ad..000000000
--- a/doc/bugs/assistant_doesn__39__t_work:___34__lost_dbus_connection__59___falling_back_to_polling__34__/comment_3_5d87371fa86ddbbcd31dfc932ab6080f._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmaB2n9HFclAvyMyDzvTPaifh5OrlF51Co"
- nickname="VS7"
- subject="comment 3"
- date="2014-05-22T06:07:50Z"
- content="""
-At least installing DBus helped to get rid of these messages in daemon.log :)
-But yes it didn't resolve the problem - assistant still stops functioning after a while. Lets proceed to [[Daemon stops working on mounted CIF share]]
-"""]]
diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn
deleted file mode 100644
index c5a75b361..000000000
--- a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-Thanks for git annex!
-
-### Please describe the problem.
-
-I've set up two computers A, B to sync to (and each other through) a remote server S. If I add files to A, it syncs with S. But B is not getting synced unless I run 'git annex sync' or restart the daemon in the webapp, i.e. I don't see these files on B at all, not even as broken symlinks. 
-The same happens if I manually copy files from A to S. B is not updating the copy count in 'git annex whereis' until I manually sync on B.
-
-It would be great if B could automatically sync when S is changed, either file locations or contents.
-
-### What steps will reproduce the problem?
-
-Both computers' local repos were setup with annex assistant, and switched into indirect mode. The server contains git repo and file data. All systems, computers and server are set to manual in the preferred content mode.
-
-### What version of git-annex are you using? On what operating system?
-
-A is running Debian testing with git-annex 4.20130827, B and S are running Debian stable with the backports version of git-annex 4.20130815~bpo70+1. A and S are 64 bit, B is 32 bit. All are up to date.
-
-### Please provide any additional information below.
-
-I tried this setup before with direct mode and different preferred content settings (A, B as client, S as backup or archive), and syncing of git and file data was working then.
-
-Despite being able to run 'sync' it is at least inconvenient to not have automatically updated file location information when I run the assistant. (I could then just run without it, but I had it happen to me that I setup a local repo w/o assistant, and when I ran assistant, expecting it would tell me "there are no local repos, would you like to create one?" it somehow automatically found the manually created one and started copying files. But that's another problem.)
-
-> [[done]] unless my diagnosis is wrong. --[[Joey]] 
diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_1_37acb3afafb1b4c4da7c778130cf3035._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_1_37acb3afafb1b4c4da7c778130cf3035._comment
deleted file mode 100644
index 94dc51d0a..000000000
--- a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_1_37acb3afafb1b4c4da7c778130cf3035._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlQsgfXntaEvZPKgd_K0dfoFcYBJXKcaFE"
- nickname="Sten"
- subject="Direct oder indirect mode makes no difference"
- date="2013-09-09T23:36:49Z"
- content="""
-Direct or indirect mode does not make a difference. I created another setup like this, only different is direct mode, otherwise the same (in particular preferred content mode is manual). Result: Still no sync.
-"""]]
diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_2_9d58887ee0184663852bde83b8d497c7._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_2_9d58887ee0184663852bde83b8d497c7._comment
deleted file mode 100644
index 8d388ceee..000000000
--- a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_2_9d58887ee0184663852bde83b8d497c7._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlQsgfXntaEvZPKgd_K0dfoFcYBJXKcaFE"
- nickname="Sten"
- subject="computer in manual mode seems to be the reason, not server"
- date="2013-09-10T02:21:59Z"
- content="""
-If I create a setup like originally described with the only difference being S set to full backup mode, I see no change in sync behavior. 
-
-In detail, what happens is: A gets files added. These changes are committed and synced. Because S is in full backup mode, the file content is also sent from A to S (this is different, but expected). However, B still does not sync until manually run. I would expect that B's manual mode only applies to file content (it is the preferred content setting), not to changes to the git repo, thus I'd expect git changes to sync to all involved (and accessible) repos.
-"""]]
diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_3_b70881c8026e30fd3ddc051bd01a888b._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_3_b70881c8026e30fd3ddc051bd01a888b._comment
deleted file mode 100644
index d42cf6cd2..000000000
--- a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_3_b70881c8026e30fd3ddc051bd01a888b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlQsgfXntaEvZPKgd_K0dfoFcYBJXKcaFE"
- nickname="Sten"
- subject="available copies update need manual sync too"
- date="2013-09-10T02:55:44Z"
- content="""
-After copying files from S to B (as expected manually), I have to (unexpectedly) manually sync again on A to update the #copies on A.
-"""]]
diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_4_43f756e2e6ff985c8e050da0e369d486._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_4_43f756e2e6ff985c8e050da0e369d486._comment
deleted file mode 100644
index 51e9cc135..000000000
--- a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_4_43f756e2e6ff985c8e050da0e369d486._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlQsgfXntaEvZPKgd_K0dfoFcYBJXKcaFE"
- nickname="Sten"
- subject="output of git annex sync "
- date="2013-09-10T03:19:51Z"
- content="""
-When running sync on B after copying file content from A to S (manually or automatically), I saw the following output (copied just the end of it):
- ...
- file.pdf                                              |    1 +
- file.txt                                              |    1 +
- 762 files changed, 762 insertions(+)
- ...
- create mode 120000 file.pdf
- create mode 120000 file.txt
-
-git-annex: /home/sten/Documents/.git/annex/merge/: getDirectoryContents: does not exist (No such file or directory)
-failed
-push server 
-Everything up-to-date
-ok
-git-annex: sync: 1 failed
-
-A subsequent sync worked without error.
-
-"""]]
diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment
deleted file mode 100644
index 05a3d7f74..000000000
--- a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.2.134"
- subject="comment 5"
- date="2013-09-13T18:30:53Z"
- content="""
-You have described the following git-annex network:
-
-	A --(ssh)-- S --(ssh)-- B
-
-So A automatically syncs to S. But there is no way at all for A to tell B that it has made changes. So B does not automatically sync.
-
-The git-annex webapp will detect this kind of situation, and display this alert:
-
-[[assistant/xmppnudge.png]]
-
-Once you set up an XMPP account, the network will look like: 
-
-	A --(ssh)-- S --(ssh)-- B
-	\_________(XMPP)_______/
-                    
-And now B will immediatly know when A has pushed a change to S, and will go get it.                                          
-
-(The `getDirectoryContents` error is probably because you are running git annex sync in a repository that the git-annex assistant is running in, and they are both using the same tmp directory for merging branches sync pulled. It does not seem to be worth worrying about.)
-"""]]
diff --git a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files.mdwn b/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files.mdwn
deleted file mode 100644
index 910796091..000000000
--- a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files.mdwn
+++ /dev/null
@@ -1,56 +0,0 @@
-__What steps will reproduce the problem?__
-
-on server:
-
-* mkdir annex
-* cd annex
-* git init
-* git annex init "donkey"
-* git commit -m "CREATE GIT ANNEX" --allow-empty
-
-on desktop:
-
-* git clone ssh://donkey/home/xyem/annex
-* cd annex
-* git annex init "jaguar"
-* git annex vicfg
-(..change origin and 'here' to 'manual' group..)
-* git annex sync
-* git annex webapp
-
-on server: 
-
-* git annex sync
-* git annex assistant
-
-(..download/move a file into the annex folder on the desktop..)
-
-__What is the expected output?__
-
-The server should be synced, gaining a broken symlink to the file. No file data transferred to the server (manual mode).
-
-__What do you see instead?__
-
-In addition to the expected/wanted behaviour above, the webapp shows the assistant trying to transfer the file contents to the server, despite it being in the manual group. This is also shown in 'ps aux | grep git' where there is a 'transferkey' operation for the file[1].
-
-__What version of git-annex are you using? On what operating system?__
-
-* server:  4.20130314
-* desktop: 4.20130314
-* OS: Arch Linux
-* Package: git-annex-bin (AUR)
-
-__Please provide any additional information below.__
-
-[1] The transfer itself doesn't work because the assistant is trying to use its own SSH connection caching, with no keys and without prompting for a password, rather than use my existing connection caching. Running the transferkey command manually seems to work though. This isn't a concern at the moment.
-
-Restarting the webapp has not effect. The file is still in the transfer queue and additional files also get added for transfer.
-
-This was working correctly on a previous version, but I'm not sure which one of these I was using at the time:
-
-* 3.20130114
-* 3.20130216
-* 4.20130227
-
-> Closing this bug report since my comment below seems a reasonable
-> explanation for the behavior you saw. [[done]] --[[Joey]] 
diff --git a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_1_e3f545d9adc27a4e7340bf16177c4fe0._comment b/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_1_e3f545d9adc27a4e7340bf16177c4fe0._comment
deleted file mode 100644
index bad85478e..000000000
--- a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_1_e3f545d9adc27a4e7340bf16177c4fe0._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-24T12:45:23Z"
- content="""
-You say you changed `origin` and `here` to be in the manual group, but did you set their preferred-content to `standard`? If you did not, the group setting will not influence which files they want, and the default behavior of wanting all files will be used.
-
-Since you are running the assistant on the server, it will automatically update to have symlinks to new files when the desktop does a git push to it. It sounds like the desktop is failing to push to the server for some reason. You can look at '.git/annex/daemon.log` to see any error messages from `git push`.
-
-If you have `ssh-askpass` installed on the client, it should use it to prompt for any necessary ssh password. Given your described configuration, git-annex will be using your regular ssh keys. You can disable its built-in ssh connection caching with `git config annex.sshcaching false` if desired.
-"""]]
diff --git a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_2_1403076dbc47733607f0c8b2856e2381._comment b/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_2_1403076dbc47733607f0c8b2856e2381._comment
deleted file mode 100644
index e30e99eee..000000000
--- a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_2_1403076dbc47733607f0c8b2856e2381._comment
+++ /dev/null
@@ -1,37 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 2"
- date="2013-04-13T20:50:16Z"
- content="""
-Ah I see. Bit of a misunderstanding on my end about what the groups did, by the looks of it. I was under the impression they controlled how files moved around, if at all (as described in the webapp), and the preferred-content was just fine-tuning controls.
-
-I just went to set this back up to see if setting it to \"standard\" in vicfg works how I want it to and now I've hit a different problem. The webapp/assistant isn't populating the git commit messages on it's own, it is launching $EDITOR (vi if unset on my system) in the background to prompt me for it (where I can't see it).
-
-    ├─xterm
-    │   └─bash
-    │       └─git annex webapp
-    │           └─git-annex webapp
-    │               ├─git --git-dir=/home/xyem/tmp/annex/.git --work-tree=/home/xyem/tmp/annex cat-file --batch
-    │               ├─git --git-dir=/home/xyem/tmp/annex/.git --work-tree=/home/xyem/tmp/annex cat-file --batch
-    │               ├─git --git-dir=/home/xyem/tmp/annex/.git --work-tree=/home/xyem/tmp/annex check-attr -z --stdin annex.backend annex.numcopies --
-    │               ├─git --git-dir=/home/xyem/tmp/annex/.git --work-tree=/home/xyem/tmp/annex commit --allow-empty-message -m  --quiet --no-verify
-    │               │   └─nano .git/COMMIT_EDITMSG
-    │               └─6*[{git-annex}]
-
-If I do the steps manually, it seems to work fine:
-
-    $ echo \"testfile\" > testfile.txt
-    $ git annex add testfile.txt
-
-    add testfile.txt (checksum...) ok
-    (Recording state in git...)
-
-    $ git --git-dir=/home/xyem/tmp/annex/.git --work-tree=/home/xyem/tmp/annex commit --allow-empty-message -m  --quiet --no-verify
-
-    [master 636605f] --quiet
-     1 file changed, 1 insertion(+)
-     create mode 120000 testfile.txt
-
-This, to me, implies it is a bug with the assistant/webapp but I don't know how to isolate it any more than that (--debug doesn't output anything else). Should I report this as another bug?
-"""]]
diff --git a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_3_af83717bfb260bea6d52ff71c6b34743._comment b/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_3_af83717bfb260bea6d52ff71c6b34743._comment
deleted file mode 100644
index 10216b5cc..000000000
--- a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_3_af83717bfb260bea6d52ff71c6b34743._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 3"
- date="2013-04-13T22:02:09Z"
- content="""
-Just noticed (while trying to commit in another annex) that the command I used above in the \"manual\" one commits with the message \"--quiet\". I guess pstree doesn't show all arguments!
-"""]]
diff --git a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_4_b4f811611d14e7392009c539fa6b8574._comment b/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_4_b4f811611d14e7392009c539fa6b8574._comment
deleted file mode 100644
index 6ff6b3c16..000000000
--- a/doc/bugs/assistant_ignores___34__manual__34___group__44___tries_to_transfer_files/comment_4_b4f811611d14e7392009c539fa6b8574._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 4"
- date="2013-04-16T20:28:44Z"
- content="""
-There's an open bug about this weird commit editor problem. Please follow up there: [[assistant_hangs_during_commit]]
-"""]]
diff --git a/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts.mdwn b/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts.mdwn
deleted file mode 100644
index 90034f7f5..000000000
--- a/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-What steps will reproduce the problem?
-
-Using the Linux tarball (i386) with configured IPv6:
-
-* git-annex.linux/git-annex-webapp
-
-A browser is then started, pointing to file:///tmp/webapp313.html which in turn points to http://localhost:$port/$blah .
-
-On my box localhost resolves to ::1, but the webapp is only listening on 127.0.0.1 so . While I can work around this by specifying 127.0.0.1 as the hostname, the next page that is loaded goes back to localhost. 
-
-What is the expected output? What do you see instead?
-
-I would expect that the webapp would bind to ::1 if possible.
-
-What version of git-annex are you using? On what operating system?
-
-3.20130102 fromt the Linux tarball release on Debian Squeeze.
-
-Please provide any additional information below.
-
-I've tested this with:
-
-* epiphany
-* iceweasel
-* chromium
-
-Iceweasel is the only one which correctly fell back to IPv4 and worked.
-
-> Ok, I've made it use the IP address in the URL. Ugly, but avoids
-> whatever mess results in this behavior. [[done]] --[[Joey]]
diff --git a/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_1_91a62a2ce14a1027d2ac8b8e88df5f0c._comment b/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_1_91a62a2ce14a1027d2ac8b8e88df5f0c._comment
deleted file mode 100644
index 540e06ee3..000000000
--- a/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_1_91a62a2ce14a1027d2ac8b8e88df5f0c._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.1.42"
- subject="comment 1"
- date="2013-01-09T23:21:58Z"
- content="""
-I have a ipv6 enabled computer here, where the webapp works fine. I think you must have something odd in your network configuration if web browsers, when sent to \"http://localhost:port/ don't manage to connect to a web server running on ipv4.
-
-The webapp only uses 127.0.0.1 if \"localhost\" resolves to that address. If \"localhost\" resolves to both ipv6 and ipv4 addresses, the webapp uses the ipv4 and not the ipv6 address. If \"localhost\" resolves to only ipv6, the webapp uses ipv6.
-
-AFAIK it's not possible to bind to both an ipv4 and an ipv6 address, and get the same port number for both, and the webapp needs a port number to use to launch the web browser. Therefore, it has to choose one address. It choses ipv4 in preference to ipv6 because there are some things that still don't support ipv6. [This commit](http://source.git-annex.branchable.com/?p=source.git;a=commit;h=467844d7d3f703f99fcde1f951f33efda5e90074) is relevant.
-"""]]
diff --git a/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_2_4982cd373eaaeee180be03c6e9fda7b1._comment b/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_2_4982cd373eaaeee180be03c6e9fda7b1._comment
deleted file mode 100644
index 849bde6e4..000000000
--- a/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_2_4982cd373eaaeee180be03c6e9fda7b1._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkF8_uQjLYm5Mf5F_JuVW-BxlvzpWjvR_o"
- nickname="Andrew"
- subject="comment 2"
- date="2013-01-09T23:51:18Z"
- content="""
-Watching tcpdump on loopback I only see a request from Epiphany to ::1, after that it gives up.  So not terribly helpful.
-
-It looks like it might be a bug in the browsers. :(
-"""]]
diff --git a/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_3_85d264e311acaa91dac0597ee8deda82._comment b/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_3_85d264e311acaa91dac0597ee8deda82._comment
deleted file mode 100644
index 91da74efc..000000000
--- a/doc/bugs/assistant_listens_on_127.0.0.1_not_::1_which_breaks_IPv6_enabled_hosts/comment_3_85d264e311acaa91dac0597ee8deda82._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkF8_uQjLYm5Mf5F_JuVW-BxlvzpWjvR_o"
- nickname="Andrew"
- subject="comment 3"
- date="2013-01-10T22:10:00Z"
- content="""
-Cool, thanks Joey. Let's hope we can remove the ugly hack one day. ;)
-"""]]
diff --git a/doc/bugs/assistant_on_windows_adding_remote_containing_linux_paths.mdwn b/doc/bugs/assistant_on_windows_adding_remote_containing_linux_paths.mdwn
deleted file mode 100644
index c6b6ee482..000000000
--- a/doc/bugs/assistant_on_windows_adding_remote_containing_linux_paths.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-### Please describe the problem.
-
-Internal Server Error
-
-internal error, /home/michele/assistannex is not absolute
-
-### What steps will reproduce the problem?
-
-create a transfer repository on a usb drive (from windows) merge it with a
-repository on linux, try to merge it on another target windows machine
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version 5.20140128-g29aea74
-
-> I'm not able to follow the steps to reproduce this, but I think 
-> I see what the problem is. `isAbsolute` on windows does not think that
-> unix-style path is absolute. Such a path can appear in a remote of a git
-> repository, particularly if part of that repository was set up on a
-> non-Windows system. While the remote won't be usable on Windows with a
-> path like that, git-annex should not choke on the path either.
-> I have fixed the code to deal with this.
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/authentication_to_rsync.net_fails.mdwn b/doc/bugs/authentication_to_rsync.net_fails.mdwn
deleted file mode 100644
index 707f93d49..000000000
--- a/doc/bugs/authentication_to_rsync.net_fails.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-### Please describe the problem.
-
-Used assistant to "Add a cloud repository".  Supplied hostname, username in webapp. Directory "annex" port 22.
-Clicked on "Use this rsync.net repository" and got
-
-**********************
-ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
-ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
-ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
-Received disconnect from 69.43.165.7: 2: Too many authentication failures for 2440
-**********************
-
-### What steps will reproduce the problem?
-See above?  A simple "ssh user@host.rsync.net ls /usr/bin" reveals that indeed no ssh-askpass is available in that namespace.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20130521 on debian linux 7.1.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-That log is empty.
-# End of transcript or log.
-"""]]
-
-> I added ssh-askpass as a recommends, so I suppose
-> I can close this. [[done]] --[[Joey]] 
diff --git a/doc/bugs/authentication_to_rsync.net_fails/comment_1_9db65f89415c8d825f268afb75244998._comment b/doc/bugs/authentication_to_rsync.net_fails/comment_1_9db65f89415c8d825f268afb75244998._comment
deleted file mode 100644
index 731d5148f..000000000
--- a/doc/bugs/authentication_to_rsync.net_fails/comment_1_9db65f89415c8d825f268afb75244998._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawliqfHEW134uawIUPwyKiyOdoF-oI5TxnQ"
- nickname="Ethan"
- subject="Doh.  /usr/bin/ssh-askpass needs to be on *local* machine."
- date="2013-08-15T20:13:31Z"
- content="""
-My mistake; the problem was the I was missing /usr/bin/ssh-askpass on my local machine, not the rsync.net host.
-
-I still think this is a bug.  I'm on a debian machine and installed git-annex from its debian package, so seems like the ssh-askpass package should be listed as a dependency.  But that's a debian packaging problem, not a git-annex bug per se, so I'll go file it elsewhere.
-"""]]
diff --git a/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn b/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn
deleted file mode 100644
index 122224a8f..000000000
--- a/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn
+++ /dev/null
@@ -1,72 +0,0 @@
-foo is a local repo, bar is a bare remote.
-
-I upgraded foo's git-annex to 0.20110325 and upgraded a local repo backend
-to version 2. I then ran `git annex copy . --to bar` and checked the
-remote. This created WORM:SHA512--123123 files in annex/objects.
-Understandable but unwanted. So I upgraded git-annex on bar's machine, as
-well.
-
-    % git annex copy . --to bar
-    copy quux (checking bar) git-annex-shell: Repository version 1 is not supported. Upgrade this repository: git-annex upgrade (to bar)
-    git-annex-shell: Repository version 1 is not supported. Upgrade this repository: git-annex upgrade
-    rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-    rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]
-    
-      rsync failed -- run git annex again to resume file transfer
-    failed
-
-Running `git annex upgrade` on bar's machine I get:
-
-    % git annex upgrade
-    upgrade  (v1 to v2) (moving content...) git-annex: Prelude.read: no parse
-
-Again, bar is a bare repo.
-Running the copy job again, I am still getting the same error as above (as expected). Partial contents of annex/objects on bar:
-
-    [...]
-    SHA512:123
-    WORM:SHA512--234
-    [...]
-
-
--- RichiH
-
-> Upgrading bare repos to v2 generally works fine, so I actually need
-> to see the full content of annex/, not a fragment, in order to debug this.
-> (Filename contents I don't need to see.) Feel free to email me the details at
-> joey@kitenet.net if you don't want to post them here. --[[Joey]]
-
->> Sent. -- RichiH
-
->>> Ok, I'm going to go work on my reading comprehension. I see now
->>> that you
->>> explained the problem pretty well. The problem is caused by these
->>> few weird v1 mixed with v2 keys in the annex.
->>> Ones like "annex/objects/WORM:SHA512--$sha512".
->>>
->>> That's a v1 key, but a corrupt form of the key; it's missing the 
->>> size and mtime fields that all WORM keys have in v1. And 
->>> the filename is itself a key, a v2 SHA512 key. These were
->>> created when you did the `git annex copy to the v1 bare repo.
->>> In v2, git-annex-shell takes a full key object, while in v1,
->>> it takes a key name and a backend name. This incompatability
->>> leads to the weird behavior seen.
->>>
->>> I had suggested you delete data.. don't. On second thought,
->>> you shouldn't delete anything. I'll simply make the v2 upgrade
->>> detect and work around this bug.
->>> --[[Joey]]
-
->>>> This should be fixed in current git. The scambled keys will be 
->>>> fixed up on upgrade. Thanks for your patience! [[done]] --[[Joey]]
-
->>>>> I should stop reading your answers via git; by the time I got to
->>>>> "second thoughts", I had already deleted the files & directories
->>>>> in question, upgraded the bare repo and was busy uploading from my
->>>>> local repo. I agree that taking care of this in the upgrade code
->>>>> is the cleanest approach, by the way.
->>>>> No need to thank me for my patience; thank you for your quickness!
->>>>> RichiH
->>>>> 
->>>>> PS: If I get a handle on the mtime issue in the SHA backend, git
->>>>> annex will be pretty much perfect :)
diff --git a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa.mdwn b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa.mdwn
deleted file mode 100644
index 87e937d42..000000000
--- a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-What steps will reproduce the problem?
-I was trying to pair two repositories on 2 different computers, 
-but my public key had this email address at the end:
-bachir@Bachirs-iMac.local
-
-What is the expected output? What do you see instead?
-I was expecting successful pairing.
-I got:
-bad comment in ssh public key ssh-rsa
-AAB3....SAK
-bachir@Bachirs-iMac.local
-
-What version of git-annex are you using? On what operating system?
-I am using the package git-annex  Version: 3.20120925 
-on MacOSX Lion
-
-Please provide any additional information below.
-I've checked your code, seems to complain about the dash '-' in the email address
-bachir@Bachirs-iMac.local
-
-> This bug is already fixed, the fix is in the 
-> 3.20121001 release. [[done]] --[[Joey]] 
diff --git a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_1_15cce6e6f455e83f4362a38c561bc973._comment b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_1_15cce6e6f455e83f4362a38c561bc973._comment
deleted file mode 100644
index 5f2dcca85..000000000
--- a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_1_15cce6e6f455e83f4362a38c561bc973._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://lorrin.myopenid.com/"
- nickname="Lorrin Nelson"
- subject="Still seeing this"
- date="2013-07-29T07:44:36Z"
- content="""
-Trying to pair Ubuntu 13.04 (git-annex 3.20121112ubuntu4) with OS X 10.7.5 (not sure where to see version info, but it was marked 2013-07-23 on the download page).
-
-If the pairing is initiated on OS X and the Ubuntu machine tries to connect, the Ubuntu browser shows:
-Internal Server Error
-
-bad comment in ssh public key ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCr0uArI+Yfusf+jICdv2tSCVQdydtoUuQixBHUGj2QlUlip4zf94HnCBBlSUhMuWBeaGUAAojp05Y3PaxQNS95bX1wWlhraQBx/8w23M68Q1L5Je60PWYha1dLREApJjl5eGxuTIXUip8UcDXIH/esB7G/lMihTjniEBqS430NxrfO01uU9HuNgQfO9zvTcJhjG+myek1GU2bx8GzYc7HAZ8VA3TsYKLaWA63w8WyFC/Hz+kunp9X8dNE11KpmNFVSk/j1QGImUOVcnGd2WupMyjLtRAKL3ikL6tBK2YccZUKPSNYek657CFR8uVek5czzQQCY5bFRAH3Pw9htsPgv user@host.fqdn
-
-Where user@host.fqdn is the user and DNS locally-resolvable host name of the Mac. However, this isn't a key I recognize. Is it generating a new one on the fly? There already are key pairs set up between the machines in my ~/.ssh directory; not sure if relevant.
-
-
-"""]]
diff --git a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_2_e9e1f38880a32610b3fbce475bffc3e4._comment b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_2_e9e1f38880a32610b3fbce475bffc3e4._comment
deleted file mode 100644
index 6028f49ed..000000000
--- a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_2_e9e1f38880a32610b3fbce475bffc3e4._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.21"
- subject="comment 2"
- date="2013-07-30T18:16:06Z"
- content="""
-Local pairing always sets up a dedicated ssh key that can only be used for git-annex syncing.
-
-I'm afraid that, unless your login is literally \"user@host.fqdn\", you've obfuscated exactly the information I'd need to diagnose the problem. If you don't feel comfortable including the real information here you can mail it to me; see [[privacy]]
-
-Also, you may want to file a new bug report, since I *did* fix and close this bug. You're probably seeing a slightly different bug.
-"""]]
diff --git a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_3_51da7f5881f65422328d341e5ab0d250._comment b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_3_51da7f5881f65422328d341e5ab0d250._comment
deleted file mode 100644
index 4cf86f646..000000000
--- a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_3_51da7f5881f65422328d341e5ab0d250._comment
+++ /dev/null
@@ -1,33 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlEhzszkzOIy8-Rx8b2mcr75QcnIc6O_OA"
- nickname="Rachel"
- subject="I'm afraid I'm getting this too"
- date="2013-09-12T12:48:04Z"
- content="""
-Very similar setup. Initially set up on a Mac, then tried to set up the first local pairing with a Linux system. Basically seeing exactly the same thing.
-
-    bad comment in ssh public key ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDa09lpmgLeRVF1KZn2gX6tmBH4Jpcou/rkPbhwLoFNLtQsdNrbjDKuyc4pDbUhexWVvub1YCLItLK0vYRdMvoJWjNzy926sHs8CxXFVg6PMQXw3wOHousSn0NkVfwUMNn5aS+1vz/WDlStmg7WzXgiPg1Whn6CKIomxA63rUMe3I+2nVkyO6jGlOkliPApVP2utURJbyxBDYDB+Ys7zUxvEcCekhxJO263myuo2gwI4A3mfTLRJMzbz8frRZJz5iuUIcOHaIDy6n0qKFq18BDux4SDwNjQ34yti5yqveRBMwFndHQYN6YHk1k26h0kyhb2T6lXaaAirSqa3dwfZuKp rachel@celestia.local
-
-
-# Versions and Stuff:
-
-## Mac:
-
-* OS X 10.8.4
-* git-annex 4.20130909-ga29f960 (downloaded about half an hour ago!)
-* BTW I have git installed from Homebrew, version 1.8.3.4 in my shell's $PATH, but obviously /usr/bin/git from the system is intact.
-* Hostname: celestia.local
-* Username: rachel
-
-## Linux:
-* Ubuntu 13.04
-* git-annex 3.20121112ubuntu4 (from Ubuntu's own repos)
-* I note that's later than the version you said this bug was fixed in, hence the report. :-)
-* Hostname: twilight.local (mDNS domain not appended even by hostname -f but avahi is working)
-* Username: rachel
-
-IPv6 is active, but I note a comment somewhere that that's probably not relevant for git-annex.
-
-Machines are very local to each other, in the same room, connected via a gigabit switch. They can definitely see each other. :-)
-
-"""]]
diff --git a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_4_ba384314c1e47ec4b72e1843e0500df9._comment b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_4_ba384314c1e47ec4b72e1843e0500df9._comment
deleted file mode 100644
index 4b9e27bba..000000000
--- a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_4_ba384314c1e47ec4b72e1843e0500df9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmpBDWko1yZmngBYzm_CeBv8RjoIMXaINE"
- nickname="Rachel"
- subject="latest works"
- date="2013-09-12T13:19:09Z"
- content="""
-Downloaded the latest tarball (4.20130911-g6625d0e) and that seems to be able to pair ok.
-
-Different bug though: It objects to push.default = simple in ~/.gitconfig, but no such complaint on osx. But that's a different bug; i'll report separately when I'm a bit more up to speed.
-"""]]
diff --git a/doc/bugs/bare_git_repos.mdwn b/doc/bugs/bare_git_repos.mdwn
deleted file mode 100644
index 5e9100acf..000000000
--- a/doc/bugs/bare_git_repos.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-It would be nice if git-annex could be used in bare git repos.
-However, that is not currently supported. Problems include:
-
-* git-annex often does not read a git repo's config before touching it,
-  so it doesn't know if the repo is bare or not
-  (reading the config when operating on ssh repos would be a pain and SLOW;
-  I had some of that code in as of 1aa19422ac8748eeff219ac4f46df166dae783c5,
-  but ripped it all out)
-* .. which results in creating `.git/annex` in a bare repo, which mightily
-  confuses git (so it will complain that the bare repo is not
-  a git repo at all!)
-* `.git-annex/` needs to have state recorded to it and committed, and that
-  is not possible with a bare repo. (If [[todo/branching]] were done,
-  that might be fixed.) (now fixed)
-
-----
-
-Update: Now that git-annex-shell is used for accessing remote repos,
-it would be possible to add smarts about bare repos there, and avoid
-some of the above problems. Probably only the state recording problem
-remains.
-
-A possible other approach to the state recording repo is to not
-record state changes on the remote in that case. Git-annex already
-records remote state changes locally whenever it modifies the state of a
-remote. --[[Joey]]
-
-> And... [[done]]! See [[/bare_repositories]] for current status
-> and gotchas. --[[Joey]] 
diff --git a/doc/bugs/bug_in_download_prebuilt_linux_tarball__44___and_constraints_issues_with_3.20121112.mdwn b/doc/bugs/bug_in_download_prebuilt_linux_tarball__44___and_constraints_issues_with_3.20121112.mdwn
deleted file mode 100644
index 4a942ec9e..000000000
--- a/doc/bugs/bug_in_download_prebuilt_linux_tarball__44___and_constraints_issues_with_3.20121112.mdwn
+++ /dev/null
@@ -1,45 +0,0 @@
-What steps will reproduce the problem?
-
-First issue:
-* The prebuilt tarball doesn't synchronize properly.
-
-Reproduce:
-* Download and untar tarball
-* Start gitannex webapp on multiple computers(i had three in use)
-* Synchronize with xmpp and an ssh server backend.
-* The tarball versions don't push/get from ssh server backend.
-
-Second issue:
-* I can't install git-annex on ubuntu 12.10(Works fine in debian unstable)
-* http://hpaste.org/77684
-
-Reproduce:
-* cabal update
-* cabal install --only-dependencies
-* cabal configure
-* cabal build
-* cabal install --bindir=$HOME/bin
-
-With these constraints the cabal install can work:
-* cabal install --only-dependencies ./ --constraint=certificate==1.2.2 --constraint=crypto-pubkey-types==0.1.1
-
-What is the expected output? What do you see instead?
-* Tarball version doesn't push to ssh backend.
-* cabal install git-annex gives http://hpaste.org/77684
-
-What version of git-annex are you using? On what operating system?
-* git-annex 3.20121112 on debian unstale (working)
-* ubuntu 12.10(failing)
-
-Please provide any additional information below.
-
-With these constraints the cabal install can work:
-* cabal install --only-dependencies ./ --constraint=certificate==1.2.2 --constraint=crypto-pubkey-types==0.1.1
-
-NOTE:
-I couldn't get the markdown to cooperate, so using pl pagetype.
-
-> I suspect this is [[done]]..
-> 
-> I fixed some bugs in the prebuilt tarball in the past 2 days that prevented it
-> from transferring files.
diff --git a/doc/bugs/bug_system_updates_when___34__done__34__.mdwn b/doc/bugs/bug_system_updates_when___34__done__34__.mdwn
deleted file mode 100644
index babb6dd0f..000000000
--- a/doc/bugs/bug_system_updates_when___34__done__34__.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-### Please describe the problem.
-
-In lieu of a better place to ask/report this.  Is it possible to have an email sent when bugs are moved into another category?  I get emails on comments but not much when the bugs are moved elsewhere - they just seem to disappear.
-
-### What steps will reproduce the problem?
-
-
-### What version of git-annex are you using? On what operating system?
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> That's because I add a [[done]] to close bugs, not a comment and you are
-> only subscribed to comments. It's possible to subscribe to changes to
-> pages, but ikiwiki does not make this easy. You should file a bug on
-> ikiwiki. --[[Joey]]
diff --git a/doc/bugs/build_is_broken_at_commit_cc0e5b7.mdwn b/doc/bugs/build_is_broken_at_commit_cc0e5b7.mdwn
deleted file mode 100644
index 43074915f..000000000
--- a/doc/bugs/build_is_broken_at_commit_cc0e5b7.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-the build is currently borked with
-
-<pre>
-ghc -O2 -threaded -Wall -ignore-package monads-fd -ignore-package monads-tf -outputdir tmp -IUtility -DWITH_ASSISTANT -DWITH_S3 -DWITH_WEBAPP -DWITH_PAIRING -DWITH_KQUEUE -DOSX --make git-annex -o tmp/git-annex Utility/libdiskfree.o Utility/libmounts.o Utility/libkqueue.o
-Assistant/Install.hs:19:8:
-Could not find module `Utility'
-Use -v to see a list of the files searched for.
-make: *** [git-annex] Error 1
-</pre>
-
-This was first introduced at commit e88e3ba
-
-> oops, -DOSX is not a good idea. [[done]] --[[Joey]] 
diff --git a/doc/bugs/build_issue_with_latest_release_0.20110522-1-gde817ba.mdwn b/doc/bugs/build_issue_with_latest_release_0.20110522-1-gde817ba.mdwn
deleted file mode 100644
index a7bae50b8..000000000
--- a/doc/bugs/build_issue_with_latest_release_0.20110522-1-gde817ba.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-A recent checkout of git-annex fails to build for me (I've installed the new dependancies as well)
-
-<pre>
-[70 of 81] Compiling Command.DropUnused ( Command/DropUnused.hs, Command/DropUnused.o )
-[71 of 81] Compiling Command.Status   ( Command/Status.hs, Command/Status.o )
-
-Command/Status.hs:133:37: Not in scope: `swap'
-make: *** [git-annex] Error 1
-</pre>
-
-it fails on OSX 10.6.x with ghc 6.12.3 and a corresponding haskell-platform install. I ran a bisect and found that commit 75a3f5027f74565d909fb940893636d081d9872a seems to have broken git-annex for me, reverting the commit allows me to build git-annex, I have not run the tests to verify everything is working correctly though.
-
-> Probably `swap` appeared only in a newer GHC. I've reverted to avoid a
-> versioned build dependency. [[done]] --[[Joey]]
diff --git a/doc/bugs/build_problem_on_OSX.mdwn b/doc/bugs/build_problem_on_OSX.mdwn
deleted file mode 100644
index e859a1150..000000000
--- a/doc/bugs/build_problem_on_OSX.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-I just squelched a bunch of build issues (to do with dependancies) on my autobuilder for OSX, this is currently happening
-
-<pre>
-install -d tmp
-ghc -O2 -Wall -outputdir tmp -IUtility  -DWITH_ASSISTANT -DWITH_S3 -DWITH_WEBAPP -DWITH_PAIRING -DWITH_XMPP -DWITH_DNS -DWITH_KQUEUE -threaded --make git-annex -o tmp/git-annex Utility/libdiskfree.o Utility/libmounts.o Utility/libkqueue.o
-
-Assistant/Threads/NetWatcher.hs:29:0:
-     warning: #warning Building without dbus support; will poll for network connection changes
-
-Assistant/Threads/MountWatcher.hs:36:0:
-     warning: #warning Building without dbus support; will use mtab polling
-[ 29 of 259] Compiling Utility.OSX      ( Utility/OSX.hs, tmp/Utility/OSX.o )
-
-Utility/OSX.hs:22:17: Not in scope: `myHomeDir'
-make: *** [git-annex] Error 1
-</pre>
-
-> Someone else reported that too; I fixed it. [[done]] --[[Joey]] 
diff --git a/doc/bugs/building_on_lenny.mdwn b/doc/bugs/building_on_lenny.mdwn
deleted file mode 100644
index 48386bde4..000000000
--- a/doc/bugs/building_on_lenny.mdwn
+++ /dev/null
@@ -1,80 +0,0 @@
-hi,
-
-I am trying to build git annex on lenny.
-
-I checked out the latest from git c88d4939453845efee04da811d64aa41046f9c11,
-installed all the packages (some from backports) as required by dpkg-buildpackage
-
-Then I get this:
-
-	...
-	mkdir -p build
-	ghc -odir build -hidir build --make git-annex
-	[ 1 of 19] Compiling Utility          ( Utility.hs, build/Utility.o )
-	[ 2 of 19] Compiling GitRepo          ( GitRepo.hs, build/GitRepo.o )
-	[ 3 of 19] Compiling GitQueue         ( GitQueue.hs, build/GitQueue.o )
-	[ 4 of 19] Compiling TypeInternals    ( TypeInternals.hs, build/TypeInternals.o )
-	[ 5 of 19] Compiling Types            ( Types.hs, build/Types.o )
-	[ 6 of 19] Compiling Annex            ( Annex.hs, build/Annex.o )
-	[ 7 of 19] Compiling Locations        ( Locations.hs, build/Locations.o )
-	[ 8 of 19] Compiling UUID             ( UUID.hs, build/UUID.o )
-	[ 9 of 19] Compiling LocationLog      ( LocationLog.hs, build/LocationLog.o )
-	[10 of 19] Compiling Core             ( Core.hs, build/Core.o )
-	[11 of 19] Compiling Backend.URL      ( Backend/URL.hs, build/Backend/URL.o )
-	[12 of 19] Compiling Backend          ( Backend.hs, build/Backend.o )
-
-	Backend.hs:114:50:
-	    Not in scope: type constructor or class `SomeException'
-	make[1]: *** [git-annex] Error 1
-	make[1]: Leaving directory `/home/cstamas/tmp/git-annex'
-	dh_auto_build: make -j1 returned exit code 2
-	make: *** [build] Error 2
-	dpkg-buildpackage: failure: debian/rules build gave error exit status 2
-
-I will try to check the mentioned file for error, but I do not know how to program in haskell.
-
-Thanks for your help! --[[cstamas]]
-
-> Newer versions of ghc changed their exception handling types, and
-> I coded git-annex to use the new style and not the old. gch6 6.12 will
-> work. I do not think there is a backport available though. --[[Joey]]
->
-> Ok, found and deployed a workaround. It is not tested. Let me know how it
-> works for you. --[[Joey]]
-
->> I did a git pull and now I get:
-
-	mkdir -p build
-	ghc -cpp -odir build -hidir build --make git-annex
-	[ 1 of 20] Compiling Portability      ( Portability.hs, build/Portability.o )
-
-	Portability.hs:13:21:
-	    Not in scope: type constructor or class `Exception'
-	make[1]: *** [git-annex] Error 1
-	make[1]: Leaving directory `/home/cstamas/tmp/git-annex'
-	dh_auto_build: make -j1 returned exit code 2
-	make: *** [build] Error 2
-	dpkg-buildpackage: failure: debian/rules build gave error exit status 2
-
->> --[[cstamas]]
-
->>> Ok well, I'm not going to try to reimplement all of
->>> Control.Exception.Extensible so I've made it use it. You will have to
->>> figure out how to install that library yourself though, I don't know
->>> how to use cabal with such an old ghc. Library is here:
->>> <http://hackage.haskell.org/package/extensible-exceptions> 
->>> and I asked how to get it on stable here:
->>> <http://ask.debian.net/questions/how-to-get-haskell-extensible-extceptions-on-stable> --[[Joey]] 
-
->>>> I made some effort with cabal on lenny. I can install (and I did it) cabal
->>>> from squeeze as dependencies are ok. Then I installed extensible
->>>> exceptions, but it places it in some local dir that git-annex's installer
->>>> (or ghc itself) does not know about.
->>>>
->>>> Later I realized that *only* for the compilation ghc6 and its friends are
->>>> needed. So I built the package on my other machine running squeeze. Then
->>>> resulting deb packages cleanly installs on lenny
->>>> 
->>>> For me this is OK. Thanks! --[[cstamas]]
-
-[[done]]
diff --git a/doc/bugs/bup_initremote_failed_with_localhost_+_username.mdwn b/doc/bugs/bup_initremote_failed_with_localhost_+_username.mdwn
deleted file mode 100644
index c15de5b3e..000000000
--- a/doc/bugs/bup_initremote_failed_with_localhost_+_username.mdwn
+++ /dev/null
@@ -1,49 +0,0 @@
-### Please describe the problem.
-Attempted to create a bup remote on the current system via ssh. It appears to have created the bup remote fine, but fails when sshing to it and does not add the remote.
-This is a normal indirect annex (currently containing a single test jpg in its root)
-I'm presuming the error is "(storing uuid...) sh: 1: cd: can't cd to /~/archie" 
-
-
-### What steps will reproduce the problem?
-git annex initremote bup type=bup encryption=none buprepo=sshservername:path
-
-I've tried using .ssh/config to remove the username from the servername passed to bup repo and it still fails.
-
-### What version of git-annex are you using? On what operating system?
-[[!format sh """
->git-annex version
-git-annex version: 4.20130615-g29d5bb9
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-"""]]
-debian wheezy i686
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-> git annex initremote bup type=bup encryption=none buprepo=bup@localhost:archie
-initremote bup (bup init...)
-Reinitialized existing Git repository in /media/backup/home/archie/.bup/
-Initialized empty Git repository in /media/backup/bup/archie/
-(storing uuid...) sh: 1: cd: can't cd to /~/archie
-git-annex: ssh failed
-
-> ssh bup@localhost
-Last login: Mon Jun 17 10:35:45 2013 from localhost
-$ ls
-archie
-$ cd archie
-$ ls
-branches  config  description  HEAD  hooks  info  objects  refs
-
-
-# End of transcript or log.
-"""]]
-
-> applied patchm, [[done]] --[[Joey]]
diff --git a/doc/bugs/bup_initremote_failed_with_localhost_+_username/comment_1_0e669c3039b089fa8a815d3ec11465d2._comment b/doc/bugs/bup_initremote_failed_with_localhost_+_username/comment_1_0e669c3039b089fa8a815d3ec11465d2._comment
deleted file mode 100644
index b8bfb0c04..000000000
--- a/doc/bugs/bup_initremote_failed_with_localhost_+_username/comment_1_0e669c3039b089fa8a815d3ec11465d2._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnrFnHRRNUQBB5RCDaIwhVmCcxQp8_yiYw"
- nickname="Oliver"
- subject="figured it out."
- date="2013-06-19T14:21:08Z"
- content="""
-It's failing because I am passing a relative url as buprepo - bup is expanding 
-
- host:dir
-
-to 
-
- ssh://host/~/dir
-
-but then onBupRemote isn't converting it back quite right.
-
-My haskell is rather rusty, but I have a working, if perhaps suboptimal patch; I'll email it across.
-
-
-"""]]
diff --git a/doc/bugs/cabal_build:___34__Could_not_find_module___96__Data.AssocList__39____34__.mdwn b/doc/bugs/cabal_build:___34__Could_not_find_module___96__Data.AssocList__39____34__.mdwn
deleted file mode 100644
index a23930bd7..000000000
--- a/doc/bugs/cabal_build:___34__Could_not_find_module___96__Data.AssocList__39____34__.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-What steps will reproduce the problem?
-
-Download current git head (fa5100d) and run cabal update; cabal install --only-dependencies; cabal configure; cabal build
-
-What is the expected output? What do you see instead?
-
-Expect succcessful build, get:
-
-Assistant/Install.hs:24:8:
-    Could not find module `Data.AssocList'
-    It is a member of the hidden package `hxt-9.3.1.1'.
-    Perhaps you need to add `hxt' to the build-depends in your .cabal file.
-    Use -v to see a list of the files searched for.
-
-
-What version of git-annex are you using? On what operating system?
-
-building using cabal from clone of git clone git://git-annex.branchable.com/, commit fa5100d (same problem happens with last release, 3.20121127).  On OS X, "Lion".
-
-
-Please provide any additional information below.
-
-> [[done]], using Data.List instead now.
diff --git a/doc/bugs/cabal_build:___34__Could_not_find_module___96__Data.AssocList__39____34__/comment_1_0da9fd67c3cc01b316f95a1df4eb62ae._comment b/doc/bugs/cabal_build:___34__Could_not_find_module___96__Data.AssocList__39____34__/comment_1_0da9fd67c3cc01b316f95a1df4eb62ae._comment
deleted file mode 100644
index 967e203c1..000000000
--- a/doc/bugs/cabal_build:___34__Could_not_find_module___96__Data.AssocList__39____34__/comment_1_0da9fd67c3cc01b316f95a1df4eb62ae._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="Could not find module `Data.AssocList' confirmed fixed."
- date="2012-11-28T03:38:19Z"
- content="""
-builds fine now, thank you!
-"""]]
diff --git a/doc/bugs/cabal_configure_is_broken_on_OSX_builds.mdwn b/doc/bugs/cabal_configure_is_broken_on_OSX_builds.mdwn
deleted file mode 100644
index ddbbcb874..000000000
--- a/doc/bugs/cabal_configure_is_broken_on_OSX_builds.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-Seems the last few commits have borked 'cabal configure' on OSX with the following error message
-
-<pre>
-[jtang@laplace git-annex (master)]$ cabal configure 
-Resolving dependencies...
-
-Build/InstallDesktopFile.hs:19:8:
-    Could not find module `Assistant.OSX'
-    Use -v to see a list of the files searched for.
-</pre>
-
-Looks like a missing module.
-
-> Was broken everywhere really, so I fixed it. [[done]] --[[Joey]] 
diff --git a/doc/bugs/cabal_install_fails_to_install_manpage.mdwn b/doc/bugs/cabal_install_fails_to_install_manpage.mdwn
deleted file mode 100644
index 265ad2432..000000000
--- a/doc/bugs/cabal_install_fails_to_install_manpage.mdwn
+++ /dev/null
@@ -1,43 +0,0 @@
-### Please describe the problem.
-
-The git-annex manual page is not installed when using [[install/cabal]] to install git-annex.
-
-### What steps will reproduce the problem?
-
-Follow [[install/cabal]] with `--bin-dir=/usr/local` and try `man git-annex`.
-
-I was expecting the manpage to be installed in `/usr/local/share/man`.
-
-### What version of git-annex are you using? On what operating system?
-
-git annex from a recent git build (4.20130909-g7f079d6) in Debian wheezy.
-
-### Please provide any additional information below.
-
-<del>This could be just a documentation problem...</del> Actually, the manpage can be read directly from the source tree in `doc/git-annex.mdwn`, but I still think it should be installed, for [[!wikipedia POLA]]'s sake. --[[anarcat]]
-
-I figured it out - that stuff is in the makefile, I updated [[install/cabal]] accordingly, so <del>done</del> - not done just yet. --[[anarcat]]
-
-> Doesn't seem right to me; Setup.hs has some stuff to do with
-> installing man pages. This does currently require that they 
-> are distributed in pre-built form in the .tar.gz on hackage, 
-> which I've just checked and they are.
-> 
-> Perhaps cabal put the man pages somewhere else? After all, you 
-> apparently did not set --datadir --[[Joey]] 
-
-> > True, I didn't - the docs didn't say to. ;) But really, it's one of two things, either Setup.hs can install manpages, and then the Makefile shouldn't install it, or we should update documentation to use the makefile only. I'll try this again next time I reinstall through cabal i guess... -- [[anarcat]]a
-
->>> The default location cabal installs man pages to is
->>> `~/.cabal/share/man/man1`. That is insane, but it is not as
->>> insane as not installing programs into PATH, which is why
->>> the documentation tells how to set --bindir to fix that particular
->>> cabal insanity. (Also, many systems don't have a good per-user
->>> man directory anyway.)
->>>
->>> `make install` does not use `cabal install` because as noted, cabal
->>> install is thurougly bat shit crazy. Not all systems that have
->>> cabal have make, which is why the cabal documentation is the way it is.
->>> --[[Joey]]
-
-[[done]]
diff --git a/doc/bugs/cabal_install_on_Ubuntu_12.04_fails_with_complaint_about_regex-base.mdwn b/doc/bugs/cabal_install_on_Ubuntu_12.04_fails_with_complaint_about_regex-base.mdwn
deleted file mode 100644
index b84d930b4..000000000
--- a/doc/bugs/cabal_install_on_Ubuntu_12.04_fails_with_complaint_about_regex-base.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-## What steps will reproduce the problem?
-
-I attempt
-
-      cabal install git-annex
-
-(already having installed `c2hs`)
-
-## What is the expected output? What do you see instead?
-
-I get
-
-        $ cabal install git-annex
-        Resolving dependencies...
-        cabal: Could not resolve dependencies:
-        trying: git-annex-3.20130216.1 (user goal)
-        trying: git-annex-3.20130216.1:+webapp
-        trying: git-annex-3.20130216.1:+assistant
-        trying: yesod-1.1.9 (dependency of git-annex-3.20130216.1:+assistant)
-        trying: http-conduit-1.9.0 (dependency of yesod-1.1.9)
-        trying: regex-compat-0.95.1/installed-851... (dependency of
-        http-conduit-1.9.0)
-        next goal: regex-base (dependency of regex-compat-0.95.1/installed-851...)
-        rejecting: regex-base-0.93.2/installed-999... (conflict: regex-base =>
-        mtl==2.0.1.0/installed-db1..., git-annex => mtl(>=2.1.1))
-        rejecting: regex-base-0.93.2, 0.93.1, 0.93, 0.92, 0.91, 0.90, 0.83, 0.72.0.2,
-        0.72.0.1, 0.71 (conflict: regex-compat => regex-base==0.93.2/installed-999...)
-
-> This is a transient version skew in cabal, generally
-> known as "cabal hell". It will be fixed when the libraries
-> involved fix their versioned dependencies, which may have
-> already happened. Precompiled builds of git-annex are provided
-> so I do not have to chase every transient version skew
-> that occurs for every use who runs into it. [[done]] --[[Joey]] 
diff --git a/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository.mdwn b/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository.mdwn
deleted file mode 100644
index 2a2832da3..000000000
--- a/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository.mdwn
+++ /dev/null
@@ -1,208 +0,0 @@
-What steps will reproduce the problem?
-
-Since syncing of non-git-annex repositories was enabled (thanks!), I see error messages
-
-    conq: invalid command syntax.
-
-in the output of git annex sync (and in the logs of the webapp), which I am fairly sure is an error from bitbucket, which I am using as the centralised repository. I know a similar thing has been reported before ([[conq:_invalid_command_syntax]]), but I really don't know how to tackle this. I have included the output from git annex sync --debug, and the ssh command which is causing this, at the end.
-
-If I strip out all the options from the ssh command, I get the same error. I don't know if this is some peculiarity from bitbucket, or a more general issue.
-
-
-Also, I don't know if this is even a problem. The syncing does seem to work properly.
-
-
---Walter
-
-**edit** I have tried with another centralised annex-less git server, and the behaviour is better (more logs below). It realises that it doesn't have annex, modifies .git/config, and then afterwards doesn't try to run the problematic command. So, my first guess is that it isn't correctly determining that that command failed in some cases?
-
-
-What version of git-annex are you using? On what operating system?
-
-4.20130423-ge0f5abb, Ubuntu 12.10
-
-Please provide any additional information below.
-
-
-[[!format sh """
-~/annex$ git annex sync --debug
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","symbolic-ref","HEAD"]
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","refs/heads/master"]
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","git-annex"]
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..44700457a651992eb40ff67a148d77217e8aa1d7","--oneline","-n1"]
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..94392bcdad74257adaadb98ce85d17a83da7648c","--oneline","-n1"]
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..ff126032854d9ead0a096acae04f105628de0cc4","--oneline","-n1"]
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..62da8e99021b72a9255064385a75c5fe643e3711","--oneline","-n1"]
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..00cca957c30882c9dfaf494101251e4c634baa31","--oneline","-n1"]
-[2013-04-24 10:21:39 NZST] chat: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","cat-file","--batch"]
-[2013-04-24 10:21:39 NZST] read: git ["config","--null","--list"]
-[2013-04-24 10:21:39 NZST] read: ssh ["-S","/home/walter/annex/.git/annex/ssh/git@bitbucket.org","-o","ControlMaster=auto","-o","ControlPersist=yes","-T","git@bitbucket.org","git-annex-shell 'configlist' '/~/waltersom/annex.git'"]
-conq: invalid command syntax.
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","ls-files","--others","--exclude-standard","--stage","-z","--","/home/walter/annex"]
-commit  
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","commit","-m","git-annex automatic sync"]
-ok
-[2013-04-24 10:21:39 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/heads/synced/master"]
-[2013-04-24 10:21:39 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/master..refs/heads/synced/master","--oneline","-n1"]
-pull bitbucket 
-[2013-04-24 10:21:39 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","fetch","bitbucket"]
-[2013-04-24 10:21:43 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/bitbucket/master"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/master..refs/remotes/bitbucket/master","--oneline","-n1"]
-[2013-04-24 10:21:43 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/bitbucket/synced/master"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/synced/master..refs/remotes/bitbucket/synced/master","--oneline","-n1"]
-ok
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","git-annex"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..44700457a651992eb40ff67a148d77217e8aa1d7","--oneline","-n1"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..94392bcdad74257adaadb98ce85d17a83da7648c","--oneline","-n1"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..ff126032854d9ead0a096acae04f105628de0cc4","--oneline","-n1"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..62da8e99021b72a9255064385a75c5fe643e3711","--oneline","-n1"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..00cca957c30882c9dfaf494101251e4c634baa31","--oneline","-n1"]
-[2013-04-24 10:21:43 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","branch","-f","synced/master"]
-[2013-04-24 10:21:43 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/bitbucket/synced/master"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/remotes/bitbucket/synced/master..refs/heads/synced/master","--oneline","-n1"]
-[2013-04-24 10:21:43 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/bitbucket/git-annex"]
-[2013-04-24 10:21:43 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/remotes/bitbucket/git-annex..git-annex","--oneline","-n1"]
-push bitbucket 
-[2013-04-24 10:21:43 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","push","bitbucket","git-annex:synced/git-annex","master:synced/master"]
-Everything up-to-date
-ok
-"""]]
-
-
-[[!format sh """
-~/annex$ ssh -vvv -S /home/walter/annex/.git/annex/ssh/git@bitbucket.org -o ControlMaster=auto -o ControlPersist=yes -T git@bitbucket.org git-annex-shell 'configlist' '/~/waltersom/annex.git'
-OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012
-debug1: Reading configuration data /etc/ssh/ssh_config
-debug1: /etc/ssh/ssh_config line 19: Applying options for *
-debug1: auto-mux: Trying existing master
-debug2: fd 3 setting O_NONBLOCK
-debug2: mux_client_hello_exchange: master version 4
-debug3: mux_client_forwards: request forwardings: 0 local, 0 remote
-debug3: mux_client_request_session: entering
-debug3: mux_client_request_alive: entering
-debug3: mux_client_request_alive: done pid = 5213
-debug3: mux_client_request_session: session request sent
-debug1: mux_client_request_session: master session id: 2
-conq: invalid command syntax.
-debug3: mux_client_read_packet: read header failed: Broken pipe
-debug2: Received exit status from master 0
-"""]]
-
-
-Here is the output once I added another (non-bitbucket) repository, also without git-annex-shell
-
-[[!format sh """
-~/annex$ git annex sync --debug
-[2013-04-24 10:56:20 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","symbolic-ref","HEAD"]
-[2013-04-24 10:56:20 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","refs/heads/master"]
-[2013-04-24 10:56:20 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","git-annex"]
-[2013-04-24 10:56:20 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-24 10:56:20 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..44700457a651992eb40ff67a148d77217e8aa1d7","--oneline","-n1"]
-[2013-04-24 10:56:20 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..94392bcdad74257adaadb98ce85d17a83da7648c","--oneline","-n1"]
-[2013-04-24 10:56:20 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..ff126032854d9ead0a096acae04f105628de0cc4","--oneline","-n1"]
-[2013-04-24 10:56:20 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..62da8e99021b72a9255064385a75c5fe643e3711","--oneline","-n1"]
-[2013-04-24 10:56:20 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..00cca957c30882c9dfaf494101251e4c634baa31","--oneline","-n1"]
-[2013-04-24 10:56:20 NZST] chat: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","cat-file","--batch"]
-[2013-04-24 10:56:20 NZST] read: git ["config","--null","--list"]
-[2013-04-24 10:56:20 NZST] read: ssh ["-S","/home/walter/annex/.git/annex/ssh/waltersom_aaatos@ssh.phx.nearlyfreespeech.net","-o","ControlMaster=auto","-o","ControlPersist=yes","-T","waltersom_aaatos@ssh.phx.nearlyfreespeech.net","git-annex-shell 'configlist' '/home/protected/gitroot/test.git'"]
-waltersom_aaatos@ssh.phx.nearlyfreespeech.net's password: 
--bash: git-annex-shell: command not found
-[2013-04-24 10:56:25 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","fetch","--quiet","aaatos"]
-waltersom_aaatos@ssh.phx.nearlyfreespeech.net's password: 
-
-  Remote aaatos does not have git-annex installed; setting remote.aaatos.annex-ignore
-[2013-04-24 10:56:30 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","config","remote.aaatos.annex-ignore","true"]
-[2013-04-24 10:56:30 NZST] read: ssh ["-S","/home/walter/annex/.git/annex/ssh/git@bitbucket.org","-o","ControlMaster=auto","-o","ControlPersist=yes","-T","git@bitbucket.org","git-annex-shell 'configlist' '/~/waltersom/annex.git'"]
-conq: invalid command syntax.
-[2013-04-24 10:56:30 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","ls-files","--others","--exclude-standard","--stage","-z","--","/home/walter/annex"]
-commit  
-[2013-04-24 10:56:30 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","commit","-m","git-annex automatic sync"]
-ok
-[2013-04-24 10:56:30 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/heads/synced/master"]
-[2013-04-24 10:56:30 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/master..refs/heads/synced/master","--oneline","-n1"]
-pull bitbucket 
-[2013-04-24 10:56:30 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","fetch","bitbucket"]
-[2013-04-24 10:56:34 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/bitbucket/master"]
-[2013-04-24 10:56:34 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/master..refs/remotes/bitbucket/master","--oneline","-n1"]
-[2013-04-24 10:56:34 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/bitbucket/synced/master"]
-[2013-04-24 10:56:35 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/synced/master..refs/remotes/bitbucket/synced/master","--oneline","-n1"]
-ok
-pull aaatos 
-[2013-04-24 10:56:35 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","fetch","aaatos"]
-waltersom_aaatos@ssh.phx.nearlyfreespeech.net's password: 
-[2013-04-24 10:56:40 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/aaatos/master"]
-[2013-04-24 10:56:40 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/aaatos/synced/master"]
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/synced/master..refs/remotes/aaatos/synced/master","--oneline","-n1"]
-ok
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","git-annex"]
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..44700457a651992eb40ff67a148d77217e8aa1d7","--oneline","-n1"]
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..94392bcdad74257adaadb98ce85d17a83da7648c","--oneline","-n1"]
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..ff126032854d9ead0a096acae04f105628de0cc4","--oneline","-n1"]
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..62da8e99021b72a9255064385a75c5fe643e3711","--oneline","-n1"]
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/heads/git-annex..00cca957c30882c9dfaf494101251e4c634baa31","--oneline","-n1"]
-[2013-04-24 10:56:40 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","branch","-f","synced/master"]
-[2013-04-24 10:56:40 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/bitbucket/synced/master"]
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/remotes/bitbucket/synced/master..refs/heads/synced/master","--oneline","-n1"]
-[2013-04-24 10:56:40 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/bitbucket/git-annex"]
-[2013-04-24 10:56:40 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/remotes/bitbucket/git-annex..git-annex","--oneline","-n1"]
-push bitbucket 
-[2013-04-24 10:56:40 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","push","bitbucket","git-annex:synced/git-annex","master:synced/master"]
-Everything up-to-date
-ok
-[2013-04-24 10:56:44 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/aaatos/synced/master"]
-[2013-04-24 10:56:44 NZST] read: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","log","refs/remotes/aaatos/synced/master..refs/heads/synced/master","--oneline","-n1"]
-[2013-04-24 10:56:44 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","show-ref","--verify","-q","refs/remotes/aaatos/git-annex"]
-push aaatos 
-[2013-04-24 10:56:44 NZST] call: git ["--git-dir=/home/walter/annex/.git","--work-tree=/home/walter/annex","push","aaatos","git-annex:synced/git-annex","master:synced/master"]
-waltersom_aaatos@ssh.phx.nearlyfreespeech.net's password: 
-Counting objects: 1363, done.
-Delta compression using up to 8 threads.
-Compressing objects: 100% (604/604), done.
-Writing objects: 100% (1363/1363), 96.41 KiB, done.
-Total 1363 (delta 709), reused 898 (delta 467)
-To waltersom_aaatos@ssh.phx.nearlyfreespeech.net:/home/protected/gitroot/test.git
- * [new branch]      git-annex -> synced/git-annex
- * [new branch]      master -> synced/master
-ok
-[2013-04-24 10:56:50 NZST] read: ssh ["-O","stop","-S","/home/walter/annex/.git/annex/ssh/waltersom_aaatos@ssh.phx.nearlyfreespeech.net","-o","ControlMaster=auto","-o","ControlPersist=yes","waltersom_aaatos@ssh.phx.nearlyfreespeech.net"]
-"""]]
-
-
-Here is the contents of .git/config (the last line was added by git annex sync)
-[[!format sh """
-[core]
-	repositoryformatversion = 0
-	filemode = true
-	bare = false
-	logallrefupdates = true
-[annex]
-	uuid = ef94eb2c-ebce-4419-900b-937c88df9aa1
-	version = 3
-	direct = true
-	diskreserve = 1 gigabyte
-	numcopies = 1
-	autocommit = true
-[gc]
-	auto = 0
-[remote "S3Sydney"]
-	annex-s3 = true
-	annex-uuid = 004d3b86-43db-4d82-9dec-347bc1b86420
-[remote "327D522A6727FE79"]
-	url = /media/walter/327D522A6727FE79/annex
-	fetch = +refs/heads/*:refs/remotes/327D522A6727FE79/*
-	annex-uuid = c9fe9266-3581-4608-aa3c-9322afd9b533
-	annex-cost = 125.0
-	annex-sync = true
-[remote "bitbucket"]
-	url = git@bitbucket.org:waltersom/annex.git
-	fetch = +refs/heads/*:refs/remotes/bitbucket/*
-[remote "aaatos"]
-	url = waltersom_aaatos@ssh.phx.nearlyfreespeech.net:/home/protected/gitroot/test.git
-	fetch = +refs/heads/*:refs/remotes/aaatos/*
-	annex-ignore = true
-"""]]
-
-> Reproduced and fixed. [[done]] --[[Joey]] 
diff --git a/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_1_dd202a7764d9df998868d595a86ffb21._comment b/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_1_dd202a7764d9df998868d595a86ffb21._comment
deleted file mode 100644
index 50a133ac8..000000000
--- a/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_1_dd202a7764d9df998868d595a86ffb21._comment
+++ /dev/null
@@ -1,30 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="you win at highlighting logs!"
- date="2013-04-23T23:04:13Z"
- content="""
-This weird message is coming from whatever equivilant bitbucket has of a login shell.
-
-I'd expect you would only see the message once. When git-annex notices it cannot run git-annex-shell on the remote, it automatically sets `remote.bitbucket.annex-ignore`. Once that is set, it will not try again to send/receive files from the remote. But due to the recent change I made, will still git push/pull to it.
-
-I don't see anything unexpected in the logs.. What would be unexpected is if `remote.bitbucket.annex-ignore` is set, and it tries to do this again next time it syncs. Or if `remote.bitbucket.annex-ignore` is not set to true in `.git/config`.
-
-Here is an example of how it's supposed to work:
-
-<pre>
-joey@gnu:~/tmp/rr>git annex sync
-fatal: unrecognized command 'git-annex-shell 'configlist' '/~/test.git''
-
-  Remote origin does not have git-annex installed; setting remote.origin.annex-ignore
-commit  
-ok
-
-joey@gnu:~/tmp/rr>git config remote.origin.annex-ignore 
-true
-
-joey@gnu:~/tmp/rr>git annex sync
-commit  
-ok
-</pre>
-"""]]
diff --git a/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_2_ca065c82ac8e3215b581660f3e44f459._comment b/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_2_ca065c82ac8e3215b581660f3e44f459._comment
deleted file mode 100644
index c7d4ad7c3..000000000
--- a/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_2_ca065c82ac8e3215b581660f3e44f459._comment
+++ /dev/null
@@ -1,51 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ"
- nickname="Walter"
- subject=":'( no format directive in comments?"
- date="2013-04-23T23:13:02Z"
- content="""
-That's right; `git config remote.bitbucket.annex-ignore true` does fix the problem.
-
-So, I guess if you're looking for more things to do, there is somehow a problem detecting that git-annex-shell isn't present sometimes.
-
-
-    ~/annex$ git config remote.bitbucket.annex-ignore
-    ~/annex$ git annex sync
-    conq: invalid command syntax.
-    commit  
-    ok
-    pull bitbucket 
-    ok
-    push bitbucket 
-    Everything up-to-date
-    ok
-    ~/annex$ git annex sync
-    conq: invalid command syntax.
-    commit  
-    ok
-    pull bitbucket 
-    ok
-    push bitbucket 
-    Everything up-to-date
-    ok
-    ~/annex$ git annex sync
-    conq: invalid command syntax.
-    commit  
-    ok
-    pull bitbucket 
-    ok
-    push bitbucket 
-    Everything up-to-date
-    ok
-    ~/annex$ git config remote.bitbucket.annex-ignore true
-    ~/annex$ git annex sync
-    commit  
-    ok
-    pull bitbucket 
-    ok
-    push bitbucket 
-    Everything up-to-date
-    ok
-    
-
-"""]]
diff --git a/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_3_927a01f9961c71bedb42c519a31b5fe5._comment b/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_3_927a01f9961c71bedb42c519a31b5fe5._comment
deleted file mode 100644
index e565eaf7a..000000000
--- a/doc/bugs/call_to_git-annex-shell_when_on_centralised___40__non-git-annex__41___repository/comment_3_927a01f9961c71bedb42c519a31b5fe5._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-23T23:13:45Z"
- content="""
-I noticed this:
-
-> debug2: Received exit status from master 0
-
-So, bitbucket prints an error message.. and exits successfully. Durrrrrr....
-
-I'll put in a fix for this if I can. FWIW, the behavior is nothing to worry about; everything will work as-is, it'll just annoyingly keep trying to ask bitbucket to please identify its repository via git-annex-shell.
-"""]]
diff --git a/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode.mdwn b/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode.mdwn
deleted file mode 100644
index ca47d3a4c..000000000
--- a/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-### Please describe the problem.
-When trying to annex get *from* an annex on a Windows machine, over HTTP, annex get fails with 404 errors.
-
-### What steps will reproduce the problem?
-1. Create an annex on a Windows and Linux machine.
-2. annex add some content on Windows repository.
-3. Configure Windows repository for HTTP access
-4. on Linux machine, fetch updates. this succeeds.
-5. attempt to "annex get <new files>"
-6. requests for files of the format ".git/annex/objects/<3-char-hash>/<3-char-hash>/SHA<filehash>.<extension>" fail with 404 errors. the annex get fails.
-
-
-### What version of git-annex are you using? On what operating system?
-Windows 7: 4.20140627-g8a36ec5 (from the git-annex download page)
-
-Debian Linux: 3.20120629 (from the package manager)
-
-### Please provide any additional information below.
-there is no <filehash>.<extension> file in the relevant directories, there are only .map and .cache files. The Windows annex is in direct mode, and the Linux annex fails to annex get from this correctly.
-
-[[!meta title="can't use a direct mode repository as a http remote"]]
-
-> [[done]]; unsupported configuration. --[[Joey]] 
diff --git a/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode/comment_1_20c31a844d8351a99cf69e05d2836e0e._comment b/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode/comment_1_20c31a844d8351a99cf69e05d2836e0e._comment
deleted file mode 100644
index 17665bd70..000000000
--- a/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode/comment_1_20c31a844d8351a99cf69e05d2836e0e._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkxl76M-3zKZXFbFf6NY6c6y-78CSKGyJw"
- nickname="T"
- subject="comment 1"
- date="2013-07-06T20:11:54Z"
- content="""
-When I tried to duplicate these results today, it failed in a different fashion.
-
-adding a new file (file2.txt) to a test repo on windows, setting up an HTTP access, and fetching and merging onto linux leaves the following state:
-[[!format sh \"\"\"
-test-git-annex@linux_host:~/test_annex$ ls -l
-total 4
-lrwxrwxrwx 1 test-git-annex test-git-annex   <datetime> file1.txt -> this is some content?
-lrwxrwxrwx 1 test-git-annex test-git-annex   <datetime> file2.txt -> some new content, on a new annex
-\"\"\"]]
-
-it is treating the contents of the files as the name of a symlink. get annex get . is unable to retrieve them as contents.
-
-"""]]
diff --git a/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode/comment_2_f26e0f763f9027d9dfc08cd840ced153._comment b/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode/comment_2_f26e0f763f9027d9dfc08cd840ced153._comment
deleted file mode 100644
index 913f5304d..000000000
--- a/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode/comment_2_f26e0f763f9027d9dfc08cd840ced153._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.254.222"
- subject="comment 2"
- date="2013-07-07T17:43:49Z"
- content="""
-You generally cannot use a git-annex repository that is in direct mode as a remote over http. A remote git-annex does not have sufficient information to safely use a direct mode repository in that way. I don't think I can fix that. The http transport will work with indirect mode repositories (not supported on Windows), and with bare repositories (should work ok on Windows).
-
-I'm perplexed by what you show happening in the comment. It appears that the content of the files has been staged into the git repository as the symlink target on Windows. I have never seen that happen, cannot imagine how git-annex could do that. My best guess is you might have run `git commit -a` after `git annex add`, and on Windows, since it doesn't really have symlinks, that could leave the symlink bit set while staging the full content of the file. You should never run `git commit -a` in a direct mode repository (Windows always uses direct mode). See [[/direct_mode]] for caveats about git commands that are unsafe to run in direct mode.
-"""]]
diff --git a/doc/bugs/can__39__t_drop_unused_files_that_never_were_added.mdwn b/doc/bugs/can__39__t_drop_unused_files_that_never_were_added.mdwn
deleted file mode 100644
index 361f21f0e..000000000
--- a/doc/bugs/can__39__t_drop_unused_files_that_never_were_added.mdwn
+++ /dev/null
@@ -1,86 +0,0 @@
-### Please describe the problem.
-
-When adding files to the annex and then deciding against it in an "unusual" way, git-annex gets confused and the file left behind can't be removed from the annex...
-
-### What steps will reproduce the problem?
-
-1. Add file with "git annex add"
-2. Decide you don't need the file add all
-3. "git rm -f newfile"
-4. "git annex unused"
-5. "git annex dropunused all"
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 5.20140210 on Debian unstable
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-$ git init
-Initialized empty Git repository in /tmp/foo/.git/
-$ ls -l
-total 0
-$ cp ~/download/hub-ctrl.c .
-$ git add hub-ctrl.c
-$ git commit
-[master (root-commit) ed7eb68] A file.
- 1 file changed, 412 insertions(+)
- create mode 100644 hub-ctrl.c
-$ cp ~/download/hub-ctrl .
-$ ls -l
-total 28
--rwxr-xr-x 1 tobias tobias 14130 Feb 19 00:49 hub-ctrl
--rw-r--r-- 1 tobias tobias  9270 Feb 19 00:48 hub-ctrl.c
-$ git annex init
-init  ok
-(Recording state in git...)
-$ git annex add
-add hub-ctrl ok
-(Recording state in git...)
-$ git status
-On branch master
-Changes to be committed:
-  (use "git reset HEAD <file>..." to unstage)
-
-	new file:   hub-ctrl
-
-$ git rm hub-ctrl
-error: the following file has changes staged in the index:
-    hub-ctrl
-(use --cached to keep the file, or -f to force removal)
-$ git rm -f hub-ctrl
-rm 'hub-ctrl'
-$ git status
-On branch master
-nothing to commit, working directory clean
-$ git annex unused
-unused . (checking for unused data...) (checking HEAD...) 
-  Some annexed data is no longer used by any files:
-    NUMBER  KEY
-    1       SHA256E-s14130--d4e777ba2b99ed0a520fbabe7b93cf2165373b4945afe8dcb626231d9051f19d
-  (To see where data was previously used, try: git log --stat -S'KEY')
-  
-  To remove unwanted data: git-annex dropunused NUMBER
-  
-ok
-$ git annex dropunused all
-dropunused 1 (unsafe) 
-  Could only verify the existence of 0 out of 1 necessary copies
-
-  Rather than dropping this file, try using: git annex move
-
-  (Use --force to override this check, or adjust numcopies.)
-failed
-git-annex: dropunused: 1 failed
-$
-
-# End of transcript or log.
-"""]]
-
-> It seems to me that if you run `git annex dropunused --force`, it will
-> remove the file. This needing --force is a recent change; git-annex
-> tries to never posibly lose data unless forced. Dropping the last
-> copy of a file certianly qualifies. [[done]] --[[Joey]]
diff --git a/doc/bugs/can__39__t_run_the_assistant_from_the_command_line_anymore__63__.mdwn b/doc/bugs/can__39__t_run_the_assistant_from_the_command_line_anymore__63__.mdwn
deleted file mode 100644
index 58828e8ca..000000000
--- a/doc/bugs/can__39__t_run_the_assistant_from_the_command_line_anymore__63__.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-What steps will reproduce the problem?
-
-just compiled the latest version of git annex from git, checkout hash was c9c0042
-
-Tried running the assistant from the command line, got unexpected error
-
-What is the expected output? What do you see instead?
-
-Expected assistant to start, instead got:
-
-    annex$  git annex assistant
-    git-annex: watch mode is not available on this system
-
-
-What version of git-annex are you using? On what operating system?
-
-annex$  git annex version
-git-annex version: 3.20130103
-local repository version: 3
-default repository version: 3
-supported repository versions: 3
-upgrade supported from repository versions: 0 1 2
-annex$ 
-
-OS X Lion.
-
-
-Please provide any additional information below.
-
-> The cabal file had a typo that prevented it from using hfsevents. I'm
-> uploading a fix now. [[done]] --[[Joey]]
diff --git a/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax.mdwn b/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax.mdwn
deleted file mode 100644
index dfe2738ef..000000000
--- a/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-What steps will reproduce the problem?
-
-* Start the assistant
-* try to add a remote server (ssh) which is not on port 22. E.g. using myhost:1234
-* after a rather long time the connection fails
-
-
-What is the expected output? What do you see instead?
-
-it would be nice if this syntax was supported, or if an (optional) port field was provided.
-second best solution: inform the user that "myhost:1234" is not the expected format.
-third best solution (already in place) fail with "some error message".
-
-
-
-
-What version of git-annex are you using? On what operating system?
-
-3.20121016 on Ubuntu 12.04 (in future maybe also on home nas with wheezy)
-
-
-Please provide any additional information below.
-
-Thanks for a nice program and all your work on debian!
-this is not really a bug more of a wishlist feature.
-
-
-[[!tag /design/assistant]]
-
-> Ok, it has a port field now. [[done]] --[[Joey]] 
diff --git a/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax/comment_1_397eb359c3f8ef30460a9556b6f55848._comment b/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax/comment_1_397eb359c3f8ef30460a9556b6f55848._comment
deleted file mode 100644
index 991a7483d..000000000
--- a/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax/comment_1_397eb359c3f8ef30460a9556b6f55848._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 1"
- date="2012-11-09T14:04:57Z"
- content="""
-edit ~/.ssh/config. add
-
-    Host myhost
-    Port 1234
-
-
-now you never have to specify the port again(for ssh,scp,rsync,etc)
-"""]]
diff --git a/doc/bugs/cannot_add_file__44___get___34__user_error__34__.mdwn b/doc/bugs/cannot_add_file__44___get___34__user_error__34__.mdwn
deleted file mode 100644
index 398cda3b6..000000000
--- a/doc/bugs/cannot_add_file__44___get___34__user_error__34__.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-What steps will reproduce the problem?
-
-I can reproduce it locally:
-
-    % annex -d add Eigene\ Bilder/
-    [2013-03-19 15:44:01 CET] read: git ["--git-dir=/Users/fschulze/Bilder/.git","--work-tree=/Users/fschulze/Bilder","ls-files","--others","--exclude-standard","-z","--","Eigene Bilder/"]
-    [2013-03-19 15:44:01 CET] read: git ["--git-dir=/Users/fschulze/Bilder/.git","--work-tree=/Users/fschulze/Bilder","diff","--name-only","--diff-filter=T","-z","--","Eigene Bilder/"]
-    add Eigene Bilder/20070311/Bild023.jpg [2013-03-19 15:44:01 CET] chat: git ["--git-dir=/Users/fschulze/Bilder/.git","--work-tree=/Users/fschulze/Bilder","check-attr","-z","--    stdin","annex.backend","annex.numcopies","--"]
-    (checksum...) [2013-03-19 15:44:01 CET] read: sha512sum ["/Users/fschulze/Bilder/.git/annex/tmp/Bild02366551.jpg"]
-
-git-annex: user error (sha512sum ["/Users/fschulze/Bilder/.git/annex/tmp/Bild02366551.jpg"] exited 127)
-failed
-
-What is the expected output? What do you see instead?
-
-The file isn't added.
-
-What version of git-annex are you using? On what operating system?
-
-OS X from dmg
-
-    git-annex version: 4.20130314
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS
-
-> The OSX app is now changed so that git-annex is a wrapper
-> script using runshell. This allows putting `git-annex.app/Contents/MacOS`
-> into PATH and using git-annex, and it will find all the libraries and
-> utilities bundled with it. [[done]] --[[Joey]]
diff --git a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_1_14aa717c1befcbbf526f25ca2f0af825._comment b/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_1_14aa717c1befcbbf526f25ca2f0af825._comment
deleted file mode 100644
index 87855ab4b..000000000
--- a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_1_14aa717c1befcbbf526f25ca2f0af825._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-19T17:19:32Z"
- content="""
-What version of OSX is this? From what url did you download the dmg? 
-
-Have you run \"runshell\" to get the shell you're using git-annex in?
-
-What happens if you run sha512sum on the file yourself?
-
-The SHA512 backend is not the default backend used by git-annex. Is the default SHA256 backend working?
-"""]]
diff --git a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_2_7f7ac59e7f3dce9d7a7d0c3379c2edcf._comment b/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_2_7f7ac59e7f3dce9d7a7d0c3379c2edcf._comment
deleted file mode 100644
index 0e9b034c0..000000000
--- a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_2_7f7ac59e7f3dce9d7a7d0c3379c2edcf._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawla3gLc6_rHuggFfy7o7eGMPvPztFZTrUQ"
- nickname="Florian"
- subject="comment 2"
- date="2013-03-19T17:42:00Z"
- content="""
-OS X Lion 10.7.5
-http://downloads.kitenet.net/git-annex/OSX/current/10.7.5_Lion/git-annex.dmg.bz2
-
-What is \"runshell\"? I used the binary from inside the app, maybe that's the issue? How am I supposed to use it from the command line? I had used a 2012 version installed via cabal before, but upgrading it didn't work anymore. I got lot's of errors from various cabal packages when I tried.
-
-Directly it seems to work fine:
-
-% ~/Applications/git-annex.app/Contents/MacOS/sha512sum Eigene\ Bilder/20070311/Bild023.jpg
-96d61ed877bcd5c9b5935aca77a1eae78bcb577d5c7aa049b247861bbcd4122ff3c2280ea6dc6152bc843e73c006281614c28d14bdd70aa1692f948e8f19bf4c  Eigene Bilder/20070311/Bild023.jpg
-
-I'm actually using SHA512E. I will try later to reproduce with just that file in another repository. Is there anything else I can provide?
-"""]]
diff --git a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_3_5ebf03120b12edb3fbb8954546e7603e._comment b/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_3_5ebf03120b12edb3fbb8954546e7603e._comment
deleted file mode 100644
index 8db2a8ea1..000000000
--- a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_3_5ebf03120b12edb3fbb8954546e7603e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-03-19T18:17:23Z"
- content="""
-`~/Applications/git-annex.app/Contents/MacOS/runshell` is a little program that sets up your shell to use the programs, and crucially, the libraries, included in the dmg. Running binaries from the app directly and not through runshell is not likely to work. I have updated [[the_OSX_page|/install/OSX]] with information about runshell.
-"""]]
diff --git a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_4_1ba6d2614778949520b47896fd98b598._comment b/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_4_1ba6d2614778949520b47896fd98b598._comment
deleted file mode 100644
index 383f21f1c..000000000
--- a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_4_1ba6d2614778949520b47896fd98b598._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawla3gLc6_rHuggFfy7o7eGMPvPztFZTrUQ"
- nickname="Florian"
- subject="comment 4"
- date="2013-03-19T21:18:19Z"
- content="""
-Using runshell solved the problem, but for my usecases I'm not happy with that. I guess I'll try with a clean cabal again.
-"""]]
diff --git a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_5_4a6e55861a63b350a02edb888b4da99b._comment b/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_5_4a6e55861a63b350a02edb888b4da99b._comment
deleted file mode 100644
index 1baec9625..000000000
--- a/doc/bugs/cannot_add_file__44___get___34__user_error__34__/comment_5_4a6e55861a63b350a02edb888b4da99b._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-03-19T22:53:30Z"
- content="""
-Well, one way to use runshell without annoyance is to put a git-annex wrapper in ~/bin
-like this:
-
-<pre>
-#!/bin/sh
-~/Applications/git-annex.app/Contents/MacOS/runshell git-annex \"$@\"
-</pre>
-
-I think I will repurpose this bug report: The git-annex inside the dmg should
-be such a wrapper, so that it can just be put into PATH and used. The actual binaries in the dmg should be hidden away in a subdirectory where users won't stumble over them.
-
-----
-
-However, cabal is a fine choice.
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server.mdwn b/doc/bugs/cannot_connect_to_xmpp_server.mdwn
deleted file mode 100644
index d64b64003..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-I cannot get the assistant to connect to my jabber account, db48x@db48x.net. I get the message stating that it may take a minute, which is never updated. At the very least I would expect some sort of error message.
-
-I get the same symptoms if I connect to an account @gmail.com, but type in the wrong password. If I put in the correct password, it connects quite quickly.
-
-### What version of git-annex are you using? On what operating system?
-
-[[!format txt """
-[db48x@celebdil ~]$ git annex version
-git-annex version: 4.20130709
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-[db48x@celebdil ~]$ uname -a
-Linux celebdil 3.9.9-201.fc18.x86_64 #1 SMP Fri Jul 5 16:42:02 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
-"""]]
-
-(Fedora 18)
-
-I get exactly the same behavior on my phone, which is running Android 4.1.2
-
-
-### Please provide any additional information below.
-
-[[!format txt """
-[db48x@celebdil books]$ cat .git/annex/daemon.log
-[2013-07-20 16:21:28 PDT] main: starting assistant version 4.20130709
-(scanning...) [2013-07-20 16:21:28 PDT] Watcher: Performing startup scan
-(started...) 
-"""]]
-
-> Closing this bug, since it's not something I can fix in git-annex,
-> but would have to be dealt with in the haskell XMPP library. 
-> Which seems unlikely given John's reply, but you never know --
-> and the bug I filed is still open ;) [[done]] --[[Joey]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_10_5072de8fcca9fe70bc235ea8c8ee2877._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_10_5072de8fcca9fe70bc235ea8c8ee2877._comment
deleted file mode 100644
index 5e2839db2..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_10_5072de8fcca9fe70bc235ea8c8ee2877._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 10"
- date="2013-07-21T03:58:35Z"
- content="""
-Upstream bug report: <http://bugs.debian.org/717463>
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_11_dabd74bba1f38b326a2d0c86d3027cd9._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_11_dabd74bba1f38b326a2d0c86d3027cd9._comment
deleted file mode 100644
index 2ceb4c08f..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_11_dabd74bba1f38b326a2d0c86d3027cd9._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://john-millikin.com/"
- nickname="John Millikin"
- subject="comment 11"
- date="2013-07-22T01:52:41Z"
- content="""
-(I'm the author of the XMPP library git-annex uses)
-
-The biggest issue I can think of with continuing in the absence of a &lt;features&gt; element is authentication. Without &lt;features&gt; the client library is not able to know which SASL mechanisms are supported, so it can't authenticate.
-
-It is possible to modify the XMPP library such that it can work around the problems exibited by this server software (adding a timeout to receipt, hardcoding a fallback SASL list), but I very much do not want to do that because it would almost certainly cause unexpected behavior when used with properly working servers.
-
-According to <a href=\"http://www.mail-archive.com/jdev@jabber.org/msg10598.html\">http://www.mail-archive.com/jdev@jabber.org/msg10598.html</a> , jabberd-1.4.3 was released in 2003. Since its release, there have been multiple severe security issues discovered, including a remote crash (see <a href=\"http://mail.jabber.org/pipermail/jabberd/2004-September/002004.html\">http://mail.jabber.org/pipermail/jabberd/2004-September/002004.html</a> and <a href=\"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1378\">http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1378</a>).
-
-In my opinion, the best course of action is for Daniel to switch to a different Jabber server software, preferably one that is still actively maintained.
-
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_12_0245b426cc0ab64f8c167b8806b03f5d._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_12_0245b426cc0ab64f8c167b8806b03f5d._comment
deleted file mode 100644
index 18f956c3e..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_12_0245b426cc0ab64f8c167b8806b03f5d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA"
- nickname="Daniel"
- subject="comment 12"
- date="2013-07-23T00:59:33Z"
- content="""
-oh, I agree that upgrading is sensible, but I don't actually control the server. Also, I don't see anything in the changelog that indicates that this bug has been fixed. The bug database is out of action as well. A brief examination of the source didn't answer any questions either. Very annoying all around.
-
-Just think of it as adding robustness in the face of a misbehaving server.
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_1_307df11b5bcf289d7999e1e7f7c461c9._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_1_307df11b5bcf289d7999e1e7f7c461c9._comment
deleted file mode 100644
index 1ad583ec7..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_1_307df11b5bcf289d7999e1e7f7c461c9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 1"
- date="2013-07-21T01:20:32Z"
- content="""
-I've fixed the gmail.com problem. It was trying all the servers returned by the SRV query, which all failed due to the bad password, and then fell back to trying gmail.com directly. For whatever reason, gmail.com will accept XMPP connections, but never responds to traffic, so it hung.
-
-The hang with your own XMPP server does not seem related to that.
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_2_f24378cf30a7d32594da90749fabec3c._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_2_f24378cf30a7d32594da90749fabec3c._comment
deleted file mode 100644
index 39c69b5ea..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_2_f24378cf30a7d32594da90749fabec3c._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 2"
- date="2013-07-21T01:26:49Z"
- content="""
-It seems to start to connect to db48x.net, and hang. It may be failing to parse the response about the password being bad, or something like that, and be sitting around waiting for a response. I'm not sure.
-
-What XMPP server software are you using?
-
-The next step would probably be to get a tcpdump of the XMPP connection, ideally with SSL disabled. (Assuming the hang is not occuring during the SSL setup.)
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_3_4b07093be844ac62b611cee1dfde5aa7._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_3_4b07093be844ac62b611cee1dfde5aa7._comment
deleted file mode 100644
index b396e97a1..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_3_4b07093be844ac62b611cee1dfde5aa7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA"
- nickname="Daniel"
- subject="comment 3"
- date="2013-07-21T02:26:38Z"
- content="""
-I captured the connection attempt; the trace is at <http://db48x.net/temp/annex-xmpp-connection.pcap.gz>
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_4_fe1ed152a485c4aebfa9b9f300101835._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_4_fe1ed152a485c4aebfa9b9f300101835._comment
deleted file mode 100644
index 89c66d173..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_4_fe1ed152a485c4aebfa9b9f300101835._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA"
- nickname="Daniel"
- subject="comment 4"
- date="2013-07-21T02:45:52Z"
- content="""
-Comparing that to when I connect to gmail, I see that my server isn't sending any stream features; my server doesn't support TLS.
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_5_2d311f520aee04287df6bddfd8535734._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_5_2d311f520aee04287df6bddfd8535734._comment
deleted file mode 100644
index 62e038941..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_5_2d311f520aee04287df6bddfd8535734._comment
+++ /dev/null
@@ -1,28 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 5"
- date="2013-07-21T02:55:36Z"
- content="""
-Great. We can see git-annex opens the XMPP stream tag, and your server responds by opening its own tag.
-
-Compare with this similar conversation:
-
-    joey@gnu:~>telnet kite 5222
-    Trying 80.68.85.49...
-    Connected to wren.kitenet.net.
-    Escape character is '^]'.
-    <?xml version='1.0'?>
-    <stream:stream xmlns=\"jabber:client\" to=\"kitenet.net\" version=\"1.0\"   xmlns:stream=\"http://etherx.jabber.org/streams\">
-    <?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'   id='e7d73883-a362-4923-89f8-0531eb9d16a0' from='kitenet.net' version='1.0' xml:lang='en'><stream:features>   
-
-So far it's the same as the conversation with your server, but now my server goes on to send another line:
-
-    <stream:features><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>  <mechanism>SCRAM-SHA-1</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms></stream:features>
-
-While your server does not send anything. 
-
-I see that my XMPP client library expects to receive a features tag at this point. Until it does, it won't continue. It may be that your server is not sending the features because it does not implement TLS or any of the other features that need to be advertised.
-
-I think I need to report this to the author of the XMPP client library. It would help to know what XMPP server software you're using, and if it has TLS support enabled.
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_6_d9f916f012184738446c5996ee9d2270._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_6_d9f916f012184738446c5996ee9d2270._comment
deleted file mode 100644
index 5bcc63d20..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_6_d9f916f012184738446c5996ee9d2270._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 6"
- date="2013-07-21T03:07:41Z"
- content="""
-If the initiating entity includes in the initial stream header the 'version' attribute set to a value of at least \"1.0\" (see Section 4.7.5), after sending the response stream header the receiving entity MUST send a <features/> child element 
-
--- <http://xmpp.org/rfcs/rfc6120.html#streams-negotiation>\"
-
-By my reading this XMPP server is not RFC compliant. It's not clear to me if there's a good way for the XMPP client
-to cater to XMPP servers that neglect to send at least an empty features tag.
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_7_0b5f9350e2367301241c7668a15815ef._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_7_0b5f9350e2367301241c7668a15815ef._comment
deleted file mode 100644
index bcb47e20a..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_7_0b5f9350e2367301241c7668a15815ef._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA"
- nickname="Daniel"
- subject="comment 7"
- date="2013-07-21T03:08:52Z"
- content="""
-My server doesn't support TLS at all, and I don't really know what software it is (It's just a freebie that comes with the webhosting for the domain, I don't actually administer it myself). I'll try to find out, perhaps it's something an upgrade can fix.
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_8_f00b6ae154004e405f0bd23b7359962e._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_8_f00b6ae154004e405f0bd23b7359962e._comment
deleted file mode 100644
index 06311fb13..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_8_f00b6ae154004e405f0bd23b7359962e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA"
- nickname="Daniel"
- subject="comment 8"
- date="2013-07-21T03:10:25Z"
- content="""
-Oh, and I agree with your reading of the spec; I was just looking that up myself. I will point out that most other software apparently treats a missing features tag as if it were an empty one, so it's certainly doable :)
-"""]]
diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_9_41b86468013da15f46be29da520afa10._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_9_41b86468013da15f46be29da520afa10._comment
deleted file mode 100644
index 67bec739e..000000000
--- a/doc/bugs/cannot_connect_to_xmpp_server/comment_9_41b86468013da15f46be29da520afa10._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA"
- nickname="Daniel"
- subject="comment 9"
- date="2013-07-21T03:24:03Z"
- content="""
-It's jabberd 1.4.3. Unfortunately the jabberd14 webpage is rather broken; I can't get to the bugzilla or even the svn or downloads page so I don't know if this is a known bug, something that's been fixed in a newer version, or anything.
-"""]]
diff --git a/doc/bugs/cannot_determine_uuid_for_origin.mdwn b/doc/bugs/cannot_determine_uuid_for_origin.mdwn
deleted file mode 100644
index 611a0f236..000000000
--- a/doc/bugs/cannot_determine_uuid_for_origin.mdwn
+++ /dev/null
@@ -1,135 +0,0 @@
-[[!toc]]
-
-### Please describe the problem.
-
-I get this error when trying to copy annexed files from my laptop to the bare repository on my server:
-
-    anarcat@angela:ohm2013$ git annex copy -t origin .
-    git-annex: cannot determine uuid for origin
-
-### What steps will reproduce the problem?
-
-Here's my setup:
-
- * `angela`: regular git repository on my laptop (`angela`) where i ran `git annex init` and `git annex add`ed 4 big files (in `~anarcat/presentations/ohm2013`)
- * `marcos-bare`: a bare git repository where i ran `git annex init` on a different server (`marcos`) (in `~anarcat/repos/presentations/ohm2013.git`)
- * `marcos-checkout`: a checkout of the above repository on marcos (in `~anarcat/presentations/ohm2013`)
-
-I ran `git pull/push` everwhere in there, and still get the error.
-
-Remotes on all repos:
-
- * `angela`: `origin  anarcat.ath.cx:repos/presentations/ohm2013.git`
- * `marcos-bare`: no remote
- * `marcos-checkout`: `origin  /home/anarcat/repos/presentations/ohm2013.git`
-
-Note that file added with `git annex addurl` on `marcos-checkout` properly gets propagated on `angela` once i do `git annex get` there.
-
-### What version of git-annex are you using? On what operating system?
-
-`angela` runs:
-
-[[!format txt """
-git-annex version: 4.20130730-ge59a8c6
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-"""]]
-
-I was able to reproduce with the backport version too.
-
-I compiled it by hand from git.
-
-`marcos` runs:
-
-[[!format txt """
-git-annex version: 3.20120629
-local repository version: unknown
-default repository version: 3
-supported repository versions: 3
-upgrade supported from repository versions: 0 1 2
-"""]]
-
-### Please provide any additional information below.
-
-In addition, there's this error on `marcos-bare`:
-
-[[!format sh """
-anarcat@marcos:ohm2013.git$ git annex status -d
-supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
-supported remote types: git S3 bup directory rsync web hook
-trusted repositories: git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","show-ref","git-annex"]
-git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","show-ref","--hash","refs/heads/git-annex"]
-git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","log","refs/heads/git-annex..6063e958c02259a39b87d0f1dc44c9272c52df3f","--oneline","-n1"]
-git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","cat-file","--batch"]
-0
-semitrusted repositories: 4
-        00000000-0000-0000-0000-000000000001 -- web
-        5868f840-02e7-11e3-94e9-9b3701bd28bb -- marcos-checkout
-        aafdd242-02e7-11e3-bb6a-6f16a5c6103e -- here (marcos-bare)
-        befc3057-d23d-4312-843a-0645e93107d8 -- angela
-untrusted repositories: 0
-dead repositories: 0
-available local disk space: 14 gigabytes (+1 megabyte reserved)
-local annex keys: 0
-local annex size: 0 bytes
-known annex keys: git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","ls-files","--cached","-z","--","/home/anarcat/repos/presentations/ohm2013.git"]
-fatal: '/home/anarcat/repos/presentations/ohm2013.git' is outside repository
-0
-known annex size: 0 bytes
-bloom filter size: 16 mebibytes (0% full)
-backend usage:
-"""]]
-
-### Workaround!
-
-I found that I could succesfully push to the non-bare repo, like this:
-
-[[!format txt """
-anarcat@angela:ohm2013$ git remote add marcos-checkout ssh://anarcat.ath.cx/~/presentations/ohm2013
-anarcat@angela:ohm2013$ git fetch marcos-checkout
-From ssh://anarcat.ath.cx/~/presentations/ohm2013
- * [new branch]      git-annex  -> marcos-checkout/git-annex
- * [new branch]      master     -> marcos-checkout/master
-anarcat@angela:ohm2013$ git annex copy AlerteRouge.webm --to marcos-checkout
-copy AlerteRouge.webm (checking marcos-checkout...) (to marcos-checkout...)
-SHA256E-s138903105--a69db8d4c3835b03bdb08cb1cccfde5c76f586f934d63283694e7101b25352a8.webm
-[...]
-"""]]
-
-It seems that git-annex doesn't like bare repos at all...
-
-### Fix
-
-It seems that my problem was specifically related to [[bare repositories]], which are not well supported historically. There has been other reports of problems in the past, which I missed in my search because symptoms were different:
-
- * [[bugs/bare git repos]]
- * [[forum/get and copy with bare repositories]]
-
-Yet while I was able to do `git annex get --all` *from* the `marcos-bare` repository, I still get the original error message while trying to `git annex copy -t marcos-bare`, which is pretty annoying considering the original files are on my laptop, which is not publicly accessible. So I basically need to add the `marcos-checkout` as a remote, copy there, then get from the bare repo to make this work, which is a rather convoluted way of doing things. :)
-
-It seems to me a proper fix would be to be able to `git annex copy --to marcos-bare`. Thanks!
-
-Update: it seems te problem was that I had the following in my `.git/config`:
-
-    [remote "marcos-bare"]
-            url = ssh://anarcat.ath.cx/~/repos/presentations/ohm2013.git
-            annex-ignore = true
-            fetch = +refs/heads/*:refs/remotes/marcos-bare/*
-
-I have *no* idea how that `annex-ignore` got there, but that was the root of my problem. Removing it it allowed my to do `git annex copy`. I really don't know how this happened, but I guess this is [[done]], although I believe this error message is really confusing and could be improved. --[[anarcat]]
-
-> `annex-ignore` is set automatically by git-annex if it fails to query
-> the uuid of a remote the first time it tries to use it. It will say
-> when it does that. The assumption
-> is that a remote whose uuid cannot be looked up is a git remote
-> on a server w/o git-annex support (like github) and it would be annoying
-> to constantly be trying and failing to get that uuid.
-> 
-> So, I've improved the error message. Now when annex-ignore is set
-> for a remote, the error you got will mention that.
-> 
-> (Also, there is not currently anything lacking in git-annex's support
-> for bare repositories.) --[[Joey]]
diff --git a/doc/bugs/case_sensitivity_on_FAT.mdwn b/doc/bugs/case_sensitivity_on_FAT.mdwn
deleted file mode 100644
index 682acc71d..000000000
--- a/doc/bugs/case_sensitivity_on_FAT.mdwn
+++ /dev/null
@@ -1,49 +0,0 @@
-I was copying files to a directory remote with `git annex copy`.  Out of 114 files, 9 of them failed with no message, just:
-
-    copy data/foo.dat (to usbdrive...) failed
-    copy data/bar.dat (to usbdrive...) failed
-
-According to strace:
-
-    31338 mkdir("/media/annex/Zp/9v/SHA256-s1362999320--d650297c8cf8c2dc0575110a52d0c5cc0ff266f294a0599f85796a6b44b23492", 0777) = -1 ENOENT (No such file or directory)
-    31338 mkdir("/media/annex/Zp/9v", 0777) = -1 ENOENT (No such file or directory)
-    31338 mkdir("/media/annex/Zp", 0777)    = -1 EEXIST (File exists)
-    31338 stat("/media/annex/Zp", 0x7f8449f170d0) = -1 ENOENT (No such file or directory)
-
-The filesystem is FAT32 and has weird case semantics.  This was mounted by udisks with its default options:
-
-    /dev/sdb1 on /media/annex type vfat (rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec)
-
-I wonder if the directory remote should use hashDirLower instead of hashDirMixed?
-
-> git-annex intentionally uses the same layout for directory and rsync
-> special remotes as it does for the .git/annex directory. As far
-> as I know it works ok on (truely) case-insensative filesystems.
-> 
-> Based on your strace, if you `ls /media/annex/Zp`, you will see
-> "No such file or directory", but if you `mkdir /media/annex/Zp` it will
-> fail with "File exists". Doesn't make much sense to me.
-> 
-> The (default) VFAT mount option shortname=mixed causes this behavior.
-> With shortname=lower it works ok. --[[Joey]]
-> 
->> So, the options for fixing this bug seem to be to fix Linux (which would
->> be a good idea IMHO but I don't really want to go there), or generally
->> convert git-annex to using lowercase for its hashing (which would be a
->> large amount of pain to rewrite all the symlinks in every git repo),
->> or some special hack around this problem. 
->> 
->> I've put in a workaround for the problem in the directory special
->> remote; it will use mixed case but fall-back to lowercase as necessary.
->> 
->> That does leave the case of a bare git repository with annexed content
->> stored on VFAT. More special casing could fix it, but that is, I
->> think, an unusual configuration. Leaving the bug open for that case,
->> and for the even more unlikely configuration of a rsync special remote
->> stored on VFAT. --[[Joey]] 
-
->>> Bare repositories now use lowercase. rsync is the only remaining
->>> unsupported possibility. --[[Joey]]
->>>> Everything now uses lowercase, with the exception of non-bare
->>>> repos, which cannot be on FAT anyway due to using symlinks. [[done]]
->>>> --[[Joey]] 
diff --git a/doc/bugs/check_for_curl_in_configure.hs.mdwn b/doc/bugs/check_for_curl_in_configure.hs.mdwn
deleted file mode 100644
index a880392bf..000000000
--- a/doc/bugs/check_for_curl_in_configure.hs.mdwn
+++ /dev/null
@@ -1,92 +0,0 @@
-[[!meta title="arbitrary/configurable backends"]]
-
-(Retitling as this has drifted..)
-
----
-
-I thought this might be useful, since curl is being used for the URL backend, it might be worth checking for it's existence.
-
-<pre>
-diff --git a/configure.hs b/configure.hs
-index 772ba54..1a563e0 100644
---- a/configure.hs
-+++ b/configure.hs
-@@ -13,6 +13,7 @@ tests = [
-        , TestCase "uuid generator" $ selectCmd "uuid" ["uuid", "uuidgen"]
-        , TestCase "xargs -0" $ requireCmd "xargs_0" "xargs -0 </dev/null"
-        , TestCase "rsync" $ requireCmd "rsync" "rsync --version >/dev/null"
-+       , TestCase "curl" $ requireCmd "curl" "curl --version >/dev/null"
-        , TestCase "unicode FilePath support" $ unicodeFilePath
-        ] ++ shaTestCases [1, 256, 512, 224, 384]
-</pre>
-
-> Well, curl is an optional extra, so requireCmd is too strong. Changed
-> to testCmd and applied, thank you!
->
-> I thought about actually *using* the resulting SysConfig.curl
-> to disable the URL backend if False.. but probably it's better
-> to just let it fail if curl is not available. Although, if we wanted
-> to add a check for wget or something and use it when curl was not
-> available, that might be worth doing. --[[Joey]] 
-
->> I was thinking that is it worth doing a generic "stat", "delete", "get" 
->> and "put" options, I do like the idea of having the possibility of 
->> being about to use completely arbitrary storage systems or arbitrary 
->> transfer systems. If there was the capability of doing so it would be 
->> interesting to see possibilities of using aria2 for using something 
->> like bittorrent as backend, or using something like irods or some 
->> grid storage system as the storage archive. It's just an idea as 
->> I have seen it implemented quite well in irods.
-
->>> I'm unsure about the idea of having a backend where that is
->>> parameterized. It would mean that one annex's GENERIC-foo key
->>> might be entirely different from another's key with the same backend
->>> and details. And a misconfiguration could get data the wrong
->>> way and get the wrong data, etc.
->>>
->>> I mostly look at the URL backend as an example that can be modified to
->>> make this kind of custom backend. You already probably know enough to
->>> make a TORRENT backend where keys are the urls to torrents to download
->>> with `aria2c --follow-torrent=mem`.
->>>
->>> I am also interested in doing backends that use eg, cloud storage.
->>> A S3 backend that could upload files to S3 in addition to downloading
->>> them, for example, would be handy. --[[Joey]]
-
->>>> So, rather than use backends to do this, it instead made more sense
->>>> to make them [[special_remotes]]. The URL backend remains a bit
->>>> of a special case, and a bittorrent backend that downloaded a file
->>>> from a bittorrent url would still be a good use of backend, but for
->>>> storing files in external data stores like S3, making it a remote
->>>> makes better sense. I think I can close this bug now, [[done]]
->>>> --[[Joey]] 
-
-also in Backend/URL.hs is it worth making a minor change to the way curl is called (I'm not sure if the following is correct or not)
-
-> It's correct, typewise, but I don't see any real reason to bother
-> with the change. But I do appreciate patches, which have been rare
-> so far, probaby because of Haskell.. :) --[[Joey]] 
-
->> heh agreed
-
-<pre>
-diff --git a/Backend/URL.hs b/Backend/URL.hs
-index 29dc8fe..4afcf86 100644
---- a/Backend/URL.hs
-+++ b/Backend/URL.hs
-@@ -50,10 +50,13 @@ dummyFsck _ _ _ = return True
- dummyOk :: Key -> Annex Bool
- dummyOk _ = return True
- 
-+curl :: [CommandParam] -> IO Bool
-+curl = boolSystem "curl"
-+
- downloadUrl :: Key -> FilePath -> Annex Bool
- downloadUrl key file = do
-        showNote "downloading"
-        showProgress -- make way for curl progress bar
--       liftIO $ boolSystem "curl" [Params "-# -o", File file, File url]
-+       liftIO $ curl [Params "-# -o", File file, File url]
-        where
-                url = join ":" $ drop 1 $ split ":" $ show key 
-</pre>
diff --git a/doc/bugs/clicking_back_in_the_web_browser_crashes.mdwn b/doc/bugs/clicking_back_in_the_web_browser_crashes.mdwn
deleted file mode 100644
index 1b7e2ec71..000000000
--- a/doc/bugs/clicking_back_in_the_web_browser_crashes.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-### Please describe the problem.
-
-When I click on the "back" button in my web browser, I get the following error message:
-
-    git-annex has shut down
-    
-    You can now close this browser window.
-
-### What steps will reproduce the problem?
-
- 1. git annex webapp
- 2. click on "configuration" (or whatever)
- 3. click on the back button of your web browser
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130815~bpo70+1 on Debian Wheezy, with Chromium Version 29.0.1547.57 Debian 7.1 (217859)
-
-### Please provide any additional information below.
-
-Click "forward" actually brings us back to sanity, and the webapp doesn't actually *crash*. -- [[anarcat]]
-
-> I have applied the page reload fix/hack. [[done]] --[[Joey]] 
diff --git a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment
deleted file mode 100644
index ece6ce0e3..000000000
--- a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.255.110"
- subject="comment 1"
- date="2013-09-09T04:23:36Z"
- content="""
-This occurs when the javascript long polling code fails 4 times in a row attempting to communicate with git-annex's web server. Normally this will mean that the assistant has been stopped. I have seen it once or twice happen while the web server is still running -- possibly due to the browser killing the connection? I have never seen it happen when navigating between pages in the webapp, which is designed to allow use of back button etc. If you can reproduce it reliably, using the chromium inspector to modify the javascript code (look for \"longpoll\") and perhaps add some debug prints might track down what is going on.
-"""]]
diff --git a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_2_643b2c99ecfe851c576a023ce4385dbb._comment b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_2_643b2c99ecfe851c576a023ce4385dbb._comment
deleted file mode 100644
index feac21ffe..000000000
--- a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_2_643b2c99ecfe851c576a023ce4385dbb._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://id.koumbit.net/anarcat"
- ip="2001:1928:1:9::1"
- subject="comment 2"
- date="2013-09-09T04:31:30Z"
- content="""
-i can reproduce reliably alright. It's quite systematic. I have found the `longpolling.js` file in the inspector, but I am not very familiar with in-browser javascript debugging, so I am not sure where to go from here.
-
-Note that the assistant doesn't actually crash. This is also reproducable in Debian sid.
-"""]]
diff --git a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_3_6e85c50439da81212f4239c74947b75e._comment b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_3_6e85c50439da81212f4239c74947b75e._comment
deleted file mode 100644
index a3dee1d52..000000000
--- a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_3_6e85c50439da81212f4239c74947b75e._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.255.110"
- subject="comment 3"
- date="2013-09-09T05:22:49Z"
- content="""
-Actually I am able to reproduce it. One thing I can see is that git-annex does not see any connection attempts from the browser when these longpolling attempts are made and fail. So this is all failing on the javascript side. Increasing the connection failure counter does not help. Every ajax request fails, no matter how many times it tries. Chromium has apparently decided that, because we've navigated back to a page, it should not be allowed to load any new resources. This seems to be new, buggy behavior.
-
-It seems the only way out of this bad state would be for the javacript to force a reload of the page. Of course, if git-annex has legitimately exited, that would fail to reload. I suppose the chromium \"this webpage is not available\" that would result is at least accurate...
-
-(At some point, I should probably try to add support for something more modern than long polling.)
-"""]]
diff --git a/doc/bugs/com.branchable.git-annex.assistant.plist_is_invalid.mdwn b/doc/bugs/com.branchable.git-annex.assistant.plist_is_invalid.mdwn
deleted file mode 100644
index d67cdcd40..000000000
--- a/doc/bugs/com.branchable.git-annex.assistant.plist_is_invalid.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-What steps will reproduce the problem?
-`cat com.branchable.git-annex.assistant`
-
-What version of git-annex are you using? On what operating system?
-  git-annex version: 3.20121112 on OS X Mountain Lion
-
-Please provide any additional information below.
-The '`RunAtLoad`'  key is missing a value.
-
-It should say:
-
-`<key>RunAtLoad</key>`<br>
-`<true/>`
-
-> Fixed in git. [[done]] --[[Joey]] 
diff --git a/doc/bugs/commit_f20a40f_breaks_on_OSX_as_mntent.h_doesn__39__t_exist.mdwn b/doc/bugs/commit_f20a40f_breaks_on_OSX_as_mntent.h_doesn__39__t_exist.mdwn
deleted file mode 100644
index dfd3ffb82..000000000
--- a/doc/bugs/commit_f20a40f_breaks_on_OSX_as_mntent.h_doesn__39__t_exist.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-commit f20a40f breaks on OSX as mntent.h doesn't exist, the closet thing available to what mntent.h provides is getmntinfo(), it looks yet another bunch of ifdef's might be needed to work around OSX. This problem maybe similarly true with FreeBSD, libfam  seems to have worked around the issue - <http://oss.sgi.com/projects/fam/download/contrib/freebsd-mntent.patch>
-
-hope the above report helps.
-
-> Thanks, that was a very useful pointer. I couldn't figure out how to
-> use Haskell's FFI to loop over the list of statfs structs returned by
-> getmntinfo, so I incorporated that C code into a little library, 
-> and it seems to work ok. [[done]] --[[Joey]]
diff --git a/doc/bugs/configure_mistakes_hashalot_bins_for_sha__63____63____63__sum_and_builds_a_broken_git-annex_executable.mdwn b/doc/bugs/configure_mistakes_hashalot_bins_for_sha__63____63____63__sum_and_builds_a_broken_git-annex_executable.mdwn
deleted file mode 100644
index b71f39e5a..000000000
--- a/doc/bugs/configure_mistakes_hashalot_bins_for_sha__63____63____63__sum_and_builds_a_broken_git-annex_executable.mdwn
+++ /dev/null
@@ -1,57 +0,0 @@
-git-annex's configure step finds hashalot's /usr/sbin/sha256, /usr/sbin/sha384, and /usr/sbin/sha512 executables and mistakes them for sha256sum, sha384sum, and sha512sum and prefers them over the correct executables.  Hashalot is not compatible, but the build does not fail producing a broken git-annex executable which tries to use hashalot's programs instead of the appropriate shaXXXsum program and is non-functional.
-
-Hashalot can be found at: <http://www.paranoiacs.org/~sluskyb/hacks/hashalot/>
-
-
-What steps will reproduce the problem?
-
-Compile with hashalot's programs in the path.
-
-
-What is the expected output? What do you see instead?
-
-Expect to see configure output:
-
-[...]
-<pre>
-  checking sha1... sha1sum
-  checking sha512... sha512sum
-  checking sha224... sha224sum
-  checking sha384... sha384sum
-  checking sha256... sha256sum
-</pre>
-[...]
-
-
-Instead I see configure output:
-
-[...]
-<pre>
-  checking sha1... sha1sum
-  checking sha512... sha512
-  checking sha224... sha224sum
-  checking sha384... sha384
-  checking sha256... sha256
-</pre>
-[...]
-
-
-What version of git-annex are you using? On what operating system?
-
-I am using 3.20120605, but have checked out the latest GIT and confirmed the bug is still there.
-
-
-Please provide any additional information below.
-
-This is not a runtime bug, only compile time.  Uninstalling Hashalot or simply removing it from the PATH is enough to work around this bug.  The bug is, however, frustrating because at first glance there appears to be no problem.  However any functions of git-annex which use the affected SHA hash functions will fail with the resulting executable and the failure gives no clear indication of why.
-
-I found this bug on Gentoo when I installed git-annex on a system which already had hashalot installed.  In the case of Gentoo, git-annex is compiled with hashalot's executables in the path, but normal users don't have /usr/sbin/ in their path so git-annex just fails to find the executable.  If you put hashalot in the path, then git annex still fails to work as hashalot is not a replacement for sha1sum and friends.
-
-It may be enough to just prefer sha???sum over sha??? if they both exist.
-
-> Grr. There is no consistency across unixes as to the names of these
-> programs and now something is installing shaN commands that don't
-> generate a checksum?!
-> 
-> Ok, fine, configure now checks that the program it finds outputs a known
-> good checksum. [[done]] --[[Joey]]
diff --git a/doc/bugs/configure_script_should_detect_uuidgen_instead_of_just_uuid.mdwn b/doc/bugs/configure_script_should_detect_uuidgen_instead_of_just_uuid.mdwn
deleted file mode 100644
index 2b9c77367..000000000
--- a/doc/bugs/configure_script_should_detect_uuidgen_instead_of_just_uuid.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-On RHEL5 (and clones) systems uuidgen is available as an alternative to
-uuid, the configure script fails, it should probably detect either uuid or
-uuidgen, or let the user decide? - also uuidgen behaves differently from
-uuid on debian.
-
-> uuidgen is now supported. --[[Joey]] [[done]]
diff --git a/doc/bugs/conflicting_haskell_packages.mdwn b/doc/bugs/conflicting_haskell_packages.mdwn
deleted file mode 100644
index 5528fad82..000000000
--- a/doc/bugs/conflicting_haskell_packages.mdwn
+++ /dev/null
@@ -1,17 +0,0 @@
-The compilation command should states which packages are used and avoid the default mechnasim that automatically search for them.
-
-This can be done by the flags -hide-packages and then -package foo
-
-> My ghc does not have a `--hide-packages` option.
-> 
-> Could you just show the build problem that you are suggesting I work
-> around? --[[Joey]]
-
-
-> Thanks npouillard, I see the problem now.
-> <http://stackoverflow.com/questions/2048953/control-monad-state-found-in-multiple-packages-haskell>
-> 
-> I've added "-ignore-package monads-fd" to GHCFLAGS. I hope I don't
-> really have to hide all packages and individually turn them back on;
-> surely this monads-fd/mtl conflict is an exception, and Haskell's module
-> system is not a mess of conflicting modules? --[[Joey]] [[done]]
diff --git a/doc/bugs/conflicting_haskell_packages/comment_1_e552a6cc6d7d1882e14130edfc2d6b3b._comment b/doc/bugs/conflicting_haskell_packages/comment_1_e552a6cc6d7d1882e14130edfc2d6b3b._comment
deleted file mode 100644
index 42f44bf9c..000000000
--- a/doc/bugs/conflicting_haskell_packages/comment_1_e552a6cc6d7d1882e14130edfc2d6b3b._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="http://ertai.myopenid.com/"
- nickname="npouillard"
- subject="how to reproduce the package conflict issue"
- date="2011-02-07T14:12:43Z"
- content="""
-If you install the monads-fd package (with cabal install for instance), then you can no longer build git-annex:
-
-<pre>
-./configure
-  checking cp -a... yes
-  checking cp -p... yes
-  checking cp --reflink=auto... yes
-  checking uuid generator... uuid
-  checking xargs -0... yes
-  checking rsync... yes
-ghc -O2 -Wall --make git-annex
-
-Annex.hs:22:7:
-    Ambiguous module name `Control.Monad.State':
-      it was found in multiple packages: monads-fd-0.2.0.0 mtl-2.0.1.0
-make: *** [git-annex] Error 1
-</pre>
-"""]]
diff --git a/doc/bugs/conq:_invalid_command_syntax.mdwn b/doc/bugs/conq:_invalid_command_syntax.mdwn
deleted file mode 100644
index 82cd51d8d..000000000
--- a/doc/bugs/conq:_invalid_command_syntax.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-I've been getting an occasional error from git-annex.
-
-The error is:   'conq: invalid command syntax.'
-
-For example, the last two commands I ran are:
-
-    $ git annex unused
-    unused . (checking for unused data...) (checking master...) (checking origin/master...) 
-      Some annexed data is no longer used by any files:
-        NUMBER  KEY
-        1       SHA256-s.....
-      (To see where data was previously used, try: git log --stat -S'KEY')
-      
-      To remove unwanted data: git-annex dropunused NUMBER
-      
-    ok
-    
-    $ git annex dropunused 1
-    dropunused 1 conq: invalid command syntax.
-    ok
-
-
-
-*OS:*  OSX + port installs of the GNU tools
-
-*git-annex-version:*  3.20111211
-
-*git-version:*  1.7.7.4
-
-> [[done]], apparently not a git-annex bug --[[Joey]] 
diff --git a/doc/bugs/conq:_invalid_command_syntax/comment_1_f33b83025ce974e496f83f248275a66a._comment b/doc/bugs/conq:_invalid_command_syntax/comment_1_f33b83025ce974e496f83f248275a66a._comment
deleted file mode 100644
index 62881bfc7..000000000
--- a/doc/bugs/conq:_invalid_command_syntax/comment_1_f33b83025ce974e496f83f248275a66a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2012-01-03T00:34:59Z"
- content="""
-AFAICs, you probably just have a \"conq\" program that is running in the background and emitted this error.
-
-The error message is not part of git-annex; it does not run any \"conq\" thing itself. Although you could try passing the --debug parameter to check the commands it does run to see if one of them somehow causes this conq thing.
-"""]]
diff --git a/doc/bugs/conq:_invalid_command_syntax/comment_2_195106ca8dedad5f4d755f625e38e8af._comment b/doc/bugs/conq:_invalid_command_syntax/comment_2_195106ca8dedad5f4d755f625e38e8af._comment
deleted file mode 100644
index 39ece1eca..000000000
--- a/doc/bugs/conq:_invalid_command_syntax/comment_2_195106ca8dedad5f4d755f625e38e8af._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2012-01-03T00:41:08Z"
- content="""
-A google search <http://www.google.com/search?hl=en&sclient=psy-ab&q=conq%3A+invalid+command+syntax&btnG=>
-finds other examples of this error message related to ssh, mercurial, and bitbucket. What that has to do with git is anyone's guess, but I'm pretty sure git-annex is not related to it at all.
-"""]]
diff --git a/doc/bugs/conq:_invalid_command_syntax/comment_3_55af43e2f43a4c373f7a0a33678d0b1c._comment b/doc/bugs/conq:_invalid_command_syntax/comment_3_55af43e2f43a4c373f7a0a33678d0b1c._comment
deleted file mode 100644
index 75132c1d6..000000000
--- a/doc/bugs/conq:_invalid_command_syntax/comment_3_55af43e2f43a4c373f7a0a33678d0b1c._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://a-or-b.myopenid.com/"
- ip="203.45.2.230"
- subject="comment 3"
- date="2012-01-03T00:49:41Z"
- content="""
-Yeah,  I saw those google links myself, but couldn't see why the bitbucket/ssh would be relevant.
-
-The strange thing is that I *only* get this message when running git-annex.
-
-I also don't have a conq in my path so I don't know where it is running from.
- 
-
-Oh well, if I ever sort it out I'll post back here.
-"""]]
diff --git a/doc/bugs/copy_doesn__39__t_scale.mdwn b/doc/bugs/copy_doesn__39__t_scale.mdwn
deleted file mode 100644
index a5ca9d9ee..000000000
--- a/doc/bugs/copy_doesn__39__t_scale.mdwn
+++ /dev/null
@@ -1,38 +0,0 @@
-It seems that git-annex copies every individual file in a separate
-transaction. This is quite costly for mass transfers: each file involves a
-separate rsync invocation and the creation of a new commit. Even with a
-meager thousand files or so in the annex, I have to wait for fifteen
-minutes to copy the contents to another disk, simply because every
-individual file involves some disk thrashing. Also, it seems suspicious
-that the git-annex branch would get a thousands commits of history from the
-simple procedure of copying everything to a new repository. Surely it would
-be better to first copy everything and then create only a single commit
-that registers the changes to the files' availability?
-
-> git-annex is very careful to commit as infrequently as possible,
-> and the current version makes *1* commit after all the copies are
-> complete, even if it transferred a billion files. The only overhead
-> incurred for each file is writing a journal file.
-> You must have an old version.
-> --[[Joey]]
-
-(I'm also not quite clear on why rsync is being used when both repositories
-are local. It seems to be just overhead.)
-
-> Even when copying to another disk it's often on 
-> some slow bus, and the file is by definition large. So it's
-> nice to support resumes of interrupted transfers of files.
-> Also because rsync has a handy progress display that is hard to get with cp.
-> 
-> (However, if the copy is to another directory in the same disk, it does
-> use cp, and even supports really fast copies on COW filesystems.)
-> --[[Joey]]
-
----
-
-Oneshot mode is now implemented, making git-annex-shell and other
-short lifetime processes not bother with committing changes.
-[[done]] --[[Joey]] 
-
-Update: Now it makes one commit at the very end of such a mass transfer.
---[[Joey]]
diff --git a/doc/bugs/copy_doesn__39__t_scale/comment_1_7c12499c9ac28a9883c029f8c659eb57._comment b/doc/bugs/copy_doesn__39__t_scale/comment_1_7c12499c9ac28a9883c029f8c659eb57._comment
deleted file mode 100644
index 749b3ba10..000000000
--- a/doc/bugs/copy_doesn__39__t_scale/comment_1_7c12499c9ac28a9883c029f8c659eb57._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk6QAwUsFHpr3Km1yQbg8hf3S7RDYf7hX4"
- nickname="Lauri"
- subject="comment 1"
- date="2012-01-28T00:17:37Z"
- content="""
-To me it very much seems that a commit per file is indeed created at the remote end, although not at the local end. See the following transcript: <https://gist.github.com/1691714>.
-
-
-"""]]
diff --git a/doc/bugs/copy_doesn__39__t_scale/comment_2_f85d8023cdbc203bb439644cf7245d4e._comment b/doc/bugs/copy_doesn__39__t_scale/comment_2_f85d8023cdbc203bb439644cf7245d4e._comment
deleted file mode 100644
index 9a2bd92fa..000000000
--- a/doc/bugs/copy_doesn__39__t_scale/comment_2_f85d8023cdbc203bb439644cf7245d4e._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2012-01-28T19:32:36Z"
- content="""
-Ah, I see, I was not thinking about the location log update that's done on the remote side.
-
-For transfers over ssh, that's a separate git-annex-shell invoked per change. For local-local transfers, it's all done in a single process but it spins up a state to handle the remote and then immediately shuts it down, also generating a commit.
-
-In either case, I think there is a nice fix. Since git-annex *does* have a journal nowadays, and goes to all the bother to
-support recovery if a process was interrupted and journalled changes that did not get committed, there's really no reason in either of these cases for the remote end to do anything more than journal the change. The next time git-annex is actually run on the remote, and needs to look up location information, it will merge the journalled changes into the branch, in a single commit.
-
-My only real concern is that some remotes might *never* have git-annex run in them directly, and would just continue to accumulate journal files forever. Although due to the way the journal is structured, it can have, at a maximum, the number of files in the git-annex branch. However, the number of files in it is expected to be relatively smal and it might get a trifle innefficient, as it lacks directory hashing. These performance problems could certainly be dealt with if they do turn out to be a problem.
-"""]]
diff --git a/doc/bugs/copy_doesn__39__t_scale/comment_3_4592765c3d77bb5664b8d16867e9d79c._comment b/doc/bugs/copy_doesn__39__t_scale/comment_3_4592765c3d77bb5664b8d16867e9d79c._comment
deleted file mode 100644
index aa9bf1e45..000000000
--- a/doc/bugs/copy_doesn__39__t_scale/comment_3_4592765c3d77bb5664b8d16867e9d79c._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk6QAwUsFHpr3Km1yQbg8hf3S7RDYf7hX4"
- nickname="Lauri"
- subject="comment 3"
- date="2012-01-29T01:51:35Z"
- content="""
-That sounds just fine, but indeed my use case was a bare backup/transfer repository that is meant to always be only at the remote end of git-annex operations. So why not as well do a single commit after everything has been copied and journaled? That's what's done at the other end too, after all. Or, if commits are to be minimized, just stage the journal into the index before finishing, but don't commit it yet?
-
-(I would actually prefer this mode of usage for other git-annex operations, too. In git you can add stuff little by little and commit them all in one go. In git-annex the add immediately creates a commit, which is unexpected and a bit annoying.)
-
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog.mdwn b/doc/bugs/copy_fast_confusing_with_broken_locationlog.mdwn
deleted file mode 100644
index 69fbc816f..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-Conversation moved from [[tips/recover_data_from_lost+found]]
-to a proper bug. --[[Joey]]
-
-(Unfortunatly that scrambled the comment creation times and thus order.)
-
-> Added a message [[done]] --[[Joey]] 
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_10_435f87d54052f264096a8f23e99eae06._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_10_435f87d54052f264096a8f23e99eae06._comment
deleted file mode 100644
index ec24c478d..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_10_435f87d54052f264096a8f23e99eae06._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 10"
- date="2011-05-15T16:47:53Z"
- content="""
-The key is the basename of the symlink target.
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_11_9be0aef403a002c1706d17deee45763c._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_11_9be0aef403a002c1706d17deee45763c._comment
deleted file mode 100644
index 7bc54573e..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_11_9be0aef403a002c1706d17deee45763c._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 11"
- date="2011-05-15T18:53:26Z"
- content="""
-It seems the objects are in the remote after all, but the remote is unaware of this fact. No idea where/why the remote lost that info, but.. Anyway, with the SHA backends, wouldn't it make sense to simply return \"OK\" and update the annex logs accordingly, no?
-
-Local:
-
-    % ls -l foo
-    lrwxrwxrwx 1 richih richih 312 Apr  3 01:18 foo -> .git/annex/objects/gG/VW/SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491/SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491
-    % 
-
-Remote:
-
-    % git-annex-shell recvkey <remote> SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491
-    git-annex-shell: key is already present in annex
-    % strace git-annex-shell recvkey /base/git-annex/fun SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491 2>&1 | grep SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491
-    stat64(\"/base/git-annex/fun/annex/objects/gG/VW/SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491/SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491\", {st_mode=S_IFREG|0444, st_size=80781, ...}) = 0
-    % ls -l /base/git-annex/fun/annex/objects/gG/VW/SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491/SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491
-    -r--r--r-- 1 richih richih 80781 2011-04-01 12:44 /base/git-annex/fun/annex/objects/gG/VW/SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491/SHA512-s80781--cef3966a19c7435acceb8fbfbff1feebe6decab7c81a0c197f00932cf9ef0eac330784cc3f0d211bd4acf56a6d16daaebe9b598aa4dfd5bfec73f4e6df3f0491
-    % 
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_12_26d60661196f63fd01ee4fbb6e2340e7._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_12_26d60661196f63fd01ee4fbb6e2340e7._comment
deleted file mode 100644
index b458a37b6..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_12_26d60661196f63fd01ee4fbb6e2340e7._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 12"
- date="2011-05-15T19:40:47Z"
- content="""
-So, it appears that you're using git annex copy --fast. As documented that assumes the location log is correct. So it avoids directly checking if the bare repo contains the file, and tries to upload it, and the bare repo is all like \"but I've already got this file!\". The only way to improve that behavior might be to let rsync go ahead and retransfer the file, which, with recovery, should require sending little data etc. But I can't say I like the idea much, as the repo already has the content, so unlocking it and letting rsync mess with it is an unnecessary risk. I think it's ok for --force to blow up
-if its assumptions turn out to be wrong.
-
-If you use git annex copy without --fast in this situation, it will do the right thing.
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_13_ead55b915d3b92a62549b2957ad211c8._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_13_ead55b915d3b92a62549b2957ad211c8._comment
deleted file mode 100644
index d92ecbba0..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_13_ead55b915d3b92a62549b2957ad211c8._comment
+++ /dev/null
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 13"
- date="2011-05-15T20:25:25Z"
- content="""
-Yes, makes sense. I am so used to using --fast, I forgot a non-fast mode existed. I still think it would be a good idea to fall back to non-fast mode if --fast runs into an error from the remote, but as that is well without my abilities how about this patch?
-
-
-    From 4855510c7a84eb5d28fdada429580a8a42b7112a Mon Sep 17 00:00:00 2001
-    From: Richard Hartmann <richih.mailinglist@gmail.com>
-    Date: Sun, 15 May 2011 22:20:42 +0200
-    Subject: [PATCH] Make error in RecvKey.hs suggest possible solution
-    
-    ---
-     Command/RecvKey.hs |    2 +-
-     1 files changed, 1 insertions(+), 1 deletions(-)
-    
-    diff --git a/Command/RecvKey.hs b/Command/RecvKey.hs
-    index 126608f..b917a1c 100644
-    --- a/Command/RecvKey.hs
-    +++ b/Command/RecvKey.hs
-    @@ -27,7 +27,7 @@ start :: CommandStartKey
-     start key = do
-        present <- inAnnex key
-        when present $
-    -       error \"key is already present in annex\"
-    +       error \"key is already present in annex. If you are running copy, try without '--fast'\"
-        
-        ok <- getViaTmp key (liftIO . rsyncServerReceive)
-        if ok
-    -- 
-    1.7.4.4
-
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_14_191de89d3988083d9cf001799818ff4a._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_14_191de89d3988083d9cf001799818ff4a._comment
deleted file mode 100644
index f45bd7046..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_14_191de89d3988083d9cf001799818ff4a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 14"
- date="2011-05-15T20:50:26Z"
- content="""
-Or, even better, wouldn't it make sense to have SHA backends always default to --fast and only use non-fast when any snags are hit, use non-fast mode for that file.
-
-Though if we continue here, we should probably move this to its own page.
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_15_b3e3b338ccfa0a32510c78ba1b1bb617._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_15_b3e3b338ccfa0a32510c78ba1b1bb617._comment
deleted file mode 100644
index b4a00bd7e..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_15_b3e3b338ccfa0a32510c78ba1b1bb617._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 15"
- date="2011-05-15T21:38:47Z"
- content="""
-PS: Just to make this clear, I am using a custom alias for all my copying needs and thus didn't even see that I used --fast. :p
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_16_04a9f4468c3246c8eff3dbe21dd90101._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_16_04a9f4468c3246c8eff3dbe21dd90101._comment
deleted file mode 100644
index 6d3dabb92..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_16_04a9f4468c3246c8eff3dbe21dd90101._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 16"
- date="2011-05-16T20:01:28Z"
- content="""
-Thanks.
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_1_6a41bf7e2db83db3a01722b516fb6886._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_1_6a41bf7e2db83db3a01722b516fb6886._comment
deleted file mode 100644
index 59c30de53..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_1_6a41bf7e2db83db3a01722b516fb6886._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-05-12T00:07:29Z"
- content="""
-I followed this to re-inject files which git annex fsck listed as missing.
-
-For everyone of those files, I get 
-
-    git-annex-shell: key is already present in annex
-    rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-    rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.8]
-
-when trying to copy the files to the remote.
-
--- Richard
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_2_9f5f1dbffb2dd24f4fcf8c2027bf0384._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_2_9f5f1dbffb2dd24f4fcf8c2027bf0384._comment
deleted file mode 100644
index 44aab3baa..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_2_9f5f1dbffb2dd24f4fcf8c2027bf0384._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-05-12T01:01:34Z"
- content="""
-Sounds like you probably didn't commit after the fsck, or didn't push so the other repository did not know the first had the content again -- but I'm not 100% sure.
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_3_b596b5cfd3377e58dbbb5d509d026b90._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_3_b596b5cfd3377e58dbbb5d509d026b90._comment
deleted file mode 100644
index 4744db995..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_3_b596b5cfd3377e58dbbb5d509d026b90._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 3"
- date="2011-05-14T09:06:54Z"
- content="""
-As my comment from work is stuck in moderation:
-
-I ran this twice:
-
-    git pull && git annex add . && git annex copy . --to <remote> --fast --quiet && git commit -a -m \"$HOST $(date +%F--%H-%M-%S-%Z)\" && git push
-
-but nothing changed
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_4_d7112c315fb016a8a399e24e9b6461d8._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_4_d7112c315fb016a8a399e24e9b6461d8._comment
deleted file mode 100644
index 1fb19ab19..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_4_d7112c315fb016a8a399e24e9b6461d8._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 4"
- date="2011-05-14T16:13:58Z"
- content="""
-Hmm. Old versions may have forgotten to git add a .git-annex location log file when recovering content with fsck. That could be another reason things are out of sync.
-
-But I'm not clear on which repo is trying to copy files to which.
-
-(NB: If the files were recovered on a bare git repo, fsck cannot update the location log there, which could also explain this.)
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_5_4ea29a6f8152eddf806c536de33ef162._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_5_4ea29a6f8152eddf806c536de33ef162._comment
deleted file mode 100644
index 0a546bd88..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_5_4ea29a6f8152eddf806c536de33ef162._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 5"
- date="2011-05-14T19:03:43Z"
- content="""
-Version: 0.20110503
-
-My local non-bare repo is copying to a remote bare repo.
-
-I have been recovering in a non-bare repo.
-
-If there is anything I can send you to help... If I removed said files and went through http://git-annex.branchable.com/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/ -- would that help?
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_6_0d85f114a103bd6532a3b3b24466012e._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_6_0d85f114a103bd6532a3b3b24466012e._comment
deleted file mode 100644
index 1e3f32531..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_6_0d85f114a103bd6532a3b3b24466012e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 6"
- date="2011-05-14T19:23:45Z"
- content="""
-Well, focus on a specific file that exhibits the problem. What does `git annex whereis` say about it? Is the content actually present in annex/objects/ on the bare repository? Does that contradict whereis?
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_7_d38d5bee6d360b0ea852f39e3a7b1bc6._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_7_d38d5bee6d360b0ea852f39e3a7b1bc6._comment
deleted file mode 100644
index f7dfad68c..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_7_d38d5bee6d360b0ea852f39e3a7b1bc6._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 7"
- date="2011-05-14T23:13:15Z"
- content="""
-It exists locally, whereis tells me it exists locally and locally, only.
-
-The object is _not_ in the bare repo.
-
-The file _might_ have gone missing before I upgraded my annex backend version to 2. Could this be a factor?
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_8_29c3de4bf5fbd990b230c443c0303cbe._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_8_29c3de4bf5fbd990b230c443c0303cbe._comment
deleted file mode 100644
index 01248914c..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_8_29c3de4bf5fbd990b230c443c0303cbe._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 8"
- date="2011-05-15T00:09:34Z"
- content="""
-What you're describing should be impossible; the error message shown can only occur if the object is present in the annex where `git-annex-shell recvkey` is run. So something strange is going on.
-
-Try reproducing it by running on the remote system, `git-annex-shell recvkey /remote/repo.git $key` .. if you can reproduce it, I guess the next thing to do will be to strace the command and see why it's thinking the object is there.
-"""]]
diff --git a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_9_2cee4f6bd6db7518fd61453c595162c6._comment b/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_9_2cee4f6bd6db7518fd61453c595162c6._comment
deleted file mode 100644
index 2755cf331..000000000
--- a/doc/bugs/copy_fast_confusing_with_broken_locationlog/comment_9_2cee4f6bd6db7518fd61453c595162c6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 9"
- date="2011-05-15T09:16:49Z"
- content="""
-Just to make sure: How do I get $key? What I did was look at the path in the object store of the local repo and see if that exact same path & file existed in the remote.
-"""]]
diff --git a/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work.mdwn b/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work.mdwn
deleted file mode 100644
index 190f3bb3b..000000000
--- a/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work.mdwn
+++ /dev/null
@@ -1,74 +0,0 @@
-### Please describe the problem.
-Copying to a gpg encrypted webdav remote (with davfs) seems to work, but fails.
-The command "git annex copy --to 1und1 some/file" returns ok, but a fsck fails and running
-the copy again copies the file again to the remote.
-
-### What steps will reproduce the problem?
-[[!format sh """
-git annex copy --to 1und1 some/file # seems ok
-git annex copy --to 1und1 some/file # copies again
-git annex fsck --from 1und1 some/file # fails
-"""]]
-
-### What version of git-annex are you using? On what operating system?
-4.20131002 on debian (mostly stable), armel.
-
-### Please provide any additional information below.
-
-I used strace to see what is going on. It seems the chunkcount file is not written. When I create that file by hand fsck is happy.
-(git annex seems to have two different locations for that file (dcf/85a and 3W/Qm). The second (3W/Qm) doesn't exist.)
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-copy to webdav (git annex copy --to 1und1 some/file)
-output of basically "strace git annex ... | grep media":
-
-9871  stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount",  <unfinished ...>
-9871  stat64("/media/1und1/git-annex/3W/Qm/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", 0xb65145d0) = -1 ENOENT (No such file or directory)
-9871  mkdir("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33", 0777 <unfinished ...>
-9871  statfs("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/",  <unfinished ...>
-9871  stat64("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
-9871  open("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK|O_LARGEFILE, 0666 <unfinished ...>
-9871  stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/",  <unfinished ...>
-9871  chmod("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", 040755 <unfinished ...>
-9871  openat(AT_FDCWD, "/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 15
-9871  unlink("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1" <unfinished ...>
-9871  rmdir("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/" <unfinished ...>
-9871  mkdir("/media/1und1/git-annex/dcf/85a", 0777) = -1 EEXIST (File exists)
-9871  stat64("/media/1und1/git-annex/dcf/85a", {st_mode=S_IFDIR|0755, st_size=64, ...}) = 0
-9871  stat64("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
-9871  rename("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", "/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/" <unfinished ...>
-9871  openat(AT_FDCWD, "/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 15
-9871  stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", {st_mode=S_IFREG|0644, st_size=11705, ...}) = 0
-9871  chmod("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", 0100444) = 0
-9871  stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", {st_mode=S_IFDIR|0755, st_size=152, ...}) = 0
-9871  chmod("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", 040555 <unfinished ...>
-
-fsck webdav, but fails (git annex fsck --from 1und1 some/file):
-
-10208 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount",  <unfinished ...>
-10208 stat64("/media/1und1/git-annex/3W/Qm/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", 0xb6428160) = -1 ENOENT (No such file or directory)
-
-
-manual file creation:
-chmod u+w ...
-echo -n 1 > /media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount
-chmod u-w ...
-
-
-fsck webdav again, now all is fine ("fixing location log"):
-10670 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", {st_mode=S_IFREG|0444, st_size=1, ...}) = 0
-10670 open("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE) = 14
-10670 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", {st_mode=S_IFREG|0444, st_size=11705, ...}) = 0
-10670 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", {st_mode=S_IFREG|0444, st_size=1, ...}) = 0
-10670 open("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE) = 14
-10670 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", {st_mode=S_IFREG|0444, st_size=11705, ...}) = 0
-10672 open("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE) = 20
-# End of transcript or log.
-"""]]
-
-> There was a bug that caused it not to write the chunkcount file.
-> I have fixed it, and put in a workaround so fsck, etc, will
-> see that the file is stored on the remote despite there being no
-> chunkcount file present. [[done]] --[[Joey]]
diff --git a/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work/comment_1_77629f620b28ac62364de44b41fa539d._comment b/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work/comment_1_77629f620b28ac62364de44b41fa539d._comment
deleted file mode 100644
index d5ad2d88d..000000000
--- a/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work/comment_1_77629f620b28ac62364de44b41fa539d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlqOu7P4tb4D-Xo2pYrjln2NsAObtErliM"
- nickname="Alexander"
- subject="comment 1"
- date="2013-10-27T07:00:01Z"
- content="""
-thanks!
-"""]]
diff --git a/doc/bugs/cross_platform_permissions_woes.mdwn b/doc/bugs/cross_platform_permissions_woes.mdwn
deleted file mode 100644
index d67ca4ae0..000000000
--- a/doc/bugs/cross_platform_permissions_woes.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-a little introduction:
-i am forced to use windows on my work laptop and workstation, also my wife needs windows.
-my "servers" would be linux, i am actually using fedora and i upgraded from fc17 since i was not able to get a recent version of git annex to compile there.
-
-what happens, is that once i try to copy from the windows machine where the file is to the linux through ssh+rsync, i receive this error - as long as the user owning the linux repository isn't root:
-
-    c:\locale>git annex copy --to linux myfile
-    copy myfile (checking linux...) (to linux...)
-    rsync: failed to open "/linux/annex/tmp/SHA256E-s10--937a89b559820f8658892"
-    myfile
-          10 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-    rsync error: syntax or usage error (code 1) at /home/lapo/package/rsync-3.0.9-1/src/rsyn
-    total size is 10  speedup is 0.09
-    failed
-    git-annex: copy: 1 failed
-
-the file in tmp has no permissions at all:
-
-    me@linux annex]$ ls -lart tmp/SHA256E-s10--937a89b559820f86588921ef3eb12c13074d078b62ef205bb597bf2e895408c3
-    ----------. 1 me me 10 Oct 13 22:50 tmp/SHA256Es10--937a89b559820f86588921ef3eb12c13074d078b62ef205bb597bf2e895408c3
-
-(just consider the following if the above makes any sense:) in another case (i cannot reproduce it now, possibly due to having upgraded git annex from some 2012 release), it happened that a failed download via copy/move from linux to windows (failed for permissions) would not be recorded as failed (on windows side), causing files to possibly be killed at the first subsequent drop command.
-
-my question is: are these 0-permissions on tmp files a bug or just due to some ignorance i did put in setting up the git/annex repo ? is a git/annex repo to be run solely as root/sudoer ? or shall i take any other step in configuring it ? 
-
-technicalities:
-
-"client": windows version:
-
-    git-annex version: 4.20131002-gf25991c
-
-"server": linux version:
-
-    git-annex version: 3.20130207
-
-> [[done]]; fixed in newer git-annex versions. --[[Joey]]
diff --git a/doc/bugs/cross_platform_permissions_woes/comment_1_7f01104de38a6a319a8f36aa1dc8b4b3._comment b/doc/bugs/cross_platform_permissions_woes/comment_1_7f01104de38a6a319a8f36aa1dc8b4b3._comment
deleted file mode 100644
index a3116cdcf..000000000
--- a/doc/bugs/cross_platform_permissions_woes/comment_1_7f01104de38a6a319a8f36aa1dc8b4b3._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="64.134.31.139"
- subject="comment 1"
- date="2013-10-15T18:29:10Z"
- content="""
-Based on the '/linux/annex/' path, your \"linux\" git remote is set up using some sort of network mount of your Linux box to Windows. 
-
-If that's the case, then rsync is running on Windows and probably doesn't know anything about permissions, to probably does something horrible when it's told to write a file to the linux filesystem.
-
-If I'm right about that, I can easily fix it, by making git-annex on Windows not use rsync for such file to file copies. But I first need you to verify if I'm right about how your \"linux\" git remote is configured.
-
-(Also, you should be able to work around the problem by changing the git remote to use a ssh:// url to the linux system.)
-"""]]
diff --git a/doc/bugs/cross_platform_permissions_woes/comment_2_0a34e11b466fad287325425e76487fa1._comment b/doc/bugs/cross_platform_permissions_woes/comment_2_0a34e11b466fad287325425e76487fa1._comment
deleted file mode 100644
index 8ee7c18a5..000000000
--- a/doc/bugs/cross_platform_permissions_woes/comment_2_0a34e11b466fad287325425e76487fa1._comment
+++ /dev/null
@@ -1,73 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmCzVCPjgg_Un_114P8iiSwExms0G2csCA"
- nickname="Michele"
- subject="details about my problem"
- date="2013-10-15T23:30:26Z"
- content="""
-Thank for your answer, but unfortunately the remote is already an ssh (although i agree it should happen most certainly also via samba/cifs mount). 
-it happens as long as the remote is NOT defined as root login. 
-I suppose it could as well be something with my setup (although i've tried different windows/linux hosts) and I have no idea how to debug it.
-
-this is a transcript of recreating the problem (i've just edited user/hostname):
-	 
-	 Microsoft Windows [Version 6.1.7601]
-     C:\>git init wintest
-     Initialized empty Git repository in C:/wintest/.git/
-     C:\>cd wintest
-     C:\wintest>git annex init wintest
-     init wintest
-       Detected a crippled filesystem.
-       Enabling direct mode.
-       Detected a filesystem without fifo support.
-       Disabling ssh connection caching.
-     ok
-     (Recording state in git...)
-     C:\wintest>echo \"thisisatest\">wintest
-     C:\wintest>git annex add wintest
-     add wintest (checksum...) ok
-     (Recording state in git...)
-     C:\wintest>git remote add remote ssh://me@linuxbox/home/me/testlinux
-     C:\wintest>ssh me@linuxbox
-     [me@home ~]$ git init --bare testlinux
-     Initialized empty Git repository in /home/me/testlinux/
-     [me@home ~]$ cd testlinux/
-     [me@home testlinux]$ git annex init linux
-     init linux ok
-     (Recording state in git...)
-     [me@home testlinux]$ exit
-     C:\wintest>git annex sync
-     commit
-     ok
-     pull remote
-     warning: no common commits
-     remote: Counting objects: 5, done.
-     remote: Compressing objects: 100% (3/3), done.
-     remote: Total 5 (delta 1), reused 0 (delta 0)
-     Unpacking objects: 100% (5/5), done.
-     From ssh://linux/home/me/testlinux
-      * [new branch]      git-annex  -> remote/git-annex
-     ok
-     (merging remote/git-annex into git-annex...)
-     (Recording state in git...)
-     push remote
-     Counting objects: 18, done.
-     Delta compression using up to 2 threads.
-     Compressing objects: 100% (12/12), done.
-     Writing objects: 100% (16/16), 1.45 KiB, done.
-     Total 16 (delta 2), reused 0 (delta 0)
-     To ssh://me@linux/home/michele/testlinux
-      * [new branch]      git-annex -> synced/git-annex
-      * [new branch]      master -> synced/master
-     ok
-     C:\wintest>git annex copy --to remote wintest
-     copy wintest (checking remote...) (to remote...)
-     wintest
-               15 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-     
-     rsync error: syntax or usage error (code 1) at /home/lapo/package/rsync-3.0.9-1/src/rsync-3.0.9/main.c(1052) [sender=
-     total size is 15  speedup is 0.13
-     failed
-     git-annex: copy: 1 failed
-     
-     C:\wintest>
-"""]]
diff --git a/doc/bugs/cross_platform_permissions_woes/comment_3_278f91b4bc4c32717ab1c39c2abf9305._comment b/doc/bugs/cross_platform_permissions_woes/comment_3_278f91b4bc4c32717ab1c39c2abf9305._comment
deleted file mode 100644
index 1cfed0a90..000000000
--- a/doc/bugs/cross_platform_permissions_woes/comment_3_278f91b4bc4c32717ab1c39c2abf9305._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="64.134.31.139"
- subject="comment 3"
- date="2013-10-16T15:47:38Z"
- content="""
-I think you will have better luck if you upgrade your server's git-annex version. I checked and some fixes for exactly this problem went in around May. Also, testing with the current version, I followed your procedure exactly and did not see the problem.
-"""]]
diff --git a/doc/bugs/cross_platform_permissions_woes/comment_4_eb6a271cb63c71341469c9ff89dc0eb9._comment b/doc/bugs/cross_platform_permissions_woes/comment_4_eb6a271cb63c71341469c9ff89dc0eb9._comment
deleted file mode 100644
index 08ebe1e6d..000000000
--- a/doc/bugs/cross_platform_permissions_woes/comment_4_eb6a271cb63c71341469c9ff89dc0eb9._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmCzVCPjgg_Un_114P8iiSwExms0G2csCA"
- nickname="Michele"
- subject="solved"
- date="2013-10-18T21:00:38Z"
- content="""
-installing very recent version on linux solved the problem !!! indeed a bug, but an old one! (quite difficult to get an updated version with cabal on fc19 and so forth, i would add a couple suggestion to share in the fedora install page)
-thank you 
-"""]]
diff --git a/doc/bugs/cyclic_drop.mdwn b/doc/bugs/cyclic_drop.mdwn
deleted file mode 100644
index 296d61aac..000000000
--- a/doc/bugs/cyclic_drop.mdwn
+++ /dev/null
@@ -1,104 +0,0 @@
-drop's verification that a remote still has content can fail
-if the remote is also dropping the content at the same time. Each
-repository checks that the other still has the content, and then both
-drop it. Could also happen with larger cycles of repositories.
-
-> Confirmed fixed now. All cases tested. [[done]]
-
----
-
-Fixing this requires locking. (Well, there are other ways, like moving the
-content to a holding area when checking if it's safe to drop, but they
-seem complicated, and would be hard to implement for move --from.)
-
-Add per-content lock files. An exclusive lock is held on content when
-it's in the process of being dropped, or moved. The lock is taken
-nonblocking; if it cannot be obtained, something else is acting on the
-content and git-annex should refuse to do anything.
-
-Then when checking inannex, try to take a shared lock. Note that to avoid
-deadlock, this must be a nonblocking lock. (Actually, with fcntl locking,
-can just check if there is a lock, without needing to take one.) 
-If it fails, the status of the content is unknown, so inannex should fail.
-Note that this failure needs to be distinguishable from "not in annex".
-
-> Thinking about these lock files, this would be a lot more files, 
-> and would possibly break some assumptions that everything in
-> `.git/annex/objects` is a key's content. (Or would need lots more
-> directories to put the lock files elsewhere.) There would be more
-> overhead to manage these and have them on disk.
-> 
-> What if it just locked the actual content file? The obvious limitation
-> is only content that was already inannex could be locked, but that
-> happens to be exactly what's needed here; if content is not present,
-> it's not going to get dropped or moved.
->
-> Of course, if some consumer of a file locked it, then it could prevent it
-> from being dropped or moved. This could be considered a bug, or a feature. :)
-> 
-> However, this would mean that such a hypothetical consumer could also
-> make inannex checks fail.
->
-> The other downside is that, for fcntl exclusive locking, the file has to
-> be opened for write. Normally the modes of content files are locked down
-> to prevent modifcation. Dealt with, but oh so nasty. Almost makes flock
-> locking seem worth using.
-
----
-
-drop --from could also cycle. Locking should fix.
-
-> Confirmed fixed now. 
-
----
-
-move --to can also be included in the cycle, since it can drop data. 
-
-Consider move to a remote that already has the content and 
-is at the same time doing a drop (or a move). The remote
-verifies the content is present on the movee, and removes its copy.
-The movee removes its copy.
-
-So move --to needs to take the content lock on start. Then the inannex
-will fail.
-
-This is why it's important for inannex to fail in a way that is
-distinguishable from "not in annex". Otherwise, move --to
-would see the cycle as the remote not having content, and try to
-redundantly send it, drop it locally, and still race.
-
-> Confirmed fixed now.
-
--- 
-
-move --from is similar. Consider a case where both the local and the remote
-are doing a move --from. Both have the content, and confirm the other does,
-via inannex checks. Then both run git-annex-shell dropkey, removing both
-copies.
-
-So move --from needs to take the content lock on start, so the inannex will
-fail.  NB: If the content is not locally present, don't take the lock.
-
-> Confirmed fixed now.
-
----
-
-Another cycle might be running move --to and move --from on the same file,
-locally. The exclusivity of the content lock solves this, as only one can
-run at a time.
-
-Would it work with a shared lock? The --to would run git-annex-shell
-inannex. The --from would also be running, and would run git-annex-shell
-dropkey. So inannex and dropkey would end up running on the remote
-at the same time. Dropkey takes the content lock, and inannex checks it,
-but what if inannex runs first? Then it returns true, and then the content
-is removed, so both the --to and --from see success and the --to proceeds
-to remove the local content that the --from already caused to be removed
-from the remote. So, no, the nasty exclusive lock is needed.
-
-> Confirmed fixed now.
-
----
-
-Another cycle might involve move --from and drop, both run on the same
-file, locally. Again, the exclusive lock solves this.
diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn
deleted file mode 100644
index 8007ae11f..000000000
--- a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn
+++ /dev/null
@@ -1,199 +0,0 @@
-### Please describe the problem.
-Data loss due to incorrect merge of repos in direct mode. (I tested the same scenario in indirect mode and it worked fine there)
-
-Given 2 repos A and B, in direct mode:
-
-1. in A: mkdir f, with a file f in it
-2. in B: touch f
-3. in B: sync 
-
-Result: Only an f.variant-f###remains, which is file f of B, and the merge conflict has already been automatically resolved. I.e. Directory f containing file f, is lost.
-
-Expected result: remaining contents: f.variant-AAA which is file f of B, f.variant-BBB which is directory f of A, containing a file f. Merge conflict marked resolved.
-
-### What steps will reproduce the problem?
-Execute the script given below in additional information.
-
-### What version of git-annex are you using?
-git-annex version: 4.20130911-g6625d0e
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi
-
-### On what operating system?
-Linux basementcat 3.10.10-1-ARCH #1 SMP PREEMPT Fri Aug 30 11:30:06 CEST 2013 x86_64 GNU/Linux
-
-### Please provide any additional information below.
-
-[[!format sh """
-[~]$ mkdir test
-[~/test]$ mkdir a
-[~/test/a]$ git init
-Initialized empty Git repository in /home/limyreth/test/a/.git/
-[~/test/a]$ git annex init test
-init test ok
-(Recording state in git...)
-[~/test/a]$ touch firstfile
-[~/test/a]$ git annex add firstfile 
-add firstfile (checksum...) ok
-(Recording state in git...)
-[~/test/a]$ git annex sync
-commit  
-ok
-git-annex: no branch is checked out
-[~]$ git clone test/a
-Cloning into 'a'...
-done.
-[~]$ mv a test/b
-[~/test/a]$ git annex direct
-commit  
-# On branch master
-nothing to commit, working directory clean
-ok
-direct firstfile ok
-direct  ok
-[~/test/a]$ ls -l
-total 0
--rw-r--r-- 1 limyreth users 0 Oct 12 15:09 firstfile
-[~/test/a]$ mkdir f
-[~/test/a]$ touch f/f
-[~/test/a]$ git annex add f/f
-add f/f (checksum...) ok
-(Recording state in git...)
-[~/test/a]$ git annex sync
-commit  
-ok
-[~/test/b]$ git remote -v
-origin	/home/limyreth/test/a (fetch)
-origin	/home/limyreth/test/a (push)
-[~/test/b]$ ls
-firstfile
-[~/test/b]$ git annex direct
-commit  
-(Recording state in git...)
-# On branch master
-nothing to commit, working directory clean
-ok
-direct  ok
-[~/test/b]$ touch f
-[~/test/b]$ git annex add f
-add f (checksum...) ok
-(Recording state in git...)
-[~/test/b]$ git annex sync
-(merging origin/git-annex into git-annex...)
-(Recording state in git...)
-commit  
-ok
-pull origin 
-remote: Counting objects: 14, done.
-remote: Compressing objects: 100% (7/7), done.
-remote: Total 9 (delta 1), reused 0 (delta 0)
-Unpacking objects: 100% (9/9), done.
-From /home/limyreth/test/a
-   2a8fa45..ad6802d  master     -> origin/master
-   1f39016..19e3e12  git-annex  -> origin/git-annex
- * [new branch]      synced/master -> origin/synced/master
-
-Adding f/f
-CONFLICT (file/directory): There is a directory with name f in refs/remotes/origin/master. Adding f as f~HEAD
-Automatic merge failed; fix conflicts and then commit the result.
-f: needs merge
-(Recording state in git...)
-ok
-[master 37a8019] git-annex automatic merge conflict fix
-
-Already up-to-date.
-ok
-(merging origin/git-annex into git-annex...)
-(Recording state in git...)
-push origin 
-Counting objects: 36, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (20/20), done.
-Writing objects: 100% (25/25), 2.16 KiB | 0 bytes/s, done.
-Total 25 (delta 5), reused 0 (delta 0)
-To /home/limyreth/test/a
-   ad6802d..37a8019  master -> synced/master
- * [new branch]      git-annex -> synced/git-annex
-ok
-[~/test/b]$ ls -l
-total 0
--rw-r--r-- 1 limyreth users 0 Oct 12 15:11 firstfile
--rw-r--r-- 1 limyreth users 0 Oct 12 15:11 f.variant-f874
-[~/test/b]$ git log --summary
-commit 37a80199abe3cf82100bbdb5dd2217ed6bcb4b62
-Merge: 5a8942a ad6802d
-Author: timdiels <timdiels.m@gmail.com>
-Date:   Sat Oct 12 15:11:47 2013 +0200
-
-    git-annex automatic merge conflict fix
-
-commit 5a8942a9a1735cb313c1f6624cbd3f48b252d9d9
-Author: timdiels <timdiels.m@gmail.com>
-Date:   Sat Oct 12 15:11:47 2013 +0200
-
-    git-annex automatic sync
-
- create mode 120000 f
-
-commit ad6802dc231d389b86154e2df900a70b18e17b29
-Author: timdiels <timdiels.m@gmail.com>
-Date:   Sat Oct 12 15:11:40 2013 +0200
-
-    git-annex automatic sync
-
- create mode 120000 f/f
-
-commit 2a8fa45bea996ab5ae219a017d4b642153e6d9c9
-Author: timdiels <timdiels.m@gmail.com>
-Date:   Sat Oct 12 15:09:40 2013 +0200
-
-    git-annex automatic sync
-
- create mode 120000 firstfile
-[~/test/a]$ git annex sync
-(merging synced/git-annex into git-annex...)
-commit  
-ok
-merge synced/master 
-Updating ad6802d..37a8019
-Fast-forward
- f.variant-f874 | 1 +
- f/f            | 1 -
- 2 files changed, 1 insertion(+), 1 deletion(-)
- create mode 120000 f.variant-f874
- delete mode 120000 f/f
-ok
-[~/test/a]$ git log --summary
-commit 37a80199abe3cf82100bbdb5dd2217ed6bcb4b62
-Merge: 5a8942a ad6802d
-Author: timdiels <timdiels.m@gmail.com>
-Date:   Sat Oct 12 15:11:47 2013 +0200
-
-    git-annex automatic merge conflict fix
-
-commit 5a8942a9a1735cb313c1f6624cbd3f48b252d9d9
-Author: timdiels <timdiels.m@gmail.com>
-Date:   Sat Oct 12 15:11:47 2013 +0200
-
-    git-annex automatic sync
-
- create mode 120000 f
-
-commit ad6802dc231d389b86154e2df900a70b18e17b29
-Author: timdiels <timdiels.m@gmail.com>
-Date:   Sat Oct 12 15:11:40 2013 +0200
-
-    git-annex automatic sync
-
- create mode 120000 f/f
-
-commit 2a8fa45bea996ab5ae219a017d4b642153e6d9c9
-Author: timdiels <timdiels.m@gmail.com>
-Date:   Sat Oct 12 15:09:40 2013 +0200
-
-    git-annex automatic sync
-
- create mode 120000 firstfile
-
-"""]]
-
-> Bug fixed; test case added; [[done]] --[[Joey]]
diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_1_294c33af08649256908a97894f93c05d._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_1_294c33af08649256908a97894f93c05d._comment
deleted file mode 100644
index 1b22d2ce5..000000000
--- a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_1_294c33af08649256908a97894f93c05d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg"
- nickname="Tim"
- subject="comment 1"
- date="2013-10-13T12:35:47Z"
- content="""
-I've just tested a similar scenario with 2 conflicting files, a file-file conflict, and then it works fine. That makes sense, as there's a test written for that.
-
-So the specific bits are: directory-file conflict of repos in direct mode.
-"""]]
diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment
deleted file mode 100644
index 7df35b33d..000000000
--- a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="64.134.31.139"
- subject="comment 2"
- date="2013-10-16T18:04:27Z"
- content="""
-I can confirm this bug, thanks for a good reproduction recipe.
-
-However, there is no actual data loss. If you switch to repo to indirect mode, you can use `git checkout` to check out the past versions from before the botched merge. When you do, you'll find that the files that the merge seemingly deleted in fact still have their contents present. It is preserved in `.git/annex/objects` by the automatic merge conflict resolution code, which does that whenever it deletes a file, whether for good reasons or for buggy reasons.
-
-So if you feel you lost data due to this, you can almost certainly get it back and I'm happy to help with that.
-
-
-"""]]
diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_3_d296ef26fc90f4e3166bba6d2de0a1ee._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_3_d296ef26fc90f4e3166bba6d2de0a1ee._comment
deleted file mode 100644
index 4adee73bd..000000000
--- a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_3_d296ef26fc90f4e3166bba6d2de0a1ee._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg"
- nickname="Tim"
- subject="comment 3"
- date="2013-10-17T16:04:03Z"
- content="""
-I had a recent backup of the data so no real harm was done.
-"""]]
diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_4_33ba2c890c962a71ae9fadc417359f8e._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_4_33ba2c890c962a71ae9fadc417359f8e._comment
deleted file mode 100644
index bff93623c..000000000
--- a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_4_33ba2c890c962a71ae9fadc417359f8e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg"
- nickname="Tim"
- subject="comment 4"
- date="2013-10-31T19:44:34Z"
- content="""
-Has this issue been fixed? I checked out the repository today and compiled with cabal, but I don't see a f.variant-A and a f.variant-B pop up after sync.
-"""]]
diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_5_39eb0bb96fd271bd0de4a3a40814ae1b._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_5_39eb0bb96fd271bd0de4a3a40814ae1b._comment
deleted file mode 100644
index 0e5d67f74..000000000
--- a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_5_39eb0bb96fd271bd0de4a3a40814ae1b._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 5"
- date="2013-11-01T15:48:21Z"
- content="""
-AFAIK this bug is fixed, which is why I wrote above, \"Bug fixed; test case added; done\"
-
-If you have reason to think otherwise, better follow up.
-
-"""]]
diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_6_d80c4b631bdf58901a06f29a2c5682e2._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_6_d80c4b631bdf58901a06f29a2c5682e2._comment
deleted file mode 100644
index 29457da8a..000000000
--- a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_6_d80c4b631bdf58901a06f29a2c5682e2._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg"
- nickname="Tim"
- subject="comment 6"
- date="2013-11-14T14:58:10Z"
- content="""
-Ah indeed, tried it again and it's indeed fixed. Tried some other things as well, and conflict resolution ended up doing just fine.
-"""]]
diff --git a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_.mdwn b/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_.mdwn
deleted file mode 100644
index 65560f245..000000000
--- a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-**What steps will reproduce the problem?**
-
-> git annex add .
-
-**What is the expected output? What do you see instead?**
-
-This was with direct mode turned on.  Distinct files should remain distinct.  Instead, many of the original files were overwritten and became copies of one of the other files.
-
-**What version of git-annex are you using? On what operating system?**
-
-Running rooted android on a Samsung Galaxy Nexus.  Working in a system directory which is not "crippled".
-The git-annex package was dated 2013-03-23 and downloaded from
-> https://downloads.kitenet.net/git-annex/android/current/
-
-**Please provide any additional information below.**
-
-I wish I could provide files that became duplicates, but I didn't make copies before adding them...  Did this twice, first adding JPG and MP4 files, then adding WAVs.  After that, I saw that of 100 JPGs and 8 MP4s, about half the JPGs and all of the MP4s had become copies of a single JPG.  Of 11 WAV files, two had been replaced with copies of one of the others.
-
-> [[done]]; turned out to be Android bug unrelated to git-annex. --[[Joey]]
diff --git a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_1_eb6db7f6a156a065e2724c2de5fc4366._comment b/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_1_eb6db7f6a156a065e2724c2de5fc4366._comment
deleted file mode 100644
index a0af0bc8f..000000000
--- a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_1_eb6db7f6a156a065e2724c2de5fc4366._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-01T18:28:21Z"
- content="""
-Are you sure these files did not already have the same content before you ran git-annex on them?
-
-Can you show me the output of `git show` when run on some of these files?
-"""]]
diff --git a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_2_59a96cade9e4881767562a139fc7fb4b._comment b/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_2_59a96cade9e4881767562a139fc7fb4b._comment
deleted file mode 100644
index f62c2e69e..000000000
--- a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_2_59a96cade9e4881767562a139fc7fb4b._comment
+++ /dev/null
@@ -1,40 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn26WQjIP5fnMgQF_L_k3Q3UrR5v8mjRTY"
- nickname="Ellis"
- subject="comment 2"
- date="2013-04-02T20:18:05Z"
- content="""
-*Are you sure these files did not already have the same content before you ran git-annex on them?*
-
-Yes, each one was a distinct photo, video, or audio recording.  The only operation performed between creation and ``git annex add`` was moving them into the import directory from the command line via e.g. ``mv /sdcard/DCIM/Camera/* .``.
-
-If you'd like, I'll try to find a set of files to reproduce the problem with.
-
-*Can you show me the output of git show when run on some of these files?*
-
-Sure.  Here are two WAV files.  The first one was correctly stored, and the second one is now a duplicate of the first.
-
-    commit bb282af90745c8a50e74c1f724e6cc708bfa9591
-    Author: Ellis Whitehead <ellis@****>
-    Date:   Mon Apr 1 17:05:19 2013 +0200
-
-        git-annex automatic sync
-
-    diff --git a/import/2013-03-02_13-57-08_jeromin.wav b/import/2013-03-02_13-57-08_jeromin.wav
-    new file mode 120000
-    index 0000000..55a8cf1
-    --- /dev/null
-    +++ b/import/2013-03-02_13-57-08_jeromin.wav
-    @@ -0,0 +1 @@
-    +../.git/annex/objects/VG/vf/SHA256E-s49222316--acd9b8f94981543c601461c4cb602dae4e7d9d9a72654a3915c6e9d0221791b7.wav/SHA256E-s49222316--acd9b8f94981543c601461c4cb602dae4e7d9d9a72654a3915c6e9d0221791b7.wav
-    \ No newline at end of file
-    diff --git a/import/2013-03-02_14-06-11_karina.wav b/import/2013-03-02_14-06-11_karina.wav
-    new file mode 120000
-    index 0000000..55a8cf1
-    --- /dev/null
-    +++ b/import/2013-03-02_14-06-11_karina.wav
-    @@ -0,0 +1 @@
-    +../.git/annex/objects/VG/vf/SHA256E-s49222316--acd9b8f94981543c601461c4cb602dae4e7d9d9a72654a3915c6e9d0221791b7.wav/SHA256E-s49222316--acd9b8f94981543c601461c4cb602dae4e7d9d9a72654a3915c6e9d0221791b7.wav
-    \ No newline at end of file
-
-"""]]
diff --git a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_3_bf9d2562d66f0f6a9478ac178606cf4e._comment b/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_3_bf9d2562d66f0f6a9478ac178606cf4e._comment
deleted file mode 100644
index 2cc257839..000000000
--- a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_3_bf9d2562d66f0f6a9478ac178606cf4e._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-02T21:34:50Z"
- content="""
-The truely odd thing about this is that when git-annex adds a direct mode file, it does *not* touch the file at all. The file is left right where it is.
-
-This is even the case if two files have the same SHA checksum. I have just verified that even in this case; neither file is touched in any way by `git annex add`.
-
-(Obviously, I never saw anything like this when working with git-annex on Android. I hope this is not some evil April Fools prank.)
-"""]]
diff --git a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_4_ad0dbdc448fff2e126ffec9aac6d7463._comment b/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_4_ad0dbdc448fff2e126ffec9aac6d7463._comment
deleted file mode 100644
index 47c53ac84..000000000
--- a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_4_ad0dbdc448fff2e126ffec9aac6d7463._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn26WQjIP5fnMgQF_L_k3Q3UrR5v8mjRTY"
- nickname="Ellis"
- subject="comment 4"
- date="2013-04-03T09:02:44Z"
- content="""
-*The truely odd thing about this is that when git-annex adds a direct mode file, it does not touch the file at all. The file is left right where it is.*
-
-After further investigation, I've managed to reproduce the error, and it is **not** caused by git-annex, but by a limitation in my device's sdcard overlay (I can now see that I was using it in an unintended fashion).  Sorry to have taken your time with this.  However, the following information may be useful for others who might also want to use git-annex from the android console to manager their media.
-
-Some android devices don't have sdcards (they are the ones which want you to use MTP (Media Transfer Protocol) to transfer data via a USB cable).  These devices emulate an sdcard for use by apps.  On my Samsung Galaxy Nexus, the emulated sdcard is at ``/sdcard``.  If your device is rooted, you will find the equivalent \"real\" filesystem at ``/data/media/0``.  There is apparently a limitation in the sdcard emulator which causes ``mv`` commands involving multiple files to semi-randomly fail when moving files from ``/sdcard`` to ``/data/media/0``.  What happens is that the command will randomly tend to replace some of the files in the move with a hardlink to another one of the files.  I have encountered no problems when moving files from ``/sdcard`` any other destination.
-
-So **don't do this** (or variants of it):
-
-    $ mv /sdcard/DCIM/Camera/* /data/media/0/annex-on-a-good-fs/import
-
-My reason for placing the repository under ``/data/media/0/`` is so that git-annex can use a non-crippled filesystem, but at the same time other apps can access the data under ``/sdcard``.  To get around the above problem, either of these two commands can be used:
-
-    $ mv /sdcard/DCIM/Camera/* /sdcard/annex-on-a-good-fs/import
-    $ mv /data/media/0/DCIM/Camera/* /data/media/0/annex-on-a-good-fs/import
-
-@joey: the instructions say to link this bug to ``done`` when it's closed, but I don't see how to do that?  Or should it be deleted, since it wasn't a git-annex bug at all?
-"""]]
diff --git a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_5_e828585e56b10710598143483ce362b6._comment b/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_5_e828585e56b10710598143483ce362b6._comment
deleted file mode 100644
index 847226699..000000000
--- a/doc/bugs/data_loss_with___34__git_annex_add__34___on_android_in_direct_mode_/comment_5_e828585e56b10710598143483ce362b6._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-04-04T16:03:50Z"
- content="""
-I'll close the bug.
-
-FWIW, I developed git-annex on an Android device with such an emulated filesystem for /sdcard. It's a FUSE filesystem with a terrible implementation. I found multiple syscalls that just failed, and was careful to avoid using them.
-
-Personally, the benefits of non-crippled filesystem do not seem worth the bother of doing what you're doing..
-"""]]
diff --git a/doc/bugs/detected_bad_bare_repository_with___60__SCREECH__62___files.mdwn b/doc/bugs/detected_bad_bare_repository_with___60__SCREECH__62___files.mdwn
deleted file mode 100644
index 0bd01056a..000000000
--- a/doc/bugs/detected_bad_bare_repository_with___60__SCREECH__62___files.mdwn
+++ /dev/null
@@ -1,73 +0,0 @@
-### Please describe the problem.
-
-Fun one: I have a backup repository created with the assistant. For some reason it's a bare repository, not sure why. It makes my hard drive scream with pain.
-
-### What steps will reproduce the problem?
-
-When I tried `git annex copy --to backup`, I saw this:
-
-[[!format sh """
-[2014-01-29 23:46:03 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","show-ref","git-annex"]
-[2014-01-29 23:46:04 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","show-ref","--hash","refs/heads/g
-[2014-01-29 23:46:11 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..ac42
-[2014-01-29 23:46:12 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..9ab4
-[2014-01-29 23:46:22 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..5795
-[2014-01-29 23:46:22 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..8006
-[2014-01-29 23:46:22 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..320e
-[2014-01-29 23:46:22 EST] chat: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","cat-file","--batch"]
-[2014-01-29 23:46:22 EST] read: git ["config","--null","--list"]
-[2014-01-29 23:46:22 EST] call: git ["--git-dir=/media/c7a29cf9-ad3e-42a8-8dd5-0f5618c218ee/mp3/.git","--work-tree=/med
-[2014-01-29 23:46:22 EST] read: git ["config","--null","--list"]
-[2014-01-29 23:46:22 EST] Detected bad bare repository with
-"""]]
-
-Then this stopped and my hard drive started scratching. It makes this horrible screeching sound because it's quite old, hence the bug title.
-
-It seems that this debug message tries to list all the objects in the filesystem, which in this case is quite large:
-
-[[!format haskell """
-fixBadBare :: Annex ()
-fixBadBare = whenM checkBadBare $ do
-        ks <- getKeysPresent
-        liftIO $ debugM "Init" $ unwords
-                [ "Detected bad bare repository with"
-                , show (length ks)
-                , "objects; fixing"
-                ]
-"""]]
-
-Maybe this could be skipped? It takes forever (7 minutes) to compute that length (21353 objects)...
-
-### What version of git-annex are you using? On what operating system?
-
-5.20140102-gd93f946, provided by joeyh as part of [[bugs/assistant_eats_all_CPU/]].
-
-### Please provide any additional information below.
-
-Here's the complete transcript of that copy:
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[2014-01-29 23:46:03 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","show-ref","git-annex"]
-[2014-01-29 23:46:04 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","show-ref","--hash","refs/heads/g
-[2014-01-29 23:46:11 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..ac42
-[2014-01-29 23:46:12 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..9ab4
-[2014-01-29 23:46:22 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..5795
-[2014-01-29 23:46:22 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..8006
-[2014-01-29 23:46:22 EST] read: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","log","refs/heads/git-annex..320e
-[2014-01-29 23:46:22 EST] chat: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","cat-file","--batch"]
-[2014-01-29 23:46:22 EST] read: git ["config","--null","--list"]
-[2014-01-29 23:46:22 EST] call: git ["--git-dir=/media/c7a29cf9-ad3e-42a8-8dd5-0f5618c218ee/mp3/.git","--work-tree=/med
-[2014-01-29 23:46:22 EST] read: git ["config","--null","--list"]
-[2014-01-29 23:46:22 EST] Detected bad bare repository with 21353 objects; fixing
-[2014-01-29 23:53:06 EST] call: git ["--git-dir=/media/c7a29cf9-ad3e-42a8-8dd5-0f5618c218ee/mp3","config","core.bare","true"]
-[2014-01-29 23:53:06 EST] read: git ["config","--null","--list"]
-[2014-01-29 23:53:06 EST] chat: git ["--git-dir=/media/c7a29cf9-ad3e-42a8-8dd5-0f5618c218ee/mp3","cat-file","--batch"]
-[2014-01-29 23:57:22 EST] call: git ["--git-dir=/srv/mp3/.git","--work-tree=/srv/mp3","config","remote..annex-uuid","c32322fa-8873-4635-8d4c-1dc27977eb6f"]
-[2014-01-29 23:57:22 EST] read: git ["config","--null","--list"]
-# End of transcript or log.
-"""]]
-
-> [[done]] per my comment --[[Joey]]
diff --git a/doc/bugs/detected_bad_bare_repository_with___60__SCREECH__62___files/comment_1_523b80ad81ad49bddfb8855d12d5561d._comment b/doc/bugs/detected_bad_bare_repository_with___60__SCREECH__62___files/comment_1_523b80ad81ad49bddfb8855d12d5561d._comment
deleted file mode 100644
index a1d853275..000000000
--- a/doc/bugs/detected_bad_bare_repository_with___60__SCREECH__62___files/comment_1_523b80ad81ad49bddfb8855d12d5561d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.199"
- subject="comment 1"
- date="2014-01-30T18:33:22Z"
- content="""
-To fix this problem, git-annex has to find all the keys in the repository. This is necessarily an expensive operation when the repository is that large. Printing out the count of them does not take any appreciable additional time.
-
-This is a one-time fix up. Once you let git-annex run and fix your repository, you should not be bothered by it again.
-"""]]
diff --git a/doc/bugs/direct_mode_renames.mdwn b/doc/bugs/direct_mode_renames.mdwn
deleted file mode 100644
index 60f449300..000000000
--- a/doc/bugs/direct_mode_renames.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-When in direct mode, renaming a file with `git mv` does not update the
-direct mode mapping to use the new filename. --[[Joey]]
-
-Consistency checks now prevent anything bad happening when the mapping file
-contains old filenames. Still, missing the new filename will prevent that
-file working properly in direct mode.
-
-Perhaps the pre-commit hook needs to update the mapping for files that were
-deleted or added.
-
-This also affects moves of files when the assistant is being used.
-In this case, the assistant updates the mapping to add the new name,
-but does not delete the old name from the mapping.
-
-> [[done]]; the pre-commit hook now updates the mappings. --[[Joey]]
diff --git a/doc/bugs/direct_mode_renames/comment_1_f18c335e0d6f4259d2470935ef391cb8._comment b/doc/bugs/direct_mode_renames/comment_1_f18c335e0d6f4259d2470935ef391cb8._comment
deleted file mode 100644
index aaf43a24e..000000000
--- a/doc/bugs/direct_mode_renames/comment_1_f18c335e0d6f4259d2470935ef391cb8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkZktNHFhxC1kYA9KKdKpYJO4clq9WDsjE"
- nickname="Jason"
- subject="comment 1"
- date="2013-02-06T06:35:21Z"
- content="""
-I'm not sure if this matters, but in my case I wasn't even using `git mv`, I was just using `mv`.
-"""]]
diff --git a/doc/bugs/direct_mode_sync_should_avoid_git_commit.mdwn b/doc/bugs/direct_mode_sync_should_avoid_git_commit.mdwn
deleted file mode 100644
index 498c4d000..000000000
--- a/doc/bugs/direct_mode_sync_should_avoid_git_commit.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-Per forum post linking to this bug, git commit can be very slow when run in a filesystem without symlink support, and seems to be reading the content of files just in order to show typechanged messages in the status.
-
-So, git annex sync should stop using git commit when in direct mode, and instead manually make its own commit. Git.Branch.commit and Git.Branch.update should be able to easily be used for this.
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/direct_mode_sync_should_avoid_git_commit/comment_1_d286800081f019651cd40355b7d5518a._comment b/doc/bugs/direct_mode_sync_should_avoid_git_commit/comment_1_d286800081f019651cd40355b7d5518a._comment
deleted file mode 100644
index 98897593c..000000000
--- a/doc/bugs/direct_mode_sync_should_avoid_git_commit/comment_1_d286800081f019651cd40355b7d5518a._comment
+++ /dev/null
@@ -1,27 +0,0 @@
-[[!comment format=mdwn
- username="TroisSinges"
- ip="82.227.207.5"
- subject="Almost done"
- date="2013-12-15T10:13:50Z"
- content="""
-Hi!
-
-Thank you for the fix, it's much better now. However, in some case, it doesn't work. For example, when I try to add inject a file in the direct repository (rm symlinkedFile ; mv /tmp/myFile symlinkedFile ; git annex add symlinkedFile), it tries to map each file in memory (which takes a very long time through the network).
-
-    # git annex add bigFile --debug
-    [2013-12-15 11:00:00 CET] read: git [\"--git-dir=/Volumes/Video/Annex/.git\",\"--work-tree=/Volumes/Video/Annex\",\"-c\",\"core.bare=false\",\"ls-files\",\"--others\",\"--exclude-standard\",\"-z\",\"--\",\"bigFile\"]
-    [2013-12-15 11:00:00 CET] read: git [\"--git-dir=/Volumes/Video/Annex/.git\",\"--work-tree=/Volumes/Video/Annex\",\"-c\",\"core.bare=false\",\"ls-files\",\"--modified\",\"-z\",\"--\",\"bigFile\"]
-
-If I use lsof, each another file in repository is mapped in memory:
-
-    # lsof -p 30130
-    git     30130 troissinges    3r   REG             46,11 4519526640  3093837953332665982 /Volumes/Video/Annex/AnotherBigFile
-
-My version of software:
-
-    git annex version
-    git-annex version: 5.20131213
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-"""]]
diff --git a/doc/bugs/direct_mode_sync_should_avoid_git_commit/comment_2_4e23201d1d1d549f72eec75987601a73._comment b/doc/bugs/direct_mode_sync_should_avoid_git_commit/comment_2_4e23201d1d1d549f72eec75987601a73._comment
deleted file mode 100644
index 5b1f7ab75..000000000
--- a/doc/bugs/direct_mode_sync_should_avoid_git_commit/comment_2_4e23201d1d1d549f72eec75987601a73._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 2"
- date="2013-12-16T17:14:06Z"
- content="""
-It seems that `ls-files --modified` runs the same code path that commit did to see if the file is changed, which here is a cheap 
-stat, and on your system mmaps and downloads it all.
-
-I cannot see a good way to avoid using `ls-files --modified`.
-
-I think it would be better to fix git.
-"""]]
diff --git a/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__.mdwn b/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__.mdwn
deleted file mode 100644
index 8ee66da19..000000000
--- a/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__.mdwn
+++ /dev/null
@@ -1,51 +0,0 @@
-### Please describe the problem.
-
-When I create a directory special remote, with encryption enabled (shared) and a chunk size restriction (any), I can copy files *to* the remote, but git annex can't find/access them afterwards.
-
-If I do the same, just without specifying chunk size, it works fine. Restricting chunk size on FAT filesystems to something less that 4GB is necessary (otherwise storing bigger files will just fail).
-
-### What steps will reproduce the problem?
-
-Assume `~/annex` is a normal git annex repository and it contains a file `data.file`.
-
-         # cd ~/annex
-         # mkdir /tmp/remote
-         # git annex initremote dirremote type=directory directory=/tmp/remote encryption=shared chunksize="300 megabytes"
-             initremote dirremote (encryption setup) (shared cipher) ok
-             (Recording state in git...)
-         # git annex copy --to dirremote data.file
-             copy data.file (gpg) (to dirremote...)
-             ok
-             (Recording state in git...)
-         # git annex fsck --from dirremote
-             fsck data.file (gpg) (fixing location log)
-               ** Based on the location log, data.file
-               ** was expected to be present, but its content is missing.
-             failed
-             (Recording state in git...)
-             git-annex: fsck: 1 failed
-
-The file is actually in the remote, e.g. `ls -R /tmp/remote` (shortened output):
-
-        /tmp/remote/be5/af7/GPGHMACSHA1--cb23b50579bf69be9cdc0243b6fda1f66218eb43:
-        GPGHMACSHA1--cb23b50579bf69be9cdc0243b6fda1f66218eb43
-        GPGHMACSHA1--cb23b50579bf69be9cdc0243b6fda1f66218eb43.chunkcount
-
-### What version of git-annex are you using? On what operating system?
-
-- mac OS X (10.8.5)
-- git-annex version: 4.20131002-gf25991c
-- `PATH` variable has `/Applications/git-annex.app/Contents/MacOS/bundle` at the front, so if git-annex comes with a binary, it is used
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; see my comment. --[[Joey]]
diff --git a/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_1_69dfbf566c75396cdaaf5ad70f1a94a8._comment b/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_1_69dfbf566c75396cdaaf5ad70f1a94a8._comment
deleted file mode 100644
index e068501ad..000000000
--- a/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_1_69dfbf566c75396cdaaf5ad70f1a94a8._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 1"
- date="2013-10-26T19:06:38Z"
- content="""
-There was a bug that caused it not to write the chunkcount file.
-I have fixed it, and put in a workaround so fsck, etc, will
-see that the file is stored on the remote despite there being no
-chunkcount file present.
-
-I was initially puzzled by your output showing the chunkcount file being present.
-However, the bug also caused it to write a chunkcount file when chunking was disabled (ie, the logic for when to write the file was inverted). 
-So, I think that the ls you show is after you set up the remote without specifying chunk size, and copied a file to it.
-
-Please test with the next autobuild of git-annex (should be one within an hour my my posting this comment) and verify it can now see the files you stored on the remote with chunking.
-
-
-"""]]
diff --git a/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_2_8d09cc0e06548c4ebde7956edd1b5d85._comment b/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_2_8d09cc0e06548c4ebde7956edd1b5d85._comment
deleted file mode 100644
index 81d6b35a3..000000000
--- a/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_2_8d09cc0e06548c4ebde7956edd1b5d85._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://jspk.clavid.com/"
- nickname="flabbergast"
- subject="comment 2"
- date="2013-10-28T09:36:19Z"
- content="""
-Thanks! I've checked now and the problem is gone.
-"""]]
diff --git a/doc/bugs/dotdot_problem.mdwn b/doc/bugs/dotdot_problem.mdwn
deleted file mode 100644
index cbefd5dae..000000000
--- a/doc/bugs/dotdot_problem.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-cannot "git annex ../foo"   (GitRepo.relative is buggy and
-git-ls-files also refuses w/o --full-name, which would need other changes)
-
-[[done]]
diff --git a/doc/bugs/drop_fails_to_see_copies_that_whereis_sees.mdwn b/doc/bugs/drop_fails_to_see_copies_that_whereis_sees.mdwn
deleted file mode 100644
index 59b76c92b..000000000
--- a/doc/bugs/drop_fails_to_see_copies_that_whereis_sees.mdwn
+++ /dev/null
@@ -1,69 +0,0 @@
-What steps will reproduce the problem?
-------------------------------------------------------
-
-I haven't tried doing this again, but here's what I did:
-
-I was copying files to my usb drive (hugex) with probably this command:
-
-    git annex copy --to=hugex .
-
-While doing that, I did something stupid in another window, and filled my local hard drive (the one I was copying from) and git annex spit out some errors about not being able to write to log files (because my local drive was full.)
-
-I suspended (^Z) git annex, made some hard drive space, then resumed (fg).
-
-At first, git annex whereis didn't see the copies of some of the files in hugex (apparently the ones where git annex had trouble writing the local log files). After a "git remote update hugex" and I think a ``git annex merge``, whereis was able to see both copies.
-
-But git drop can't see both copies, and won't let me drop my local copy. I ran ``git annex fsck .`` on the directory with the now files I was copying above, and that didn't seem to change anything (or report errors.)
-
-Here's a terminal session where I'm showing the problem and some hopefully useful text:
-
-	compy compy compy ~/video/tv/keen-eddie> git annex whereis 02-horse-heir.avi 
-	whereis 02-horse-heir.avi (2 copies) 
-  		5bfe091c-ed07-11df-842e-eb791a485889 -- here (compy)
-   		e15161ec-f1bf-11df-a7b5-eb1f0e6921ee -- hugex
-	ok
-	compy compy compy ~/video/tv/keen-eddie> git annex drop 02-horse-heir.avi 
-	drop 02-horse-heir.avi (unsafe) 
-  	  Could only verify the existence of 1 out of 2 necessary copies
-
-  	  No other repository is known to contain the file.
-
-  	  (Use --force to override this check, or adjust annex.numcopies.)
-	failed
-	git-annex: drop: 1 failed
-	zsh: exit 1     git annex drop 02-horse-heir.avi
-	compy compy compy ~/video/tv/keen-eddie> ls -lh 02-horse-heir.avi              
-	lrwxrwxrwx 1 jasonwoof jasonwoof 149 Nov 15 04:19 02-horse-heir.avi -> ../../../.git/annex/objects/KV/8G/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7
-	compy compy compy ~/video/tv/keen-eddie> ls --dereference -lh 02-horse-heir.avi
-	-r--r--r-- 1 jasonwoof jasonwoof 342M Nov 15 04:19 02-horse-heir.avi
-	compy compy compy ~/video/tv/keen-eddie> ls -lh ../../../.git/annex/objects/KV/8G/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7
-	-r--r--r-- 1 jasonwoof jasonwoof 342M Nov 15 04:19 ../../../.git/annex/objects/KV/8G/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7
-	compy compy compy ~/video/tv/keen-eddie> ls -lh /media/hugex/jason/home.git/annex/objects/5bd/6a1/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7
-	-r--r--r-- 1 jasonwoof jasonwoof 342M Jan  7 16:27 /media/hugex/jason/home.git/annex/objects/5bd/6a1/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7/SHA1-s358316330--7fcbf33b711e41def269f042842212d0bf3736a7
-
-That last command is showing that the file is indeed in hugex's annex/objects
-
-
-Oh, and another wrinkle. hugex is a bare repo. I tried to fsck hugex's video/tv directory, but it said that directory doesn't exist (I assume because there's no working copy.)
-
-
-What is the expected output? What do you see instead?
-------------------------------------------------------------------------------
-
-I'd like ``git annex drop`` to have the same kind of confidence in the copies of these files on hugex.
-
-How can I resolve this. I tried ``git annex copy --to=hugex .`` again, but that command knows that these files are already copied to hugex.
-
-What version of git-annex are you using? On what operating system?
-
-3.20130102 on debian unstable (thanks for packaging!)
-
-Please provide any additional information below.
-------------------------------------------------------------------
-
-You can also reach me at ``jason@jasonwoof.com``
-
-> [[done]]; the confusing message has been improved.
-> 
-> BTW, you can use `git annex move` to ensure a file is on another repo and
-> drop it locally. --[[Joey]]
diff --git a/doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_1_f5a9d99d90daf5eba4773d361fa1807a._comment b/doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_1_f5a9d99d90daf5eba4773d361fa1807a._comment
deleted file mode 100644
index 647c6db3a..000000000
--- a/doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_1_f5a9d99d90daf5eba4773d361fa1807a._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.211"
- subject="comment 1"
- date="2013-01-08T18:43:33Z"
- content="""
-So, the first part of this is git-annex behaving as designed. When there's a fatal disk problem and it cannot update its local location log, only the remote's location log gets updated. After a `git annex sync` (or your manual equivilant), the location log changes get propigated from the remote, and the local repository returns to a consistent state.
-
-As to the drop problem, look at it again. You have numcopies configured to 2, and there are currently 2 copies of the file. So dropping 1 would leave the numcopies constraint unsatisfied, and so it doesn't. You can override --numcopies 1 or --force the drop, but I don't see a bug here.
-
-(Perhaps the \"No other repository is known to contain the file.\" message is confusing in this context? It doesn't mean that no other repo has the file at all, but that there are no other repositories, that it was not able to check, that might have the file. If you had another removable drive with the file, and the drive was detached, this message would instead say \"Try making some of these repositories available: otherdrive\")
-
-(Re fscking in a bare repo, in a bare repository, you cannot fsck specific files/directories; fsck just checks every single key that git-annex knows about.)
-"""]]
diff --git a/doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_2_040aa454cd8acd2857ef36884465576f._comment b/doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_2_040aa454cd8acd2857ef36884465576f._comment
deleted file mode 100644
index 58f69646b..000000000
--- a/doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_2_040aa454cd8acd2857ef36884465576f._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://jasonwoof.com/"
- nickname="JasonWoof"
- subject="Thank you."
- date="2013-01-08T23:02:33Z"
- content="""
-First off, awesome that git annex auto-fixes itself after I make hard drive space and merge.
-
-The problem was that I didn't realize that my .gitattributes that were supposed to set numcopies to 1 didn't work. (Because I didn't realize that they don't apply recursively.) I fixed my .gitattributes, and then was able to drop those files.
-
-And you are right that the text \"No other repository is known to contain the file\" threw me off. Perhaps when numcopies > 1 you could change that message to \"Not enough other repositories are known to contain the file\".
-
-Thank you.
-
--- Jason
-"""]]
diff --git a/doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_3_f5d8faab325ee26800ecad5aba49b54b._comment b/doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_3_f5d8faab325ee26800ecad5aba49b54b._comment
deleted file mode 100644
index ca6287dd6..000000000
--- a/doc/bugs/drop_fails_to_see_copies_that_whereis_sees/comment_3_f5d8faab325ee26800ecad5aba49b54b._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://jasonwoof.com/"
- nickname="JasonWoof"
- subject="language suggestions"
- date="2013-01-09T04:31:40Z"
- content="""
-Maybe it could read \"Could not verify that enough copies of the file exist to safely drop it\". Or \"Could not verify that enough other repositories contain this file to safely drop it.\"
-
-It might be cool (if this isn't supported already) if there was a command to drop a file that would automatically copy it to another repo first if needed to satisfy numcopies.
-"""]]
diff --git a/doc/bugs/dropping_and_re-adding_from_web_remotes_doesn__39__t_work.mdwn b/doc/bugs/dropping_and_re-adding_from_web_remotes_doesn__39__t_work.mdwn
deleted file mode 100644
index 30327ba1f..000000000
--- a/doc/bugs/dropping_and_re-adding_from_web_remotes_doesn__39__t_work.mdwn
+++ /dev/null
@@ -1,139 +0,0 @@
-In experimenting with the web remote, I found that dropping a URL gave an error, but still succeeded, while re-adding the same URL fails to work correctly.
-
-#What steps will reproduce the problem?
-
-<pre>
-/tmp $ dd if=/dev/zero of=/tmp/file.bin count=1024
-1024+0 records in
-1024+0 records out
-524288 bytes (524 kB) copied, 0.0135652 s, 38.6 MB/s
-/tmp $ mkdir /tmp/repo
-/tmp $ cd /tmp/repo
-/tmp/repo $ git init
-Initialized empty Git repository in /tmp/repo/.git/
-/tmp/repo $ git annex init "test"
-init test ok
-(Recording state in git...)
-/tmp/repo $ git annex addurl file:///tmp/file.bin --file annexed.bin
-######################################################################## 100.0%
-(checksum...) ok
-(Recording state in git...)
-/tmp/repo $ git annex drop annexed.bin 
-drop annexed.bin (checking file:///tmp/file.bin...) ok
-(Recording state in git...)
-/tmp/repo $ mv /tmp/file.bin /tmp/file2.bin 
-/tmp/repo $ git annex get annexed.bin 
-get annexed.bin (from web...) 
-curl: (37) Couldn't open file /tmp/file.bin
-
-  Unable to access these remotes: web
-
-  Try making some of these repositories available:
-        00000000-0000-0000-0000-000000000001 -- web
-failed
-git-annex: get: 1 failed
-/tmp/repo $ git annex drop --from web annexed.bin --force
-drop web annexed.bin
-  removal from web not supported
-failed
-(Recording state in git...)
-git-annex: drop: 1 failed
-/tmp/repo $ git annex get annexed.bin 
-get annexed.bin (not available) 
-  No other repository is known to contain the file.
-failed
-git-annex: get: 1 failed
-/tmp/repo $ mv /tmp/file2.bin /tmp/file.bin 
-/tmp/repo $ git annex addurl file:///tmp/file.bin --file annexed.bin
-addurl annexed.bin ok
-/tmp/repo $ git annex whereis annexed.bin
-whereis annexed.bin (0 copies) failed
-git-annex: whereis: 1 failed
-/tmp/repo $ git annex addurl file:///tmp/file.bin --file annexed2.bin
-######################################################################## 100.0%
-(checksum...) ok
-(Recording state in git...)
-/tmp/repo $ git annex whereis annexed.bin
-whereis annexed.bin (1 copy)
-        e2418e81-ec04-4091-aabe-ed75d65f93fa -- here (test)
-ok
-/tmp/repo $ git annex whereis annexed2.bin
-whereis annexed2.bin (1 copy)
-        e2418e81-ec04-4091-aabe-ed75d65f93fa -- here (test)
-ok
-/tmp/repo $ git annex drop annexed.bin
-drop annexed.bin (unsafe)
-  Could only verify the existence of 0 out of 1 necessary copies
-
-  No other repository is known to contain the file.
-
-  (Use --force to override this check, or adjust annex.numcopies.)
-failed
-git-annex: drop: 1 failed
-/tmp/repo $ git annex drop annexed2.bin
-drop annexed2.bin (unsafe)
-  Could only verify the existence of 0 out of 1 necessary copies
-
-  No other repository is known to contain the file.
-
-  (Use --force to override this check, or adjust annex.numcopies.)
-failed
-git-annex: drop: 1 failed
-/tmp/repo $ mv /tmp/file.bin /tmp/file2.bin 
-/tmp/repo $ git annex addurl file:///tmp/file2.bin --file annexed.bin
-addurl annexed.bin ok
-(Recording state in git...)
-/tmp/repo $ git annex whereis annexed2.bin 
-whereis annexed2.bin (2 copies) 
-        00000000-0000-0000-0000-000000000001 -- web
-        e2418e81-ec04-4091-aabe-ed75d65f93fa -- here (test)
-
-  web: file:///tmp/file.bin
-  web: file:///tmp/file2.bin
-ok
-/tmp/repo $ mv /tmp/file2.bin /tmp/file.bin 
-/tmp/repo $ git annex drop annexed.bin 
-drop annexed.bin (checking file:///tmp/file.bin...) ok
-(Recording state in git...)
-/tmp/repo $ git annex get annexed.bin 
-get annexed.bin (from web...) 
-######################################################################## 100.0%
-ok
-(Recording state in git...)
-/tmp/repo $ git annex drop annexed.bin 
-drop annexed.bin (checking file:///tmp/file.bin...) ok
-(Recording state in git...)
-/tmp/repo $ mv /tmp/file.bin /tmp/file2.bin 
-/tmp/repo $ git annex get annexed.bin 
-get annexed.bin (from web...) 
-curl: (37) Couldn't open file /tmp/file.bin
-######################################################################## 100.0%
-ok
-(Recording state in git...)
-</pre>
-
-#What is the expected output? What do you see inst
-
-
-When dropping one file and I see "git-annex: drop: 1 failed" I would expect the file to still be in the remote as far as git-annex is concerned.
-
-When re-adding the URL, I expect the file to be re-added to the web remote. (note that it re-appears after adding the same file via a different URL)
-
-
-#What version of git-annex are you using? On what operating system?
-
-
-3.20121112 on Gentoo Linux
-
-
-#Please provide any additional information below.
-
-This seems to be a corner case, and would probably have minimal impact on most people.
-
-> Yeah, dropping from the web is pretty weird.
-> 
-> I guess it makes sense to do if a website stops having a file and you don't
-> want git-annex to try to download from it anymore. So, I've made dropping
-> from the web remove all urls associated with the file, rather than failing.
-> 
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/dropunused_doesn__39__t_handle_double_spaces_in_filename.mdwn b/doc/bugs/dropunused_doesn__39__t_handle_double_spaces_in_filename.mdwn
deleted file mode 100644
index a6b44cd2a..000000000
--- a/doc/bugs/dropunused_doesn__39__t_handle_double_spaces_in_filename.mdwn
+++ /dev/null
@@ -1,87 +0,0 @@
-Unused files with double spaces in their name are not removed by `dropunused`:
-
-Script:
-
-    #!/bin/bash
-    
-    BASE=/tmp/unused-bug
-    
-    # setup
-    set -x
-    chmod -R +w $BASE
-    rm -rf $BASE
-    mkdir -p $BASE
-    cd $BASE
-    
-    # create annex
-    git init .
-    git annex init
-    
-    # make a file with two spaces
-    echo hello > 'foo  bar'
-    
-    # add it
-    git annex add --backend WORM 'foo  bar'
-    git commit -m 'add'
-    
-    # remove it
-    git rm 'foo  bar'
-    git commit -m 'remove'
-    
-    # unused
-    git annex unused
-    git annex dropunused 1
-    git annex unused
-
-Output:
-
-    + chmod -R +w /tmp/unused-bug
-    + rm -rf /tmp/unused-bug
-    + mkdir -p /tmp/unused-bug
-    + cd /tmp/unused-bug
-    + git init .
-    Initialized empty Git repository in /tmp/unused-bug/.git/
-    + git annex init
-    init  ok
-    + echo hello
-    + git annex add --backend WORM 'foo  bar'
-    add foo  bar ok
-    (Recording state in git...)
-    + git commit -m add
-    [master (root-commit) 926f7f5] add
-     1 files changed, 1 insertions(+), 0 deletions(-)
-     create mode 120000 foo  bar
-    + git rm 'foo  bar'
-    rm 'foo  bar'
-    + git commit -m remove
-    [master d025e3f] remove
-     1 files changed, 0 insertions(+), 1 deletions(-)
-     delete mode 120000 foo  bar
-    + git annex unused
-    unused . (checking for unused data...) (checking master...) 
-      Some annexed data is no longer used by any files:
-        NUMBER  KEY
-        1       WORM-s6-m1322200438--foo  bar
-      (To see where data was previously used, try: git log --stat -S'KEY')
-      
-      To remove unwanted data: git-annex dropunused NUMBER
-      
-    ok
-    + git annex dropunused 1
-    dropunused 1 ok
-    + git annex unused
-    unused . (checking for unused data...) (checking master...) 
-      Some annexed data is no longer used by any files:
-        NUMBER  KEY
-        1       WORM-s6-m1322200438--foo  bar
-      (To see where data was previously used, try: git log --stat -S'KEY')
-      
-      To remove unwanted data: git-annex dropunused NUMBER
-      
-    ok
-
-Strange that `dropunused` still said "ok" when it didn't succeed at removing the file.
-
-> It was misparsing the unused file, so it thought you'd asked it to drop a
-> key that didn't exist (which means already dropped) so no error. I've
-> fixed the bug. [[done]] --[[Joey]] 
diff --git a/doc/bugs/dropunused_doesn__39__t_work_in_my_case__63__.mdwn b/doc/bugs/dropunused_doesn__39__t_work_in_my_case__63__.mdwn
deleted file mode 100644
index 7428b091a..000000000
--- a/doc/bugs/dropunused_doesn__39__t_work_in_my_case__63__.mdwn
+++ /dev/null
@@ -1,70 +0,0 @@
-What steps will reproduce the problem?
-
-I am unable to create a minimal setup to reproduce this unfortunately. But my case is the following:
-
-* Two synced repos, I have switched between direct and indirect in both, currently they are indirect
-* I have two submodules in the repos (not related to the unuesd files)
-
-* I used "git rm -r" to remove a bunch of files along with "git mv" to move some
-* I have three commits of actions like this
-
-* In one repo, the one where I did the deletions, I have 172 unused files, and all seem to come from the first of the three commits
-* In the second repo, to which I synced, I have 188 unused files, which includes a couple of files from the third commit as well
-
-* If I try to dropunused either a single file or the whole range of the files, from either repo, I get git-annex telling me "ok, recording state" but when I run unused again the files are still there. And looking into .git/objects/annex/ the file is still present
-
-This is the debug from the drop command:
-
-    dropunused 9 [2013-02-07 12:47:24 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","show-ref","git-annex"]
-    [2013-02-07 12:47:24 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","show-ref","--hash","refs/heads/git-annex"]
-    [2013-02-07 12:47:24 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","log","refs/heads/git-annex..5f3fc9db5c7badb5fb25c3159c20584f11dadaf9","--oneline","-n1"]
-    [2013-02-07 12:47:24 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","log","refs/heads/git-annex..8e5674078706864f2eade86d8aa43027e05afc1d","--oneline","-n1"]
-    [2013-02-07 12:47:24 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","log","refs/heads/git-annex..cbe492cfa79728698f5d891d7f716fbcd9fc29e2","--oneline","-n1"]
-    [2013-02-07 12:47:24 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","log","refs/heads/git-annex..48a1bdf98a10ad9a81c0587f8909e94c1c0dccc4","--oneline","-n1"]
-    [2013-02-07 12:47:24 CET] chat: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","cat-file","--batch"]
-    [2013-02-07 12:47:24 CET] read: git ["config","--null","--list"]
-    [2013-02-07 12:47:24 CET] chat: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","hash-object","-w","--stdin-paths"]
-    [2013-02-07 12:47:24 CET] feed: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","update-index","-z","--index-info"]
-    [2013-02-07 12:47:24 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","show-ref","--hash","refs/heads/git-annex"]
-    [2013-02-07 12:47:24 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","write-tree"]
-    [2013-02-07 12:47:24 CET] chat: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","commit-tree","76f5041bc6e8a109e0309a09b5f36cd0da8b204a","-p","refs/heads/git-annex"]
-    [2013-02-07 12:47:24 CET] call: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","update-ref","refs/heads/git-annex","96de755475bdd8f0f948dd6421c3956803a63e66"]
-    ok
-    (Recording state in git...)
-
-If I run it again, I get:
-
-    dropunused 9 [2013-02-07 12:47:47 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","show-ref","git-annex"]
-    [2013-02-07 12:47:47 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","show-ref","--hash","refs/heads/git-annex"]
-    [2013-02-07 12:47:47 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","log","refs/heads/git-annex..96de755475bdd8f0f948dd6421c3956803a63e66","--oneline","-n1"]
-    [2013-02-07 12:47:48 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","log","refs/heads/git-annex..8e5674078706864f2eade86d8aa43027e05afc1d","--oneline","-n1"]
-    [2013-02-07 12:47:48 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","log","refs/heads/git-annex..cbe492cfa79728698f5d891d7f716fbcd9fc29e2","--oneline","-n1"]
-    [2013-02-07 12:47:48 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","log","refs/heads/git-annex..48a1bdf98a10ad9a81c0587f8909e94c1c0dccc4","--oneline","-n1"]
-    [2013-02-07 12:47:48 CET] chat: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","cat-file","--batch"]
-    [2013-02-07 12:47:48 CET] read: git ["config","--null","--list"]
-    [2013-02-07 12:47:48 CET] chat: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","hash-object","-w","--stdin-paths"]
-    [2013-02-07 12:47:48 CET] feed: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","update-index","-z","--index-info"]
-    [2013-02-07 12:47:48 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","show-ref","--hash","refs/heads/git-annex"]
-    [2013-02-07 12:47:48 CET] read: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","write-tree"]
-    [2013-02-07 12:47:48 CET] chat: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","commit-tree","e40d82db10c60519f6a3a72055e9577850972fdf","-p","refs/heads/git-annex"]
-    [2013-02-07 12:47:48 CET] call: git ["--git-dir=/home/arand/.git","--work-tree=/home/arand","update-ref","refs/heads/git-annex","6cf49f629251f9b39fa8b457cf6590c71c1d509b"]
-    ok
-    (Recording state in git...)
-
-
-What version of git-annex are you using? On what operating system?
-
-git-annex: 3.20130124
-Debian: sid 2013-02-01
-
-> I put a fix in for this in 57780cb3a4dfe1292b72e1412ec4d2a70b6d04ce 
-> but it was buggy and I had to revert it.
-> 
-> The bug is caused by direct mode cache and mapping info.
-> This makes getKeysPresent find keys that are not present.
-> It would be expensive to make getKeysPresent check that the
-> actual key files are present (it just lists the directories). 
-> But this seems to be needed, since direct mode can leave
-> cache and mapping files behind. --[[Joey]]
-
->> Now fixed properly. [[done]] --[[Joey]]
diff --git a/doc/bugs/enableremote_broken_with_direct_mode__63__.mdwn b/doc/bugs/enableremote_broken_with_direct_mode__63__.mdwn
deleted file mode 100644
index a44cef431..000000000
--- a/doc/bugs/enableremote_broken_with_direct_mode__63__.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-### Please describe the problem.
-I have 2 regular annex locations plus one on glacier. I recently cloned one location, converted it to direct mode, then tried to enableremote glacier.
-
-When I ran the webapp everything seemed to be ok, it showed file transfers to glacier which appeared to be completing very quickly. When I looked in the log file however, I saw the files weren't actually transferring and I was getting lots of errors:
-
-  Set both AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to use glacier
-
-In order to get glacier working I had to manually copy the creds file to the new repo. The transfer errors should also made obvious in the webapp.
-
-### What steps will reproduce the problem?
-[[!format sh """
-git clone server:/location
-git annex init "laptop"
-git remote add "server" server:/location
-git annex direct
-
-Then I ran:
-git annex enableremote glacier
-Which prints:
-(merging origin/git-annex origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-enableremote glacier (gpg) ok
-(Recording state in git...)
-"""]]
-But in fact it hasn't actually copied the creds to use it.
-
-
-### What version of git-annex are you using? On what operating system?
-5.20140221, debian.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> Should be fixed in 5.20140227. [[done]] --[[Joey]]
diff --git a/doc/bugs/enableremote_broken_with_direct_mode__63__/comment_1_a2e61f5de7a28498de0c2d5e3d51eab4._comment b/doc/bugs/enableremote_broken_with_direct_mode__63__/comment_1_a2e61f5de7a28498de0c2d5e3d51eab4._comment
deleted file mode 100644
index 84cf2d4bf..000000000
--- a/doc/bugs/enableremote_broken_with_direct_mode__63__/comment_1_a2e61f5de7a28498de0c2d5e3d51eab4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.146"
- subject="comment 1"
- date="2014-02-27T15:35:28Z"
- content="""
-5.20140221 had a bug in passing the creds on when setting up remotes in the webapp. This is fixed in 5.20140227.
-"""]]
diff --git a/doc/bugs/encrypted_S3_stalls.mdwn b/doc/bugs/encrypted_S3_stalls.mdwn
deleted file mode 100644
index 109e6e793..000000000
--- a/doc/bugs/encrypted_S3_stalls.mdwn
+++ /dev/null
@@ -1,9 +0,0 @@
-Sending large-ish (few megabytes) files to encrypted S3 remotes stalls out.
-It works for the tiny files I was using to test while developing it, on
-dialup.
-
-There was a similar issue with bup, which I fixed by forking a process
-rather than using a thread to do some IO. Probably need the same here.
---[[Joey]]
-
-[[done]] --[[Joey]] 
diff --git a/doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption.mdwn b/doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption.mdwn
deleted file mode 100644
index 15bc95f27..000000000
--- a/doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-What steps will reproduce the problem?
-    % > git annex initremote glacier type=glacier encryption=E9053BDA
-    -- SNIP --
-    initremote glacier [2013-01-10 14:50:12 PST] read: gpg ["--quiet","--trust-model","always","--with-colons","--list-public-keys","E9053BDA"]
-    [2013-01-10 14:50:12 PST] chat: gpg ["--quiet","--trust-model","always","--decrypt"]
-    
-    You need a passphrase to unlock the secret key for
-    user: "Andrew Mark Kraut <akraut@gmail.com>"
-    4096-bit ELG key, ID 353E49B9, created 2008-11-11 (main key ID E9053BDA)
-    
-    [2013-01-10 14:50:13 PST] chat: gpg ["--quiet","--trust-model","always","--encrypt","--no-encrypt-to","--no-default-recipient","--recipient","B608B8F6E9053BDA"]
-    (encryption updated with gpg key B608B8F6E9053BDA) [2013-01-10 14:50:13 PST] call: glacier ["--region=us-west-1","vault","create","glacier-06D927EC-5761-447B-86AC-CA66040BAC25"]
-    [2013-01-10 14:50:13 PST] call: git ["--git-dir=/Users/akraut/Desktop/annex/.git","--work-tree=/Users/akraut/Desktop/annex","config","remote.glacier.annex-glacier","true"]
-    [2013-01-10 14:50:13 PST] call: git ["--git-dir=/Users/akraut/Desktop/annex/.git","--work-tree=/Users/akraut/Desktop/annex","config","remote.glacier.annex-uuid","06D927EC-5761-447B-86AC-CA66040BAC25"]
-    (gpg) [2013-01-10 14:50:13 PST] chat: gpg ["--quiet","--trust-model","always","--decrypt"]
-    
-    You need a passphrase to unlock the secret key for
-    user: "Andrew Mark Kraut <akraut@gmail.com>"
-    4096-bit ELG key, ID 353E49B9, created 2008-11-11 (main key ID E9053BDA)
-    
-    [2013-01-10 14:50:14 PST] chat: gpg ["--quiet","--trust-model","always","--passphrase-fd","8","--symmetric","--force-mdc"]
-    ok
-
-What is the expected output? What do you see instead?
-
-> I expect any transfers to this remote (glacier) to use the given gpg key, but instead it uses --symmetric, as you can see above.
-
-What version of git-annex are you using? On what operating system?
-
-    git-annex version: 3.20130107
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3
-    upgrade supported from repository versions: 0 1 2
-
-
-Please provide any additional information below.
-
-> Symmetric encryption is used as described in [[design/encryption]],
-> with the symmetric key stored encrypted using your gpg key.
-> 
-> The extra prompting described in the comments in the bug.
-> 
-> I've reproduced this with gpg 2.0.19. It is a documented incompatability
-> between gpg 1.x and 2.x; the latter needs --batch included in its
-> parameters. I've put in a fix. [[done]]
diff --git a/doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption/comment_1_2f4ec4b7b92a0f0a0c4c0758da4a05a5._comment b/doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption/comment_1_2f4ec4b7b92a0f0a0c4c0758da4a05a5._comment
deleted file mode 100644
index d4c537ed9..000000000
--- a/doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption/comment_1_2f4ec4b7b92a0f0a0c4c0758da4a05a5._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q"
- nickname="Andrew"
- subject="comment 1"
- date="2013-01-11T00:01:08Z"
- content="""
-Ok, I just reread [[design/encryption]] and perhaps this isn't a bug after all.
-Though, the annoyance I experience that made me dig into this a bit perhaps is a bug.
-
-In my example output above, if I 'git annex copy dir_full_of_files --to=glacier', I will get the GPG agent's passphrase prompt for each file, even if I have passphrase caching turned on and (on my mac) even if I have the passphrase saved in the keychain. Additionally, GPG will successfully encrypt the file if I enter anything at all into the passphrase prompt as long as I enter something. This leads me to believe that it either doesn't actually need to decrypt my GPG private key or it's using what I enter as the symmetric encryption key.
-
-Ideas?
-"""]]
diff --git a/doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption/comment_2_7c0aeae6b1b2b0338735b0231c5db7d4._comment b/doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption/comment_2_7c0aeae6b1b2b0338735b0231c5db7d4._comment
deleted file mode 100644
index 86dc2aa71..000000000
--- a/doc/bugs/encryption_given_a_gpg_keyid_still_uses_symmetric_encryption/comment_2_7c0aeae6b1b2b0338735b0231c5db7d4._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 2"
- date="2013-01-16T02:17:44Z"
- content="""
-What operating system is this? 
-
-How did you install git-annex? 
-
-Can you still reproduce the bug? 
-
-What happens if you run this command; does it prompt for a passphrase?
-
-touch foo; echo foo| gpg --symmetric --passphrase-fd=0 foo
-"""]]
diff --git a/doc/bugs/encryption_key_is_surprising.mdwn b/doc/bugs/encryption_key_is_surprising.mdwn
deleted file mode 100644
index 5b18610b5..000000000
--- a/doc/bugs/encryption_key_is_surprising.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-Crypto.hs seems to imply that the cipher key it's acting upon is 512 bytes long. Because of a probable programming mistake the key that's actually used is a bit surprising. The random key is generated by this snippet in Utility/Gpg.hs:
-
-    {- Creates a block of high-quality random data suitable to use as a cipher.
-     - It is armored, to avoid newlines, since gpg only reads ciphers up to the
-     - first newline. -}
-    genRandom :: Int -> IO String
-    genRandom size = readStrict
-        [ Params "--gen-random --armor"
-        , Param $ show randomquality
-        , Param $ show size
-        ]
-      where
-        -- 1 is /dev/urandom; 2 is /dev/random
-        randomquality = 1 :: Int
-
-This lets GPG generate the randomness and by passing armor, it avoids newlines. However, this base64 encoding is never undone on the way to Crypto.hs. Hence what cipherPassphrase and cipherHmac do is dropping or skipping the first 256 bytes of the base64 value. Base64, with its 6 bit per byte encoding, causes the Hmac function to operate on 192 bytes instead of 256 bytes. The key used by GPG will be larger. Some assertions that the resulting functions really operate on strings of the right length would've been helpful. Also GPG and HMAC get tested, the encryption/decryption part are not tested AFAICS.
-
-The encryption wiki page could have had more information. Enough code (sadly in Python, not reusing the Haskell code) to operate on the resulting files can be found in [this Gist](https://gist.github.com/pkern/5078559).
-
--- Philipp Kern
-
-> In addition to the comment below, I have added a check that gpg outputs
-> the expected quantity of data, and the storage of the cipher is now
-> documented in [[internals]]. Think I can call this [[done]]. --[[Joey]]
diff --git a/doc/bugs/encryption_key_is_surprising/comment_1_5b172830ac31d51a1687bc8b1db489f9._comment b/doc/bugs/encryption_key_is_surprising/comment_1_5b172830ac31d51a1687bc8b1db489f9._comment
deleted file mode 100644
index 04854b3a4..000000000
--- a/doc/bugs/encryption_key_is_surprising/comment_1_5b172830ac31d51a1687bc8b1db489f9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-04T00:04:53Z"
- content="""
-My first concern is if this means it's insecure. Luckily it seems not; HMAC SHA1 needs only 64 bytes of entropy, which are more than provided in the 256 bytes of base64 provided. As long as both gpg and the HMAC code use the full provided key (and not just the first 64 bytes of it, say), we're ok. And as far as I can tell, both do fully consume and use the key.
-
-So, I don't feel the need to change the code, aside from some minor improvements to variable names.
-"""]]
diff --git a/doc/bugs/encryption_key_is_surprising/comment_2_5b7e6bb36c3333dfd71808e8b4544746._comment b/doc/bugs/encryption_key_is_surprising/comment_2_5b7e6bb36c3333dfd71808e8b4544746._comment
deleted file mode 100644
index 24f8452c3..000000000
--- a/doc/bugs/encryption_key_is_surprising/comment_2_5b7e6bb36c3333dfd71808e8b4544746._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://phil.0x539.de/"
- nickname="Philipp Kern"
- subject="comment 2"
- date="2013-03-04T07:36:55Z"
- content="""
-GPG also reduces the key material to the size of a SHA1 hash (because we're using the default option for s2k-digest-algo) to generate the symmetric key used with CAST5. So I wonder a bit why we bother with 512 bytes in the first place. Also they come from urandom (even on Linux), despite being generated once per remote. So maybe the strongness of the weakest link should be written down somewhere.
-"""]]
diff --git a/doc/bugs/encryption_key_is_surprising/comment_4_8ec86b8c35bce15337a143e275961cd5._comment b/doc/bugs/encryption_key_is_surprising/comment_4_8ec86b8c35bce15337a143e275961cd5._comment
deleted file mode 100644
index ba5be68d4..000000000
--- a/doc/bugs/encryption_key_is_surprising/comment_4_8ec86b8c35bce15337a143e275961cd5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://phil.0x539.de/"
- nickname="Philipp Kern"
- subject="comment 4"
- date="2013-03-05T07:17:08Z"
- content="""
-You (presumably) hand over 320 bytes of entropy to GPG, but you don't control the encryption key directly. GPG assumes that what it's given as a symmetric key is not at all random. Hence, with the default options (for OpenPGP interop, apparently) it will derive a 128 bit from the given passphrase. For this it uses (again, by default) salted SHA1 on the whole passphrase. So the strength of the cipher is 128 bit CAST5 or an attack on salted SHA1 with a mostly known input length (but this does seem large).
-"""]]
diff --git a/doc/bugs/encryption_key_is_surprising/comment_4_c5e49b3a0eceabe6d14f5226d7ba4c7a._comment b/doc/bugs/encryption_key_is_surprising/comment_4_c5e49b3a0eceabe6d14f5226d7ba4c7a._comment
deleted file mode 100644
index a685626e5..000000000
--- a/doc/bugs/encryption_key_is_surprising/comment_4_c5e49b3a0eceabe6d14f5226d7ba4c7a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 4"
- date="2013-03-04T17:29:28Z"
- content="""
-What do you mean by \"reduces\"? I assume it doesn't just take the first N bytes?
-"""]]
diff --git a/doc/bugs/encryption_key_is_surprising/comment_5_cd7cbf0c0ee9cafec344dfbf1acd9590._comment b/doc/bugs/encryption_key_is_surprising/comment_5_cd7cbf0c0ee9cafec344dfbf1acd9590._comment
deleted file mode 100644
index 4e7635402..000000000
--- a/doc/bugs/encryption_key_is_surprising/comment_5_cd7cbf0c0ee9cafec344dfbf1acd9590._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://kaizer.se/"
- nickname="ulrik.sverdrup"
- subject="GPG Cipher Algo"
- date="2013-03-06T04:53:06Z"
- content="""
-The GPG cipher algorithm is user configurable (unless annex overrides it) the best way to set it is personal-cipher-preferences. Annex' job is simply to provide enough key material for any viable GPG option (so 256 bits of random data). Also note that GPG's string-to-key \"s2k\" algorithm is an iterated application SHA-1 (also this can be configured). For a quick context, it will use a strength number (for example count=128*1024) and it will hash as many iterations as [count]/[key byte length].
-"""]]
diff --git a/doc/bugs/encryption_key_is_surprising/comment_6_01381524114d885961704acc3f172536._comment b/doc/bugs/encryption_key_is_surprising/comment_6_01381524114d885961704acc3f172536._comment
deleted file mode 100644
index 21898b522..000000000
--- a/doc/bugs/encryption_key_is_surprising/comment_6_01381524114d885961704acc3f172536._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://kaizer.se/"
- nickname="ulrik.sverdrup"
- subject="comment 6"
- date="2013-03-06T05:30:16Z"
- content="""
-I'm not very clear, sorry. S2K is not iterative in the way for example PBKDF2 is. It will hash a very long repetition of salt + passphrase + salt + passphrase etc in one go. The repetition of this happens if more key bits than the hash digest size are needed.
-"""]]
diff --git a/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment b/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment
deleted file mode 100644
index 19863e8f8..000000000
--- a/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://phil.0x539.de/"
- nickname="Philipp Kern"
- subject="comment 7"
- date="2013-03-07T15:21:55Z"
- content="""
-For the default git-annex will pass plenty of key bytes to make this unnecessary. True, one could adjust <code>$HOME/.gnupg/gpg.conf</code> to select another s2k algorithm and another cipher for the data (the two relevant options being <code>s2k-digest-algo</code> and <code>cipher-algo</code>). To be honest, I'd also like a per-repository gpg options setting for the symmetric cipher. For instance I know that I always want compression with gpg unless I use it with annexed data (at least in certain repositories).
-"""]]
diff --git a/doc/bugs/error_building_git-annex_3.20120624_using_cabal.mdwn b/doc/bugs/error_building_git-annex_3.20120624_using_cabal.mdwn
deleted file mode 100644
index df83f4e4e..000000000
--- a/doc/bugs/error_building_git-annex_3.20120624_using_cabal.mdwn
+++ /dev/null
@@ -1,159 +0,0 @@
-I am trying to install git-annex 3.20120624 using cabal.  My currently installed version of git-annex is 3.20120615.  After a "cabal update", the build of git-annex fails:
-
-    bram@falafel% cabal install git-annex
-    Resolving dependencies...
-    [1 of 4] Compiling Utility.SafeCommand ( /tmp/git-annex-3.20120624-4173/git-annex-3.20120624/Utility/SafeCommand.hs, /tmp/git-annex-3.20120624-4173/git-annex-3.20120624/dist/setup/Utility/SafeCommand.o )
-    [2 of 4] Compiling Build.TestConfig ( /tmp/git-annex-3.20120624-4173/git-annex-3.20120624/Build/TestConfig.hs, /tmp/git-annex-3.20120624-4173/git-annex-3.20120624/dist/setup/Build/TestConfig.o )
-    [3 of 4] Compiling Build.Configure  ( /tmp/git-annex-3.20120624-4173/git-annex-3.20120624/Build/Configure.hs, /tmp/git-annex-3.20120624-4173/git-annex-3.20120624/dist/setup/Build/Configure.o )
-    [4 of 4] Compiling Main             ( /tmp/git-annex-3.20120624-4173/git-annex-3.20120624/Setup.hs, /tmp/git-annex-3.20120624-4173/git-annex-3.20120624/dist/setup/Main.o )
-    Linking /tmp/git-annex-3.20120624-4173/git-annex-3.20120624/dist/setup/setup ...
-      checking version... 3.20120624
-      checking git... yes
-      checking git version... 1.7.9.5
-      checking cp -a... yes
-      checking cp -p... yes
-      checking cp --reflink=auto... yes
-      checking uuid generator... uuid
-      checking xargs -0... yes
-      checking rsync... yes
-      checking curl... no
-      checking wget... yes
-      checking bup... no
-      checking gpg... yes
-      checking lsof... yes
-      checking ssh connection caching... yes
-      checking sha1... sha1sum
-      checking sha512... sha512sum
-      checking sha224... sha224sum
-      checking sha384... sha384sum
-      checking sha256... sha256sum
-    Configuring git-annex-3.20120624...
-    Building git-annex-3.20120624...
-    Preprocessing executable 'git-annex' for git-annex-3.20120624...
-    [  1 of 183] Compiling Utility.Percentage ( Utility/Percentage.hs, dist/build/git-annex/git-annex-tmp/Utility/Percentage.o )
-    [  2 of 183] Compiling Utility.Dot      ( Utility/Dot.hs, dist/build/git-annex/git-annex-tmp/Utility/Dot.o )
-    [  3 of 183] Compiling Utility.ThreadLock ( Utility/ThreadLock.hs, dist/build/git-annex/git-annex-tmp/Utility/ThreadLock.o )
-    [  4 of 183] Compiling Utility.Base64   ( Utility/Base64.hs, dist/build/git-annex/git-annex-tmp/Utility/Base64.o )
-    [  5 of 183] Compiling Utility.DataUnits ( Utility/DataUnits.hs, dist/build/git-annex/git-annex-tmp/Utility/DataUnits.o )
-    [  6 of 183] Compiling Utility.JSONStream ( Utility/JSONStream.hs, dist/build/git-annex/git-annex-tmp/Utility/JSONStream.o )
-    [  7 of 183] Compiling Messages.JSON    ( Messages/JSON.hs, dist/build/git-annex/git-annex-tmp/Messages/JSON.o )
-    [  8 of 183] Compiling Build.SysConfig  ( Build/SysConfig.hs, dist/build/git-annex/git-annex-tmp/Build/SysConfig.o )
-    [  9 of 183] Compiling Types.KeySource  ( Types/KeySource.hs, dist/build/git-annex/git-annex-tmp/Types/KeySource.o )
-    [ 10 of 183] Compiling Types.UUID       ( Types/UUID.hs, dist/build/git-annex/git-annex-tmp/Types/UUID.o )
-    [ 11 of 183] Compiling Utility.State    ( Utility/State.hs, dist/build/git-annex/git-annex-tmp/Utility/State.o )
-    [ 12 of 183] Compiling Types.Messages   ( Types/Messages.hs, dist/build/git-annex/git-annex-tmp/Types/Messages.o )
-    [ 13 of 183] Compiling Types.TrustLevel ( Types/TrustLevel.hs, dist/build/git-annex/git-annex-tmp/Types/TrustLevel.o )
-    [ 14 of 183] Compiling Types.BranchState ( Types/BranchState.hs, dist/build/git-annex/git-annex-tmp/Types/BranchState.o )
-    [ 15 of 183] Compiling Git.Index        ( Git/Index.hs, dist/build/git-annex/git-annex-tmp/Git/Index.o )
-    [ 16 of 183] Compiling Utility.PartialPrelude ( Utility/PartialPrelude.hs, dist/build/git-annex/git-annex-tmp/Utility/PartialPrelude.o )
-    [ 17 of 183] Compiling Utility.Format   ( Utility/Format.hs, dist/build/git-annex/git-annex-tmp/Utility/Format.o )
-    [ 18 of 183] Compiling Utility.FileSystemEncoding ( Utility/FileSystemEncoding.hs, dist/build/git-annex/git-annex-tmp/Utility/FileSystemEncoding.o )
-    [ 19 of 183] Compiling Utility.Touch    ( dist/build/git-annex/git-annex-tmp/Utility/Touch.hs, dist/build/git-annex/git-annex-tmp/Utility/Touch.o )
-    [ 20 of 183] Compiling Utility.Monad    ( Utility/Monad.hs, dist/build/git-annex/git-annex-tmp/Utility/Monad.o )
-    [ 21 of 183] Compiling Utility.Path     ( Utility/Path.hs, dist/build/git-annex/git-annex-tmp/Utility/Path.o )
-    [ 22 of 183] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, dist/build/git-annex/git-annex-tmp/Utility/SafeCommand.o )
-    [ 23 of 183] Compiling Utility.RsyncFile ( Utility/RsyncFile.hs, dist/build/git-annex/git-annex-tmp/Utility/RsyncFile.o )
-    [ 24 of 183] Compiling Utility.Exception ( Utility/Exception.hs, dist/build/git-annex/git-annex-tmp/Utility/Exception.o )
-    [ 25 of 183] Compiling Utility.TempFile ( Utility/TempFile.hs, dist/build/git-annex/git-annex-tmp/Utility/TempFile.o )
-    [ 26 of 183] Compiling Utility.Directory ( Utility/Directory.hs, dist/build/git-annex/git-annex-tmp/Utility/Directory.o )
-    [ 27 of 183] Compiling Utility.Misc     ( Utility/Misc.hs, dist/build/git-annex/git-annex-tmp/Utility/Misc.o )
-    [ 28 of 183] Compiling Git.Types        ( Git/Types.hs, dist/build/git-annex/git-annex-tmp/Git/Types.o )
-    [ 29 of 183] Compiling Common           ( Common.hs, dist/build/git-annex/git-annex-tmp/Common.o )
-    [ 30 of 183] Compiling Utility.FileMode ( Utility/FileMode.hs, dist/build/git-annex/git-annex-tmp/Utility/FileMode.o )
-    [ 31 of 183] Compiling Git              ( Git.hs, dist/build/git-annex/git-annex-tmp/Git.o )
-    [ 32 of 183] Compiling Git.Command      ( Git/Command.hs, dist/build/git-annex/git-annex-tmp/Git/Command.o )
-    [ 33 of 183] Compiling Git.Ref          ( Git/Ref.hs, dist/build/git-annex/git-annex-tmp/Git/Ref.o )
-    [ 34 of 183] Compiling Git.FilePath     ( Git/FilePath.hs, dist/build/git-annex/git-annex-tmp/Git/FilePath.o )
-    [ 35 of 183] Compiling Utility.Matcher  ( Utility/Matcher.hs, dist/build/git-annex/git-annex-tmp/Utility/Matcher.o )
-    [ 36 of 183] Compiling Utility.Gpg      ( Utility/Gpg.hs, dist/build/git-annex/git-annex-tmp/Utility/Gpg.o )
-    [ 37 of 183] Compiling Types.Crypto     ( Types/Crypto.hs, dist/build/git-annex/git-annex-tmp/Types/Crypto.o )
-    [ 38 of 183] Compiling Types.Key        ( Types/Key.hs, dist/build/git-annex/git-annex-tmp/Types/Key.o )
-    [ 39 of 183] Compiling Types.Backend    ( Types/Backend.hs, dist/build/git-annex/git-annex-tmp/Types/Backend.o )
-    [ 40 of 183] Compiling Types.Remote     ( Types/Remote.hs, dist/build/git-annex/git-annex-tmp/Types/Remote.o )
-    [ 41 of 183] Compiling Git.Sha          ( Git/Sha.hs, dist/build/git-annex/git-annex-tmp/Git/Sha.o )
-    [ 42 of 183] Compiling Git.Branch       ( Git/Branch.hs, dist/build/git-annex/git-annex-tmp/Git/Branch.o )
-    [ 43 of 183] Compiling Git.UpdateIndex  ( Git/UpdateIndex.hs, dist/build/git-annex/git-annex-tmp/Git/UpdateIndex.o )
-    [ 44 of 183] Compiling Git.Queue        ( Git/Queue.hs, dist/build/git-annex/git-annex-tmp/Git/Queue.o )
-    [ 45 of 183] Compiling Git.Url          ( Git/Url.hs, dist/build/git-annex/git-annex-tmp/Git/Url.o )
-    [ 46 of 183] Compiling Git.Construct    ( Git/Construct.hs, dist/build/git-annex/git-annex-tmp/Git/Construct.o )
-    [ 47 of 183] Compiling Git.Config       ( Git/Config.hs, dist/build/git-annex/git-annex-tmp/Git/Config.o )
-    [ 48 of 183] Compiling Git.SharedRepository ( Git/SharedRepository.hs, dist/build/git-annex/git-annex-tmp/Git/SharedRepository.o )
-    [ 49 of 183] Compiling Git.Version      ( Git/Version.hs, dist/build/git-annex/git-annex-tmp/Git/Version.o )
-    [ 50 of 183] Compiling Utility.CoProcess ( Utility/CoProcess.hs, dist/build/git-annex/git-annex-tmp/Utility/CoProcess.o )
-    [ 51 of 183] Compiling Git.HashObject   ( Git/HashObject.hs, dist/build/git-annex/git-annex-tmp/Git/HashObject.o )
-    [ 52 of 183] Compiling Git.CatFile      ( Git/CatFile.hs, dist/build/git-annex/git-annex-tmp/Git/CatFile.o )
-    [ 53 of 183] Compiling Git.UnionMerge   ( Git/UnionMerge.hs, dist/build/git-annex/git-annex-tmp/Git/UnionMerge.o )
-    [ 54 of 183] Compiling Git.CheckAttr    ( Git/CheckAttr.hs, dist/build/git-annex/git-annex-tmp/Git/CheckAttr.o )
-    [ 55 of 183] Compiling Annex            ( Annex.hs, dist/build/git-annex/git-annex-tmp/Annex.o )
-    [ 56 of 183] Compiling Types.Option     ( Types/Option.hs, dist/build/git-annex/git-annex-tmp/Types/Option.o )
-    [ 57 of 183] Compiling Types            ( Types.hs, dist/build/git-annex/git-annex-tmp/Types.o )
-    [ 58 of 183] Compiling Messages         ( Messages.hs, dist/build/git-annex/git-annex-tmp/Messages.o )
-    [ 59 of 183] Compiling Types.Command    ( Types/Command.hs, dist/build/git-annex/git-annex-tmp/Types/Command.o )
-    [ 60 of 183] Compiling Locations        ( Locations.hs, dist/build/git-annex/git-annex-tmp/Locations.o )
-    [ 61 of 183] Compiling Common.Annex     ( Common/Annex.hs, dist/build/git-annex/git-annex-tmp/Common/Annex.o )
-    [ 62 of 183] Compiling Annex.Exception  ( Annex/Exception.hs, dist/build/git-annex/git-annex-tmp/Annex/Exception.o )
-    [ 63 of 183] Compiling Annex.BranchState ( Annex/BranchState.hs, dist/build/git-annex/git-annex-tmp/Annex/BranchState.o )
-    [ 64 of 183] Compiling Annex.CatFile    ( Annex/CatFile.hs, dist/build/git-annex/git-annex-tmp/Annex/CatFile.o )
-    [ 65 of 183] Compiling Annex.Perms      ( Annex/Perms.hs, dist/build/git-annex/git-annex-tmp/Annex/Perms.o )
-    [ 66 of 183] Compiling Annex.Journal    ( Annex/Journal.hs, dist/build/git-annex/git-annex-tmp/Annex/Journal.o )
-    [ 67 of 183] Compiling Annex.Branch     ( Annex/Branch.hs, dist/build/git-annex/git-annex-tmp/Annex/Branch.o )
-    [ 68 of 183] Compiling Crypto           ( Crypto.hs, dist/build/git-annex/git-annex-tmp/Crypto.o )
-    [ 69 of 183] Compiling Usage            ( Usage.hs, dist/build/git-annex/git-annex-tmp/Usage.o )
-    [ 70 of 183] Compiling Annex.CheckAttr  ( Annex/CheckAttr.hs, dist/build/git-annex/git-annex-tmp/Annex/CheckAttr.o )
-    [ 71 of 183] Compiling Remote.Helper.Special ( Remote/Helper/Special.hs, dist/build/git-annex/git-annex-tmp/Remote/Helper/Special.o )
-    [ 72 of 183] Compiling Logs.Presence    ( Logs/Presence.hs, dist/build/git-annex/git-annex-tmp/Logs/Presence.o )
-    [ 73 of 183] Compiling Logs.Location    ( Logs/Location.hs, dist/build/git-annex/git-annex-tmp/Logs/Location.o )
-    [ 74 of 183] Compiling Logs.Web         ( Logs/Web.hs, dist/build/git-annex/git-annex-tmp/Logs/Web.o )
-    [ 75 of 183] Compiling Annex.LockPool   ( Annex/LockPool.hs, dist/build/git-annex/git-annex-tmp/Annex/LockPool.o )
-    [ 76 of 183] Compiling Backend.SHA      ( Backend/SHA.hs, dist/build/git-annex/git-annex-tmp/Backend/SHA.o )
-    [ 77 of 183] Compiling Backend.WORM     ( Backend/WORM.hs, dist/build/git-annex/git-annex-tmp/Backend/WORM.o )
-    [ 78 of 183] Compiling Backend.URL      ( Backend/URL.hs, dist/build/git-annex/git-annex-tmp/Backend/URL.o )
-    [ 79 of 183] Compiling Assistant.ThreadedMonad ( Assistant/ThreadedMonad.hs, dist/build/git-annex/git-annex-tmp/Assistant/ThreadedMonad.o )
-    [ 80 of 183] Compiling Logs.UUIDBased   ( Logs/UUIDBased.hs, dist/build/git-annex/git-annex-tmp/Logs/UUIDBased.o )
-    [ 81 of 183] Compiling Logs.Remote      ( Logs/Remote.hs, dist/build/git-annex/git-annex-tmp/Logs/Remote.o )
-    [ 82 of 183] Compiling Utility.DiskFree ( Utility/DiskFree.hs, dist/build/git-annex/git-annex-tmp/Utility/DiskFree.o )
-    [ 83 of 183] Compiling Utility.Url      ( Utility/Url.hs, dist/build/git-annex/git-annex-tmp/Utility/Url.o )
-    [ 84 of 183] Compiling Utility.CopyFile ( Utility/CopyFile.hs, dist/build/git-annex/git-annex-tmp/Utility/CopyFile.o )
-    [ 85 of 183] Compiling Git.LsFiles      ( Git/LsFiles.hs, dist/build/git-annex/git-annex-tmp/Git/LsFiles.o )
-    [ 86 of 183] Compiling Git.AutoCorrect  ( Git/AutoCorrect.hs, dist/build/git-annex/git-annex-tmp/Git/AutoCorrect.o )
-    [ 87 of 183] Compiling Git.CurrentRepo  ( Git/CurrentRepo.hs, dist/build/git-annex/git-annex-tmp/Git/CurrentRepo.o )
-    [ 88 of 183] Compiling Utility.Daemon   ( Utility/Daemon.hs, dist/build/git-annex/git-annex-tmp/Utility/Daemon.o )
-    [ 89 of 183] Compiling Utility.LogFile  ( Utility/LogFile.hs, dist/build/git-annex/git-annex-tmp/Utility/LogFile.o )
-    [ 90 of 183] Compiling Utility.ThreadScheduler ( Utility/ThreadScheduler.hs, dist/build/git-annex/git-annex-tmp/Utility/ThreadScheduler.o )
-    [ 91 of 183] Compiling Assistant.DaemonStatus ( Assistant/DaemonStatus.hs, dist/build/git-annex/git-annex-tmp/Assistant/DaemonStatus.o )
-    [ 92 of 183] Compiling Utility.Types.DirWatcher ( Utility/Types/DirWatcher.hs, dist/build/git-annex/git-annex-tmp/Utility/Types/DirWatcher.o )
-    [ 93 of 183] Compiling Utility.INotify  ( Utility/INotify.hs, dist/build/git-annex/git-annex-tmp/Utility/INotify.o )
-    [ 94 of 183] Compiling Utility.DirWatcher ( Utility/DirWatcher.hs, dist/build/git-annex/git-annex-tmp/Utility/DirWatcher.o )
-    [ 95 of 183] Compiling Utility.Lsof     ( Utility/Lsof.hs, dist/build/git-annex/git-annex-tmp/Utility/Lsof.o )
-    [ 96 of 183] Compiling Git.Merge        ( Git/Merge.hs, dist/build/git-annex/git-annex-tmp/Git/Merge.o )
-    [ 97 of 183] Compiling Git.Filename     ( Git/Filename.hs, dist/build/git-annex/git-annex-tmp/Git/Filename.o )
-    [ 98 of 183] Compiling Git.LsTree       ( Git/LsTree.hs, dist/build/git-annex/git-annex-tmp/Git/LsTree.o )
-    [ 99 of 183] Compiling Config           ( Config.hs, dist/build/git-annex/git-annex-tmp/Config.o )
-    [100 of 183] Compiling Annex.UUID       ( Annex/UUID.hs, dist/build/git-annex/git-annex-tmp/Annex/UUID.o )
-    [101 of 183] Compiling Logs.UUID        ( Logs/UUID.hs, dist/build/git-annex/git-annex-tmp/Logs/UUID.o )
-    [102 of 183] Compiling Backend          ( Backend.hs, dist/build/git-annex/git-annex-tmp/Backend.o )
-    [103 of 183] Compiling Remote.Helper.Hooks ( Remote/Helper/Hooks.hs, dist/build/git-annex/git-annex-tmp/Remote/Helper/Hooks.o )
-    [104 of 183] Compiling Remote.Helper.Encryptable ( Remote/Helper/Encryptable.hs, dist/build/git-annex/git-annex-tmp/Remote/Helper/Encryptable.o )
-    [105 of 183] Compiling Annex.Queue      ( Annex/Queue.hs, dist/build/git-annex/git-annex-tmp/Annex/Queue.o )
-    [106 of 183] Compiling Annex.Content    ( Annex/Content.hs, dist/build/git-annex/git-annex-tmp/Annex/Content.o )
-    [107 of 183] Compiling Remote.S3        ( Remote/S3.hs, dist/build/git-annex/git-annex-tmp/Remote/S3.o )
-    [108 of 183] Compiling Remote.Directory ( Remote/Directory.hs, dist/build/git-annex/git-annex-tmp/Remote/Directory.o )
-    [109 of 183] Compiling Remote.Rsync     ( Remote/Rsync.hs, dist/build/git-annex/git-annex-tmp/Remote/Rsync.o )
-    [110 of 183] Compiling Remote.Web       ( Remote/Web.hs, dist/build/git-annex/git-annex-tmp/Remote/Web.o )
-    [111 of 183] Compiling Remote.Hook      ( Remote/Hook.hs, dist/build/git-annex/git-annex-tmp/Remote/Hook.o )
-    [112 of 183] Compiling Upgrade.V2       ( Upgrade/V2.hs, dist/build/git-annex/git-annex-tmp/Upgrade/V2.o )
-    [113 of 183] Compiling Assistant.Changes ( Assistant/Changes.hs, dist/build/git-annex/git-annex-tmp/Assistant/Changes.o )
-    
-    Assistant/Changes.hs:73:30:
-        Not in scope: `tryReadTChan'
-        Perhaps you meant `readTChan' (imported from Control.Concurrent.STM)
-    cabal: Error: some packages failed to install:
-    git-annex-3.20120624 failed during the building phase. The exception was:
-    ExitFailure 1
-
-This is using haskell-platform 2012.1.0.0~debian1 on Ubuntu 12.04.
-
-> Turns out it needs version 2.3 of the STM library. (libghc-stm-dev
-> package). I've made cabal detect an older version and skip building
-> the new `git annex watch` command, so you'll be able to build the next
-> release. [[done]] --[[Joey]]
diff --git a/doc/bugs/error_propigation.mdwn b/doc/bugs/error_propigation.mdwn
deleted file mode 100644
index 25998907e..000000000
--- a/doc/bugs/error_propigation.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-If a subcommand fails w/o throwing an error, no error is propigated to the
-git-annex exit code. With --quiet, this makes it look like the command
-succeeded. [[done]]
diff --git a/doc/bugs/error_when_using_repositories_with_non-ASCII_characters.mdwn b/doc/bugs/error_when_using_repositories_with_non-ASCII_characters.mdwn
deleted file mode 100644
index d88b86b44..000000000
--- a/doc/bugs/error_when_using_repositories_with_non-ASCII_characters.mdwn
+++ /dev/null
@@ -1,62 +0,0 @@
-*What steps will reproduce the problem?*
-
-    hactar% mkdir demonstração
-    hactar% cd demonstração
-    hactar% cp ~/tmp/*(.) .
-    hactar% git init
-    Initialized empty Git repository in /tmp/demonstração/.git/
-    hactar% git annex init
-    init  ok
-    (Recording state in git...)
-    hactar% git annex add .
-    add Equipment Consumption.ods (checksum...) ok
-    add Personal.vcard (checksum...) ok
-    add Trampo.vcard (checksum...) ok
-    add blah.txt (checksum...) ok
-    [ more git output ]
-    hactar% git commit -m initial
-    [master (root-commit) d16bafb] initial
-     42 files changed, 42 insertions(+)
-    [ more git output ]
-    hactar% cd /var/tmp
-    hactar% git clone ssh://localhost//tmp/demonstração demonstração
-    Cloning into 'demonstração'...
-    remote: Counting objects: 176, done.
-    remote: Compressing objects: 100% (134/134), done.
-    remote: Total 176 (delta 1), reused 0 (delta 0)
-    Receiving objects: 100% (176/176), 17.23 KiB, done.
-    Resolving deltas: 100% (1/1), done.
-    hactar% cd demonstração
-    hactar% git annex init
-    init  ok
-    (Recording state in git...)
-    hactar% git annex status
-    supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-    supported remote types: git S3 bup directory rsync web hook
-    trusted repositories: (merging origin/git-annex into git-annex...)
-
-    git-annex: fd:14: commitBuffer: invalid argument (invalid character)
-    failed
-    git-annex: status: 1 failed
-
-*What is the expected output? What do you see instead?*
-
-I expect that "git annex status" will complete successfuly and show information about all repositories.
-Instead of that I get the "git-annex: fd:14: commitBuffer: invalid argument (invalid character)" error above.
-
-*What version of git-annex are you using? On what operating system?*
-
-This is with Debian's git-annex_3.20121001_i386.deb installed on an Ubuntu 12.04 system.
-Using Ubuntu's original version (3.20120406) the error message is a bit different (here I used the name acentuação instead of demonstração):
-
-    trusted repositories: git-annex-shell: //tmp/acentuação: changeWorkingDirectory: does not exist (No such file or directory)
-    Command ssh ["-S","/var/tmp/acentua\231\227o/.git/annex/ssh/localhost","-o","ControlMaster=auto","-o","ControlPersist=yes","localhost","git-annex-shell 'configlist' '//tmp/acentua\195\167\195\163o'"] failed; exit code 1
-
-> I think this is the last unvalid utf-8 bug in git-annex. At least,
-> the last one I hypothesized exists. It's in the union merge code. I will
-> try to look at it again soon; the last 2 times I looked at that code
-> I could not see an easy way to make it allow invalid utf-8 encoded data.
-> --[[Joey]] 
-
->> [[done]], although I am no longer so sure this was the last utf-8
->> encoding bug.. --[[Joey]]
diff --git a/doc/bugs/error_when_using_repositories_with_non-ASCII_characters/comment_1_38cc2d2ed907649df085de8ad83cb9dd._comment b/doc/bugs/error_when_using_repositories_with_non-ASCII_characters/comment_1_38cc2d2ed907649df085de8ad83cb9dd._comment
deleted file mode 100644
index 69d7f1da1..000000000
--- a/doc/bugs/error_when_using_repositories_with_non-ASCII_characters/comment_1_38cc2d2ed907649df085de8ad83cb9dd._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmcYryijvlF8bJvM_eZNSrUPEkMlxMDGTQ"
- nickname="Thiago"
- subject="The bug is actually something completely different!"
- date="2012-10-04T03:53:57Z"
- content="""
-Ok, this is a mix of luser error and a bug.
-
-I noticed that I wasn't providing a description in git annex init. So if I do \"git annex init foo\" in the first repository and \"git annex init bar\" in the clone, then git annex status works!
-
-So the bug is actually that you need to provide a description in git annex init, even though the man page says a description will be generated otherwise.
-
-(In my defense I hit the non-ACII characters bug with the git annex version in Ubuntu, and that one still has the same error even if a description is provided so this was fixed later).
-"""]]
diff --git a/doc/bugs/error_with_file_names_starting_with_dash.mdwn b/doc/bugs/error_with_file_names_starting_with_dash.mdwn
deleted file mode 100644
index 84bf1cfa0..000000000
--- a/doc/bugs/error_with_file_names_starting_with_dash.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-git annex add has problems if items start with dashes, example:
-
--wut-a-directory-name-/file1
-
-leads to
-
-[[!format bash """
-add -wut-a-directory-name-/file1 (checksum...) sha1sum: invalid option -- 'u'
-„sha1sum --help“ gibt weitere Informationen.
-
-  git-annex: <file descriptor: 15>: hGetLine: end of file
-"""]]
-
-> This is fixed in git, at least I think I've found all cases where
-> filenames are passed to programs and escaped them. --[[Joey]] [[done]]
diff --git a/doc/bugs/fails_to_handle_lot_of_files.mdwn b/doc/bugs/fails_to_handle_lot_of_files.mdwn
deleted file mode 100644
index 470a5180f..000000000
--- a/doc/bugs/fails_to_handle_lot_of_files.mdwn
+++ /dev/null
@@ -1,445 +0,0 @@
-    git-annex version: 3.20111011
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3
-    upgrade supported from repository versions: 0 1 2
-
-I just created a new remote on a USB drive and wanted to copy my files over. git-annex wasn't too happy about that ;)
-I included a few OK transfers as there was an error before git-annex ran into a wall. As I could easily access that temp file after it aborted, I suspect something went wrong internally before git-annex started to throw those errors.
-
-Please note the "_n TIMES_" comments. It's how often I got the same error message...
-
-
-
-    git annex copy . --to USB --fast
-    
-    copy redacted.JPG (to USB...) 
-    redacted
-         4035668 100%   77.91MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4036374 bytes  received 31 bytes  8072810.00 bytes/sec
-    total size is 4035668  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18002094 100%   74.19MB/s    0:00:00 (xfer#1, to-check=0/1)
-    WARNING: redacted failed verification -- update retained (will try again).
-    redacted
-        18002094 100%   19.60MB/s    0:00:00 (xfer#2, to-check=0/1)
-    rsync: open "copy_target/.git/annex/tmp/redacted_E13" failed: Permission denied (13)
-    
-    sent 36008841 bytes  received 52 bytes  24005928.67 bytes/sec
-    total size is 18002094  speedup is 0.50
-    rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.8]
-    
-      rsync failed -- run git annex again to resume file transfer
-    failed
-    copy redacted.JPG (to USB...) 
-    redacted
-         3687111 100%   39.16MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 3687773 bytes  received 31 bytes  2458536.00 bytes/sec
-    total size is 3687111  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17877177 100%   79.15MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17879573 bytes  received 31 bytes  11919736.00 bytes/sec
-    total size is 17877177  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         3694921 100%   40.14MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 3695583 bytes  received 31 bytes  2463742.67 bytes/sec
-    total size is 3694921  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17875448 100%   71.20MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17877844 bytes  received 31 bytes  11918583.33 bytes/sec
-    total size is 17875448  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         3833377 100%   62.49MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 3834055 bytes  received 31 bytes  2556057.33 bytes/sec
-    total size is 3833377  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17938200 100%   65.43MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17940604 bytes  received 31 bytes  11960423.33 bytes/sec
-    total size is 17938200  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4512557 100%   83.77MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4513319 bytes  received 31 bytes  3008900.00 bytes/sec
-    total size is 4512557  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18001641 100%   76.16MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18004053 bytes  received 31 bytes  12002722.67 bytes/sec
-    total size is 18001641  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4394272 100%   50.11MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4395022 bytes  received 31 bytes  8790106.00 bytes/sec
-    total size is 4394272  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18095781 100%   73.30MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18098205 bytes  received 31 bytes  12065490.67 bytes/sec
-    total size is 18095781  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4683795 100%   65.23MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4684577 bytes  received 31 bytes  9369216.00 bytes/sec
-    total size is 4683795  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18172801 100%   74.25MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18175233 bytes  received 31 bytes  36350528.00 bytes/sec
-    total size is 18172801  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4486231 100%   77.22MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4486989 bytes  received 31 bytes  8974040.00 bytes/sec
-    total size is 4486231  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17860427 100%   68.56MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17862823 bytes  received 31 bytes  35725708.00 bytes/sec
-    total size is 17860427  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4499768 100%   36.41MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4500530 bytes  received 31 bytes  9001122.00 bytes/sec
-    total size is 4499768  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17840132 100%   74.48MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17842524 bytes  received 31 bytes  11895036.67 bytes/sec
-    total size is 17840132  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4358032 100%   75.00MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4358774 bytes  received 31 bytes  8717610.00 bytes/sec
-    total size is 4358032  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18084753 100%   61.48MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18087173 bytes  received 31 bytes  12058136.00 bytes/sec
-    total size is 18084753  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4270213 100%   68.49MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4270947 bytes  received 31 bytes  2847318.67 bytes/sec
-    total size is 4270213  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17661246 100%   68.34MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17663614 bytes  received 31 bytes  11775763.33 bytes/sec
-    total size is 17661246  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4538305 100%   63.19MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4539071 bytes  received 31 bytes  9078204.00 bytes/sec
-    total size is 4538305  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18672466 100%   68.90MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18674958 bytes  received 31 bytes  12449992.67 bytes/sec
-    total size is 18672466  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4453445 100%   73.96MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4454199 bytes  received 31 bytes  8908460.00 bytes/sec
-    total size is 4453445  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18495494 100%   59.28MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18497966 bytes  received 31 bytes  12331998.00 bytes/sec
-    total size is 18495494  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4255858 100%   70.66MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4256588 bytes  received 31 bytes  1702647.60 bytes/sec
-    total size is 4255858  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18376531 100%   69.15MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18378987 bytes  received 31 bytes  36758036.00 bytes/sec
-    total size is 18376531  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4013365 100%   48.67MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4014067 bytes  received 31 bytes  8028196.00 bytes/sec
-    total size is 4013365  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17606341 100%   51.73MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17608705 bytes  received 31 bytes  11739157.33 bytes/sec
-    total size is 17606341  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4179869 100%   74.62MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4180591 bytes  received 31 bytes  8361244.00 bytes/sec
-    total size is 4179869  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18382569 100%   67.05MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18385025 bytes  received 31 bytes  12256704.00 bytes/sec
-    total size is 18382569  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4318363 100%   44.91MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4319101 bytes  received 31 bytes  8638264.00 bytes/sec
-    total size is 4318363  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17715958 100%   72.69MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17718334 bytes  received 31 bytes  11812243.33 bytes/sec
-    total size is 17715958  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4241893 100%   65.81MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4242623 bytes  received 31 bytes  8485308.00 bytes/sec
-    total size is 4241893  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17717287 100%   71.77MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17719663 bytes  received 31 bytes  11813129.33 bytes/sec
-    total size is 17717287  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4488380 100%   49.99MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4489138 bytes  received 31 bytes  2992779.33 bytes/sec
-    total size is 4488380  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        17770208 100%   38.80MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 17772592 bytes  received 31 bytes  11848415.33 bytes/sec
-    total size is 17770208  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4603958 100%   76.48MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4604732 bytes  received 31 bytes  9209526.00 bytes/sec
-    total size is 4603958  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18744380 100%   74.66MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18746884 bytes  received 31 bytes  12497943.33 bytes/sec
-    total size is 18744380  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4592098 100%   79.06MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4592872 bytes  received 31 bytes  3061935.33 bytes/sec
-    total size is 4592098  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18746205 100%   43.00MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18748709 bytes  received 31 bytes  12499160.00 bytes/sec
-    total size is 18746205  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         7493353 100%   80.85MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 7494479 bytes  received 31 bytes  14989020.00 bytes/sec
-    total size is 7493353  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        19496768 100%   81.77MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 19499360 bytes  received 31 bytes  12999594.00 bytes/sec
-    total size is 19496768  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         5462482 100%   82.19MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 5463360 bytes  received 31 bytes  10926782.00 bytes/sec
-    total size is 5462482  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        19669815 100%   80.37MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 19672431 bytes  received 31 bytes  13114974.67 bytes/sec
-    total size is 19669815  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         5449487 100%   57.40MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 5450365 bytes  received 31 bytes  3633597.33 bytes/sec
-    total size is 5449487  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        19633259 100%   74.18MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 19635871 bytes  received 31 bytes  13090601.33 bytes/sec
-    total size is 19633259  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         5392184 100%   62.33MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 5393054 bytes  received 31 bytes  3595390.00 bytes/sec
-    total size is 5392184  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        18912104 100%   65.00MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 18914628 bytes  received 31 bytes  12609772.67 bytes/sec
-    total size is 18912104  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4869300 100%   80.92MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4870106 bytes  received 31 bytes  9740274.00 bytes/sec
-    total size is 4869300  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        20178932 100%   68.13MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 20181608 bytes  received 31 bytes  13454426.00 bytes/sec
-    total size is 20178932  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         4995425 100%   86.05MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 4996247 bytes  received 31 bytes  9992556.00 bytes/sec
-    total size is 4995425  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        19970679 100%   76.36MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 19973331 bytes  received 31 bytes  13315574.67 bytes/sec
-    total size is 19970679  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         7905795 100%   66.45MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 7906973 bytes  received 31 bytes  15814008.00 bytes/sec
-    total size is 7905795  speedup is 1.00
-    ok
-    copy redacted.NEF (to USB...) 
-    redacted
-        21234069 100%   78.07MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 21236877 bytes  received 31 bytes  8494763.20 bytes/sec
-    total size is 21234069  speedup is 1.00
-    ok
-    copy redacted.JPG (to USB...) 
-    redacted
-         7963979 100%   62.51MB/s    0:00:00 (xfer#1, to-check=0/1)
-    
-    sent 7965165 bytes  received 31 bytes  5310130.67 bytes/sec
-    total size is 7963979  speedup is 1.00
-    git ["--git-dir=copy_target/.git","--work-tree=copy_target","update-index","-z","--index-info"]: Error in fork: forkProcess: resource exhausted (Resource temporarily unavailable)
-    
-    git-annex: user error (git ["--git-dir=copy_target/.git","--work-tree=copy_target","update-index","-z","--index-info"]: Error in fork: forkProcess: resource exhausted (Resource temporarily unavailable))
-    failed
-    _506 TIMES_ (user error (Error in fork: forkProcess: resource exhausted (Resource temporarily unavailable))) failed
-    _11 TIMES_ copy foo (createPipe: resource exhausted (Too many open files)) failed
-    _2 TIMES_ (user error (Error in fork: forkProcess: resource exhausted (Resource temporarily unavailable))) failed
-    _8574 TIMES_: copy foo (createPipe: resource exhausted (Too many open files)) failed
-    git-annex: createPipe: resource exhausted (Too many open files)
-    failed
-    git-annex: 9101 failed
-    
-    % ls copy_target/.git/annex/tmp/redacted_E13 copy_target/.git/annex/tmp/SHA512E-redacted_E13 # works
-    % find source -type l | wc -l
-    13554
-    % find copy_target -type l | wc -l
-    13554
-    % find copy_target/.git/annex/objects -type f | wc -l
-    4455
-    % find source -type f | wc -l
-    13554
-
-> Fixed unreaped process leak.
-> (This has nothing to do with NTFS). Ran test with 10k files
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/fails_to_handle_lot_of_files/comment_1_09d8e4e66d8273fab611bd29e82dc7fc._comment b/doc/bugs/fails_to_handle_lot_of_files/comment_1_09d8e4e66d8273fab611bd29e82dc7fc._comment
deleted file mode 100644
index 587b1fd97..000000000
--- a/doc/bugs/fails_to_handle_lot_of_files/comment_1_09d8e4e66d8273fab611bd29e82dc7fc._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-10-26T17:16:52Z"
- content="""
-After another run, i am at 8909 files in the remote, now.
-"""]]
diff --git a/doc/bugs/fails_to_handle_lot_of_files/comment_2_fd2ec05f4b5a7a6ae6bd9f5dbc3156de._comment b/doc/bugs/fails_to_handle_lot_of_files/comment_2_fd2ec05f4b5a7a6ae6bd9f5dbc3156de._comment
deleted file mode 100644
index 8e83fc19f..000000000
--- a/doc/bugs/fails_to_handle_lot_of_files/comment_2_fd2ec05f4b5a7a6ae6bd9f5dbc3156de._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2011-10-26T18:22:34Z"
- content="""
-In case this matters, I just realized that this disk has been formatted with NTFS instead of a sane FS.
-"""]]
diff --git a/doc/bugs/fatal:_Out_of_memory__63___mmap_failed:_No_error.mdwn b/doc/bugs/fatal:_Out_of_memory__63___mmap_failed:_No_error.mdwn
deleted file mode 100644
index d4bb7bede..000000000
--- a/doc/bugs/fatal:_Out_of_memory__63___mmap_failed:_No_error.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-### Please describe the problem.
-
-When adding files, the error
-
- fatal: Out of memory? mmap failed: No error
-
-appears 
-
-
-### What steps will reproduce the problem?
-
-In Windows, I have a directory with 8GB and 333.820 files (of course, in different directory, the big one is probably the Android SDK).
-
-### What version of git-annex are you using? On what operating system?
-
-Windows 8.
-
- $ git annex version
- git-annex version: 5.20140411-gda795e0
- build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash
- key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
- remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external
- local repository version: 5
- supported repository version: 5
- upgrade supported from repository versions: 2 3 4
-
-
-### Please provide any additional information below.
-
-
-> closing as not a git-annex bug at all, but a git bug. [[done]] --[[Joey]]
diff --git a/doc/bugs/fatal:_Out_of_memory__63___mmap_failed:_No_error/comment_1_3bc14a8b093ebb2c0571f5a554ef8cf3._comment b/doc/bugs/fatal:_Out_of_memory__63___mmap_failed:_No_error/comment_1_3bc14a8b093ebb2c0571f5a554ef8cf3._comment
deleted file mode 100644
index bf120c20a..000000000
--- a/doc/bugs/fatal:_Out_of_memory__63___mmap_failed:_No_error/comment_1_3bc14a8b093ebb2c0571f5a554ef8cf3._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.191"
- subject="comment 1"
- date="2014-04-17T17:25:29Z"
- content="""
-That error message is a git error message (from git's `wrapper.c`), not a git-annex error message.
-
-It's quite possible that git does not scale to as many file on Windows as it does on Unix, and git is known to not scale particularly well to vast numbers of files even on unix, although running out of memory is not the typical failure mode there.
-
-I think you should file a bug report on git.
-"""]]
diff --git a/doc/bugs/fatal:_empty_ident_name.mdwn b/doc/bugs/fatal:_empty_ident_name.mdwn
deleted file mode 100644
index 241477287..000000000
--- a/doc/bugs/fatal:_empty_ident_name.mdwn
+++ /dev/null
@@ -1,51 +0,0 @@
-**What steps will reproduce the problem?**
-
-    stone@skynet ~/annex $ git init
-    Initialized empty Git repository in /home/stone/annex/.git/
-    stone@skynet ~/annex $ git annex init "work"
-    init work 
-    *** Please tell me who you are.
-    
-    Run
-    
-      git config --global user.email "you@example.com"
-      git config --global user.name "Your Name"
-    
-    to set your account's default identity.
-    Omit --global to set the identity only in this repository.
-    
-    fatal: empty ident name (for <stone@skynet>) not allowed
-    git-annex: git ["--git-dir=/home/stone/annex/.git","--work-tree=/home/stone/annex","commit-tree","4b825dc652cb6eb9a060e64bf8d69288fbee4904"] exited 128
-    stone@skynet ~/annex $ git config -l
-    user.email=stone@nospam.hu
-    user.name=Stone
-    core.editor=nano
-    color.ui=auto
-    core.repositoryformatversion=0
-    core.filemode=true
-    core.bare=false
-    core.logallrefupdates=true
-    annex.uuid=499fb545-0b98-4bfc-816c-fb3704f3aaa0
-    stone@skynet ~/annex $ cat ~/.gitconfig 
-    [user]
-    	email = stone@nospam.hu
-    	name = Stone
-    [core]
-    	editor = nano
-    [color]
-    	ui = auto
-    stone@skynet ~/annex $ 
-
-**What is the expected output? What do you see instead?**
-
-
-**What version of git-annex are you using? On what operating system?**
-
-commit 56c037c69e75def74d6ea90de8aa8a1954c52178 Arch Linux
-
-**Please provide any additional information below.**
-
-> [[done]] by adding name to the user, in /etc/passwd. --Stone
-
->> Actually, [[done]] by avoiding clobbering HOME when running some git
->> commands. --[[Joey]]
diff --git a/doc/bugs/fatal:_empty_ident_name/comment_1_ceae87308fb75a1f79c7c8d63ec47226._comment b/doc/bugs/fatal:_empty_ident_name/comment_1_ceae87308fb75a1f79c7c8d63ec47226._comment
deleted file mode 100644
index 798658a46..000000000
--- a/doc/bugs/fatal:_empty_ident_name/comment_1_ceae87308fb75a1f79c7c8d63ec47226._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.16"
- subject="comment 1"
- date="2012-08-31T15:04:09Z"
- content="""
-This is an error message from git. [Git faq](https://git.wiki.kernel.org/index.php/GitFaq#Git_commit_is_dying_telling_me_.22fatal:_empty_ident_.3Cuser.40myhost.3E_not_allowed.22.2C_what.27s_wrong.3F). I don't understand why git is doing it given the configuration shown, but I suppose it would do the same thing if you run git commit by hand.
-"""]]
diff --git a/doc/bugs/fatal:_empty_ident_name/comment_2_68832ee3e0e7244ce62bccabe2e52630._comment b/doc/bugs/fatal:_empty_ident_name/comment_2_68832ee3e0e7244ce62bccabe2e52630._comment
deleted file mode 100644
index 934fcdfaf..000000000
--- a/doc/bugs/fatal:_empty_ident_name/comment_2_68832ee3e0e7244ce62bccabe2e52630._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl1yBP_JDsO1TWSC1usoHXpfDRU01u_GXY"
- nickname="Péter Károly"
- subject="comment 2"
- date="2012-08-31T18:30:15Z"
- content="""
-I use git on the same machine nearly every day, it does not complain on commit.
-
-(On the same session after \"git annex init\" failed...)
-
-    stone@skynet ~/annex $ echo stone > bu
-    stone@skynet ~/annex $ git add bu 
-    stone@skynet ~/annex $ git commit -a
-    [master (root-commit) ae5d41f] ds
-     1 file changed, 1 insertion(+)
-     create mode 100644 bu
-    stone@skynet ~/annex $ git log
-    commit ae5d41fdd0b7082740633cf7931bb5a07be0fc5e
-    Author: Stone <stone@nospam.hu>
-    Date:   Fri Aug 31 20:26:45 2012 +0200
-    
-        ds
-    stone@skynet ~/annex $ 
-
-"""]]
diff --git a/doc/bugs/fatal:_empty_ident_name/comment_3_ed31ad316747343d7730e4c2d7dacd24._comment b/doc/bugs/fatal:_empty_ident_name/comment_3_ed31ad316747343d7730e4c2d7dacd24._comment
deleted file mode 100644
index ff7f39e44..000000000
--- a/doc/bugs/fatal:_empty_ident_name/comment_3_ed31ad316747343d7730e4c2d7dacd24._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.16"
- subject="comment 3"
- date="2012-08-31T18:52:53Z"
- content="""
-Why don't you try the identical command that git-annex is running that fails:
-
-`git --git-dir=/home/stone/annex/.git --work-tree=/home/stone/annex commit-tree 4b825dc652cb6eb9a060e64bf8d69288fbee4904`
-"""]]
diff --git a/doc/bugs/fatal:_empty_ident_name/comment_4_b812d6f30e8a866bce7260a9ee3218e3._comment b/doc/bugs/fatal:_empty_ident_name/comment_4_b812d6f30e8a866bce7260a9ee3218e3._comment
deleted file mode 100644
index 9e8a1900e..000000000
--- a/doc/bugs/fatal:_empty_ident_name/comment_4_b812d6f30e8a866bce7260a9ee3218e3._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl1yBP_JDsO1TWSC1usoHXpfDRU01u_GXY"
- nickname="Péter Károly"
- subject="comment 4"
- date="2012-09-01T15:05:52Z"
- content="""
-Finally I managed to get it working.
-
-My use on the computer didn't had name, so the 5th colum of my /etc/password file was empty. After I filled in my name everything worked like charm.
-
-Interesting that not my user's name from /etc/passwd get into the git log but the one that was in my ~/.gitconfig.
-
-"""]]
diff --git a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__.mdwn b/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__.mdwn
deleted file mode 100644
index f81abb9d5..000000000
--- a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__.mdwn
+++ /dev/null
@@ -1,52 +0,0 @@
-### Please describe the problem.
-git annex status returns:
-
-annexed files in working tree: fatal: git ls-files: cannot generate relative filenames containing '..'
-
-There are unlocked files mixed with locked (symlinked) throughout the repository after a commit. 
-Perhaps my repo is in an inconsistent state?
-
-### What steps will reproduce the problem?
-Run git annex status
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20131106.  Redhat EL6 running on KVM.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-[username@box pnt]$ git annex status
-repository mode: indirect
-trusted repositories: 0
-semitrusted repositories: 2
-        00000000-0000-0000-0000-000000000001 -- web
-        1ff41d2d-02bd-4795-88b9-bf3fbbeabef7 -- here
-untrusted repositories: 0
-transfers in progress: none
-available local disk space: 36.86 terabytes (+1 megabyte reserved)
-local annex keys: 35750
-local annex size: 251.11 gigabytes
-annexed files in working tree: fatal: git ls-files: cannot generate relative filenames containing '..'
-0
-size of annexed files in working tree: 0 bytes
-bloom filter size: 16 mebibytes (7.2% full)
-backend usage: 
-        SHA256: 18471
-        SHA256E: 17279
-[username@box pnt]$ git annex version
-git-annex version: 4.20131106
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-
-# End of transcript or log.
-"""]]
-
-> Added note about git version to from scratch installation instructions.
-> Debian package already depends on a newer version. [[done]] --[[Joey]]
diff --git a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_1_8a4045634bffc29c8147056096b7089d._comment b/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_1_8a4045634bffc29c8147056096b7089d._comment
deleted file mode 100644
index d5bda1344..000000000
--- a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_1_8a4045634bffc29c8147056096b7089d._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 1"
- date="2013-12-16T16:05:38Z"
- content="""
-Do you get the same error message if you run:
-
-git -c core.bare=false ls-files --cached --others
-
-What version of git? I cannot find that error message anywhere in the current version.
-
-"""]]
diff --git a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_2_a1539aaec74074b4667ac27cfcfcccd6._comment b/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_2_a1539aaec74074b4667ac27cfcfcccd6._comment
deleted file mode 100644
index a73bc78e3..000000000
--- a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_2_a1539aaec74074b4667ac27cfcfcccd6._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnWaZGX4m5Oic-vvIKUJHZLrY5W1G7mtQ4"
- nickname="Andrew"
- subject="comment 2"
- date="2013-12-16T16:11:24Z"
- content="""
-[username@box pnt]$ git -c core.bare=false ls-files --cached --others
-Unknown option: -c
-usage: git [--version] [--exec-path[=GIT_EXEC_PATH]] [--html-path]
-           [-p|--paginate|--no-pager] [--no-replace-objects]
-           [--bare] [--git-dir=GIT_DIR] [--work-tree=GIT_WORK_TREE]
-           [--help] COMMAND [ARGS]
-
-[username@box pnt]$ git --version
-git version 1.7.1
-"""]]
diff --git a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_3_d252f39ddb9c9c14784c85a8b850a4ec._comment b/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_3_d252f39ddb9c9c14784c85a8b850a4ec._comment
deleted file mode 100644
index 33514aa1c..000000000
--- a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_3_d252f39ddb9c9c14784c85a8b850a4ec._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 3"
- date="2013-12-16T16:27:28Z"
- content="""
-You can leave off the -c core.bare=false, if your git does not support it.
-
-That is an exceptionally old version of git. I'm sure it's the problem, so you should upgrade.
-"""]]
diff --git a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_4_eb07c84dc0b15b68c99d0ef4144f82f5._comment b/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_4_eb07c84dc0b15b68c99d0ef4144f82f5._comment
deleted file mode 100644
index 4791d9dc4..000000000
--- a/doc/bugs/fatal:_git_ls-files:_cannot_generate_relative_filenames_containing___39__..__39__/comment_4_eb07c84dc0b15b68c99d0ef4144f82f5._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnWaZGX4m5Oic-vvIKUJHZLrY5W1G7mtQ4"
- nickname="Andrew"
- subject="comment 4"
- date="2013-12-16T20:16:26Z"
- content="""
-Built and installed Git 1.8.5 from source and the problem went away.
-
-Thanks!
-"""]]
diff --git a/doc/bugs/feature_request:_addhash.mdwn b/doc/bugs/feature_request:_addhash.mdwn
deleted file mode 100644
index e818a3327..000000000
--- a/doc/bugs/feature_request:_addhash.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-### Use case 1
-
-I have a big repo using a SHA256E back-end. Along comes a new shiny SKEIN512E back-end and I would like to transition to using that, because it's faster and moves from ridiculously to ludicrously low risk of collisions.
-
-I can set `.gitattributes` to use the new back-end for any new files added, but then I when I import some arbitrary mix of existing and new files to the repo it will not deduplicate any more, it will add all the files under the new hash scheme.
-
-### Use case 2
-
-I have a big repo of files I have added using `addurl --fast`. I download the files, and they are in the repo.
-
- - I cannot verify later that none of them have been damaged.
- - If I come across an offline collection of some of the files, I cannot easily get them into the annex by a simple import.
-
-### Workaround
-
-In both these cases, what I can do is <del>unlock (maybe?) or unannex (definitely) all of the files, and then re-add them using the new hash</del> <em>use `migrate` to relink the files using the new scheme</em>. In both use cases this means I now risk having duplicates in various clones of the repo, and would have to clean them up with `drop-unused` -- after first having re-copied them from a repo that has them under the new hash <em>or `migrate`d them in each clone using the pre-migration commit; Either way is problematic for special remotes, in particular glacier</em>. I also lose the continuity of the history of that object.
-
-<del>In use case 2 I also lose the URLs of the files and would have to re-add them using `addurl`.</del> <em>This is probably not true when using `migrate`.</em>
-
-... which brings me to the proposed feature.
-
-### addhash
-
-Symmetrical to `addurl`, which in one form can take an existing hashed (or URL-sourced) file and add an URL source to it, `addhash` can take an existing URL-sourced (or hashed) file and add a hash reference to it (given that the file is in the annex so that the hash may be calculated) -- an alias under which it may also be identified, in addition to the existing URL or hash.
-
- - Any file added to the annex after `addhash` will use the symlink name of the original hash if their hash matches the `addhash`ed one.
- - An `fsck` run will use one of the available hashes to verify the integrity of the file, maybe according to some internal order of preference, or possibly a configurable one.
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/feature_request:_addhash/comment_1_064e963adb6834813380fd836bb58566._comment b/doc/bugs/feature_request:_addhash/comment_1_064e963adb6834813380fd836bb58566._comment
deleted file mode 100644
index 60757d7ba..000000000
--- a/doc/bugs/feature_request:_addhash/comment_1_064e963adb6834813380fd836bb58566._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 1"
- date="2013-12-15T19:45:25Z"
- content="""
-This exists, it's `git annex migrate`
-"""]]
diff --git a/doc/bugs/feature_request:_addhash/comment_2_7b712786c580dd1ca24479664c31eed6._comment b/doc/bugs/feature_request:_addhash/comment_2_7b712786c580dd1ca24479664c31eed6._comment
deleted file mode 100644
index fde99e889..000000000
--- a/doc/bugs/feature_request:_addhash/comment_2_7b712786c580dd1ca24479664c31eed6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://id.clacke.se/"
- nickname="clacke"
- subject="Re: git annex migrate"
- date="2013-12-17T22:04:09Z"
- content="""
-`migrate` replaces the manual work described in \"Workaround\", but has the drawback described in its own manual -- the content is now available under two keys in the annex. This proposal adds one layer of abstraction to avoid that duplication. It's entirely possible that this layer of abstraction is a bad idea with horrible complexity and/or performance issues, but I wanted to put this idea out there.
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn b/doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn
deleted file mode 100644
index 701536844..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn
+++ /dev/null
@@ -1,54 +0,0 @@
-### Please describe the problem.
-
-I have a latex file which takes two passes to build.  It is in a directory managed by git-annex assistant and configured to use a remote SSH server as a transfer back-end.
-
-If I use latexmk to build the file with the git-assistant on then the build fails.  If I turn off the git-assistant it succeeds.
-
-### What steps will reproduce the problem?
-
-[[!format sh """
-~/current/www.cmt.mhs.man.ac.uk $ git-annex assistant --autostart
-~/current/www.cmt.mhs.man.ac.uk $ latexmk -c admin_guide_cmt.tex
-~/current/www.cmt.mhs.man.ac.uk $ latexmk -pdf -silent admin_guide_cmt.tex
-
-Latexmk: Run number 1 of rule 'pdflatex'
-This is pdfTeX, Version 3.1415926-2.5-1.40.13 (TeX Live 2013/dev)
- restricted \write18 enabled.
-entering extended mode
-print() on closed filehandle GEN32 at /usr/bin/latexmk line 4742.
-print() on closed filehandle GEN32 at /usr/bin/latexmk line 4759.
-print() on closed filehandle GEN32 at /usr/bin/latexmk line 4761.
-"""]]
-
-Dropping the silent option shows that the admin_guide_cmt.aux file is not available for writing - despite being created.  I suspect that the assistant is somehow locking the file, or using it between passes of latex.  If the auxillary files all ready exist then there is no problem (i.e., don't do the cleanup via latexmk -c)
-
-Disabling the assistant makes everything work.  Latexmk is doing something odd - I can't replicate with the native latex build commands.
-
-### What version of git-annex are you using? On what operating system?
-
-Latest version, via cabal, on Fedora 18.
-
-### Please provide any additional information below.
-
-Nothing appears wrong with the assistant transfer wise.
-[[!format sh """
-add www.cmt.mhs.man.ac.uk/admin_guide_cmt.aux (checksum...) ok
-add www.cmt.mhs.man.ac.uk/admin_guide_cmt.fdb_latexmk (checksum...) [2013-06-11 14:42:17 BST] Committer: Committing changes to g
-it                                                                                                                             
-admin_guide_cmt.fdb_latexmk
-         264 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 372 bytes  received 42 bytes  828.00 bytes/sec
-total size is 264  speedup is 0.64
-[2013-06-11 14:42:17 BST] Transferrer: Uploaded admin_gui..b_latexmk
-[2013-06-11 14:42:18 BST] Committer: Adding 3 files
-ok
-(Recording state in git...)
-add www.cmt.mhs.man.ac.uk/admin_guide_cmt.fls (checksum...) ok
-add www.cmt.mhs.man.ac.uk/admin_guide_cmt.log (checksum...) ok
-
-# End of transcript or log.
-"""]]
-
-> Ok, I was able to remove the write bit fiddling in direct mode. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_10_fadf06f5ab34e36ab130536ec55afc8e._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_10_fadf06f5ab34e36ab130536ec55afc8e._comment
deleted file mode 100644
index 79cfafa17..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_10_fadf06f5ab34e36ab130536ec55afc8e._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU"
- nickname="Matt"
- subject="comment 10"
- date="2013-06-11T19:27:04Z"
- content="""
-First off, I really like git-annex :-)
-
-Secondly, if I make the change as suggested, what are the consequences?  When you add files to the annex back-end it may still be open and being written to?  But then the next hash-function will reveal the differences of an incomplete upload and fix things....  But it may be too late as it's sent to other repositories...hmmmmm...I guess I want to know if I do this will my data be safe?  I suspect not.
-
-Perhaps the race condition could be mitigated against (not solved) by simply introducing a slight delay?  If only 5 secs it will catch many of these cases.  And longer would prevent git committing files that I save, realize I've slightly got wrong, tweak and save again.
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_11_4a337f7b1140c45e5dd660b40202f696._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_11_4a337f7b1140c45e5dd660b40202f696._comment
deleted file mode 100644
index 99787d4c6..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_11_4a337f7b1140c45e5dd660b40202f696._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 11"
- date="2013-06-12T17:03:07Z"
- content="""
-There's an annex.delayadd git config setting you can use that makes it wait a specified number of seconds before committing. So it would indeed be a workaround to set: `git config annex.delayadd 2`
-
-However, I'm pretty confident I can entirely avoid this problem, safely.
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_1_05e1398e78218ced9c2da6a2510949e8._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_1_05e1398e78218ced9c2da6a2510949e8._comment
deleted file mode 100644
index 8adb71b38..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_1_05e1398e78218ced9c2da6a2510949e8._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU"
- nickname="Matt"
- subject="comment 1"
- date="2013-06-11T13:59:53Z"
- content="""
-Here's a sample latex document
-  
-    \documentclass[twocolumn,a4paper]{article}
-    \title{Test}
-    \begin{document}
-    \maketitle
-    \begin{abstract}
-      Test
-    \end{abstract}
-
-    Some unresolved refs for two passes:
-    \ref{one:a} and \ref{two:b}
-
-    \end{document}
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_2_9226f0adf091154c0d8a08b340b71869._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_2_9226f0adf091154c0d8a08b340b71869._comment
deleted file mode 100644
index c30d751a8..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_2_9226f0adf091154c0d8a08b340b71869._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU"
- nickname="Matt"
- subject="comment 2"
- date="2013-06-11T14:13:22Z"
- content="""
-My temporary work around so that I may continue to use the assistant is to touch an appropriate test.aux before running latexmk.
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_3_44d3e2096b7d45a1062222bee83a346d._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_3_44d3e2096b7d45a1062222bee83a346d._comment
deleted file mode 100644
index d12a09421..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_3_44d3e2096b7d45a1062222bee83a346d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU"
- nickname="Matt"
- subject="comment 3"
- date="2013-06-11T14:23:50Z"
- content="""
-FYI - I replicated this bug on an OSX system using the latest pre-packaged build of git-annex and TexLive.
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_4_f2e1d188b7b2d2daf0d832c59a68583e._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_4_f2e1d188b7b2d2daf0d832c59a68583e._comment
deleted file mode 100644
index 438036e70..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_4_f2e1d188b7b2d2daf0d832c59a68583e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 4"
- date="2013-06-11T14:42:09Z"
- content="""
-Are you using direct mode in your repository?
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_5_998fe58994ecf855310e4b8e6cce9e18._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_5_998fe58994ecf855310e4b8e6cce9e18._comment
deleted file mode 100644
index 8d27f6b5e..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_5_998fe58994ecf855310e4b8e6cce9e18._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU"
- nickname="Matt"
- subject="comment 5"
- date="2013-06-11T14:47:40Z"
- content="""
-hi, yes I am.  Is this bad?
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment
deleted file mode 100644
index 54f533a92..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 6"
- date="2013-06-11T15:09:44Z"
- content="""
-No. Direct mode makes this kind of problem less likely to occur.
-
-Are you only seeing this problem on OSX?
-
-My guess, which  is only a guess at this point is that while direct mode leaves files in-place etc, which should avoid this kind of problem, it does mess with their permissions berifly when ingesting them into the annex. The write bit is breifly turned off,
-while it checks that nothing currently has the file open to be written.
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_7_c713f6316d889c8fc52326f21375c1c4._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_7_c713f6316d889c8fc52326f21375c1c4._comment
deleted file mode 100644
index 754ffe774..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_7_c713f6316d889c8fc52326f21375c1c4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 7"
- date="2013-06-11T15:14:44Z"
- content="""
-Re-reading, I see you're using Fedora and OSX.
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_8_6dd23bab7983b8b1f938dd4f21a16f5a._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_8_6dd23bab7983b8b1f938dd4f21a16f5a._comment
deleted file mode 100644
index 400f7597f..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_8_6dd23bab7983b8b1f938dd4f21a16f5a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 8"
- date="2013-06-11T15:17:56Z"
- content="""
-I can reproduce the bug. Doesn't look likely to involve a race, since it happens every time.
-"""]]
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_9_961c8f968eff0b39a85b607ee3f7630d._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_9_961c8f968eff0b39a85b607ee3f7630d._comment
deleted file mode 100644
index 419abf698..000000000
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_9_961c8f968eff0b39a85b607ee3f7630d._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 9"
- date="2013-06-11T15:30:14Z"
- content="""
-My guess about the write bit seems to be spot on. Which does mean it's a race, just one that happens to be easy to reproduce. It does not happen every time, but 1 time out of 10 or more often.
-
-You can try commenting out the `preventWrite` line in `Command/Add.hs` and rebuilding to see it fix it for you too. I will need to think long and hard about how to make files be ingested safely without turning off the write bit. But, I had been meaning to work on that at some point anyway, so good to have this bug to make it happen.
-
-I instrumented latexmk's call to `$out_handle->open` to see how it's failing:
-
-open failed: Permission denied 256 
-
-Which confirms the problem. It seems that it first creates the file, and then closes it, and then re-opens it to write to it some more. git-annex gets in between these two calls and messes up the permissions behind its back.
-"""]]
diff --git a/doc/bugs/file_modification_times.mdwn b/doc/bugs/file_modification_times.mdwn
deleted file mode 100644
index 2f75dcab7..000000000
--- a/doc/bugs/file_modification_times.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-### Please describe the problem.
-The files created in another remote when syncing is "now" rather than keeping the modification time of the source file. As such, git-annex assistant is removing an important bit of information about the file.
-
-### What steps will reproduce the problem?
-1) create two repositories in your computer using webapp
-2) add files to RepoA, see that they are synced to the RepoB.
-3) check the file modification times from any file manager. you will see that while files in RepoA carry correct modification time, synced file in RepoB carries current time.
-
-### What version of git-annex are you using? On what operating system?
-Ubuntu 13.10 32bit version 4.20130815 from apt-get.
-
-> duplicate of [[todo/add_metadata_to_annexed_files]] --[[Joey]]
-> [[done]]
diff --git a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__.mdwn b/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__.mdwn
deleted file mode 100644
index 9b2e89ca2..000000000
--- a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-### Please describe the problem.
-The log doesn't say what the webapp is running (probably ssh or similar), but it complains that ~/.ssh/config has the wrong permissions. This being cygwin, I'm not sure I can even change them; I'll poke around and see. Currently they're 0644.
-
-### What steps will reproduce the problem?
-Create a remote repository
-
-### What version of git-annex are you using? On what operating system?
-Windows 7, git-annex version 5.20131230-g192d991
-
-### Please provide any additional information below.
-I have no daemon.log, and the console log isn't particularly detailed today; it had just created an ssh key and shown it's fingerprint.
-
-> Ok, I guess this is ssh refusing to use a file that has a group
-> write bit set (when the owner is not the only member of its group),
-> or perhaps that has the world write bit set.
->
-> I have made the assistant unset those modes when creating and modifying
-> ssh config files. Hopefully that is enough for Windows too.. I can't
-> really test it there, but am calling this provisionally [[done]].
-> --[[Joey]]
diff --git a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_1_a04b71f4f81c477d18f14d8dfe8b378f._comment b/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_1_a04b71f4f81c477d18f14d8dfe8b378f._comment
deleted file mode 100644
index a01f4be80..000000000
--- a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_1_a04b71f4f81c477d18f14d8dfe8b378f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA"
- nickname="Daniel"
- subject="comment 1"
- date="2014-01-01T09:50:27Z"
- content="""
-So I can get around this by manually changing the permissions on this directory and it's files (using the windows permissions editor) so that only the user has access to it, and no other groups do (including Administrators). This seems like something the assistant should handle.
-"""]]
diff --git a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_2_0dbc908984b4b5bcc1283db807e058cb._comment b/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_2_0dbc908984b4b5bcc1283db807e058cb._comment
deleted file mode 100644
index 3cae49416..000000000
--- a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_2_0dbc908984b4b5bcc1283db807e058cb._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 2"
- date="2014-01-01T21:03:31Z"
- content="""
-Did you say you're using cygwin? That would suggest that you have a ~/.ssh/config that might have been set up before you started using git-annex.
-
-When I run the git-annex webapp at the DOS prompt, it sets up a .ssh/config with permissions that ssh doesn't dislike.
-"""]]
diff --git a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_3_ff6cd2bb007d41284a09e470e060c32d._comment b/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_3_ff6cd2bb007d41284a09e470e060c32d._comment
deleted file mode 100644
index 6940a80f6..000000000
--- a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__/comment_3_ff6cd2bb007d41284a09e470e060c32d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA"
- nickname="Daniel"
- subject="comment 3"
- date="2014-01-01T23:52:32Z"
- content="""
-No, ~/.ssh/config is fresh. I'm running git annex webapp from the git bash prompt, which is some unholy combination of msys and cygwin.
-"""]]
diff --git a/doc/bugs/fix_for_makefile_to_check_if_OS_is_linux_or_not___40__relates_to_the_new_inotify_flag__41__.mdwn b/doc/bugs/fix_for_makefile_to_check_if_OS_is_linux_or_not___40__relates_to_the_new_inotify_flag__41__.mdwn
deleted file mode 100644
index fee00855e..000000000
--- a/doc/bugs/fix_for_makefile_to_check_if_OS_is_linux_or_not___40__relates_to_the_new_inotify_flag__41__.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-Since the watch branch is now merged into master, it doesn't quite build cleanly on non-linux systems anymore. So here's a small change to the Makefile to work around the problem for now.
-
-<pre>
-From 707cb47744775c324060febe11987db5f10ed9ff Mon Sep 17 00:00:00 2001
-From: Jimmy Tang <jtang@tchpc.tcd.ie>
-Date: Mon, 18 Jun 2012 09:20:35 +0100
-Subject: [PATCH] Teach _Makefile_ to only do _-DWITH_INOTIFY_ when on a Linux
- machine.
-
----
- Makefile |    8 +++++++-
- 1 file changed, 7 insertions(+), 1 deletion(-)
-
-diff --git a/Makefile b/Makefile
-index 6d36e8b..8884b5c 100644
---- a/Makefile
-+++ b/Makefile
-@@ -1,6 +1,12 @@
-+OS:=$(shell uname | sed 's/[-_].*//')
-+
-+ifeq ($(OS),Linux)
-+BASEFLAGS_OPTS+=-DWITH_INOTIFY
-+endif
-+
- PREFIX=/usr
- IGNORE=-ignore-package monads-fd -ignore-package monads-tf
--BASEFLAGS=-Wall $(IGNORE) -outputdir tmp -IUtility -DWITH_S3 -DWITH_INOTIFY
-+BASEFLAGS=-Wall $(IGNORE) -outputdir tmp -IUtility -DWITH_S3 $(BASEFLAGS_OPTS)
- GHCFLAGS=-O2 $(BASEFLAGS)
- 
- ifdef PROFILE
--- 
-1.7.10.4
-</pre>
-
-[[done]], thanks --[[Joey]] 
diff --git a/doc/bugs/free_space_checking.mdwn b/doc/bugs/free_space_checking.mdwn
deleted file mode 100644
index 92e8be40d..000000000
--- a/doc/bugs/free_space_checking.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-Should check that there is enough free space before trying to copy a
-file around.
-
-* Need a way to tell how much free space is available on the disk containing
-  a given repository.
-
-* And, need a way to tell the size of a file before copying it from
-  a remote, to check local disk space.
-
-  As of annex.version 2, this metadata can be available for any type
-  of backend. Newly added files will always have file size metadata,
-  while files that used a SHA backend and were added before the upgrade
-  won't.
-
-  So, need a migration process from eg SHA1 to SHA1+filesize. It will
-  find files that lack size info, and rename their keys to add the size
-  info. Users with old repos can run this on them, to get the missing
-  info recorded.
-
-> [[done]]; no migtation process for old SHA1 keys from v1 repo though.
-> --[[Joey]] 
diff --git a/doc/bugs/free_space_checking/comment_1_a868e805be43c5a7c19c41f1af8e41e6._comment b/doc/bugs/free_space_checking/comment_1_a868e805be43c5a7c19c41f1af8e41e6._comment
deleted file mode 100644
index 954433deb..000000000
--- a/doc/bugs/free_space_checking/comment_1_a868e805be43c5a7c19c41f1af8e41e6._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-03-15T14:11:27Z"
- content="""
-Keep in mind that lots of small files may have significant overhead, so a warning that it's not possible to make sure there's enough space would make sense for certain corner cases. Actually finding out the exact overhead is beyond git-annex' scope and, given transparent compression etc, ability, but a warning, optionally with a \"do you want to continue\" prompt can't hurt.
-
--- RichiH
-"""]]
diff --git a/doc/bugs/free_space_checking/comment_2_8a65f6d3dcf5baa3f7f2dbe1346e2615._comment b/doc/bugs/free_space_checking/comment_2_8a65f6d3dcf5baa3f7f2dbe1346e2615._comment
deleted file mode 100644
index 9a43fe3f2..000000000
--- a/doc/bugs/free_space_checking/comment_2_8a65f6d3dcf5baa3f7f2dbe1346e2615._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-03-16T03:04:50Z"
- content="""
-Right. You probably don't want git-annex to fill up your entire drive anyway, so if it tries to reseve 10 mb or 1% or whatever (probably configurable) for overhead, that should be good enough.
-"""]]
diff --git a/doc/bugs/free_space_checking/comment_3_0fc6ff79a357b1619d13018ccacc7c10._comment b/doc/bugs/free_space_checking/comment_3_0fc6ff79a357b1619d13018ccacc7c10._comment
deleted file mode 100644
index ea4fb6c23..000000000
--- a/doc/bugs/free_space_checking/comment_3_0fc6ff79a357b1619d13018ccacc7c10._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 3"
- date="2011-03-16T15:40:56Z"
- content="""
-Sometimes, I might want to fill up the disk as much as possible. Thus, a warning is preferable to erroring out too early, imo -- Richard
-"""]]
diff --git a/doc/bugs/fsck__47__fix_should_check__47__fix_the_permissions_of_.git__47__annex.mdwn b/doc/bugs/fsck__47__fix_should_check__47__fix_the_permissions_of_.git__47__annex.mdwn
deleted file mode 100644
index c649ff9f7..000000000
--- a/doc/bugs/fsck__47__fix_should_check__47__fix_the_permissions_of_.git__47__annex.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-git annex carefully setup restrictive permissions of .git/annex directories and files.
-
-The fsck command should check that they are still correct.
-The fix command should fix them.
-
-PS: Thanks for this nice tool!
-
-> Good idea, [[done]] (actually, fsck just fixes them too)! --[[Joey]]
diff --git a/doc/bugs/fsck_claims_failed_checksum_when_less_copies_than_required_are_found.mdwn b/doc/bugs/fsck_claims_failed_checksum_when_less_copies_than_required_are_found.mdwn
deleted file mode 100644
index fe6536b6a..000000000
--- a/doc/bugs/fsck_claims_failed_checksum_when_less_copies_than_required_are_found.mdwn
+++ /dev/null
@@ -1,57 +0,0 @@
-    (checksum...) failed
-    fsck foo (fixing location log) 
-      Only 1 of 2 trustworthy copies exist of foo
-      Back it up with git-annex copy.
-
-> You've given me severely partial output, and no test case, but until
-> it says "fsck foo", the output is pertaining to some other file than foo.
-> As far as I can see, there is no bug here. --[[Joey]]
-
->> Sorry, I thought it would be obvious, but that's no excuse for not
->> providing additional explanation. The problem is that fsck tells me a
->> file's fsck has failed without printing extra details. In this case, the
->> checksum is OK while I don't have enough copies to satisfy the fsck. The
->> fact that I don't have enough copies is obviously relevant, but I would
->> still like to know if the checksums are OK. -- Richard
-
->>> I think you're misreading the truncated output you posted. The actual,
->>> full output would make much more sense. --[[Joey]]
-
->>>> No. I have a total of 14908 annex keys, 3333 of which are on a remote. The only message other than 'checksum OK' and the above is 'git-annex: 11577 failed'.
->>>> I checked several files manually, their checksums are OK so `git annex
->>>> fsck` is reporting those files as completely failed when they "only" miss copies. -- Richard
-
->>>>> fsck considers not enough copies to be a failure condition; it prints
->>>>> error messages about it etc. That has nothing to do with checksums.
->>>>> --[[Joey]]
-
->>>>>> I get that. Still, I think it would be _extremely_ useful to know what failures occurred, exactly. Not having enough copies is Not Good, yet not having enough copies and a locally correct file is _lot_ better than having not enough copies and a broken file. I.e. I would prefer:
-
-    (checksum...) OK
-    Not enough copies: Only 1 of 2 trustworthy copies exist of foo
-
->>>>>> or similar and at the end
-
-    git-annex: 0 wrong checksums
-    git-annex: 11577 with too few copies
-
->>>>>> In the end, it comes down to the distinction of different failure classes. -- Richard
-
->>>>>>> For the third, and final time: 
->>>>>>> # You are misreading the truncated output you posted
->>>>>>> The "checksum" line is regarding **different** file than the 
->>>>>>> not enough copies message. fsck does not attempt to checksum a file
->>>>>>> that is not present. [[done]] --[[Joey]]
-
-
->>>>>>>> I realized early on that I pasted the wrong cross-passage, but as there is a ton of the same output, I didn't think it would matter. I wasn't aware that it does not try to checksum when there aren't enough copies. To be fair, you only just mentioned that.
->>>>>>>> Personally, I think that's a bug as it makes ensuring local correctness before copying a file to remotes impossible.
->>>>>>>> Either way, I really didn't know it actually _skipped_ checksumming; that part was missing.
->>>>>>>> For the benefit of anyone else who might read this, this is the correct order:
-
-    fsck foo (fixing location log) 
-      Only 1 of 2 trustworthy copies exist of foo
-      Back it up with git-annex copy.
-    (checksum...) failed
-
->>>>>>>> If you would like to keep things this way, fine. I think it's less than ideal, but I don't want to argue, either. -- Richard
diff --git a/doc/bugs/fsck_output.mdwn b/doc/bugs/fsck_output.mdwn
deleted file mode 100644
index 1b00dd7b3..000000000
--- a/doc/bugs/fsck_output.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-When you check several files and the fsck fails, you get confusing output:
-
-<pre>
-O fsck test1 (checksum...) 
-E  Only 1 of 2 trustworthy copies of test1 exist.
-E  Back it up with git-annex copy.
-O
-O failed
-O fsck test2 (checksum...) 
-E  Only 1 of 2 trustworthy copies of test2 exist.
-E  Back it up with git-annex copy.
-O 
-O failed
-</pre>
-
-The newline is in the wrong place and confuses the user. It should be printed _after_ "failed".
-
-> This is a consequence of part of the output being printed to stderr, and
-> part to stdout. I've marked the lines above with E and O.
-> 
-> Normally a "failed" is preceeded by a message output to stdout desribing
-> the problem; such a message will not be "\n" terminated, so a newline
-> is always displayed before "failed". In this case, since the message
-> is sent to stderr, it is newline terminated.
-> 
-> Fixing this properly would involve storing state, or rethinking 
-> when git-annex displays newlines (and I rather like its behavior
-> otherwise).
-> 
-> A related problem occurs if an error message is unexpetedly printed.
-> Dummying up an example:
-> 
-> O get test1 (from foo...) E git-annex: failed to run ssh
-> failed
-> 
-> --[[Joey]] 
-
->> Well, I fixed this in all cases except a thrown non-IO error (last
->> example aboce), which output is printed by haskell's runtime. I'd
->> have to add a second error handler to handle those, and it's not
->> clear what it would do. Often an error will occur before anything
->> else is printed, and then the current behavior is right; if something
->> has been printed it would be nice to have a newline before the error,
->> but by the time the error is caught we'd be out of the annex monad
->> and not really have any way to know if something has been printed.
->> I think my fix is good enough [[done]] --[[Joey]] 
diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn b/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn
deleted file mode 100644
index dba775d37..000000000
--- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-git annex fsck marks files as bad when the checksumming fails. But this could also be due to a read error when the actual data stored is correct. So, fsck should check twice when a checksum fails.
-
-> [[done]]; apparently problem was caused by bad RAM. --[[Joey]]
diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_1_03af24b70adbcd9f4b94d009f6b71d0a._comment b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_1_03af24b70adbcd9f4b94d009f6b71d0a._comment
deleted file mode 100644
index 543777e26..000000000
--- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_1_03af24b70adbcd9f4b94d009f6b71d0a._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 1"
- date="2013-01-14T16:26:59Z"
- content="""
-Why stop at checking twice? The second check could also fail with a read error, and perhaps the third one would succeed. :P
-
-Seriously, I doubt that this is likely to be a benefit with a modern drive. If the file has a read error once, then error correction has already failed, and it's likely to fail again. Even if it managed to succeed the second time, you have a file that is being read wrong some of the time, which is not a good thing for fsck to leave unnoticed.
-
-Fsck moves bad files to `.git/annex/bad`, so the data in them can be recovered if it comes to that. Hopefully
-though, there's a copy of the file in another repository, so git-annex can just get it from there instead.
-"""]]
diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_2_41214a7d18c66b694645248d6ebeadbf._comment b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_2_41214a7d18c66b694645248d6ebeadbf._comment
deleted file mode 100644
index ea9518cb6..000000000
--- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_2_41214a7d18c66b694645248d6ebeadbf._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkHDm_DOFRcHYebCnnYKKyIwiPD4iOiiIU"
- nickname="Jörn"
- subject="comment 2"
- date="2013-01-14T17:37:45Z"
- content="""
-Maybe I was too quick in blaming the hard drive. It might be my problem is somewhere else. Let me do what I should have done in the first place and give you a detailed problem description:
-
-I have got three hard drives, two internal, one external connected via USB. I have got a couple of repositories with small files (mp3, JPEGs and so on). Those are fine, fsck never complains about them. 
-But in one repository with video files (i.e. much bigger files than in the other repos), git-annex fsck will always find some broken files. I run git-annex get to retrieve the broken files from other sources. Then I run
-fsck again - and it complains about some other files. This happens on all drives.
-
-This could mean:
-
-- all my drives are broken. However, SMART data are unsuspicious, and one of the drives is just a couple of days old.
-- git-annex fsck is broken
-- read errors like I mentioned in my first post
-- some process actually _altering_ the files (should not happen when the files are locked, right?)
-- something completely different? Some possibly dangerous source of radiation? :)
-
-Any ideas on this? Maybe I should hash the data in .git/annex/bad and check which value I get - can I tell git-annex to do so?
-
-Thanks,
-Jörn
-"""]]
diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_3_e7ddd77ea35994f2051f840e9b4c7e0c._comment b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_3_e7ddd77ea35994f2051f840e9b4c7e0c._comment
deleted file mode 100644
index f7d6221de..000000000
--- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_3_e7ddd77ea35994f2051f840e9b4c7e0c._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 3"
- date="2013-01-14T19:06:37Z"
- content="""
-I would doubt you'd have three broken drives, or read errors from 3 drives. 
-
-You can use `sha256sum` to checksum the files in `bad` yourself, and compare the results with their names.
-If it matches, that would point to some kind of bug in fsck.
-"""]]
diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_4_36a70d5a378983a76fcdbb7fba044044._comment b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_4_36a70d5a378983a76fcdbb7fba044044._comment
deleted file mode 100644
index 64df24bdb..000000000
--- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_4_36a70d5a378983a76fcdbb7fba044044._comment
+++ /dev/null
@@ -1,32 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkHDm_DOFRcHYebCnnYKKyIwiPD4iOiiIU"
- nickname="Jörn"
- subject="comment 4"
- date="2013-01-14T20:04:48Z"
- content="""
-On the internal disk some files match, others don't:
-
-     42c95aee60c41157ee6d092eeea7fab73dff7b45a6e16ba77a02e2a6fec01c15  SHA256-s1099424853--42c95aee60c41157ee6d092eeea7fab73dff7b45a6e16ba77a02e2a6fec01c15
-     44c4d3b0f29d86597ae09cf52563e0a2adec7074f5359901fde8dbf88f9bc8ad  SHA256-s1173029201--bb981fddd750db1255cc1fda1f9612250f766e4da946eac4c294d8071196615c
-     a9d804fe633ae69d0c926dea41059c211f78cf891abfa275c579bcc8e12fa700  SHA256-s1363601770--a9d804fe633ae69d0c926dea41059c211f78cf891abfa275c579bcc8e12fa700
-     bac5f30b696b643c76a456e3018214ce64be7d289afaac96a7fdba03eccf73fd  SHA256-s1422005768--5754211ac3e7e6314de9aa34f7b1cfd3c9aed432f52b26189c4587dc505a30e8
-     be953e962d9c6a2699f361e468023aae34b1f7c66ad93852d8f88846b60ecbcc  SHA256-s1424026123--258dbe5704a46ecd3190d278efdd2adfeee9ad81843bfaa0ed7adbc10ccd5362
-     b9f06383c76a0161312aaf6298eb764dbfb8e1e51555ec06d8c85c9f5df9fe20  SHA256-s1448369674--a703dfd46c147396def6e1db22c7917dbdf010658aa32df1cf598e37a04d5897
-     e2d748ee5c5098316bbe20c3f771f7f552b07c394a1e9932cba2a90883b6fb5c  SHA256-s1480008949--505c7d2685290069140b2f03fa72a5b5e3f59c14961c60c5fd6532be05ad1c84
-     ac0d49461ca67ca2de0588491c39089634ae194870594dd869fbc84d42831baa  SHA256-s1489602933--f3ff3fc71b4f5493db476f29f373a4b3bf8808e9a7487589fee632ea58a415af
-     b9b1d133772c88a1c5f856e2d4bcb696a453c795337b9f97cfa4c00876f49b88  SHA256-s1512599506--78dc0bdf0b4e382283a770a36c7f699c83611a0436059e6bb44c8e94d26cca5f
-     497af65e2d400e5651d9b850bc5efbaa006cec08f3f0dfce5d09b8e3f994a80b  SHA256-s1524648153--85548bcb693491eeae1d1315a6037d5a9a15d2a10066f04f6e7ce75b6eb1ca47
-     cb793e7ac6df827e96f7dfa34a10f13a899140372c4db58b08650314596d30fa  SHA256-s1541427964--16b8f7d5e5e12af88e947b26ca4d38d6b6692de92a77d9ffef0c8c1d560db727
-     27ea446f928239ade9c3c1f38119fa38da50a74036f9987d57cce3b52ae632e9  SHA256-s1561020163--cfce86c309d16af772e68527ba365ceac5db447d5bbfc335e063a2a4e9d513d6
-     940d2c7ff3bde5662d71a1a463f6949c6dd6cf244d43ab7d48014a10d0fa5d6a  SHA256-s1562397113--a057d447b5b32d2f1a440247d9dc3c3ca697798d73dd740670a3033dd0fcbb68
-     [...]
-
-
-On the usb drive, hashes match:
-
-     [joern@heracles bad]$ sha256sum *
-     e306e07a09af9be9a974632c777935ddd0f5333b603b5f205dba03753619d682  SHA256-s1564783770--e306e07a09af9be9a974632c777935ddd0f5333b603b5f205dba03753619d682
-     8fe78a325a08099e56df44ff46d482607723dfc9402bcd8f4850907327603f05  SHA256-s207925248--8fe78a325a08099e56df44ff46d482607723dfc9402bcd8f4850907327603f05
-     8823bd4ccf5f6ff2fe0976de6a856490ef3de0ab1c1e128bde770b732e86d94c  SHA256-s923668098--8823bd4ccf5f6ff2fe0976de6a856490ef3de0ab1c1e128bde770b732e86d94c
-
-"""]]
diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment
deleted file mode 100644
index fb3838511..000000000
--- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_5_899c4afbc988d81984c5c3397285bb01._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 5"
- date="2013-01-14T21:57:30Z"
- content="""
-If you have both the corrupted file and the good file you can use the `cmp` command to show exactly how they differ:
-
-    cmp -l file1 file2
-
-If files are regularly marked as corrupted you might have bad ram.
-"""]]
diff --git a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_6_dbff51d00c5645eb1832aa4644889c5e._comment b/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_6_dbff51d00c5645eb1832aa4644889c5e._comment
deleted file mode 100644
index 724be0df0..000000000
--- a/doc/bugs/fsck_should_double-check_when_a_content-check_fails/comment_6_dbff51d00c5645eb1832aa4644889c5e._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkHDm_DOFRcHYebCnnYKKyIwiPD4iOiiIU"
- nickname="Jörn"
- subject="comment 6"
- date="2013-01-15T09:38:34Z"
- content="""
-That was a good advice. I have just run memtest, and it seems my memory is broken. So this was probably the cause for all this trouble.
-
-Thanks!
-"""]]
diff --git a/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t.mdwn b/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t.mdwn
deleted file mode 100644
index e9051f9f3..000000000
--- a/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t.mdwn
+++ /dev/null
@@ -1,35 +0,0 @@
-What steps will reproduce the problem?
-What is the expected output? What do you see instead?
-
-I can reproduce it locally, but don't know what's causing it. The file content is the same, I checked with md5sum and sha512sum. But fsck still thinks the content is different. Are there other factors I could check which fsck looks at? I'm using SHA512E backend.
-
-What version of git-annex are you using? On what operating system?
-
-git-annex version: 3.20120807 Ubuntu 12.04 updated on Aug 20th annex was installed via cabal on Aug 20th, all other packages are from ubuntu.
-
-> What is the error message from fsck? --[[Joey]] 
-
-This is the output:
-
-> reinject ....Moon.avi (checksum...) 
-> Bad file content; moved to /mnt/.../.git/annex/bad/SHA512E-s94402560--ead9db1f34739014a216239d9624bce74d92fe723de06505f9b94cb4c063142ba42b04546f11d3d33869b736e40ded2ff779cb32b26aa10482f09407df0f3c8d.Moon.avi
-failed
-> (Recording state in git...)
-> git-annex: reinject: 1 failed
-
-The original file also has sha512 ead9db1f34739014a216239d9624bce74d92fe723de06505f9b94cb4c063142ba42b04546f11d3d33869b736e40ded2ff779cb32b26aa10482f09407df0f3c8d
-
->> And what sha512 does the file in .git/annex/bad have **now**? (fsck
->> preserves the original filename; this says nothing about what the
->> current checksum is, if the file has been corrupted). --[[Joey]]
-
-The same, as it's the file I was trying to inject:
-
-ead9db1f34739014a216239d9624bce74d92fe723de06505f9b94cb4c063142ba42b04546f11d3d33869b736e40ded2ff779cb32b26aa10482f09407df0f3c8d  .git/annex/bad/SHA512E-s94402560--ead9db1f34739014a216239d9624bce74d92fe723de06505f9b94cb4c063142ba42b04546f11d3d33869b736e40ded2ff779cb32b26aa10482f09407df0f3c8d.Moon.avi
-
-That's what puzzles me, it is the same file, but for some weird reason git annex thinks it's not.
-
-> Ok, reproduced and fixed the bug. The "E" backends recently got support
-> for 2 levels of filename extensions, but were not made to drop them both
-> when fscking. [[done]] (I'll release a fixed version probably tomorrow;
-> fix is in git now.) --[[Joey]] 
diff --git a/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t/comment_1_cafb58eca97a0a66110ac39b169d8de3._comment b/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t/comment_1_cafb58eca97a0a66110ac39b169d8de3._comment
deleted file mode 100644
index 9f63dbfa9..000000000
--- a/doc/bugs/fsck_thinks_file_content_is_bad_when_it_isn__39__t/comment_1_cafb58eca97a0a66110ac39b169d8de3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawla3gLc6_rHuggFfy7o7eGMPvPztFZTrUQ"
- nickname="Florian"
- subject="comment 1"
- date="2012-08-27T08:59:23Z"
- content="""
-Works!
-"""]]
diff --git a/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn b/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn
deleted file mode 100644
index c256778c8..000000000
--- a/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-git-annex 4.20130911 on Debian Wheezy.
-
-Using `git annex initremote type=gcrypt` as described [here](http://git-annex.branchable.com/tips/fully_encrypted_git_repositories_with_gcrypt/) creates the repository and pushes the `git-annex` branch to it.  It doesn't push `master` (or more generally: the currently checked out branch), as I have verified using `git remote show`.
-
-Manually pushing the branch makes `git annex sync` sync both branches with the gcrypt remote.
-
-I think that it should push the current branch upon creation of the special remote, since for at least me, the whole reason for wanting `git-remote-gcrypt` is that metadata as well as data can be stored encrypted on an SSH server.
-
-Thanks for considering this.
-
-> The git-annex branch is pushed by initremote because I have to push
-> *something* to determine the gcrypt-id. However, this is an implementation
-> detail, and not a feature of initremote. (It's more like a bug of
-> git-remote-gcrypt.)
-> 
-> `git annex sync` will always push your currently checked out branch,
-> as well as the git-annex branch, no matter what `initremote` has done.
-> 
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/get_failed__44___but_remote_has_the_file.mdwn b/doc/bugs/get_failed__44___but_remote_has_the_file.mdwn
deleted file mode 100644
index 254e3d820..000000000
--- a/doc/bugs/get_failed__44___but_remote_has_the_file.mdwn
+++ /dev/null
@@ -1,40 +0,0 @@
-Not sure what caused this, but I have a file that exists on two remotes, but I can only get it from one of them.  If I try to get it from the other, it fails immediately (without even connecting):
-
-    pilot:~/vid/tv/Show$ git annex whereis Show\ -\ S03E08.mp4
-    whereis Show - S03E08.mp4 (2 copies) 
-            09c0b436-f8de-11e0-842f-b7644539d57f -- psychosis
-            82814942-f8e0-11e0-b053-e70a61e98e19 -- bucket
-    ok
-
-    pilot:~/vid/tv/Show$ git annex fsck Show\ -\ S03E08.mp4
-    fsck Show - S03E08.mp4 ok
-
-    pilot:~/vid/tv/Show$ git annex get --from bucket Show\ -\ S03E08.mp4
-    get Show - S03E08.mp4 failed
-    git-annex: get: 1 failed
-
-    pilot:~/vid/tv/Show$ git annex get --debug --from bucket Show\ -\ S03E08.mp4
-    [2013-01-17 19:05:13 EST] read: git ["--git-dir=/home/jim/vid/.git","--work-tree=/home/jim/vid","show-ref","git-annex"]
-    [2013-01-17 19:05:13 EST] read: git ["--git-dir=/home/jim/vid/.git","--work-tree=/home/jim/vid","show-ref","--hash","refs/heads/git-annex"]
-    [2013-01-17 19:05:13 EST] read: git ["--git-dir=/home/jim/vid/.git","--work-tree=/home/jim/vid","log","refs/heads/git-annex..e41c3b1ee9127129f2c9fc3fa5d4771afcb5ffd7","--oneline","-n1"]
-    [2013-01-17 19:05:13 EST] read: git ["--git-dir=/home/jim/vid/.git","--work-tree=/home/jim/vid","log","refs/heads/git-annex..a7ae08bccede282f46c2073f6c3e52685a593482","--oneline","-n1"]
-    [2013-01-17 19:05:13 EST] read: git ["--git-dir=/home/jim/vid/.git","--work-tree=/home/jim/vid","log","refs/heads/git-annex..ae0f84e906423f4da465e3d3df9d46545684d3f5","--oneline","-n1"]
-    [2013-01-17 19:05:13 EST] chat: git ["--git-dir=/home/jim/vid/.git","--work-tree=/home/jim/vid","cat-file","--batch"]
-    [2013-01-17 19:05:13 EST] read: git ["--git-dir=/home/jim/vid/.git","--work-tree=/home/jim/vid","ls-files","--cached","-z","--","Show - S03E08.mp4"]
-    get Show - S03E08.mp4 failed
-    git-annex: get: 1 failed
-
-Same `git annex version` on both `pilot` and `bucket`, and I ran `git annex sync` on both.
-
-    git-annex version: 3.20130114
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3
-    upgrade supported from repository versions: 0 1 2
-
-How should I debug this?
-
-> [[done]], in c6fbed48 I had made some changes to allow transfers
-> to work from readonly filesystems, but a too broad error trapping
-> hid the "transfer already in progress" error it is supposed to display
-> in this case. --[[Joey]]
diff --git a/doc/bugs/get_failed__44___but_remote_has_the_file/comment_1_55c8b73ce05dfca11a393bb296b99b9a._comment b/doc/bugs/get_failed__44___but_remote_has_the_file/comment_1_55c8b73ce05dfca11a393bb296b99b9a._comment
deleted file mode 100644
index 24825b2eb..000000000
--- a/doc/bugs/get_failed__44___but_remote_has_the_file/comment_1_55c8b73ce05dfca11a393bb296b99b9a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.3.194"
- subject="comment 1"
- date="2013-01-18T20:25:01Z"
- content="""
-One completely legitimate way for this to happen would be if bucket is a removable drive or other filesystem, and it is not mounted (or its directory doesn't contain a git repo for whatever reason). It would look identical to what you showed happening.
-
-Otherwise, what kind of remote is bucket? Special remote or git remote?
-"""]]
diff --git a/doc/bugs/get_failed__44___but_remote_has_the_file/comment_2_474c67a421dca4c245e7bfe495d3f6d3._comment b/doc/bugs/get_failed__44___but_remote_has_the_file/comment_2_474c67a421dca4c245e7bfe495d3f6d3._comment
deleted file mode 100644
index a7e3d6b17..000000000
--- a/doc/bugs/get_failed__44___but_remote_has_the_file/comment_2_474c67a421dca4c245e7bfe495d3f6d3._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck"
- nickname="Jim"
- subject="comment 2"
- date="2013-01-19T21:40:14Z"
- content="""
-They're all git remotes:
-
-    pilot:~/vid/tv$ git remote -v show
-    bucket	ssh://bucket/home/jim/private/vid (fetch)
-    bucket	ssh://bucket/home/jim/private/vid (push)
-    origin	https://git/jim/annex.git (fetch)
-    origin	https://git/jim/annex.git (push)
-    psychosis	ssh://psychosis/vid/annex (fetch)
-    psychosis	ssh://psychosis/vid/annex (push)
-
-And it never even attempts a ssh connection to bucket.
-"""]]
diff --git a/doc/bugs/get_failed__44___but_remote_has_the_file/comment_3_845e8a23d63fb0b071c63ee736697d26._comment b/doc/bugs/get_failed__44___but_remote_has_the_file/comment_3_845e8a23d63fb0b071c63ee736697d26._comment
deleted file mode 100644
index 0ddbe14bf..000000000
--- a/doc/bugs/get_failed__44___but_remote_has_the_file/comment_3_845e8a23d63fb0b071c63ee736697d26._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck"
- nickname="Jim"
- subject="comment 3"
- date="2013-01-19T22:21:04Z"
- content="""
-Wait, that's weird, it works today.  I'm thinking that maybe there was another copy of `git-annex` backgrounded and holding a lock, since that reproduces this behavior:
-
-    pilot:~/vid/tv/Show$ git annex get --from bucket Show\ -\ S03E08.mp4
-    get Show - S03E08.mp4 (from bucket...) 
-    Enter passphrase for key '/home/jim/.ssh/id_rsa': 
-    SHA256E-s358393024--efda17d23d68b85d47ad342f8e41f79ac04d4a65d7ef654b4838b995b86bdefe.mp4
-        96043008  26%   10.27MB/s    0:00:24  ^Z
-    [1]+  Stopped                 git annex get --from bucket Show\ -\ S03E08.mp4
-    pilot:~/vid/tv/Show$ git annex get --from bucket Show\ -\ S03E08.mp4
-    get Show - S03E08.mp4 failed
-    git-annex: get: 1 failed
-
-So, I guess this is probably \"not a bug\", but having a more specific error would be really helpful.
-"""]]
diff --git a/doc/bugs/get_failed__44___but_remote_has_the_file/comment_4_7dec21cb67e7f4dbdb49da97f2443e8f._comment b/doc/bugs/get_failed__44___but_remote_has_the_file/comment_4_7dec21cb67e7f4dbdb49da97f2443e8f._comment
deleted file mode 100644
index fd9a1f6d3..000000000
--- a/doc/bugs/get_failed__44___but_remote_has_the_file/comment_4_7dec21cb67e7f4dbdb49da97f2443e8f._comment
+++ /dev/null
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawla7u6eLKNYZ09Z7xwBffqLaXquMQC07fU"
- nickname="Matthias"
- subject="ssh stall triggers this"
- date="2013-03-14T22:55:11Z"
- content="""
-I experienced a very similar bug today.
-
-While retrieving a rather large file from a remote git repository my internet connection broke down such that the ssh connection stalled. I noticed this and killed the transfer on my side. After the connection was up again I restarted the transfer and got the following output:
-
-git annex get --debug backup.iso
-[2013-03-14 23:30:26 CET] read: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"backup.iso\"]
-get backup.iso [2013-03-14 23:30:26 CET] read: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"show-ref\",\"git-annex\"]
-[2013-03-14 23:30:26 CET] read: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-[2013-03-14 23:30:26 CET] read: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"log\",\"refs/heads/git-annex..7a133679de4f30a0c9cc552b6c9c85e8120e88e6\",\"--oneline\",\"-n1\"]
-[2013-03-14 23:30:26 CET] read: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"log\",\"refs/heads/git-annex..715af259c233713a420f670a134f4550ba67832a\",\"--oneline\",\"-n1\"]
-[2013-03-14 23:30:26 CET] read: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"log\",\"refs/heads/git-annex..7a905bff06ee702886829ca4482330071549994d\",\"--oneline\",\"-n1\"]
-[2013-03-14 23:30:26 CET] read: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"log\",\"refs/heads/git-annex..51ca0f25220b216b12a236c05d2e2a5c121a99b7\",\"--oneline\",\"-n1\"]
-[2013-03-14 23:30:26 CET] read: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"log\",\"refs/heads/git-annex..02f889b99107ddc699f204f4628539112dd90b81\",\"--oneline\",\"-n1\"]
-[2013-03-14 23:30:26 CET] read: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"log\",\"refs/heads/git-annex..01da68a6d86554532701fafb46242dd706e25499\",\"--oneline\",\"-n1\"]
-[2013-03-14 23:30:26 CET] chat: git [\"--git-dir=/home/user/annex/.git\",\"--work-tree=/home/user/annex\",\"cat-file\",\"--batch\"]
-(from origin...) 
-[2013-03-14 23:30:26 CET] read: rsync [\"--progress\",\"--inplace\",\"-e\",\"'ssh' '-S' '/home/user/annex/.git/annex/ssh/server.com' '-o' 'ControlMaster=auto' '-o' 'ControlPersist=yes' 'server.com' 'git-annex-shell ''sendkey'' ''/~/annex'' ''SHA256E-s4628086525--9d8a04ebcfabbda5baa29dbd834cc7e4c3ac5d7b74fec7a23023025952e78686.iso'' --uuid a3b225c4-d832-11e0-b8a3-cbd1782bb1f4 ''--'' ''remoteuuid=e4e649ca-16f9-11e1-ac1d-5f8104ffa876'' ''direct='' ''associatedfile=backup.iso'' ''--'''\",\"--\",\"dummy:\",\"/home/user/annex/.git/annex/tmp/SHA256E-s4628086525--9d8a04ebcfabbda5baa29dbd834cc7e4c3ac5d7b74fec7a23023025952e78686.iso\"]
-rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
-rsync error: error in rsync protocol data stream (code 12) at io.c(605) [Receiver=3.0.9]
-
-  Unable to access these remotes: origin
-
-However, I could retrieve any other file from origin. The problem was that git-annex-shell was still running on the remote side and therefore preventing me from fetching the file and only this file. Once I logged into the remote server, killed the still running git-annex-shell, \"git annex get\" behaved as it should and fetched the file.
-
-However, there is definitely room for an improved error message which at least gives a hint what the problem could be. Of course, the best solution would be if the file was simply transfered.
-
-
- 
-"""]]
diff --git a/doc/bugs/get_fails_for_file:__47____47___web_remotes_if_the_file_is_empty.mdwn b/doc/bugs/get_fails_for_file:__47____47___web_remotes_if_the_file_is_empty.mdwn
deleted file mode 100644
index bb943fa86..000000000
--- a/doc/bugs/get_fails_for_file:__47____47___web_remotes_if_the_file_is_empty.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-###What steps will reproduce the problem?
-    $ touch /home/arand/empty
-    $ git annex addurl 'file:///home/arand/empty'                                                                             
-    addurl _home_arand_empty (downloading file:///home/arand/empty ...) 
-    
-    git-annex: /home/arand/tmp/c/.git/annex/tmp/URL--file&c%%%home%arand%empty: getFileStatus: does not exist (No such file or directory)
-    failed
-    git-annex: addurl: 1 failed
-
-###What is the expected output? What do you see instead?
-If it is possible to distinguish between empty files and files that just fail to open, it would be nice if Annex were able to handle it, or at least give a more obvious error message.
-
-###What version of git-annex are you using? On what operating system?
-
-Debian sid/experimental
-
-    git-annex version: 4.20130227
-    local repository version: 4
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-> Seems that curl doesn't write the file it was asked to 
-> output to in this case. Crazy. Does not affect empty 
-> http urls. Switched to using just cp for file://
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/get_from_bup-remote_with_pubkey_failing.mdwn b/doc/bugs/get_from_bup-remote_with_pubkey_failing.mdwn
deleted file mode 100644
index 5ec1aa9aa..000000000
--- a/doc/bugs/get_from_bup-remote_with_pubkey_failing.mdwn
+++ /dev/null
@@ -1,93 +0,0 @@
-### Please describe the problem.
-
-I'm unable to 'git annex get' a file from a bup-remote with encryption set to 'pubkey'.
-
-### What steps will reproduce the problem?
-     
-I added a bup-remote using [these instructions](http://git-annex.branchable.com/walkthrough/using_bup/):
-
-        bash-3.2$ git annex initremote mybup type=bup encryption=pubkey keyid=0xABE8244505D63E81 buprepo=gumdrop:/home/gert/.bup
-
-        # now adding files and moving them:
-        bash-3.2$ mkdir orgmode && touch orgmode/some.org
-        bash-3.2$ git annex add orgmode/some.org
-        add orgmode/some.org (checksum...) ok
-        (Recording state in git...)
-        bash-3.2$ git commit
-        [master bce8c83] Some.org
-         1 file changed, 1 insertion(+)
-         create mode 120000 orgmode/some.org
-        bash-3.2$ git annex move orgmode/ --to=mybup
-        move orgmode/another.org (gpg)
-        U moet een geheime zin opgeven om de geheime sleutel te gebruiken
-        van: “email”
-        4096-bit RSA key, ID 0xFF8DE378DE223820, created 2013-11-10
-                 (sub-sleutel bij hoofd sleutel ID 0xE9B90528FDA4E1E6)
-
-        (checking mybup...) ok
-        (Recording state in git...)
-        bash-3.2$ less orgmode/another.org
-        orgmode/another.org: No such file or directory
-        bash-3.2$ git annex get orgmode/another.org --debug
-        [2013-11-13 16:18:07 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","ls-files","--cached","-z","--","orgmode/another.org"]
-        get orgmode/another.org [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","show-ref","git-annex"]
-        [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","show-ref","--hash","refs/heads/git-annex"]
-        [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..f25f9bb2b78a8b9c4b64087f1378c68fb5c0a2f1","--oneline","-n1"]
-        [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..1b0a3dd72be437d800e58d659837d6e528cbbc39","--oneline","-n1"]
-        [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..f62419efea58245d232a52ceaf0eaefe3b0fdced","--oneline","-n1"]
-        [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..eb6f0cd983d9a3637e984aa815537fe20a5c2a69","--oneline","-n1"]
-        [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..5362118e643462a0875bfe31d493ffe64413f2d8","--oneline","-n1"]
-        [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..e5afaf82ce25f60a108c0ae873b6fd57c5d28ca7","--oneline","-n1"]
-        [2013-11-13 16:18:08 CET] chat: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","cat-file","--batch"]
-        [2013-11-13 16:18:08 CET] read: git ["config","--null","--list"]
-        (from mybup...) (gpg) [2013-11-13 16:18:08 CET] chat: gpg ["--quiet","--trust-model","always","--decrypt"]
-
-        U moet een geheime zin opgeven om de geheime sleutel te gebruiken
-        van: “<email>”
-        4096-bit RSA key, ID 0xFF8DE378DE223820, created 2013-11-10
-                 (sub-sleutel bij hoofd sleutel ID 0xE9B90528FDA4E1E6)
-
-        [2013-11-13 16:18:15 CET] read: bup ["join","-r","gumdrop:/home/gert/.bup","GPGHMACSHA1--67aec1b62d05d000442cf8e7d9df8d327eaf26d5"]
-        [2013-11-13 16:18:15 CET] chat: gpg ["--quiet","--trust-model","always","--batch","--decrypt"]
-        gpg: kan geheime zin niet opvragen in batch modus
-        gpg: decoderen mislukt: secret key not available
-
-          Unable to access these remotes: mybup
-
-          Try making some of these repositories available:
-          080e97d2-4f82-4292-acb7-a48d82009258 -- mybup (mybupmy bup repository at gumdrop)
-
-          (Note that these git remotes have annex-ignore set: origin)
-        failed
-        git-annex: get: 1 failed
-
-### What version of git-annex are you using? On what operating system?
-
-Running git-annex version 4.20131105-g136b030 on OSX 10.8.5.
-
-### Please provide any additional information below.
-
-My ideas:
-
-"Unable to access these remotes: mybup" is weird, I just moved files there.
-
-"secret key not available" makes me think it's looking for the primary secret key (which is indeed offline).
-When I encrypt a file with the same key I used to create the remote it just works:
-
-    $ gpg --armor --recipient 0xABE8244505D63E81 --encrypt file.txt
-    $ gpg --decrypt file.txt.asc
-
-When prompting for my passphrase it states "4096-bit RSA key, ID 0xFF8DE378DE223820, created 2013-11-10".
-That is a different subkey than what I entered when I setting up the remote.
-
-My keys/subkeys:
-
-    pub  4096R/0xE9B90528FDA4E1E6  aangemaakt: 2013-11-10  vervaldatum: 2014-11-10  gebruik: SC
-                               vertrouwen: ultimate      geldigheid: ultimate
-    sub  4096R/0x98816CFB398B4666  aangemaakt: 2013-11-10  vervaldatum: 2014-11-10  gebruik: E
-    sub  4096R/0x91951718D5F11CDD  aangemaakt: 2013-11-10  vervaldatum: 2014-11-10  gebruik: S
-    sub  4096R/0xABE8244505D63E81  aangemaakt: 2013-11-10  vervaldatum: 2014-11-10  gebruik: E
-    sub  4096R/0xB44520A46B27144D  aangemaakt: 2013-11-10  vervaldatum: 2014-11-10  gebruik: S
-    sub  4096R/0xFF8DE378DE223820  aangemaakt: 2013-11-10  vervaldatum: 2014-11-10  gebruik: E
-
-> This was already fixed in version 4.20131106. [[done]] --[[Joey]] 
diff --git a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799.mdwn b/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799.mdwn
deleted file mode 100644
index f9a61a859..000000000
--- a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799.mdwn
+++ /dev/null
@@ -1,75 +0,0 @@
-I ran git-annex (git version) on three machines with ghc-7.0.2 for about a month, but recently (no more than a week ago) I've started getting this error for every file on "git annex get":
-
-    git-annex-shell: internal error: evacuate(static): strange closure type 30799
-        (GHC version 7.0.2 for i386_unknown_linux)
-        Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
-
-There were no changes to ghc or it's modules, so I assume something has changed in git-annex itself.
-
-strace shows "git annnex get" (on "host1") performing following exec's:
-
-    [pid  9481] execve("/usr/bin/rsync", ["rsync", "-p", "--progress", "--inplace", "-e", "'ssh' 'user@host2' 'git-annex-shell ''sendkey'' ''/remote/path'' ''SHA1-s6654080--abd8edec20648ade69351d68ae1c64c8074a6f0b'' ''--'''", ":", "/local/path/.git/annex/tmp/SHA1-s6654080--abd8edec20648ade69351d68ae1c64c8074a6f0b"], [/* 41 vars */]) = 0
-    [pid  9482] execve("/usr/bin/ssh", ["ssh", "user@host2", "git-annex-shell 'sendkey' '/remote/path' 'SHA1-s6654080--abd8edec20648ade69351d68ae1c64c8074a6f0b' '--'", "", "rsync", "--server", "--sender", "-vpe.Lsf", "--inplace", ".", ""], [/* 41 vars */] <unfinished ...>
-
-I've tried running the second command directly from the shell and got the same error message from a remote GHC.
-Adding strace before git-annex-shell to remote command yielded something like this in the end:
-
-    stat64("/local/path.git", 0xb727d610) = -1 ENOENT (No such file or directory)
-    stat64("/local/path.git", 0xb727d6b0) = -1 ENOENT (No such file or directory)
-    waitpid(7525, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0) = 7525
-    chdir("/home/user")                  = 0
-    rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0
-    write(2, "git-annex-shell: internal error: ", 33git-annex-shell: internal error: ) = 33
-    ...
-
-Note that "/local/path" here is not what's specified in rsync arguments at all, and git repo with files-to-be-fetched on "host2" is in "/remote/path", but "/local/path" is present in git remotes there since I mount it via nfs from "host1" (yes, to the same path as it's there):
-
-    [remote "nfs"]
-      url = /local/path
-      fetch = +refs/heads/*:refs/remotes/nfs/*
-      push = refs/heads/*:refs/remotes/host2/*
-      annex-uuid = 0a4e14ba-5236-11e0-9004-7f24452c0f05
-
-If I comment that remote out from "/remote/path/.git/config", "git annex get" works fine.
-The only git-command git-annex-shell seem to exec there (on "host2") is "git config --list", so it's shouldn't be git trying to do something with it's remotes - it's git-annex itself, right?
-
-Anyways, looks like a simple path-joining error, if "/local/path.git" should be "/local/path/.git" there.
-
-I'm actually quite confused about what it's trying to do with that path.
-Connect from "host1" to "host2" just to connect back to "host1"?
-What for, when it should just fetch files from "host2"?
-
-> git-annex (and git-annex shell) always start up by learning what git
-> remotes are locally configured, and this includes checking them to
-> try to look up their annex.uuid setting.
-> 
-> Since git will, given a remote like "url = /foo", first look in
-> "/foo.git" for a bare git repository, so too does git-annex.
-> I do not think this is a path joining error. That seems likely to
-> be a red herring. --[[Joey]]
-
-Not sure if it's a bug or I'm doing something wrong, but if git-annex really need to check something in git remotes' paths, error message (the one at the top of this post) can be a more descriptive, I guess.
-Something like "error: failed to do something with git remote X on a remote host" would've been a lot less confusing than that GHC thing.
-
-Thanks!
-
-> I've never seen anything like this error message. I don't know if the
-> problem is caused by building with GHC 7, or what. You didn't say what
-> OS you're using. Searching for the error message, it seems to involve
-> Mac OS X. 
-
-> For example: <http://hackage.haskell.org/trac/ghc/ticket/3771>
->> The error "strange closure type" indicates some kind of memory corruption, which can have many different causes, from bugs in the GC to hardware failures.
-> 
-> You said that you'd been using git-annex built with that version of GHC
-> successfully before. Perhaps you could use `git bisect` to see if you can
-> identify a point in git-annex's history where this started happening?
-> Since you  can reproduce the problem by just running git-annex-shell at
-> the command line with the right parameters, it should be easy to bisect it.
-> 
-> Probably your best bet will be changing to a different version or build of
-> GHC.. --[[Joey]] 
-
----
-
-forwarded to GHC upstream; closing [[done]] --[[Joey]] 
diff --git a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_1_1c19e716069911f17bbebd196d9e4b61._comment b/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_1_1c19e716069911f17bbebd196d9e4b61._comment
deleted file mode 100644
index 98f0adc3d..000000000
--- a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_1_1c19e716069911f17bbebd196d9e4b61._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://fraggod.pip.verisignlabs.com.pip.verisignlabs.com/"
- subject="Bisect it is, then"
- date="2011-04-03T04:45:49Z"
- content="""
-Hm, if path's ok, guess there's no way around git-bisect indeed. Wonder if there's some kind of ccache for haskell...
-
-OS is linux, amd64 on \"host1\" and i386 on \"host2\" where git-annex-shell is crashing.
-I'll try to come up with a commit, thanks for clarifications.
-"""]]
diff --git a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_2_a4d66f29d257044e548313e014ca3dc3._comment b/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_2_a4d66f29d257044e548313e014ca3dc3._comment
deleted file mode 100644
index fb3658191..000000000
--- a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_2_a4d66f29d257044e548313e014ca3dc3._comment
+++ /dev/null
@@ -1,66 +0,0 @@
-[[!comment format=mdwn
- username="http://fraggod.pip.verisignlabs.com.pip.verisignlabs.com/"
- subject="Bisect results"
- date="2011-04-03T06:22:15Z"
- content="""
-Completed git-bisect twice, getting roughly the same results:
-
-    828a84ba3341d4b7a84292d8b9002a8095dd2382 is the first bad commit
-    commit 828a84ba3341d4b7a84292d8b9002a8095dd2382
-    Author: Joey Hess <joey@kitenet.net>
-    Date:   Sat Mar 19 14:33:24 2011 -0400
-
-        Add version command to show git-annex version as well as repository version information.
-
-    :040000 040000 ed849b7b6e9b177d6887ecebd6a0f146357824f3 1c98699dfd3fc3a3e2ce6b55150c4ef917de96e9 M      Command
-    :100644 100644 b9c22bdfb403b0bdb1999411ccfd34e934f45f5c adf07e5b3e6260b296c982a01a73116b8a9a023c M      GitAnnex.hs
-    :100644 100644 76dd156f83f3d757e1c20c80d689d24d0c533e16 d201cc73edb31f833b6d00edcbe4cf3f48eaecb0 M      Upgrade.hs
-    :100644 100644 5f414e93b84589473af5b093381694090c278e50 d4a58d77a29a6a02daf13cec0df08b5aab74f65e M      Version.hs
-    :100644 100644 f5c2956488a7afafd20374873d79579fb09b1677 f8cd577e992d38c7ec1438ce5c141eb0eb410243 M      configure.hs
-    :040000 040000 f9b7295e997c0a5b1dda352f151417564458bd6e a30008475c1889f4fd8d60d4d9c982563380a692 M      debian
-    :040000 040000 9d87a5d8b9b9fe7b722df303252ffd5760d66f75 08834f61a10d36651b3cdcc38389f45991acdf5e M      doc
-
-contents of final refs/bisect:
-
-    bad (828a84ba3341d4b7a84292d8b9002a8095dd2382)
-    good-33cb114be5135ce02671d8ce80440d40e97ca824
-    good-942480c47f69e13cf053b8f50c98c2ce4eaa256e
-    good-ca48255495e1b8ef4bda5f7f019c482d2a59b431
-
-\"roughly\" because second bisect gave two commits as a result, failing to build one of them (missing .o file on link, guess it's because of -j4 and bad deps in that version's build system):
-
-    There are only 'skip'ped commits left to test.
-    The first bad commit could be any of:
-    828a84ba3341d4b7a84292d8b9002a8095dd2382
-    5022a69e45a073046a2b14b6a4e798910c920ee9
-    We cannot bisect more!
-
-Also noticed that \"git-annex-shell ...\" command succeeds if ran as root user, while failing from unprivileged one.
-There are no permission/access errors in \"strace -f git-annex-shell ...\", so I guess it could be some bug in the GHC indeed.
-
-JIC, logged a whole second bisect operation.
-Resulting log: [http://fraggod.net/static/share/git-annex-bisect.log](http://fraggod.net/static/share/git-annex-bisect.log)
-
-Bisect script I've used (git-annex-shell dies with error code 134 - SIGABRT on GHC error):
-
-    res=
-    while true; do
-      if [[ -n \"$res\" ]]; then
-        cd /var/tmp/paludis/build/dev-scm-git-annex-scm.bak/work/git-annex-scm
-        echo \"---=== BISECT ($res) ===---\"; git bisect \"$res\" 2>&1; echo '---=== /BISECT ===---'
-        cd
-        rm -Rf /var/tmp/paludis/build/dev-scm-git-annex-scm
-        cp -a --reflink=auto /var/tmp/paludis/build/dev-scm-git-annex-scm{.bak,}
-        chown -R paludisbuild: /var/tmp/paludis/build/dev-scm-git-annex-scm
-      fi
-      res=
-      cave resolve -zx1 git-annex --skip-until-phase configure || res=skip
-      if [[ -z \"$res\" ]]; then
-        cd /remote/path
-        sudo -u user git-annex-shell 'sendkey' '/remote/path' 'SHA1-s6654080--abd8edec20648ade69351d68ae1c64c8074a6f0b' '--' rsync --server --sender -vpe.Lsf --inplace . ''
-        if [[ $? -eq 134 ]]; then res=bad; else res=good; fi
-        cd
-      fi
-    done 2>&1 | tee ~/git-annex-bisect.log
-
-"""]]
diff --git a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_3_f5f1081eb18143383b2fb1f57d8640f5._comment b/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_3_f5f1081eb18143383b2fb1f57d8640f5._comment
deleted file mode 100644
index 491b53786..000000000
--- a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_3_f5f1081eb18143383b2fb1f57d8640f5._comment
+++ /dev/null
@@ -1,38 +0,0 @@
-[[!comment format=mdwn
- username="http://fraggod.pip.verisignlabs.com.pip.verisignlabs.com/"
- subject="comment 3"
- date="2011-04-03T06:57:02Z"
- content="""
-Repeated bisect with -j1, just to be sure it's not a random error, and it gave me 828a84ba3341d4b7a84292d8b9002a8095dd2382 again.
-Guess I'll look through the changes there a bit later and try to revert these until it works.
-
-Not sure if it's repeatable by anyone but me  (and hence worth fixing), but here's a bit more of info about the system:
-
-    Exherbo linux
-    Linux sacrilege 2.6.38.2-fg.roam #4 SMP PREEMPT Mon Mar 28 21:08:47 YEKST 2011 i686 GNU/Linux
-
-    dev-lang/ghc-7.0.2:7.0.2::installed
-    dev-haskell/HUnit-1.2.2.3:1.2.2.3::installed
-    dev-haskell/MissingH-1.1.0.3:1.1.0.3::installed
-    dev-haskell/QuickCheck-2.4.0.1:2.4.0.1::installed
-    dev-haskell/array-0.3.0.2:0.3.0.2::installed
-    dev-haskell/bytestring-0.9.1.7:0.9.1.7::installed
-    dev-haskell/containers-0.4.0.0:0.4.0.0::installed
-    dev-haskell/extensible-exceptions-0.1.1.2:0.1.1.2::installed
-    dev-haskell/filepath-1.2.0.0:1.2.0.0::installed
-    dev-haskell/hslogger-1.1.3:0::installed
-    dev-haskell/mtl-2.0.1.0:2.0.1.0::installed
-    dev-haskell/network-2.3.0.1:2.3.0.1::installed
-    dev-haskell/old-locale-1.0.0.2:1.0.0.2::installed
-    dev-haskell/parsec-3.1.0:3.1.0::installed
-    dev-haskell/pcre-light-0.4:0::installed
-    dev-haskell/regex-base-0.93.2:0.93.2::installed
-    dev-haskell/regex-compat-0.93.1:0.93.1::installed
-    dev-haskell/regex-posix-0.94.4:0.94.4::installed
-    dev-haskell/syb-0.3:0.3::installed
-    dev-haskell/transformers-0.2.2.0:0.2.2.0::installed
-    dev-haskell/utf8-string-0.3.6:0.3.6::installed
-
-(some stuff listed here as ::installed, but contains no files, since these packages detect whether ghc-7.0.2 already comes with the same/newer package version)
-
-"""]]
diff --git a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_4_b1f818b85c3540591c48e7ba8560d070._comment b/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_4_b1f818b85c3540591c48e7ba8560d070._comment
deleted file mode 100644
index 45d3d8bac..000000000
--- a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_4_b1f818b85c3540591c48e7ba8560d070._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 4"
- date="2011-04-03T16:06:34Z"
- content="""
-Nice work on the bisection. It's obviously a compiler bug. Having two test cases that differ in only as trivial and innocous a commit as 828a84ba3341d4b7a84292d8b9002a8095dd2382 might help a GHC developer track it down.
-
-We should probably forward this as a GHC bug. I hope you can find a different version or build of GHC to build git-annex with.
-"""]]
diff --git a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_5_67406dd8d9bd4944202353508468c907._comment b/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_5_67406dd8d9bd4944202353508468c907._comment
deleted file mode 100644
index bffa9bb86..000000000
--- a/doc/bugs/git-annex-shell:_internal_error:_evacuate__40__static__41__:_strange_closure_type_30799/comment_5_67406dd8d9bd4944202353508468c907._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://fraggod.pip.verisignlabs.com.pip.verisignlabs.com/"
- subject="Reported the issue to GHC"
- date="2011-04-07T13:44:36Z"
- content="""
-Finally got around to [report the issue to GHC tracker](http://hackage.haskell.org/trac/ghc/ticket/5085#comment:7).
-
-Looks quite alike (at least to the haskell-illiterate person like me) to a highest-priority issue that's hanging right at the top of the list.
-There are other similar reports, but they seem to be either related to PowerPC Macs, closed as invalid or due to needinfo inactivity.
-
-Guess any further discussion belongs there, unless ghc developers will bounce it back.
-Thanks a lot for your help, Joey, and for sharing a great thing that git-annex is.
-"""]]
diff --git a/doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__.mdwn b/doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__.mdwn
deleted file mode 100644
index 174e8082a..000000000
--- a/doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__.mdwn
+++ /dev/null
@@ -1,53 +0,0 @@
-What steps will reproduce the problem?
-On Arch Linux, using a cabal installation or prebuilt binaries:
-
-    git-annex get foobar
-
-The remote is an ssh URL: ssh://user@host/path/to/repo.git. Fetching the URL worked just fine.
-
-
-What is the expected output? What do you see instead?
-I expect git-annex to retrieve the file from the remote.
-Insted I see this:
-
-        get foobar (from origin...)                                              
-        git-annex-shell: user error (unrecognized option `--uuid'                                                                                       
-                                                                                 
-        Usage: git-annex-shell [-c] command [parameters ...] [option ..]         
-                                                                                 
-        Options:                                                                 
-                   --force         allow actions that may lose annexed data      
-          -F       --fast          avoid slow operations                         
-          -q       --quiet         avoid verbose output                          
-          -v       --verbose       allow verbose output (default)                
-          -d       --debug         show debug messages                           
-          -b NAME  --backend=NAME  specify key-value backend to use              
-                                                                                 
-        Commands:                                                                
-          configlist DIRECTORY          outputs relevant git configuration       
-          inannex    DIRECTORY KEY ...  checks if keys are present in the annex  
-          dropkey    DIRECTORY KEY ...  drops annexed content for specified keys 
-          recvkey    DIRECTORY KEY      runs rsync in server mode to receive content
-          sendkey    DIRECTORY KEY      runs rsync in server mode to send content
-        )                                                                        
-        rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
-        rsync error: error in rsync protocol data stream (code 12) at io.c(605) [Receiver=3.0.9]
-                                                                                 
-          Unable to access these remotes: origin                                 
-                                                                                 
-          Try making some of these repositories available:                       
-                5afcfc68-aa55-11e2-b5aa-73eac1531269 -- origin (my_remote)       
-        failed                                                                   
-        git-annex: get: 1 failed
-
-
-What version of git-annex are you using? On what operating system?
-git-annex does not understand a '--version' switch and I cannot find another option to print the version. It's the latest I just installed via cabal.
-OS is Arch Linux on kernel 3.8.8
-
-> This happens if the remote server has a very old version of
-> git-annex-shell. While I would not, today, add a new option like
-> --uuid that breaks backwards compatability as happened here, 
-> I don't intend to try to make git-annex backwards compatible
-> with that old version. Not even Debian stable has such an old version of 
-> git-annex anymore, so there's no excuse not to upgrade. [[done]]
diff --git a/doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__/comment_1_13510e954e36484e196e7395a3a9bf1f._comment b/doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__/comment_1_13510e954e36484e196e7395a3a9bf1f._comment
deleted file mode 100644
index 639e364d8..000000000
--- a/doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__/comment_1_13510e954e36484e196e7395a3a9bf1f._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-23T17:57:10Z"
- content="""
-`git annex version` is how you tell git-annex to print its version.
-
-The problem is not with the locally installed version of git-annex. You have a *very* old version of git-annex-shell installed on the server you're using as a remote. The last version of git-annex that did not support `git-annex-shell --uuid` was 3.20110928. You need to upgrade it to make it work with modern git-annex.
-"""]]
diff --git a/doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__/comment_2_7edc478a76983a3b3c68d01f24dce613._comment b/doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__/comment_2_7edc478a76983a3b3c68d01f24dce613._comment
deleted file mode 100644
index 86faca325..000000000
--- a/doc/bugs/git-annex-shell:_user_error___40__unrecognized_option___96__--uuid__39__/comment_2_7edc478a76983a3b3c68d01f24dce613._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn8nmg2ti0tVOD215PNBmLKvf2S4kXkQAY"
- nickname="Sören"
- subject="comment 2"
- date="2013-04-24T05:39:09Z"
- content="""
-Thanks, for the response. You're correct.
-I finally have it working. But it's not really easy, dealing with Arch Linux and Ubuntu 11.10 and make them talk to each other.
-"""]]
diff --git a/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option.mdwn b/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option.mdwn
deleted file mode 100644
index 8d4a7c512..000000000
--- a/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option.mdwn
+++ /dev/null
@@ -1,37 +0,0 @@
-<h4>What steps will reproduce the problem?</h4>
-
-On <tt>host1.example.tld</tt>:
-<pre><code>    git init /tmp/annex
-    cd /tmp/annex
-    git annex init
-    git config annex.rsync-options '--bwlimit=100'
-    dd if=/dev/urandom of=bigfile bs=1024 count=102400
-    git annex add bigfile
-    git commit -am bigfile
-</code></pre>
-
-On <tt>host2.example.tld</tt>:
-<pre><code>    git clone ssh://host1.example.tld/tmp/annex /tmp/annex
-    cd /tmp/annex
-    git annex init
-    git config annex.rsync-options '--bwlimit=100'
-    git annex get --from=origin bigfile
-</code></pre>
-
-<h4>What is the expected output? What do you see instead?</h4>
-<tt>bigfile</tt> is retrieved full speed, despite the <tt>bwlimit</tt> option. In fact on the origin <tt>host1.example.tld</tt>, <tt>ps x | grep rsync</tt> shows:
-<pre><code>
-    21386 ?        Ssl    0:00 git-annex-shell sendkey /tmp/annex SHA256E-s104857600--3e87b769b88db67c56f8c8a0245203a1c22cdb027f0a1230dac8309b1a9fded0 --uuid 7002cb3d-2205-4
-f8d-892b-5c35c693d76c -- remoteuuid=67263f47-7a5f-4a75-937b-7cffafa85f56 direct= associatedfile=bigfile -- dummy rsync --server --sender -ve.Lsf --bwlimit=100 --inplace .
-    21390 ?        S      0:01 rsync --server -t --inplace -e.Lsf . --sender /tmp/annex/.git/annex/objects/jX/3W/SHA256E-s104857600--3e87b769b88db67c56f8c8a0245203a1c22cdb02
-7f0a1230dac8309b1a9fded0/SHA256E-s104857600--3e87b769b88db67c56f8c8a0245203a1c22cdb027f0a1230dac8309b1a9fded0
-</code></pre>
-
-On the first line the option is indeed there, but it's somehow not forwarded to the actual rsync command. (On the client <tt>host2.example.tld</tt> the option shows up, but the sender's bandwidth seems to take precedence.)
-
-<h4>What version of git-annex are you using? On what operating system?</h4>
-
-git-annex 4.20130227, on Debian GNU/Linux (sid, i386).
-
-> [[done]], --bwlimit is now passed through from the caller.
-> Thanks, guilhem
diff --git a/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_1_8cda861c11ef2fff3442e5a0df741939._comment b/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_1_8cda861c11ef2fff3442e5a0df741939._comment
deleted file mode 100644
index 8c82c7e36..000000000
--- a/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_1_8cda861c11ef2fff3442e5a0df741939._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-09T06:13:17Z"
- content="""
-git-annex-shell cannot pass arbitrary rsync parameters through as specified by the client, because this would be a security hole (eg, allows overwriting or exposing arbitrary files). I'd have to pick out and whitelist safe parameters to make that work. 
-
-I'm also not sure if rsync --server does anything with --bwlimit, it's more of a client side option. When rsync is connecting to a rsync:// server, it can't tell the server to run with --bwlimit, AFAIK.
-
-Also, the bwlimit option works by stalling the connection occasionally, it's hardly very good and you'll sometime see it ramp back to full speed in between stalls.
-"""]]
diff --git a/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_2_15e06f6db9a14a8217dea25e24ddc23a._comment b/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_2_15e06f6db9a14a8217dea25e24ddc23a._comment
deleted file mode 100644
index 8c41b51f0..000000000
--- a/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_2_15e06f6db9a14a8217dea25e24ddc23a._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="46.239.117.180"
- subject="comment 2"
- date="2013-03-10T03:06:55Z"
- content="""
-From my tests, Rsync actually seems to honor the bandwidth limit that's in the sender's options. In particular, a dirty hard-coding of the limit in <tt>Utility.Rsync.rsyncServerParams</tt> (forwarding the option from <tt>git-annex-shell</tt> to the actuall rsync command, and) did the trick for me.
-
-I know Rsync merely tries to respect <tt>bwlimit</tt> on average, but for large files it's good enough I think. And for those like me who have a volume quota on their connection, it'd a plus to make <tt>git-annex-shell</tt> respect that limit. Well of course I could ask my users to use something like <tt>trickle</tt>, but external commands are more likely to be forgotten than a config option ;-)
-
-I couldn't see where in the code you whitelist the list of safe commands; Did you mean there is already such a thing, or is it empty right now? In any case, my wish doesn't seem to be hard to implement, and I'd be happy to try to provide a patch in the next few days.
-"""]]
diff --git a/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_3_d36045e2b466882108c5bf09580755fa._comment b/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_3_d36045e2b466882108c5bf09580755fa._comment
deleted file mode 100644
index 2b39d4bfa..000000000
--- a/doc/bugs/git-annex-shell_doesn__39__t_honour_Rsync__39__s_bwlimit_option/comment_3_d36045e2b466882108c5bf09580755fa._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-03-10T16:58:44Z"
- content="""
-There is not yet a white list, no. Patch would be appreciated.
-"""]]
diff --git a/doc/bugs/git-annex:_Argument_list_too_long.mdwn b/doc/bugs/git-annex:_Argument_list_too_long.mdwn
deleted file mode 100644
index f12d5da65..000000000
--- a/doc/bugs/git-annex:_Argument_list_too_long.mdwn
+++ /dev/null
@@ -1,40 +0,0 @@
-### Please describe the problem.
-
-Creating a SSH remote git-annex repository using the assisstant gives transcript:
-
-Initialized empty shared Git repository in /home/flindner/annex2/
-exec: 76: git-annex: Argument list too long
-
-### What steps will reproduce the problem?
-
-Using assistent: Creating a new empty local repository. Next, add another remote server repository using SSH. Checking the server went fine. I choose creating git repository. After about 5 minutes the error message above appears. In that time on the server runshell and git take plenty of CPU power but almost no memory. The directory on the server is created, but pairing was not successfull.
-
-### What version of git-annex are you using? On what operating system?
-
-Local: git-annex-standalone 4.20130909-1 from Archlinux AUR
-Remote: git-annex-standalone-i386.tar.gz as of 13. sept. 13. on Debian Squeeze.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-daemon.log is empty.
-
-Log from the web GUI:
-
-[2013-09-13 12:34:11 CEST] main: starting assistant version 4.20130827-g4f18612
-
-  No known network monitor available through dbus; falling back to polling
-(scanning...) [2013-09-13 12:34:11 CEST] Watcher: Performing startup scan
-(started...) 
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; I have added a guard to runshell to detect when it has
-> started to loop. Although I don't understand how a system could be
-> misconfigured to let that happen, without going far out of your way to 
-> mess it up, it's a failure mode that's worth guarding against. --[[Joey]]
diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_1_3f83ea525436b2379ab29a0f860c4669._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_1_3f83ea525436b2379ab29a0f860c4669._comment
deleted file mode 100644
index 43f4aa98b..000000000
--- a/doc/bugs/git-annex:_Argument_list_too_long/comment_1_3f83ea525436b2379ab29a0f860c4669._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.2.134"
- subject="comment 1"
- date="2013-09-13T15:31:35Z"
- content="""
-Can you add set -x near the top of the server's runshell script and run this again also with debugging enabled in the local assistant, and post the log, please.
-"""]]
diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_2_b417c94169378ef7d0d278ebae517fa1._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_2_b417c94169378ef7d0d278ebae517fa1._comment
deleted file mode 100644
index cd90d9c3b..000000000
--- a/doc/bugs/git-annex:_Argument_list_too_long/comment_2_b417c94169378ef7d0d278ebae517fa1._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w"
- nickname="Florian"
- subject="comment 2"
- date="2013-09-14T08:49:23Z"
- content="""
-Is there any way to get the transcript from a log file, not from the web page? The output is so enormous that it crashed my browser out of memory (which is 16 GiB) when I tried to paste it. daemon.log contains no interesting output.
-"""]]
diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_3_fa925cca216cb810ad80482b19fc6053._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_3_fa925cca216cb810ad80482b19fc6053._comment
deleted file mode 100644
index e182ca2c3..000000000
--- a/doc/bugs/git-annex:_Argument_list_too_long/comment_3_fa925cca216cb810ad80482b19fc6053._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w"
- nickname="Florian"
- subject="comment 3"
- date="2013-09-15T23:08:48Z"
- content="""
-Ok, I managed to get the transcript. It is located at <http://xgm.de/upload/transcript.log> (partly) resp. <http://xgm.de/upload/transcript.log.gz> (complete). Looks like the same script is executed again and again with an ever growing LD_LIBRARY_PATH argument list. The same happens when I simply run \"git-annex\" on the shell of the server. \"runshell\" standalone works fine.
-"""]]
diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_4_8bd2996107b2d272c32810658e07e715._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_4_8bd2996107b2d272c32810658e07e715._comment
deleted file mode 100644
index 033e695f5..000000000
--- a/doc/bugs/git-annex:_Argument_list_too_long/comment_4_8bd2996107b2d272c32810658e07e715._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w"
- nickname="Florian"
- subject="comment 4"
- date="2013-09-15T23:10:38Z"
- content="""
-Addendum: git inside runshells works, git-annex not.
-"""]]
diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_5_378de7d7503a64611eab62f2f5cffef3._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_5_378de7d7503a64611eab62f2f5cffef3._comment
deleted file mode 100644
index b10c66c81..000000000
--- a/doc/bugs/git-annex:_Argument_list_too_long/comment_5_378de7d7503a64611eab62f2f5cffef3._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w"
- nickname="Florian"
- subject="comment 5"
- date="2013-09-16T09:00:34Z"
- content="""
-Ok, bug can be closed, it was never a bug (at least not in git-annex). I was using the i386 build on a x86_64 machine.
-
-Server is virtual machine from Strato.
-
-$ uname -a
-Linux h1774498.stratoserver.net 2.6.32-042stab078.27 #1 SMP Mon Jul 1 20:48:07 MSK 2013 i686 GNU/Linux
-
-Since there was no x86_64 in the uname output, I thought it was a i386 machine. The git-annex binaries gave a \"File not found\" error message, the git binaries worked. Nothing I connected to a wrong architecture... Sorry for the hassle!
-"""]]
diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_6_a94e17151348d02999442dd1219babfb._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_6_a94e17151348d02999442dd1219babfb._comment
deleted file mode 100644
index a788f2c8e..000000000
--- a/doc/bugs/git-annex:_Argument_list_too_long/comment_6_a94e17151348d02999442dd1219babfb._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.14.105"
- subject="comment 6"
- date="2013-09-19T17:31:46Z"
- content="""
-I have tried to reproduce this bug, running the amd64 build on i386, and cannot. When I run the git-annex shell script included in the standalone bundle, it runs runshell, which in turn tries to run bin/git-annex. Since the architecture is wrong, that fails.
-
-I suppose your shell could instead, if presented with a binary of the wrong architecture, skip it and keep searching PATH for another one. That would be a most odd behavior, but if that were the case and you put the git-annex script into PATH, it would lead to what you describe.
-"""]]
diff --git a/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__.mdwn b/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__.mdwn
deleted file mode 100644
index 862259422..000000000
--- a/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-What steps will reproduce the problem?
-
-    alip@hayalet /tmp/aaa (git)-[master] % git annex init aaa
-    init aaa ok
-    (Recording state in git...)
-    alip@hayalet /tmp/aaa (git)-[master] % git remote add çüş /tmp/çüş
-    alip@hayalet /tmp/aaa (git)-[master] % git annex sync --debug
-    git ["--git-dir=/tmp/aaa/.git","--work-tree=/tmp/aaa","symbolic-ref","HEAD"]
-    git ["--git-dir=/tmp/aaa/.git","--work-tree=/tmp/aaa","show-ref","git-annex"]
-    git ["--git-dir=/tmp/aaa/.git","--work-tree=/tmp/aaa","show-ref","--hash","refs/heads/git-annex"]
-    git ["--git-dir=/tmp/aaa/.git","--work-tree=/tmp/aaa","log","refs/heads/git-annex..bc45cd9c2cb7c9b0c7a12a4c0210fe6a262abac9","--oneline","-n1"]
-    git ["--git-dir=/tmp/aaa/.git","--work-tree=/tmp/aaa","log","refs/heads/git-annex..9220bfedd1e13b2d791c918e2d59901af353825f","--oneline","-n1"]
-    (merging origin/git-annex into git-annex...)
-    git ["--git-dir=/tmp/aaa/.git","--work-tree=/tmp/aaa","cat-file","--batch"]
-    git ["--git-dir=/tmp/aaa/.git","--work-tree=/tmp/aaa","update-index","-z","--index-info"]
-    git ["--git-dir=/tmp/aaa/.git","--work-tree=/tmp/aaa","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","9220bfedd1e13b2d791c918e2d59901af353825f"]
-    git-annex: Cannot decode byte '\xfc': Data.Text.Encoding.decodeUtf8: Invalid UTF-8 stream
-    1 alip@hayalet /tmp/aaa (git)-[master] % 
-
-What is the expected output? What do you see instead?
-
-Syncing a repository under a path with utf-8 characters in its name fails.
-
-What version of git-annex are you using? On what operating system?
-
-git-annex version: 3.20120624
-
-On Exherbo, linux-3.4
-
-Please provide any additional information below.
-
-'\xfc' is valid UTF-8: 'LATIN SMALL LETTER U WITH DIAERESIS'
-
-> closing as non-reproducible and presumably fixed. [[done]] --[[Joey]] 
diff --git a/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_1_f1a7352b04f395e06e0094c1f51b6fff._comment b/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_1_f1a7352b04f395e06e0094c1f51b6fff._comment
deleted file mode 100644
index 28faa7b45..000000000
--- a/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_1_f1a7352b04f395e06e0094c1f51b6fff._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.25"
- subject="comment 1"
- date="2012-06-27T02:48:31Z"
- content="""
-I don't think this has to do with the path name of the repository containing utf-8 at all.
-
-Your recipe for reproducing this depends on some pre-existing repository that I don't know how to set up to reproduce this bug. All I can guess is that, based on the \"decodeUtf8\" in the error message, it's coming from the one part of the code that still uses that, the union merger.
-
-
-"""]]
diff --git a/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_2_c1890067079cd99667f31cbb4d2e4545._comment b/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_2_c1890067079cd99667f31cbb4d2e4545._comment
deleted file mode 100644
index 3486be733..000000000
--- a/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_2_c1890067079cd99667f31cbb4d2e4545._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.25"
- subject="comment 2"
- date="2012-06-27T03:08:13Z"
- content="""
-Since I can't reproduce it I am not sure, but it may be fixed by the commits I've just made.
-"""]]
diff --git a/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_3_213c96085c60c8e52cd803df07240158._comment b/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_3_213c96085c60c8e52cd803df07240158._comment
deleted file mode 100644
index 48a382029..000000000
--- a/doc/bugs/git-annex:_Cannot_decode_byte___39____92__xfc__39__/comment_3_213c96085c60c8e52cd803df07240158._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkWzAq6TusMi9zI3FLkDOETRIAUTtmGZVg"
- nickname="Ali"
- subject="comment 3"
- date="2012-06-27T12:56:37Z"
- content="""
-Yes, the problem is fixed.
-
-The repository was a normal git repository with path /tmp/çüş (git init)
-and with annex description \"çüş\" (git annex init çüş)
-
-afaict, i can't reproduce the problem anymore either :-)
-"""]]
diff --git a/doc/bugs/git-annex:_Not_in_a_git_repository._.mdwn b/doc/bugs/git-annex:_Not_in_a_git_repository._.mdwn
deleted file mode 100644
index a2817661e..000000000
--- a/doc/bugs/git-annex:_Not_in_a_git_repository._.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-What steps will reproduce the problem?
-
-As a default user i want to start git-annex assistent with
-
-`$ git-annex webapp`
-
-`git-annex: Not in a git repository.`
-
-What is the expected output? What do you see instead?
-
-I would expect the assistent to popup in a opened browser window.
-
-What version of git-annex are you using? On what operating system?
-
-Debian wheezy with git-annex version: 3.20130114
-
-Please provide any additional information below.
-
-Its working if i start `git-annex webapp` as root. I had the same error on previous version.
-
-> I've made some improvements. Think this was user error. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_1_e10363a912953a646b87c824d1c6e5d4._comment b/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_1_e10363a912953a646b87c824d1c6e5d4._comment
deleted file mode 100644
index ea2b1fbf3..000000000
--- a/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_1_e10363a912953a646b87c824d1c6e5d4._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 1"
- date="2013-01-15T20:20:22Z"
- content="""
-Sounds like a permissions error. Take a look at the repository in `~/Desktop/annex/` or `~/annex/` , and see if it contains files owned by root, or has bad directory permissions that would prevent your normal user from accessing it. Don't forget to check in its `.git` directory.
-
-I'd recommend not running the git-annex webapp as root. (There may be valid use cases for root to use git-annex in command-line mode.)
-"""]]
diff --git a/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_2_9e96063a664b2be8a36d7940e7632d3f._comment b/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_2_9e96063a664b2be8a36d7940e7632d3f._comment
deleted file mode 100644
index 4b054b120..000000000
--- a/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_2_9e96063a664b2be8a36d7940e7632d3f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmaMxYm33s0H-nxBo5uzYUzdIECoyR8Ug8"
- nickname="Stefan"
- subject="removing config"
- date="2013-02-11T20:42:29Z"
- content="""
-What fixed this for me was to remove .config/git-annex.
-"""]]
diff --git a/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_3_8c9bd76b0e1200723ec13fbef943a2cc._comment b/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_3_8c9bd76b0e1200723ec13fbef943a2cc._comment
deleted file mode 100644
index 403933886..000000000
--- a/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_3_8c9bd76b0e1200723ec13fbef943a2cc._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.183"
- subject="comment 3"
- date="2013-02-12T15:42:57Z"
- content="""
-What can happen is that `.config/git-annex/autostart` can list a repository that is somehow trashed. For example, I've seen this when I let the webapp make a repository, and then manually deleted the directory, while the webapp was running. The webapp then re-creates the directory, but it's not a valid git repo, just a mostly empty directory.
-
-Tend to see this as user error though..
-"""]]
diff --git a/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_4_8c49979b8a815f0d6f9de39ee9a88730._comment b/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_4_8c49979b8a815f0d6f9de39ee9a88730._comment
deleted file mode 100644
index 3b7fee676..000000000
--- a/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_4_8c49979b8a815f0d6f9de39ee9a88730._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="modules"
- ip="2.206.0.102"
- subject="comment 4"
- date="2013-04-03T07:45:53Z"
- content="""
-Seems like a user error from my side. I removed repos while webapp was still running. Removing ~/.config/git-annex solved my problem. Thanks.
-"""]]
diff --git a/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error.mdwn b/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error.mdwn
deleted file mode 100644
index b7c67e398..000000000
--- a/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error.mdwn
+++ /dev/null
@@ -1,35 +0,0 @@
-### Please describe the problem.
-$ WEBDAV_USERNAME=xxx@gmail.com WEBDAV_PASSWORD=xxx git annex initremote box.com type=webdav url=https://dav.box.com/dav/git-annex-Pictures chunksize=75mb encryption=shared
-initremote box.com (encryption setup) (shared cipher) (testing WebDAV server...)
-
-git-annex: WebDAV failed to write file: TlsNotSupported: user error
-failed
-git-annex: initremote: 1 failed
-
-
-### What steps will reproduce the problem?
-Compiled with cabal.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 5.20131213
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 5
-upgrade supported from repository versions: 0 1 2 4
-
-ArchLinux
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_1_2c54c57f456e4570666fd7a5731dcd27._comment b/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_1_2c54c57f456e4570666fd7a5731dcd27._comment
deleted file mode 100644
index cf649c1dd..000000000
--- a/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_1_2c54c57f456e4570666fd7a5731dcd27._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 1"
- date="2013-12-16T16:06:26Z"
- content="""
-Tested this with the Debian build and it works ok.
-
-TlsNotSupported is a new exception thrown by http-client, which is a very new library. Using an older version of http-conduit should avoid whatever the bug is.
-Probably something to do with http-conduit not using http-client-tls, so http-client is left with no way to handle TLS connections.
-"""]]
diff --git a/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_2_c9a9f070b2eaff9f68f603ca1defec81._comment b/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_2_c9a9f070b2eaff9f68f603ca1defec81._comment
deleted file mode 100644
index 95f611593..000000000
--- a/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_2_c9a9f070b2eaff9f68f603ca1defec81._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 2"
- date="2013-12-16T16:23:10Z"
- content="""
-This turns out to have been a bug in version 0.5 of the haskell DAV library, and was fixed already in a newer version. So cabal update; cabal install DAV; cabal install git-annex
-"""]]
diff --git a/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_3_62ff37a8429cfb3577d4250c701811d0._comment b/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_3_62ff37a8429cfb3577d4250c701811d0._comment
deleted file mode 100644
index 304d85901..000000000
--- a/doc/bugs/git-annex:_WebDAV_failed_to_write_file:_TlsNotSupported:_user_error/comment_3_62ff37a8429cfb3577d4250c701811d0._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawleVyKk2kQsB_HgEdS7w1s0BmgRGy1aay0"
- nickname="Milan"
- subject="comment 3"
- date="2013-12-16T16:41:08Z"
- content="""
-Thanks, after the update it works.
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed.mdwn b/doc/bugs/git-annex:_status:_1_failed.mdwn
deleted file mode 100644
index 65f00469c..000000000
--- a/doc/bugs/git-annex:_status:_1_failed.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-Hi
-
-I have a 1 To repository on my local linux box
-
-when i try :
-
-    git annex status
-
-i get :
-
-    git-annex: /media/malima/nazare/.git/annex/tmp/0723300. Everywhere I Dub --: getFileStatus: does not exist (No such file or directory)
-    failed
-
-how could i fix this issue ?
-
-many thanks for help
-
-> [[done]]; I managed to reproduce this bug by making a temp file named
-> ".git/annex/tmp/foo-", or indeed with any dash in it. This is enough
-> to make git-annex think it's a key, but badly formed enough that
-> it fails trying to use that key. Fixed to ignore such non-key files.
-> 
-> I'm unsure why `.git/annex/tmp` would have such files in it.
-> Perhaps the assistant was running, but crashed while adding files?
-> --[[Joey]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_10_7cd9de88e55633fc75460f4fe0400f09._comment b/doc/bugs/git-annex:_status:_1_failed/comment_10_7cd9de88e55633fc75460f4fe0400f09._comment
deleted file mode 100644
index 556982e34..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_10_7cd9de88e55633fc75460f4fe0400f09._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="RaspberryPie"
- ip="204.8.156.142"
- subject="comment 10"
- date="2013-10-15T18:49:26Z"
- content="""
-`git annex status` complains about `.git/annex/tmp/problematic_file--`. That file doesn't exist, but `.git/annex/tmp/problematic_file-` (with one dash) does. And the file itself (no dashes) does exist in a subdir of the annex.  
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_11_504a944aab34155046f2fd82c2878f3e._comment b/doc/bugs/git-annex:_status:_1_failed/comment_11_504a944aab34155046f2fd82c2878f3e._comment
deleted file mode 100644
index 45ee3a050..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_11_504a944aab34155046f2fd82c2878f3e._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="RaspberryPie"
- ip="96.44.189.101"
- subject="comment 11"
- date="2013-10-27T00:59:56Z"
- content="""
-I've tried a few things and found a workaround for the problem. TL;DR: `git annex dropunused`
-
-First I created a new annex with the same data. This time I used `git annex add` instead of having the assistant add the files. Adding went fine (no status error). Only when I started the assistant I got the error right away, with exactly the same file as the last time. 
-
-When I removed the file from the annex, the error remained, but this time with a different problematic file in the same directory. 
-
-Then I stumbled upon [this forum post](http://git-annex.branchable.com/forum/dot_git_slash_annex_slash_tmp/). It relates to this bug in that the files git-annex is complaining about are located in .git/annex/tmp. `git annex unused` returned about 130 entries (of about 1,200 files total). The last entry was my problematic file. The second-to-last entry was the file that gave me the same error when I removed the original problematic file. This lets me assume that the bug causes `git annex status' to produce 130 errors, of which only the last one gets displayed.
-
-So I ran `git annex dropunused 1-130 --force`. (The command wouldn't run without `--force`, saying that it couldn't make sure if numcopies were being met. This may or may not be related to network problems I'm having lately.) Anyway, now the error was finally gone and the status output didn't complain anymore.
-
-Weird stuff.
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_1_c235cc83c75474e6393e08d2d94b119d._comment b/doc/bugs/git-annex:_status:_1_failed/comment_1_c235cc83c75474e6393e08d2d94b119d._comment
deleted file mode 100644
index a5a378c99..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_1_c235cc83c75474e6393e08d2d94b119d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.255.110"
- subject="comment 1"
- date="2013-09-09T19:38:50Z"
- content="""
-You might try moving the .git/annex/transfer/ directory out of the way. 
-
-What version of git-annex do you have installed?
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_2_932f6aaa712298a47868002872e16310._comment b/doc/bugs/git-annex:_status:_1_failed/comment_2_932f6aaa712298a47868002872e16310._comment
deleted file mode 100644
index 98fb1d805..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_2_932f6aaa712298a47868002872e16310._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="eezec"
- ip="93.21.246.236"
- subject="comment 2"
- date="2013-09-10T06:05:32Z"
- content="""
-i have
-    git-annex version: 4.20130815
-
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_3_4bf55320439de152a65e2f21d4a0604b._comment b/doc/bugs/git-annex:_status:_1_failed/comment_3_4bf55320439de152a65e2f21d4a0604b._comment
deleted file mode 100644
index 0c3604ad6..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_3_4bf55320439de152a65e2f21d4a0604b._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="eezec"
- ip="93.21.246.236"
- subject="comment 3"
- date="2013-09-11T06:12:20Z"
- content="""
-Joey .. moving transfer didn't work .. i have the same message when doing
-
-    git annex status
-    ....
-    getFileStatus: does not exist (No such file or directory)
-    ....
-    git-annex: status: 1 failed
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_4_cb2cfb798c6171f77eb7c4c4061c0f0c._comment b/doc/bugs/git-annex:_status:_1_failed/comment_4_cb2cfb798c6171f77eb7c4c4061c0f0c._comment
deleted file mode 100644
index 3e4ecb82f..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_4_cb2cfb798c6171f77eb7c4c4061c0f0c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.51"
- subject="comment 4"
- date="2013-09-12T21:10:12Z"
- content="""
-can you `strace git-annex status` ?
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_5_05c84dde377298adfd3fc20749b3108f._comment b/doc/bugs/git-annex:_status:_1_failed/comment_5_05c84dde377298adfd3fc20749b3108f._comment
deleted file mode 100644
index 61af9e9df..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_5_05c84dde377298adfd3fc20749b3108f._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="RaspberryPie"
- ip="213.61.149.100"
- subject="comment 5"
- date="2013-10-13T06:33:24Z"
- content="""
-I use v4.20130909 and get the same error when running `git-annex status`. Does it matter that my filename in question is shown to have two dashes (--) at the end, just as in OP's case? Other files in .git/annex/tmp only have one dash at the end. 
-
-Joey, I straced the command and sent the output to your kitenet e-mail address. Hope it helps.
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_6_bb5141e29c665bc0bb82611ea27d4be8._comment b/doc/bugs/git-annex:_status:_1_failed/comment_6_bb5141e29c665bc0bb82611ea27d4be8._comment
deleted file mode 100644
index ab720b6ce..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_6_bb5141e29c665bc0bb82611ea27d4be8._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.22"
- subject="comment 6"
- date="2013-10-13T17:35:20Z"
- content="""
-What is the last line printed before this error message?
-
-My preliminary analysis is that it is checking the sizes of stale files in .git/annex/tmp, and could fail if a temp file was deleted just as it was running.
-But if so it would be unlikely to happen every time `git annex status` is run. Or even if it did happen every time (perhaps because you appear to be running the git-annex assistant and it might be adding a lot of files in the background), the filename in the error message would be different every time. I have just committed a fix for that problem to git, but am not 100% sure it's really the problem that you're seeing.
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_7_5fd39168c9e1bf43909ee0ab3c75c40c._comment b/doc/bugs/git-annex:_status:_1_failed/comment_7_5fd39168c9e1bf43909ee0ab3c75c40c._comment
deleted file mode 100644
index 54f87581c..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_7_5fd39168c9e1bf43909ee0ab3c75c40c._comment
+++ /dev/null
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="RaspberryPie"
- ip="37.130.227.133"
- subject="comment 7"
- date="2013-10-13T22:14:05Z"
- content="""
-Yes, I run the assistant in the background. The error came up after I ran 
-
-    git init
-    git annex init
-    git annex direct
-    git annex assistant
-
-in a directory containing a lot of files (around 80G). Right away, `git annex status` gave me the error below. The file name in question never changed during the process of adding files and hasn't changed after all files have been added.
-
-Here's the complete command line output:
-
-    $ git annex status
-    supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-    supported remote types: git gcrypt S3 bup directory rsync web glacier hook
-    repository mode: direct
-    trusted repositories: 0
-    semitrusted repositories: 2
-       	00000000-0000-0000-0000-000000000001 -- web
-        c1bb8eb9-fb0c-4bac-b0df-37df25b2d1e7 -- here
-    untrusted repositories: 0
-    transfers in progress: none
-    available local disk space: 1.74 terabytes (+10 gigabytes reserved)
-
-    git-annex: /storage/media/.git/annex/tmp/problematic_file--: getFileStatus: does not exist (No such file or directory)
-    failed
-    git-annex: status: 1 failed
-
-
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment b/doc/bugs/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment
deleted file mode 100644
index e4fae1f31..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="RaspberryPie"
- ip="204.8.156.142"
- subject="comment 8"
- date="2013-10-14T17:49:05Z"
- content="""
-Quick question: Is there any way to get rid of the error in the existing repository (e.g. remove the problematic tmp file entry) so I can get a complete status output? Bonus points if I don't have to annex every single file anew. `git annex fsck` doesn't work, as doesn't `git annex fix` (it's a direct repo).
-"""]]
diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_9_573377d444aee0895b231082bc6839a4._comment b/doc/bugs/git-annex:_status:_1_failed/comment_9_573377d444aee0895b231082bc6839a4._comment
deleted file mode 100644
index 208f178a3..000000000
--- a/doc/bugs/git-annex:_status:_1_failed/comment_9_573377d444aee0895b231082bc6839a4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="64.134.31.139"
- subject="comment 9"
- date="2013-10-15T17:51:04Z"
- content="""
-Does the file that it's complaining about exist?
-"""]]
diff --git a/doc/bugs/git-annex_3.20130216.1_tests_are_broken.mdwn b/doc/bugs/git-annex_3.20130216.1_tests_are_broken.mdwn
deleted file mode 100644
index 6df6bf489..000000000
--- a/doc/bugs/git-annex_3.20130216.1_tests_are_broken.mdwn
+++ /dev/null
@@ -1,43 +0,0 @@
-    $ pwd
-    [bla]/git-annex-3.20130216.1
-    $ runhaskell Setup configure --prefix=/usr --libdir=/usr/lib64 --docdir=/usr/share/doc/git-annex-3.20130216.1-r2 \
-    --htmldir=/usr/share/doc/git-annex-3.20130216.1-r2/html --with-compiler=ghc-7.6.2 --enable-shared \
-    --disable-executable-stripping --global --verbose --enable-tests --flags=S3 --flags=-WebDAV --flags=-Inotify \
-    --flags=Dbus --flags=-Assistant --flags=-Webapp --flags=-Pairing --flags=-XMPP --flags=-DNS
-    $ runhaskell Setup.hs build
-    Building git-annex-3.20130217...
-    Preprocessing test suite 'test' for git-annex-3.20130217...
-    
-    Annex/UUID.hs:30:8:
-        Could not find module `System.Random'
-        It is a member of the hidden package `random-1.0.1.1'.
-        Perhaps you need to add `random' to the build-depends in your .cabal file.
-        Use -v to see a list of the files searched for.
-
-Adding `random` to the dependencies of the test suite results in:
-
-    $ runhaskell Setup.hs build
-    Building git-annex-3.20130217...
-    Preprocessing test suite 'test' for git-annex-3.20130217...
-    
-    Annex/UUID.hs:29:18:
-        Could not find module `Data.UUID'
-        It is a member of the hidden package `uuid-1.2.9'.
-        Perhaps you need to add `uuid' to the build-depends in your .cabal file.
-        Use -v to see a list of the files searched for.
-
-Adding `uuid` results in:
-
-    $ runhaskell Setup.hs build
-    Building git-annex-3.20130217...
-    Preprocessing test suite 'test' for git-annex-3.20130217...
-    
-    Command/Add.hs:25:8:
-        Could not find module `Utility.Touch'
-        Use -v to see a list of the files searched for.
-
-
-Also: you included ".git-annex.cabal.swp" in the tarball.
-
-> These problems in the cabal file were fixed the other day. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/git-annex___38___rsync_can__39__t_copy_files_with___39__:__39___in_their_names.mdwn b/doc/bugs/git-annex___38___rsync_can__39__t_copy_files_with___39__:__39___in_their_names.mdwn
deleted file mode 100644
index b55493dc4..000000000
--- a/doc/bugs/git-annex___38___rsync_can__39__t_copy_files_with___39__:__39___in_their_names.mdwn
+++ /dev/null
@@ -1,38 +0,0 @@
-What steps will reproduce the problem?
-
-Send a file with the character ':' in it. rsync fails to send those files from the command line as well
-confusing them with hostnames. As far as I know a workaround is prepending the pathname with './'
-(for rsync commandline invocation that is)
-
-What is the expected output? What do you see instead?
-
-    copy müzik/Mixxx/Recordings/2013-01-15_16h:13m:03s.mp3 (checking kaotik...) (to kaotik...) 
-    git-annex: //home/alip/kaotika/.git/annex/transfer/download/effe4eef-926f-494c-a3b6-eeecdc208fb9/SHA256-s36349200--ce51eaf316b19c61831
-    41f0bda1c54be7e590e5999753a4b1c16bafab93a3fc1: commitBuffer: invalid argument (invalid character)
-    git-annex-shell: recvkey: 1 failed
-    protocol version mismatch -- is your shell clean?
-    (see the rsync man page for an explanation)
-    rsync error: protocol incompatibility (code 2) at compat.c(174) [sender=3.0.9]
-
-
-What version of git-annex are you using? On what operating system?
-
-    git-annex version: 3.20120807
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3
-    upgrade supported from repository versions: 0 1 2
-
-Operating system is Linux (Exherbo) although this isn't a packaged installation.
-I installed it by hand from git sources.
-
-Please provide any additional information below.
-
-Thanks for the wonderful tool!
-
-> This is a duplicate of
-> [[bugs/commitBuffer:_invalid_argument___40__invalid_character__41__]],
-> which was fixed in version 3.20120924. You need to upgrade the git-annex
-> on kaotik. [[done]]
->
-> (It has nothing to do with rsync or colon in filenames.) --[[Joey]]
diff --git a/doc/bugs/git-annex_add_hangs_indefinitely_on_all_files.mdwn b/doc/bugs/git-annex_add_hangs_indefinitely_on_all_files.mdwn
deleted file mode 100644
index 24fcac89e..000000000
--- a/doc/bugs/git-annex_add_hangs_indefinitely_on_all_files.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-### Please describe the problem.
-
-Running "git annex add" on a file of any size (whether 10KB or 1GB) hangs forever, must be killed with ^C, and does not add the file.
-
-"git annex unannex" still works, as do other commands like "git annex status", "git annex whereis", etc.
-
-### What steps will reproduce the problem?
-
-Running "git annex add" from this computer on any git annex repository on any hard drive.
-
-### What version of git-annex are you using? On what operating system?
-
-I am using 3.20121127 on Arch Linux with git version 1.8.5.2.
-
-My hard drive has several gigabytes of free space, and I have no trouble using git itself for development in other repositories.
-
-I have been using this for over a year with no problem; I first noticed this about a week ago, and it must have started within the last ~3 weeks at most.
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-$git annex add test.txt
-add test.txt 
-
-# End of transcript or log.
-"""]]
-
-> [[done]]
diff --git a/doc/bugs/git-annex_add_hangs_indefinitely_on_all_files/comment_1_f787155da9a4d92c41546c35f3bd6a08._comment b/doc/bugs/git-annex_add_hangs_indefinitely_on_all_files/comment_1_f787155da9a4d92c41546c35f3bd6a08._comment
deleted file mode 100644
index f22fd23ea..000000000
--- a/doc/bugs/git-annex_add_hangs_indefinitely_on_all_files/comment_1_f787155da9a4d92c41546c35f3bd6a08._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.35"
- subject="comment 1"
- date="2014-01-07T03:40:01Z"
- content="""
-3.20121127 is over a year out of date. You need to upgrade to a current version. I'd not be surprised if this is some incompatability with such an old git-annex and the rather new version of git you have installed.
-
-Assuming a current version of git-annex still has the problem (which seems unlikely), run the command again with --debug and paste the full output.
-
-
-"""]]
diff --git a/doc/bugs/git-annex_add_hangs_indefinitely_on_all_files/comment_2_66ad95d98c12b4b26e06e3fe28f0ed01._comment b/doc/bugs/git-annex_add_hangs_indefinitely_on_all_files/comment_2_66ad95d98c12b4b26e06e3fe28f0ed01._comment
deleted file mode 100644
index a4387e669..000000000
--- a/doc/bugs/git-annex_add_hangs_indefinitely_on_all_files/comment_2_66ad95d98c12b4b26e06e3fe28f0ed01._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmi5n3M8NMWsDYth_TGGRuJ4_CM2tPQfwg"
- nickname="Aditya"
- subject="comment 2"
- date="2014-01-07T04:54:40Z"
- content="""
-Wow, I did not realize how horribly out-of-date the Arch AUR package for this was - I've fixed it: https://aur.archlinux.org/packages/git-annex-bin/
-
-Thanks for the help - it seems to be working now.
-"""]]
diff --git a/doc/bugs/git-annex_add_should_repack_as_it_goes.mdwn b/doc/bugs/git-annex_add_should_repack_as_it_goes.mdwn
deleted file mode 100644
index e9c444857..000000000
--- a/doc/bugs/git-annex_add_should_repack_as_it_goes.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-What steps will reproduce the problem?
-
-1. Create a fresh git-annex repository
-2. Add a directory tree to it with about 300,000 files in it
-3. wait
-4. change the tree; attempt a git commit
-
-What is the expected output? What do you see instead?
-
-git commit hangs due to the large number of loose objects created during the git annex add. If git annex had stopped to repack the git repo a few times along the way, I think this might have been avoided.
-
-What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130323
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS
-
-Darwin pluto.local 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan  6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64
-(Mac OS 10.8.3)
-
-git version 1.8.2
-
-> Based on the benchmarks below, repacking even once does not speed things
-> up; repacking repeatedly as `git annex add` runs would slow things down.
-> 
-> It might be worth following up with the git developers why `git commit`
-> scans loose objects after it has already output the commit sha1sum.
-> 
-> Don't see any improvements git-annex can make. [[done]] --[[Joey]]
diff --git a/doc/bugs/git-annex_add_should_repack_as_it_goes/comment_1_dbcaa0be4cd764128fb7263a95f73a32._comment b/doc/bugs/git-annex_add_should_repack_as_it_goes/comment_1_dbcaa0be4cd764128fb7263a95f73a32._comment
deleted file mode 100644
index bdbeec108..000000000
--- a/doc/bugs/git-annex_add_should_repack_as_it_goes/comment_1_dbcaa0be4cd764128fb7263a95f73a32._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-05T02:31:08Z"
- content="""
-I created 300,000 files and added them. I found the following main cost centers:
-
-* Checksumming all those files has overhead. Can be avoided by using `--backend=WORM`
-* git-annex runs `git add` after every 10k files it processes. As the index file grows in size, `git add` gets slower (git has to rewrite the index file each time; which really needs to be improved on the git side in order for git to scale better to lots of files). Can be avoided by setting `annex.queuesize` to a larger value. If you have enough memory, git-annex can buffer all 300,000 files and only run `git add` once.
-* At the end of `git annex add`, it has to stage location logs for all files. This takes a few minutes; it probably on a par with the overhead of running `git add` once with an equal number of files.
-
-After `git annex add`, I ran `git commit -m add`. This commit took only 11 minutes.  (5 year old netbook with a SSD.) That may seem like a long time, but the (un-optimised) `git annex add` took 4 hours or so.
-
-In that commit, I saw these cost centers:
-
-* The `pre-commit` hooks runs `git annex pre-commit`, which scans all 300,000 symlinks to make sure they don't need fixing. That took around 5 seconds. Can be disabled if you don't mind manually running `git annex fix` when moving files.
-* Calculating the commit took a while.
-* `git commit` did process all the loose object files. It did not create a pack, and I am not sure why it needed to look at them, especially since it had already printed the sha of the commit, and so had already created all the objects it needed to at that point.
-
-Next I will try again, and first run `git gc` before `git commit` ....
-"""]]
diff --git a/doc/bugs/git-annex_add_should_repack_as_it_goes/comment_2_6a27551c4fb7f62ed9f627134c755d01._comment b/doc/bugs/git-annex_add_should_repack_as_it_goes/comment_2_6a27551c4fb7f62ed9f627134c755d01._comment
deleted file mode 100644
index 6f2207a6a..000000000
--- a/doc/bugs/git-annex_add_should_repack_as_it_goes/comment_2_6a27551c4fb7f62ed9f627134c755d01._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-04-05T06:33:54Z"
- content="""
-`git repack` took 18 minutes. However, it actually only packed the objects for the commit `git annex add` makes to the git-annex branch. Objects for the staged symlinks are left loose, presumably because no commit refers to them.
-
-Unsurprisingly, then, `git commit` still took as long as before.
-
-I then ran `git repack` again. It packed all the loose objects this time. After this, `git commit` only takes 11 seconds. If I remove the `pre-commit` hook, it drops to a respectable 5 seconds.
-
-
-"""]]
diff --git a/doc/bugs/git-annex_add_should_repack_as_it_goes/comment_3_ff8b589fbcf25c98abd1c58830074650._comment b/doc/bugs/git-annex_add_should_repack_as_it_goes/comment_3_ff8b589fbcf25c98abd1c58830074650._comment
deleted file mode 100644
index e60460443..000000000
--- a/doc/bugs/git-annex_add_should_repack_as_it_goes/comment_3_ff8b589fbcf25c98abd1c58830074650._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-06T06:32:56Z"
- content="""
-More testing shows that only the first git commit is slow. A second commit will be fast whether or not `git-repack` has been run in between.
-"""]]
diff --git a/doc/bugs/git-annex_branch_corruption.mdwn b/doc/bugs/git-annex_branch_corruption.mdwn
deleted file mode 100644
index 9c864d85f..000000000
--- a/doc/bugs/git-annex_branch_corruption.mdwn
+++ /dev/null
@@ -1,95 +0,0 @@
-Below is a test case which shows a way that the git-annex branch
-can become corrupted and lose data, including location log records and
-uuid.log lines.
-
-At the end, a commit on the git-annex branch removes one of the 2 lines
-from the uuid.log; which should never happen.
-
-The actual problem occurs earlier, at the "push point". Here a repo is
-cloned from the main one, initialized (adding the last uuid.log line),
-and then pushed back to the main one. That push is a fast-forward, so is
-allowed to directly update the git-annex branch in the main repo:
-
-	b884fe5..c497739  git-annex -> git-annex
-
-Now the git-annex branch has a change that is not reflected in
-`.git/annex/index`, so the next time a change is made, it's committed
-using the out of date index, which causes a reversion of the changes
-that were pushed to the branch.
-
----
-
-## Thoughts
-
-This is essentially the same reason why git blocks pushes to the checked-out
-branch of a non-bare repository. 
-
-This problem only affects workflows that involve pushing. Pulling workflows
-do not directly update the local git-annex branch, so avoid the problem.
-
-And while bare repos are pushed to, they rarely have changes made directly
-to their git-annex branches, so while I think the same problem could
-happen with pushing to a bare repo, it's unlikely.
-
-None of which is to say this is not a bad bug that needs to be comprehensively
-fixed. 
-
-Probably git-annex needs to record which ref of the git-annex branch
-corresponds to its index, and if the branch is at a different ref,
-merge it into the index.
-
-> And now that's [[done]]. I managed to do it with very little slowdown.
-> 
-> A side benefit is that users can now safely check out the git-annex
-> branch and commit changes to it, and git-annex will notice them.
-> Before, it was documented to ignore such changes.
-> --[[Joey]] 
-
----
-
-## Workaround
-
-Users who want to prevent this bug from occuring when pushing to their
-non-bare repositories can install this script as `.git/hooks/update`
-
-<pre>
-#!/bin/sh
-if [ "$1" = refs/heads/git-annex ]; then
-	exit 1
-fi
-</pre>
-
---[[Joey]] 
-
----
-
-## Test Case
-<pre>
-#!/bin/sh
-mkdir annextest
-cd annextest
-
-git init dir1
-cd dir1
-git annex init
-touch foo 
-echo hi > bar
-git annex add
-git commit -m add
-
-cd ..
-git clone dir1 dir2
-cd dir2
-git annex init otherdir
-git annex get
-# push point
-git push
-
-cd ..
-cd dir1
-echo "before"
-git show git-annex:uuid.log
-git annex drop foo --force
-echo "after"
-git show git-annex:uuid.log
-</pre>
diff --git a/doc/bugs/git-annex_branch_push_race.mdwn b/doc/bugs/git-annex_branch_push_race.mdwn
deleted file mode 100644
index 013ff70dd..000000000
--- a/doc/bugs/git-annex_branch_push_race.mdwn
+++ /dev/null
@@ -1,45 +0,0 @@
-The fix for the [[git-annex_branch_corruption]] bug is subject to a race.
-With that fix, git-annex does this when committing a change to the branch:
-
-1. lock the journal file (this avoids git-annex racing itself, FWIW)
-2. check what the head of the branch points to, to see if a newer branch
-   has appeared
-3. if so, updates the index file from the branch
-4. stages changes in the index
-5. commits to the branch using the index file
-
-If a push to the branch comes in during 2-5, then
-[[git-annex_branch_corruption]] could still occur.
-
----
-
-## approach 1, using locking
-
-Add an update hook and a post-update hook. The update hook
-will use locking to ensure that no git-annex is currently running
-a commit, and block any git-annex's from starting one. It
-will background itself, and remain running during the push.
-The post-update hook will signal it to exit.
-
-I don't like this approach much, since it involves a daemon, two hooks,
-and lots of things to go wrong. And it blocks using git-annex during a
-push. This approach should be a last resort.
-
-## approach 2, lockless method
-
-After a commit is made to the branch, check to see if the parent of
-the commit is the same ref that the index file was last updated to. If it's
-not, then the race occurred.
-
-How to recover from the race? Well, just union merging the parent of the
-commit into the index file and re-committing should work, I think. When
-the race occurs, the commit reverts its parent's changes, and this will
-redo them. 
-
-(Of course, this re-commit will also be subject to the race, and
-will need the same check for the race as the other commits. It won't loop
-forever, I hope.)
-
-> [[done]] and tested.
-
---[[Joey]]
diff --git a/doc/bugs/git-annex_direct_fails_on_repositories_with_a_partial_set_of_files.mdwn b/doc/bugs/git-annex_direct_fails_on_repositories_with_a_partial_set_of_files.mdwn
deleted file mode 100644
index de88b0246..000000000
--- a/doc/bugs/git-annex_direct_fails_on_repositories_with_a_partial_set_of_files.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-## What steps will reproduce the problem?
-
-Running the following in an annex with an archive directory with all the files dropped and located offsite
-
-     git annex direct
-
-It seems that if not all the files are in the annex, then the direct mode files.
-
-## What is the expected output? What do you see instead?
-
-The expectation is that either direct mode reverts its changes if it fails instead of
-
-    url: createLink: does not exist (No such file or directory)
-    failed
-    git-annex: direct: 1 failed
-
-It leaves the annex in the indirect mode, but there are a bunch of .map files lying around in git-annex's control directory.
-
-## What version of git-annex are you using? On what operating system?
-
-Running 3.20130102 on OSX
-
-## Please provide any additional information below.
-
-> More specifically, git annex direct fails, on OSX only, when there are two
-> files that both have the same content. Apparently OSX doesn't allow
-> hard linking two symbolic links together. There was no harm in it doing that
-> otherwise, but then again no reason for it to do so, so I've put in a fix.
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn b/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn
deleted file mode 100644
index db6a35293..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx.mdwn
+++ /dev/null
@@ -1,100 +0,0 @@
-Currently the hashed directories in .git-annex allow for upper and lower case directory names... on linux (or any case sensitive filesystem) the directory names such as 'Gg' and 'GG' are different and unique. However on systems like OSX (and probably windows if it is ever supported) the directory names 'Gg' is the same as 'GG'
-
-In one of the annex'd repos that I have this has occured...
-
-<pre>
-$ git add -i                                                                                          
-           staged     unstaged path
-  1:    unchanged        +1/-1 .git-annex/GM/GV/WORM-s183630166-m1301072171--somefile.log
-  2:    unchanged        +1/-1 .git-annex/Gm/GV/WORM-s183630166-m1301072171--somefile.log
-</pre>
-
-
-this has somewhat confused git when it tries to stage/merge files, I didn't notice this at first, but it is definately a problem for someone using case insensitive filesystems  like the default OSX HFS+ formats or vfat/fat32.
-
-> I feel a bit stupid to not have considered case-insensative filesystems.
-> They are just so far from where I have lived for 20 years that it's hard
-> to keep them in mind.
-> 
-> I guess that
-> [[git-annex_has_issues_with_git_when_staging__47__commiting_logs]] is
-> somehow a consequence (or cause?) of this, but I don't quite understand
-> how this is causing git to fail to stage files, or stage the same file
-> twice under different capitalizations. git-annex always will run git add
-> on the path with the "correct" capitalization. So unless something else
-> has added the path with the other capitalization (perhaps git add
-> .git-annex manually?) I don't understand how you get to this state.
-> --[[Joey]]
-
->> I think I got myself into this situation when I copied some files over from a HFS+ partition to a GPFS network share (which is pretty posix compliant) over samba. It probably is related to the [[git-annex_has_issues_with_git_when_staging__47__commiting_logs]]. I thought they were unique enough to have two bug reports logged as one is a git behavioural thing and the other is git-annex specific.
-
->>> If you copied `.git/` over, perhaps you got a git repo without
->>> core.ignorecase set right for the filesystem it landed on?
-
->>>> I usually git clone or do a fresh repository and pull things in, I was also unaware of this ignorecase setting as well.
-
->>> 
->>> Something like this might reproduce it:
-
-<pre>
-# mkdir test; cd test; git init
-# git config core.ignorecase false
-# mkdir Foo
-# touch Foo/bar
-# git add Foo/bar
-# git add foo/bar
-# git add fOo/bar
-# git status
-# touch foo/other
-# git add fOo/other
-# git status
-</pre>
-
->>>> And then either git commit or git clone would probably get confused
->>>> if it thought 3 distinct files had been committed.
->>>> --[[Joey]]
-
->>>>> Doing the above test on a HFS+ partition yields this
-
-<pre>
-## with ignorecase=false
-commit bb024c6fd7482b2d10f60ae899cb7a949aca1ad8
-Author: Jimmy Tang <jtang@exia>
-Date:   Sun Mar 27 18:40:24 2011 +0100
-
-    commit
-
-diff --git a/Foo/bar b/Foo/bar
-new file mode 100644
-index 0000000..e69de29
-diff --git a/fOo/bar b/fOo/bar
-new file mode 100644
-index 0000000..e69de29
-diff --git a/fOo/other b/fOo/other
-new file mode 100644
-index 0000000..e69de29
-diff --git a/foo/bar b/foo/bar
-new file mode 100644
-index 0000000..e69de29
-</pre>
-
->>>>> and without changing ignorecase
-
-<pre>
-commit 909a089158ffb98f8e91f98905e2bfdc7234666f
-Author: Jimmy Tang <jtang@exia>
-Date:   Sun Mar 27 18:46:57 2011 +0100
-
-    commit
-
-diff --git a/Foo/bar b/Foo/bar
-new file mode 100644
-index 0000000..e69de29
-diff --git a/Foo/other b/Foo/other
-new file mode 100644
-index 0000000..e69de29
-</pre>
-
-> Closing this bug, as it seems I have dealt with it adequately now.
-> [[done]]
-> --[[Joey]] 
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_10_f3594de3ba2ab17771a4b116031511bb._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_10_f3594de3ba2ab17771a4b116031511bb._comment
deleted file mode 100644
index c3e6b5e59..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_10_f3594de3ba2ab17771a4b116031511bb._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 10"
- date="2011-04-01T16:11:52Z"
- content="""
-No, I don't need a copy of your repo now.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_11_97de7252bf5d2a4f1381f4b2b4e24ef8._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_11_97de7252bf5d2a4f1381f4b2b4e24ef8._comment
deleted file mode 100644
index db605f965..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_11_97de7252bf5d2a4f1381f4b2b4e24ef8._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 11"
- date="2011-04-02T17:53:58Z"
- content="""
-I have pushed out a preliminary fix. The old mixed-case directories will be left where they are, and still read from by git-annex. New data will be written to new, lower-case directories. I think that once git stops seeing changes being made
-to mixed-case, colliding directories, the bugs you ran into won't manifest any more.
-
-You will need to find a way to get your git repository out of the state where it complains about uncommitted files (and won't let you commit them). I have not found a reliable way to do that; git reset --hard worked in one case but not in another. May need to clone a fresh git repository.
-
-Let me know how it works out.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_12_f1c53c3058a587185e7a78d84987539d._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_12_f1c53c3058a587185e7a78d84987539d._comment
deleted file mode 100644
index 5f9a0ae27..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_12_f1c53c3058a587185e7a78d84987539d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 12"
- date="2011-04-02T17:58:24Z"
- content="""
-Also, you can delete `.git-annex/??` if you want to, then running `git annex fsck --fast` in each of your clones would regenerate the data using only the lower-case hash directories.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_13_4f56aea35effe5c10ef37d7ad7adb48c._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_13_4f56aea35effe5c10ef37d7ad7adb48c._comment
deleted file mode 100644
index b4a5a72d0..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_13_4f56aea35effe5c10ef37d7ad7adb48c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 13"
- date="2011-04-03T07:43:37Z"
- content="""
-Ok, thanks for the fix. It seems the fix isn't too reliable with my repos, I get different numbers of  \"** No known copies of...\" in the various cloned repos that I have. After all the \"messing\" that I have done to my repos I think git-annex has gotten very confused. I will just leave things as they are and let git-annex slowly migrate over to the new format or re-clone from a linux source and see how things go. I will report back on this issue in abit after I use it more to see.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_14_cc2a53c31332fe4b828ef1e72c2a4d49._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_14_cc2a53c31332fe4b828ef1e72c2a4d49._comment
deleted file mode 100644
index b92c3ab4a..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_14_cc2a53c31332fe4b828ef1e72c2a4d49._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 14"
- date="2011-04-03T08:24:17Z"
- content="""
-I meant to say in it wasn't reliable when I was following the instructions for \"Comment 12\". I did find that just doing a  \"git annex copy -t externalusb .\"  then a \"git annex drop .\" from the root of my cloned and \"none trusted\" annexed repos to be more reliable, it just means I temporarily need a load of space to get myself out of my earlier mess.
-
-On testing this bug fix, I found a minor behavioural issue with [[git annex copy -f REMOTE . doesn't work as expected]]
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_15_37f1d669c1fa53ee371f781c7bb820ae._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_15_37f1d669c1fa53ee371f781c7bb820ae._comment
deleted file mode 100644
index d722d546a..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_15_37f1d669c1fa53ee371f781c7bb820ae._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="gernot"
- ip="213.168.117.192"
- subject="comment 15"
- date="2011-04-03T15:41:00Z"
- content="""
-I also ran into problems on a case-insensitive HFS+ file system, it seems.  I
-tried following the instructions in comment 12:
-
-	1. Remove everything in .git-annex besides uuid.log and trust.log
-	2. git annex fsck --fast
-	3. Commit
-
-However, I still see upper and lower case directories in .git-annex.  Did I
-misunderstand that they should all be lower case now?
-
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_16_8a4ab1af59098f4950726cf53636c2b3._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_16_8a4ab1af59098f4950726cf53636c2b3._comment
deleted file mode 100644
index 97eab78c9..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_16_8a4ab1af59098f4950726cf53636c2b3._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 16"
- date="2011-04-03T16:02:33Z"
- content="""
-I think the correct steps should be, make a backup first :) then ...
-
-1. git pull  # update your clone, and commit everything so you don't lose anything
-2. git annex fsck --fast # check the repo first, just in case
-3. rm -rf .git-annex/?? # remove the old metadata
-4. git annex fsck --fast # get git annex to regenerate it all
-5. push your changes out to your other repos, you will need to make sure git-annex is updated everywhere if there are remotes in your setup.
-
-I eventually migrated all of my own annex'd repos and I no longer have the old hashed directories but the new ones in the form
-
-    .git/annex/aaa/bbb/foo.log
-
-I did lose some tracking information but not data (as far as I can see for now), but that was quickly fixed by pushing and pulling to my bare repo which tracks most of my data.
-
-I also found that it worked a bit more reliably for me on the copies of repos that were located on case sensitive filesystems, but I guess that was expected.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_17_515d5c5fbf5bd0c188a4f1e936d913e2._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_17_515d5c5fbf5bd0c188a4f1e936d913e2._comment
deleted file mode 100644
index f7feac67c..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_17_515d5c5fbf5bd0c188a4f1e936d913e2._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 17"
- date="2011-04-03T16:53:51Z"
- content="""
-@gernot step 0 is to upgrade git-annex to current git, on all systems where you use it, in case that wasn't clear.
-
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_18_db64c91dd1322a0ab168190686db494f._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_18_db64c91dd1322a0ab168190686db494f._comment
deleted file mode 100644
index 550558ec1..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_18_db64c91dd1322a0ab168190686db494f._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="gernot"
- ip="213.168.117.192"
- subject="comment 18"
- date="2011-04-03T19:46:16Z"
- content="""
-Joey, sorry, I got it wrong.  I thought upgrading git didn't help and you
-adjusted things in git-annex instead.
-
-Anyway, can I get around upgrading on all hosts by reformatting the drive to
-case-sensitive HFS+? Or will I have to upgrade git (currently version 1.7.2.5)
-eventually anyway?
-
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_19_ff555c271637af065203ca99c9eeaf89._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_19_ff555c271637af065203ca99c9eeaf89._comment
deleted file mode 100644
index 2676b3589..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_19_ff555c271637af065203ca99c9eeaf89._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 19"
- date="2011-04-03T19:53:44Z"
- content="""
-Git does not need to be upgraded. Git-annex needs to be upgraded to git rev 616e6f8a840ef4d99632d12a2e7ea15c3cfb1805 or newer, on all machines.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_1_9a7b09de132097100c1a68ea7b846727._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_1_9a7b09de132097100c1a68ea7b846727._comment
deleted file mode 100644
index aa5e46ca2..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_1_9a7b09de132097100c1a68ea7b846727._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 1"
- date="2011-03-28T07:23:41Z"
- content="""
-One possible work around is to just create a loopback file system with a case sensitive filesystem. I think I might do that for anything that I really care about for now.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_20_7e328b970169fffb8bce373d1522743b._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_20_7e328b970169fffb8bce373d1522743b._comment
deleted file mode 100644
index 8f0f5ef18..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_20_7e328b970169fffb8bce373d1522743b._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="ssqq"
- ip="208.70.196.4"
- subject="Still a problem on 0.20110523"
- date="2011-06-02T20:31:55Z"
- content="""
-Hi,
-
-(I'm new to git and git annex, so please forgive any mistakes I make...)
-
-My repo is messed up right now.  The fact that I copied the repo with rsync -a back and forth from a case insensitive filesystem to a case sensitive one, probably didn't help.
-
-I believe the annexed files in .git/annex/objects/ are still using a mixed case directory hashing scheme.  That's the problem I'm having.  The symlinks point to the wrong case and are now broken.  I don't think the latest versions of git-annex changed that (it only changed the hashing under .git-annex, right?).
-
-Even if I clean up my repo, I think I'm still going to have a problem because I have one repo on an OS X case insensitive filesystem and my other repos on case sensitive Linux filesystems.  Potentially the directory name under .git/annex/objects will have a different case.  Then the symlink might have a different case than my Linux FS.  Does git-annex track changes in git by the contents of the symlink?  In which case the case difference would show up as a change even though there is no change?
-
-Is it possible to change the directory hashing scheme under .git/annex/objects to use lowercase names?
-
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_21_98f632652b0db9131b0173d3572f4d62._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_21_98f632652b0db9131b0173d3572f4d62._comment
deleted file mode 100644
index 453a8be11..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_21_98f632652b0db9131b0173d3572f4d62._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 21"
- date="2011-06-10T16:46:03Z"
- content="""
-@seqq git-annex always uses the same case when creating and accessing the files pointed to by the symlinks. So it will not matter if it's used on a case-insensative, or case-insensative but preserving system like OSX.
-
-You need to fix up the cases of the files in .git/annex/objects to what it expects. I'm not sure what would be the best way to do that. The method described in [[walkthrough/recover_data_from_lost+found]] might work well.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_22_52d41afd7fd0b71a4c8e84ab1b4df5bd._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_22_52d41afd7fd0b71a4c8e84ab1b4df5bd._comment
deleted file mode 100644
index 7fa1e7468..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_22_52d41afd7fd0b71a4c8e84ab1b4df5bd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawltmUlf_zHb-hDkjLLYeUxyd81YVoIgZew"
- nickname="Jaen"
- subject="Still somewhat broken"
- date="2012-12-25T17:58:53Z"
- content="""
-I moved an external HDD formatted with NTFS from Mac (case-insensitive) to Linux (case sensitive), and half of the links are broken now... What can I do to fix this?
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_23_c2cd8a69c37539c0511bae02016180ca._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_23_c2cd8a69c37539c0511bae02016180ca._comment
deleted file mode 100644
index 8ec1abd89..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_23_c2cd8a69c37539c0511bae02016180ca._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawltmUlf_zHb-hDkjLLYeUxyd81YVoIgZew"
- nickname="Jaen"
- subject="comment 23"
- date="2012-12-25T20:21:15Z"
- content="""
-(to be clear, Mac put eg. hashes \"Gg\" and \"gg\" into the same directory, while Linux expects them to be in separate dirs)
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_2_174952fc3e3be12912e5fcfe78f2dd13._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_2_174952fc3e3be12912e5fcfe78f2dd13._comment
deleted file mode 100644
index 6e6e5dc6b..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_2_174952fc3e3be12912e5fcfe78f2dd13._comment
+++ /dev/null
@@ -1,185 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 2"
- date="2011-03-28T15:09:45Z"
- content="""
-I think I know how I got myself into this mess... I was on my mac workstation and I had just pulled in a change set from another repo on a linux workstation after I had a made a bunch of moves. here's a bit of a log of what happened...
-
-
-<pre>
-jtang@x00:~/sources $ git pull cports-devel master
-Warning: untrusted X11 forwarding setup failed: xauth key data not generated
-Warning: No xauth data; using fake authentication data for X11 forwarding.
-remote: Counting objects: 4195, done.
-remote: Compressing objects: 100% (1135/1135), done.
-remote: Total 2582 (delta 866), reused 2576 (delta 860)
-Receiving objects: 100% (2582/2582), 229.42 KiB | 111 KiB/s, done.
-Resolving deltas: 100% (866/866), completed with 9 local objects.
-From cports-devel:/home/people/jtang/sources
- * branch            master     -> FETCH_HEAD
-Updating 319df99..ab0a98c
-error: Your local changes to the following files would be overwritten by merge:
-	.git-annex/09/5X/WORM-s361516678-m1301310614--l_fcompxe_intel64_2011.2.137.tgz.log
-	.git-annex/43/2g/WORM-s19509673-m1301310496--l_fcompxe_2011.2.137_redist.tgz.log
-	.git-annex/4J/qF/WORM-s18891115-m1301310934--w_flm_p_1.0.011_ia64.zip.log
-	.git-annex/87/w1/WORM-s12212473-m1301310909--w_flm_p_1.0.011_ia32.zip.log
-	.git-annex/99/Jq/WORM-s194345957-m1301310926--l_mkl_10.3.2.137_ia32.log
-	.git-annex/99/kf/WORM-s9784531-m1301311680--l_ccompxe_2011.2.137_redist.log
-	.git-annex/FF/f3/WORM-s93033394-m1301311706--l_gen_ipp_7.0.2.137.log
-	.git-annex/MF/xZ/WORM-s515140733-m1301310936--l_cprof_p_11.1.075.log
-	.git-annex/XW/X8/WORM-s355559731-m1301310797--l_mkl_10.3.2.137.log
-	.git-annex/fJ/mZ/WORM-s1372886477-m1301313368--l_cproc_p_11.1.075.log
-	.git-annex/j7/Q9/WORM-s44423202-m1301310622--l_cprof_p_11.1.075_redist.log
-	.git-annex/k4/K7/WORM-s239539070-m1301310760--l_mkl_10.3.2.137_intel64.log
-	.git-annex/kz/01/WORM-s279573314-m1301310783--l_cprof_p_11.1.075_ia32.log
-	.git-annex/p6/Kq/WORM-s31199343-m1301311829--l_cproc_p_11.1.075_redist.log
-	.git-annex/pz/J5/WORM-s626995277-m1301312301--l_ccompxe_ia32_2011.2.137.log
-	.git-annex/v3/kX/WORM-s339693045-m1301310851--l_cprof_p_11.1.075_intel64.log
-Please, commit your changes or stash them before you can merge.
-error: Your local changes to the following files would be overwritten by merge:
-	.git-annex/12/3W/WORM-s3058814-m1276699694--Botan-1.8.9.tgz.log
-	.git-annex/1G/qV/WORM-s9122-m1251558854--Array-Compare-2.01.tar.gz.log
-	.git-annex/3W/W5/WORM-s231523-m1270740744--DBD-Pg-2.17.1.tar.gz.log
-	.git-annex/3x/PX/WORM-s380310-m1293025187--HTSeq-0.4.7.tar.gz.log
-	.git-annex/45/gk/WORM-s67337-m1248732018--ExtUtils-Install-1.54.tar.gz.log
-	.git-annex/4J/7Q/WORM-s8608-m1224694862--Algorithm-Munkres-0.08.tar.gz.log
-	.git-annex/4g/XQ/WORM-s89208-m1278682033--HTML-Parser-3.66.tar.gz.log
-	.git-annex/54/jw/WORM-s300163-m1226422051--AcePerl-1.92.tar.gz.log
-	.git-annex/63/kj/WORM-s1213460-m1262942058--DBD-SQLite-1.29.tar.gz.log
-	.git-annex/6Z/42/WORM-s4074-m943766010--File-Sync-0.09.tar.gz.log
-	.git-annex/8F/M5/WORM-s6989-m1263161127--Digest-HMAC-1.02.tar.gz.log
-	.git-annex/G2/FK/WORM-s3309-m1163872981--Bundle-BioPerl-2.1.8.tar.gz.log
-	.git-annex/Gk/XF/WORM-s23572243-m1279546902--EMBOSS-6.3.1.tar.gz.log
-	.git-annex/Jk/X6/WORM-s566429-m1279309002--DBI-1.612.tar.gz.log
-	.git-annex/K6/fV/WORM-s1561451-m1240055295--Convert-Binary-C-0.74.tar.gz.log
-	.git-annex/KM/4q/WORM-s146959-m1268515086--Graph-0.94.tar.gz.log
-	.git-annex/MF/m2/WORM-s425766-m1212514609--Data-Stag-0.11.tar.gz.log
-	.git-annex/QJ/P6/WORM-s1045868-m1282215033--9base-6.tar.gz.log
-	.git-annex/Qm/WG/WORM-s39078-m1278163547--Digest-SHA1-2.13.tar.gz.log
-	.git-annex/Wq/Fj/WORM-s45680640-m1297862101--BclConverter-1.7.1.tar.log
-	.git-annex/Wq/Wm/WORM-s263536640-m1295025537--CASAVA_v1.7.0.tar.log
-	.git-annex/XW/qm/WORM-s36609-m1276050470--Bio-ASN1-EntrezGene-1.10-withoutworldwriteables.tar.gz.log
-	.git-annex/f7/g0/WORM-s40872-m1278273227--ExtUtils-ParseXS-2.2206.tar.gz.log
-	.git-annex/j3/JF/WORM-s11753-m1232427595--Clone-0.31.tar.gz.log
-	.git-annex/kX/9g/WORM-s84690-m1229117599--GraphViz-2.04.tar.gz.log
-	.git-annex/km/z5/WORM-s44634-m1275505134--Authen-SASL-2.15.tar.gz.log
-	.git-annex/kw/J3/WORM-s132396-m1278780649--DBD-mysql-4.016.tar.gz.log
-	.git-annex/p5/1P/WORM-s53736-m1278673485--Archive-Tar-1.64.tar.gz.log
-	.git-annex/wv/zG/WORM-s30584-m1268774021--ExtUtils-CBuilder-0.2703.tar.gz.log
-	.git-annex/x5/7v/WORM-s10462526-m1254242591--BioPerl-1.6.1.tar.gz.log
-Please, commit your changes or stash them before you can merge.
-error: The following untracked working tree files would be overwritten by merge:
-	.git-annex/1g/X3/WORM-s309910751-m1301311322--l_fcompxe_ia32_2011.2.137.tgz.log
-	.git-annex/3w/Xf/WORM-s805764902-m1301312756--l_cproc_p_11.1.075_intel64.log
-	.git-annex/9Q/Wz/WORM-s1234430253-m1301311891--l_ccompxe_2011.2.137.log
-	.git-annex/FQ/4z/WORM-s318168323-m1301310848--l_cprof_p_11.1.075_ia64.log
-	.git-annex/FV/0P/WORM-s710135470-m1301311835--l_ccompxe_intel64_2011.2.137.log
-	.git-annex/Jx/qM/WORM-s599386592-m1301310731--l_fcompxe_2011.2.137.tgz.log
-	.git-annex/KX/w1/WORM-s35976002-m1301312193--l_tbb_3.0.6.174.log
-	.git-annex/Vw/jK/WORM-s15795178-m1301310913--w_flm_p_1.0.011_intel64.zip.log
-	.git-annex/jK/zK/WORM-s374617670-m1301312705--l_ipp_7.0.2.137_intel64.log
-	.git-annex/vK/kv/WORM-s584342291-m1301312669--l_cproc_p_11.1.075_ia64.log
-	.git-annex/vw/v1/WORM-s736986678-m1301312794--l_cproc_p_11.1.075_ia32.log
-	.git-annex/zq/7X/WORM-s343075585-m1301312233--l_ipp_7.0.2.137_ia32.log
-Please move or remove them before you can merge.
-Aborting
-1|jtang@x00:~/sources $ git status
-# On branch master
-# Your branch is ahead of 'origin/master' by 2 commits.
-#
-# Changes to be committed:
-#   (use \"git reset HEAD <file>...\" to unstage)
-#
-#	modified:   .git-annex/09/5X/WORM-s361516678-m1301310614--l_fcompxe_intel64_2011.2.137.tgz.log
-#	modified:   .git-annex/43/2g/WORM-s19509673-m1301310496--l_fcompxe_2011.2.137_redist.tgz.log
-#	modified:   .git-annex/4J/qF/WORM-s18891115-m1301310934--w_flm_p_1.0.011_ia64.zip.log
-#	modified:   .git-annex/87/w1/WORM-s12212473-m1301310909--w_flm_p_1.0.011_ia32.zip.log
-#	modified:   .git-annex/99/Jq/WORM-s194345957-m1301310926--l_mkl_10.3.2.137_ia32.log
-#	modified:   .git-annex/99/kf/WORM-s9784531-m1301311680--l_ccompxe_2011.2.137_redist.log
-#	modified:   .git-annex/FF/f3/WORM-s93033394-m1301311706--l_gen_ipp_7.0.2.137.log
-#	modified:   .git-annex/MF/xZ/WORM-s515140733-m1301310936--l_cprof_p_11.1.075.log
-#	modified:   .git-annex/XW/X8/WORM-s355559731-m1301310797--l_mkl_10.3.2.137.log
-#	modified:   .git-annex/fJ/mZ/WORM-s1372886477-m1301313368--l_cproc_p_11.1.075.log
-#	modified:   .git-annex/j7/Q9/WORM-s44423202-m1301310622--l_cprof_p_11.1.075_redist.log
-#	modified:   .git-annex/k4/K7/WORM-s239539070-m1301310760--l_mkl_10.3.2.137_intel64.log
-#	modified:   .git-annex/kz/01/WORM-s279573314-m1301310783--l_cprof_p_11.1.075_ia32.log
-#	modified:   .git-annex/p6/Kq/WORM-s31199343-m1301311829--l_cproc_p_11.1.075_redist.log
-#	modified:   .git-annex/pz/J5/WORM-s626995277-m1301312301--l_ccompxe_ia32_2011.2.137.log
-#	modified:   .git-annex/v3/kX/WORM-s339693045-m1301310851--l_cprof_p_11.1.075_intel64.log
-#
-# Changes not staged for commit:
-#   (use \"git add <file>...\" to update what will be committed)
-#   (use \"git checkout -- <file>...\" to discard changes in working directory)
-#
-#	modified:   .git-annex/12/3W/WORM-s3058814-m1276699694--Botan-1.8.9.tgz.log
-#	modified:   .git-annex/1G/qV/WORM-s9122-m1251558854--Array-Compare-2.01.tar.gz.log
-#	modified:   .git-annex/3W/W5/WORM-s231523-m1270740744--DBD-Pg-2.17.1.tar.gz.log
-#	modified:   .git-annex/3x/PX/WORM-s380310-m1293025187--HTSeq-0.4.7.tar.gz.log
-#	modified:   .git-annex/45/gk/WORM-s67337-m1248732018--ExtUtils-Install-1.54.tar.gz.log
-#	modified:   .git-annex/4J/7Q/WORM-s8608-m1224694862--Algorithm-Munkres-0.08.tar.gz.log
-#	modified:   .git-annex/4g/XQ/WORM-s89208-m1278682033--HTML-Parser-3.66.tar.gz.log
-#	modified:   .git-annex/54/jw/WORM-s300163-m1226422051--AcePerl-1.92.tar.gz.log
-#	modified:   .git-annex/63/kj/WORM-s1213460-m1262942058--DBD-SQLite-1.29.tar.gz.log
-#	modified:   .git-annex/6Z/42/WORM-s4074-m943766010--File-Sync-0.09.tar.gz.log
-#	modified:   .git-annex/8F/M5/WORM-s6989-m1263161127--Digest-HMAC-1.02.tar.gz.log
-#	modified:   .git-annex/G2/FK/WORM-s3309-m1163872981--Bundle-BioPerl-2.1.8.tar.gz.log
-#	modified:   .git-annex/Gk/XF/WORM-s23572243-m1279546902--EMBOSS-6.3.1.tar.gz.log
-#	modified:   .git-annex/Jk/X6/WORM-s566429-m1279309002--DBI-1.612.tar.gz.log
-#	modified:   .git-annex/K6/fV/WORM-s1561451-m1240055295--Convert-Binary-C-0.74.tar.gz.log
-#	modified:   .git-annex/KM/4q/WORM-s146959-m1268515086--Graph-0.94.tar.gz.log
-#	modified:   .git-annex/MF/m2/WORM-s425766-m1212514609--Data-Stag-0.11.tar.gz.log
-#	modified:   .git-annex/QJ/P6/WORM-s1045868-m1282215033--9base-6.tar.gz.log
-#	modified:   .git-annex/Qm/WG/WORM-s39078-m1278163547--Digest-SHA1-2.13.tar.gz.log
-#	modified:   .git-annex/Wq/Fj/WORM-s45680640-m1297862101--BclConverter-1.7.1.tar.log
-#	modified:   .git-annex/Wq/Wm/WORM-s263536640-m1295025537--CASAVA_v1.7.0.tar.log
-#	modified:   .git-annex/XW/qm/WORM-s36609-m1276050470--Bio-ASN1-EntrezGene-1.10-withoutworldwriteables.tar.gz.log
-#	modified:   .git-annex/Zq/7X/WORM-s343075585-m1301312233--l_ipp_7.0.2.137_ia32.log
-#	modified:   .git-annex/f7/g0/WORM-s40872-m1278273227--ExtUtils-ParseXS-2.2206.tar.gz.log
-#	modified:   .git-annex/j3/JF/WORM-s11753-m1232427595--Clone-0.31.tar.gz.log
-#	modified:   .git-annex/kX/9g/WORM-s84690-m1229117599--GraphViz-2.04.tar.gz.log
-#	modified:   .git-annex/km/z5/WORM-s44634-m1275505134--Authen-SASL-2.15.tar.gz.log
-#	modified:   .git-annex/kw/J3/WORM-s132396-m1278780649--DBD-mysql-4.016.tar.gz.log
-#	modified:   .git-annex/p5/1P/WORM-s53736-m1278673485--Archive-Tar-1.64.tar.gz.log
-#	modified:   .git-annex/wv/zG/WORM-s30584-m1268774021--ExtUtils-CBuilder-0.2703.tar.gz.log
-#	modified:   .git-annex/x5/7v/WORM-s10462526-m1254242591--BioPerl-1.6.1.tar.gz.log
-#
-# Untracked files:
-#   (use \"git add <file>...\" to include in what will be committed)
-#
-#	.git-annex/1G/X3/
-#	.git-annex/3W/Xf/
-#	.git-annex/9q/Wz/
-#	.git-annex/Fq/4z/
-#	.git-annex/Jk/zK/
-#	.git-annex/Kx/w1/
-#	.git-annex/VK/kv/
-#	.git-annex/fv/0P/
-#	.git-annex/jX/qM/
-#	.git-annex/vW/jK/
-#	.git-annex/vW/v1/
-jtang@x00:~/sources $ git commit -a -m \"snap\"
-[master 45f254a] snap
- 47 files changed, 64 insertions(+), 30 deletions(-)
-jtang@x00:~/sources $ git status
-# On branch master
-# Your branch is ahead of 'origin/master' by 3 commits.
-#
-# Untracked files:
-#   (use \"git add <file>...\" to include in what will be committed)
-#
-#	.git-annex/1G/X3/
-#	.git-annex/3W/Xf/
-#	.git-annex/9q/Wz/
-#	.git-annex/Fq/4z/
-#	.git-annex/Jk/zK/
-#	.git-annex/Kx/w1/
-#	.git-annex/VK/kv/
-#	.git-annex/fv/0P/
-#	.git-annex/jX/qM/
-#	.git-annex/vW/jK/
-#	.git-annex/vW/v1/
-nothing added to commit but untracked files present (use \"git add\" to track)
-jtang@x00:~/sources $ git pull
-</pre>
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_3_a18ada7ac74c63be5753fdb2fe68dae5._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_3_a18ada7ac74c63be5753fdb2fe68dae5._comment
deleted file mode 100644
index 00988ab58..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_3_a18ada7ac74c63be5753fdb2fe68dae5._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 3"
- date="2011-03-28T15:25:18Z"
- content="""
-So, there is evidence here of a circumstance caused by the [[other_bug|git-annex_has_issues_with_git_when_staging__47__commiting_logs]], as I suspected.
-
-I don't think that manual `git commit -a` caused the problem. I suspect it was a subsequent `git add` that caused git to follow the wrong case paths and add the files in the wrong place. Ie, when you run \"git add .git-annex\", it recurses into `.git-annex/Gm/`, and adds files using that case, that were previously added from `.git-annex/GM/`.
-
-For completeness, can you verify this repo's core.ignorecase setting?
-
----
-
-I hate that you are stuck using loop filesystems to work around this bug. If my guess is correct, you don't need to, as long as you avoid manually running \"git add .git-annex\". I take this bug seriously. While I'm currently very involved in adding Amazon S3 support to git-annex (which will take days more of solid work), I do plan to make a loop filesystem of my own, probably vfat, so I can try and reproduce this on a case-insensative filesystem. If you could confirm my above hypothesis, that would speed things up for me.
-
-It's possible I will have to tweak the hash directories. Hopefully if so, I will only tweak them for *new* keys; if I had to do a v3 backend just to fix this stupid thing, I'd be sad -- upgrading all my offline disks from v1 to v2 took me many days.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_4_039e945617a6c1852c96974a402db29c._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_4_039e945617a6c1852c96974a402db29c._comment
deleted file mode 100644
index d045f7120..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_4_039e945617a6c1852c96974a402db29c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 4"
- date="2011-03-28T15:41:56Z"
- content="""
-In my \"sources\" repo on x00, the current setting is this \"ignorecase = true\" it was the first repo that I created before I clone it elsewhere and pull my changes back, it is on a HFS+ partition which is case insensitive and it is replicated on a portable hdd with a bare repo on a exfat partition. I wonder if my portable disk has a partially borked repo :P
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_5_eacd0b18475c05ab9feed8cf7290b79a._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_5_eacd0b18475c05ab9feed8cf7290b79a._comment
deleted file mode 100644
index 7127a6eef..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_5_eacd0b18475c05ab9feed8cf7290b79a._comment
+++ /dev/null
@@ -1,37 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 5"
- date="2011-03-28T15:51:11Z"
- content="""
-I also failed to mention, that in the case when i have stray log files after what has happened in comment 2, I get this left over after a commit when git is confused...
-
-
-<pre>
-jtang@x00:~/sources $ git status
-# On branch master
-# Your branch is ahead of 'origin/master' by 1 commit.
-#
-# Changes not staged for commit:
-#   (use \"git add <file>...\" to update what will be committed)
-#   (use \"git checkout -- <file>...\" to discard changes in working directory)
-#
-#	modified:   .git-annex/1G/X3/WORM-s309910751-m1301311322--l_fcompxe_ia32_2011.2.137.tgz.log
-#	modified:   .git-annex/3W/Xf/WORM-s805764902-m1301312756--l_cproc_p_11.1.075_intel64.log
-#	modified:   .git-annex/9Q/Wz/WORM-s1234430253-m1301311891--l_ccompxe_2011.2.137.log
-#	modified:   .git-annex/FQ/4z/WORM-s318168323-m1301310848--l_cprof_p_11.1.075_ia64.log
-#	modified:   .git-annex/FV/0P/WORM-s710135470-m1301311835--l_ccompxe_intel64_2011.2.137.log
-#	modified:   .git-annex/Jk/zK/WORM-s374617670-m1301312705--l_ipp_7.0.2.137_intel64.log
-#	modified:   .git-annex/Jx/qM/WORM-s599386592-m1301310731--l_fcompxe_2011.2.137.tgz.log
-#	modified:   .git-annex/KX/w1/WORM-s35976002-m1301312193--l_tbb_3.0.6.174.log
-#	modified:   .git-annex/VK/kv/WORM-s584342291-m1301312669--l_cproc_p_11.1.075_ia64.log
-#	modified:   .git-annex/Vw/jK/WORM-s15795178-m1301310913--w_flm_p_1.0.011_intel64.zip.log
-#	modified:   .git-annex/Zq/7X/WORM-s343075585-m1301312233--l_ipp_7.0.2.137_ia32.log
-#	modified:   .git-annex/vW/v1/WORM-s736986678-m1301312794--l_cproc_p_11.1.075_ia32.log
-#
-no changes added to commit (use \"git add\" and/or \"git commit -a\")
-</pre>
-
-
-Up until now I have just been updating the status of the staged files by hand and commiting it on my mac x00, this probably isn't helping. I'd rather not lose the tracking information.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_6_e55117cb628dc532e468519252571474._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_6_e55117cb628dc532e468519252571474._comment
deleted file mode 100644
index aae020972..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_6_e55117cb628dc532e468519252571474._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 6"
- date="2011-03-31T18:02:42Z"
- content="""
-Alright, I have created a case-insensative HFS+ filesystem here on my linux laptop. 
-
-I have not been able to trick git into staging the same file with 2 different capitalizations yet.
-
-It might be helpful if you can send me a copy of a git repository where 'git add -i' shows the same file staged with two capitalizations. Leaving out .git/annex of course. (joey@kitenet.net; a tarball would probably work)
-
-It seems that `git add` only started properly working on case insensative filesystems quite recently. The commit in question is 5e738ae820ec53c45895b029baa3a1f63e654b1b, \"Support case folding for git add when core.ignorecase=true\", which was first released in git 1.7.4, January 30, 2011. If you don't yet have that version, that could explain the problem entirely. In about half an hour (dialup!) I will have downloaded an older git and will see if I can reproduce the problem with it.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_7_0f4f471102e394ebb01da40e4d0fd9f6._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_7_0f4f471102e394ebb01da40e4d0fd9f6._comment
deleted file mode 100644
index 92b205bc3..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_7_0f4f471102e394ebb01da40e4d0fd9f6._comment
+++ /dev/null
@@ -1,68 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 7"
- date="2011-03-31T19:08:01Z"
- content="""
-git 1.7.4 does not make things better. With it, if I add first \"X/foo\" and then \"x/bar\", it commits \"X/bar\".
-
-That will *certainly* cause problems when interoperating with a repo clone on a case-sensative filesystem, since
-git-annex there will not see the location log that git committed to the wrong case directory.
-
-It's possible there is some interoperability problem when pulling from linux like you did, onto HFS+, too. I am not quite sure. Ah, I did find one.. if I clone the repo with \"X/foo\" in it to a case-sensative filesystem, and add a \"x/foo\" there,
-and pull that commit back to HFS+, git says:
-
-<pre>
- * branch            master     -> FETCH_HEAD
-Updating 8754149..e3d4640
-Fast-forward
- x/foo |    1 +
- 1 files changed, 1 insertions(+), 0 deletions(-)
- create mode 100644 x/foo
-joey@gnu:/mnt/r4>ls
-X/
-joey@gnu:/mnt/r4>git st
-# On branch master
-# Changes not staged for commit:
-#   (use \"git add <file>...\" to update what will be committed)
-#   (use \"git checkout -- <file>...\" to discard changes in working directory
-
-#	modified:   X/foo
-</pre>
-
-Aha -- that lets me reproduce your problem with the same file being staged twice with different capitalizations, too:
-
-<pre>
-joey@gnu:/mnt/r4>echo haaai >| x/foo
-joey@gnu:/mnt/r4>git st
-# On branch master
-# Changes not staged for commit:
-#   (use \"git add <file>...\" to update what will be committed)
-#   (use \"git checkout -- <file>...\" to discard changes in working directory)
-#
-#	modified:   X/bar
-#	modified:   X/foo
-#	modified:   x/foo
-#
-joey@gnu:/mnt/r4>git commit -a
-fatal: Will not add file alias 'X/Bar' ('x/Bar' already exists in index)
-</pre>
-
-And modified files that git refuses to commit, which entirely explains [[git-annex_has_issues_with_git_when_staging__47__commiting_logs]].
-
-<pre>
-joey@gnu:/mnt/r4>git add X/foo
-joey@gnu:/mnt/r4>git commit X/foo
-# On branch master
-# Changes not staged for commit:
-#   (use \"git add <file>...\" to update what will be committed)
-#   (use \"git checkout -- <file>...\" to discard changes in working directory)
-#
-#	modified:   X/bar
-#	modified:   X/foo
-#
-no changes added to commit (use \"git add\" and/or \"git commit -a\")
-</pre>
-
-I think git is frankly, buggy. It seems I will need to work around this by stopping using mixed case hashing for location logs.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_8_68e2d6ccdb9622b879e4bc7005804623._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_8_68e2d6ccdb9622b879e4bc7005804623._comment
deleted file mode 100644
index 05fe4658d..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_8_68e2d6ccdb9622b879e4bc7005804623._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 8"
- date="2011-03-31T19:28:02Z"
- content="""
-I've posted about this on the git mailing list. It's possible that these bugs, which can be shown to affect things other than just git-annex, will be fixed in git.
-
-I will wait a while to see. But am considering making git-annex use all-lowercase hash dirs for the log files. Maybe it could first look for .git-annex/aaaa/bbbb/foo.log, but also look for, read, and merge in any info from 
-.git-annex/Aa/Bb/foo.log. And always write to the new style filenames. This would avoid confusing git with changes to
-mixed-case files, and avoid another massive transition.
-"""]]
diff --git a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_9_45b11ddd200261115b653c7a14d28aa9._comment b/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_9_45b11ddd200261115b653c7a14d28aa9._comment
deleted file mode 100644
index 8dfe74642..000000000
--- a/doc/bugs/git-annex_directory_hashing_problems_on_osx/comment_9_45b11ddd200261115b653c7a14d28aa9._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 9"
- date="2011-03-31T21:32:10Z"
- content="""
-I'm was running git 1.7.4.1 at the time when I came across it, I have just upgraded to 1.7.4.2. I've also just moved to using a loopback fs for the stuff i care about. Do you still want a repo that exhibits the problem (excluding the .git/annex data) ??? I'm also not sure if 1.7.4.2 has corrected the problem yet as I haven't done much with my repos since. I suspect just making all the .git-annex hashed directories seems to be lower case might be better in the long run. 
-"""]]
diff --git a/doc/bugs/git-annex_doesn__39__t_list_files_containing_ISO8859-15_characters.mdwn b/doc/bugs/git-annex_doesn__39__t_list_files_containing_ISO8859-15_characters.mdwn
deleted file mode 100644
index 382ca9a0c..000000000
--- a/doc/bugs/git-annex_doesn__39__t_list_files_containing_ISO8859-15_characters.mdwn
+++ /dev/null
@@ -1,48 +0,0 @@
-<h4>What steps will reproduce the problem?</h4>
-<pre><code>    git init /tmp/test
-    cd /tmp/test
-    git annex init
-    touch òó ō
-    git annex add òó ō
-    git annex find --include='*'
-</code></pre>
-
-<h4>What is the expected output? What do you see instead?</h4>
-Only <tt>ō</tt> is listed. Files containing ISO8859-15 characters that are not in ASCII-7, such as <tt>òó</tt>, are not listed by
-<code>git annex find --include='*'</code>. On the other hand, <code>git annex find --in=here</code> lists both.
-
-<h4>What version of git-annex are you using? On what operating system?</h4>
-git-annex 4.20130227, on Debian GNU/Linux (sid, i386).
-
-<h4>Please provide any additional information below.</h4>
-<pre><code>    ~$ locale
-    LANG=en_US.UTF-8
-    LANGUAGE=en
-    LC_CTYPE="en_US.UTF-8"
-    LC_NUMERIC=C
-    LC_TIME=en_DK.UTF-8
-    LC_COLLATE="en_US.UTF-8"
-    LC_MONETARY="en_US.UTF-8"
-    LC_MESSAGES="en_US.UTF-8"
-    LC_PAPER=sv_SE.UTF-8
-    LC_NAME=sv_SE.UTF-8
-    LC_ADDRESS=sv_SE.UTF-8
-    LC_TELEPHONE=sv_SE.UTF-8
-    LC_MEASUREMENT=sv_SE.UTF-8
-    LC_IDENTIFICATION="en_US.UTF-8"
-    LC_ALL=
-</code></pre>
-
-> Tracked this back to a bug in either the C library or the haskell
-> regex-posix wrpaper around it. I'm not sure which, but I emailed the
-> maintainer of the haskell library. It just doesn't think these
-> things are characters; even `.` fails to match them! Everything should
-> match that...
-> 
-> There are apparently quite a lot of bugs on POSIX regex libraries
-> as implemented on different systems:
-> <http://www.haskell.org/haskellwiki/Regex_Posix>
-> 
-> It seemed best to jettison this dependency entirely; I've switched it to
-> haskell's pure regex-tdfa library, which works nicely. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/git-annex_doesn__39__t_list_files_containing_ISO8859-15_characters/comment_1_b84e831298c03b12471fb75da597e365._comment b/doc/bugs/git-annex_doesn__39__t_list_files_containing_ISO8859-15_characters/comment_1_b84e831298c03b12471fb75da597e365._comment
deleted file mode 100644
index 17d3d398a..000000000
--- a/doc/bugs/git-annex_doesn__39__t_list_files_containing_ISO8859-15_characters/comment_1_b84e831298c03b12471fb75da597e365._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.212"
- subject="comment 1"
- date="2013-03-08T20:09:02Z"
- content="""
-Wow, that was fast :-) Many thanks!
-"""]]
diff --git a/doc/bugs/git-annex_dropunused_has_no_effect.mdwn b/doc/bugs/git-annex_dropunused_has_no_effect.mdwn
deleted file mode 100644
index b9b159e3d..000000000
--- a/doc/bugs/git-annex_dropunused_has_no_effect.mdwn
+++ /dev/null
@@ -1,12 +0,0 @@
-Hi Joey,
-
-I have a repository with many thousands of unused files.  It's hard to know exactly how many because it takes up to 5 seconds to print the name of every single one, so I'm largely guessing based on my knowledge of what I've recently deleted.
-
-When I run `git annex dropunused FOO`, it doesn't matter what `FOO` is -- a number, a range, the word "foo" -- the `dropunused` command returns to the prompt instantly in all cases.
-
-What can I do to drop all these unused files eating up i-nodes?  Is there a debug flag I can turn on?
-
-Thanks,
-  John
-
-> added a message [[done]] --[[Joey]]
diff --git a/doc/bugs/git-annex_dropunused_has_no_effect/comment_1_66b581eb7111a9e98c6406ec75b899cf._comment b/doc/bugs/git-annex_dropunused_has_no_effect/comment_1_66b581eb7111a9e98c6406ec75b899cf._comment
deleted file mode 100644
index 0624eb27c..000000000
--- a/doc/bugs/git-annex_dropunused_has_no_effect/comment_1_66b581eb7111a9e98c6406ec75b899cf._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~arand"
- nickname="arand"
- subject="comment 1"
- date="2013-03-03T22:34:27Z"
- content="""
-Vhat kind of annex is this (direct/indirect, on what filesystem, etc.)?
-
-Also what version of git-annex?
-
-I know that direct mode didn't support dropunused, at least before, and on earlier versions of annex switching back to indirect after deleting things in direct didn't work either for dropunused, if I recall correctly.
-"""]]
diff --git a/doc/bugs/git-annex_dropunused_has_no_effect/comment_2_11c46cd2087511c3d22b7ce7c149b3e9._comment b/doc/bugs/git-annex_dropunused_has_no_effect/comment_2_11c46cd2087511c3d22b7ce7c149b3e9._comment
deleted file mode 100644
index 22a8a0c4f..000000000
--- a/doc/bugs/git-annex_dropunused_has_no_effect/comment_2_11c46cd2087511c3d22b7ce7c149b3e9._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 2"
- date="2013-03-03T22:43:41Z"
- content="""
-It's a ZFS filesystem, using indirect mode.  Here are my version numbers:
-
-    Vulcan:~/src/fpco $ git annex version
-    git-annex version: 4.20130227
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-"""]]
diff --git a/doc/bugs/git-annex_dropunused_has_no_effect/comment_3_b1c3d8c6ec4b20727aaa9c4b746531b0._comment b/doc/bugs/git-annex_dropunused_has_no_effect/comment_3_b1c3d8c6ec4b20727aaa9c4b746531b0._comment
deleted file mode 100644
index b1c2ce085..000000000
--- a/doc/bugs/git-annex_dropunused_has_no_effect/comment_3_b1c3d8c6ec4b20727aaa9c4b746531b0._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-03-03T23:56:17Z"
- content="""
-dropunused will do nothing if the number provided to drop is not listed in `.git/annex/unused`
-
-The file should be generated when you run `git annex unused`
-"""]]
diff --git a/doc/bugs/git-annex_dropunused_has_no_effect/comment_4_f05a9a3760858c5ee5c98dd8ab059c28._comment b/doc/bugs/git-annex_dropunused_has_no_effect/comment_4_f05a9a3760858c5ee5c98dd8ab059c28._comment
deleted file mode 100644
index 9e18696b1..000000000
--- a/doc/bugs/git-annex_dropunused_has_no_effect/comment_4_f05a9a3760858c5ee5c98dd8ab059c28._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="comment 4"
- date="2013-03-05T22:43:12Z"
- content="""
-Ah, thanks Joey, that explains it.  An error message to that effect would be great!
-"""]]
diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows.mdwn b/doc/bugs/git-annex_fails_to_initialize_under_Windows.mdwn
deleted file mode 100644
index 1d281f2ca..000000000
--- a/doc/bugs/git-annex_fails_to_initialize_under_Windows.mdwn
+++ /dev/null
@@ -1,215 +0,0 @@
-### Please describe the problem.
-Git-annex fails to initialize and fails tests.
-
-### What steps will reproduce the problem?
-Attempted initialization:
-
-    C:\Users\Andrew\Documents\GitHub\git-annex-test [master]> git annex init
-    init
-      Detected a filesystem without fifo support.
-
-      Disabling ssh connection caching.
-
-      Detected a crippled filesystem.
-
-      Enabling direct mode.
-    fatal: index file open failed: Invalid argument
-    git-annex: git [Param "checkout",Param "-q",Param "-B",Param "annex/direct/master"] failed
-
-Tests:
-
-    C:\Users\Andrew\Documents\GitHub\git-annex-test [master]> git annex test
-    Tests
-      QuickCheck
-        prop_idempotent_deencode_git:                     OK
-          +++ OK, passed 1000 tests.
-        prop_idempotent_deencode:                         OK
-          +++ OK, passed 1000 tests.
-        prop_idempotent_fileKey:                          OK
-          +++ OK, passed 1000 tests.
-        prop_idempotent_key_encode:                       OK
-          +++ OK, passed 1000 tests.
-        prop_idempotent_key_decode:                       OK
-          +++ OK, passed 1000 tests.
-        prop_idempotent_shellEscape:                      OK
-          +++ OK, passed 1000 tests.
-        prop_idempotent_shellEscape_multiword:            OK
-          +++ OK, passed 1000 tests.
-        prop_logs_sane:                                   OK
-          +++ OK, passed 1000 tests.
-        prop_idempotent_configEscape:                     OK
-          +++ OK, passed 1000 tests.
-        prop_parse_show_Config:                           OK
-          +++ OK, passed 1000 tests.
-        prop_parentDir_basics:                            OK
-          +++ OK, passed 1000 tests.
-        prop_relPathDirToFile_basics:                     OK
-          +++ OK, passed 1000 tests.
-        prop_relPathDirToFile_regressionTest:             OK
-          +++ OK, passed 1000 tests.
-        prop_cost_sane:                                   OK
-          +++ OK, passed 1000 tests.
-        prop_matcher_sane:                                OK
-          +++ OK, passed 1000 tests.
-        prop_HmacSha1WithCipher_sane:                     OK
-          +++ OK, passed 1000 tests.
-        prop_TimeStamp_sane:                              OK
-          +++ OK, passed 1000 tests.
-        prop_addLog_sane:                                 OK
-          +++ OK, passed 1000 tests.
-        prop_verifiable_sane:                             OK
-          +++ OK, passed 1000 tests.
-        prop_segment_regressionTest:                      OK
-          +++ OK, passed 1000 tests.
-        prop_read_write_transferinfo:                     OK
-          +++ OK, passed 1000 tests.
-        prop_read_show_inodecache:                        OK
-          +++ OK, passed 1000 tests.
-        prop_parse_show_log:                              OK
-          +++ OK, passed 1000 tests.
-        prop_read_show_TrustLevel:                        OK
-          +++ OK, passed 1000 tests.
-        prop_parse_show_TrustLog:                         OK
-          +++ OK, passed 1000 tests.
-        prop_hashes_stable:                               OK
-          +++ OK, passed 1000 tests.
-        prop_schedule_roundtrips:                         OK
-          +++ OK, passed 1000 tests.
-        prop_duration_roundtrips:                         OK
-          +++ OK, passed 1000 tests.
-        prop_metadata_sane:                               OK
-          +++ OK, passed 1000 tests.
-        prop_metadata_serialize:                          OK
-          +++ OK, passed 1000 tests.
-        prop_branchView_legal:                            OK
-          +++ OK, passed 1000 tests.
-        prop_view_roundtrips:                             OK
-          +++ OK, passed 1000 tests.
-        prop_viewedFile_rountrips:                    I n i t  TOeKs
-    ts
-          i n+i+t+:  OK, passed 1000 tests.
-      Unit Tests
-        add sha1dup:                                      git-annex: System.PosixCompat.User.getEffectiveUserID: not support
-    ed: illegal operation
-    FAIL
-        init failed
-      add:  git-annex: System.PosixCompat.User.getEffectiveUserID: not supported: illegal operation
-    FAIL
-        add failed
-
-    2 out of 2 tests failed
-    FAIL
-          Exception: init tests failed! cannot continue
-        add extras:                                       FAIL
-          Exception: init tests failed! cannot continue
-        reinject:                                         FAIL
-          Exception: init tests failed! cannot continue
-        unannex (no copy):                                FAIL
-          Exception: init tests failed! cannot continue
-        unannex (with copy):                              FAIL
-          Exception: init tests failed! cannot continue
-        drop (no remote):                                 FAIL
-          Exception: init tests failed! cannot continue
-        drop (with remote):                               FAIL
-          Exception: init tests failed! cannot continue
-        drop (untrusted remote):                          FAIL
-          Exception: init tests failed! cannot continue
-        get:                                              FAIL
-          Exception: init tests failed! cannot continue
-        move:                                             FAIL
-          Exception: init tests failed! cannot continue
-        copy:                                             FAIL
-          Exception: init tests failed! cannot continue
-        lock:                                             FAIL
-          Exception: init tests failed! cannot continue
-        edit (no pre-commit):                             FAIL
-          Exception: init tests failed! cannot continue
-        edit (pre-commit):                                FAIL
-          Exception: init tests failed! cannot continue
-        fix:                                              FAIL
-          Exception: init tests failed! cannot continue
-        trust:                                            FAIL
-          Exception: init tests failed! cannot continue
-        fsck (basics):                                    FAIL
-          Exception: init tests failed! cannot continue
-        fsck (bare):                                      FAIL
-          Exception: init tests failed! cannot continue
-        fsck (local untrusted):                           FAIL
-          Exception: init tests failed! cannot continue
-        fsck (remote untrusted):                          FAIL
-          Exception: init tests failed! cannot continue
-        migrate:                                          FAIL
-          Exception: init tests failed! cannot continue
-        migrate (via gitattributes):                      FAIL
-          Exception: init tests failed! cannot continue
-         unused:                                          FAIL
-          Exception: init tests failed! cannot continue
-        describe:                                         FAIL
-          Exception: init tests failed! cannot continue
-        find:                                             FAIL
-          Exception: init tests failed! cannot continue
-        merge:                                            FAIL
-          Exception: init tests failed! cannot continue
-        info:                                             FAIL
-          Exception: init tests failed! cannot continue
-        version:                                          FAIL
-          Exception: init tests failed! cannot continue
-        sync:                                             FAIL
-          Exception: init tests failed! cannot continue
-        union merge regression:                           FAIL
-          Exception: init tests failed! cannot continue
-        conflict resolution:                              FAIL
-          Exception: init tests failed! cannot continue
-        conflict_resolution (mixed directory and file):   FAIL
-          Exception: init tests failed! cannot continue
-        conflict_resolution (mixed directory and file) 2: FAIL
-          Exception: init tests failed! cannot continue
-        map:                                              FAIL
-          Exception: init tests failed! cannot continue
-        uninit:                                           FAIL
-          Exception: init tests failed! cannot continue
-        uninit (in git-annex branch):                     FAIL
-          Exception: init tests failed! cannot continue
-        upgrade:                                          FAIL
-          Exception: init tests failed! cannot continue
-        whereis:                                          FAIL
-          Exception: init tests failed! cannot continue
-        hook remote:                                      FAIL
-          Exception: init tests failed! cannot continue
-        directory remote:                                 FAIL
-          Exception: init tests failed! cannot continue
-        rsync remote:                                     FAIL
-          Exception: init tests failed! cannot continue
-        bup remote:                                       FAIL
-          Exception: init tests failed! cannot continue
-        crypto:                                           FAIL
-          Exception: init tests failed! cannot continue
-        preferred content:                                FAIL
-          Exception: init tests failed! cannot continue
-        add subdirs:                                      FAIL
-          Exception: init tests failed! cannot continue
-    
-    45 out of 78 tests failed
-      (This could be due to a bug in git-annex, or an incompatability
-       with utilities, such as git, installed on this system.)
-
-### What version of git-annex are you using? On what operating system?
-    C:\Users\Andrew\Documents\GitHub\git-annex-test [master]> git --version
-    git version 1.8.4.msysgit.0
-    C:\Users\Andrew\Documents\GitHub\git-annex-test [master]> git annex version
-    git-annex version: 5.20140227-gd872677
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256
-    SKEIN512 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external
-    local repository version: 5
-    supported repository version: 5
-    upgrade supported from repository versions: 2 3 4
-    C:\Users\Andrew\Documents\GitHub\git-annex-test [master]> (Get-WmiObject -class Win32_OperatingSystem).Caption
-    Microsoft Windows 8.1
-
-### Please provide any additional information below.
-^^^ See above
-
-> [[done]]; I have made the windows documentation document the need for
-> msysgit 1.9. --[[Joey]]
diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_1_082277b9b906a2cc0fcace6790f5cfad._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_1_082277b9b906a2cc0fcace6790f5cfad._comment
deleted file mode 100644
index 781528bcb..000000000
--- a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_1_082277b9b906a2cc0fcace6790f5cfad._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.41"
- subject="comment 1"
- date="2014-03-26T20:50:55Z"
- content="""
-That's a fairly old version of git-annex, so you could try upgrading.
-
-This might happen if your shell environment you're using to run git-annex does not have either USERPROFILE or HOME envorironment variable set, or does not have one of USERNAME, USER, and LOGNAME set.
-"""]]
diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_2_b9a3a0104bc56f9110fc58c9df140f12._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_2_b9a3a0104bc56f9110fc58c9df140f12._comment
deleted file mode 100644
index 1fcfc5a51..000000000
--- a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_2_b9a3a0104bc56f9110fc58c9df140f12._comment
+++ /dev/null
@@ -1,34 +0,0 @@
-[[!comment format=mdwn
- username="ayutheos"
- ip="49.124.177.13"
- subject="comment 2"
- date="2014-04-10T07:52:36Z"
- content="""
-I'm getting this error too. 
-
-    user@NOTEBOOK /d/pictures
-    $ git annex init \"photos\"
-    init photos
-      Detected a filesystem without fifo support.
-
-      Disabling ssh connection caching.
-
-      Detected a crippled filesystem.
-
-      Enabling direct mode.
-    fatal: index file open failed: Invalid argument
-    git-annex: git [Param \"checkout\",Param \"-q\",Param \"-B\",Param \"annex/direct/master\"] failed
-
-git-annex version:
-
-    user@NOTEBOOK /d/pictures
-    $ git annex version
-    git-annex version: 5.20140403-gdfa17fc
-    build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external
-    local repository version: 5
-    supported repository version: 5
-    upgrade supported from repository versions: 2 3 4
-
-"""]]
diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_3_7aeeccd6c4bd97224980a2752e0f8ba8._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_3_7aeeccd6c4bd97224980a2752e0f8ba8._comment
deleted file mode 100644
index aa4d513f8..000000000
--- a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_3_7aeeccd6c4bd97224980a2752e0f8ba8._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.191"
- subject="comment 3"
- date="2014-04-17T21:08:36Z"
- content="""
-@ayutheos, can you confirm that running this git command fails the same way?
-
-git checkout -B annex/direct/master
-
-What version of git do you have installed?
-
-(Note to self: This checkout happens when enabling direct mode.. Works for me in a new git repo made on FAT. This repo does not have a .git/index file, and the error message \"fatal: index file open failed: Invalid argument\" comes from git when it tries to read the index file.)
-"""]]
diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_4_12b6ed59c8b7ded6b6b9150b32e58ce4._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_4_12b6ed59c8b7ded6b6b9150b32e58ce4._comment
deleted file mode 100644
index 5ba16a0cb..000000000
--- a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_4_12b6ed59c8b7ded6b6b9150b32e58ce4._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="ayutheos"
- ip="49.125.229.80"
- subject="comment 4"
- date="2014-04-19T03:13:17Z"
- content="""
-I'm using git version 1.8.4.msysgit.0 on Windows 7 64-bit.
-
-I took a screenshot of git annex init command at [[http://i.imgur.com/YV9vean.png]]
-
-I deleted both the .git and .t folders before re-trying to initialise git annex. However when initialising git annex the 2nd time, folder .t was not created.
-
-Folder `D:\pictures` is an existing folder.
-
-
-
-"""]]
diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_5_f975059733fca678e93b791b2a250535._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_5_f975059733fca678e93b791b2a250535._comment
deleted file mode 100644
index 319cb3617..000000000
--- a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_5_f975059733fca678e93b791b2a250535._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.191"
- subject="comment 5"
- date="2014-04-20T18:35:39Z"
- content="""
-You might want to try upgrading to msysgit 1.9.0, which is the one I am using for windows development.
-
-So, your screenshot shows that git checkout -B annex/direct/master worked ok when you ran it, but then when git-annex init failed, it was running
-the same command, only with a -q also. The -q is only quiet mode, shouldn't matter.
-
-(The .t folder is created when running git-annex test, so not relevant.)
-"""]]
diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_6_66cfbb5ce75d322f68b4c41f11bb15ae._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_6_66cfbb5ce75d322f68b4c41f11bb15ae._comment
deleted file mode 100644
index 4f53e02d5..000000000
--- a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_6_66cfbb5ce75d322f68b4c41f11bb15ae._comment
+++ /dev/null
@@ -1,59 +0,0 @@
-[[!comment format=mdwn
- username="ayutheos"
- ip="49.124.129.253"
- subject="comment 6"
- date="2014-04-23T08:56:58Z"
- content="""
-I upgraded git to 1.9.0.msysgit.0, and managed to initialise git-annex:
-
-    user@NOTEBOOK /d/pictures
-    $ git init
-    Initialized empty Git repository in D:/pictures/.git/
-    
-    user@NOTEBOOK /d/pictures
-    $ git annex init \"laptop photos\"
-    init laptop photos
-      Detected a filesystem without fifo support.
-    
-      Disabling ssh connection caching.
-    
-      Detected a crippled filesystem.
-    
-      Enabling direct mode.
-    ok
-    (Recording state in git...)
-
-But there's a message that it detected a crippled filesystem? What does that mean?
-
-Running `git status` gives:
-
-    user@NOTEBOOK /d/pictures
-    $ git st
-    fatal: This operation must be run in a work tree
-
-And then I run `git init`
-
-    user@NOTEBOOK /d/pictures
-    $ git init
-    Reinitialized existing Git repository in D:/pictures/.git/
-    
-    user@NOTEBOOK /d/pictures
-    $ git st
-    On branch annex/direct/master
-    
-    Initial commit
-    
-    Untracked files:
-      (use \"git add <file>...\" to include in what will be committed)
-    
-            2011/
-            2012/
-            2013/
-            2014/
-            dump/
-            to burn/
-    
-    nothing added to commit but untracked files present (use \"git add\" to track)
-
-..and git works ok. Any suggestions what might be wrong?
-"""]]
diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_7_9195b2373b0c5298ebbe309414d26ee4._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_7_9195b2373b0c5298ebbe309414d26ee4._comment
deleted file mode 100644
index 8a53a8acb..000000000
--- a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_7_9195b2373b0c5298ebbe309414d26ee4._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 7"
- date="2014-04-23T17:47:59Z"
- content="""
-Ok, I am tempted to close this bug if it only happens with an older version of msysgit. It really is looking like a bug in git, or in the msysgit port.
-
-The \"crippled filesystem\" is normal on Windows. git-annex does not try to use symblic links on Windows, and so is limited to working in [[direct_mode]].
-"""]]
diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_8_bf3f1e801bee930673907d9a8eb4c147._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_8_bf3f1e801bee930673907d9a8eb4c147._comment
deleted file mode 100644
index 3228d7bf5..000000000
--- a/doc/bugs/git-annex_fails_to_initialize_under_Windows/comment_8_bf3f1e801bee930673907d9a8eb4c147._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="Clément"
- ip="95.211.55.195"
- subject="comment 8"
- date="2014-05-02T10:29:20Z"
- content="""
-I can confirm that the error got away when I upgraded to msysgit 1.9 !
-"""]]
diff --git a/doc/bugs/git-annex_fix_not_noticing_file_renames.mdwn b/doc/bugs/git-annex_fix_not_noticing_file_renames.mdwn
deleted file mode 100644
index a68533980..000000000
--- a/doc/bugs/git-annex_fix_not_noticing_file_renames.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-What steps will reproduce the problem?
-
-    ~$ mkdir testannex
-    ~$ cd testannex/
-    testannex$ git init
-    Initialized empty Git repository in /Users/ed/testannex/.git/
-    testannex$ git annex init "test annex"
-    init test annex ok
-    (Recording state in git...)
-    testannex$ echo "file1" > file1
-    testannex$ git annex add file1
-    add file1 (checksum...) ok
-    (Recording state in git...)
-    testannex$ mkdir directory
-    testannex$ mv file1 directory/
-    testannex$ cat directory/file1 
-    cat: directory/file1: No such file or directory
-    testannex$ git annex fix directory/file1
-    git-annex: directory/file1 not found
-
-
-What is the expected output? What do you see instead?
-
-    git annex fix should fix the symlink.  It looks like maybe it's *following* the symlink?
-
-What version of git-annex are you using? On what operating system?
-
-    checkout:  20d195f   compiled on OS X 10.7 using cabal.  
-
-Please provide any additional information below.
-
-    git annex assistant is not noticing file renames either.
-
-> git-annex commands (other than `git annex add`) only operate on files
-> checked into git, which `directory/file1` is not, since you did not use
-> `git mv`. Once you `git add` the file, it'll work. [[done]] --[[Joey]]
diff --git a/doc/bugs/git-annex_fix_not_noticing_file_renames/comment_1_4edd95200d59ec5a5426167b8da8e3f9._comment b/doc/bugs/git-annex_fix_not_noticing_file_renames/comment_1_4edd95200d59ec5a5426167b8da8e3f9._comment
deleted file mode 100644
index 589dfbf06..000000000
--- a/doc/bugs/git-annex_fix_not_noticing_file_renames/comment_1_4edd95200d59ec5a5426167b8da8e3f9._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 1"
- date="2012-12-13T20:14:37Z"
- content="""
-Thanks for the response!  It's good to know how it works right now.
-
-The reason I was expecting it to work on the files even if I moved them without git rename, is this:
-
-Imaginary use case:
-
-I am using git annex assistant, and not using the command line at all.  Maybe I don't know anything about git.  I am on a machine in the \"client\" group, so it drops content in \"archive\" subdirectories after storing it safely in a repository in the \"backup\" group.
-
-To add content to git annex, I drag and drop it into the git annex directory.  Assistant notices, and it gets added to the annex (it is now a symlink).  Yay!
-
-To archive content, I drag and drop the file (its symlink actually) from the git annex directory to an annex/archive directory, assistant notices, and it gets moved off to backup directories, and this symlink becomes dead.  This doesn't work because git annex assistant doesn't notice renames.
-
-To retrieve content from an archive, I drag and drop the dead link in the archive directory to a parent directory, and git annex notices and grabs the content from a backup somewhere.  This doesn't work, because git annex assistant doesn't notice renames.
-
-These kinds of operations are necessary if I'm going to archive and unarchive files, or otherwise move and manage them, while the assistant is running, without using git from the command line.
-
-
-"""]]
diff --git a/doc/bugs/git-annex_fix_not_noticing_file_renames/comment_2_a9a44debefb3bdd4b8ed2d1cf53f2338._comment b/doc/bugs/git-annex_fix_not_noticing_file_renames/comment_2_a9a44debefb3bdd4b8ed2d1cf53f2338._comment
deleted file mode 100644
index 33f05eac7..000000000
--- a/doc/bugs/git-annex_fix_not_noticing_file_renames/comment_2_a9a44debefb3bdd4b8ed2d1cf53f2338._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.117"
- subject="comment 2"
- date="2012-12-13T20:24:32Z"
- content="""
-The assistant does notice renames, and also automatically fixes links.
-"""]]
diff --git a/doc/bugs/git-annex_fix_not_noticing_file_renames/comment_3_0efb11f35b872b75a3fbc4ebb71ac827._comment b/doc/bugs/git-annex_fix_not_noticing_file_renames/comment_3_0efb11f35b872b75a3fbc4ebb71ac827._comment
deleted file mode 100644
index 75c02dda1..000000000
--- a/doc/bugs/git-annex_fix_not_noticing_file_renames/comment_3_0efb11f35b872b75a3fbc4ebb71ac827._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 3"
- date="2012-12-13T20:39:57Z"
- content="""
-The assistant doesn't seem to be noticing renames or fixing files anymore, for me; that was what got me started on this bug report, though it sounds like I took it in an irrelevant direction by focusing on the command line and \"git annex fix.\"
-
-I'll double check, and submit a new bug report if I can confirm that assistant isn't doing what it should.
-"""]]
diff --git a/doc/bugs/git-annex_get:_requested_key_is_not_present.mdwn b/doc/bugs/git-annex_get:_requested_key_is_not_present.mdwn
deleted file mode 100644
index f4c5b3d09..000000000
--- a/doc/bugs/git-annex_get:_requested_key_is_not_present.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-### Please describe the problem.
-
-I setup 3 repositories on my laptop and 3 on my server using the webapp, see the following scheme:
-
-Laptop <- sync with -> Server
-
-    /home/fabian/Dokumente (Client) <-> /mnt/raid/Dokumente (Full-Backup)
-    /home/fabian/Bilder (Client)    <-> /mnt/raid/Bilder (Full-Backup)
-    /mnt/data-common/Audio (Manual) <-> /mnt/raid/Audio (Full-Backup)
-
-As you can see, the Audio folder is in manual mode on the laptop, so it does not get any files automatically.
-If I now want to get a folder with 'git-annex get' I get the following error:
-
-    fabian@fabian-thinkpad /mnt/data-common/Audio $ git-annex get Musik
-    get Musik/+⁄-/2003 - You Are Here (Bonus Disc)/01 - I've Been Lost.ogg (from eifel.fritz.box__mnt_raid_Audio...) 
-      requested key is not present
-    rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
-    rsync error: error in rsync protocol data stream (code 12) at io.c(605) [Receiver=3.0.9]
-
-      Unable to access these remotes: eifel.fritz.box__mnt_raid_Audio
-    
-      Try making some of these repositories available:
-      	efe13d8c-2b02-455f-9874-b7043caa332f -- eifel.fritz.box__mnt_raid_Audio (fabian@eifel:/mnt/raid/Audio)
-    failed
-
-### What steps will reproduce the problem?
-
-I do not really know the minimal setup to reproduce this problem.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex 4.20130417 on Gentoo Linux using Ebuilds from Haskell overlay
-
-> I suspect this was some kind of misconfiguration, or 
-> one of the kinds of data corruption that git-annex can automatically heal from. 
-> 
-> I am pretty sure I didn't make any changes to git-annex that caused
-> the problem to stop happening!
-> 
-> While it would be very good to get to the bottom of this, I don't see
-> any benefit to keeping this report open without more info. [[done]] --[[Joey]]
diff --git a/doc/bugs/git-annex_get:_requested_key_is_not_present/comment_1_d4baa6607a61d0e6a7cea1325a5ddf95._comment b/doc/bugs/git-annex_get:_requested_key_is_not_present/comment_1_d4baa6607a61d0e6a7cea1325a5ddf95._comment
deleted file mode 100644
index 70c3f77d0..000000000
--- a/doc/bugs/git-annex_get:_requested_key_is_not_present/comment_1_d4baa6607a61d0e6a7cea1325a5ddf95._comment
+++ /dev/null
@@ -1,26 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-27T19:54:42Z"
- content="""
-This error message means that the file's content is not present on your server. 
-
-It seems like git-annex *thinks* the file is there, so it sent it there. But something appears to have happened to it.
-
-You can investigate like this:
-
-* Get the file's key, by running `basename $(git cat-file p 'HEAD:Musik/+⁄-/2003 - You Are Here (Bonus Disc)/01 - I've Been Lost.ogg')`
-* Run `find` in /mnt/raid/Audio on the server, and grep for that key.
-
-If that finds any files, we may have a git-annex bug of some kind.
-
-If it finds an empty directory, that's an indication that the file's content was sent to the server before, but has now somehow gotten deleted.
-
-----
-
-You may also want to run, on the client: `git annex fsck --fast --from eifel.fritz.box__mnt_raid_Audio`  
-That will check that all the files it thinks should be on the server are still there. If it says \"fixing location log\",
-then it's found other files that were expected to be on the server but don't seem to be any longer.
-
-"""]]
diff --git a/doc/bugs/git-annex_get:_requested_key_is_not_present/comment_2_b49725488c3db5e00ede7b65ed9d62fa._comment b/doc/bugs/git-annex_get:_requested_key_is_not_present/comment_2_b49725488c3db5e00ede7b65ed9d62fa._comment
deleted file mode 100644
index 46a488c20..000000000
--- a/doc/bugs/git-annex_get:_requested_key_is_not_present/comment_2_b49725488c3db5e00ede7b65ed9d62fa._comment
+++ /dev/null
@@ -1,110 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~maestro-alubia"
- nickname="maestro-alubia"
- subject="comment 2"
- date="2013-04-29T21:04:30Z"
- content="""
-Thanks for explaining the error message.
-
-I did some investigation but I am not really understanding what is going on.
-
-But step by step, lets take a file without any confusing characters in filename (e.g. '/'), so we use the file \".directory\".
-
-1.) I run on the client:
-[[!format sh \"\"\"
-fabian@fabian-thinkpad /mnt/data-common/Audio $ ls -la .directory 
-lrwxrwxrwx 1 fabian fabian 180 25. Apr 17:15 .directory -> .git/annex/objects/Ff/m9/SHA256E-s91--378daa8e2a232ae5a04d9f6c83003d8ccfe6c8b7547c1789a130ba94017283ed/SHA256E-s91--378daa8e2a232ae5a04d9f6c83003d8ccfe6c8b7547c1789a130ba94017283ed
-fabian@fabian-thinkpad /mnt/data-common/Audio $ basename $(git cat-file -p \"HEAD:.directory\")
-SHA256E-s91--378daa8e2a232ae5a04d9f6c83003d8ccfe6c8b7547c1789a130ba94017283ed
-\"\"\"]]
-
-2.) I run on the server:
-
-[[!format sh \"\"\"
-fabian@eifel:/mnt/raid/Audio$ ls -la .directory 
--rw----r-x 1 fabian fabian 91 Dez 13 17:35 .directory
-fabian@eifel:/mnt/raid/Audio$ basename $(git cat-file -p \"HEAD:.directory\")
-SHA256E-s91--378daa8e2a232ae5a04d9f6c83003d8ccfe6c8b7547c1789a130ba94017283ed
-fabian@eifel:/mnt/raid/Audio$ git-annex fsck .directory 
-fsck .directory (checksum...) ok
-\"\"\"]]
-
-So obviously the file is present on the server (it is using direct mode).
-
-3.) On the client again:
-
-[[!format sh \"\"\"
-fabian@fabian-thinkpad /mnt/data-common/Audio $ git-annex get .directory 
-get .directory (from eifel.fritz.box__mnt_raid_Audio...) 
-  requested key is not present
-rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
-rsync error: error in rsync protocol data stream (code 12) at io.c(605) [Receiver=3.0.9]
-
-  Unable to access these remotes: eifel.fritz.box__mnt_raid_Audio
-
-  Try making some of these repositories available:
-  	efe13d8c-2b02-455f-9874-b7043caa332f -- eifel.fritz.box__mnt_raid_Audio (fabian@eifel:/mnt/raid/Audio)
-failed
-git-annex: get: 1 failed
-fsck .directory (checking eifel.fritz.box__mnt_raid_Audio...) (fixing location log) 
-  ** Based on the location log, .directory
-  ** was expected to be present, but its content is missing.
-
-  ** No known copies exist of .directory
-failed
-(Recording state in git...)
-git-annex: fsck: 1 failed
-fabian@fabian-thinkpad /mnt/data-common/Audio $ git-annex get .directory 
-get .directory (not available) 
-  No other repository is known to contain the file.
-failed
-git-annex: get: 1 failed
-\"\"\"]]
-
-Also running \"git annex sync\" on both sides does not help.
-
-This is the configuration:
-
-Client:
-[[!format sh \"\"\"
-fabian@fabian-thinkpad /mnt/data-common/Audio $ cat .git/config 
-[core]
-	repositoryformatversion = 0
-	filemode = true
-	bare = false
-	logallrefupdates = true
-[annex]
-	uuid = a1f816fe-3fce-4887-a85c-b7b9e501a5d7
-	version = 3
-[remote \"eifel.fritz.box__mnt_raid_Audio\"]
-	url = ssh://fabian@git-annex-eifel.fritz.box-fabian_mntraidAudio/mnt/raid/Audio/
-	fetch = +refs/heads/*:refs/remotes/eifel.fritz.box__mnt_raid_Audio/*
-	annex-uuid = efe13d8c-2b02-455f-9874-b7043caa332f
-	annex-cost = 175.0
-\"\"\"]]
-
-Server:
-[[!format sh \"\"\"
-fabian@eifel:/mnt/raid/Audio$ cat .git/config 
-[core]
-	repositoryformatversion = 0
-	filemode = true
-	bare = false
-	logallrefupdates = true
-[annex]
-	uuid = efe13d8c-2b02-455f-9874-b7043caa332f
-	version = 3
-	direct = true
-[gc]
-	auto = 0
-[remote \"fabianthinkpad.fritz.box__mnt_datacommon_Audio\"]
-	url = ssh://fabian@git-annex-fabian-thinkpad.fritz.box-fabian_mntdatacommonAudio/mnt/data-common/Audio/
-	fetch = +refs/heads/*:refs/remotes/fabianthinkpad.fritz.box__mnt_datacommon_Audio/*
-	annex-uuid = a1f816fe-3fce-4887-a85c-b7b9e501a5d7
-	annex-cost = 175.0
-\"\"\"]]
-
-Please let me know if you need more information.
-
-Btw: I sent some money to my flattr account so I can support you soon. Thanks again for your work!
-"""]]
diff --git a/doc/bugs/git-annex_get:_requested_key_is_not_present/comment_3_c17a7138579b93c6f14e3444c11664ac._comment b/doc/bugs/git-annex_get:_requested_key_is_not_present/comment_3_c17a7138579b93c6f14e3444c11664ac._comment
deleted file mode 100644
index b43e2fbdc..000000000
--- a/doc/bugs/git-annex_get:_requested_key_is_not_present/comment_3_c17a7138579b93c6f14e3444c11664ac._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~maestro-alubia"
- nickname="maestro-alubia"
- subject="Fixed"
- date="2013-06-30T11:50:42Z"
- content="""
-The bug seems to be fixed in recent versions of git-annex (tested with 4.20130601 on \"client\" and 4.20130621 on \"server\"). Everything is now working as expected. Thank you very much for your work!
-"""]]
diff --git a/doc/bugs/git-annex_has_issues_with_git_when_staging__47__commiting_logs.mdwn b/doc/bugs/git-annex_has_issues_with_git_when_staging__47__commiting_logs.mdwn
deleted file mode 100644
index ed629c424..000000000
--- a/doc/bugs/git-annex_has_issues_with_git_when_staging__47__commiting_logs.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-After a series of pretty convoluted copying files around between annex'd repos and pulling changes around between repos. I noticed that occassionally when git-annex tries to stage files (the `.git-annex/*/*/*logs`) git some times gets wedged and doing a "git commit -a" doesn't seem to work or files might not get added thus leaving a bunch of untracked files or modified files that aren't staged for a commit.
-
-I tried running a *`git rm --cached -f -r *`* then *git add -u .git-annex/* or the usual *git add* then a commit fixes things for me. If I don't do that then my subsequent merges/pulls will fail and result in *no known copies of files* I suspect git-annex might have just touched some file modes and git picked up the changes but got confused since there was no content change. It might also just be a git on OSX thing and it doesn't affect linux/bsd users.
-
-For now it's just a bit of extra work for me when it does occur but it does not seem to occur often.
-
-> What do you mean when you say that git "got wedged"? It hung somehow?
->
-> If git-annex runs concurrently with another git command that locks
-> the repository, its git add of log files can fail.
-> 
-> Update: Also, of course, if you are running a "got annex get" or
-> similar, and ctrl-c it after it has gotten some files, it can
-> end up with unstaged or in some cases un-added log files that git-annex
-> wrote -- since git-annex only stages log files in git on shutdown, and
-> ctrl-c bypasses that.
-> --[[Joey]] 
-
->> It "got wedged" as in git doesn't let me commit anything, even though it tells me that there is stuff to be committed in the staging area.
-
->>> I've never seen git refuse to commit staged files. There would have to
->>> be some error message? --[[Joey]] 
-
->>>> there were no error messages at all
-
->>>>> Can I see a transcript? I'm having difficulty getting my head around
->>>>> what git is doing. Sounds like the files could just not be `git
->>>>> added` yet, but I get the impression from other things that you say
->>>>> that it's not so simple. --[[Joey]] 
-
-This turns out to be a bug in git, and I have posted a bug report on the mailing list.
-The git-annex behavior that causes this situation is being handled as
-another bug, [[git-annex directory hashing problems on osx]].
-So, closing this bug report. [[done]] --[[Joey]]
diff --git a/doc/bugs/git-annex_immediately_re-gets_dropped_files.mdwn b/doc/bugs/git-annex_immediately_re-gets_dropped_files.mdwn
deleted file mode 100644
index 2368df98d..000000000
--- a/doc/bugs/git-annex_immediately_re-gets_dropped_files.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-### Please describe the problem.
-
-I have some files that I want to drop from my laptop. However, as soon as I drop them (git-annex drop), the assistant starts to download them again from another repository. At first glance, this seems like a variant of [[bugs/Handling_of_files_inside_and_outside_archive_directory_at_the_same_time]].
-
-I would expect that after an explicit drop command, the files would not be re-downloaded.
-
-The repository that this is happening on is a "client" type, direct-mode repository.
-
-### What steps will reproduce the problem?
-
-    git annex drop drop-test/TestFile.data
-
-### What version of git-annex are you using? On what operating system?
-    git-annex version: 4.20130618-g333cb8e
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-    local repository version: 4
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-    I am running Ubuntu 13.04
-
-### Please provide any additional information below.
-
-log emailed.
-
-> [[done]]; not a bug, should use manual mode if manually deciding which files are in a repository --[[Joey]] 
diff --git a/doc/bugs/git-annex_immediately_re-gets_dropped_files/comment_1_09e616a4866e726a48be4febe6375cc8._comment b/doc/bugs/git-annex_immediately_re-gets_dropped_files/comment_1_09e616a4866e726a48be4febe6375cc8._comment
deleted file mode 100644
index 3976f08fa..000000000
--- a/doc/bugs/git-annex_immediately_re-gets_dropped_files/comment_1_09e616a4866e726a48be4febe6375cc8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-06-18T21:01:03Z"
- content="""
-The assistant does not have information to guess why a file has changed, it just sees it has, and takes appropriate action to get it in sync. If you want to manually manage which files are present, you should enable manual mode.
-"""]]
diff --git a/doc/bugs/git-annex_incorrectly_parses_bare_IPv6_addresses.mdwn b/doc/bugs/git-annex_incorrectly_parses_bare_IPv6_addresses.mdwn
deleted file mode 100644
index c94952b49..000000000
--- a/doc/bugs/git-annex_incorrectly_parses_bare_IPv6_addresses.mdwn
+++ /dev/null
@@ -1,59 +0,0 @@
-I have a git remote in a git-annex-enabled repository. Here's what it looks like in .git/config:
-
-<pre>
-[remote "renaissance"]
-        url = ssh://[2001:0:53aa:64c:24ef:5ce4:2ef9:cdda]/home/paulproteus/Music/annex/
-        fetch = +refs/heads/*:refs/remotes/renaissance/*
-        annex-uuid = 2992752e-1a13-11e0-ba68-57d3c800da64
-</pre>
-
-I wanted to "git annex get" some data. git-annex appears to pass incorrectly-formatted IPv6 addresses to rsync:
-
-<pre>
-get primary/emusiq/Arab Strap/Monday At The Hug And Pint/01-The Shy Retirer.mp3 (copying from renaissance...) 
-ssh: Could not resolve hostname [2001:0:53aa:64c:24ef:5ce4:2ef9:cdda]: Name or service not known
-rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
-rsync error: unexplained error (code 255) at io.c(601) [Receiver=3.0.7]
-
-  rsync failed -- run git annex again to resume file transfer
-  Unable to access these remotes: renaissance
-  Try making some of these repositories available:
-  	2992752e-1a13-11e0-ba68-57d3c800da64
-failed
-</pre>
-
-In this case, the square brackets should not be there.
-
-I tried changing the .git/config syntax slightly, and got a different, also-incorrect behavior:
-
-<pre>
-[remote "renaissance"]
-        url = [2001:0:53aa:64c:24ef:5ce4:2ef9:cdda]:/home/paulproteus/Music/annex/
-        fetch = +refs/heads/*:refs/remotes/renaissance/*
-        annex-uuid = 2992752e-1a13-11e0-ba68-57d3c800da64
-</pre>
-
-<pre>
-paulproteus@pathi:~/Music/annex$ git annex get
-git-annex: bad url ssh://[2001/~/0:53aa:64c:24ef:5ce4:2ef9:cdda]:/home/paulproteus/Music/annex/
-</pre>
-
-(Note that both these .git/config entries work fine with "git fetch".)
-
--- Asheesh.
-
-> Technically, this seems to be a bug in the haskell URI library; it honors
-> the `[]` in parsing, but does not remove them when the URI is queried for
-> the host part. 
-
-<pre>
-Prelude Network.URI> let (Just u) = parseURI "http://foo@[2001:0:53aa:64c:24ef:5ce4:2ef9:cdda]/bar"
-Prelude Network.URI> let (Just a) = uriAuthority u
-Prelude Network.URI> uriRegName a
-"[2001:0:53aa:64c:24ef:5ce4:2ef9:cdda]"
-Prelude Network.URI> isIPv6address $ uriRegName a
-False
-</pre>
-
-> I have filed a [bug upstream](http://trac.haskell.org/network/ticket/40), and put a workaround in git-annex. [[done]]
-> --[[Joey]] 
diff --git a/doc/bugs/git-annex_losing_rsync_remotes_with_encryption_enabled.mdwn b/doc/bugs/git-annex_losing_rsync_remotes_with_encryption_enabled.mdwn
deleted file mode 100644
index 8df3608db..000000000
--- a/doc/bugs/git-annex_losing_rsync_remotes_with_encryption_enabled.mdwn
+++ /dev/null
@@ -1,103 +0,0 @@
-Somehow git-annex has again lost a complete rsync remote with encryption enabled...
-
-git-annex version was 3.20111111
-
-> "once again" ? When did it do it before?
-
->> It's the second time i uploaded all the files to an encrypted rsync remote and git-annex is not able to find it anymore. --[[gebi]]
-
-> "lost" ? How is the remote lost?
-
->> git-annex is not able to find any files on the encrypted rsync remote anymore.
->> Copy does not copy the content again but drop doesn't find it, thus it's somehow "lost" and in an strange state.
->> I've also had the state where the content was already on the remote side but git-annex copy would copy it again,
->> ignoring all the data on the remote side. --[[gebi]]
-
-Both *remoteserver* and *localserver* are rsync remotes with enabled encryption.
-All commands are executed on the git repository on my laptop.
-Target of origin is a gitolite repository without annex support (thus the two rsync remotes).
-
-Is there a way in git-annex to verify that all files fullfill the numcopies, in my case
-numcopies=2, and can be read from the remotes their are on?
-I thought that *copy* would verify that, but seems not.
-    
-    % g a copy --to remoteserver tools
-    copy tools/md5_sha1_utility.exe (gpg) (checking remoteserver...) ok
-    copy tools/win32diskimager-RELEASE-0.2-r23-win32.zip (checking remoteserver...) ok
-    
-    % g a copy --to localserver tools
-    copy tools/md5_sha1_utility.exe (gpg) (checking localserver...) ok
-    copy tools/win32diskimager-RELEASE-0.2-r23-win32.zip (checking localserver...) ok
-    
-    % g a drop tools
-    drop tools/md5_sha1_utility.exe (gpg) (checking localserver...) (checking remoteserver...) (unsafe)
-      Could only verify the existence of 1 out of 2 necessary copies
-      
-      Try making some of these repositories available:
-            718a9b5c-1b4a-11e1-8211-6f094f20e050 -- remoteserver (remote backupserver)
-      
-      (Use --force to override this check, or adjust annex.numcopies.)
-    failed
-    drop tools/win32diskimager-RELEASE-0.2-r23-win32.zip (checking localserver...) (checking remoteserver...) (unsafe)
-      Could only verify the existence of 1 out of 2 necessary copies
-      
-      Try making some of these repositories available:
-            718a9b5c-1b4a-11e1-8211-6f094f20e050 -- remoteserver (remote backupserver)
-      
-      (Use --force to override this check, or adjust annex.numcopies.)
-    failed
-    git-annex: drop: 2 failed
-    
-    % g a fsck tools
-    fsck tools/md5_sha1_utility.exe (checksum...) ok
-    fsck tools/win32diskimager-RELEASE-0.2-r23-win32.zip (checksum...) ok
-
-> Copy does do an explicit check that the content is present on remoteserver,
-> and based on the above, the content was found to be already there,
-> which is why it did not copy it again.
-> 
-> Drop does an indentical check that the content is present, and 
-> since it failed to find it, I am left thinking something must have
-> happened to the remove in between the copy and the drop to cause the
-> content to go away.
-> 
-> What happens if you copy the data to remoteserver again? --[[Joey]]
-
-The commands above are executed within a few seconds and completely repeatable. --[[gebi]]
-
-> In that case, why don't you run the commands with `-d` to see the actual
-> rsync command it's running to check if the content is present. 
-> Then you can try repeatedly running the command by hand and see why it
-> sometimes succeeds and sometimes fail.
-
-The commands fail and succeed consistently, not either or.
-git annex copy succeeds consistently with not copying the content to remote because it checks and it's already there.
-
-git annex drop fails consistently with error because content is missing on the exact same remote git annex copy checks
-and thinks the content is there. --[[gebi]]
-
-> The command will be something like this:
-> `rsync --quiet hostname:/dir/file 2>/dev/null`
-> 
-> The exit status is what's used to see if content is present -- and
-> currently any failure even a failure to connect is taken to mean it's not
-> present. --[[Joey]]
-
-hm... thats interesting, git annex drop and git annex copy check for different hashes on the same file at the same remote...
-
-git annex drop -d tools/md5_sha1_utility.exe
-> Running: sh ["-c","rsync --quiet 'REMOVED_HOST:annex/work/JF/z7/'\"'\"'GPGHMACSHA1--7ffb3840f0e37aee964352e98808403655e8473a/GPGHMACSHA1--7ffb3840f0e37aee964352e98808403655e8473a'\"'\"'' 2>/dev/null"]
-
-git annex copy --to remoteserver -d tools/md5_sha1_utility.exe
-> Running: sh ["-c","rsync --quiet 'REMOVED_HOST:annex/work/1F/PQ/'\"'\"'GPGHMACSHA1--ff075e57f649300c5698e346be74fb6e22d70e35/GPGHMACSHA1--ff075e57f649300c5698e346be74fb6e22d70e35'\"'\"'' 2>/dev/null"]
-
-And yes, only the hash *annex copy* is checking for exists on the remote side. --[[gebi]]
-
-> Ok, this is due to too aggressive caching of the decrypted cipher
-> for a remote. When dopping, it decrypts localserver's cipher, 
-> caches it, and then when checking remoteserver it says hey, 
-> here's an already decrypted cipher -- it must be the right one!
-> 
-> Problem reproduced here, and fixed. [[done]] --[[Joey]]
-
-THX Joey! -- [[gebi]]
diff --git a/doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_.mdwn b/doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_.mdwn
deleted file mode 100644
index 53b993de2..000000000
--- a/doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-What steps will reproduce the problem?
-
-    $ git clone ~/corbeau/travail/ travail
-    Cloning into 'travail'...
-    done.
-    Checking out files: 100% (8670/8670), done.
-    $ cd travail
-    $ git annex init "portable USB drive"
-    init portable USB drive 
-      Detected a crippled filesystem.
-
-      Enabling direct mode.
-
-    git-annex: /media/LACIE/travail/.git/annex/objects/k1: createDirectory: already exists (File exists)
-    failed
-    git-annex: init: 1 failed
-
-What version of git-annex are you using? On what operating system?
-    $ apt-cache policy git-annex
-    git-annex:
-    Installé : 3.20130216
-
-This on a amd64 debian sid recently updated
-
-
-Please provide any additional information below.
-
-The problem is that git annex already created a /media/LACIE/travail/.git/annex/objects/K1 file (same name in uppercase) and FAT isn't realy case sensitive.
-
-
-> I *think* I've found the place that used createDirectory
-> rather than createDirectoryIfMissing and fixed it. [[done]] --[[Joey]]
diff --git a/doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_/comment_1_850695231926dfe94f11342d3af7f63c._comment b/doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_/comment_1_850695231926dfe94f11342d3af7f63c._comment
deleted file mode 100644
index a11bb3bf5..000000000
--- a/doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_/comment_1_850695231926dfe94f11342d3af7f63c._comment
+++ /dev/null
@@ -1,54 +0,0 @@
-[[!comment format=mdwn
- username="http://hands.com/~phil/"
- nickname="fil"
- subject="still seems to be a problem with 4.20130323"
- date="2013-03-31T16:49:47Z"
- content="""
-Hi Joey,
-
-Seems that I can still get this to choke on a VFAT system:
-
-    poker% sudo mount -o loop,gid=25,fmask=0117,dmask=0007 /home/phil/nobackup/annextest-image/vfat-annex-test.img /mnt 
-    poker% mount | grep /mnt                                                                                      
-    /home/phil/nobackup/annextest-image/vfat-annex-test.img on /mnt type vfat (rw,relatime,gid=25,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro)        
-    poker% cd /mnt 
-    poker% git init                                                                                               
-    Initialized empty Git repository in /mnt/.git/
-    poker% git annex init simple\ test
-    init simple test 
-      Detected a crippled filesystem.
-    
-      Enabling direct mode.
-    ok
-    (Recording state in git...)
-    poker% for i in $(seq 1 42) ; do echo $i > $i.txt ; done
-    poker% git annex add *.txt
-    add 10.txt (checksum...) ok
-    add 11.txt (checksum...) ok
-    ...
-    add 40.txt (checksum...) ok
-    add 41.txt (checksum...) ok
-    add 42.txt (checksum...) 
-    git-annex: /mnt/.git/annex/objects/Wj/56: createDirectory: does not exist (No such file or directory)
-    failed
-    add 4.txt (checksum...) ok
-    add 5.txt (checksum...) ok
-    add 6.txt (checksum...) ok
-    add 7.txt (checksum...) ok
-    add 8.txt (checksum...) ok
-    add 9.txt (checksum...) ok
-    (Recording state in git...)
-    git-annex: add: 1 failed
-    poker% ls -ld /mnt/.git/annex/objects/[wW][jJ]
-    drwxrwx--- 3 root floppy 4096 Mar 31 17:21 /mnt/.git/annex/objects/wJ
-    poker% git annex version  
-    git-annex version: 4.20130323
-
-perhaps I shouldn't be trying that anyway -- I was wanting to create a direct mode repo on each of my camera's SD cards, which the camera will happily ignore, but allows me to add new photos to the repo by plugging the card into my laptop, and then copy them elsewhere using git annex magic.  I'm hoping that would allow me to leave favourite photos on the camera, for showing off photos when without my laptop, while not becoming confused about which photos I've already got copies of and can safely delete (with annex's drop telling me when I try to delete things I shouldn't).
-
-The reason not to use a special directory remote (at least I think this is right judging from the wiki info) is that the camera won't grok the filenames under .git/annex/... so the photos need to be left with their names as created by the camera.
-
-Anyway, while experimenting with that idea, I bumped into the above, which seems like a continuation of this bug.
-
-_Update:_  Just tried that again, having cloned the git and rebuilt locally, and I'm still seeing the same behaviour with the very latest (i.e. 11b3942ef2aa13fe38d79e91392fc43d65a7e019)
-"""]]
diff --git a/doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_/comment_2_c2a2f801a3e18ad597ff0acf2f104557._comment b/doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_/comment_2_c2a2f801a3e18ad597ff0acf2f104557._comment
deleted file mode 100644
index 8ab32ede2..000000000
--- a/doc/bugs/git-annex_on_crippled_filesystem_can_still_failed_due_to_case_/comment_2_c2a2f801a3e18ad597ff0acf2f104557._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-04-04T19:47:50Z"
- content="""
-Whups, this bug report was closed; I almost missed this new bug and test case.
-
-So, on these filesystems that are horribly confused about case, it's possible for `mkdir FOO` to fail with \"already exists\", because there is a directory named `foo` ... but then `mkdir FOO/bar` fails with \"no such file or directory\". 
-
-That is an intractable problem. It follows that it's simply not safe to use mixed case files on such a filesystem. You will always shoot your later self in the foot. (I personally think it's outright foolish to use a filesystem with such horrible semantics at all, but whatever.)
-
-So.. I took a good look at this, and it turns out that
-
-* since this is a crippled filesystem anyway, git-annex doesn't use symlinks on it
-* so there's no reason to use the mixed case hash directories that we're stuck using to avoid breaking everyone's symlinks to the content
-* so we can do what is already done for all bare repos, and make non-bare repos on crippled filesystems use the all-lower case hash directories
-* which are, happily, all 3 letters long, so they cannot conflict with mixed case hash directories
-* so I was able to 100% fix this and even resuming `git annex add` in the test case will recover and it will all just work.
-
-Yay!
-"""]]
diff --git a/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__.mdwn b/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__.mdwn
deleted file mode 100644
index a682c12cc..000000000
--- a/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__.mdwn
+++ /dev/null
@@ -1,358 +0,0 @@
-### Please describe the problem.
-
-I installed the git-annex app for MacOSX (10.8.4)
-
-### What steps will reproduce the problem?
-
-- Created a repository
-- In the configuration, entered my google username/password
-
-### What version of git-annex are you using? On what operating system?
-
-bundle version: 0.0.1
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-Process:         git-annex [12934]
-Path:            /Applications/git-annex.app/Contents/MacOS/bundle/git-annex
-Identifier:      git-annex
-Version:         0
-Code Type:       X86-64 (Native)
-Parent Process:  ??? [1]
-User ID:         502
-
-Date/Time:       2013-08-17 12:27:12.495 -0700
-OS Version:      Mac OS X 10.8.4 (12E55)
-Report Version:  10
-Sleep/Wake UUID: 6DB42174-0147-4C8B-B83E-F305823297CA
-
-Interval Since Last Report:          294009 sec
-Crashes Since Last Report:           4
-Per-App Crashes Since Last Report:   4
-Anonymous UUID:                      0D492F72-DAE5-360C-A6D6-ECB38FD53115
-
-Crashed Thread:  3
-
-Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
-Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
-
-VM Regions Near 0:
---> 
-    __TEXT                 000000010b5e6000-000000010e08d000 [ 42.7M] r-x/rwx SM=COW  /Applications/git-annex.app/Contents/MacOS/bundle/git-annex
-
-Thread 0:: Dispatch queue: com.apple.main-thread
-0   libsystem_kernel.dylib        	0x00007fff931400fa __psynch_cvwait + 10
-1   libsystem_c.dylib             	0x00007fff86adffe9 _pthread_cond_wait + 869
-2   git-annex                     	0x000000010df20179 0x10b5e6000 + 43229561
-3   git-annex                     	0x000000010defc8eb 0x10b5e6000 + 43084011
-4   git-annex                     	0x000000010df0bc86 0x10b5e6000 + 43146374
-5   git-annex                     	0x000000010df0c6fb 0x10b5e6000 + 43149051
-6   git-annex                     	0x000000010df07b46 0x10b5e6000 + 43129670
-7   git-annex                     	0x000000010df07c69 0x10b5e6000 + 43129961
-8   git-annex                     	0x000000010bcff518 0x10b5e6000 + 7443736
-9   libdyld.dylib                 	0x00007fff8c3e47e1 start + 1
-
-Thread 1:
-0   libsystem_kernel.dylib        	0x00007fff931400fa __psynch_cvwait + 10
-1   libsystem_c.dylib             	0x00007fff86adffe9 _pthread_cond_wait + 869
-2   git-annex                     	0x000000010df20179 0x10b5e6000 + 43229561
-3   git-annex                     	0x000000010defc8eb 0x10b5e6000 + 43084011
-4   git-annex                     	0x000000010df0bc86 0x10b5e6000 + 43146374
-5   git-annex                     	0x000000010df0c5e0 0x10b5e6000 + 43148768
-6   libsystem_c.dylib             	0x00007fff86adb7a2 _pthread_start + 327
-7   libsystem_c.dylib             	0x00007fff86ac81e1 thread_start + 13
-
-Thread 2:
-0   libsystem_kernel.dylib        	0x00007fff931400fa __psynch_cvwait + 10
-1   libsystem_c.dylib             	0x00007fff86adffe9 _pthread_cond_wait + 869
-2   git-annex                     	0x000000010df20179 0x10b5e6000 + 43229561
-3   git-annex                     	0x000000010defc8eb 0x10b5e6000 + 43084011
-4   git-annex                     	0x000000010df0bc86 0x10b5e6000 + 43146374
-5   git-annex                     	0x000000010df0c5e0 0x10b5e6000 + 43148768
-6   libsystem_c.dylib             	0x00007fff86adb7a2 _pthread_start + 327
-7   libsystem_c.dylib             	0x00007fff86ac81e1 thread_start + 13
-
-Thread 3 Crashed:
-0   libsystem_c.dylib             	0x00007fff86ae0bf9 pthread_mutex_lock + 20
-1   H                             	0x000000010e9fd29f gnutls_system_mutex_lock + 12
-2   H                             	0x000000010ea7fa29 wrap_nettle_rnd_refresh + 20
-3   H                             	0x000000010e9fee89 gnutls_deinit + 42
-4   git-annex                     	0x000000010caf0a3a 0x10b5e6000 + 22063674
-
-Thread 4:
-0   libsystem_kernel.dylib        	0x00007fff93140d2a kevent64 + 10
-1   git-annex                     	0x000000010deab5fa 0x10b5e6000 + 42751482
-
-Thread 5:
-0   libsystem_kernel.dylib        	0x00007fff931400fa __psynch_cvwait + 10
-1   libsystem_c.dylib             	0x00007fff86adffe9 _pthread_cond_wait + 869
-2   git-annex                     	0x000000010df20179 0x10b5e6000 + 43229561
-3   git-annex                     	0x000000010defc8eb 0x10b5e6000 + 43084011
-4   git-annex                     	0x000000010df0bc86 0x10b5e6000 + 43146374
-5   git-annex                     	0x000000010df0c5e0 0x10b5e6000 + 43148768
-6   libsystem_c.dylib             	0x00007fff86adb7a2 _pthread_start + 327
-7   libsystem_c.dylib             	0x00007fff86ac81e1 thread_start + 13
-
-Thread 6:: Dispatch queue: com.apple.libdispatch-manager
-0   libsystem_kernel.dylib        	0x00007fff93140d16 kevent + 10
-1   libdispatch.dylib             	0x00007fff8e6fedea _dispatch_mgr_invoke + 883
-2   libdispatch.dylib             	0x00007fff8e6fe9ee _dispatch_mgr_thread + 54
-
-Thread 7:
-0   libsystem_kernel.dylib        	0x00007fff9313e686 mach_msg_trap + 10
-1   libsystem_kernel.dylib        	0x00007fff9313dc42 mach_msg + 70
-2   com.apple.CoreFoundation      	0x00007fff8c1e2233 __CFRunLoopServiceMachPort + 195
-3   com.apple.CoreFoundation      	0x00007fff8c1e7916 __CFRunLoopRun + 1078
-4   com.apple.CoreFoundation      	0x00007fff8c1e70e2 CFRunLoopRunSpecific + 290
-5   com.apple.CoreFoundation      	0x00007fff8c1f5dd1 CFRunLoopRun + 97
-6   git-annex                     	0x000000010c72b3ec 0x10b5e6000 + 18109420
-7   libsystem_c.dylib             	0x00007fff86adb7a2 _pthread_start + 327
-8   libsystem_c.dylib             	0x00007fff86ac81e1 thread_start + 13
-
-Thread 8:
-0   libsystem_kernel.dylib        	0x00007fff9313e686 mach_msg_trap + 10
-1   libsystem_kernel.dylib        	0x00007fff9313dc42 mach_msg + 70
-2   com.apple.CoreFoundation      	0x00007fff8c1e2233 __CFRunLoopServiceMachPort + 195
-3   com.apple.CoreFoundation      	0x00007fff8c1e7916 __CFRunLoopRun + 1078
-4   com.apple.CoreFoundation      	0x00007fff8c1e70e2 CFRunLoopRunSpecific + 290
-5   com.apple.CoreFoundation      	0x00007fff8c1f5dd1 CFRunLoopRun + 97
-6   git-annex                     	0x000000010c72b3ec 0x10b5e6000 + 18109420
-7   libsystem_c.dylib             	0x00007fff86adb7a2 _pthread_start + 327
-8   libsystem_c.dylib             	0x00007fff86ac81e1 thread_start + 13
-
-Thread 9:
-0   libsystem_kernel.dylib        	0x00007fff9313e686 mach_msg_trap + 10
-1   libsystem_kernel.dylib        	0x00007fff9313dc42 mach_msg + 70
-2   com.apple.CoreFoundation      	0x00007fff8c1e2233 __CFRunLoopServiceMachPort + 195
-3   com.apple.CoreFoundation      	0x00007fff8c1e7916 __CFRunLoopRun + 1078
-4   com.apple.CoreFoundation      	0x00007fff8c1e70e2 CFRunLoopRunSpecific + 290
-5   com.apple.CoreFoundation      	0x00007fff8c1f5dd1 CFRunLoopRun + 97
-6   git-annex                     	0x000000010c72b3ec 0x10b5e6000 + 18109420
-7   libsystem_c.dylib             	0x00007fff86adb7a2 _pthread_start + 327
-8   libsystem_c.dylib             	0x00007fff86ac81e1 thread_start + 13
-
-Thread 3 crashed with X86 Thread State (64-bit):
-  rax: 0x000000010eaaca28  rbx: 0x00007f9dc38000c0  rcx: 0x000000010f87ce00  rdx: 0x000000010e3c28f0
-  rdi: 0x0000000000000000  rsi: 0x001c4500001c4500  rbp: 0x000000010f87ce10  rsp: 0x000000010f87cdd0
-   r8: 0x0000000000002060   r9: 0x000000010f87ce00  r10: 0x000000010eabf328  r11: 0x000000010e9fee5f
-  r12: 0x000000010f5585d8  r13: 0x000000010e3c2798  r14: 0x0000000000000000  r15: 0x000000010f548140
-  rip: 0x00007fff86ae0bf9  rfl: 0x0000000000010202  cr2: 0x0000000000000000
-Logical CPU: 0
-
-Binary Images:
-       0x10b5e6000 -        0x10e08cff7 +git-annex (0) <2C4C13B3-4830-322A-A144-9E51B386EB1E> /Applications/git-annex.app/Contents/MacOS/bundle/git-annex
-       0x10e85a000 -        0x10e957ff7 +E (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /Applications/git-annex.app/Contents/MacOS/bundle/E
-       0x10e990000 -        0x10e9a4fff +F (0) <FA90B1B1-A866-3A6C-BB97-06955F4C8C0B> /Applications/git-annex.app/Contents/MacOS/bundle/F
-       0x10e9ab000 -        0x10e9d8ff7 +G (0) <D80652C0-9A55-351C-8EAF-2364359BA0A2> /Applications/git-annex.app/Contents/MacOS/bundle/G
-       0x10e9de000 -        0x10eaabfdf +H (0) <29C3AFF5-8EFB-3A16-81F6-0DA6CF2675A6> /Applications/git-annex.app/Contents/MacOS/bundle/H
-       0x10eadd000 -        0x10eaefff7 +B (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /Applications/git-annex.app/Contents/MacOS/bundle/B
-       0x10eaf7000 -        0x10ebecfff +D (34) <FEE8B996-EB44-37FA-B96E-D379664DEFE1> /Applications/git-annex.app/Contents/MacOS/bundle/D
-       0x10ec01000 -        0x10ed1992f +I (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /Applications/git-annex.app/Contents/MacOS/bundle/I
-       0x10ed3d000 -        0x10ef3dfff +S (491.11.3) <5783D305-04E8-3D17-94F7-1CEAFA975240> /Applications/git-annex.app/Contents/MacOS/bundle/S
-       0x10f048000 -        0x10f06dff7 +Z (26) <D86169F3-9F31-377A-9AF3-DB17142052E4> /Applications/git-annex.app/Contents/MacOS/bundle/Z
-       0x10f0a1000 -        0x10f109ff7 +0A (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /Applications/git-annex.app/Contents/MacOS/bundle/0A
-       0x10f163000 -        0x10f1ccfff +0B (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /Applications/git-annex.app/Contents/MacOS/bundle/0B
-       0x10f235000 -        0x10f248fff +T (0) <C8970714-4C86-3BE6-94D6-4835DCC8A003> /Applications/git-annex.app/Contents/MacOS/bundle/T
-       0x10f257000 -        0x10f264ff7 +U (0) <DCFF385A-090B-3407-868C-91544A2EFEE1> /Applications/git-annex.app/Contents/MacOS/bundle/U
-       0x10f26f000 -        0x10f291ff7 +V (0) <51B317C7-94CC-3C58-B515-924BB3AF0BCC> /Applications/git-annex.app/Contents/MacOS/bundle/V
-       0x10f29b000 -        0x10f2a8ff7 +W (0) <91CF16BE-027F-3FE6-B1EE-6B8BFD51FC1B> /Applications/git-annex.app/Contents/MacOS/bundle/W
-       0x10f2b4000 -        0x10f310fd7 +X (0) <84D934AF-A321-36C0-BBCF-CD3FDAEB0B95> /Applications/git-annex.app/Contents/MacOS/bundle/X
-    0x7fff6b1e6000 -     0x7fff6b21a93f  dyld (210.2.3) <36CAA36E-72BC-3E48-96D9-B96A2DF77730> /usr/lib/dyld
-    0x7fff8652a000 -     0x7fff865d0ff7  com.apple.CoreServices.OSServices (557.6 - 557.6) <FFDDD2D8-690D-388F-A48F-4750A792D2CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
-    0x7fff865d1000 -     0x7fff865e8fff  libGL.dylib (8.9.2) <B8E5948D-BCF2-3727-B74E-D74B8EDC82D6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
-    0x7fff865e9000 -     0x7fff86610fff  com.apple.framework.familycontrols (4.1 - 410) <50F5A52C-8FB6-300A-977D-5CFDE4D5796B> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls
-    0x7fff86611000 -     0x7fff8663cfff  libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib
-    0x7fff86649000 -     0x7fff86698ff7  libcorecrypto.dylib (106.2) <CE0C29A3-C420-339B-ADAA-52F4683233CC> /usr/lib/system/libcorecrypto.dylib
-    0x7fff8669d000 -     0x7fff866a3fff  com.apple.DiskArbitration (2.5.2 - 2.5.2) <C713A35A-360E-36CE-AC0A-25C86A3F50CA> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
-    0x7fff866a4000 -     0x7fff86ac1fff  FaceCoreLight (2.4.1) <DDAFFD7A-D312-3407-A010-5AEF3E17831B> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLight
-    0x7fff86ac7000 -     0x7fff86b93ff7  libsystem_c.dylib (825.26) <4C9EB006-FE1F-3F8F-8074-DFD94CF2CE7B> /usr/lib/system/libsystem_c.dylib
-    0x7fff86d50000 -     0x7fff86da1ff7  com.apple.SystemConfiguration (1.12.2 - 1.12.2) <581BF463-C15A-363B-999A-E830222FA925> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
-    0x7fff86dee000 -     0x7fff86deefff  com.apple.Accelerate.vecLib (3.8 - vecLib 3.8) <B5A18EE8-DF81-38DD-ACAF-7076B2A26225> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
-    0x7fff86def000 -     0x7fff86df4fff  com.apple.OpenDirectory (10.8 - 151.10) <CF44120B-9B01-32DD-852E-C9C0E1243FC0> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
-    0x7fff86df5000 -     0x7fff86df6fff  libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib
-    0x7fff86e0a000 -     0x7fff87201fff  libLAPACK.dylib (1073.4) <D632EC8B-2BA0-3853-800A-20DA00A1091C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
-    0x7fff87622000 -     0x7fff87650ff7  libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
-    0x7fff8766c000 -     0x7fff8769dff7  com.apple.DictionaryServices (1.2 - 184.4) <FB0540FF-5034-3591-A28D-6887FBC220F7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
-    0x7fff8769e000 -     0x7fff8769efff  libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
-    0x7fff87732000 -     0x7fff87754ff7  libxpc.dylib (140.43) <70BC645B-6952-3264-930C-C835010CCEF9> /usr/lib/system/libxpc.dylib
-    0x7fff87755000 -     0x7fff877d7ff7  com.apple.Heimdal (3.0 - 2.0) <C94B0C6C-1320-35A1-8143-FE252E7B2A08> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
-    0x7fff877d8000 -     0x7fff87859fff  com.apple.Metadata (10.7.0 - 707.11) <2DD25313-420D-351A-90F1-300E95C970CA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
-    0x7fff87cbf000 -     0x7fff87d19fff  com.apple.print.framework.PrintCore (8.3 - 387.2) <5BA0CBED-4D80-386A-9646-F835C9805B71> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
-    0x7fff87e27000 -     0x7fff87e34ff7  com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
-    0x7fff87f54000 -     0x7fff87f68fff  com.apple.speech.synthesis.framework (4.1.12 - 4.1.12) <94EDF2AB-809C-3D15-BED5-7AD45B2A7C16> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
-    0x7fff87f77000 -     0x7fff87f7dff7  libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib
-    0x7fff87fab000 -     0x7fff87fabfff  com.apple.Accelerate (1.8 - Accelerate 1.8) <6AD48543-0864-3D40-80CE-01F184F24B45> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
-    0x7fff88161000 -     0x7fff88162ff7  libSystem.B.dylib (169.3) <9089D72D-E714-31E1-80C8-698A8E8B05AD> /usr/lib/libSystem.B.dylib
-    0x7fff88167000 -     0x7fff88205ff7  com.apple.ink.framework (10.8.2 - 150) <3D8D16A2-7E01-3EA1-B637-83A36D353308> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
-    0x7fff88222000 -     0x7fff88223ff7  libsystem_sandbox.dylib (220.3) <B739DA63-B675-387A-AD84-412A651143C0> /usr/lib/system/libsystem_sandbox.dylib
-    0x7fff88224000 -     0x7fff88228ff7  com.apple.TCC (1.0 - 1) <F2F3B753-FC73-3543-8BBE-859FDBB4D6A6> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
-    0x7fff88229000 -     0x7fff88230fff  libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
-    0x7fff88a6e000 -     0x7fff88a8dff7  libresolv.9.dylib (51) <0882DC2D-A892-31FF-AD8C-0BB518C48B23> /usr/lib/libresolv.9.dylib
-    0x7fff88a8e000 -     0x7fff88aa1ff7  libbsm.0.dylib (32) <F497D3CE-40D9-3551-84B4-3D5E39600737> /usr/lib/libbsm.0.dylib
-    0x7fff88bbd000 -     0x7fff88bbdfff  com.apple.ApplicationServices (45 - 45) <A3ABF20B-ED3A-32B5-830E-B37831A45A80> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
-    0x7fff88bce000 -     0x7fff88bf6fff  libJPEG.dylib (850) <DC750E1E-BD07-339B-A4A6-D86BFE969F68> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
-    0x7fff88bf7000 -     0x7fff88bf9fff  libquarantine.dylib (52.1) <143B726E-DF47-37A8-90AA-F059CFD1A2E4> /usr/lib/system/libquarantine.dylib
-    0x7fff88fe0000 -     0x7fff8933ffff  com.apple.Foundation (6.8 - 945.18) <1D7E58E6-FA3A-3CE8-AC85-B9D06B8C0AA0> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
-    0x7fff89340000 -     0x7fff89575ff7  com.apple.CoreData (106.1 - 407.7) <A676E1A4-2144-376B-92B8-B450DD1D78E5> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
-    0x7fff89576000 -     0x7fff8957dfff  libGFXShared.dylib (8.9.2) <398F8D57-EC82-3E13-AC8E-470BE19237D7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
-    0x7fff895d4000 -     0x7fff8a201fff  com.apple.AppKit (6.8 - 1187.39) <199962F0-B06B-3666-8FD5-5C90374BA16A> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
-    0x7fff8a202000 -     0x7fff8a519ff7  com.apple.CoreServices.CarbonCore (1037.6 - 1037.6) <1E567A52-677F-3168-979F-5FBB0818D52B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
-    0x7fff8a5e0000 -     0x7fff8a5e7fff  com.apple.NetFS (5.0 - 4.0) <82E24B9A-7742-3DA3-9E99-ED267D98C05E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
-    0x7fff8a5e8000 -     0x7fff8a63fff7  com.apple.ScalableUserInterface (1.0 - 1) <F1D43DFB-1796-361B-AD4B-39F1EED3BE19> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface
-    0x7fff8a71b000 -     0x7fff8a767ff7  libauto.dylib (185.4) <AD5A4CE7-CB53-313C-9FAE-673303CC2D35> /usr/lib/libauto.dylib
-    0x7fff8a768000 -     0x7fff8a768fff  libOpenScriptingUtil.dylib (148.3) <F8681222-0969-3B10-8BCE-C55A4B9C520C> /usr/lib/libOpenScriptingUtil.dylib
-    0x7fff8a7e7000 -     0x7fff8a808ff7  libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib
-    0x7fff8a809000 -     0x7fff8a815fff  com.apple.CrashReporterSupport (10.8.3 - 418) <DE6AFE16-D97E-399D-82ED-3522C773C36E> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
-    0x7fff8a816000 -     0x7fff8b1a64af  com.apple.CoreGraphics (1.600.0 - 332) <5AB32E51-9154-3733-B83B-A9A748652847> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
-    0x7fff8b1a7000 -     0x7fff8b1befff  com.apple.CFOpenDirectory (10.8 - 151.10) <10F41DA4-AD54-3F52-B898-588D9A117171> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
-    0x7fff8b242000 -     0x7fff8b285ff7  com.apple.bom (12.0 - 192) <0BF1F2D2-3648-36B7-BE4B-551A0173209B> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
-    0x7fff8b286000 -     0x7fff8b2c3fef  libGLImage.dylib (8.9.2) <C38649ED-E1C9-315E-9953-F33E8C6A3C89> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
-    0x7fff8b2c4000 -     0x7fff8b303ff7  com.apple.QD (3.42.1 - 285.1) <77A20C25-EBB5-341C-A05C-5D458B97AD5C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
-    0x7fff8b304000 -     0x7fff8b39efff  libvMisc.dylib (380.6) <714336EA-1C0E-3735-B31C-19DFDAAF6221> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
-    0x7fff8b3b8000 -     0x7fff8b566fff  com.apple.QuartzCore (1.8 - 304.3) <F450F2DE-2F24-3557-98B6-310E05DAC17F> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
-    0x7fff8ba39000 -     0x7fff8ba4cff7  com.apple.LangAnalysis (1.7.0 - 1.7.0) <2F2694E9-A7BC-33C7-B4CF-8EC907DF0FEB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
-    0x7fff8bd12000 -     0x7fff8bd1cfff  com.apple.speech.recognition.framework (4.1.5 - 4.1.5) <D803919C-3102-3515-A178-61E9C86C46A1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
-    0x7fff8c0d6000 -     0x7fff8c0d7ff7  libdnsinfo.dylib (453.19) <14202FFB-C3CA-3FCC-94B0-14611BF8692D> /usr/lib/system/libdnsinfo.dylib
-    0x7fff8c179000 -     0x7fff8c17efff  libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib
-    0x7fff8c1b2000 -     0x7fff8c39cff7  com.apple.CoreFoundation (6.8 - 744.19) <0F7403CA-2CB8-3D0A-992B-679701DF27CA> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
-    0x7fff8c39d000 -     0x7fff8c3c4ff7  com.apple.PerformanceAnalysis (1.16 - 16) <E4888388-F41B-313E-9CBB-5807D077BDA9> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
-    0x7fff8c3e2000 -     0x7fff8c3e5ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
-    0x7fff8c3e6000 -     0x7fff8c3e8fff  libCVMSPluginSupport.dylib (8.9.2) <EF1192AC-3357-3A0B-BFAF-6594D7737892> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
-    0x7fff8c3e9000 -     0x7fff8c484fff  com.apple.CoreSymbolication (3.0 - 117) <50716F74-41C2-3BB9-AC16-12C4D4C2DD1E> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
-    0x7fff8c75b000 -     0x7fff8c75bfff  com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
-    0x7fff8cf1f000 -     0x7fff8d094ff7  com.apple.CFNetwork (596.4.3 - 596.4.3) <A57B3308-2F08-3EC3-B4AC-39A3D9F0B9F7> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
-    0x7fff8d0ae000 -     0x7fff8d0e4fff  libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
-    0x7fff8d0e5000 -     0x7fff8d148ff7  com.apple.audio.CoreAudio (4.1.1 - 4.1.1) <9ACD3AED-6C04-3BBB-AB2A-FC253B16D093> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
-    0x7fff8d156000 -     0x7fff8d16cfff  com.apple.MultitouchSupport.framework (235.29 - 235.29) <617EC8F1-BCE7-3553-86DD-F857866E1257> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
-    0x7fff8d16d000 -     0x7fff8d171fff  libGIF.dylib (850) <D4525F87-759C-338C-B283-BB8DE815D3D5> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
-    0x7fff8d264000 -     0x7fff8d2aeff7  libGLU.dylib (8.9.2) <1B5511FF-1064-3004-A245-972CE5687D37> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
-    0x7fff8d2b2000 -     0x7fff8d2dcff7  com.apple.CoreVideo (1.8 - 99.4) <E5082966-6D81-3973-A05A-38AA5B85F886> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
-    0x7fff8d58d000 -     0x7fff8d591fff  com.apple.IOSurface (86.0.4 - 86.0.4) <26F01CD4-B76B-37A3-989D-66E8140542B3> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
-    0x7fff8d6de000 -     0x7fff8d78ffff  com.apple.LaunchServices (539.9 - 539.9) <07FC6766-778E-3479-8F28-D2C9917E1DD1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
-    0x7fff8d7bf000 -     0x7fff8d80eff7  libFontRegistry.dylib (100) <2E03D7DA-9B8F-31BB-8FB5-3D3B6272127F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
-    0x7fff8d80f000 -     0x7fff8d88fff7  com.apple.ApplicationServices.ATS (332 - 341.1) <39B53565-FA31-3F61-B090-C787C983142E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
-    0x7fff8d94e000 -     0x7fff8d95bfff  com.apple.AppleFSCompression (49 - 1.0) <5508344A-2A7E-3122-9562-6F363910A80E> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
-    0x7fff8d95c000 -     0x7fff8d99fff7  com.apple.RemoteViewServices (2.0 - 80.6) <5CFA361D-4853-3ACC-9EFC-A2AC1F43BA4B> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
-    0x7fff8dac2000 -     0x7fff8dac8fff  libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib
-    0x7fff8dac9000 -     0x7fff8db03ff7  com.apple.GSS (3.0 - 2.0) <970CAE00-1437-3F4E-B677-0FDB3714C08C> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
-    0x7fff8db09000 -     0x7fff8db12ff7  com.apple.CommerceCore (1.0 - 26.1) <40A129A8-4E5D-3C7A-B299-8CB203C4C65D> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore
-    0x7fff8db13000 -     0x7fff8db15fff  com.apple.TrustEvaluationAgent (2.0 - 23) <A97D348B-32BF-3E52-8DF2-59BFAD21E1A3> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent
-    0x7fff8de6c000 -     0x7fff8de6eff7  libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
-    0x7fff8de6f000 -     0x7fff8de8eff7  com.apple.ChunkingLibrary (2.0 - 133.3) <8BEC9AFB-DCAA-37E8-A5AB-24422B234ECF> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
-    0x7fff8de8f000 -     0x7fff8deeefff  com.apple.AE (645.6 - 645.6) <44F403C1-660A-3543-AB9C-3902E02F936F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
-    0x7fff8deef000 -     0x7fff8dfecfff  libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib
-    0x7fff8e06b000 -     0x7fff8e076ff7  com.apple.bsd.ServiceManagement (2.0 - 2.0) <C12962D5-85FB-349E-AA56-64F4F487F219> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
-    0x7fff8e077000 -     0x7fff8e086fff  com.apple.opengl (1.8.9 - 1.8.9) <6FD163A7-16CC-3D1F-B4B5-B0FDC4ADBF79> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
-    0x7fff8e087000 -     0x7fff8e092fff  com.apple.CommonAuth (3.0 - 2.0) <7A953C1F-8B18-3E46-9BEA-26D9B5B7745D> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
-    0x7fff8e093000 -     0x7fff8e093fff  com.apple.Cocoa (6.7 - 19) <1F77945C-F37A-3171-B22E-F7AB0FCBB4D4> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
-    0x7fff8e1f3000 -     0x7fff8e1f4fff  libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib
-    0x7fff8e23c000 -     0x7fff8e23cffd  com.apple.audio.units.AudioUnit (1.9 - 1.9) <EC55FB59-2443-3F08-9142-7BCC93C76E4E> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
-    0x7fff8e23d000 -     0x7fff8e30fff7  com.apple.CoreText (260.0 - 275.16) <5BFC1D67-6A6F-38BC-9D90-9C712684EDAC> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
-    0x7fff8e310000 -     0x7fff8e31eff7  libkxld.dylib (2050.24.15) <A619A9AC-09AF-3FF3-95BF-F07CC530EC31> /usr/lib/system/libkxld.dylib
-    0x7fff8e31f000 -     0x7fff8e38dff7  com.apple.framework.IOKit (2.0.1 - 755.24.1) <04BFB138-8AF4-310A-8E8C-045D8A239654> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
-    0x7fff8e39f000 -     0x7fff8e525fff  libBLAS.dylib (1073.4) <C102C0F6-8CB6-3B49-BA6B-2EB61F0B2784> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
-    0x7fff8e553000 -     0x7fff8e597fff  libcups.2.dylib (327.6) <9C01D012-6F4C-3B69-B614-1B408B0ED4E3> /usr/lib/libcups.2.dylib
-    0x7fff8e598000 -     0x7fff8e5a6fff  libcommonCrypto.dylib (60027) <BAAFE0C9-BB86-3CA7-88C0-E3CBA98DA06F> /usr/lib/system/libcommonCrypto.dylib
-    0x7fff8e6fa000 -     0x7fff8e70fff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
-    0x7fff8e710000 -     0x7fff8e71eff7  libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
-    0x7fff8e71f000 -     0x7fff8e741ff7  com.apple.Kerberos (2.0 - 1) <C49B8820-34ED-39D7-A407-A3E854153556> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
-    0x7fff8e788000 -     0x7fff8e797ff7  libxar.1.dylib (105) <370ED355-E516-311E-BAFD-D80633A84BE1> /usr/lib/libxar.1.dylib
-    0x7fff8f144000 -     0x7fff8f1d1ff7  com.apple.SearchKit (1.4.0 - 1.4.0) <C7F43889-F8BF-3CB9-AD66-11AEFCBCEDE7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
-    0x7fff8f24c000 -     0x7fff8f24ffff  libRadiance.dylib (850) <62E3F7FB-03E3-3937-A857-AF57A75EAF09> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
-    0x7fff8f533000 -     0x7fff8f7d7ff7  com.apple.CoreImage (8.4.0 - 1.0.1) <CC6DD22B-FFC6-310B-BE13-2397A02C79EF> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage
-    0x7fff8f7d8000 -     0x7fff8f840fff  libvDSP.dylib (380.6) <CD4C5EEB-9E63-30C4-8103-7A5EAEA0BE60> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
-    0x7fff8f8ab000 -     0x7fff8f8affff  libpam.2.dylib (20) <C8F45864-5B58-3237-87E1-2C258A1D73B8> /usr/lib/libpam.2.dylib
-    0x7fff8fabb000 -     0x7fff8fb28ff7  com.apple.datadetectorscore (4.1 - 269.3) <5775F0DB-87D6-310D-8B03-E2AD729EFB28> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
-    0x7fff8fc60000 -     0x7fff8fcbcff7  com.apple.Symbolication (1.3 - 93) <97F3B1D2-D81D-3F37-87B3-B9A686124CF5> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
-    0x7fff8fd91000 -     0x7fff8fe6bfff  com.apple.backup.framework (1.4.3 - 1.4.3) <6B65C44C-7777-3331-AD9D-438D10AAC777> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
-    0x7fff8fe6c000 -     0x7fff8fe79fff  libbz2.1.0.dylib (29) <CE9785E8-B535-3504-B392-82F0064D9AF2> /usr/lib/libbz2.1.0.dylib
-    0x7fff8fe89000 -     0x7fff8ffdbfff  com.apple.audio.toolbox.AudioToolbox (1.9 - 1.9) <62770C0F-5600-3EF9-A893-8A234663FFF5> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
-    0x7fff90071000 -     0x7fff90173fff  libJP2.dylib (850) <2E43216C-3A5A-3693-820C-38B360698FA0> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
-    0x7fff90ab4000 -     0x7fff90b79ff7  com.apple.coreui (2.0 - 181.1) <83D2C92D-6842-3C9D-9289-39D5B4554C3A> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
-    0x7fff90e1a000 -     0x7fff90e1bfff  liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib
-    0x7fff90f20000 -     0x7fff90fddff7  com.apple.ColorSync (4.8.0 - 4.8.0) <6CE333AE-EDDB-3768-9598-9DB38041DC55> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
-    0x7fff90fde000 -     0x7fff9105dff7  com.apple.securityfoundation (6.0 - 55115.4) <8676E0DF-295F-3690-BDAA-6C9C1D210B88> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
-    0x7fff9105e000 -     0x7fff910b4fff  com.apple.HIServices (1.20 - 417) <BCD36950-013F-35C2-918E-05A93A47BE8C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
-    0x7fff910b5000 -     0x7fff910d6fff  com.apple.Ubiquity (1.2 - 243.15) <C9A7EE77-B637-3676-B667-C0843BBB0409> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity
-    0x7fff910de000 -     0x7fff91133ff7  libTIFF.dylib (850) <EDAF0D99-70AF-3B3F-9EFA-9463C91D0E3C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
-    0x7fff9125c000 -     0x7fff9127cfff  libPng.dylib (850) <203C43BF-FAD3-3CCB-81D5-F2770E36338B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
-    0x7fff9127f000 -     0x7fff91398fff  com.apple.ImageIO.framework (3.2.1 - 850) <C3FFCEEB-AA0C-314B-9E94-7005EE48A403> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
-    0x7fff9139f000 -     0x7fff913b6fff  com.apple.GenerationalStorage (1.1 - 132.3) <FD4A84B3-13A8-3C60-A59E-25A361447A17> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
-    0x7fff91582000 -     0x7fff91586fff  libCoreVMClient.dylib (32.3) <AD8391D9-56DD-3A78-A294-6A30E6ECE1A2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
-    0x7fff91587000 -     0x7fff915bdfff  com.apple.DebugSymbols (98 - 98) <14E788B1-4EB2-3FD7-934B-849534DFC198> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
-    0x7fff915cd000 -     0x7fff915d5fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
-    0x7fff915d6000 -     0x7fff915e1fff  libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
-    0x7fff91650000 -     0x7fff917ebfef  com.apple.vImage (6.0 - 6.0) <FAE13169-295A-33A5-8E6B-7C2CC1407FA7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
-    0x7fff917ec000 -     0x7fff917f4ff7  libsystem_dnssd.dylib (379.38.1) <BDCB8566-0189-34C0-9634-35ABD3EFE25B> /usr/lib/system/libsystem_dnssd.dylib
-    0x7fff9182d000 -     0x7fff91938fff  libFontParser.dylib (84.6) <96C42E49-79A6-3475-B5E4-6A782599A6DA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
-    0x7fff919d8000 -     0x7fff919ddfff  libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib
-    0x7fff919de000 -     0x7fff919defff  com.apple.vecLib (3.8 - vecLib 3.8) <794317C7-4E38-338A-A874-5E18001C8503> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
-    0x7fff919df000 -     0x7fff91cb0ff7  com.apple.security (7.0 - 55179.13) <F428E306-C407-3B55-BA82-E58755E8A76F> /System/Library/Frameworks/Security.framework/Versions/A/Security
-    0x7fff91d3f000 -     0x7fff9206ffff  com.apple.HIToolbox (2.0 - 626.1) <656D08C2-9068-3532-ABDD-32EC5057CCB2> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
-    0x7fff92084000 -     0x7fff920deff7  com.apple.opencl (2.2.19 - 2.2.19) <3C7DFB2C-B3F9-3447-A1FC-EAAA42181A6E> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
-    0x7fff9216c000 -     0x7fff9216dff7  libremovefile.dylib (23.2) <6763BC8E-18B8-3AD9-8FFA-B43713A7264F> /usr/lib/system/libremovefile.dylib
-    0x7fff9312e000 -     0x7fff93149ff7  libsystem_kernel.dylib (2050.24.15) <A9F97289-7985-31D6-AF89-151830684461> /usr/lib/system/libsystem_kernel.dylib
-    0x7fff9314d000 -     0x7fff9326dfff  com.apple.desktopservices (1.7.4 - 1.7.4) <ED3DA8C0-160F-3CDC-B537-BF2E766AB7C1> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
-
-External Modification Summary:
-  Calls made by other processes targeting this process:
-    task_for_pid: 1
-    thread_create: 0
-    thread_set_state: 0
-  Calls made by this process:
-    task_for_pid: 0
-    thread_create: 0
-    thread_set_state: 0
-  Calls made by all processes on this machine:
-    task_for_pid: 168404
-    thread_create: 1
-    thread_set_state: 0
-
-VM Region Summary:
-ReadOnly portion of Libraries: Total=109.3M resident=31.8M(29%) swapped_out_or_unallocated=77.5M(71%)
-Writable regions: Total=90.9M written=16.1M(18%) resident=17.5M(19%) swapped_out=0K(0%) unallocated=73.4M(81%)
- 
-REGION TYPE                      VIRTUAL
-===========                      =======
-MALLOC                             62.5M
-MALLOC guard page                    48K
-STACK GUARD                        56.0M
-Stack                              12.6M
-VM_ALLOCATE                        12.0M
-__DATA                             13.8M
-__IMAGE                             528K
-__LINKEDIT                         58.6M
-__TEXT                            134.3M
-__UNICODE                           544K
-shared memory                       308K
-===========                      =======
-TOTAL                             351.2M
-
-Model: MacBookPro10,1, BootROM MBP101.00EE.B03, 4 processors, Intel Core i7, 2.8 GHz, 16 GB, SMC 2.3f35
-Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB
-Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
-Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
-Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
-AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.98.100.17)
-Bluetooth: Version 4.1.4f2 12041, 2 service, 18 devices, 1 incoming serial ports
-Network Service: Wi-Fi, AirPort, en0
-Serial ATA Device: APPLE SSD SM768E, 751.28 GB
-USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2
-USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8510, 0x1a110000 / 3
-USB Device: USB Receiver, 0x046d  (Logitech Inc.), 0xc52b, 0x14200000 / 1
-USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2
-USB Device: hub_device, 0x0424  (SMSC), 0x2512, 0x1d180000 / 3
-USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0262, 0x1d182000 / 5
-USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 4
-USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8286, 0x1d181300 / 6
-
-# End of transcript or log.
-"""]]
-
-> This got fixed in haskell gnutls 0.1.5. I have updated the Mtn Lion
-> autobuilder and it will be in tonight's build. [[done]]
-> --[[Joey]] 
diff --git a/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_1_97abb8442329d19c9687002f43afac74._comment b/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_1_97abb8442329d19c9687002f43afac74._comment
deleted file mode 100644
index 4dcc5412c..000000000
--- a/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_1_97abb8442329d19c9687002f43afac74._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 1"
- date="2013-08-26T19:51:48Z"
- content="""
-So this is a crash in the gnutls library used for XMPP. Someone else using OSX reported a similar crash to me by email, reproducible reliably by setting up xmpp with google. This is great debugging info:
-
-<pre>
-Thread 3 Crashed:
-0   libsystem_c.dylib               0x00007fff86ae0bf9 pthread_mutex_lock + 20
-1   H                               0x000000010e9fd29f gnutls_system_mutex_lock + 12
-2   H                               0x000000010ea7fa29 wrap_nettle_rnd_refresh + 20
-3   H                               0x000000010e9fee89 gnutls_deinit + 42
-4   git-annex                       0x000000010caf0a3a 0x10b5e6000 + 22063674
-</pre>
-
-Looks like `gnutls_deinit` was called and it crashed there, inside pthread code. So I think git-annex has already managed to connect to the XMPP server (to test it) and the cleanup is where it's crashing.
-
-This is the second time I have seen a gnutls-related crash using XMPP. The other one was tracked down by John Millikin to a resource allocation bug in haskell-gnutls and fixed. 
-
-I have written a test case that reproduces the problem -- just forking a dozen threads that each try to connect to the google xmpp server and then close the connection. After a dozen or so succeed, one will reliably cause a segfault. Forwarded this test case to John.
-"""]]
diff --git a/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_2_3405f3cd699860ee239cf23ade19e92c._comment b/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_2_3405f3cd699860ee239cf23ade19e92c._comment
deleted file mode 100644
index 18b2b7a52..000000000
--- a/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_2_3405f3cd699860ee239cf23ade19e92c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.7"
- subject="comment 2"
- date="2013-08-29T18:15:08Z"
- content="""
-I now have a test case that shows that this can happen reliably on OSX if you enter the wrong XMPP password repeatedly. It might also happen if you just enter the wrong password once, with a server like google's, since the assistant will try falling back to different servers. John is aware of this haskell-gnutls problem.
-
-John also found, and we hope fixed (but it's hard to tell) a bug in haskell-gnutls that caused a crash maybe 1 time in 10 under some conditions on OSX, when the right password was entered.
-"""]]
diff --git a/doc/bugs/git-annex_sync_broken_on_squeeze_backports.mdwn b/doc/bugs/git-annex_sync_broken_on_squeeze_backports.mdwn
deleted file mode 100644
index 4e307fd68..000000000
--- a/doc/bugs/git-annex_sync_broken_on_squeeze_backports.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-What steps will reproduce the problem?
-
-    git-annex sync
-
-What is the expected output? What do you see instead?
-
-The following error is mixed in with the output, took me a while to notice it:
-
-    Running: git ["--git-dir=/spare/annex/.git","--work-tree=/spare/annex","merge","--no-edit","refs/remotes/pip/synced/master"] 
-    error: unknown option `no-edit'
-
-What version of git-annex are you using? On what operating system?
-
-3.20120629~bpo60+1 on debian squeeze
-
-Please provide any additional information below.
-
-Installing git from backports as well cleared up the problem.
-
-> Uploading a fix for this now. [[done]] Thanks for reporting. --[[Joey]] 
diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn
deleted file mode 100644
index cf54eea85..000000000
--- a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-###What steps will reproduce the problem?
-
-1. Start git annex webapp, and make new repository on two computers.
-1. Pair them as "Local computer"s, and they synchronize fine, a file created on one shows up on the other.
-1. Disconnect one of the computers from the network, and create a new file
-1. Check where the file is.
-
-###What is the expected output? What do you see instead?
-
-    git annex whereis new file
-
-shows the file being in both repositories, when in fact it has had no chance to get added to the one on the other computer, and is not in it.
-
-
-###What version of git-annex are you using? On what operating system?
-
-Both 4.20130405 on Ubuntu 12.10
-
-###Please provide any additional information below.
-
-I noticed this first when using a USB drive to communicate between work and home. Making changes at home, it thought that the new files were now present at work, when the computer there is off, and a long way away.
---Walter
-
-> A little while ago, I made this change:
-
-  * direct mode: Direct mode commands now work on files staged in the index,
-    they do not need to be committed to git.
-
-> I think that fixes the confusing behavior described here. [[done]] --[[Joey]] 
diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_1_6722fd627ec4add9f2b16546bd8ef341._comment b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_1_6722fd627ec4add9f2b16546bd8ef341._comment
deleted file mode 100644
index fa8053660..000000000
--- a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_1_6722fd627ec4add9f2b16546bd8ef341._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-16T19:26:49Z"
- content="""
-Please show me the full output of `git annex whereis`, and also the contents of `.git/config`
-"""]]
diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_2_508e475f764e1cb453b756eb50bc3a15._comment b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_2_508e475f764e1cb453b756eb50bc3a15._comment
deleted file mode 100644
index c6fea0dbf..000000000
--- a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_2_508e475f764e1cb453b756eb50bc3a15._comment
+++ /dev/null
@@ -1,34 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ"
- nickname="Walter"
- subject="comment 2"
- date="2013-04-16T20:25:45Z"
- content="""
-    walter@dionysus:~/presence$ echo 1 > Here.txt
-    walter@dionysus:~/presence$ git annex whereis
-    whereis Here.txt (2 copies) 
-        1c6ffc98-d12c-4844-920b-5e28bc8e8b60 -- here (walter@dionysus:~/presence)
-        8da299b6-006c-4410-9b3d-a542766d40a4 -- kronos.local_presence (walter@kronos:~/presence)
-    ok
-
-This is while kronos is turned off.
-
-The contents of .git/config:
-
-    [core]
-    	repositoryformatversion = 0
-    	filemode = true
-    	bare = false
-    	logallrefupdates = true
-    [annex]
-    	uuid = 1c6ffc98-d12c-4844-920b-5e28bc8e8b60
-    	version = 3
-    	direct = true
-    [gc]
-    	auto = 0
-    [remote \"kronos.local_presence\"]
-    	url = ssh://walter@git-annex-kronos.local-walter/~/presence/
-    	fetch = +refs/heads/*:refs/remotes/kronos.local_presence/*
-    	annex-uuid = 8da299b6-006c-4410-9b3d-a542766d40a4
-        	annex-cost = 175.0
-"""]]
diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_3_1656ba18c519a262c57ef626a3449e77._comment b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_3_1656ba18c519a262c57ef626a3449e77._comment
deleted file mode 100644
index 3a33becb8..000000000
--- a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_3_1656ba18c519a262c57ef626a3449e77._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-16T20:33:44Z"
- content="""
-> walter@dionysus:~/presence$ echo 1 > Here.txt
-> walter@dionysus:~/presence$ git annex whereis
-> whereis Here.txt (2 copies)
-
-It seems the file Here.txt must already have been added to git-annex before this point ... or whereis would not show it. Did you leave out a step? Was the file already added? Are you using direct mode?
-"""]]
diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_4_347dc3b6e5bc6c4195ec09d54bc1398e._comment b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_4_347dc3b6e5bc6c4195ec09d54bc1398e._comment
deleted file mode 100644
index 2fc2b573d..000000000
--- a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_4_347dc3b6e5bc6c4195ec09d54bc1398e._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ"
- nickname="Walter"
- subject="comment 4"
- date="2013-04-16T20:42:34Z"
- content="""
-The repository is a direct mode one.
-
-I think there's something in your comment though; the content (\"1\") had already been added to a file (since deleted on dionysus),
-however it does seem a bit inconsistent.
-
-    walter@dionysus:~/presence$ echo 1 > New1
-    walter@dionysus:~/presence$ echo 1 > New1.txt
-    walter@dionysus:~/presence$ git annex whereis New1 New1.txt
-    whereis New1 (1 copy) 
-      	1c6ffc98-d12c-4844-920b-5e28bc8e8b60 -- here (walter@dionysus:~/presence)
-    ok
-    whereis New1.txt (2 copies) 
-       	1c6ffc98-d12c-4844-920b-5e28bc8e8b60 -- here (walter@dionysus:~/presence)
-       	8da299b6-006c-4410-9b3d-a542766d40a4 -- kronos.local_presence (walter@kronos:~/presence)
-    ok
-
-
-"""]]
diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_5_a9c93bfc3278ef8b1117eac2af859bc3._comment b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_5_a9c93bfc3278ef8b1117eac2af859bc3._comment
deleted file mode 100644
index aa08f6024..000000000
--- a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_5_a9c93bfc3278ef8b1117eac2af859bc3._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-04-16T21:25:45Z"
- content="""
-In a direct mode repository, until you commit changes to a file, `git annex whereis` and most other git-annex commands will operate on the version that was last committed to git.
-
-That seems to be the source of your confusion.
-
-I think this can be confusing.. It might make sense for git-annex whereis to skip over modified files in direct mode.
-"""]]
diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_6_804dd62beef64f7d4e203bdb28cbe660._comment b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_6_804dd62beef64f7d4e203bdb28cbe660._comment
deleted file mode 100644
index 1cb046af9..000000000
--- a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_6_804dd62beef64f7d4e203bdb28cbe660._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ"
- nickname="Walter"
- subject="comment 6"
- date="2013-04-16T22:40:04Z"
- content="""
-I am running the webapp, and thought that changes get made immediately?
-Especially, these are files that I never manually commit/add/anything, and are not modified after creation even.
-
-Specifically, in my previous comment, files New1 and New1.txt are (to my eyes) created and treated identically, yet `git annex whereis` gives different results.
-"""]]
diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_7_4ef107d70647780eb5347cae6f467fed._comment b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_7_4ef107d70647780eb5347cae6f467fed._comment
deleted file mode 100644
index f7ca0a5af..000000000
--- a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_7_4ef107d70647780eb5347cae6f467fed._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ"
- nickname="Walter"
- subject="comment 7"
- date="2013-04-17T20:50:34Z"
- content="""
-So looking in .git/annex/objects, it is obvious that the difference between New1 and New1.txt is the extension.
-
-So, I think that explains all the things I was seeing. I guess the main point of confusion (though I can't think of a better way) is the distinction between data stored in .git/annex/objects, and files in the working folder.
-If I thought in terms of hashes, that is all that would need to be shown in git annex whereis is which hashes are where (and then it would be obvious if several files have the same hash, that once one of them is present somewhere then all of them are).
-
-"""]]
diff --git a/doc/bugs/git-repair_real_world_failure_example.mdwn b/doc/bugs/git-repair_real_world_failure_example.mdwn
deleted file mode 100644
index f7110dcc0..000000000
--- a/doc/bugs/git-repair_real_world_failure_example.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-I was given these 2 repos, git-repair fails on the first, and the
-second is a backup copy from before the problem:
-
-* <http://www.clacke.se/annex/podcasts.git.tar.xz>
-* <http://www.clacke.se/annex/podcasts-bak.git.tar.xz>
-
---[[Joey]]
-
-> Tested with current version, and it successfully repairs. 
-> Bug reporter was using an older version (based on some old messages).
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_add_..._adds_too_much.mdwn b/doc/bugs/git_annex_add_..._adds_too_much.mdwn
deleted file mode 100644
index 4eb46455f..000000000
--- a/doc/bugs/git_annex_add_..._adds_too_much.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-When a hidden file (starting with a dot) is git-annex add'ed, other non-tracked files are also added 
-
-What steps will reproduce the problem?
-
-$ touch a .b
-
-$ git annex add .b
-
-add a (checksum...) ok
-
-add .b (checksum...) ok
-
-(Recording state in git...)
-
-
-What is the expected output? What do you see instead?
-
-Only file .b should be added.
-
-What version of git-annex are you using? On what operating system?
-
-3.20120406
-(same problem with version 3.20120123) on Debian.
-
-> Thanks for reporting this bug, I've fixed it in git. [[done]] --[[Joey]] 
diff --git a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long.mdwn b/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long.mdwn
deleted file mode 100644
index d17e569f1..000000000
--- a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-Recently I ran into the following situation under Ubuntu with an encrypted home directory (which shortens the length that filenames can be):
-
-    $ git annex add 687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif
-    add 687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif failed
-    git-annex: /home/lhuhn/annex/.git/annex/tmp/155_518_WORM-s426663-m1310064100--687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif.log: openBinaryFile: invalid argument (File name too long)
-    git-annex: 1 failed
-
-The file seems to be completely gone.  It no longer exists in the current directory, or under .git/annex.
-
-I don't mind horribly that git-annex failed due to the name length limit, but it shouldn't have deleted my file in the process (fortunately the file wasn't very important, or hard to recover).
-
-> [[done]], as noted it did not delete content and now it makes the symlink
-> before trying to write to the location log, avoiding that gotcha.
-> --[[Joey]] 
diff --git a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_1_9650284913bec2a00cf551b90ab5d8ff._comment b/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_1_9650284913bec2a00cf551b90ab5d8ff._comment
deleted file mode 100644
index 1df159181..000000000
--- a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_1_9650284913bec2a00cf551b90ab5d8ff._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-07-07T20:27:33Z"
- content="""
-When I reproduce this, the file is not gone, it's been moved under .git/annex/objects. There is no way an add can delete a file, since all it does is rename it. It would be good for it to error unwind and move the file back though.
-
-<pre>
-joey@gnu:~/tmp/a>touch 663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif
-joey@gnu:~/tmp/a>git annex add *.gif
-add 663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif failed
-git-annex: /home/joey/tmp/a/.git/annex/tmp/8e2_6a4_WORM-s0-m1310069979--663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif.log: openBinaryFile: invalid argument (File name too long)
-joey@gnu:~/tmp/a>touch 663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif
-joey@gnu:~/tmp/a>git annex add *.gif
-add 663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif failed
-git-annex: /home/joey/tmp/a/.git/annex/tmp/8e2_6a4_WORM-s0-m1310069979--663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif.log: openBinaryFile: invalid argument (File name too long)
-joey@gnu:~/tmp/a>find .git/annex/objects -type f
-.git/annex/objects/Mk/92/WORM-s0-m1310069979--663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif/WORM-s0-m1310069979--663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966687474703a2f2f6d656469612e74756d626c722e636f6d2f74756d626c725f6c656673756557324c703171663879656b2e676966.gif
-</pre>
-"""]]
diff --git a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_2_c6c8d2a1f444d85c582bc5396b08e148._comment b/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_2_c6c8d2a1f444d85c582bc5396b08e148._comment
deleted file mode 100644
index bd53627bb..000000000
--- a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_2_c6c8d2a1f444d85c582bc5396b08e148._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnpdM9F8VbtQ_H5PaPMpGSxPe_d5L1eJ6w"
- nickname="Rafaël"
- subject="this happens also when the user has not the permission to set the file mode"
- date="2011-07-08T00:21:31Z"
- content="""
-For example if the file is owned by root, I guess git-annex fails when it tries to remove write permissions (I retested with the last version of today (whose \"version\" subcommand still outputs 3.20110702)).By the way, it would be nice to have a log file created containing the list of all failures, to avoid having to scan manually all the output of a long git-annex operation.
-"""]]
diff --git a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_3_5776864d78d56849001dd12e3adb9cbe._comment b/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_3_5776864d78d56849001dd12e3adb9cbe._comment
deleted file mode 100644
index f9d1b5d68..000000000
--- a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_3_5776864d78d56849001dd12e3adb9cbe._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnpdM9F8VbtQ_H5PaPMpGSxPe_d5L1eJ6w"
- nickname="Rafaël"
- subject="comment 3"
- date="2011-07-08T00:45:30Z"
- content="""
-comment on the output of 'git-annex version' (from my last comment): now I get the right version 3.20110707. But I checked in my console that the three commands \"git checkout 3.20110707\", \"make\" and \"./git-annex version\" gave me before 3.20110702, I don't know why...
-"""]]
diff --git a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_4_371ec7b4ae73280ede31edfe90b42a95._comment b/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_4_371ec7b4ae73280ede31edfe90b42a95._comment
deleted file mode 100644
index 1ba57c199..000000000
--- a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_4_371ec7b4ae73280ede31edfe90b42a95._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 4"
- date="2011-07-08T01:32:30Z"
- content="""
-Indeed, I've made it even more robust now, handling the case where the file has weird permissions too, and undoing the failed add so the file is always back at the start state. Had to add a dependency on another haskell module to allow this, so it took some time to figure out how to do it..
-
-"""]]
diff --git a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_5_4fb04f646de591640f8504c0caf61acd._comment b/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_5_4fb04f646de591640f8504c0caf61acd._comment
deleted file mode 100644
index 3ece2646f..000000000
--- a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_5_4fb04f646de591640f8504c0caf61acd._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="ckeen"
- ip="79.249.110.228"
- subject="Maybe related to this bug?"
- date="2013-07-30T14:50:35Z"
- content="""
-I have noticed similar behaviour with the importfeed command: [[tips/downloading_podcasts/#comment-3e448e43830be7e6dbe59fff6bc81e75]]
-
-After the import fails, the symlinks are created and subsequent get command return with no ouput and error code 0.
-
-Or is this a different bug?
-"""]]
diff --git a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_6_b4055409fe48da95bb3101c0242ef0bc._comment b/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_6_b4055409fe48da95bb3101c0242ef0bc._comment
deleted file mode 100644
index bfdc3bcf9..000000000
--- a/doc/bugs/git_annex_add_eats_files_when_filename_is_too_long/comment_6_b4055409fe48da95bb3101c0242ef0bc._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.21"
- subject="comment 6"
- date="2013-07-30T17:18:15Z"
- content="""
-This is an unrelated bug that was fixed 2 years ago.
-"""]]
diff --git a/doc/bugs/git_annex_add_error_with_Andrew_File_System.mdwn b/doc/bugs/git_annex_add_error_with_Andrew_File_System.mdwn
deleted file mode 100644
index bdddd96e2..000000000
--- a/doc/bugs/git_annex_add_error_with_Andrew_File_System.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-I have a git annex clone on Andrew File System. I obtain an error when I try
-to add a file to the annex:
-
-git-annex: test: createLink: unsupported operation (Invalid cross-device link)
-
-### What steps will reproduce the problem?
-Create a test file with touch and add it with git annex add.
-
-### What version of git-annex are you using? On what operating system?
-git-annex 4.20130723 on Debian sid.
-
-### Please provide any additional information below.
-
-[[!format sh """
-gio@crack:~/nobackup/archive$ touch test
-gio@crack:~/nobackup/archive$ git annex add test
-add test 
-git-annex: test: createLink: unsupported operation (Invalid cross-device link)
-failed
-git-annex: add: 1 failed
-gio@crack:~/nobackup/archive$ logout
-"""]]
-
-It seems to me that AFS doesn't support hard links between different
-directories.
-
-> [[done]] per comments --[[Joey]] 
diff --git a/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_1_bc783e551fc0e8da87bc95bff5b8f73a._comment b/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_1_bc783e551fc0e8da87bc95bff5b8f73a._comment
deleted file mode 100644
index 7a0d15842..000000000
--- a/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_1_bc783e551fc0e8da87bc95bff5b8f73a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~giomasce"
- nickname="giomasce"
- subject="Reference"
- date="2013-08-12T11:39:44Z"
- content="""
-https://lists.openafs.org/pipermail/openafs-info/2007-December/028158.html
-"""]]
diff --git a/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_2_faefcf69bd61c47566131cb31b78cc19._comment b/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_2_faefcf69bd61c47566131cb31b78cc19._comment
deleted file mode 100644
index a2301499c..000000000
--- a/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_2_faefcf69bd61c47566131cb31b78cc19._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 2"
- date="2013-08-24T19:48:46Z"
- content="""
-I'm confused by this bug report, because it seems to me I already fixed this same problem in commit a64106dcef5c5aad825662ef115cb2a1cc6985a8. There the problem was that encfs in paranoia mode doesn't support hard links. So I made it detect when createLink fails, and fall back to a code path that doesn't need hard links.
-
-Can you re-check the version you have, and perhaps try with a current daily build?
-"""]]
diff --git a/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_3_d5014c8b78437b9fddbb1e83d3679081._comment b/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_3_d5014c8b78437b9fddbb1e83d3679081._comment
deleted file mode 100644
index 3d30cea41..000000000
--- a/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_3_d5014c8b78437b9fddbb1e83d3679081._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~giomasce"
- nickname="giomasce"
- subject="comment 3"
- date="2013-09-07T15:35:48Z"
- content="""
-Apparently I wrote a wrong version number. The version actually running on the system I tested is much older. Probably I wrote the one of my own laptop instead.
-
-The bug can be closed, sorry for the noise.
-"""]]
diff --git a/doc/bugs/git_annex_add_memory_leak.mdwn b/doc/bugs/git_annex_add_memory_leak.mdwn
deleted file mode 100644
index 4bcffb17b..000000000
--- a/doc/bugs/git_annex_add_memory_leak.mdwn
+++ /dev/null
@@ -1,39 +0,0 @@
-For the record, `git annex add` has had a series of memory leaks.
-Mostly these are minor -- until you need to check in a few
-million files in a single operation. 
-
-If this happens to you, git-annex will run out of memory and stop.
-(Generally well before your system runs out of memory, since it has some
-built-in ulimits.) You can recover by just re-running the `git annex add`
--- it will automatically pick up where it left off.
-
-A history of the leaks:
-
-* Originally, `git annex add` remembered all the files
-  it had added, and fed them to git at the end. Of course
-  that made its memory use grow, so it was fixed to periodically
-  flush its buffer. Fixed in version 0.20110417.
-
-* Something called a "lazy state monad" caused "thunks" to build
-  up and memory to leak. Also affected other git annex commands
-  than `add`. Adding files using a SHA* backend hit the worst.
-  Fixed in versions afer 3.20120123.
-
-* Committing journal files turned out to have another memory leak.
-  After adding a lot of files ran out of memory, this left the journal
-  behind and could affect other git-annex commands. Fixed in versions afer
-  3.20120123.
-
-* The count of the number of failed commands was updated lazily, which
-  caused a slow leak when running on a lot of files. Fixed in versions afer
-  3.20120123.
-
-* (Note that `git ls-files --others`, which is used to find files to add,
-  also uses surpsisingly large amounts
-  of memory when you have a lot of files. It buffers
-  the entire list, so it can compare it with the files in the index,
-  before outputting anything.
-  This is Not Our Problem, but I'm sure the git developers
-  would appreciate a patch that fixes it.)
-
-[[done]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left.mdwn b/doc/bugs/git_annex_add_removes_file_with_no_data_left.mdwn
deleted file mode 100644
index 0256c8476..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left.mdwn
+++ /dev/null
@@ -1,103 +0,0 @@
-### Please describe the problem.
-Using git-annex from Debian (4.20130709), I attempted to add a 410M file named `Expressionlessm.tar`. It acted like it succeeded, but the link it created was broken. Other files would add correctly.
-
-### What steps will reproduce the problem?
-I can reliably cause the file to be removed and replaced with a dangling symlink by doing `git annex add Expressionlessm.tar`. The "addition" completes much faster than normal. Using the old version of git-annex that Ubuntu provides (3.20131112ubuntu4), the file adds correctly in at least one place it was having issues.
-
-### What version of git-annex are you using? On what operating system?
-I'm using the version of git-annex from Debian Sid on Ubuntu 13.04 (perhaps that's my issue?)
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-andrew@andrew-desktop:/media/MainStore/Projects$ git status
-# On branch master
-# Untracked files:
-#   (use "git add <file>..." to include in what will be committed)
-#
-==========Snip!=================
-nothing added to commit but untracked files present (use "git add" to track)
-
-
-
-andrew@andrew-desktop:/media/MainStore/Projects$ ls
-==========Snip!=================
-Expressionlessm.tar
-Expressionlessm.tar.bkup
-==========Snip!=================
-
-
-
-andrew@andrew-desktop:/media/MainStore/Projects$ tar tf Expressionlessm.tar 
-Expressionlessm/
-==========Snip!=================
-# Tar file is valid at this point
-
-
-andrew@andrew-desktop:/media/MainStore/Projects$ git annex add Expressionlessm.tar
-add Expressionlessm.tar ok
-(Recording state in git...)
-
-
-
-andrew@andrew-desktop:/media/MainStore/Projects$ ls
-==========Snip!=================
-Expressionlessm.tar
-Expressionlessm.tar.bkup
-==========Snip!=================
-
-
-
-andrew@andrew-desktop:/media/MainStore/Projects$ ls -l
-==========Snip!=================
-lrwxrwxrwx 1 andrew andrew       109 Jul 12 02:29 Expressionlessm.tar -> ../.git/annex/objects/vk/mF/SHA256-s3131909--a2808d850ba2e880ac58bf622cd68edd7e72ea2775b984d52b5d5266c43b03f0
--rw-rw-r-- 1 andrew andrew 428759040 Jul 10 20:30 Expressionlessm.tar.bkup
-==========Snip!=================
-
-
-
-andrew@andrew-desktop:/media/MainStore/Projects$ tar tf Expressionlessm.tar 
-tar: Expressionlessm.tar: Cannot open: No such file or directory
-tar: Error is not recoverable: exiting now
-
-
-=================================================================
-W O R K I N G   V E R S I O N
-This is what it looks like when the add works.
-=================================================================
-andrew@andrew-desktop:/media/MainStore/Projects$ cp Expressionlessm.tar.bkup Expressionlessm.tar
-andrew@andrew-desktop:/media/MainStore/Projects$ git annex add Expressionlessm.tar
-add Expressionlessm.tar (checksum...) ok
-(Recording state in git...)
-andrew@andrew-desktop:/media/MainStore/Projects$ git status
-# On branch master
-# Changes to be committed:
-#   (use "git reset HEAD <file>..." to unstage)
-#
-#	new file:   Expressionlessm.tar
-#
-# Untracked files:
-==========Snip!=================
-
-
-
-andrew@andrew-desktop:/media/MainStore/Projects$ ls -l
-==========Snip!=================
-lrwxrwxrwx 1 andrew andrew       195 Jul 12 02:20 Expressionlessm.tar -> ../.git/annex/objects/3v/Z7/SHA256-s428759040--133040f7b9d34ebce235aa24a0a16ab72af8f70e7a0722810d873815a2338eb2/SHA256-s428759040--133040f7b9d34ebce235aa24a0a16ab72af8f70e7a0722810d873815a2338eb2
--rw-rw-r-- 1 andrew andrew 428759040 Jul 10 20:30 Expressionlessm.tar.bkup
-==========Snip!=================
-# Notice the link target is different this time.
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; this bug is now prevented on several levels.
-> 
-> BTW, the earlier behavior where it didn't even make a valid .git/annex/objects/
-> symlink is also explained by this bug I've fixed. It pulled a truncated
-> link out of the tarball, and used that.
-> --[[Joey]] 
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_10_9cc749a6efd4359a99316036f5bc867f._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_10_9cc749a6efd4359a99316036f5bc867f._comment
deleted file mode 100644
index aa3d2c79b..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_10_9cc749a6efd4359a99316036f5bc867f._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="andy"
- ip="108.202.17.204"
- subject="comment 10"
- date="2013-07-20T23:50:50Z"
- content="""
-Wow! Thanks!
-
-I'd be happy to help test something if you need.
-
-Also, I just want to say that I really appreciate your openness about the process of fixing this, and that you so quickly deleted the part of the file you didn't need. It's not particularly sensitive, but I really like how you handled that. Thank you.
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_11_1fed5be9db29866e4dc3d3bb12907bf3._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_11_1fed5be9db29866e4dc3d3bb12907bf3._comment
deleted file mode 100644
index 95309dcf6..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_11_1fed5be9db29866e4dc3d3bb12907bf3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 11"
- date="2013-07-21T00:25:04Z"
- content="""
-I've updated the linux daily builds with this bug fix, so if you want to you can get the new standalone tarball and use that.
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_12_06d517ac4ef8def4629a40d7c3549bac._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_12_06d517ac4ef8def4629a40d7c3549bac._comment
deleted file mode 100644
index 30a6526f0..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_12_06d517ac4ef8def4629a40d7c3549bac._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="andy"
- ip="108.202.17.204"
- subject="comment 12"
- date="2013-07-21T04:47:33Z"
- content="""
-Thanks! Works great!
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_1_8f081aeba7065d143a453dc128543f59._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_1_8f081aeba7065d143a453dc128543f59._comment
deleted file mode 100644
index 89531ca16..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_1_8f081aeba7065d143a453dc128543f59._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 1"
- date="2013-07-18T19:37:33Z"
- content="""
-Sorry about the delay getting to this, I've been overloaded.
-
-The link that you show:
-
-`Expressionlessm.tar -> ../.git/annex/objects/vk/mF/SHA256-s3131909--a2808d850ba2e880ac58bf622cd68edd7e72ea2775b984d52b5d5266c`
-
-.. That's not right at all.  I don't understand in the least how this could happen, and am flummoxed how to try to debug it. It just doesn't match anything I know about how the code works.
-
-If I understand you correctly, it's only happening with one particular file content.
-
-I think you either need to rule out it being due to the way you've installed git-annex, perhaps by installing the linux standalone tarball, and seeing if you can get the same behavior with that. Or you could send me the repository by email (joey@kitenet.net) and I'll see if I can reproduce it, and if so, will certainly be able to debug and fix it.
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_2_54a4b10723fd8a80dd486377ff15ce0d._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_2_54a4b10723fd8a80dd486377ff15ce0d._comment
deleted file mode 100644
index 7ac34e751..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_2_54a4b10723fd8a80dd486377ff15ce0d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 2"
- date="2013-07-18T19:46:12Z"
- content="""
-Hmm, given the size of the repo, please don't email it directly, if you choose to do that. But getting me access to it would certainly be useful.
-
-
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_3_f1964e4e07991a251c2795da0361a4e2._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_3_f1964e4e07991a251c2795da0361a4e2._comment
deleted file mode 100644
index 68ca291d2..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_3_f1964e4e07991a251c2795da0361a4e2._comment
+++ /dev/null
@@ -1,28 +0,0 @@
-[[!comment format=mdwn
- username="andy"
- ip="108.202.17.204"
- subject="Further testing"
- date="2013-07-19T06:02:53Z"
- content="""
-I've just tried it again with the git-annex-standalone-amd64.tar.gz bundle. The problem seems to persist.
-
-I've got a typescript (with no timing info) of the problem occurring with the bundle that I could e-mail to you if it would be of any help. I could also get you the ~410M file that's having issues if you're interested. FWIW, its SHA256 according to `sha256sum` on Ubuntu is `133040f7b9d34ebce235aa24a0a16ab72af8f70e7a0722810d873815a2338eb2`.
-
-    andrew@andrew-desktop:/media/MainStore$ lsb_release -a
-    No LSB modules are available.
-    Distributor ID:	Ubuntu
-    Description:	Ubuntu 13.04
-    Release:    	13.04
-    Codename:   	raring
-
-
-
-	andrew@andrew-desktop:/media/MainStore/testspace$ ls -l
-	total 8
-	lrwxrwxrwx 1 andrew andrew 180 Jul 18 22:09 demofile -> .git/annex/objects/10/8J/SHA256E-s11--896769fb2f15d59f398863a11f3e0aaafac022bb99dfd6db34d7c78e1da307e3/SHA256E-s11--896769fb2f15d59f398863a11f3e0aaafac022bb99dfd6db34d7c78e1da307e3
-	lrwxrwxrwx 1 andrew andrew 188 Jul 18 22:10 express.tar -> .git/annex/objects/vk/mF/SHA256-s3131909--a2808d850ba2e880ac58bf622cd68edd7e72ea2775b984d52b5d5266c43b03f0/SHA256-s3131909--a2808d850ba2e880ac58bf622cd68edd7e72ea2775b984d52b5d5266c43b03f0
-
-
-Notice that the path to the file has changed from the version posted before.
---Andy
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_4_73c38d843c30f00f6fd8883db8e55f62._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_4_73c38d843c30f00f6fd8883db8e55f62._comment
deleted file mode 100644
index 9d68a431c..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_4_73c38d843c30f00f6fd8883db8e55f62._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 4"
- date="2013-07-20T19:54:59Z"
- content="""
-You don't seem to be getting the broken symlink when using the bundle. Is the symlink still not pointing to the content of the file?
-
-I do think I will need the file to debug further, unless you'd like to go on a possibly hundred step round-trip debugging sage with me.
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_5_7ede5ee312f3abdf78979c0d52a7871a._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_5_7ede5ee312f3abdf78979c0d52a7871a._comment
deleted file mode 100644
index ccf5e574f..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_5_7ede5ee312f3abdf78979c0d52a7871a._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="andy"
- ip="108.202.17.204"
- subject="comment 5"
- date="2013-07-20T21:34:08Z"
- content="""
-Yes, the symlink was still broken. Or rather, `tar -tf filename.tar` didn't like the file.
-
-The file's about 193 M bzipped. I'll be e-mailing you a link to an S3 copy with DojOsEf2 in the subject line of the email--once the upload finishes. :)
-
-I'm not sure if this is relevant, but the file is a tar of an annex and another git repo. Perhaps that is influencing something (although I presume it shouldn't)?
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_6_e37cf18708f09619442c3a9532d12ed9._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_6_e37cf18708f09619442c3a9532d12ed9._comment
deleted file mode 100644
index c1056de9e..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_6_e37cf18708f09619442c3a9532d12ed9._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 6"
- date="2013-07-20T22:43:27Z"
- content="""
-Got the file. Verified checksum.
-
-Reproduced bug!
-
-Wow, it really seems to be a bug specific to this one particular
-file content. That's crazy.
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_7_a744ef7dd3a224a911ebb24858bc2fd6._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_7_a744ef7dd3a224a911ebb24858bc2fd6._comment
deleted file mode 100644
index aa60ef2fc..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_7_a744ef7dd3a224a911ebb24858bc2fd6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 7"
- date="2013-07-20T23:00:59Z"
- content="""
-Can be reproduced with first 500kb of file. I have deleted all the rest of the file, without looking at it. (Scout's honor!)
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_8_f97141b255073b90120895148220c2d7._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_8_f97141b255073b90120895148220c2d7._comment
deleted file mode 100644
index 8bde55470..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_8_f97141b255073b90120895148220c2d7._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 8"
- date="2013-07-20T23:07:17Z"
- content="""
-Ok, it is in fact relevant that the file is a tarball of a git-annex repository, because git-annex add turns out to be looking at the beginning of the file, and seeing that it contains a git-annex link.
-
-I thought that code was only supposed to fire in repos on FAT filesystems that don't have symlinks. So, several issues to fix here, it seems..
-"""]]
diff --git a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment b/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment
deleted file mode 100644
index f7ae63cf8..000000000
--- a/doc/bugs/git_annex_add_removes_file_with_no_data_left/comment_9_dd2be11dfd190129d491f5f891e7cd1a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 9"
- date="2013-07-20T23:26:09Z"
- content="""
-Ok, I've put in 2 separate bug fixes, any one of which would have been sufficient to prevent this data loss. Am working on a third fix to detect this kind of problem at a higher level and avoid losing content even if it gets all confused.
-
-This bug may be a candidate to be backported to Debian stable, since it causes data loss.
-"""]]
diff --git a/doc/bugs/git_annex_assistant_--autostart_failed.mdwn b/doc/bugs/git_annex_assistant_--autostart_failed.mdwn
deleted file mode 100644
index 8833944ec..000000000
--- a/doc/bugs/git_annex_assistant_--autostart_failed.mdwn
+++ /dev/null
@@ -1,39 +0,0 @@
-**What steps will reproduce the problem?**
-
-Run *git annex assistant --autostart*
-
-    git-annex autostart in /home/tobru/annex/repo1
-    failed
-    git-annex autostart in /home/tobru/annex/repo2
-    failed
-    git-annex autostart in /home/tobru/annex/repo3
-    failed
-    git-annex autostart in /home/tobru/annex/repo4
-    failed
-    git-annex autostart in /home/tobru/annex/repo5
-    failed
-
-Running *git annex assistant* in each directory starts the assistant without errors.
-
-What could cause autostart to fail? Is there any log? Or a --debug parameter?
-
-
-**What is the expected output? What do you see instead?**
-
-The assistant should start on all known repositories
-
-**What version of git-annex are you using? On what operating system?**
-
-4.20130417-g4bb97d5 on Ubuntu
-
-**Please provide any additional information below.**
-
-The ~/.config/git-annex/autostart file looks like this:
-
-    /home/tobru/annex/repo1
-    /home/tobru/annex/repo2
-    /home/tobru/annex/repo3
-    /home/tobru/annex/repo4
-    /home/tobru/annex/repo5
-
-> Closing, seems local misconfiguration. --[[Joey]] [[done]]
diff --git a/doc/bugs/git_annex_assistant_--autostart_failed/comment_1_746545273b53849c42ff6272324e5155._comment b/doc/bugs/git_annex_assistant_--autostart_failed/comment_1_746545273b53849c42ff6272324e5155._comment
deleted file mode 100644
index 7267ec1c4..000000000
--- a/doc/bugs/git_annex_assistant_--autostart_failed/comment_1_746545273b53849c42ff6272324e5155._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-18T20:08:12Z"
- content="""
-The most likely cause of this error is a bad `~/.config/git-annex/program` file. Either the file is missing, or it points to the wrong location for the git-annex command. All that --autostart does is run the program listed on that file in each repository listed in the autostart file. Note that you don't need the file when git-annex is installed in your PATH.
-
-So, how did you install git-annex?
-"""]]
diff --git a/doc/bugs/git_annex_assistant_--autostart_failed/comment_2_5bdf6f94da12e551ae12e7f550a84d62._comment b/doc/bugs/git_annex_assistant_--autostart_failed/comment_2_5bdf6f94da12e551ae12e7f550a84d62._comment
deleted file mode 100644
index 6fb9fba9d..000000000
--- a/doc/bugs/git_annex_assistant_--autostart_failed/comment_2_5bdf6f94da12e551ae12e7f550a84d62._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawniayrgSdVLUc3c6bf93VbO-_HT4hzxmyo"
- nickname="Tobias"
- subject="comment 2"
- date="2013-04-19T06:48:39Z"
- content="""
-You're right, this files was the problem. I recently removed my manually downloaded standalone tarball and switched to use gitannex-install. So the path was not correct anymore... Thanks a lot for the hint!
-"""]]
diff --git a/doc/bugs/git_annex_assistant_--autostart_failed/comment_3_bfd646f69946a5fe926b270cf94f87cb._comment b/doc/bugs/git_annex_assistant_--autostart_failed/comment_3_bfd646f69946a5fe926b270cf94f87cb._comment
deleted file mode 100644
index e53a3115d..000000000
--- a/doc/bugs/git_annex_assistant_--autostart_failed/comment_3_bfd646f69946a5fe926b270cf94f87cb._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn26WQjIP5fnMgQF_L_k3Q3UrR5v8mjRTY"
- nickname="Ellis"
- subject="comment 3"
- date="2013-05-06T18:24:35Z"
- content="""
-I just had the exact same issue.  Thanks for posting the fix.
-"""]]
diff --git a/doc/bugs/git_annex_content_fails_with_a_parse_error.mdwn b/doc/bugs/git_annex_content_fails_with_a_parse_error.mdwn
deleted file mode 100644
index 38c8fa28d..000000000
--- a/doc/bugs/git_annex_content_fails_with_a_parse_error.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-### Please describe the problem.
-
-I tried to use git annex content, but that failed with a parse error.
-
-
-### What steps will reproduce the problem?
-
-Type this anywhere: 
-
-git annex --debug content . "exclude(foo.ml)"
-content . git-annex: Parse error: Parse failure: near "foo.ml"
-
-It fails with the example of the man page:
-   git annex content . "include(*.mp3) or include(*.ogg)"
-
-However, it works when trying: git annex content . "include()".
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130709.1, ubuntu quantal
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> Fixed the example, thanks. --[[Joey]] [[done]]
diff --git a/doc/bugs/git_annex_content_fails_with_a_parse_error/comment_1_2b60b6ae0115de13ecf837b34dadcd1d._comment b/doc/bugs/git_annex_content_fails_with_a_parse_error/comment_1_2b60b6ae0115de13ecf837b34dadcd1d._comment
deleted file mode 100644
index 75a157964..000000000
--- a/doc/bugs/git_annex_content_fails_with_a_parse_error/comment_1_2b60b6ae0115de13ecf837b34dadcd1d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="Matt"
- ip="78.251.139.64"
- subject="Correct syntax"
- date="2013-07-15T08:46:51Z"
- content="""
-After some digging, it turned out that the correct syntax is                git annex content . \"include=*.mp3 or include=*.ogg\". So it is more a documentation bug
-"""]]
diff --git a/doc/bugs/git_annex_copy_-f_REMOTE_._doesn__39__t_work_as_expected.mdwn b/doc/bugs/git_annex_copy_-f_REMOTE_._doesn__39__t_work_as_expected.mdwn
deleted file mode 100644
index 3bda45149..000000000
--- a/doc/bugs/git_annex_copy_-f_REMOTE_._doesn__39__t_work_as_expected.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-I was testing out the fix/workaround for [[git-annex directory hashing problems on osx]] and I tried using the short forms of some of the commands i.e.
-
-    git annex copy -f externalusb .
-
-which gives me
-
-    git-annex: user error (option `-f' is ambiguous; could be one of:
-      -f         --force        allow actions that may lose annexed data
-      -f REMOTE  --from=REMOTE  specify from where to transfer content
-
-
-I would have expected that since *--to* is the same as *-t* and *--from* is the same as *-f* as the in program documentation suggests. But *-f* clashes with the force command, I would suggest that the short form of *--force* be changed to *-F* and possibly rename the *Fast* commands to *Quick* and use *-Q* as the short form of the *Quick* operations. I didn't try the *-f* option with the move command, but it probably suffers from the same issue. It's probably better to avoid clashing short forms of command options.
-
-I guess this issue is just a documentation issue and a minor interface change if needed and not a bug of git-annex, but a quirk.
-
-> Yeah, -f needs to be from; -F was already --fast. I have made --force not
-> have any short option abbreviation, I think it's entirely reasonable to
-> avoid fat-fingering an option that can lose data. [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved.mdwn b/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved.mdwn
deleted file mode 100644
index f41a80616..000000000
--- a/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-git-annex is trying to ssh (twice by the look of it) to a remote that is not involved in the copy. In this case, git-annex gives a usage error, but not before calling ssh twice:
-
-    $ git annex copy --from=hugex --to=h2 01-pilot.avi
-    ssh: connect to host 192.168.1.5 port 22: No route to host
-    ssh: connect to host 192.168.1.5 port 22: No route to host
-    fatal: Could not read from remote repository.
-    
-    Please make sure you have the correct access rights
-    and the repository exists.
-    git-annex: only one of --from or --to can be specified
-
-git-annex shouldn't be running ssh before checking commandline arguments! Or, in this case at all, since both remotes mentioned on the commandline are local:
-
-    $ git config remote.hugex.url
-    /media/hugex/jason/home.git
-    $ git config remote.h2.url
-    /media/h2/backup/git/home.git
-
-
-I'm running git-annex 4.20130627 as shipped with debian unstable.
-
--- 
-Jason
-
-P.S. 192.168.1.5 is set as the HostName for one of my other remotes in my ~/.ssh/config, so this isn't _totally_ out of the blue. 
-
-> [[done]]; see comment's explanation. --[[Joey]]
diff --git a/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved/comment_1_f1330935a07460c9c8bc82ee8d4709c5._comment b/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved/comment_1_f1330935a07460c9c8bc82ee8d4709c5._comment
deleted file mode 100644
index 2595e083b..000000000
--- a/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved/comment_1_f1330935a07460c9c8bc82ee8d4709c5._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 1"
- date="2013-06-30T17:27:07Z"
- content="""
-git-annex needs to discover the uuid of each remote before it can use it. So it currently goes off the discover these uuids at startup time.
-
-If you have a remote that you do not want git-annex to use, you can set remote.name.annex-ignore and it will not do this discovery process for that remote.
-
-While it would be possible to defer the lookup until an operation that needs to know the remote's uuid, it would complicate the code quite a bit, so I have not tried to do so.
-"""]]
diff --git a/doc/bugs/git_annex_describe_can_break_uuid.log.mdwn b/doc/bugs/git_annex_describe_can_break_uuid.log.mdwn
deleted file mode 100644
index 16e6981f5..000000000
--- a/doc/bugs/git_annex_describe_can_break_uuid.log.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-### Please describe the problem.
-
-`uuid.log` can end up in a state where `git annex describe` (and probably other things) stops working.
-
-### What steps will reproduce the problem?
-
-Run `git annex describe` against a remote that is not a an initialized git-annex repo.
-
-### What version of git-annex are you using? On what operating system?
-
-debian-packaged git-annex 4.20131106 on Linux Mint 13/Maya (Ubuntu Precise/12.04)
-
-### Please provide any additional information below.
-
-I will follow comments, but can also be found at [[https://microca.st/clacke]].
-
-Full transcript to reproduce:
-
-[[!format sh """
-$ git init a
-Initialized empty Git repository in /tmp/annex/a/.git/
-$ git init b
-Initialized empty Git repository in /tmp/annex/b/.git/
-$ cd a/
-$ git annex init
-init  ok
-(Recording state in git...)
-$ git remote add -f b ../b
-Updating b
-$ git annex describe b b # this should not be ok
-describe b ok
-(Recording state in git...)
-$ git annex describe b b
-describe b git-annex: Prelude.last: empty list
-$ git cat-file blob git-annex:uuid.log
- b timestamp=1383987654.900868s
-...
-
-# End of transcript.
-"""]]
-
-> Fixed the bug and made git breakage not crash git-annex. [[done]]
-> --[[Joey]] 
-
-> > Update: Also made it automatically clean up the cruft this put in the
-> > log. --[[Joey]] 
diff --git a/doc/bugs/git_annex_describe_can_break_uuid.log/comment_2_9ead36f13cbde6c822b231441de636ae._comment b/doc/bugs/git_annex_describe_can_break_uuid.log/comment_2_9ead36f13cbde6c822b231441de636ae._comment
deleted file mode 100644
index a5616234e..000000000
--- a/doc/bugs/git_annex_describe_can_break_uuid.log/comment_2_9ead36f13cbde6c822b231441de636ae._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://id.clacke.se/"
- nickname="clacke"
- subject="comment 2"
- date="2013-11-11T05:32:14Z"
- content="""
-Great, thanks!
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful.mdwn b/doc/bugs/git_annex_does_nothing_useful.mdwn
deleted file mode 100644
index b68e53da9..000000000
--- a/doc/bugs/git_annex_does_nothing_useful.mdwn
+++ /dev/null
@@ -1,67 +0,0 @@
-As you can see, I'm running a pretty recent build of git-annex (ac799c3f363e0008b23e9c174e6fedc35e6fa92a),
-
-    $ git annex version
-    git-annex version: 3.20120630
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3
-    upgrade supported from repository versions: 0 1 2
-
-We have a file here which isn't currently available yet isn't
-currently available (the link is shown in red),
-
-    $ ls -l plot.py
-    lrwxrwxrwx 1 ben ben 77 Jul  6 14:01 plot.py -> ../.git/annex/objects/WORM:1301941019:720:plot.py/WORM:1301941019:720:plot.py
-    $ 
-
-Yet git-annex should be able to tell us where it is,
-
-    $ git-annex whereis plot.py
-    $ 
-
-Hmm, well that's strange. What's happening here,
-
-    $ git-annex whereis plot.py -d
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","show-ref","git-annex"]
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","show-ref","--hash","refs/heads/git-annex"]
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","log","refs/heads/git-annex..d5582e05f41011b571a17003934fe9e40859e4be","--oneline","-n1"]
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","cat-file","--batch"]
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","ls-files","--cached","-z","--","plot.py"]
-    $ 
-
-Alright, well maybe `git-annex get` will work,
-
-    $ git annex get plot.py -d
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","ls-files","--cached","-z","--","plot.py"]
-    $ ls -l plot.py
-    lrwxrwxrwx 1 ben ben 77 Jul  6 14:01 plot.py -> ../.git/annex/objects/WORM:1301941019:720:plot.py/WORM:1301941019:720:plot.py
-
-Nope, the link is still shown in red.
-
-Alright, what about `git-annex copy`?
-
-    $ git annex copy plot.py --from=goldnerlab --to=here -d 
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","show-ref","git-annex"]
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","show-ref","--hash","refs/heads/git-annex"]
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","log","refs/heads/git-annex..d5582e05f41011b571a17003934fe9e40859e4be","--oneline","-n1"]
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","cat-file","--batch"]
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","ls-files","--cached","-z","--","plot.py"]
-    $ ls -l plot.py
-    lrwxrwxrwx 1 ben ben 77 Jul  6 14:01 plot.py -> ../.git/annex/objects/WORM:1301941019:720:plot.py/WORM:1301941019:720:plot.py
-
-Still red.
-
-Alright, what if I just try to get a non-existent file?
-
-    $ git annex get adsflkah -d
-    git ["--git-dir=/home/ben/lori/analysis/data/.git","--work-tree=/home/ben/lori/analysis/data","ls-files","--cached","-z","--","adsflkah"]
-    $
-
-Alright, it didn't fail with an error, that's very strange. What is going on here?
-
-[[!meta title="v1 file is ignored"]]
-
-> I don't think I want to make git-annex deal with v1 files, and
-> I doubt there are many repos left using them. This seems to be a case
-> of an upgrade not being done, for whatever reason. Closing [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_10_457354dc0018333002dc5049935c0feb._comment b/doc/bugs/git_annex_does_nothing_useful/comment_10_457354dc0018333002dc5049935c0feb._comment
deleted file mode 100644
index 266cff3db..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_10_457354dc0018333002dc5049935c0feb._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl0"
- nickname="Ben"
- subject="comment 10"
- date="2012-07-10T14:17:42Z"
- content="""
-Hmm, the commands above seem to have worked on both machines (both running 3.20120630). I guess I should probably just try rebuilding my data/ repository from scratch, eh?
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_11_8a6d244165dd238ddf9dd629795de2f6._comment b/doc/bugs/git_annex_does_nothing_useful/comment_11_8a6d244165dd238ddf9dd629795de2f6._comment
deleted file mode 100644
index 1de08ae60..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_11_8a6d244165dd238ddf9dd629795de2f6._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 11"
- date="2012-07-10T14:26:06Z"
- content="""
-I suppose.. joey can probably help you investigate exactly what went wrong.  You might want to save an empty clone of the git repository for later..
-
-The easiest way to fix the data is probably to run a `git annex uninit` in the old repository which will put the files back how they were before and then `git-annex import` them into a new repository.
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_12_30d06bc0f1c37d988a1a31962b57533c._comment b/doc/bugs/git_annex_does_nothing_useful/comment_12_30d06bc0f1c37d988a1a31962b57533c._comment
deleted file mode 100644
index 3de157752..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_12_30d06bc0f1c37d988a1a31962b57533c._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="165.98.113.100"
- subject="comment 12"
- date="2012-07-11T23:23:04Z"
- content="""
-Looking at this a leetle more closely, you had:
-
-<pre>
-lrwxrwxrwx 1 ben ben 77 Jul  6 14:01 plot.py -> ../.git/annex/objects/WORM:1301941019:720:plot.py/WORM:1301941019:720:plot.py
-</pre>
-
-Well, that is not how a git-annex symlink currently looks, so it ignores it.
-
-Apparenly this repository was created with an old version of git-annex, possibly version 1, and you've dropped in the current version, but the normal upgrade machinery failed. This could happen if you made a new clone of a version 1 bare repository.
-
-I suggest you first find out what version of git-annex was originally used to create this repository (ie, version 0, 1, or 2 ... probably 1). Then make a clone, and \"git config annex.version $N\" where N=the version used). Then \"git annex upgrade\" and you should be good to go. Remember to push or sync the upgrade back to the bare repo so you don't need to do this again.
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_1_fc4f51ddcbc69631e2835b86c3489c8e._comment b/doc/bugs/git_annex_does_nothing_useful/comment_1_fc4f51ddcbc69631e2835b86c3489c8e._comment
deleted file mode 100644
index 6bf6e96f6..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_1_fc4f51ddcbc69631e2835b86c3489c8e._comment
+++ /dev/null
@@ -1,7 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- subject="comment 1"
- date="2012-07-09T23:16:32Z"
- content="""
-`git ls-files` is not listing your file. Perhaps your file is not checked into git?
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_2_9bb1647e6c59f1ed7b13b81ecc33f920._comment b/doc/bugs/git_annex_does_nothing_useful/comment_2_9bb1647e6c59f1ed7b13b81ecc33f920._comment
deleted file mode 100644
index 3423bfae4..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_2_9bb1647e6c59f1ed7b13b81ecc33f920._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl0"
- nickname="Ben"
- subject="comment 2"
- date="2012-07-09T23:31:08Z"
- content="""
-Not really sure what to say about that other than,
-
-    $ git --git-dir=/home/ben/lori/analysis/data/.git --work-tree=/home/ben/lori/analysis/data ls-files --cached -- plot.py
-    plot.py
-    $ 
-
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_3_d434f5c614a27b75d73530b5b918b851._comment b/doc/bugs/git_annex_does_nothing_useful/comment_3_d434f5c614a27b75d73530b5b918b851._comment
deleted file mode 100644
index f03aa2745..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_3_d434f5c614a27b75d73530b5b918b851._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="Remotes? "
- date="2012-07-10T00:23:11Z"
- content="""
-What does
-
-    git-annex status
-
-Show? 
-
-Do you have any remotes configured? It looks like you don't somehow. 
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_4_998e33219d29ea41b0b2a5d2955a9862._comment b/doc/bugs/git_annex_does_nothing_useful/comment_4_998e33219d29ea41b0b2a5d2955a9862._comment
deleted file mode 100644
index fc9f6c30c..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_4_998e33219d29ea41b0b2a5d2955a9862._comment
+++ /dev/null
@@ -1,46 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl0"
- nickname="Ben"
- subject="comment 4"
- date="2012-07-10T01:46:23Z"
- content="""
-    $ git annex status
-    supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
-    supported remote types: git S3 bup directory rsync web hook
-    trusted repositories: 0
-    semitrusted repositories: 3
-            00000000-0000-0000-0000-000000000001 -- web
-            02e4ea72-a77c-11e1-bbd7-0749b04e4b59 -- goldnerlab (Data for Goldner)
-            3c1fd026-c794-11e1-8ebb-dbe8684e8a73 -- here
-    untrusted repositories: 0
-    dead repositories: 0
-    transfers in progress: none
-    available local disk space: 16 gigabytes (+1 megabyte reserved)
-    local annex keys: 0
-    local annex size: 0 bytes
-    known annex keys: 0
-    known annex size: 0 bytes
-    bloom filter size: 16 mebibytes (0% full)
-    backend usage: 
-    $ git remote 
-    goldnerlab
-    $ git remote show goldnerlab
-    * remote goldnerlab
-      Fetch URL: goldnerlab:data
-      Push  URL: goldnerlab:data
-      HEAD branch (remote HEAD is ambiguous, may be one of the following):
-        master
-        synced/master
-      Remote branches:
-        git-annex     tracked
-        master        tracked
-        synced/master tracked
-      Local branch configured for 'git pull':
-        master merges with remote master
-      Local refs configured for 'git push':
-        git-annex     pushes to git-annex     (up to date)
-        master        pushes to master        (up to date)
-        synced/master pushes to synced/master (up to date)
-    
-
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_5_c72e2571e5b8c06bbfa2276a7ad1e8a6._comment b/doc/bugs/git_annex_does_nothing_useful/comment_5_c72e2571e5b8c06bbfa2276a7ad1e8a6._comment
deleted file mode 100644
index 90159b5b4..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_5_c72e2571e5b8c06bbfa2276a7ad1e8a6._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 5"
- date="2012-07-10T03:03:27Z"
- content="""
-Well that's odd. You have remotes but no annexed files.. 
-
-Can you post the commands you used to arrive at this situation? I'm not sure how you would have done that.. Maybe you just need a 
-
-    git-annex sync
-
-to get things going? 
-
-I think somehow you cloned the git repo but not the annex stuff. 
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_6_bc8b42432ba25de8f972c192bc3cdff6._comment b/doc/bugs/git_annex_does_nothing_useful/comment_6_bc8b42432ba25de8f972c192bc3cdff6._comment
deleted file mode 100644
index ad98e6874..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_6_bc8b42432ba25de8f972c192bc3cdff6._comment
+++ /dev/null
@@ -1,44 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl0"
- nickname="Ben"
- subject="comment 6"
- date="2012-07-10T03:26:35Z"
- content="""
-I can easily reproduce the issue as follows,                                                                                                              
-                                                                                                                                                          
-    $ git clone goldnerlab:data                                                                                                                           
-    Cloning into 'data'...                                                                                                                                
-    remote: Counting objects: 61902, done.                                                                                                                
-    remote: Compressing objects: 100% (61354/61354), done.                                                                                                
-    remote: Total 61902 (delta 356), reused 61902 (delta 356)                                                                                             
-    Receiving objects: 100% (61902/61902), 5.50 MiB | 894 KiB/s, done.                                                                                    
-    Resolving deltas: 100% (356/356), done.                                                                                                               
-    $ cd data                                                                                                                                             
-    $ git annex sync                                                                                                                                      
-    (merging origin/git-annex into git-annex...)                                                                                                          
-    commit                                                                                                                                                
-    (Recording state in git...)                                                                                                                           
-    # On branch master                                                                                                                                    
-    nothing to commit (working directory clean)                                                                                                           
-    ok                                                                                                                                                    
-    pull origin                                                                                                                                           
-    ok                                                                                                                                                    
-    push origin                                                                                                                                           
-    Counting objects: 8, done.                                                                                                                            
-    Delta compression using up to 2 threads.                                                                                                              
-    Compressing objects: 100% (5/5), done.                                                                                                                
-    Writing objects: 100% (6/6), 726 bytes, done.                                                                                                         
-    Total 6 (delta 1), reused 1 (delta 0)                                                                                                                 
-    Auto packing the repository for optimum performance.                                                                                                  
-    warning: There are too many unreachable loose objects; run 'git prune' to remove them.                                                                
-    To goldnerlab:data                                                                                                                                    
-       d5582e0..aaddf3c  git-annex -> git-annex                                                                                                           
-    ok                                                                                                                                                    
-                                                                                                                                                          
-Everything looks good so far. I verify that alex/plot.py doesn't exist. Now let's try getting it,                                                         
-                                                                                                                                                          
-    $ git annex get alex/plot.py -d                                                                                                                       
-    git [\"--git-dir=/home/ben/data/.git\",\"--work-tree=/home/ben/data\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"alex/plot.py\"]                                     
-                                                                                                                                                          
-Uh oh. ls confirms that get was unsucessful.            
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_7_e7469a4c5e45078ade775f5cbdd17cfc._comment b/doc/bugs/git_annex_does_nothing_useful/comment_7_e7469a4c5e45078ade775f5cbdd17cfc._comment
deleted file mode 100644
index c40e4e2cf..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_7_e7469a4c5e45078ade775f5cbdd17cfc._comment
+++ /dev/null
@@ -1,67 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 7"
- date="2012-07-10T12:37:43Z"
- content="""
-But how was the goldnerlab:data repository created?  That looks to be where the problem is..
-
-I have a slightly older version, but in general it should work the same..
-you can see right away, when I do git annex status it shows \"known annex keys: 1\".
-if you do git annex status on goldnerlab, does it say you have any annex keys?
-
-
-    $ git-annex version
-    git-annex version: 3.20120614~bpo60+1
-    $ mkdir a
-    $ cd a
-    $ git init
-    Initialized empty Git repository in /tmp/a/.git/
-    $ git annex init a
-    init a ok
-    (Recording state in git...)
-    $ echo hi > file
-    $ git annex add file
-    add file (checksum...) ok
-    (Recording state in git...)
-    $ git commit -m added
-    fatal: No HEAD commit to compare with (yet)
-    fatal: No HEAD commit to compare with (yet)
-    [master (root-commit) cfa9049] added
-     1 files changed, 1 insertions(+), 0 deletions(-)
-     create mode 120000 file
-    $ cd ..
-    $ git clone a a_clone
-    Cloning into a_clone...
-    done.
-    $ cd a_clone
-    $ git annex status
-    (merging origin/git-annex into git-annex...)
-    supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
-    supported remote types: git bup directory rsync web hook
-    trusted repositories: 0
-    semitrusted repositories: 3
-            00000000-0000-0000-0000-000000000001 -- web
-            445d616e-ca8b-11e1-b170-ff8b03c54243 -- origin (a)
-            5d3db51c-ca8b-11e1-bbc3-039dd06ab47b -- here
-    untrusted repositories: 0
-    dead repositories: 0
-    available local disk space: 63 megabytes (+1 megabyte reserved)
-    local annex keys: 0
-    local annex size: 0 bytes
-    known annex keys: 1
-    known annex size: 3 bytes
-    backend usage:
-            SHA256: 1
-    (Recording state in git...)
-    $ ls
-    file
-    $ cat file
-    cat: file: No such file or directory
-    $ git annex get file
-    get file (from origin...) ok
-    (Recording state in git...)
-    $ cat file
-    hi
-
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_8_bc9e6fd284440a59ffe4e4ed1f73f7d7._comment b/doc/bugs/git_annex_does_nothing_useful/comment_8_bc9e6fd284440a59ffe4e4ed1f73f7d7._comment
deleted file mode 100644
index 85d03f04b..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_8_bc9e6fd284440a59ffe4e4ed1f73f7d7._comment
+++ /dev/null
@@ -1,30 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl0"
- nickname="Ben"
- subject="comment 8"
- date="2012-07-10T13:02:37Z"
- content="""
-On goldnerlab,
-
-    $ git annex status
-    supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
-    supported remote types: git S3 bup directory rsync web hook
-    trusted repositories: 0
-    semitrusted repositories: 4
-        00000000-0000-0000-0000-000000000001 -- web
-        02e4ea72-a77c-11e1-bbd7-0749b04e4b59 -- here (Data for Goldner)
-        351f3ddc-ca3e-11e1-a3fc-6338ef4724a7
-        3c1fd026-c794-11e1-8ebb-dbe8684e8a73
-    untrusted repositories: 0
-    dead repositories: 0
-    transfers in progress: none
-    available local disk space: 2 terabytes (+1 megabyte reserved)
-    local annex keys: 19101
-    local annex size: 41 gigabytes
-    known annex keys: 19122
-    known annex size: 41 gigabytes
-    bloom filter size: 16 mebibytes (3.8% full)
-    backend usage:
-            WORM: 38223
-
-"""]]
diff --git a/doc/bugs/git_annex_does_nothing_useful/comment_9_38a2dbeee3750d79ca9a943a02fceb29._comment b/doc/bugs/git_annex_does_nothing_useful/comment_9_38a2dbeee3750d79ca9a943a02fceb29._comment
deleted file mode 100644
index dc3206ac5..000000000
--- a/doc/bugs/git_annex_does_nothing_useful/comment_9_38a2dbeee3750d79ca9a943a02fceb29._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 9"
- date="2012-07-10T14:08:10Z"
- content="""
-Can you run the series of commands I had above on your two machines?  I figure there are two possibilities:
-
-1. There is something wrong with the git-annex versions you are using.
-2. There is something wrong with your repository. (\"warning: There are too many unreachable loose objects\"?)
-
-so if you can make a temp repository on goldnerlab, then clone it on the other machine and see where it fails, that would be helpful.
- 
-after cloning git-annex status should hopefully say that you have 1 known key, not 0.
-
-Obviously this won't fix the problem, but it will at least narrow it down.
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file.mdwn b/doc/bugs/git_annex_fork_bombs_on_gpg_file.mdwn
deleted file mode 100644
index 9bfe3ee3b..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-### Please describe the problem.
-git-annex goes into a loop of I think Haskell's createProcess function and causes the entire operating system to starve of process creation.
-
-### What steps will reproduce the problem?
-The last file git-annex was processing was tinco.gpg, my gpg key exported with
-  
-   gpg --export mail@tinco.nl --output tinco.gpg 
-
-### What version of git-annex are you using? On what operating system?
-4.20130516-g8a26544 on OSX
-
-I had a remote setup using bup.
-
-### Please provide any additional information below.
-Unfortunately to fix the problem I have deleted the entire git repository and made a new init in the same directory, this time without the gpg file. Everything seems to be working now.
-
-What I remember about the log file is that the last thing it said was something along the lines of 
-
-add tinco.gpg
-
-.. (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) ..etc
-
-recv (resource unavailable or something) ..
-
-> [[done]]; fixed 3 bugs! --[[Joey]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_10_6e29b60cd77f3288e33ad270f95f410e._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_10_6e29b60cd77f3288e33ad270f95f410e._comment
deleted file mode 100644
index 0338219ac..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_10_6e29b60cd77f3288e33ad270f95f410e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://me.tinco.nl/"
- nickname="Tinco"
- subject="comment 10"
- date="2013-05-19T20:45:53Z"
- content="""
-Alright! So first the issue was that gpg was asking for a passphrase. I fixed that by installing gpgtools for mac, but that one doesn't have a gpg executable, instead it has gpg2. I hadn't noticed that, so that's why it was saying 'resource vanished' without a proper error message, it simply couldn't find the gpg executable. I did ln -s /usr/local/bin/gpg2 /usr/local/bin/gpg, and now it's happily copying files. Thanks for helping me find out what was wrong!
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_11_ad13e3221ae06086e86800316912d951._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_11_ad13e3221ae06086e86800316912d951._comment
deleted file mode 100644
index 301b0f973..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_11_ad13e3221ae06086e86800316912d951._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 11"
- date="2013-05-19T21:13:41Z"
- content="""
-You're certainly welcome.
-
-So, you did not install git-annex from the dmg? That bundles its own gpg.
-
-I'm curious about this passphrase thing.. Does gpgtools + gpg2 on the Mac cause it to ask for a passphrase better, like in a dialog window? Perhaps I can improve the gpg stuff bundled in the dmg..
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_12_41746b731eae7f280bb668c776022bcb._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_12_41746b731eae7f280bb668c776022bcb._comment
deleted file mode 100644
index ee27c5491..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_12_41746b731eae7f280bb668c776022bcb._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://me.tinco.nl/"
- nickname="Tinco"
- subject="comment 12"
- date="2013-05-19T21:24:48Z"
- content="""
-Yes exactly, it spawns a dialog window and overall has a very nice interface for managing gpg keys. I switched from the DMG to cabal because I couldn't get the bundled gpg to ask for my password, setting up a gpg-agent seemed pretty complicated, so I just went for the packaged approach from https://gpgtools.org/.
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_13_56ca8590110abffeed6d826c54ca1136._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_13_56ca8590110abffeed6d826c54ca1136._comment
deleted file mode 100644
index 64ee5e876..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_13_56ca8590110abffeed6d826c54ca1136._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 13"
- date="2013-05-19T22:03:57Z"
- content="""
-Ok, I've made a note that I should look into pulling in gpgtools rather than gpg into the DMG. At least if the webapp every gets a UI that allows setting up remotes that are encrypted to a gpg key. Currently the webapp avoids that because I know gpg password prompting is not sorted out everywhere.
-
-And also, I've made the configure script check for gpg2 if it can't find a gpg.
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_1_73ae438a37e4c5f56fe291448e1c64dd._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_1_73ae438a37e4c5f56fe291448e1c64dd._comment
deleted file mode 100644
index e1c3ed279..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_1_73ae438a37e4c5f56fe291448e1c64dd._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://me.tinco.nl/"
- nickname="Tinco"
- subject="comment 1"
- date="2013-05-18T23:32:32Z"
- content="""
-Nevermind the gpg file suspicion, it now crashes without that file too:
-
-[2013-05-19 01:30:36 CEST] main: starting assistant version 4.20130516-g8a26544
-
-(scanning...) [2013-05-19 01:30:36 CEST] Watcher: Performing startup scan
-(started...) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) (gpg) 
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_2_aa237adebe7674b8cdb9a967bb5f96a8._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_2_aa237adebe7674b8cdb9a967bb5f96a8._comment
deleted file mode 100644
index f5358da98..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_2_aa237adebe7674b8cdb9a967bb5f96a8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://me.tinco.nl/"
- nickname="Tinco"
- subject="comment 2"
- date="2013-05-18T23:36:22Z"
- content="""
-So that probably means I have some problem with the gpg encryption, that is used by bup. Maybe it doesn't even have to do with git annex, I'll see if I can make it say more in the log.
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_3_ab403d7abbbbabd498b954b0b9742755._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_3_ab403d7abbbbabd498b954b0b9742755._comment
deleted file mode 100644
index 0ffbcccae..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_3_ab403d7abbbbabd498b954b0b9742755._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-05-18T23:59:59Z"
- content="""
-run it with `--debug`
-
-paste the whole log, not an except
-
-get a `ps lax` so we can see which programs are running which other programs and how many programs are running at the same time
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_4_a35d04440b1220faf9088107c3f17762._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_4_a35d04440b1220faf9088107c3f17762._comment
deleted file mode 100644
index bd1fef019..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_4_a35d04440b1220faf9088107c3f17762._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://me.tinco.nl/"
- nickname="Tinco"
- subject="comment 4"
- date="2013-05-19T03:15:10Z"
- content="""
-Ok I got some interesting data from the debug switch, posted it here: https://pastee.org/ kn2hv (remove space, TTL 1 month)
-
-And managed to get a ps lax in after launch but before I'm starved of processes: http://pastie.org/pastes/7928091/text?key=gdywhjzo8xm5etcgv8e8jw
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_5_8345331b9b313769ba401da2ffd89332._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_5_8345331b9b313769ba401da2ffd89332._comment
deleted file mode 100644
index d0ff6f008..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_5_8345331b9b313769ba401da2ffd89332._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://me.tinco.nl/"
- nickname="Tinco"
- subject="comment 5"
- date="2013-05-19T12:37:22Z"
- content="""
-Sorry, I just noticed that after I killed the process it created some more logs. The log I previously pasted is moved to log.3, here are the additional ones (all created in around the same minute:)
-
-http://pastie.org/7929225
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_6_7eb535ca38b3e84d44d0f8cbf5e61b8b._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_6_7eb535ca38b3e84d44d0f8cbf5e61b8b._comment
deleted file mode 100644
index 03f213c43..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_6_7eb535ca38b3e84d44d0f8cbf5e61b8b._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 6"
- date="2013-05-19T16:39:44Z"
- content="""
-So there are a lot of uploads attempts being made (and apparently failing), and a lot of zombie git-annex processes are building up as children of the git-annex transferkeys process. That isolates the problem some.
-
-The repeated \"(gpg)\" is an interesting clue, since normally git-annex only runs gpg once, to unlock an encrypted special remote's encryption key, and then should retain the key, cached in memory. I was able to reproduce this part of the bug (but not the zombie processes) when I purposfully broke the bup special remote by making it throw an error when it was supposed to run bup to send a file. That defeats the caching, since the state, including the cache, is thrown away when there's an exception. Working on a fix for that..
-
-That doesn't explain what's actually causing the problem for you, but it does certainly suggest the bup special remote code is failing in some unusual way. What happens if rather than starting the assistant, you use git-annex manually to send files to the remote? Run:
-
-<pre>
-git annex copy --to ffe41272-608e-43c4-8f35-e9cd63087892 --debug
-</pre>
-
-(You may want to give it the name of just 1 file to send.)
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_7_a3aa4231a82917c56cbdf52b65db7133._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_7_a3aa4231a82917c56cbdf52b65db7133._comment
deleted file mode 100644
index 16961afd3..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_7_a3aa4231a82917c56cbdf52b65db7133._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="http://me.tinco.nl/"
- nickname="Tinco"
- subject="comment 7"
- date="2013-05-19T19:27:03Z"
- content="""
-Hi Joey thanks for working with me on this. The result from copying one file over is 'resource vanished':
-
-    [2013-05-19 21:24:53 CEST] read: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"show-ref\",\"git-annex\"]
-    [2013-05-19 21:24:53 CEST] read: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-05-19 21:24:53 CEST] read: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"log\",\"refs/heads/git-annex..f0523a06e2eb7217d98fe2b9f6ec5afa724ccd92\",\"--oneline\",\"-n1\"]
-    [2013-05-19 21:24:53 CEST] chat: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"cat-file\",\"--batch\"]
-    [2013-05-19 21:24:53 CEST] read: git [\"--git-dir=/Users/tinco/Documents/.git\",\"--work-tree=/Users/tinco/Documents\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"About Stacks.pdf\"]
-    copy About Stacks.pdf (gpg) [2013-05-19 21:24:53 CEST] chat: gpg [\"--quiet\",\"--trust-model\",\"always\",\"--decrypt\"]
-
-    git-annex: fd:12: hClose: resource vanished (Broken pipe)
-    failed
-    git-annex: copy: 1 failed
-
-
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment
deleted file mode 100644
index 38b136b37..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 8"
- date="2013-05-19T19:35:51Z"
- content="""
-I've fixed the repeated \"(gpg)\" problem. But that is not the real problem...
-
-Looks to me like there is a problem with running gpg to extract the encryption key of the repository. I can cause the same \"resource vanished\" message if I make gpg exit 1 immediately when it starts. I also managed to get 3 zombies when failing to send 100 files. Although in my case they were gpg zombies, not git-annex zombies.
-
-Can you run `gpg` manually at the command line? If you installed git-annex from the OSX dmg file, you need to have used \"runshell\" to get the gpg that's included in it onto the PATH before you do this.
-"""]]
diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_9_7d80f131f43312bb061df2be7fa956ef._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_9_7d80f131f43312bb061df2be7fa956ef._comment
deleted file mode 100644
index ff81f53a4..000000000
--- a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_9_7d80f131f43312bb061df2be7fa956ef._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 9"
- date="2013-05-19T19:53:04Z"
- content="""
-I've fixed things so it will not pile up zombie processes. It'll still fail to send stuff if gpg is broken, but it'll fail more nicely now.
-
-We still need to find out why gpg is failing to run on your system..
-"""]]
diff --git a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files.mdwn b/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files.mdwn
deleted file mode 100644
index 9563f0683..000000000
--- a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-What steps will reproduce the problem?
-
-Put some large files into a direct mode repository (so fsck time is noticeable).  git annex add them, commit, run git annex fsck.
-
-What is the expected output? What do you see instead?
-
-Expected: files are checksummed, which should take considerable amount of time for each file.  For reference, in indirect mode, fsck takes a while for files of ~1GB size.
-Actually: in direct mode, git annex fsck goes through all of the files in an instant and prints OK for each. I believe the file content is not verified.
-Multiple runs of git annex fsck do the same thing.
-
-What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130405, Linux
-
-Please provide any additional information below.
-
-> I've fixed it, fsck is indeed checksumming direct mode files now, as long
-> as they're not known to be modified. [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_1_a6cde4aa495512344fa7f50e10749c68._comment b/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_1_a6cde4aa495512344fa7f50e10749c68._comment
deleted file mode 100644
index 5aaebc342..000000000
--- a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_1_a6cde4aa495512344fa7f50e10749c68._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-04-14T17:50:53Z"
- content="""
-This is expected. The content of direct mode files can change at any time, so fsck does not have a locked down object with a known checksum that it can verify. Similarly, fsck skips unlocked files in indirect mode.
-"""]]
diff --git a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_2_4ac3b87ec0bc0514c4eff9f5a75b9f5d._comment b/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_2_4ac3b87ec0bc0514c4eff9f5a75b9f5d._comment
deleted file mode 100644
index 3befccd39..000000000
--- a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_2_4ac3b87ec0bc0514c4eff9f5a75b9f5d._comment
+++ /dev/null
@@ -1,26 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog"
- nickname="Michael"
- subject="comment 2"
- date="2013-04-15T01:32:52Z"
- content="""
-I'm still somewhat confused about the following commit (which seems to suggest fsck in direct mode could actually checksum files):
-
-commit 0da2507fd622120217cf03038b851b47c47ace53
-Author: Joey Hess <joey@kitenet.net>
-Date:   Tue Jan 8 15:07:00 2013 -0400
-
-    improve direct mode fsck
-    
-    An earlier commit (mislabeled) made direct mode fsck check file checksums.
-    While it's expected for files to change at any time in direct mode, and so
-    fsck cannot complain every time there's a checksum mismatch, it is possible
-    for it to detect when a file does not *seem* to have changed, then check
-    its checksum, and so detect disk corruption or other problems.
-    
-    This commit improves that, by checking a second time, if the checksum
-    fails, that the file is still not modified, before taking action. This way,
-    a direct mode file can be modified while being fscked.
-
-
-"""]]
diff --git a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_3_d18b1fdc866edf2786d2c6b7ec55119f._comment b/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_3_d18b1fdc866edf2786d2c6b7ec55119f._comment
deleted file mode 100644
index a7b2b38da..000000000
--- a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_3_d18b1fdc866edf2786d2c6b7ec55119f._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-16T20:16:51Z"
- content="""
-Thanks for digging that up!
-
-I'd forgotten I finessed the problem that way.. And it looks like that patch was broken and never checked the right file.
-
-"""]]
diff --git a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_4_31e4fcbf63c11cc374a849daf3ce1dbc._comment b/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_4_31e4fcbf63c11cc374a849daf3ce1dbc._comment
deleted file mode 100644
index 57af75673..000000000
--- a/doc/bugs/git_annex_fsck_in_direct_mode_does_not_checksum_files/comment_4_31e4fcbf63c11cc374a849daf3ce1dbc._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog"
- nickname="Michael"
- subject="Thanks!"
- date="2013-04-17T18:33:41Z"
- content="""
-It does fsck for real now.
-"""]]
diff --git a/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn b/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn
deleted file mode 100644
index 9a044860a..000000000
--- a/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-What is says on the tin:
-
-git annex fsck is a no-op in bare repos
-
-See http://lists.madduck.net/pipermail/vcs-home/2011-June/000433.html
-
-> Thinking about this some more, it would be difficult to do anything
-> when bad content is found, since it also cannot update the location log.
-> 
-> So this may be another thing blocked by [[todo/branching]], assuming
-> that is fixed in a way that makes `.git-annex` available to bare repos.
-> --[[Joey]] 
-
->> Even if there is nothing it can _do_, knowing that the data is intact,
->> or not, is valuable in and as of itself. -- RichiH
-
->>> While storing the data is no longer an issue in bare repos, fsck would
->>> need a special mode that examines all the location logs, since it
->>> cannot run thru the checked out files. --[[Joey]] 
-
->>>> [[done]]! --[[Joey]] 
diff --git a/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos/comment_1_fc59fbd1cdf8ca97b0a4471d9914aaa1._comment b/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos/comment_1_fc59fbd1cdf8ca97b0a4471d9914aaa1._comment
deleted file mode 100644
index d50938a78..000000000
--- a/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos/comment_1_fc59fbd1cdf8ca97b0a4471d9914aaa1._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-06-13T16:58:52Z"
- content="""
-And, maybe, a way to start a fsck from remote? At least when the other side is a ssh or git annex shell, this would work.
-"""]]
diff --git a/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos/comment_2_273a45e6977d40d39e0d9ab924a83240._comment b/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos/comment_2_273a45e6977d40d39e0d9ab924a83240._comment
deleted file mode 100644
index b01590a7a..000000000
--- a/doc/bugs/git_annex_fsck_is_a_no-op_in_bare_repos/comment_2_273a45e6977d40d39e0d9ab924a83240._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://ertai.myopenid.com/"
- nickname="npouillard"
- subject="git annex fsck --from remote"
- date="2011-06-25T16:20:44Z"
- content="""
-Currently fsck silently ignores --to/--from.
-It should at least complain if it is not supported.
-"""]]
diff --git a/doc/bugs/git_annex_get_choke_when_remote_is_an_ssh_url_with_a_port.mdwn b/doc/bugs/git_annex_get_choke_when_remote_is_an_ssh_url_with_a_port.mdwn
deleted file mode 100644
index 92cc9170f..000000000
--- a/doc/bugs/git_annex_get_choke_when_remote_is_an_ssh_url_with_a_port.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-when i want to
-
-    git annex get file
-
-on repo ssh://host-without-port/annex, it works, but if i want to get a file from ssh://host:5122/annex, it tries to run command
-ssh ["host:5122", "git-annex-shell 'configlist' '/annex/file'"] and fails. ssh needs the -p option to set the default port, it doesn't support host:port notation.
-this is confusing because git can handle this url correctly, and will happily clone/push/pull to/from these url.
-
-temporary workaround is to use ssh://host/annex as url and define remote.name.annex-ssh-options to "-p 5122", but we need to use this workaround when doing annex get and undo the workaround when pushing/cloning.
-
-if i had more time, i would have learned haskell and provided a patch ;)
-
-> Fixed in git! --[[Joey]] [[done]]
diff --git a/doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn b/doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn
deleted file mode 100644
index d35282e75..000000000
--- a/doc/bugs/git_annex_gets_confused_about_remotes_with_dots_in_their_names.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-For test.com//test, I get this:
-
-    % git annex copy . --to test.com//test
-    (getting UUID for test...) git-annex: there is no git remote named "test.com//test"
-
-And my .git/config changes from
-
-    [remote "test.com//test"]
-    	url = richih@test.com:/test
-    	fetch = +refs/heads/*:refs/remotes/test.com//test/*
-
-to
-
-    [remote "test.com//test"]
-    	url = richih@test.com:/test
-    	fetch = +refs/heads/*:refs/remotes/test.com//test/*
-    	annex-uuid = xyz
-    [remote "test"]
-    	annex-uuid = xyz
-
-
-Unless I am misunderstanding something, git annex gets confused about what the name of the remote it supposed to be, truncates at the dot for some operations and uses the full name for others.
-
-> I've fixed this bug. [[done]]
-> 
-> However, using "/" in a remote name seems likely to me to confuse 
-> git's own remote branch handling. Although I've never tried it.
-> --[[Joey]] 
-
->> From what I can see, git handles / just fine, but would get upset about : which is why it's not allowed in a remote's name.
->> My naming scheme is host//path/to/annex. It sorts nicely and gives all important information left to right with the most specific parts at the beginning and end.
->> If you have any other ideas or scheme, I am all ears :)
->> Either way, thanks for fixing this so quickly.
->> -- RichiH
diff --git a/doc/bugs/git_annex_import_destroys_a_fellow_git_annex_repository.mdwn b/doc/bugs/git_annex_import_destroys_a_fellow_git_annex_repository.mdwn
deleted file mode 100644
index c8307ca6b..000000000
--- a/doc/bugs/git_annex_import_destroys_a_fellow_git_annex_repository.mdwn
+++ /dev/null
@@ -1,130 +0,0 @@
-### Please describe the problem.
-
-`git annex import` not only [[does not work with git annex repositories|bugs/`git annex import` does not work on other git annex repositories]], it even destroys the meta-data in that repository, because it moves the `.git/*` metadata out of the remote repository.
-
-### What steps will reproduce the problem?
-
-[[!format txt """
-git init foo
-cd foo
-git annex init
-dd if=/dev/urandom of=foo bs=1M count=1
-git annex add foo
-git commit -m'files'
-cd ../
-git init bar
-cd bar
-git annex init
-mkdir foo
-cd foo
-git annex import ../../foo
-cd ../../foo
-git status
-"""]]
-
-
-### What version of git-annex are you using? On what operating system?
-
-[[!format txt """
-anarcat@angela:foo$ git annex version
-git-annex version: 4.20130921-g434dc22
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi
-"""]]
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-anarcat@angela:~$ cd /tmp
-anarcat@angela:/tmp$ mkdir test
-anarcat@angela:/tmp$ cd test
-anarcat@angela:test$ ls
-anarcat@angela:test$ git init foo
-Initialized empty Git repository in /tmp/test/foo/.git/
-anarcat@angela:test$ cd foo
-anarcat@angela:foo$ git annex init
-init  ok
-(Recording state in git...)
-anarcat@angela:foo$ dd if=/dev/urandom of=foo bs=1M count=1
-1+0 enregistrements lus
-1+0 enregistrements écrits
-1048576 octets (1,0 MB) copiés, 0,410384 s, 2,6 MB/s
-anarcat@angela:foo$ git annex add foo
-add foo (checksum...) ok
-(Recording state in git...)
-anarcat@angela:foo$ git commit -m'files'
-[master (root-commit) 83daa0b] files
- 1 file changed, 1 insertion(+)
- create mode 120000 foo
-anarcat@angela:foo$ cd ../
-anarcat@angela:test$ git init bar
-Initialized empty Git repository in /tmp/test/bar/.git/
-anarcat@angela:test$ cd bar
-anarcat@angela:bar$ git annex init
-init  ok
-(Recording state in git...)
-anarcat@angela:bar$ mkdir foo
-anarcat@angela:bar$ cd foo
-anarcat@angela:foo$ git annex import ../../foo
-import .git/COMMIT_EDITMSG (checksum...) ok
-import .git/description (checksum...) ok
-import .git/config (checksum...) ok
-import .git/index (checksum...) ok
-import .git/HEAD (checksum...) ok
-import .git/annex/journal.lck (checksum...) ok
-import .git/annex/index.lck (checksum...) ok
-import .git/annex/sentinal (checksum...) ok
-import .git/annex/sentinal.cache (checksum...) ok
-import .git/annex/index (checksum...) ok
-import .git/annex/objects/w2/Kz/SHA256E-s1048576--f957108785c8dc30cf792948b89d61af257c40e5ef0e1d20ff6cf6aadaf6f66b/SHA256E-s1048576--f957108785c8dc30cf792948b89d61af257c40e5ef0e1d20ff6cf6aadaf6f66b
-git-annex: ../../foo/.git/annex/objects/w2/Kz/SHA256E-s1048576--f957108785c8dc30cf792948b89d61af257c40e5ef0e1d20ff6cf6aadaf6f66b/SHA256E-s1048576--f957108785c8dc30cf792948b89d61af257c40e5ef0e1d20ff6cf6aadaf6f66b: rename: permission denied (Permission denied)
-failed
-import .git/objects/0e/6881452189b7fc34809f101f075da7cca9d9d8 (checksum...) ok
-import .git/objects/03/c0163611cd061af17b2dd58a93c95ffbb05040 (checksum...) ok
-import .git/objects/39/10912eab082d015bface04ed3a8ed658b94893 (checksum...) ok
-import .git/objects/21/05f6aaf523510f25516b04a0c07d5900df2b0b (checksum...) ok
-import .git/objects/83/daa0b1d8290191f53d1d3b5e39e03653a89ce2 (checksum...) ok
-import .git/objects/83/8fa78626a6cdc4399186172df9109d321ca0bf (checksum...) ok
-import .git/objects/dc/1e1b7b811079e1c5826d44958b736fc3a3a458 (checksum...) ok
-import .git/objects/7b/4d3d6a3ee2286b2da15c1aca39353d63c16fa2 (checksum...) ok
-import .git/objects/86/2b2a09ebc7a1eb298dccc57be75bad897a7c10 (checksum...) ok
-import .git/objects/e1/61ad2ad1843e39937caaf6add6f690fd361126 (checksum...) ok
-import .git/objects/4b/825dc642cb6eb9a060e54bf8d69288fbee4904 (checksum...) ok
-import .git/objects/9b/47feee99b5f24e0dc96cf4a20fcb88c0ec007d (checksum...) ok
-import .git/objects/b0/8c838cfb09bafae40a05312092c37360c880b0 (checksum...) ok
-import .git/refs/heads/master (checksum...) ok
-import .git/refs/heads/git-annex (checksum...) ok
-import .git/logs/HEAD (checksum...) ok
-import .git/logs/refs/heads/master (checksum...) ok
-import .git/logs/refs/heads/git-annex (checksum...) ok
-import .git/info/exclude (checksum...) ok
-import .git/hooks/pre-applypatch.sample (checksum...) ok
-import .git/hooks/applypatch-msg.sample (checksum...) ok
-import .git/hooks/pre-rebase.sample (checksum...) ok
-import .git/hooks/update.sample (checksum...) ok
-import .git/hooks/commit-msg.sample (checksum...) ok
-import .git/hooks/pre-commit (checksum...) ok
-import .git/hooks/prepare-commit-msg.sample (checksum...) ok
-import .git/hooks/post-update.sample (checksum...) ok
-import .git/hooks/pre-commit.sample (checksum...) ok
-(Recording state in git...)
-error: Invalid path 'foo/.git/COMMIT_EDITMSG'
-error: unable to add foo/.git/COMMIT_EDITMSG to index
-fatal: adding files failed
-
-git-annex: user error (xargs ["-0","git","--git-dir=/tmp/test/bar/.git","--work-tree=/tmp/test/bar","add","--"] exited 123)
-failed
-git-annex: import: 2 failed
-anarcat@angela:foo$ cd ../../foo
-anarcat@angela:foo$ git status
-fatal: Not a git repository (or any of the parent directories): .git
-anarcat@angela:foo$
-# End of transcript or log.
-"""]]
-
-Thanks! --[[anarcat]]
-
-> Would have thought this was obviously something you shouldn't do
-> (sorta like running git-annex import on your home directory),
-> but ok, it can skip .git directories. [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_importfeed_fails.mdwn b/doc/bugs/git_annex_importfeed_fails.mdwn
deleted file mode 100644
index 244ed769c..000000000
--- a/doc/bugs/git_annex_importfeed_fails.mdwn
+++ /dev/null
@@ -1,64 +0,0 @@
-### Please describe the problem.
-
-git annex importfeed fails
-
-### What steps will reproduce the  problem?
-
-git annex importfeed http://www.tatw.co.uk/podcast.xml
-
-### On what operating system?
-
-Ubuntu 12.04, the prebuilt linux tarball
-
-[[!format sh """
-$ git annex version
-git-annex version: 4.20130922-g7dc188a
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-"""]]
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-$ git annex importfeed http://www.tatw.co.uk/podcast.xml
-(checking known urls...)
-(Recording state in git...)
-importfeed http://www.tatw.co.uk/podcast.xml
---2013-09-27 12:16:09--  http://www.tatw.co.uk/podcast.xml
-Résolution de www.tatw.co.uk (www.tatw.co.uk)... 88.190.26.130
-Connexion vers www.tatw.co.uk (www.tatw.co.uk)|88.190.26.130|:80... connecté.
-requête HTTP transmise, en attente de la réponse... 200 OK
-Longueur: 41267 (40K) [application/xml]
-Sauvegarde en : «/tmp/user/2166/feed10670»
-
-100%[==========================================================================>] 41 267      81,6K/s   ds 0,5s
-
-2013-09-27 12:16:10 (81,6 KB/s) - «/tmp/user/2166/feed10670» sauvegardé [41267/41267]
-
-addurl Above___Beyond__Group_Therapy/_001_Group_Therapy_Radio_with_Above___Beyond (downloading  ...)
-failed
-addurl Above___Beyond__Group_Therapy/_002_Group_Therapy_Radio_with_Above___Beyond (downloading  ...)
-failed
-addurl Above___Beyond__Group_Therapy/_003_Group_Therapy_Radio_with_Above___Beyond (downloading  ...)
-failed
-addurl Above___Beyond__Group_Therapy/_004_Group_Therapy_Radio_with_Above___Beyond (downloading  ...)
-failed
-
-etc
-
-
-# End of transcript or log.
-"""]]
-
-> This is a bug in the feed library: <https://github.com/sof/feed/issues/7>  
-> And already fixed upstream this morning, so if you need the fix 
-> immediately, build with cabal. Otherwise fix will percolate out to
-> builds eventually.
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/git_annex_indirect_can_fail_catastrophically.mdwn b/doc/bugs/git_annex_indirect_can_fail_catastrophically.mdwn
deleted file mode 100644
index 3dc193683..000000000
--- a/doc/bugs/git_annex_indirect_can_fail_catastrophically.mdwn
+++ /dev/null
@@ -1,78 +0,0 @@
-### Please describe the problem.
-
-I have a repo that I initialized in direct mode because i felt unconfortable with the "symlink forest" approach.
-
-Now that I prefer that, i want to switch back to indirect mode. The problem is, when I did that, I realized that some files in the repo were not writable by my user, and git annex indirect crashed, and didn't "indirect" all the files. Now the repo is in a "half-direct" state, and I seem to be unable to recover.
-
-### What steps will reproduce the problem?
-
-[[!format txt """
-git init
-git annex init
-git annex direct
-git annex add . # make sure some files are not writable by your user
-git annex indirect
-"""]]
-
-The `indirect` step will stop at the file that is not writable and will fail to move some files to `.git/annex`. And then the repo is in `indirect` mode yet some files are still not symlinks.
-
-Doing a `git annex direct` will try to commit all those nasty files into git, as it does a `git commit -a`.
-
-### What version of git-annex are you using? On what operating system?
-
-    git-annex version: 4.20130912-ga1faca3
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi
-
-Debian wheezy.
-
-### Please provide any additional information below.
-
-Ideally, there would be a way to just tell git annex it's really still in direct mode and migrate the remaining files.
-
-The workaround is, obviously, to make sure you own all those files before messing around:
-
-    chown -R you *
-    chmod -R u+w *
-
-A [[patch]], maybe, that allows you to flip cleanly between the two modes:
-
-[[!format diff """
-From a21dfc97da96883b2a088bb5f3f466296f08d858 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@koumbit.org>
-Date: Mon, 16 Sep 2013 13:58:29 -0400
-Subject: [PATCH] do not commit -a when going back to direct mode
-
-without this, if we switched to indirect mode but failed doing so
-(because of a permission problem, for example), going back to
-direct mode will commit all files to git, which we really want 
-to avoid.
-
----
- Command/Direct.hs |    1 -
- 1 file changed, 1 deletion(-)
-
-diff --git a/Command/Direct.hs b/Command/Direct.hs
-index 7835988..ed8ea6c 100644
---- a/Command/Direct.hs
-+++ b/Command/Direct.hs
-@@ -33,7 +33,6 @@ perform = do
-        showOutput
-        _ <- inRepo $ Git.Command.runBool
-                [ Param "commit"
--               , Param "-a"
-                , Param "-m"
-                , Param "commit before switching to direct mode"
-                ]
---
-1.7.10.4
-
-"""]]
-
-Any update on this? Why is `-a` used here? -- [[anarcat]]
-
-> -a is not really the problem. You certainly do usually want
-> to commit your changes before converting to direct mode.
-> 
-> [[done]]; now when this happens it catches the exception and 
-> leaves the file in direct mode, which is the same as it being
-> unlocked. --[[Joey]]
diff --git a/doc/bugs/git_annex_indirect_can_fail_catastrophically/comment_1_0b085e7e8c8e364f479574bc00c7c394._comment b/doc/bugs/git_annex_indirect_can_fail_catastrophically/comment_1_0b085e7e8c8e364f479574bc00c7c394._comment
deleted file mode 100644
index 68814881d..000000000
--- a/doc/bugs/git_annex_indirect_can_fail_catastrophically/comment_1_0b085e7e8c8e364f479574bc00c7c394._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.220"
- subject="comment 1"
- date="2013-09-25T18:57:25Z"
- content="""
-Worse than  being stuck partway converted, it fails in such a way that the file you can't write to is left stuck in .git/annex/objects/ without a symlink pointint to it. 
-
-Here is how to recover:
-
-1. run `git annex direct`
-2. run `git annex indirect`
-3. run `git annex direct`
-4. run `git annex indirect`
-5. run `git revert HEAD`
-6. run `git annex direct`
-7. fix the permission of the file
-8. run `git annex indirect`
-
-Please don't ask me why this works, but it will..
-"""]]
diff --git a/doc/bugs/git_annex_info_listings_can_be_confusing.mdwn b/doc/bugs/git_annex_info_listings_can_be_confusing.mdwn
deleted file mode 100644
index aaf2a9560..000000000
--- a/doc/bugs/git_annex_info_listings_can_be_confusing.mdwn
+++ /dev/null
@@ -1,33 +0,0 @@
-### Please describe the problem.
-
-The output of git-annex info can be confusing as the format rules change based on positioning
-
-    repository mode: indirect
-    trusted repositories: 0
-    semitrusted repositories: 5
-        00000000-0000-0000-0000-000000000001 -- web
-        105776ba-bd78-4884-9126-aeb7c1e6da21 -- UoM Laptop
-        79ff3c20-fab3-44dd-88f7-cc1a41eb73d6 -- here (UoM Desktop Client)
-        949a8fc3-6334-5f5e-887d-b1e5725ea443 -- isilon (UoM Isilon Encrypted Git Backup)
-        c3cec307-367b-4373-8cb9-a3da67cee745 -- home (Mac Mini Home Client)
-
-Here we see the description surrounded in brackets and also not in brackets.  The second annex listed does not have a name (as there is no git remote configured).  Always including the brackets or an additional setting I think would make things much clearer esp. when setting things up.
-
-    
-### What steps will reproduce the problem?
-
-
-### What version of git-annex are you using? On what operating system?
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-[[done]] --[[Joey]] 
diff --git a/doc/bugs/git_annex_initremote_needs_some___34__error_checking__34__.mdwn b/doc/bugs/git_annex_initremote_needs_some___34__error_checking__34__.mdwn
deleted file mode 100644
index 6b57f8ce5..000000000
--- a/doc/bugs/git_annex_initremote_needs_some___34__error_checking__34__.mdwn
+++ /dev/null
@@ -1,65 +0,0 @@
-_git annex initremote_ without a complete command set still adds an entry to the uuid.log etc... and thus clutters up the state of the annex. I would not have expected this behaviour as a user.
-
-_initremote_ should fail and not do anything if the commands that it has been given are incomplete or incorrect. I was initialising a few rsync repos and noticed that i ended up having mutiple rsync remotes with the same name but different uuid's. I know its hard if not impossible to remove these uuid's so I have just marked them as "dead" in my live annexes.
-
-Here's a transcript of the problem
-
-<pre>
-x00:sandbox jtang$ mkdir atest
-x00:sandbox jtang$ cd atest/
-x00:atest jtang$ git init
-Initialized empty Git repository in /Users/jtang/sandbox/atest/.git/
-x00:atest jtang$ git annex init 
-init  ok
-(Recording state in git...)
-x00:atest jtang$ git annex status
-supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
-supported remote types: git S3 bup directory rsync web hook
-trusted repositories: 0
-semitrusted repositories: 2
-	00000000-0000-0000-0000-000000000001 -- web
- 	cbb58e1c-d737-11e1-b682-83239d5ff2e0 -- here
-untrusted repositories: 0
-dead repositories: 0
-transfers in progress: none
-available local disk space: 185 gigabytes (+1 megabyte reserved)
-local annex keys: 0
-local annex size: 0 bytes
-known annex keys: 0
-known annex size: 0 bytes
-bloom filter size: 16 mebibytes (0% full)
-backend usage: 
-x00:atest jtang$ git annex initremote foo
-git-annex: Specify the type of remote with type=
-x00:atest jtang$ git annex initremote foo type=rsync
-(Recording state in git...)
-initremote foo git-annex: Specify encryption=key or encryption=none or encryption=shared
-x00:atest jtang$ git annex initremote foo type=rsync
-(Recording state in git...)
-initremote foo git-annex: Specify encryption=key or encryption=none or encryption=shared
-x00:atest jtang$ git annex status
-supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
-supported remote types: git S3 bup directory rsync web hook
-trusted repositories: (Recording state in git...)
-0
-semitrusted repositories: 5
-	00000000-0000-0000-0000-000000000001 -- web
- 	cbb58e1c-d737-11e1-b682-83239d5ff2e0 -- here
- 	d3adfcd0-d737-11e1-b15b-b7032388f8aa -- foo
- 	d6d8e1e0-d737-11e1-956a-0b3d3451226a -- foo
- 	d78d795c-d737-11e1-ac98-4fe3d6fdfd54 -- foo
-untrusted repositories: 0
-dead repositories: 0
-transfers in progress: none
-available local disk space: 185 gigabytes (+1 megabyte reserved)
-local annex keys: 0
-local annex size: 0 bytes
-known annex keys: 0
-known annex size: 0 bytes
-bloom filter size: 16 mebibytes (0% full)
-backend usage: 
-x00:atest jtang$ 
-</pre>
-
-> Indeed, I broke that in June by making it record the name in a much too
-> early stage. Now fixed. [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_initremote_walks_.git-annex.mdwn b/doc/bugs/git_annex_initremote_walks_.git-annex.mdwn
deleted file mode 100644
index acd369bde..000000000
--- a/doc/bugs/git_annex_initremote_walks_.git-annex.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-a <!-- (a suggestion for introducing severity tags on bugs,
-feel free to discard) --> issue: `git annex initremote` (in particular, adding
-a key as described in [[encryption]] -- `git annex initremote my_remote
-encryption=my_key`) seems to iterate over the `.git-annex/???/???/*.log` files
-with lstat (tested using strace).
-
-in a 50k key git-annex on a slow disk, this takes quite a while, while not
-seeming necessary (it's just re-encrypting the shared secret, is it?).
-
-could you verify the observed behavior?
-
-> This is due to `git commit` being called. `git commit` exposes git's 
-> rather innefficient handling of the index; in order to make a commit
-> it has to write a new index file, and it does this by scanning every
-> file in the repository. I think that git generally needs its index
-> file handleing overhauled, particularly to deal with repositories with
-> large numbers of files. git-annex is seems to already be running
-> `git commit` in its most efficient mode, by specifying exactly what file
-> to commit. [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_lock_dangerous.mdwn b/doc/bugs/git_annex_lock_dangerous.mdwn
deleted file mode 100644
index ae0ff24b6..000000000
--- a/doc/bugs/git_annex_lock_dangerous.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-### Please describe the problem.
-
-Git annex lock discards data without --force; this is misleading from the name.
-
-### What steps will reproduce the problem?
-
-    git annex unlock something.txt
-    kwrite something.txt # edit
-    git annex lock something.txt # lock is the opposite of unlock, right?
-
-Oops, just lost my changes!
-
-If you want my opinion, `git annex lock` should either require `-f` to throw away data or should be renamed (e.g. to `revert` or `checkout`).
-
-### What version of git-annex are you using? On what operating system?
-
-git version 1.8.1.2, git-annex version: 4.20130815, Kubuntu 13.04
-
-> Agreed; [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn b/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn
deleted file mode 100644
index 263338d64..000000000
--- a/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-`git annex migrate` leaves old, unlinked backend versions lying around. It
-would be great if these were purged automatically somehow. 
-
-> Yes, this is an issue mentioned in the
-> [[tips/migrating_data_to_a_new_backend]].
-> 
-> Since multiple files can point to the same content, it could be that
-> only one file has been migrated, and the content is still used. So
-> the content either has to be retained, or an operation as expensive
-> as `git annex unused` used to find if something else still uses it. 
-> 
-> Rather than adding such an
-> expensive operation to each call to migrate, I focused on hard-linking
-> the values for the old and new keys, so that the old keys don't actually
-> use any additional resources (beyond an extra inode).
-> 
-> This way a lot of migrations can be done, and only when you're done you
-> can do the more expensive cleanup pass if you want to. --[[Joey]]
-> [[done]]
diff --git a/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around/comment_1_f3e418144e5a5a9b3eda459546fc2bb0._comment b/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around/comment_1_f3e418144e5a5a9b3eda459546fc2bb0._comment
deleted file mode 100644
index dac018cfa..000000000
--- a/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around/comment_1_f3e418144e5a5a9b3eda459546fc2bb0._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://nicolas-schodet.myopenid.com/"
- ip="2a01:e35:8ae6:f130:1e4b:d6ff:fe78:1ddb"
- subject="Hardlink on remote repository?"
- date="2013-08-15T06:58:16Z"
- content="""
-Does the hardlink magic also work on the remote repository? If I understand correctly, the remote does not know that the new hash is the same file (and also, file needs to be transferred again) unless the migration is done on all remote before synchronizing. Is it right?
-"""]]
diff --git a/doc/bugs/git_annex_should_use___39__git_add_-f__39___internally.mdwn b/doc/bugs/git_annex_should_use___39__git_add_-f__39___internally.mdwn
deleted file mode 100644
index a92f5871b..000000000
--- a/doc/bugs/git_annex_should_use___39__git_add_-f__39___internally.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-I have this line in the .gitignore file of one of my repos:
-*log
-
-So the command 'git annex init name' fails to add the file ".git-annex/uuid.log", and the same problem happens when git-annex-add'ing files.
-
-> This is avoided on the v3 branch, which does not store these files in the
-> same branch as your repository.
-
-Also, when a file is git-ignored, it should be possible to 'git annex add' it with a -f/--force option, the same way git does it.
-
-> Reasonable, [[done]] --[[Joey]] 
diff --git a/doc/bugs/git_annex_should_use___39__git_add_-f__39___internally/comment_1_7683bf02cf9e97830fb4690314501568._comment b/doc/bugs/git_annex_should_use___39__git_add_-f__39___internally/comment_1_7683bf02cf9e97830fb4690314501568._comment
deleted file mode 100644
index c556fbd77..000000000
--- a/doc/bugs/git_annex_should_use___39__git_add_-f__39___internally/comment_1_7683bf02cf9e97830fb4690314501568._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnpdM9F8VbtQ_H5PaPMpGSxPe_d5L1eJ6w"
- nickname="Rafaël"
- subject="comment 1"
- date="2011-07-03T11:56:45Z"
- content="""
-And what about emitting a warning, as git does, that some files were not annex-added (when not using --force)?
-"""]]
diff --git a/doc/bugs/git_annex_sync___40__sync_content_without_--content_flag__41__.mdwn b/doc/bugs/git_annex_sync___40__sync_content_without_--content_flag__41__.mdwn
deleted file mode 100644
index d2b4ddb72..000000000
--- a/doc/bugs/git_annex_sync___40__sync_content_without_--content_flag__41__.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-### Please describe the problem.
-
-Not sure if it's a bug, but pls explain why it sync files and how to stop it by cfg.
-
-Repos. created with Assistant - git annex sync i an indirect mode not only fetch metadata but also a files. What is the correct way to disable file sync (so only broken links are created in working tree)
-
-Desired:
-to boostrap annex infrastructure with assistant, but then some repos switch to indirect mode (while still synced by assistant/webapp) but only metadata (not files). Files to be fetched on request (like git annex get xyz/*) when needed.
-
-### What steps will reproduce the problem?
-
-1. with git annex webapp create two repos on two nodes (Alice and Bob).
-2. pair them using discovery on local lan
-3. on Bob stop assistant and fire "git annex indirect"
-4. add files to Alice repo
-5. run git annex sync on Bob repo from CLI
-
-Bob's repo not only sync metadata but also retrive files.
-The documentation says "sync" only sync metadata.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 5.20140420-ga25b8bb
-
-> `git annex sync`, when used without --content, does not sync the content
-> of files. However, in your example, Alice is still runing the assistant.
-> The assistant will notice when Bob's git annex sync sends it a change,
-> and see there are new files, and go get them. If you don't want that to
-> happen, you'll need to disable the assistant on Alice too, or configure
-> it to not sync with bob, etc.
-> 
-> Not a bug, so [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_sync___40__sync_content_without_--content_flag__41__/comment_1_a797542acb1f0c51dd4c75e4566558f0._comment b/doc/bugs/git_annex_sync___40__sync_content_without_--content_flag__41__/comment_1_a797542acb1f0c51dd4c75e4566558f0._comment
deleted file mode 100644
index 4f35163f6..000000000
--- a/doc/bugs/git_annex_sync___40__sync_content_without_--content_flag__41__/comment_1_a797542acb1f0c51dd4c75e4566558f0._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 1"
- date="2014-04-30T20:54:05Z"
- content="""
-On this screen: http://git-annex.branchable.com/assistant/example.png  click settings next to each repo
-
-Set the type to manual: https://git-annex.branchable.com/assistant/repogroups.png
-"""]]
diff --git a/doc/bugs/git_annex_test_under_windows_8.1.mdwn b/doc/bugs/git_annex_test_under_windows_8.1.mdwn
deleted file mode 100644
index 2ca64eb61..000000000
--- a/doc/bugs/git_annex_test_under_windows_8.1.mdwn
+++ /dev/null
@@ -1,67 +0,0 @@
-### Please describe the problem.
-I installed git and git annex under Windows (8.1) and ran git annex test. All except one tests passed with "ok"
-
-### What steps will reproduce the problem?
-git annex test 
-under Windows 8.1
-
-### What version of git-annex are you using? On what operating system?
-$ git --version
-git version 1.9.0.msysgit.0
-
-$ git annex version
-git-annex version: 5.20140320-g63535e3
-build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL 
-remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external local repository version: 5 supported repository version: 5 upgrade supported from repository versions: 2 3 4
-
-Windows 8.1
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-    prop_view_roundtrips:                           FAIL
-      *** Failed! Falsifiable (after 814 tests and 5 shrinks):
-      "a"
-      IMneitta DTaetsat s(
-fr o miLniistt:  [(MetaField "1\194",fromList [MetaValue (CurrentlySet True) "\r
-+\231Gb\157\227\ETB\bG",MetaValue (CurrentlySet True) "\DEL\239~\243_p\DC2."]),(
-MetaField "EG",fromList [MetaValue (CurrentlySet True) "",MetaValue (CurrentlySe
-t True) "\v\205] .T(",MetaValue (CurrentlySet False) "\NAK\128lo\169w",MetaValue
- (CurrentlySet True) "\SYN\STX\ENQ\n#u\ETXv\CANP<F)",MetaValue (CurrentlySet Fal
-se) "\US\213~",MetaValue (CurrentlySet False) "K\r3\v\165\&0\RSqk#\141",MetaValu
-e (CurrentlySet False) "Kx\b\231\156\220?+\216\v\146",MetaValue (CurrentlySet Tr
-ue) "j.\189\150\FS3{\233S\STX\SItg",MetaValue (CurrentlySet True) "\242\248\134\
-206\bal\174\135A\SI"]),(MetaField "k",fromList [MetaValue (CurrentlySet True) "\
-FS\150\129\b\fhjV\DC3\203",MetaValue (CurrentlySet False) "V.&sZ\245\f\a_\227\14
-0",MetaValue (CurrentlySet True) "\136r\ENQK{/\SI'\SYNN\235Q?",MetaValue (Curren
-tlySet True) "\179\255\233\227v\SUB]\n8",MetaValue (CurrentlySet True) "\238S\DC
-1"]),(MetaField "\179",fromList [MetaValue (CurrentlySet True) "\SOH+\ENQ",MetaV
-alue (CurrentlySet True) "\ACK{\140\248I\DLEw^\\\ENQF4",MetaValue (CurrentlySet
-False) "\FSc\239\r)HL\STX#V\DC1",MetaValue (CurrentlySet True) "Hc\219\146\230\1
-79\207",MetaValue (CurrentlySet False) "I]",MetaValue (CurrentlySet False) "P\19
-6\&0o\214\&8iH\251",MetaValue (CurrentlySet True) "`X",MetaValue (CurrentlySet F
-alse) "u\DEL\DC3Q\200",MetaValue (CurrentlySet True) "\128?",MetaValue (Currentl
-ySet True) "\225\135\f>\128\US~p",MetaValue (CurrentlySet False) "\250C\b\DC1\17
-6\154KT\191\SOf?\SI"]),(MetaField "\225a",fromList [MetaValue (CurrentlySet True
-) "",MetaValue (CurrentlySet True) "\b\ETB\b",MetaValue (CurrentlySet True) "\f\
-161\FS\176h-\ta\169\t",MetaValue (CurrentlySet False) "4",MetaValue (CurrentlySe
-t True) "A\FS\244V:\249kl5\ETX\SOH\SI)",MetaValue (CurrentlySet False) "Z",MetaV
-alue (CurrentlySet True) "\\Lt~\235v\"\211\DLE\NAK\210",MetaValue (CurrentlySet
-False) "a\SYNN",MetaValue (CurrentlySet True) "g:init test repo U5j\167G\ap-\ETX
-",MetaValue (CurrentlySet False) "l\NULoW\238rD",MetaValue (CurrentlySet True) "
-}\202\141\183Nxr",MetaValue (CurrentlySet False) "\170=\216S\ETB\187\SUB+!\DC3",
-MetaValue (CurrentlySet True) "\240H\GS\NAK\ETB\SYNRq\153\&4\204\EOT"])])
-      True
-      Use --quickcheck-replay '13 347062936 40785707' to reproduce.
-    prop_viewedFile_rountrips:                      OK
-      +++ OK, passed 1000 t
-e s tDse.t
-
-# End of transcript or log.
-"""]]
-
-> A sort of windows-specific bug in the test suite. I've fixed it. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/git_annex_uninit_loses_content_when_interrupted.mdwn b/doc/bugs/git_annex_uninit_loses_content_when_interrupted.mdwn
deleted file mode 100644
index e7698883f..000000000
--- a/doc/bugs/git_annex_uninit_loses_content_when_interrupted.mdwn
+++ /dev/null
@@ -1,33 +0,0 @@
-### Please describe the problem.
-
-When git annex uninit is interrupted, git status shows
-
-# On branch master
-# Changes to be committed:
-#   (use "git reset HEAD <file>..." to unstage)
-
-deleted:    file1
-
-file1 is the file that was being processed at the time of the interrupt.
-
-### What steps will reproduce the problem?
-
-git annex uninit
-
-Ctrl-C
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130709
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; see my comment --[[Joey]]
diff --git a/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment b/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment
deleted file mode 100644
index f9865ca69..000000000
--- a/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.90"
- subject="comment 1"
- date="2013-07-16T18:29:37Z"
- content="""
-All you have to do to get file1 back is check its symlink back out of git's history. `git checkout file1` should suffice to recover. \"Loses content\" is way overstating the severity of this bug.
-"""]]
diff --git a/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment b/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment
deleted file mode 100644
index 2b6fc4186..000000000
--- a/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_2_0e99f6ef4f8b342ef0ebc64dbf8e2ce6._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.90"
- subject="comment 2"
- date="2013-07-16T19:08:49Z"
- content="""
-However, if you then run `git annex uninit` a second time, it goes ahead and deletes the content! That is a bug.
-
-I looked into trying to make uninit always replace the symlink atomically with the file content. It can't be done when using --fast, since it's not possible to atomically replace a symlink with a hard link (AFAIK). It should be possible to do it in the normal mode, but it would require manually constructing a commit, since git does not provide a way to delete a file from the index and commit that staged change without also committing any other changes that are staged -- and uninit should preseve any changes to non-annexed files that the user has staged. So, I don't think atomic operation is the right answer.
-
-Instead, I have made uninit refuse to delete .git/annex/objects unless it's empty, and if objects are still left in there, for whatever reason, it'll fail at the end with a nice message explaining some options. I think this is the right fix because it also avoids uninit removing historical versions of files that were stored in git-annex.g
-"""]]
diff --git a/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex.mdwn b/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex.mdwn
deleted file mode 100644
index 71fd408e2..000000000
--- a/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-### Please describe the problem.
-
-Suppose there are files not added/committed to git annex.
-Once git annex uninit is complete, these files are deleted.
-
-### What steps will reproduce the problem?
-
-cp big-file annex-dir;
-cd annex-dir;
-git annex uninit
-
-...
-big-file is gone
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130709
-Linux Ubuntu 13.04
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-[[!tag moreinfo]]
-
-> [[done]]; unreproducible by anyone. --[[Joey]]
diff --git a/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment b/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment
deleted file mode 100644
index bf5f04a90..000000000
--- a/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.90"
- subject="comment 1"
- date="2013-07-16T18:21:18Z"
- content="""
-I can't reproduce that. uninit leaves alone files that are not checked into git. Indeed, it only ever does anything to files that are checked into git and are symlinks to git-annex content. So I don't see how it could possibly behave as described.
-
-Please provide a complete transcript of the problem you are seeing.
-"""]]
diff --git a/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_2_3aa125635609fce41ab0c98cefb81f98._comment b/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_2_3aa125635609fce41ab0c98cefb81f98._comment
deleted file mode 100644
index dec43f390..000000000
--- a/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_2_3aa125635609fce41ab0c98cefb81f98._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog"
- nickname="Michael"
- subject="can't reproduce this anymore"
- date="2013-07-17T17:04:05Z"
- content="""
-This could have been a PEBKAC.
-
-"""]]
diff --git a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems.mdwn b/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems.mdwn
deleted file mode 100644
index fb0bdb093..000000000
--- a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-What steps will reproduce the problem?
-I don't know exactly when it started
-
-What is the expected output? What do you see instead?
-When I run git annex unused I get
-
-    unused . (checking for unused data...) (checking master...) git-annex: Cannot decode byte '\xb4': Data.Text.Encoding.decodeUtf8: Invalid UTF-8 stream
-
-Most likely I have added some file with a strange encoding that git-annex can't decode. The problem is that the unused process aborts because of this.
-
-What version of git-annex are you using? On what operating system?
- 3.20120522, Debian testing
-
-> I've just fixed this bug in git, will be in the next release. --[[Joey]]
-> [[done]]
diff --git a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_1_8ba4fdb9f2d3bd44db5e910526cb9124._comment b/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_1_8ba4fdb9f2d3bd44db5e910526cb9124._comment
deleted file mode 100644
index ddea8225e..000000000
--- a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_1_8ba4fdb9f2d3bd44db5e910526cb9124._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.2.6"
- subject="comment 1"
- date="2012-06-20T14:30:27Z"
- content="""
-Try running `git annex unused --debug`; this will tell us the git command that's outputing the data it cannot process. Then you can try running that git command and see what the problem filename is.
-"""]]
diff --git a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_2_2a4a2b3e287a0444a1c8e8d98768a206._comment b/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_2_2a4a2b3e287a0444a1c8e8d98768a206._comment
deleted file mode 100644
index 8afe3143c..000000000
--- a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_2_2a4a2b3e287a0444a1c8e8d98768a206._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.2.6"
- subject="comment 2"
- date="2012-06-20T14:34:23Z"
- content="""
-Your `locale` setting may also be relevant. FWIW, I've tried to create a file with `\xb4` in its name and have not gotten git-annex unused to crash on it.
-"""]]
diff --git a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_3_dacfdb8322045fc4ceefc9128bf7c505._comment b/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_3_dacfdb8322045fc4ceefc9128bf7c505._comment
deleted file mode 100644
index 8e2aa285a..000000000
--- a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_3_dacfdb8322045fc4ceefc9128bf7c505._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnXgp-iIaBK5pnk22xqMVERQb97VyXaejs"
- nickname="Kristian"
- subject="comment 3"
- date="2012-06-20T14:37:09Z"
- content="""
-This is what happens when I add the debug parameter
-
-git annex unused --debug
-
-unused . (checking for unused data...) git [\"--git-dir=/home/kristian/AnnexMedia/.git\",\"--work-tree=/home/kristian/AnnexMedia\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"/home/kristian/AnnexMedia\"]
-git [\"--git-dir=/home/kristian/AnnexMedia/.git\",\"--work-tree=/home/kristian/AnnexMedia\",\"show-ref\"]
-(checking master...) git [\"--git-dir=/home/kristian/AnnexMedia/.git\",\"--work-tree=/home/kristian/AnnexMedia\",\"ls-tree\",\"--full-tree\",\"-z\",\"-r\",\"--\",\"refs/heads/master\"]
-git [\"--git-dir=/home/kristian/AnnexMedia/.git\",\"--work-tree=/home/kristian/AnnexMedia\",\"cat-file\",\"--batch\"]
-git-annex: Cannot decode byte '\xb4': Data.Text.Encoding.decodeUtf8: Invalid UTF-8 stream
-
-"""]]
diff --git a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_4_7889a3ff5ce80c6322448aa674df8525._comment b/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_4_7889a3ff5ce80c6322448aa674df8525._comment
deleted file mode 100644
index da97b12f7..000000000
--- a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_4_7889a3ff5ce80c6322448aa674df8525._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.2.6"
- subject="comment 4"
- date="2012-06-20T14:49:09Z"
- content="""
-Ah, reproduced it; need to use the WORM backend and have the file present in another branch..
-
-
-"""]]
diff --git a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_5_6d28c2537ce24eeb3496ca349823defd._comment b/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_5_6d28c2537ce24eeb3496ca349823defd._comment
deleted file mode 100644
index fafd1d248..000000000
--- a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_5_6d28c2537ce24eeb3496ca349823defd._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnXgp-iIaBK5pnk22xqMVERQb97VyXaejs"
- nickname="Kristian"
- subject="comment 5"
- date="2012-06-20T14:55:33Z"
- content="""
-I checkout out the git annex branch and using 
-
-    find * | grep -P \"[\xb4]\"
-
-I found a file
-
-    43e/b16/WORM-s4118528-m1245167306--Jerry Lee Lewis - Whole Lotta Shakin\302\264 Going\302\264 On.mp3.log   
-
-The corresponding file also existed in the master branch (as a link).
-
-I moved both these files to a folder outside my repository and synched my git-annex branch with by master server. I still get the same error. Is there any other place where information about this file is stored?
-
-"""]]
diff --git a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_6_4bf14ecef622988e80976c0fb55c24b9._comment b/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_6_4bf14ecef622988e80976c0fb55c24b9._comment
deleted file mode 100644
index b35e31da6..000000000
--- a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_6_4bf14ecef622988e80976c0fb55c24b9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.2.6"
- subject="comment 6"
- date="2012-06-20T16:59:53Z"
- content="""
-git-annex was not crashing due to content in the git-annex branch, but due to a symlink in one of your regular git branches, probably master and origin/master. 
-
-This bug is fixed in git master, if you need the fix before the next release.
-"""]]
diff --git a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_7_d2e5382fe0f38fb9dd9ee69901c68151._comment b/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_7_d2e5382fe0f38fb9dd9ee69901c68151._comment
deleted file mode 100644
index 65a02fed9..000000000
--- a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_7_d2e5382fe0f38fb9dd9ee69901c68151._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmL8pteP2jbYJUn1M3CbeLDvz2SWAA1wtg"
- nickname="Kristian"
- subject="comment 7"
- date="2012-06-20T20:49:06Z"
- content="""
-Thank you
-"""]]
diff --git a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_8_b282757537cda863d3dc6d0bbfd6b656._comment b/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_8_b282757537cda863d3dc6d0bbfd6b656._comment
deleted file mode 100644
index ff1de6b2e..000000000
--- a/doc/bugs/git_annex_unused_aborts_due_to_filename_encoding_problems/comment_8_b282757537cda863d3dc6d0bbfd6b656._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnXgp-iIaBK5pnk22xqMVERQb97VyXaejs"
- nickname="Kristian"
- subject="comment 8"
- date="2012-06-21T07:08:22Z"
- content="""
-Confirmed. I built the newest version of git-annex and it solved the issue :)
-"""]]
diff --git a/doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent.mdwn b/doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent.mdwn
deleted file mode 100644
index 86151d116..000000000
--- a/doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent.mdwn
+++ /dev/null
@@ -1,106 +0,0 @@
-The "git annex unused" command considers remote branches as well as local branches.  This means that an
-object may be considered unused or not depending on what remotes are present and when they were last synced.
-
-I ran into this issue when experimenting with using repos on removable storage.  I'll post more about
-what I was trying to do in the forum.  I'm posting this in bugs as I believe the inconsistent behavior
-should probably be considered a bug.
-
-#What steps will reproduce the problem?
-
-Here is a sample session illustrating the problem.  At the end, you can see that the object is
-not shown as unused, then the remote is removed and it is shown as unused, then the remote is added
-back and the file is once again not shown as unused.
-
-    /tmp/git $ mkdir 1 2
-    /tmp/git $ cd 1
-    /tmp/git/1 $ git init
-    Initialized empty Git repository in /tmp/git/1/.git/
-    /tmp/git/1 $ git annex init 1
-    init 1 ok
-    (Recording state in git...)
-    /tmp/git/1 $ git remote add 2 ../2
-    /tmp/git/1 $ dd if=/dev/urandom of=file.bin count=100
-    100+0 records in
-    100+0 records out
-    51200 bytes (51 kB) copied, 0.0113172 s, 4.5 MB/s
-    /tmp/git/1 $ git annex add file.bin 
-    add file.bin (checksum...) ok
-    (Recording state in git...)
-    /tmp/git/1 $ git commit -m 'added file'
-    [master (root-commit) 3c1ad30] added file
-     1 files changed, 1 insertions(+), 0 deletions(-)
-     create mode 120000 file.bin
-    /tmp/git/1 $ cd ../2
-    /tmp/git/2 $ git init
-    Initialized empty Git repository in /tmp/git/2/.git/
-    /tmp/git/2 $ git annex init 2
-    init 2 ok
-    (Recording state in git...)
-    /tmp/git/2 $ git remote add 1 ../1
-    /tmp/git/2 $ git fetch 1
-    warning: no common commits
-    remote: Counting objects: 13, done.
-    remote: Compressing objects: 100% (9/9), done.
-    remote: Total 13 (delta 0), reused 0 (delta 0)
-    Unpacking objects: 100% (13/13), done.
-    From ../1
-     * [new branch]      git-annex  -> 1/git-annex
-     * [new branch]      master     -> 1/master
-    /tmp/git/2 $ git checkout -b master 1/master
-    Branch master set up to track remote branch master from 1.
-    Already on 'master'
-    /tmp/git/2 $ cd ../1
-    /tmp/git/1 $ git fetch 2
-    remote: Counting objects: 5, done.
-    remote: Compressing objects: 100% (3/3), done.
-    remote: Total 5 (delta 0), reused 0 (delta 0)
-    Unpacking objects: 100% (5/5), done.
-    From ../2
-     * [new branch]      git-annex  -> 2/git-annex
-     * [new branch]      master     -> 2/master
-    /tmp/git/1 $ git rm file.bin 
-    rm 'file.bin'
-    /tmp/git/1 $ git commit -m 'rmed file'
-    [master ab242b0] rmed file
-     1 files changed, 0 insertions(+), 1 deletions(-)
-     delete mode 120000 file.bin
-    /tmp/git/1 $ git annex unused
-    unused . (checking for unused data...) (checking master...) (checking 2/master...) ok
-    /tmp/git/1 $ git remote rm 2
-    /tmp/git/1 $ git annex unused
-    unused . (checking for unused data...) (checking master...) 
-      Some annexed data is no longer used by any files:
-        NUMBER  KEY
-        1       SHA256E-s51200--e400e5abea095ad4364d8f97c5fe1a3f8a6db670b2dfee951d7c9674afc9a21d.bin
-      (To see where data was previously used, try: git log --stat -S'KEY')
-      
-      To remove unwanted data: git-annex dropunused NUMBER
-      
-    ok
-    /tmp/git/1 $ git remote add 2 ../2
-    /tmp/git/1 $ git fetch 2
-    From ../2
-     * [new branch]      git-annex  -> 2/git-annex
-     * [new branch]      master     -> 2/master
-    /tmp/git/1 $ git annex unused
-    unused . (checking for unused data...) (checking master...) (checking 2/master...) ok
-    /tmp/git/1 $ 
-
-
-#What is the expected output? What do you see instead?
-
-I expected that the object's unused status would not change based on which remotes this particular
-repo knows about.  In other words, I expected the unused status to be based on the local branches
-and possibly information in the git-annex branch.
-
-#What version of git-annex are you using? On what operating system?
-
-Gentoo Linux, git annex version 3.20121211
-
-#Please provide any additional information below.
-
-The forum post describing what I was trying to accomplish is [[forum/Best way to manage files on removable media?]]
-
-> While it would be nice if git-annex unused could somehow know about
-> branches that exist on remotes that git doesn't have locally, this is
-> impossible. It does the best it can. [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent/comment_1_a636ffe55b11c46a0afcc0b9a3a88cd4._comment b/doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent/comment_1_a636ffe55b11c46a0afcc0b9a3a88cd4._comment
deleted file mode 100644
index 97af66bc7..000000000
--- a/doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent/comment_1_a636ffe55b11c46a0afcc0b9a3a88cd4._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.126"
- subject="comment 1"
- date="2012-12-23T19:51:52Z"
- content="""
-The goal is not to consider an object unused that some other remote is known to rely on. We try as hard as we can to avoid losing data, at the expense of possibly not dropping unused content as early as possible.
-
-Running `git annex sync` or similar to get current with the state of all remotes before dropping objects they might still rely on seems reasonable from this perspective.
-"""]]
diff --git a/doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent/comment_2_5e1ad57420efd16ae09c9e5cad55b5f2._comment b/doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent/comment_2_5e1ad57420efd16ae09c9e5cad55b5f2._comment
deleted file mode 100644
index ffc0359a8..000000000
--- a/doc/bugs/git_annex_unused_considers_remote_branches_which_makes_it_inconsistent/comment_2_5e1ad57420efd16ae09c9e5cad55b5f2._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="Steve"
- ip="92.104.175.136"
- subject="comment 2"
- date="2013-01-01T23:51:53Z"
- content="""
-I filed the bug because I thought the inconsistent behavior was bad.  For example;  If you move the data to a repo which doesn't know about the unsynced remote, it'll happily get dropped with dropunused as opposed to being considered in use in the current repo.
-
-There probably aren't too many people who want to have remotes set that are usually unreachable, and I can work around it now that I know it exists.
-
-If it is expected behavior, feel free to close the bug.
-
-"""]]
diff --git a/doc/bugs/git_annex_unused_seems_to_check_for_current_path.mdwn b/doc/bugs/git_annex_unused_seems_to_check_for_current_path.mdwn
deleted file mode 100644
index f2d301cd7..000000000
--- a/doc/bugs/git_annex_unused_seems_to_check_for_current_path.mdwn
+++ /dev/null
@@ -1,39 +0,0 @@
-When I run `git annex unused` from my repository's root it shows everything ok:
-
-    ~/annex$ git annex unused
-    unused  (checking for unused data...) ok
-
-But... When I run it from a subdirectory, it shows a lot:
-
-    ~/annex/Software$ git annex unused
-    unused  (checking for unused data...) 
-      Some annexed data is no longer pointed to by any files in the repository:
-        NUMBER  KEY
-        1       SHA1:########################################
-    ...
-        921     SHA1:########################################
-      (To see where data was previously used, try: git log --stat -S'KEY')
-      (To remove unwanted data: git-annex dropunused NUMBER)
-      ok
-
-Is this a bug or by design? By removing these "unused" files with `dropunused` I've just lost the only copy of 160 files.
-
-I am using git-annex version 836e71297b8e3b5bd6f89f7eb1198f59af985b0b
-
-> I'm very sorry you lost data.
-> 
-> But, git annex unused absolutely does not let the current directory
-> influence what it does. It always scans the entire repo from the top.
-> And I've tested it just now to make sure that in a subdirectory
-> it does the same thing as at the top. 
-> 
-> There are only two ways this could happen that I can think of:
-> 
-> 1. If "Software" were a separate git repository than "~/annex".
-> 2. If gitignores or something made `git ls-files`
->    not list the files when ran in the subdir. This seems *possible*,
->    but I don't know how to construct such an ignore.
-> 
-> --[[Joey]] 
-
->> Closing as there is no followup. [[done]] --[[Joey]] 
diff --git a/doc/bugs/git_annex_upgrade_output_is_inconsistent_and_spammy.mdwn b/doc/bugs/git_annex_upgrade_output_is_inconsistent_and_spammy.mdwn
deleted file mode 100644
index ec8a10915..000000000
--- a/doc/bugs/git_annex_upgrade_output_is_inconsistent_and_spammy.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-Upgrading from v1 to v3:
-
-    upgrade . (v1 to v2...) (moving content...) (updating symlinks...) (moving location logs...) (v2 to v3...) ..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
-      git-annex branch created
-      Be sure to push this branch when pushing to remotes.
-    ok
-
-A whirly would be preferable, imo.
-
-> Erm, I'm pretty sure you were the one who asked for there to be some
-> progress dots, Richard.
-> 
-> I'm not particularly interested in implementing a whirley that would only
-> be used in this one place, in code that very few users are going to run
-> again. I could remove the dots.. [[done]] --[[Joey]]
diff --git a/doc/bugs/git_annex_upgrade_output_is_inconsistent_and_spammy/comment_1_3a01c81efba321b0e46d1bc0426ad8d1._comment b/doc/bugs/git_annex_upgrade_output_is_inconsistent_and_spammy/comment_1_3a01c81efba321b0e46d1bc0426ad8d1._comment
deleted file mode 100644
index 4f9565517..000000000
--- a/doc/bugs/git_annex_upgrade_output_is_inconsistent_and_spammy/comment_1_3a01c81efba321b0e46d1bc0426ad8d1._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-10-29T17:03:26Z"
- content="""
-I could dig it out, but I am sure I said dots are fine and a whirly better.
-
-Still, WONTFIX is fine.
-"""]]
diff --git a/doc/bugs/git_annex_version_should_without_being_in_a_repo_.mdwn b/doc/bugs/git_annex_version_should_without_being_in_a_repo_.mdwn
deleted file mode 100644
index 5c995852b..000000000
--- a/doc/bugs/git_annex_version_should_without_being_in_a_repo_.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-was checking the version of git-annex on a machine before cloning a repo...
-
-    $ git annex version
-    git-annex: Not in a git repository.
-
-> made difficult by the Annex monad, but I made it work! --[[Joey]]
-> [[done]]
diff --git a/doc/bugs/git_annex_version_should_without_being_in_a_repo_/comment_1_e7b26eeb1a765fd83280ef907c0deef2._comment b/doc/bugs/git_annex_version_should_without_being_in_a_repo_/comment_1_e7b26eeb1a765fd83280ef907c0deef2._comment
deleted file mode 100644
index ab30d8a45..000000000
--- a/doc/bugs/git_annex_version_should_without_being_in_a_repo_/comment_1_e7b26eeb1a765fd83280ef907c0deef2._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 1"
- date="2011-11-16T03:24:30Z"
- content="""
-oh, and that probably goes for 'help' and other subcommands as well.
-"""]]
diff --git a/doc/bugs/git_annex_webapp_runs_on_wine.mdwn b/doc/bugs/git_annex_webapp_runs_on_wine.mdwn
deleted file mode 100644
index c430239eb..000000000
--- a/doc/bugs/git_annex_webapp_runs_on_wine.mdwn
+++ /dev/null
@@ -1,47 +0,0 @@
-### Please describe the problem.
-I just installed git-annex-20130601 on Gentoo and when running git annex webapp it started to run things on wine.
-
-### What steps will reproduce the problem?
-On Gentoo ~amd64:
-[[!format sh """
- ~$ layman -a haskell
- ~$ USE=webapp emerge -1 git-annex
- ~$ git annex webapp
-"""]]
-### What version of git-annex are you using? On what operating system?
-dev-vcs/git-annex-4.20130601 from https://github.com/gentoo-haskell/gentoo-haskell/tree/master/dev-vcs/git-annex
-
-On Gentoo ~amd64
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-~$ git annex webapp
-Launching web browser on file:///tmp/webapp14071.html
-libpng warning: Application built with libpng-1.6.2 but running with 1.5.13
-err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
-libpng warning: Application built with libpng-1.6.2 but running with 1.5.13
-err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
-libpng warning: Application built with libpng-1.6.2 but running with 1.5.13
-err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
-...
-fixme:exec:SHELL_execute flags ignored: 0x00000100
-fixme:exec:SHELL_execute flags ignored: 0x00000100
-fixme:exec:SHELL_execute flags ignored: 0x00000100
-...
-
-22185 me     20   0 2580M 10196  8156 S  0.0  0.1  0:00.09 ├─ start /ProgIDOpen htmlfile /home/reinis/.wine/dosdevices/z:/tmp/webapp2554.html
- 2597 me     21   1 2596M 10984  8764 S  0.0  0.1  0:01.23 ├─ c:\windows\system32\explorer.exe /desktop
- 2589 me     20   0 2581M  2344  1932 S  0.0  0.0  0:00.00 ├─ c:\windows\system32\plugplay.exe
- 2581 me     20   0 2593M  8900  7500 S  0.0  0.1  0:00.09 ├─ c:\windows\system32\winedevice.exe MountMgr
- 2577 me     20   0 2583M  2776  2272 S  0.0  0.0  0:00.00 ├─ c:\windows\system32\services.exe
- 2571 me     20   0 24960  7532   772 S 46.1  0.1  2:29.06 ├─ /usr/bin/wineserver
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; this is a misconfigured system, not a git-annex bug, 
-> and git-annex honors git config web.browser to allow working around
-> this. --[[Joey]]
diff --git a/doc/bugs/git_annex_webapp_runs_on_wine/comment_1_c71dfa42780c0fc78f88ce054e5f3ee3._comment b/doc/bugs/git_annex_webapp_runs_on_wine/comment_1_c71dfa42780c0fc78f88ce054e5f3ee3._comment
deleted file mode 100644
index e94df5783..000000000
--- a/doc/bugs/git_annex_webapp_runs_on_wine/comment_1_c71dfa42780c0fc78f88ce054e5f3ee3._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-06-14T18:10:11Z"
- content="""
-I've had one other user report having this problem. It seems that wine installs some sort of .desktop file claiming it is the One True program to use to open urls. Since git-annex uses the `xdg-open` command, and in some desktop environments that command trusts these .desktop files to be accurate and not nonsensical. So it goes ahead and opens MSIE or whatever.
-
-Happily, git has a configuration setting that you can use to tell it exactly which web browser you want, bypassing all the xdg-open nonsense:
-
-git config web.browser w3m
-
-git-annex honors this configuration setting.
-
-You may also want to investigate the .desktop file that wine has installed on your system, and file appropriate bugs with either your distribution or wine package distributor to get that fixed. It seems that it would affect any program using xdg-open, not only git-annex.
-"""]]
diff --git a/doc/bugs/git_annex_webapp_runs_on_wine/comment_2_f28441b18b0be90c1e58348455ce09d9._comment b/doc/bugs/git_annex_webapp_runs_on_wine/comment_2_f28441b18b0be90c1e58348455ce09d9._comment
deleted file mode 100644
index 9853705b3..000000000
--- a/doc/bugs/git_annex_webapp_runs_on_wine/comment_2_f28441b18b0be90c1e58348455ce09d9._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm01ida6POv7vqyUYtOlymEbJTbrImAIzM"
- nickname="Reinis"
- subject="comment 2"
- date="2013-06-14T18:49:06Z"
- content="""
-Thanks! It looks like it is a xdg issue, I can reproduce it by running xdg-open manually.
-
-Faulty file is:
-[[!format sh \"\"\"
-~$ grep -ri htmlfile .local/share/applications/
-.local/share/applications/wine-extension-htm.desktop
-~$ rm .local/share/applications/wine-extension-*
-~$ locate .desktop | parallel grep -ri htmlfile {}
-\"\"\"]]
-
-Then it tried to open with /usr/bin/emacsclient! In Gnome setting Firefox is listed as default browser, but xdg-settings thinks that it is Epiphany, what a mess..
-
-Anyways, this fixes it:
-[[!format sh \"\"\"
-~$ xdg-settings set default-web-browser firefox.desktop
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive.mdwn b/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive.mdwn
deleted file mode 100644
index 6e1c00781..000000000
--- a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive.mdwn
+++ /dev/null
@@ -1,60 +0,0 @@
-One of my remotes, on a USB drive, is behaving exceedingly strangely.  Files sometimes refuse to copy to it - whether I copy to it from my home annex, or whether I "cd" to that USB drive and try to "get" files to it.
-
-Note that the external HD is a FAT32 filesystem.  This has never caused problems in the past, but I am wondering if some of the recent work on "crippled" filesystems might have caused breakage on existing repositories which had been working well on FAT32 filesystems?
-
-What steps will reproduce the problem?
-
-On my annex, something like this:
-
-<pre>
-Talislanta Books$ git annex whereis talislanta_fantasy_roleplaying.pdf
-whereis talislanta_fantasy_roleplaying.pdf (2 copies) 
-  	d16d0d1a-3cdd-11e2-9161-67c83599f720 -- homeworld
-   	fa2bd02e-3ce2-11e2-a675-47389975a32e -- here (macbook)
-ok
-Talislanta Books$ git annex copy --to=toshiba talislanta_fantasy_roleplaying.pdf
-copy talislanta_fantasy_roleplaying.pdf ok
-Talislanta Books$ git annex whereis talislanta_fantasy_roleplaying.pdf
-whereis talislanta_fantasy_roleplaying.pdf (2 copies) 
-  	d16d0d1a-3cdd-11e2-9161-67c83599f720 -- homeworld
-   	fa2bd02e-3ce2-11e2-a675-47389975a32e -- here (macbook)
-ok
-Talislanta Books$ cd /Volumes/TOSHIBAEXT/annex/Books/archive/Talislanta\ Books/
-Talislanta Books$ git annex whereis talislanta_fantasy_roleplaying.pdf
-whereis talislanta_fantasy_roleplaying.pdf (2 copies) 
-  	d16d0d1a-3cdd-11e2-9161-67c83599f720 -- homeworld
-   	fa2bd02e-3ce2-11e2-a675-47389975a32e -- macbook
-ok
-Talislanta Books$ git annex get talislanta_fantasy_roleplaying.pdf
-Talislanta Books$ git annex whereis talislanta_fantasy_roleplaying.pdf
-whereis talislanta_fantasy_roleplaying.pdf (2 copies) 
-  	d16d0d1a-3cdd-11e2-9161-67c83599f720 -- homeworld
-   	fa2bd02e-3ce2-11e2-a675-47389975a32e -- macbook
-ok
-Talislanta Books$
-</pre>
-
-
-What is the expected output? What do you see instead?
-
-I should be able to copy files to my external hard drive, /Volumes/TOSHIBAEXT/annex
-
-
-What version of git-annex are you using? On what operating system?
-
-<pre>
-Talislanta Books$ git annex version
-git-annex version: 3.20130216
-local repository version: 3
-default repository version: 3
-supported repository versions: 3
-upgrade supported from repository versions: 0 1 2
-</pre>
-
-OS X 10.6 (lion)
-
-Please provide any additional information below.
-
-Most files are affected by this, a few are not.  I don't see any pattern to which is which.
-
-> Both bugs reported here are now [[done]]. --[[Joey]]
diff --git a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_1_7707017fbf3d92ee21d600fe0aefce4f._comment b/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_1_7707017fbf3d92ee21d600fe0aefce4f._comment
deleted file mode 100644
index 2f157417f..000000000
--- a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_1_7707017fbf3d92ee21d600fe0aefce4f._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 1"
- date="2013-02-25T06:18:58Z"
- content="""
-Just tried downgrading to 3.20130207 and the behavior is the same.  :(
-
-
-"""]]
diff --git a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_2_f3392ec3ca7392823cbad2cc9b77f54e._comment b/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_2_f3392ec3ca7392823cbad2cc9b77f54e._comment
deleted file mode 100644
index 17379f354..000000000
--- a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_2_f3392ec3ca7392823cbad2cc9b77f54e._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 2"
- date="2013-02-25T12:44:18Z"
- content="""
-Update: git annex fsck --fast --from=toshiba fixed this.  Guess I was up too late to think about the obvious.  Sorry bout that.
-
-"""]]
diff --git a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_3_b3d016a487b12748fe2c4d14300eb158._comment b/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_3_b3d016a487b12748fe2c4d14300eb158._comment
deleted file mode 100644
index f891af92e..000000000
--- a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_3_b3d016a487b12748fe2c4d14300eb158._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 3"
- date="2013-02-25T14:24:29Z"
- content="""
-This is still weird though.
-
-Setup: I have my home drive, an ssh remote, and a usb remote.
-
-Home drive is a \"client\" and the other two are \"backups.\"  numcopies = 2.
-
-WHen I start the assistant and watch it in the webapp, it starts furiously copying content in \"archive\" subdirectories from the USB remote to the home drive, and then dropping it from the USB remote!
-
-I then kill the assistant because I do not want content dropped from my backup, that's why it's a backup.
-
-Is there any way to tell *why* the assistant is doing this crazy thing?
-
-
-"""]]
diff --git a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_4_61f600511a3172f0707e5809fc444d0c._comment b/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_4_61f600511a3172f0707e5809fc444d0c._comment
deleted file mode 100644
index c8b6788f3..000000000
--- a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_4_61f600511a3172f0707e5809fc444d0c._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 4"
- date="2013-02-25T14:57:20Z"
- content="""
-Yeah, the assistant wants to drop *everything* on my USB drive.  When I vicfg I see that the usb drive repo is \"untrusted/backup/standard\".  Why in the world would the assistant want to drop everything on it?
-
-"""]]
diff --git a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_5_8cf029ac7bf3c19dcb0b613eed3b52ac._comment b/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_5_8cf029ac7bf3c19dcb0b613eed3b52ac._comment
deleted file mode 100644
index 2c133e8d0..000000000
--- a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_5_8cf029ac7bf3c19dcb0b613eed3b52ac._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 5"
- date="2013-02-25T16:02:44Z"
- content="""
-Downgrading to 3.20130207 and testing.... this seems to have been a regression since 3.20130207.  3.20130207 seems right now to be behaving normally, not trying to drop things it shouldn't.  Is it possible something went terribly wrong with preferred content settings since 3.20130207?  
-
-Still testing, but things look good so far.
-"""]]
diff --git a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_6_e40d88eba7d8aec1530ce1d32d1c85f2._comment b/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_6_e40d88eba7d8aec1530ce1d32d1c85f2._comment
deleted file mode 100644
index 830a1c631..000000000
--- a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_6_e40d88eba7d8aec1530ce1d32d1c85f2._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.210"
- subject="comment 6"
- date="2013-02-26T17:20:13Z"
- content="""
-The recent switch to using the Glob library seems to be responsible for this problem. It seems that
-with Glob, \"\*\" matches \"foo\", but not \"directory/foo\", so the \"\*\" in preferred content for backup repositories matches only files in the top directory!
-
-Writing test cases and fixing this now.
-"""]]
diff --git a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_7_b101fab9e690d1b335a1a29abab68d6c._comment b/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_7_b101fab9e690d1b335a1a29abab68d6c._comment
deleted file mode 100644
index 178b62fa7..000000000
--- a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_7_b101fab9e690d1b335a1a29abab68d6c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.210"
- subject="comment 7"
- date="2013-02-26T18:41:57Z"
- content="""
-Getting back to the original problem, it seemed to be that the remote already had the files, but the local location log was not aware of this. Perhaps because the remote got the files from somewhere else and `git annex sync` or similar had not been run to get that into into the local repo recently? Anyway, copying files to the remote was correctly detected to be unnecessary.
-
-Currently, when that happens, it does not update the local location log. That is a change made fairly recently, in 40df26757a61d4f057bcbf38cd5fe949d1c9be95, as a kind of optimisation -- I'd seen it updating the location log during mass copies when it didn't need to, which just bloats `.git`. Seems that optimisation went too far: It should avoid updating the location log when it was correct, but if the location log is wrong, it should optimistically update it.
-"""]]
diff --git a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_8_b30d32086314a7e357f3dd6608828ee5._comment b/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_8_b30d32086314a7e357f3dd6608828ee5._comment
deleted file mode 100644
index 32a801224..000000000
--- a/doc/bugs/git_annex_won__39__t_copy_files_to_my_usb_drive/comment_8_b30d32086314a7e357f3dd6608828ee5._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 8"
- date="2013-02-26T21:55:23Z"
- content="""
-Cool, glad this led to an important fix, even if it turned out to be unrelated to the thing I opened the bug report for.
-
-"""]]
diff --git a/doc/bugs/git_annix_breaks_git_commit_after_uninstall.mdwn b/doc/bugs/git_annix_breaks_git_commit_after_uninstall.mdwn
deleted file mode 100644
index a6fdab0fe..000000000
--- a/doc/bugs/git_annix_breaks_git_commit_after_uninstall.mdwn
+++ /dev/null
@@ -1,42 +0,0 @@
-Sorry to be reporting another vague bug, this one interferes with my work unfortunately.
-
-### Please describe the problem.
-After uninstalling git-annix, running git commit returns the following error:
-
-git: 'annex' is not a git command. See 'git --help'.
-
-### What steps will reproduce the problem?
-
-Install git-annex using the ubuntu ppa of fmarcier like so:
-
-    sudo apt-get install git-annex
-
-Then remove it:
-
-    sudo apt-get remove git-annex
-
-Then go to work in a git project, that is not in annex and has no relation to it. Add your changes and run commit:
-
-    git add my-new-file
-    git commit -m "added new file"
-
-I expect it to confirm the file is committed, instead I get the error message:
-  
-    git: 'annex' is not a git command. See 'git --help'.
-
-### What version of git-annex are you using? On what operating system?
-
-Ubuntu 13.04, using the PPA by marcier linked on the branchable website.
-
-> I don't think this is something I want to change.. `git-annex init`
-> installs a pre-commit hook that runs `git annex fix`. If git-annex
-> is removed that hook is left behind to fail. However, if you were really
-> using git-annex in the repo, that's the least of your troubles. If you were
-> using git-annex in the repo and stopped, then you should run `git annex uninit` to remove the hook.
->
-> The only change I could make is to have the hook check if git-annex
-> is in PATH before trying to run it. But this adds time and complexity
-> to the usual case for a edge case. And keeps cruft around in the edge case
-> rather than informing you of the problem. 
-> 
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/git_annix_breaks_git_commit_after_uninstall/comment_1_c8b1bab40d3bb2468a5bba7b116e854e._comment b/doc/bugs/git_annix_breaks_git_commit_after_uninstall/comment_1_c8b1bab40d3bb2468a5bba7b116e854e._comment
deleted file mode 100644
index 1494a876f..000000000
--- a/doc/bugs/git_annix_breaks_git_commit_after_uninstall/comment_1_c8b1bab40d3bb2468a5bba7b116e854e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://me.tinco.nl/"
- nickname="Tinco"
- subject="comment 1"
- date="2013-05-19T15:35:27Z"
- content="""
-I'm sorry, there seems to be an annex directory in the .git of that repository.. apparently I have accidentily made it an annex repository. I'm going to find out how to remove it now :)
-"""]]
diff --git a/doc/bugs/git_annix_breaks_git_commit_after_uninstall/comment_2_4173770375fca51dcaf9b974296d041a._comment b/doc/bugs/git_annix_breaks_git_commit_after_uninstall/comment_2_4173770375fca51dcaf9b974296d041a._comment
deleted file mode 100644
index a354c5516..000000000
--- a/doc/bugs/git_annix_breaks_git_commit_after_uninstall/comment_2_4173770375fca51dcaf9b974296d041a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://me.tinco.nl/"
- nickname="Tinco"
- subject="comment 2"
- date="2013-05-19T15:37:23Z"
- content="""
-Alright, found there's a pre-commit hook that performed a git annex task. I removed it and now it all works again.
-"""]]
diff --git a/doc/bugs/git_defunct_processes___40__child_of_git-annex_assistant__41__.mdwn b/doc/bugs/git_defunct_processes___40__child_of_git-annex_assistant__41__.mdwn
deleted file mode 100644
index 14eb3b329..000000000
--- a/doc/bugs/git_defunct_processes___40__child_of_git-annex_assistant__41__.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-What steps will reproduce the problem?
-
-run git annex assistant, add a file, which is picked up and pushed by the assistant.  
-
-What is the expected output? What do you see instead?
-
-a ps -ef shows a large number of defunct git processes.. for example:
-<pre>
-nelg      9622     1  0 02:01 ?        00:00:01 git-annex assistant
-nelg      9637  9622  0 02:01 ?        00:00:00 git --git-dir=/home/nelg/Downloads/test2/.git --work-tree=/home/nelg/Downloads/test2 cat-file --batch
-nelg     12080  9622  0 02:19 ?        00:00:00 [git] &lt;defunct&gt;
-nelg     12082  9622  0 02:19 ?        00:00:00 [git] &lt;defunct&gt;
-nelg     12083  9622  0 02:19 ?        00:00:00 [git] &lt;defunct&gt;
-nelg     12084  9622  0 02:19 ?        00:00:00 [git] &lt;defunct&gt;
------
-</pre>
-
-What version of git-annex are you using? On what operating system?
-
-Compiled git annex from git (cbcd208d158f8e42dda03a5eeaf1bac21045a140), on Mandriva 2010.2, 32 bit, using ghc-7.4.1.
- git version 1.7.1
-
-
-Please provide any additional information below.
-
-I also found that the version of git I have does not support the option: --allow-empty-message
-So, suggest that if the version of git installed is an older version, that the params in  Assistant/Threads/Committer.hs
-are changed to  [ Param "-m", Param "git assistant".... or something like that.
-
-I have done this on my copy for testing it.
-
-For testing, I am also using two repositories on the same computer.  I set this up from the command line, as the web app does not seem to support syncing to two different git folders on the same computer.
-
-> [[done]]; all zombies are squelched now in the assistant. --[[Joey]]
diff --git a/doc/bugs/git_defunct_processes___40__child_of_git-annex_assistant__41__/comment_1_5e3f4b63db5cd32b63fb3e6a78f9b093._comment b/doc/bugs/git_defunct_processes___40__child_of_git-annex_assistant__41__/comment_1_5e3f4b63db5cd32b63fb3e6a78f9b093._comment
deleted file mode 100644
index f70cdd1bd..000000000
--- a/doc/bugs/git_defunct_processes___40__child_of_git-annex_assistant__41__/comment_1_5e3f4b63db5cd32b63fb3e6a78f9b093._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.84"
- subject="comment 1"
- date="2012-09-19T17:02:47Z"
- content="""
-Thanks for the note about --allow-empty-message. That appeared in 1.7.2, I've added a fallback for the old version.
-
-As far as I know, the assistant always reaps old children eventually, but it does it somewhat lazily. Effectively each time it starts up a new set of git children it reaps the old set. So you should not see them grow without bounds or anything like that.
-"""]]
diff --git a/doc/bugs/git_repo_fails_to_checkout.mdwn b/doc/bugs/git_repo_fails_to_checkout.mdwn
deleted file mode 100644
index 0c3b66018..000000000
--- a/doc/bugs/git_repo_fails_to_checkout.mdwn
+++ /dev/null
@@ -1,39 +0,0 @@
-### Please describe the problem.
-
-Attempting to clone the git repository produces
-
-    (master) cayley:git-annex% git checkout -f HEAD
-    error: unable to create file doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__.mdwn (File name too long)
-    fatal: cannot create directory at 'doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__': File name too long
-
-### What steps will reproduce the problem?
-
-I get the above with either
-
-    git clone https://github.com/joeyh/git-annex
-
-or (after this fails) retrying with
-
-    cd git-annex
-    git checkout -f HEAD
-
-### What version of git-annex are you using? On what operating system?
-
-I am running git 1.9.0 from git (5f95c9f850b19b368c43ae399cc831b17a26a5ac in the git git repo) on Ubuntu 13.04.
-
-> More encfs brain-damange.
-
-	One such limitation is filename length.  If your underlying
-	filesystem limits you to N characters in a filename, then
-	EncFS will limit you to approximately 3*(N-2)/4.
- 
-> It's really astounding that Ubuntu inflicts that POS on users.
-> However, I can't see that as justification for limiting the
-> git-annex repository to filenames shorter than `PATH_MAX` -- just
-> as DOS's problems with both filename length and also `:` in filenames
-> is not a good reason to mangle the repository.
-> 
-> In either case, it's up to the user to find a way to make it work. 
-> In the DOS case, that involves using Cygwin's git. In the encfs case,
-> it presumably means checking it out into a real filesystem.
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/git_repo_fails_to_checkout/comment_1_d92e7e3b41382501a08f6a66c673b1fd._comment b/doc/bugs/git_repo_fails_to_checkout/comment_1_d92e7e3b41382501a08f6a66c673b1fd._comment
deleted file mode 100644
index 55e063f39..000000000
--- a/doc/bugs/git_repo_fails_to_checkout/comment_1_d92e7e3b41382501a08f6a66c673b1fd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://geoffreyirving.myopenid.com/"
- nickname="Geoffrey Irving"
- subject="encrypted home directory"
- date="2014-02-18T18:05:24Z"
- content="""
-It looks like this problem is related to using an encrypted home directory.
-"""]]
diff --git a/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated.mdwn b/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated.mdwn
deleted file mode 100644
index e5960b62e..000000000
--- a/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-### Please describe the problem.
-I created a .gitignore file and added it to git annex. In the assistant webapp log, the error "The installed version of git is too old for .gitignores to be honored by git-annex." shows up. According to [[bugs/assistant_ignore_.gitignore/]] this bug should be fixed in a later git version.
-
-### What steps will reproduce the problem?
-Download the current prebuilt linux tarball from [[/install]], extract it, run "./runshell", then "git --version" returns "git version 1.7.10.4"
-
-### What version of git-annex are you using? On what operating system?
-git-annex-standalone-amd64.tar.gz	2013-09-22 09:56 (Linux Ubuntu Precise)
-
-> Updated to wheezy backport 1.8.4. [[done]] for now, obviously it will go
-> out of date again eventually.. --[[Joey]]
diff --git a/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated/comment_1_2a5a07498df9d38531d4570f7b463b9a._comment b/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated/comment_1_2a5a07498df9d38531d4570f7b463b9a._comment
deleted file mode 100644
index 5287ea935..000000000
--- a/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated/comment_1_2a5a07498df9d38531d4570f7b463b9a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.220"
- subject="comment 1"
- date="2013-09-25T18:18:49Z"
- content="""
-The tarballs are built on Debian stable in order to have an old enough libc to work most places. So I am limited to what is available in stable and backports. Once there is a backport available of git, I will use it.
-"""]]
diff --git a/doc/bugs/gix-annex_help_is_homicidal.mdwn b/doc/bugs/gix-annex_help_is_homicidal.mdwn
deleted file mode 100644
index f4a8d7213..000000000
--- a/doc/bugs/gix-annex_help_is_homicidal.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-> What steps will reproduce the problem?
-
-Run 'git-annex help'
-
-> What is the expected output?
-
-Something similar to 'git-annex --help', or a pointer to --help.
-
-> What do you see instead?
-
-    git-annex: Unknown command 'help'
-    Did you mean one of these?
-    	drop
-    	dead
-
-> What version of git-annex are you using? On what operating system?
-
-git-annex version 3.20120825 on Arch Linux x86_64, installed from AUR package git-annex and using the [haskell] repository for dependencies.
-
->> Lol, that's great! Also worth noting that with help.autocorrect=1, it'd
->> actually run drop. Only with --force can you lose data however.
->>
->> I've added a help command. [[done]] --[[Joey]]
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails.mdwn b/doc/bugs/gpg_bundled_with_OSX_build_fails.mdwn
deleted file mode 100644
index 701e67cc5..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-What steps will reproduce the problem?
-
-run
-
-    /Applications/git-annex.app/Contents/MacOS/bin/gpg
-
-from the terminal
-
-What is the expected output? What do you see instead?
-
-I expect to see typical gpg output.  Instead, I see
-
-    dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib
-        Referenced from: /Applications/git-annex.app/Contents/MacOS/bin/gpg
-        Reason: Incompatible library version: gpg requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0
-    Trace/BPT trap: 5
-
-What version of git-annex are you using? On what operating system?
-
-git annex Version: 3.20121017 on Mac OS X 10.7.5
-
-[[!tag /design/assistant/OSX]]
-
-> Libraries are now handled better in the OSX app and this should be able
-> to happen anymore. [[done]] --[[Joey]] 
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_1_ec911f920db6c354ba998ffbb5886606._comment b/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_1_ec911f920db6c354ba998ffbb5886606._comment
deleted file mode 100644
index 574a25b5f..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_1_ec911f920db6c354ba998ffbb5886606._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.194"
- subject="comment 1"
- date="2012-11-01T02:36:07Z"
- content="""
-You need to use runshell to run the commands included in the OSX app. 
-
-(Also, using them outside of git-annex is not really something that is intended to be supported.)
-"""]]
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_2_bf2a3ab1bbe258bd501ec4b776882adf._comment b/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_2_bf2a3ab1bbe258bd501ec4b776882adf._comment
deleted file mode 100644
index 268a577ca..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_2_bf2a3ab1bbe258bd501ec4b776882adf._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/6xTna_B_h.ECb6_ftC2dYLytAEwrv36etg_054U-#4c1e7"
- nickname="Fake"
- subject="comment 2"
- date="2012-11-01T11:49:55Z"
- content="""
-Ok, thanks for the info.  I actually tried running this directly because I was getting the same error from inside of git-annex assistant.  When I add a remote server repository with encrypted rsync, I am able to add the server (\"Check this server\" works), but when I click on the \"Use an encrypted rsync repository on the server\" button, I get the following error:
-
-    Internal Server Error
-    
-    user error (gpg [\"--quiet\",\"--trust-model\",\"always\",\"--gen-random\",\"--armor\",\"1\",\"512\"] exited 5)
-"""]]
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_3_c0142427400323c00bd8294415ae32c5._comment b/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_3_c0142427400323c00bd8294415ae32c5._comment
deleted file mode 100644
index 163ce66c0..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_3_c0142427400323c00bd8294415ae32c5._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/6xTna_B_h.ECb6_ftC2dYLytAEwrv36etg_054U-#4c1e7"
- nickname="Fake"
- subject="comment 3"
- date="2012-11-01T11:52:30Z"
- content="""
-A little more info.  Here is the error from the console log when I try to add the remote server repository.
-
-    Dyld Error Message:
-      Library not loaded: /opt/local/lib/libncurses.5.dylib
-      Referenced from: /Applications/git-annex.app/Contents/MacOS/opt/local/lib/libreadline.6.2.dylib
-      Reason: no suitable image found.  Did find:
-    	/usr/lib/libncurses.5.dylib: mach-o, but wrong architecture
-    	/usr/lib/libncurses.5.dylib: mach-o, but wrong architecture
-"""]]
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_4_b56db4b5afc276f88a2b980e22fda8a0._comment b/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_4_b56db4b5afc276f88a2b980e22fda8a0._comment
deleted file mode 100644
index 64946b41a..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_4_b56db4b5afc276f88a2b980e22fda8a0._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.194"
- subject="comment 4"
- date="2012-11-01T13:40:39Z"
- content="""
-Ah ok, thanks for the info about this problem.
-
-Which URL did you download the app from? We have 2 builds.
-"""]]
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_5_a4eda81e5f927c463593bc48fbe84077._comment b/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_5_a4eda81e5f927c463593bc48fbe84077._comment
deleted file mode 100644
index d5a583020..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_5_a4eda81e5f927c463593bc48fbe84077._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/6xTna_B_h.ECb6_ftC2dYLytAEwrv36etg_054U-#4c1e7"
- nickname="Fake"
- subject="comment 5"
- date="2012-11-01T14:29:40Z"
- content="""
-This is the beta release (http://downloads.kitenet.net/git-annex/OSX/git-annex.dmg.bz2)  Right now the link to the daily build is broken.
-
-I found the link on this page: http://git-annex.branchable.com/install/OSX/
-
-Thanks!
-"""]]
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_6_2f0b9331d16a208883bac586258a7b50._comment b/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_6_2f0b9331d16a208883bac586258a7b50._comment
deleted file mode 100644
index abcfb6fb2..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_6_2f0b9331d16a208883bac586258a7b50._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.6.49"
- subject="comment 6"
- date="2012-11-26T23:53:01Z"
- content="""
-The OSX app has been updated for today's release, and includes a lot of missing libraries. Your testing of it would be appreciated.
-"""]]
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_7_c05c484a6134f93796cff08de0f63e80._comment b/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_7_c05c484a6134f93796cff08de0f63e80._comment
deleted file mode 100644
index 1e60e5d25..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_7_c05c484a6134f93796cff08de0f63e80._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlpOeCs7zZLR-PBGPxUgjWlg7bwAAzQZyk"
- nickname="Seth"
- subject="comment 7"
- date="2013-06-29T17:26:54Z"
- content="""
-I get this same internal server error when doing the encrypted rsync repo option:
-
-    user error (gpg [\"--quiet\",\"--trust-model\",\"always\",\"--gen-random\",\"--armor\",\"1\",\"512\"] exited 2)
-
-Currently using the file found here:
-
-http://downloads.kitenet.net/git-annex/OSX/current/10.7.5_Lion/
-
-Using MacOS 10.7.5 Lion
-"""]]
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_8_f2cb5467ebe80cf67e1155b771b73978._comment b/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_8_f2cb5467ebe80cf67e1155b771b73978._comment
deleted file mode 100644
index 5b2bf88b2..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_8_f2cb5467ebe80cf67e1155b771b73978._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 8"
- date="2013-06-30T18:02:03Z"
- content="""
-That's not the same error (2 != 5), and posting comments to long-closed bugs is never a good idea if your goal is to report a current bug in a way that will ensure it's noticed and that anyone remembers to follow up on it. You should file a new bug report, and include whatever actual error message is output *before* the message you pasted.
-"""]]
diff --git a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_9_27bbda7e31f55b29e1473555ee17e613._comment b/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_9_27bbda7e31f55b29e1473555ee17e613._comment
deleted file mode 100644
index cd2002411..000000000
--- a/doc/bugs/gpg_bundled_with_OSX_build_fails/comment_9_27bbda7e31f55b29e1473555ee17e613._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlpOeCs7zZLR-PBGPxUgjWlg7bwAAzQZyk"
- nickname="Seth"
- subject="comment 9"
- date="2013-06-30T19:38:07Z"
- content="""
-Just so you know, this post is what comes up on google when I search the error. 
-"""]]
diff --git a/doc/bugs/gpg_error_on_android.mdwn b/doc/bugs/gpg_error_on_android.mdwn
deleted file mode 100644
index 3e69f05f2..000000000
--- a/doc/bugs/gpg_error_on_android.mdwn
+++ /dev/null
@@ -1,39 +0,0 @@
-### Please describe the problem.
-
-Adding an existing cloud repo on box.com results in an gpg error:
-
-    user error (gpg ["--quiet","--trust-model","always","--batch","--passphrase-fd","86","--decrypt"] exited 2)
-
-### What steps will reproduce the problem?
-
-Enabling an existing cloud repository.
-
-### What version of git-annex are you using? On what operating system?
-
-Latest Android (4.20130516-g32 40006) on a rooted Samsung Galaxy Note (CyanogenMod 10.1)
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/debug.log
-
-(merging refs/synced/de8a8792-70de-48c3-a646-a168ce1d9d35/c25hdXRoQGphYmJlci5vcmc=/git-annex into git-annex...)
-(Recording state in git...)
-(gpg) gpg: can't open `/usr/local/share/gnupg/options.skel': No such file or directory
-gpg: DBG: locking for `/sdcard/git-annex.home/.gnupg/secring.gpg.lock' done via O_EXCL
-gpg: DBG: locking for `/sdcard/git-annex.home/.gnupg/pubring.gpg.lock' done via O_EXCL
-gpg: encrypted with unknown algorithm 3
-gpg: decryption failed: secret key not available
-(gpg) gpg: encrypted with unknown algorithm 3
-gpg: decryption failed: secret key not available
-(gpg) gpg: encrypted with unknown algorithm 3
-gpg: decryption failed: secret key not available
-(gpg) gpg: encrypted with unknown algorithm 3
-gpg: decryption failed: secret key not available
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; I have deployed the new gpg build for Android and the
-> nightly Android app build is now using it. --[[Joey]]
diff --git a/doc/bugs/gpg_error_on_android/comment_1_870583fd1b7a33b688b9a228077d1333._comment b/doc/bugs/gpg_error_on_android/comment_1_870583fd1b7a33b688b9a228077d1333._comment
deleted file mode 100644
index b15500454..000000000
--- a/doc/bugs/gpg_error_on_android/comment_1_870583fd1b7a33b688b9a228077d1333._comment
+++ /dev/null
@@ -1,629 +0,0 @@
-[[!comment format=mdwn
- username="carlo"
- ip="118.208.45.43"
- subject="comment 1"
- date="2013-07-06T03:29:10Z"
- content="""
-I see similar errors on my Samsung Galaxy S3, running Cyanogenmod 9. The phone is trying to sync with an encrypted rsync repository on my Linode. My laptop can sync with no problems.
-
-Here's a dump from daemon.log. Let me know if you need more details.
-
-    [2013-07-06 13:10:22 EST] main: starting assistant version 4.20130704-gaf18656
-    Already up-to-date.
-
-    (scanning...) [2013-07-06 13:10:23 EST] Watcher: Performing startup scan
-    Already up-to-date.
-    Already up-to-date.
-
-
-    (started...) (gpg) [2013-07-06 13:10:28 EST] XMPPSendPack: Syncing with nk 
-    [2013-07-06 13:10:28 EST] XMPPReceivePack: Syncing with nk 
-    [2013-07-06 13:10:29 EST] XMPPSendPack: Syncing with nk 
-
-    <snip>
-
-    GPGHMACSHA1--cfa7bdccfada399b50f086901621ba66a789a4df
-    Already up-to-date.
-    
-              0   0%    0.00kB/s    0:00:00  [2013-07-06 13:10:36 EST] Committer: Committing changes to git
-    [2013-07-06 13:10:36 EST] XMPPSendPack: Syncing with nk 
-    
-        262,144   0%  203.34kB/s    0:06:43  Already up-to-date.
-    
-        655,360   0%  211.99kB/s    0:06:25  [2013-07-06 13:10:38 EST] XMPPSendPack: Syncing with nk 
-    [2013-07-06 13:10:39 EST] XMPPSendPack: Syncing with nk 
-    
-      1,638,400   1%  395.65kB/s    0:03:23  
-      2,424,832   2%  464.04kB/s    0:02:52  
-      2,981,888   3%  546.05kB/s    0:02:25  
-      3,538,944   4%  682.17kB/s    0:01:55  
-      4,096,000   4%  581.68kB/s    0:02:14  
-      4,653,056   5%  529.05kB/s    0:02:26  
-      5,210,112   6%  525.60kB/s    0:02:26  
-      5,767,168   7%  526.24kB/s    0:02:25  
-      6,324,224   7%  526.75kB/s    0:02:24  
-      6,881,280   8%  529.83kB/s    0:02:22  
-      7,438,336   9%  532.94kB/s    0:02:20  (gpg) 
-      7,798,784   9%  486.16kB/s    0:02:33  
-      8,519,680  10%  525.75kB/s    0:02:20  
-      9,076,736  11%  526.01kB/s    0:02:19  
-      9,502,720  11%  459.23kB/s    0:02:38  
-     10,354,688  12%  556.40kB/s    0:02:09  
-     10,911,744  13%  514.20kB/s    0:02:18  (gpg) 
-     11,501,568  13%  508.81kB/s    0:02:19  (gpg) 
-     12,091,392  14%  585.73kB/s    0:01:59  
-    GPGHMACSHA1--15b3dbca166df23b9b14e88bcfb08dceeeeaade9
-    
-              0   0%    0.00kB/s    0:00:00  
-     12,615,680  15%  521.25kB/s    0:02:13  
-        294,912  26%  266.17kB/s    0:00:03  
-     12,910,592  15%  459.84kB/s    0:02:30  
-        589,824  52%  266.67kB/s    0:00:01  
-     13,205,504  16%  396.57kB/s    0:02:54  
-        884,736  79%  266.42kB/s    0:00:00  
-     13,500,416  16%  321.72kB/s    0:03:33  
-      1,116,373 100%  275.58kB/s    0:00:03 (xfr#1, to-chk=0/1)
-    
-     13,860,864  16%  285.92kB/s    0:03:59  
-     14,221,312  17%  304.91kB/s    0:03:43  
-     14,909,440  18%  403.88kB/s    0:02:46  
-    GPGHMACSHA1--ec1cbd34a82fe0997354669b2c7b38419f73d07e
-    
-              0   0%    0.00kB/s    0:00:00  
-     15,400,960  18%  450.59kB/s    0:02:28  gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-    
-        294,912  26%  266.42kB/s    0:00:03  
-    GPGHMACSHA1--b979ec76f3b12b63db8ee540fc9a018cffb82aa8
-    
-     15,663,104  19%  426.46kB/s    0:02:36  
-              0   0%    0.00kB/s    0:00:00  
-        393,216  35%  178.19kB/s    0:00:03  
-     15,761,408  19%  364.08kB/s    0:03:02  
-        131,072  11%  115.21kB/s    0:00:08  
-        688,128  62%  206.52kB/s    0:00:01  
-     16,056,320  19%  262.23kB/s    0:04:12  
-        393,216  34%  176.71kB/s    0:00:04  
-        884,736  80%  199.40kB/s    0:00:01  
-     16,252,928  19%  194.67kB/s    0:05:39  
-        589,824  51%  177.01kB/s    0:00:03  
-      1,095,420 100%  205.52kB/s    0:00:05 (xfr#1, to-chk=0/1)
-    
-     16,482,304  20%  183.44kB/s    0:05:58  
-        819,200  70%  185.96kB/s    0:00:01  
-     16,777,216  20%  224.84kB/s    0:04:51  
-      1,114,112  96%  227.27kB/s    0:00:00  
-      1,154,143 100%  211.07kB/s    0:00:05 (xfr#1, to-chk=0/1)
-    
-     17,334,272  21%  289.96kB/s    0:03:44  
-     17,891,328  21%  376.91kB/s    0:02:50  gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-    send: resource vanisheds e(nBdr:o kreens opuirpcee) 
-    vanished (Broken pipe)
-    
-     18,448,384  22%  461.76kB/s    0:02:18  gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-    se
-     19,005,440  23%  531.25kB/s    0:01:59  nd: resource vanished (Broken pipe)
-    
-     19,562,496  23%  532.81kB/s    0:01:57  
-     19,922,944  24%  484.14kB/s    0:02:08  
-     20,643,840  25%  525.36kB/s    0:01:57  
-     21,200,896  25%  525.62kB/s    0:01:56  
-     21,757,952  26%  526.13kB/s    0:01:55  
-     22,085,632  26%  518.16kB/s    0:01:56  
-     22,872,064  27%  529.05kB/s    0:01:52  
-     23,429,120  28%  528.80kB/s    0:01:51  
-     23,953,408  29%  516.75kB/s    0:01:52  
-     24,543,232  29%  583.66kB/s    0:01:38  
-     25,034,752  30%  516.51kB/s    0:01:50  
-     25,460,736  30%  466.71kB/s    0:02:01  
-     26,050,560  31%  481.20kB/s    0:01:56  
-     26,607,616  32%  471.25kB/s    0:01:58  
-     27,164,672  33%  486.21kB/s    0:01:53  
-     27,721,728  33%  536.44kB/s    0:01:41  
-     28,278,784  34%  533.33kB/s    0:01:41  
-     28,835,840  35%  533.59kB/s    0:01:40  
-     29,392,896  35%  529.44kB/s    0:01:39  
-     29,982,720  36%  532.95kB/s    0:01:38  
-     30,539,776  37%  533.46kB/s    0:01:37  
-     31,096,832  37%  533.46kB/s    0:01:35  
-     31,653,888  38%  537.23kB/s    0:01:34  
-     31,752,192  38%  409.87kB/s    0:02:03  
-     32,800,768  39%  524.96kB/s    0:01:34  
-     33,357,824  40%  524.84kB/s    0:01:33  
-     33,914,880  41%  524.96kB/s    0:01:32  
-     34,471,936  41%  652.74kB/s    0:01:13  
-     35,028,992  42%  533.33kB/s    0:01:28  
-     35,586,048  43%  533.46kB/s    0:01:27  
-     36,143,104  43%  533.07kB/s    0:01:26  
-     36,700,160  44%  533.33kB/s    0:01:25  
-     37,257,216  45%  533.33kB/s    0:01:24  
-     37,814,272  45%  533.20kB/s    0:01:23  
-     38,240,256  46%  467.37kB/s    0:01:34  
-     39,059,456  47%  525.19kB/s    0:01:22  
-     39,616,512  48%  525.31kB/s    0:01:21  
-     40,173,568  48%  525.43kB/s    0:01:20  
-     40,632,320  49%  574.52kB/s    0:01:12  
-     41,254,912  50%  527.82kB/s    0:01:17  
-     41,811,968  50%  528.08kB/s    0:01:16  
-     42,369,024  51%  527.82kB/s    0:01:15  
-     42,926,080  52%  549.15kB/s    0:01:11  
-     43,483,136  52%  533.59kB/s    0:01:12  
-     44,040,192  53%  533.20kB/s    0:01:11  
-     44,597,248  54%  533.20kB/s    0:01:10  
-     45,121,536  54%  525.49kB/s    0:01:10  
-     45,678,592  55%  525.49kB/s    0:01:09  
-     46,039,040  55%  476.68kB/s    0:01:16  
-     46,792,704  56%  520.89kB/s    0:01:08  
-     47,349,760  57%  528.41kB/s    0:01:06  
-     47,906,816  58%  520.20kB/s    0:01:06  
-     48,431,104  58%  500.32kB/s    0:01:07  
-     49,020,928  59%  406.05kB/s    0:01:21  
-     49,807,360  60%  446.10kB/s    0:01:12  
-     50,364,416  61%  451.55kB/s    0:01:10  
-     50,921,472  61%  504.88kB/s    0:01:02  
-     51,412,992  62%  569.76kB/s    0:00:54  
-     51,970,048  63%  515.00kB/s    0:00:58  
-     52,527,104  63%  514.87kB/s    0:00:57  
-     53,084,160  64%  515.25kB/s    0:00:56  
-     53,641,216  65%  530.47kB/s    0:00:54  
-     54,198,272  65%  532.94kB/s    0:00:52  
-     54,755,328  66%  533.46kB/s    0:00:51  
-     55,312,384  67%  533.20kB/s    0:00:50  
-     55,869,440  67%  533.33kB/s    0:00:49  
-     56,426,496  68%  533.46kB/s    0:00:48  
-     56,983,552  69%  533.20kB/s    0:00:47  
-     57,409,536  69%  466.09kB/s    0:00:53  
-     58,228,736  70%  525.79kB/s    0:00:45  
-     58,785,792  71%  525.67kB/s    0:00:44  
-     59,342,848  72%  520.68kB/s    0:00:44  
-     59,736,064  72%  547.60kB/s    0:00:41  
-     60,489,728  73%  528.10kB/s    0:00:41  
-     61,046,784  74%  528.48kB/s    0:00:40  
-     61,603,840  74%  533.72kB/s    0:00:38  
-     62,128,128  75%  567.40kB/s    0:00:35  
-     62,226,432  75%  399.53kB/s    0:00:50  
-     62,652,416  76%  369.81kB/s    0:00:53  
-     62,947,328  76%  300.78kB/s    0:01:04  
-     63,438,848  77%  292.97kB/s    0:01:04  
-     63,963,136  77%  400.66kB/s    0:00:45  
-     64,520,192  78%  426.27kB/s    0:00:41  
-     65,110,016  79%  495.54kB/s    0:00:34  
-     65,601,536  79%  497.76kB/s    0:00:33  
-     66,158,592  80%  506.62kB/s    0:00:31  
-     66,715,648  81%  511.33kB/s    0:00:30  
-     67,207,168  81%  452.20kB/s    0:00:33  
-     68,059,136  82%  527.01kB/s    0:00:27  
-     68,616,192  83%  526.55kB/s    0:00:26  
-     69,173,248  84%  527.24kB/s    0:00:24  
-     69,500,928  84%  529.30kB/s    0:00:24  
-     70,320,128  85%  527.98kB/s    0:00:22  
-     70,877,184  86%  527.60kB/s    0:00:21  
-     71,434,240  86%  526.84kB/s    0:00:20  
-     71,991,296  87%  595.93kB/s    0:00:17  
-     72,548,352  88%  529.70kB/s    0:00:18  
-     73,105,408  88%  528.16kB/s    0:00:17  [2013-07-06 13:13:01 EST] XMPPSendPack: Syncing with ch 
-    
-     73,662,464  89%  527.39kB/s    0:00:16  [2013-07-06 13:13:02 EST] XMPPSendPack: Syncing with ch 
-    
-     74,219,520  90%  524.08kB/s    0:00:15  
-     74,743,808  90%  511.21kB/s    0:00:14  
-     75,104,256  91%  410.00kB/s    0:00:17  
-     75,497,472  91%  377.34kB/s    0:00:18  
-     76,152,832  92%  402.22kB/s    0:00:15  
-     76,709,888  93%  413.44kB/s    0:00:13  
-     77,201,408  93%  458.58kB/s    0:00:11  
-     78,020,608  94%  552.96kB/s    0:00:07  
-     78,577,664  95%  528.45kB/s    0:00:07  
-     79,134,720  96%  528.34kB/s    0:00:06  
-     79,691,776  96%  597.25kB/s    0:00:04  
-     80,248,832  97%  532.42kB/s    0:00:03  
-     80,805,888  98%  533.33kB/s    0:00:02  
-     81,362,944  98%  533.07kB/s    0:00:01  
-     81,920,000  99%  533.07kB/s    0:00:00  
-     82,307,694 100%  491.43kB/s    0:02:43 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-    send: resource vanished (Broken pipe)
-
-    GPGHMACSHA1--836e8cdf7c23d119e08f9d9cb3377abb438f2312
-    
-              0   0%    0.00kB/s    0:00:00  
-        131,072  11%  115.84kB/s    0:00:08  
-        229,376  19%  106.41kB/s    0:00:08  
-        393,216  34%  118.08kB/s    0:00:06  
-        655,360  56%  149.46kB/s    0:00:03  
-        917,504  79%  180.24kB/s    0:00:01  
-      1,154,559 100%  184.38kB/s    0:00:06 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--c34a27463185c59e8cb7df7f647333072e18ddb9
-    
-              0   0%    0.00kB/s    0:00:00  
-        294,912  16%  272.73kB/s    0:00:05  
-        655,360  36%  304.18kB/s    0:00:03  
-      1,114,112  62%  343.54kB/s    0:00:01  
-      1,441,792  81%  335.32kB/s    0:00:00  
-      1,772,175 100%  351.61kB/s    0:00:04 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--7bc715e8c49feb30ba974b246ad8b69bcef8f407
-    
-              0   0%    0.00kB/s    0:00:00  
-        393,216  31%  373.18kB/s    0:00:02  
-        819,200  66%  340.43kB/s    0:00:01  
-      1,234,572 100%  411.48kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--dbc6af27d9b732f3ea7b29f7316cf67986db8ff0
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  60%  532.81kB/s    0:00:00  
-        913,536 100%  540.03kB/s    0:00:01 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--84ce3dc5fe676eb10cfe595564482d48daceeb33
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  44%  532.29kB/s    0:00:01  
-      1,114,112  88%  532.29kB/s    0:00:00  
-      1,256,801 100%  548.90kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--9d042d017e8efc60f82ee3789edbbd8422ddbf1c
-    
-              0   0%    0.00kB/s    0:00:00  
-        491,520  42%  469.67kB/s    0:00:01  
-        950,272  81%  458.50kB/s    0:00:00  
-      1,165,242 100%  483.81kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--951b2f84c011debef9e6dc213d859cc6366f8e01
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  44%  535.96kB/s    0:00:01  
-        983,040  78%  460.21kB/s    0:00:00  
-      1,257,173 100%  468.23kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--88b8021104955c3ff14da53cdf5c8dd445719bfa
-    
-              0   0%    0.00kB/s    0:00:00  
-        589,824  38%  544.94kB/s    0:00:01  
-      1,146,880  75%  536.66kB/s    0:00:00  
-      1,518,637 100%  493.03kB/s    0:00:03 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--89a254b76c1dd92c3bcf6c2db0745287ca306ae6
-    
-              0   0%    0.00kB/s    0:00:00  
-        393,216  29%  367.11kB/s    0:00:02  
-        819,200  61%  391.01kB/s    0:00:01  
-      1,277,952  96%  404.01kB/s    0:00:00  
-      1,326,036 100%  417.32kB/s    0:00:03 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--b975ff334766d744ce6827be273ad7f46dddcdeb
-    
-              0   0%    0.00kB/s    0:00:00  
-        524,288  52%  496.61kB/s    0:00:00  
-        996,592 100%  480.85kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--e828d8bbe5d34598fef577170a9fa9187d09e312
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  35%  529.18kB/s    0:00:01  
-      1,114,112  70%  529.96kB/s    0:00:00  
-      1,581,185 100%  542.18kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--f6b7fc900cd45830afe01711e369d17453a997dd
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  35%  538.61kB/s    0:00:01  
-      1,114,112  70%  535.17kB/s    0:00:00  
-      1,573,373 100%  547.97kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--d7a0413362aff13ce23c76d05d684df1fa884635
-    
-              0   0%    0.00kB/s    0:00:00  
-        524,288  30%  504.93kB/s    0:00:02  
-        950,272  55%  397.94kB/s    0:00:01  
-      1,699,965 100%  524.36kB/s    0:00:03 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--f98f1613a3b8f160ea4029eb9fa3c45f9a2a1bc6
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  37%  532.81kB/s    0:00:01  
-      1,114,112  75%  525.10kB/s    0:00:00  
-      1,478,031 100%  548.19kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--1d35cc37e4a83908a29c0651448a96269458218d
-    
-              0   0%    0.00kB/s    0:00:00  
-        589,824  39%  558.14kB/s    0:00:01  
-      1,146,880  77%  544.75kB/s    0:00:00  
-      1,475,738 100%  556.00kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--41779d89d985def50ee52dbb1abaf41cfb248f02
-    
-              0   0%    0.00kB/s    0:00:00  
-        524,288  77%  509.45kB/s    0:00:00  
-        680,795 100%  500.25kB/s    0:00:01 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--0ac2341072949bd0d26df145e3cef8d39ba177ad
-    
-              0   0%    0.00kB/s    0:00:00  
-        851,968  78%  794.65kB/s    0:00:00  
-      1,085,714 100%  758.96kB/s    0:00:01 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--96239a54b31856d30e50eedb2a3352ec87fd6d1e
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  47%  528.16kB/s    0:00:01  
-      1,114,112  95%  529.96kB/s    0:00:00  
-      1,166,134 100%  549.88kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--e40a7caa66fa1656428cbec103645089579065f8
-    
-              0   0%    0.00kB/s    0:00:00  
-         98,304   7%   95.05kB/s    0:00:13  
-        622,592  45%  297.02kB/s    0:00:02  
-        753,664  55%  232.91kB/s    0:00:02  
-        884,736  64%  204.74kB/s    0:00:02  
-      1,310,720  95%  280.97kB/s    0:00:00  
-      1,369,673 100%  251.94kB/s    0:00:05 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--4907edd5704e1a3540e946cfc80b29226599e466
-    
-              0   0%    0.00kB/s    0:00:00  
-        327,680  25%  310.98kB/s    0:00:03  
-        688,128  52%  328.77kB/s    0:00:01  
-      1,114,112  85%  350.74kB/s    0:00:00  
-      1,303,313 100%  369.78kB/s    0:00:03 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--2a0a0f546f08334d8cd90f2930057837dcf5ba09
-    
-              0   0%    0.00kB/s    0:00:00  
-        491,520  39%  475.25kB/s    0:00:01  
-        917,504  73%  438.57kB/s    0:00:00  
-      1,146,880  92%  359.67kB/s    0:00:00  
-      1,246,084 100%  344.82kB/s    0:00:03 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--9eb761916db3868a5ffe7b310ae5ac3cc7046ae5
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  44%  517.60kB/s    0:00:01  
-        786,432  62%  329.05kB/s    0:00:01  
-      1,254,828 100%  515.31kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--e644608fd731b8eaf6d5d04e78e165300eb25f98
-    
-              0   0%    0.00kB/s    0:00:00  
-        589,824  52%  561.40kB/s    0:00:00  
-      1,048,576  93%  503.19kB/s    0:00:00  
-      1,116,566 100%  522.47kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--58e2af2853f65840a6e16eb7c03d005ed2e79c40
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  42%  530.21kB/s    0:00:01  
-      1,114,112  85%  531.25kB/s    0:00:00  
-      1,300,115 100%  546.79kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--c5c714419a2d7c0f4699f31862e7011a15014482
-    
-              0   0%    0.00kB/s    0:00:00  
-        589,824  38%  547.53kB/s    0:00:01  
-      1,146,880  75%  538.46kB/s    0:00:00  
-      1,521,103 100%  550.17kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--15df191feeb70009d1babbf45edfd895c7ed16fe
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  43%  541.29kB/s    0:00:01  
-      1,114,112  87%  536.22kB/s    0:00:00  
-      1,277,262 100%  550.70kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--da82fe427bcc275851fcff2406702bdf711a0d05
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  39%  539.68kB/s    0:00:01  
-      1,114,112  79%  535.43kB/s    0:00:00  
-      1,394,802 100%  546.16kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--d4a3cd0a0cdfb63e0c822c2971bec47351f0d691
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  43%  542.37kB/s    0:00:01  
-      1,114,112  86%  535.17kB/s    0:00:00  
-      1,284,784 100%  550.05kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--b97860268c7d4811de5d0529fcb6964e72404e77
-    
-              0   0%    0.00kB/s    0:00:00  
-         40,966 100%   13.02MB/s    0:00:00 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--a8b3e383f310580bb6c1035144763ec7db044f78
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  75%  538.08kB/s    0:00:00  
-        733,303 100%  564.76kB/s    0:00:01 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--29011935e74ac079fcb329a43739baeaa17d098c
-    
-              0   0%    0.00kB/s    0:00:00  
-         89,335 100%    1.11MB/s    0:00:00 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--fd6e992885ee3c8305d01166eecf3c464627c4f7
-    
-              0   0%    0.00kB/s    0:00:00  
-         41,462 100%   13.18MB/s    0:00:00 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--a2069f368ff8402a2cb1418bd4b9732af7c4d4a9
-    
-              0   0%    0.00kB/s    0:00:00  
-        170,729 100%  706.47kB/s    0:00:00 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--6792222db461942b05679e53db4e54fa789ca01f
-    
-              0   0%    0.00kB/s    0:00:00  
-            592 100%  578.13kB/s    0:00:00 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--d18187ee562acebfc027ae87ca256ee76291ebc9
-    
-              0   0%    0.00kB/s    0:00:00  
-         92,078 100%    1.16MB/s    0:00:00 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--099750d6c62696356befb2d9f0c6eced87d44982
-    
-              0   0%    0.00kB/s    0:00:00  
-         17,889 100%   17.06MB/s    0:00:00 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--5bfba3f4483f32f614082626cb19c9a80dcef47f
-    
-              0   0%    0.00kB/s    0:00:00  
-        557,056  34%  542.37kB/s    0:00:01  
-      1,114,112  68%  529.44kB/s    0:00:00  
-      1,572,864  96%  493.89kB/s    0:00:00  
-      1,636,134 100%  511.29kB/s    0:00:03 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--c63f95ff9e5e7162324f198763d82135a782a672
-    
-              0   0%    0.00kB/s    0:00:00  
-         11,074 100%   10.56MB/s    0:00:00 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--d5355ccf4f2f48a8adf698d00416569996408c99
-    
-              0   0%    0.00kB/s    0:00:00  
-         17,389 100%   16.58MB/s    0:00:00 (xfr#1, to-chk=0/1)
-    gpg: encrypted with unknown algorithm 3
-    gpg: decryption failed: secret key not available
-
-    GPGHMACSHA1--cd50fc92525ee650189b89373a4791be4c7ffa24
-    
-              0   0%    0.00kB/s    0:00:00  
-        131,072   0%   91.30kB/s    0:06:06  
-        294,912   0%  110.85kB/s    0:05:00  
-        491,520   1%  133.37kB/s    0:04:08  
-        819,200   2%  173.24kB/s    0:03:09  
-      1,343,488   3%  277.48kB/s    0:01:56  
-      1,900,544   5%  383.00kB/s    0:01:22  
-      2,359,296   7%  438.88kB/s    0:01:11  
-      2,785,280   8%  456.82kB/s    0:01:07  
-      3,244,032   9%  390.90kB/s    0:01:17  
-      3,637,248  10%  356.83kB/s    0:01:24  
-      4,259,840  12%  388.28kB/s    0:01:15  
-      4,718,592  14%  395.97kB/s    0:01:13  
-      5,046,272  15%  385.54kB/s    0:01:14  
-      5,210,112  15%  326.18kB/s    0:01:27  
-      6,094,848  18%  385.21kB/s    0:01:11  
-      6,488,064  19%  372.65kB/s    0:01:12  [2013-07-06 13:16:29 EST] XMPPReceivePack: Syncing with ch 
-    
-      6,914,048  20%  403.45kB/s    0:01:06  
-      7,143,424  21%  409.28kB/s    0:01:04  
-      7,667,712  22%  334.06kB/s    0:01:17  
-      8,126,464  24%  347.75kB/s    0:01:13  
-      8,683,520  25%  398.80kB/s    0:01:02  
-      9,240,576  27%  500.86kB/s    0:00:48  
-      9,797,632  29%  507.32kB/s    0:00:46  
-     10,256,384  30%  511.31kB/s    0:00:45  
-     10,682,368  31%  479.25kB/s    0:00:47  
-     11,206,656  33%  471.63kB/s    0:00:47  
-     11,763,712  34%  471.86kB/s    0:00:46  
-     12,320,768  36%  494.24kB/s    0:00:43  
-     12,615,680  37%  460.15kB/s    0:00:45  
-     13,434,880  39%  526.37kB/s    0:00:38  
-     13,991,936  41%  527.39kB/s    0:00:37  
-     14,548,992  43%  527.77kB/s    0:00:36  
-     14,843,904  44%  528.54kB/s    0:00:35  
-     15,663,104  46%  528.54kB/s    0:00:33  
-     16,220,160  48%  528.54kB/s    0:00:32  
-     16,777,216  49%  527.90kB/s    0:00:31  
-     17,334,272  51%  592.02kB/s    0:00:27  
-     17,891,328  53%  533.33kB/s    0:00:29  
-     18,448,384  54%  533.20kB/s    0:00:28  
-     19,005,440  56%  533.73kB/s    0:00:27  
-     19,562,496  58%  533.46kB/s    0:00:26  
-     20,119,552  59%  533.20kB/s    0:00:25  
-     20,414,464  60%  467.95kB/s    0:00:28  
-     21,233,664  63%  528.28kB/s    0:00:23  
-     21,790,720  64%  528.67kB/s    0:00:22  
-     22,347,776  66%  528.67kB/s    0:00:21  
-     22,740,992  67%  492.20kB/s    0:00:22  
-     23,494,656  69%  477.61kB/s    0:00:21  
-     24,051,712  71%  477.41kB/s    0:00:20  
-     24,608,768  73%  477.30kB/s    0:00:18  
-     25,165,824  74%  577.28kB/s    0:00:14  
-     25,722,880  76%  532.81kB/s    0:00:14  
-     26,279,936  78%  533.20kB/s    0:00:13  
-     26,804,224  79%  522.80kB/s    0:00:13  
-
-"""]]
diff --git a/doc/bugs/gpg_error_on_android/comment_2_9ce5511a109bde50d8cf87bad0268b4a._comment b/doc/bugs/gpg_error_on_android/comment_2_9ce5511a109bde50d8cf87bad0268b4a._comment
deleted file mode 100644
index f1cd47296..000000000
--- a/doc/bugs/gpg_error_on_android/comment_2_9ce5511a109bde50d8cf87bad0268b4a._comment
+++ /dev/null
@@ -1,26 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.235"
- subject="comment 2"
- date="2013-07-08T19:57:10Z"
- content="""
-Based on <http://pthree.org/2009/06/08/gnupg-up-and-close/> and <http://www.faqs.org/rfcs/rfc4880.html>, symmetric encryption algorithm 3 is CAST5.
-
-When I run `gpg -v --version` on Android, I get a very short list of Cipher algorithms, just \"3DES (S2)\".
-
-Compare with on Linux, where it supports:
-
-<pre>
-Cipher: 3DES (S2), CAST5 (S3), BLOWFISH (S4), AES (S7), AES192 (S8), 
-        AES256 (S9), TWOFISH (S10), CAMELLIA128 (S11), CAMELLIA192 (S12), 
-        CAMELLIA256 (S13)
-</pre>
-
-I suspect that you guys have a gpg on your non-android side that either defaults to CAST5, or has been configured, via the default-preference-list setting in gpg.conf, to use it. It should be possible to adjust your gpg.conf to use 3DES by default, and then things will interoperate (anything already encrypted by git-annex still won't be visible on Android of course).
-
-The gpg shipped with git-annex on Android could be rebuilt to include these. However, it would probably need porting of more libraries to Android. I stopped once I got gpg to compile at all, and had to pass several configure flags to disable features, 
-
-This is something that anyone interested could work on.  (Ie, no Haskell!) See `standalone/android/Makefile` in the git-annex source tree, which uses the Android SDK and NDK to cross-compile gnupg for Android. 
-
-I think that getting it to build without `--enable-minimal` would probably get most of the way there.  Aha.. I just tried this, and the new binary seems to support nearly everything the linux one does, no extra libraries needed!
-"""]]
diff --git a/doc/bugs/gpg_error_on_android/comment_3_b345e80f38d38f82cfcfce3102138fb8._comment b/doc/bugs/gpg_error_on_android/comment_3_b345e80f38d38f82cfcfce3102138fb8._comment
deleted file mode 100644
index 14cd6070c..000000000
--- a/doc/bugs/gpg_error_on_android/comment_3_b345e80f38d38f82cfcfce3102138fb8._comment
+++ /dev/null
@@ -1,46 +0,0 @@
-[[!comment format=mdwn
- username="carlo"
- ip="118.208.1.126"
- subject="comment 3"
- date="2013-07-09T00:34:45Z"
- content="""
-I downloaded the daily build and the errors \"gpg: encrypted with
-unknown algorithm 3\" and \"gpg: decryption failed: secret key not
-available\" have gone, but now there is the problem \"gpg: decryption
-failed: bad key\". Logs are below.
-
-I'm in the process of setting up an Android build environment so I
-can debug this in more detail (I haven't done any Android development
-before but I do have Haskell experience).
-
-    [2013-07-09 10:21:22 EST] main: starting assistant version 4.20130708-g207c9f3
-    Already up-to-date.
-
-    (scanning...) [2013-07-09 10:21:23 EST] Watcher: Performing startup scan
-    Already up-to-date.
-    Already up-to-date.
-    (gpg) 
-
-    (started...) [2013-07-09 10:21:28 EST] XMPPSendPack: Syncing with carlo.hamalainen 
-
-    GPGHMACSHA1--15b3dbca166df23b9b14e88bcfb08dceeeeaade9
-          1,116,373 100%  421.09kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: decryption failed: bad key
-
-    GPGHMACSHA1--ec1cbd34a82fe0997354669b2c7b38419f73d07e
-          1,095,420 100%  236.15kB/s    0:00:04 (xfr#1, to-chk=0/1)
-    gpg: decryption failed: bad key
-
-    GPGHMACSHA1--b979ec76f3b12b63db8ee540fc9a018cffb82aa8
-          1,154,143 100%  412.85kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: decryption failed: bad key
-
-    GPGHMACSHA1--836e8cdf7c23d119e08f9d9cb3377abb438f2312
-          1,154,559 100%  411.95kB/s    0:00:02 (xfr#1, to-chk=0/1)
-    gpg: decryption failed: bad key
-
-    GPGHMACSHA1--c34a27463185c59e8cb7df7f647333072e18ddb9
-          1,772,175 100%  401.63kB/s    0:00:04 (xfr#1, to-chk=0/1)
-    gpg: decryption failed: bad key
-
-"""]]
diff --git a/doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment b/doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment
deleted file mode 100644
index 5fdfa8211..000000000
--- a/doc/bugs/gpg_error_on_android/comment_4_032f42235b7f26854e725041ca33384b._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.235"
- subject="comment 4"
- date="2013-07-09T18:03:12Z"
- content="""
-So, I am able to get the \"bad\" key message out of gpg if I encrypt with --symmetric with a passphrase and then enter the wrong passphrase when decrypting.
-
-Perhaps git-annex is sending gpg the wrong encryption key, or perhaps the git repo it's operating in has an old version of the key for this remote somehow?
-"""]]
diff --git a/doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant.mdwn b/doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant.mdwn
deleted file mode 100644
index 1a0680c79..000000000
--- a/doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant.mdwn
+++ /dev/null
@@ -1,55 +0,0 @@
-### Please describe the problem.
-
-When I use the web app and try to create a remote on a remote server (via ssh connection) the assistant shows a gpg error.
-
-### What steps will reproduce the problem?
-
-1. Start the the web app using git-annex web app
-2. create a local repository
-3. create a new repository on a Remote server (Set up a repository on a remote server using ssh).
-4. provide correct server address, user, port, etc.
-
-Then gpg fails. 
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20131106
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-local repository version: unknown
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-
-On Mac OS X 10.9 Mavericks, build 13A603.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[2013-11-14 21:03:47 CET] main: starting assistant version 4.20131106
-[2013-11-14 21:03:47 CET] Cronner: You should enable consistency checking to protect your data. 
-(Recording state in git...)
-(scanning...) [2013-11-14 21:03:47 CET] Watcher: Performing startup scan
-(started...) [2013-11-14 21:04:47 CET] Cronner: Consistency check in progress
-[2013-11-14 21:05:21 CET] Committer: Adding sunflower.html test.html cindy.css d3.js d3.min.js Accessors.js Essentials.js List.js Namespace.js and 6 other files
-
-(Recording state in git...)
-
-add /Users/ulli/Documents/annex/test.html (checksum...) ok
-### several similar adds removed for privacy reasons.
- 
-[2013-11-14 21:05:22 CET] Committer: Committing changes to git
-ok
-(Recording state in git...)
-(Recording state in git...)
-14/Nov/2013:21:21:05 +0100 [Error#yesod-core] user error (gpg ["--quiet","--trust-model","always","--with-colons","--list-secret-keys","--fixed-list-mode"] exited 127) @(yesod-core-1.2.5:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-
-# End of transcript or log.
-"""]]
-
-> I've had reports from others that gpg works when installing from the
-> bundle. [[done]] --[[Joey]] 
diff --git a/doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant/comment_1_7b409701c650b55b3472accd70555f16._comment b/doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant/comment_1_7b409701c650b55b3472accd70555f16._comment
deleted file mode 100644
index 7b1ed7420..000000000
--- a/doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant/comment_1_7b409701c650b55b3472accd70555f16._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmkXtBdMgE1d9nCz2iBc4f85xh4izZ_auU"
- nickname="Ulrich"
- subject="Easy to fix."
- date="2013-11-14T20:36:17Z"
- content="""
-Well, this only happens when gpg is not available. Everything works fine after a quick \"brew install gpg\".
-"""]]
diff --git a/doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant/comment_2_40b00f7258512677516ec5036b89090f._comment b/doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant/comment_2_40b00f7258512677516ec5036b89090f._comment
deleted file mode 100644
index ecc9717d2..000000000
--- a/doc/bugs/gpg_fails_on_Mac_OS_10.9_when_creating_a_new_remote_repository_via_assistant/comment_2_40b00f7258512677516ec5036b89090f._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.246"
- subject="comment 2"
- date="2013-11-14T22:10:32Z"
- content="""
-gpg is included in the bundle though:
-
-<pre>
-oberon:tmp joeyh$ /Volumes/git-annex/git-annex.app/Contents/MacOS/runshell
-bash-3.2$ which gpg
-/Volumes/git-annex/git-annex.app/Contents/MacOS/bundle/gpg
-</pre>
-"""]]
diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation.mdwn b/doc/bugs/gpg_hangs_on_glacier_remote_creation.mdwn
deleted file mode 100644
index b4aaa57ea..000000000
--- a/doc/bugs/gpg_hangs_on_glacier_remote_creation.mdwn
+++ /dev/null
@@ -1,78 +0,0 @@
-### Please describe the problem.
-when attempting to create a glacier special remote one of the gpg sub-commands hangs without returning.
-
-### What steps will reproduce the problem?
-I'm not sure what will reproduce this issue. I recently upgraded from the apt-get version of git-annex (version 3) to the cabal version (version 4 shown below), but I'm not sure if that is relevant at all).
-
-### What version of git-annex are you using? On what operating system?
-
-git version: 1.7.9.5
-
-(git annex was installed using cabal)
-[[!format sh """
-$> git-annex version
-git-annex version: 4.20130709
-build flags: Testsuite S3 Inotify DBus
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-"""]]
-
-OS version:
-
-12.04.2 LTS, Precise Pangolin
-
-GPG version:
-
-[[!format sh """
-$> gpg --version
-gpg (GnuPG) 1.4.11
-Copyright (C) 2010 Free Software Foundation, Inc.
-License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
-This is free software: you are free to change and redistribute it.
-There is NO WARRANTY, to the extent permitted by law.
-
-Home: ~/.gnupg
-Supported algorithms:
-Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
-Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128,
-        CAMELLIA192, CAMELLIA256
-Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
-Compression: Uncompressed, ZIP, ZLIB, BZIP2
-"""]]
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-$> git annex initremote glacier type=glacier encryption=annex-l1@ggg.local embedcreds=yes vault=some-vault-name --verbose --debug
-[2013-07-20 22:45:13 MDT] read: git ["--git-dir=/home/cantora/annex-l1/.git","--work-tree=/home/cantora/annex-l1","show-ref","git-annex"]
-[2013-07-20 22:45:13 MDT] read: git ["--git-dir=/home/cantora/annex-l1/.git","--work-tree=/home/cantora/annex-l1","show-ref","--hash","refs/heads/git-annex"]
-[2013-07-20 22:45:13 MDT] read: git ["--git-dir=/home/cantora/annex-l1/.git","--work-tree=/home/cantora/annex-l1","log","refs/heads/git-annex..181aa86dfd264557ab73285220d70c67f868b349","--oneline","-n1"]
-[2013-07-20 22:45:13 MDT] read: git ["--git-dir=/home/cantora/annex-l1/.git","--work-tree=/home/cantora/annex-l1","log","refs/heads/git-annex..1dc6e1c4bca2102fc25e86491ab89338750ee1f6","--oneline","-n1"]
-[2013-07-20 22:45:13 MDT] read: git ["--git-dir=/home/cantora/annex-l1/.git","--work-tree=/home/cantora/annex-l1","log","refs/heads/git-annex..b919b83cafeff420d23af24ff7de35b4ff955c8c","--oneline","-n1"]
-[2013-07-20 22:45:13 MDT] chat: git ["--git-dir=/home/cantora/annex-l1/.git","--work-tree=/home/cantora/annex-l1","cat-file","--batch"]
-[2013-07-20 22:45:13 MDT] read: git ["config","--null","--list"]
-initremote glacier (encryption setup) [2013-07-20 22:45:13 MDT] read: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--with-colons","--list-public-keys","annex-l1@ggg.local"]
-[2013-07-20 22:45:13 MDT] read: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--gen-random","--armor","2","512"]
-[2013-07-20 22:47:37 MDT] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--encrypt","--no-encrypt-to","--no-default-recipient","--recipient","DF31708872834ABA"]
-(with gpg key DF31708872834ABA) [2013-07-20 22:47:37 MDT] call: glacier ["--region=us-east-1","vault","create","some-vault-name"]
-[2013-07-20 22:47:38 MDT] call: git ["--git-dir=/home/cantora/annex-l1/.git","--work-tree=/home/cantora/annex-l1","config","remote.glacier.annex-glacier","true"]
-[2013-07-20 22:47:38 MDT] call: git ["--git-dir=/home/cantora/annex-l1/.git","--work-tree=/home/cantora/annex-l1","config","remote.glacier.annex-uuid","a9739087-7860-4ed0-bc38-0b6031b1afd3"]
-(gpg) [2013-07-20 22:47:38 MDT] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--decrypt"]
-[2013-07-20 22:47:38 MDT] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--batch","--passphrase-fd","3","--symmetric","--force-mdc"]
-#at this point it simply waits forever. not sure what it's waiting for, stdin maybe? maybe fd 3 is empty??
-
-#[on a different terminal]
-$> ps ax | grep gpg | grep -v ssh
- 2024 ?        Ss     0:00 /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/cantora/.gnupg/gpg-agent-info-ggg /usr/bin/dbus-launch --exit-with-session gnome-session --session=ubuntu
- 8341 pts/4    SL+    0:00 gpg --batch --no-tty --use-agent --quiet --trust-model always --batch --passphrase-fd 3 --symmetric --force-mdc
- 8652 pts/5    S+     0:00 grep --color=auto gpg
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; see comments --[[Joey]] 
diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment
deleted file mode 100644
index 2dae713b0..000000000
--- a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.1.10"
- subject="comment 1"
- date="2013-07-22T21:41:01Z"
- content="""
-I have tried but have not had any luck reproducing this when initializing a glacier remote.
-
-Do you also get this problem if you initialize a special remote of another type, such as the directory special remote, that's encrypted to the same gpg key?
-
-Can you reproduce the hang using the [[/install/Linux_standalone]] tarball?
-
-You should be able to tell which file descriptor gpg is blocking on. Just attach strace to the gpg process, and see what file descriptor it says gpg is reading from (or perhaps writing to). Since git-annex feeds it both a passphrase and data to encrypt, knowing the number of the file descriptor will narrow down the bug's cause.
-"""]]
diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_2_dd11fd25c8bb1f2d7e1292c07abf553e._comment b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_2_dd11fd25c8bb1f2d7e1292c07abf553e._comment
deleted file mode 100644
index 7749bed1e..000000000
--- a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_2_dd11fd25c8bb1f2d7e1292c07abf553e._comment
+++ /dev/null
@@ -1,591 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkiAsTXFXZbLE8iyy6yDtvz4MPFbzsk3c0"
- nickname="Tony"
- subject="strace of gpg process"
- date="2013-07-24T00:02:22Z"
- content="""
-Hello, here is some trace information on the gpg process, I hope it helps.
-
-the initremote command used:
-[[!format sh \"\"\"
-$> strace -o /tmp/git-annex.trace -e trace=file -e trace=read -f git annex initremote glacier type=glacier encryption=testA@ggg.local embedcreds=yes vault=test-vault --verbose --debug                                                                      
-[2013-07-23 15:36:06 MDT] read: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"show-ref\",\"git-annex\"]
-[2013-07-23 15:36:06 MDT] read: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]                                                                                                        
-[2013-07-23 15:36:06 MDT] read: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"log\",\"refs/heads/git-annex..55754a54c5777336d594af0a173805d150deb828\",\"--oneline\",\"-n1\"]                                                          
-[2013-07-23 15:36:06 MDT] chat: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"cat-file\",\"--batch\"]
-initremote glacier (encryption setup) [2013-07-23 15:36:07 MDT] read: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--with-colons\",\"--list-public-keys\",\"testA@ggg.local\"]                                                                 
-[2013-07-23 15:36:07 MDT] read: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--gen-random\",\"--armor\",\"2\",\"512\"]
-[2013-07-23 15:39:12 MDT] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--encrypt\",\"--no-encrypt-to\",\"--no-default-recipient\",\"--recipient\",\"05E4CF57CBCAD77C\"]                                                                      
-(with gpg key 05E4CF57CBCAD77C) [2013-07-23 15:39:12 MDT] call: glacier [\"--region=us-east-1\",\"vault\",\"create\",\"test-vault\"]
-[2013-07-23 15:39:14 MDT] call: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"config\",\"remote.glacier.annex-glacier\",\"true\"]                                                                                                    
-[2013-07-23 15:39:14 MDT] call: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"config\",\"remote.glacier.annex-uuid\",\"397411b1-30be-4bdc-b3dd-6ab0d8f8ae8b\"]                                                                       
-(gpg) [2013-07-23 15:39:14 MDT] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--decrypt\"]
-[2013-07-23 15:39:14 MDT] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--batch\",\"--passphrase-fd\",\"3\",\"--symmetric\",\"--force-mdc\"]                                                                                                  
-^C                                                                                                                        
-gpg: Interrupt caught ... exiting
-\"\"\"]]
-
-the hanging gpg process:
-[[!format sh \"\"\"
-$> ps ax | grep gpg | grep -v ssh                                                                        
- 2017 ?        Ss     0:02 /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/cantora/.gnupg/gpg-agent-info-ggg /usr/bin/dbus-launch --exit-with-session gnome-session --session=ubuntu                                                                             
- 8268 pts/3    SL+    0:00 gpg --batch --no-tty --use-agent --quiet --trust-model always --batch --passphrase-fd 3 --symmetric --force-mdc
- 8357 pts/4    S+     0:00 grep --color=auto gpg 
-\"\"\"]]
-
-and the content of the trace (only the end where the gpg process is created):
-
-[[!format txt \"\"\"
-[...]
-8265  read(5, \"[core]\n\trepositoryformatversion \"..., 4096) = 199
-8265  read(5, \"\", 4096)                 = 0
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8245  --- SIGCHLD (Child exited) @ 0 (0) ---
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8266  read(3, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\2209\0\0\0\0\0\0\"..., 832) = 832
-8266  read(3, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P \0\0\0\0\0\0\"..., 832) = 832
-8266  read(3, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\26\0\0\0\0\0\0\"..., 832) = 832
-8266  read(3, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\\"\1\0\0\0\0\0\"..., 832) = 832
-8266  read(3, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\r\0\0\0\0\0\0\"..., 832) = 832
-8266  read(3, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\25\0\0\0\0\0\0\"..., 832) = 832
-8266  read(3, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\30\2\0\0\0\0\0\"..., 832) = 832
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8266  read(3, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\301\0\0\0\0\0\0\"..., 832) = 832
-8266  read(3, \"# Options for GnuPG\n# Copyright \"..., 4096) = 4096
-8266  read(3, \"ost servers (with the notable ex\"..., 4096) = 4096
-8266  read(3, \"t during gpg-agent startup.\n# In\"..., 4096) = 1206
-8266  read(3, \"\", 4096)                 = 0
-8266  read(3, \"\225\7>\4Q\340r!\1\20\0\313B\370D\25\275g\317\270\3>\356\243H\230w\303\252\303\2712\"..., 4096) = 4096
-8266  read(3, \"\231\2\r\4M\370\317\334\1\20\0\223\337X\257\366/\t\307\376\214\207,\26\233+R\31j#K\266\"..., 4096) = 4096
-8266  read(0,  <unfinished ...>
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8266  <... read resumed> \"\205\1\f\3Xp+\246\227\277\336\3\1\7\376 B3K\224\352T\373$\30\246\f?h\272\266\21\"..., 8192) = 889
-8266  read(3,  <unfinished ...>
-8245  read(7,  <unfinished ...>
-8266  <... read resumed> \"\225\7>\4Q\340r!\1\20\0\313B\370D\25\275g\317\270\3>\356\243H\230w\303\252\303\2712\"..., 8192) = 8192
-8245  <... read resumed> 0x7fbc17ead010, 8096) = -1 EAGAIN (Resource temporarily unavailable)
-8266  read(3, \": \351R\326\342Y\325Sk\3~\31X\252d\24\357{+\17\237m\35\273\201\250T\10\200n\226\"..., 8192) = 4129
-8266  read(3, \"\225\7>\4Q\340r!\1\20\0\313B\370D\25\275g\317\270\3>\356\243H\230w\303\252\303\2712\"..., 8192) = 8192
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8266  read(3, \": \351R\326\342Y\325Sk\3~\31X\252d\24\357{+\17\237m\35\273\201\250T\10\200n\226\"..., 8192) = 4129
-8266  read(4, \"\225\3\276\4Q\354\214U\1\10\0\351 NjDf\31\305\16~$\272i#\321\325\10\276\307\273{\"..., 8192) = 2560
-8266  read(4, \"\", 8192)                 = 0
-8266  read(5, \"\231\2\r\4M\370\317\334\1\20\0\223\337X\257\366/\t\307\376\214\207,\26\233+R\31j#K\266\"..., 8192) = 7836
-8266  read(6, \"\231\1\r\4Q\354\214U\1\10\0\351 NjDf\31\305\16~$\272i#\321\325\10\276\307\273{\"..., 8192) = 1182
-8266  read(6, \"\", 8192)                 = 0
-8266  read(5, \"\231\2\r\4M\370\317\334\1\20\0\223\337X\257\366/\t\307\376\214\207,\26\233+R\31j#K\266\"..., 8192) = 7836
-8266  read(6, \"\231\1\r\4Q\354\214U\1\10\0\351 NjDf\31\305\16~$\272i#\321\325\10\276\307\273{\"..., 8192) = 1182
-8266  read(6, \"\", 8192)                 = 0
-8266  read(7, \"OK your orders please\n\", 1002) = 22
-8266  read(7, \"OK \n\", 1002)            = 4
-8266  read(7, \"OK \n\", 1002)            = 4
-8266  read(7, \"OK \n\", 1002)            = 4
-8266  read(7, \"OK \n\", 1002)            = 4
-8266  read(7, \"OK \n\", 1002)            = 4
-8266  read(8, \"# Locale name alias data base.\n#\"..., 4096) = 2570
-8266  read(8, \"\", 4096)                 = 0
-8266  read(8, \"TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\4\0\0\0\4\0\0\0\0\"..., 4096) = 2427
-8266  read(8, \"TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\5\0\0\0\5\0\0\0\0\"..., 4096) = 1550
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8266  read(7, \"OK 616e746f7831616e746f78\n\", 1002) = 26
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8266  read(6, \"\231\2\r\4M\370\317\334\1\20\0\223\337X\257\366/\t\307\376\214\207,\26\233+R\31j#K\266\"..., 8192) = 7836
-8266  read(5, \"\231\1\r\4Q\354\214U\1\10\0\351 NjDf\31\305\16~$\272i#\321\325\10\276\307\273{\"..., 8192) = 1182
-8266  read(5, \"\", 8192)                 = 0
-8266  read(0, \"\", 8192)                 = 0
-8245  read(7, \"hssHvXB6YTHPFmwu0uliVVZlm+olG/Do\"..., 8096) = 685
-8245  read(7, 0x7fbc17ead010, 8096)     = -1 EAGAIN (Resource temporarily unavailable)
-8245  --- SIGCHLD (Child exited) @ 0 (0) ---
-8245  read(7, \"\", 8096)                 = 0
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8245  --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
-8268  read(4, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\2209\0\0\0\0\0\0\"..., 832) = 832
-8268  read(4, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P \0\0\0\0\0\0\"..., 832) = 832
-8268  read(4, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\26\0\0\0\0\0\0\"..., 832) = 832
-8268  read(4, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\\"\1\0\0\0\0\0\"..., 832) = 832
-8268  read(4, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\r\0\0\0\0\0\0\"..., 832) = 832
-8268  read(4, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\25\0\0\0\0\0\0\"..., 832) = 832
-8268  read(4, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\30\2\0\0\0\0\0\"..., 832) = 832
-8268  read(4, \"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\301\0\0\0\0\0\0\"..., 832) = 832
-8268  read(4, \"# Options for GnuPG\n# Copyright \"..., 4096) = 4096
-8268  read(4, \"ost servers (with the notable ex\"..., 4096) = 4096
-8268  read(4, \"t during gpg-agent startup.\n# In\"..., 4096) = 1206
-8268  read(4, \"\", 4096)                 = 0
-8268  read(4, \"\231\2\r\4M\370\317\334\1\20\0\223\337X\257\366/\t\307\376\214\207,\26\233+R\31j#K\266\"..., 4096) = 4096
-8268  read(3, \"0\", 1)                   = 1
-8268  read(3, \"5\", 1)                   = 1
-8268  read(3, \"B\", 1)                   = 1
-8268  read(3, \"5\", 1)                   = 1
-8268  read(3, \"7\", 1)                   = 1
-8268  read(3, \"u\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"X\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"X\", 1)                   = 1
-8268  read(3, \"u\", 1)                   = 1
-8268  read(3, \"R\", 1)                   = 1
-8268  read(3, \"D\", 1)                   = 1
-8268  read(3, \"n\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"T\", 1)                   = 1
-8268  read(3, \"h\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"Q\", 1)                   = 1
-8268  read(3, \"t\", 1)                   = 1
-8268  read(3, \"k\", 1)                   = 1
-8268  read(3, \"1\", 1)                   = 1
-8268  read(3, \"6\", 1)                   = 1
-8268  read(3, \"F\", 1)                   = 1
-8268  read(3, \"7\", 1)                   = 1
-8268  read(3, \"K\", 1)                   = 1
-8268  read(3, \"/\", 1)                   = 1
-8268  read(3, \"o\", 1)                   = 1
-8268  read(3, \"v\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"8\", 1)                   = 1
-8268  read(3, \"8\", 1)                   = 1
-8268  read(3, \"5\", 1)                   = 1
-8268  read(3, \"Y\", 1)                   = 1
-8268  read(3, \"6\", 1)                   = 1
-8268  read(3, \"u\", 1)                   = 1
-8268  read(3, \"R\", 1)                   = 1
-8268  read(3, \"V\", 1)                   = 1
-8268  read(3, \"k\", 1)                   = 1
-8268  read(3, \"M\", 1)                   = 1
-8268  read(3, \"n\", 1)                   = 1
-8268  read(3, \"a\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"u\", 1)                   = 1
-8268  read(3, \"Q\", 1)                   = 1
-8268  read(3, \"o\", 1)                   = 1
-8268  read(3, \"9\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"u\", 1)                   = 1
-8268  read(3, \"9\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"q\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"3\", 1)                   = 1
-8268  read(3, \"3\", 1)                   = 1
-8268  read(3, \"v\", 1)                   = 1
-8268  read(3, \"t\", 1)                   = 1
-8268  read(3, \"K\", 1)                   = 1
-8268  read(3, \"c\", 1)                   = 1
-8268  read(3, \"b\", 1)                   = 1
-8268  read(3, \"a\", 1)                   = 1
-8268  read(3, \"8\", 1)                   = 1
-8268  read(3, \"q\", 1)                   = 1
-8268  read(3, \"4\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"y\", 1)                   = 1
-8268  read(3, \"b\", 1)                   = 1
-8268  read(3, \"i\", 1)                   = 1
-8268  read(3, \"k\", 1)                   = 1
-8268  read(3, \"n\", 1)                   = 1
-8268  read(3, \"i\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"V\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"X\", 1)                   = 1
-8268  read(3, \"Q\", 1)                   = 1
-8268  read(3, \"y\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"6\", 1)                   = 1
-8268  read(3, \"K\", 1)                   = 1
-8268  read(3, \"C\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"C\", 1)                   = 1
-8268  read(3, \"3\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"0\", 1)                   = 1
-8268  read(3, \"Q\", 1)                   = 1
-8268  read(3, \"X\", 1)                   = 1
-8268  read(3, \"c\", 1)                   = 1
-8268  read(3, \"T\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"a\", 1)                   = 1
-8268  read(3, \"u\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"h\", 1)                   = 1
-8268  read(3, \"G\", 1)                   = 1
-8268  read(3, \"q\", 1)                   = 1
-8268  read(3, \"1\", 1)                   = 1
-8268  read(3, \"v\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"4\", 1)                   = 1
-8268  read(3, \"o\", 1)                   = 1
-8268  read(3, \"T\", 1)                   = 1
-8268  read(3, \"Z\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"5\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"j\", 1)                   = 1
-8268  read(3, \"W\", 1)                   = 1
-8268  read(3, \"y\", 1)                   = 1
-8268  read(3, \"i\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"r\", 1)                   = 1
-8268  read(3, \"5\", 1)                   = 1
-8268  read(3, \"m\", 1)                   = 1
-8268  read(3, \"G\", 1)                   = 1
-8268  read(3, \"b\", 1)                   = 1
-8268  read(3, \"0\", 1)                   = 1
-8268  read(3, \"v\", 1)                   = 1
-8268  read(3, \"9\", 1)                   = 1
-8268  read(3, \"U\", 1)                   = 1
-8268  read(3, \"p\", 1)                   = 1
-8268  read(3, \"F\", 1)                   = 1
-8268  read(3, \"R\", 1)                   = 1
-8268  read(3, \"c\", 1)                   = 1
-8268  read(3, \"/\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"F\", 1)                   = 1
-8268  read(3, \"4\", 1)                   = 1
-8268  read(3, \"g\", 1)                   = 1
-8268  read(3, \"G\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"D\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"t\", 1)                   = 1
-8268  read(3, \"B\", 1)                   = 1
-8268  read(3, \"z\", 1)                   = 1
-8268  read(3, \"q\", 1)                   = 1
-8268  read(3, \"a\", 1)                   = 1
-8268  read(3, \"u\", 1)                   = 1
-8268  read(3, \"9\", 1)                   = 1
-8268  read(3, \"S\", 1)                   = 1
-8268  read(3, \"W\", 1)                   = 1
-8268  read(3, \"2\", 1)                   = 1
-8268  read(3, \"r\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"2\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"j\", 1)                   = 1
-8268  read(3, \"T\", 1)                   = 1
-8268  read(3, \"D\", 1)                   = 1
-8268  read(3, \"w\", 1)                   = 1
-8268  read(3, \"R\", 1)                   = 1
-8268  read(3, \"1\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"j\", 1)                   = 1
-8268  read(3, \"D\", 1)                   = 1
-8268  read(3, \"a\", 1)                   = 1
-8268  read(3, \"Y\", 1)                   = 1
-8268  read(3, \"b\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"v\", 1)                   = 1
-8268  read(3, \"x\", 1)                   = 1
-8268  read(3, \"g\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"V\", 1)                   = 1
-8268  read(3, \"m\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"U\", 1)                   = 1
-8268  read(3, \"K\", 1)                   = 1
-8268  read(3, \"p\", 1)                   = 1
-8268  read(3, \"e\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"R\", 1)                   = 1
-8268  read(3, \"4\", 1)                   = 1
-8268  read(3, \"Y\", 1)                   = 1
-8268  read(3, \"C\", 1)                   = 1
-8268  read(3, \"w\", 1)                   = 1
-8268  read(3, \"o\", 1)                   = 1
-8268  read(3, \"4\", 1)                   = 1
-8268  read(3, \"c\", 1)                   = 1
-8268  read(3, \"C\", 1)                   = 1
-8268  read(3, \"i\", 1)                   = 1
-8268  read(3, \"U\", 1)                   = 1
-8268  read(3, \"q\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"b\", 1)                   = 1
-8268  read(3, \"K\", 1)                   = 1
-8268  read(3, \"p\", 1)                   = 1
-8268  read(3, \"9\", 1)                   = 1
-8268  read(3, \"T\", 1)                   = 1
-8268  read(3, \"/\", 1)                   = 1
-8268  read(3, \"2\", 1)                   = 1
-8268  read(3, \"R\", 1)                   = 1
-8268  read(3, \"s\", 1)                   = 1
-8268  read(3, \"O\", 1)                   = 1
-8268  read(3, \"P\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"a\", 1)                   = 1
-8268  read(3, \"e\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"M\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"I\", 1)                   = 1
-8268  read(3, \"h\", 1)                   = 1
-8268  read(3, \"T\", 1)                   = 1
-8268  read(3, \"c\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"w\", 1)                   = 1
-8268  read(3, \"D\", 1)                   = 1
-8268  read(3, \"e\", 1)                   = 1
-8268  read(3, \"O\", 1)                   = 1
-8268  read(3, \"g\", 1)                   = 1
-8268  read(3, \"c\", 1)                   = 1
-8268  read(3, \"M\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"n\", 1)                   = 1
-8268  read(3, \"U\", 1)                   = 1
-8268  read(3, \"C\", 1)                   = 1
-8268  read(3, \"O\", 1)                   = 1
-8268  read(3, \"H\", 1)                   = 1
-8268  read(3, \"I\", 1)                   = 1
-8268  read(3, \"w\", 1)                   = 1
-8268  read(3, \"h\", 1)                   = 1
-8268  read(3, \"I\", 1)                   = 1
-8268  read(3, \"Z\", 1)                   = 1
-8268  read(3, \"W\", 1)                   = 1
-8268  read(3, \"c\", 1)                   = 1
-8268  read(3, \"T\", 1)                   = 1
-8268  read(3, \"1\", 1)                   = 1
-8268  read(3, \"n\", 1)                   = 1
-8268  read(3, \"p\", 1)                   = 1
-8268  read(3, \"Y\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"U\", 1)                   = 1
-8268  read(3, \"9\", 1)                   = 1
-8268  read(3, \"H\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"g\", 1)                   = 1
-8268  read(3, \"D\", 1)                   = 1
-8268  read(3, \"G\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"5\", 1)                   = 1
-8268  read(3, \"B\", 1)                   = 1
-8268  read(3, \"m\", 1)                   = 1
-8268  read(3, \"V\", 1)                   = 1
-8268  read(3, \"w\", 1)                   = 1
-8268  read(3, \"Q\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"B\", 1)                   = 1
-8268  read(3, \"r\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"n\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"s\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"X\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"m\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"t\", 1)                   = 1
-8268  read(3, \"X\", 1)                   = 1
-8268  read(3, \"S\", 1)                   = 1
-8268  read(3, \"R\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"n\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"U\", 1)                   = 1
-8268  read(3, \"S\", 1)                   = 1
-8268  read(3, \"v\", 1)                   = 1
-8268  read(3, \"i\", 1)                   = 1
-8268  read(3, \"Z\", 1)                   = 1
-8268  read(3, \"S\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"5\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"8\", 1)                   = 1
-8268  read(3, \"3\", 1)                   = 1
-8268  read(3, \"K\", 1)                   = 1
-8268  read(3, \"v\", 1)                   = 1
-8268  read(3, \"O\", 1)                   = 1
-8268  read(3, \"x\", 1)                   = 1
-8268  read(3, \"q\", 1)                   = 1
-8268  read(3, \"v\", 1)                   = 1
-8268  read(3, \"5\", 1)                   = 1
-8268  read(3, \"6\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"Y\", 1)                   = 1
-8268  read(3, \"Z\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"h\", 1)                   = 1
-8268  read(3, \"V\", 1)                   = 1
-8268  read(3, \"a\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"z\", 1)                   = 1
-8268  read(3, \"P\", 1)                   = 1
-8268  read(3, \"y\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"2\", 1)                   = 1
-8268  read(3, \"0\", 1)                   = 1
-8268  read(3, \"n\", 1)                   = 1
-8268  read(3, \"U\", 1)                   = 1
-8268  read(3, \"P\", 1)                   = 1
-8268  read(3, \"0\", 1)                   = 1
-8268  read(3, \"j\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"F\", 1)                   = 1
-8268  read(3, \"g\", 1)                   = 1
-8268  read(3, \"4\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"B\", 1)                   = 1
-8268  read(3, \"C\", 1)                   = 1
-8268  read(3, \"J\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"T\", 1)                   = 1
-8268  read(3, \"H\", 1)                   = 1
-8268  read(3, \"x\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"k\", 1)                   = 1
-8268  read(3, \"o\", 1)                   = 1
-8268  read(3, \"Y\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"X\", 1)                   = 1
-8268  read(3, \"X\", 1)                   = 1
-8268  read(3, \"/\", 1)                   = 1
-8268  read(3, \"e\", 1)                   = 1
-8268  read(3, \"j\", 1)                   = 1
-8268  read(3, \"g\", 1)                   = 1
-8268  read(3, \"8\", 1)                   = 1
-8268  read(3, \"j\", 1)                   = 1
-8268  read(3, \"o\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"h\", 1)                   = 1
-8268  read(3, \"w\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"C\", 1)                   = 1
-8268  read(3, \"/\", 1)                   = 1
-8268  read(3, \"0\", 1)                   = 1
-8268  read(3, \"I\", 1)                   = 1
-8268  read(3, \"r\", 1)                   = 1
-8268  read(3, \"r\", 1)                   = 1
-8268  read(3, \"5\", 1)                   = 1
-8268  read(3, \"p\", 1)                   = 1
-8268  read(3, \"w\", 1)                   = 1
-8268  read(3, \"I\", 1)                   = 1
-8268  read(3, \"c\", 1)                   = 1
-8268  read(3, \"H\", 1)                   = 1
-8268  read(3, \"S\", 1)                   = 1
-8268  read(3, \"C\", 1)                   = 1
-8268  read(3, \"d\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"Y\", 1)                   = 1
-8268  read(3, \"W\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"U\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"O\", 1)                   = 1
-8268  read(3, \"s\", 1)                   = 1
-8268  read(3, \"Y\", 1)                   = 1
-8268  read(3, \"m\", 1)                   = 1
-8268  read(3, \"+\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"Z\", 1)                   = 1
-8268  read(3, \"q\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"2\", 1)                   = 1
-8268  read(3, \"V\", 1)                   = 1
-8268  read(3, \"f\", 1)                   = 1
-8268  read(3, \"h\", 1)                   = 1
-8268  read(3, \"E\", 1)                   = 1
-8268  read(3, \"j\", 1)                   = 1
-8268  read(3, \"K\", 1)                   = 1
-8268  read(3, \"I\", 1)                   = 1
-8268  read(3, \"O\", 1)                   = 1
-8268  read(3, \"9\", 1)                   = 1
-8268  read(3, \"B\", 1)                   = 1
-8268  read(3, \"y\", 1)                   = 1
-8268  read(3, \"T\", 1)                   = 1
-8268  read(3, \"N\", 1)                   = 1
-8268  read(3, \"V\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"W\", 1)                   = 1
-8268  read(3, \"u\", 1)                   = 1
-8268  read(3, \"0\", 1)                   = 1
-8268  read(3, \"s\", 1)                   = 1
-8268  read(3, \"6\", 1)                   = 1
-8268  read(3, \"k\", 1)                   = 1
-8268  read(3, \"7\", 1)                   = 1
-8268  read(3, \"U\", 1)                   = 1
-8268  read(3, \"0\", 1)                   = 1
-8268  read(3, \"j\", 1)                   = 1
-8268  read(3, \"k\", 1)                   = 1
-8268  read(3, \"M\", 1)                   = 1
-8268  read(3, \"k\", 1)                   = 1
-8268  read(3, \"y\", 1)                   = 1
-8268  read(3, \"R\", 1)                   = 1
-8268  read(3, \"3\", 1)                   = 1
-8268  read(3, \"a\", 1)                   = 1
-8268  read(3, \"m\", 1)                   = 1
-8268  read(3, \"J\", 1)                   = 1
-8268  read(3, \"0\", 1)                   = 1
-8268  read(3, \"a\", 1)                   = 1
-8268  read(3, \"A\", 1)                   = 1
-8268  read(3, \"g\", 1)                   = 1
-8268  read(3, \"t\", 1)                   = 1
-8268  read(3, \"z\", 1)                   = 1
-8268  read(3, \"Y\", 1)                   = 1
-8268  read(3, \"l\", 1)                   = 1
-8268  read(3, \"F\", 1)                   = 1
-8268  read(3, \"L\", 1)                   = 1
-8268  read(3, \"S\", 1)                   = 1
-8268  read(3, \"J\", 1)                   = 1
-8268  read(3, \"Q\", 1)                   = 1
-8268  read(3, \"z\", 1)                   = 1
-8268  read(3, \"6\", 1)                   = 1
-8268  read(3, \"k\", 1)                   = 1
-8268  read(3, \"=\", 1)                   = 1
-8268  read(3, \"\n\", 1)                  = 1
-8268  read(4, \"q\224R\236\341\264\336\23\315FTD\341\253\372\6o\206\326\376\243\326\34L\1\245;\tb\361v\\\"..., 600) = 600
-8268  read(4, \"\2548\332\257\334\237\343\354\23\224\377\377\302\264\352\21\", 16) = 16
-8268  read(0, 0x1911620, 8192)          = ? ERESTARTSYS (To be restarted)
-8250  <... read resumed> 0x7fb8e76a4000, 4096) = ? ERESTARTSYS (To be restarted)
-8268  --- SIGINT (Interrupt) @ 0 (0) ---
-8250  --- SIGINT (Interrupt) @ 0 (0) ---
-8268  --- SIGINT (Interrupt) @ 0 (0) ---
-8245  --- SIGINT (Interrupt) @ 0 (0) ---
-8244  --- SIGINT (Interrupt) @ 0 (0) ---
-8244  --- SIGINT (Interrupt) @ 0 (0) ---
-8244  +++ killed by SIGINT +++
-
-\"\"\"]]
-
-So it looks like its waiting on fd 0.
-
-Also, here is what happens when I create a directory special remote with encryption:
-[[!format sh \"\"\"
-$> git annex initremote test-remote type=directory directory=/tmp/test-remote encryption=testA@ggg.local --verbose --debug                                                                                                                                     
-[2013-07-23 16:07:10 MDT] read: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"show-ref\",\"git-annex\"]
-[2013-07-23 16:07:10 MDT] read: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]                                                                                                                
-[2013-07-23 16:07:10 MDT] read: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"log\",\"refs/heads/git-annex..27b816334be0c912ae8a4e3811fda0db397974c1\",\"--oneline\",\"-n1\"]
-[2013-07-23 16:07:10 MDT] chat: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"cat-file\",\"--batch\"]
-initremote test-remote (encryption setup) [2013-07-23 16:07:10 MDT] read: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--with-colons\",\"--list-public-keys\",\"testA@ggg.local\"]
-[2013-07-23 16:07:10 MDT] read: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--gen-random\",\"--armor\",\"2\",\"512\"]
-[2013-07-23 16:10:43 MDT] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--encrypt\",\"--no-encrypt-to\",\"--no-default-recipient\",\"--recipient\",\"05E4CF57CBCAD77C\"]
-(with gpg key 05E4CF57CBCAD77C) [2013-07-23 16:10:43 MDT] call: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"config\",\"remote.test-remote.annex-directory\",\"/tmp/test-remote\"]
-[2013-07-23 16:10:43 MDT] call: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"config\",\"remote.test-remote.annex-uuid\",\"c3fdb6be-2a3b-4bc0-a4df-0fbf7216fd85\"]
-ok
-[2013-07-23 16:10:43 MDT] chat: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"hash-object\",\"-w\",\"--stdin-paths\",\"--no-filters\"]
-[2013-07-23 16:10:43 MDT] feed: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"update-index\",\"-z\",\"--index-info\"]
-[2013-07-23 16:10:43 MDT] read: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-(Recording state in git...)
-[2013-07-23 16:10:43 MDT] read: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"write-tree\"]
-[2013-07-23 16:10:43 MDT] chat: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"commit-tree\",\"19dff833a084fa6b36c9438d6ee77f0122ce9bfd\",\"-p\",\"refs/heads/git-annex\"]
-[2013-07-23 16:10:43 MDT] call: git [\"--git-dir=/home/cantora/annex-test/.git\",\"--work-tree=/home/cantora/annex-test\",\"update-ref\",\"refs/heads/git-annex\",\"f06b1b83b38adc7692adedebc10d03daf584dbbb\"]
-$> git remote
-test-remote
-\"\"\"]]
-So the directory special remote seems to work just fine.
-
-Ill try using the standalone linux install later when I have some more time and post the results back here.
-"""]]
diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_3_543d8a13756c1355a5752867bdcbefd3._comment b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_3_543d8a13756c1355a5752867bdcbefd3._comment
deleted file mode 100644
index 1e23e881a..000000000
--- a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_3_543d8a13756c1355a5752867bdcbefd3._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkiAsTXFXZbLE8iyy6yDtvz4MPFbzsk3c0"
- nickname="Tony"
- subject="unable to run standalone linux install"
- date="2013-07-24T17:57:22Z"
- content="""
-i was unable to test for this bug with the standalone install; this is what happens when i try:
-
-[[!format sh \"\"\"
-$> ./runshell 
-$ which git-annex
-/home/cantora/install/git-annex.linux/bin/git-annex
-$ git-annex version
-git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.16' not found (required by /home/cantora/install/git-annex.linux//usr/lib/x86_64-linux-gnu/libkrb5.so.3)
-git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /home/cantora/install/git-annex.linux//lib/x86_64-linux-gnu/libcom_err.so.2)
-git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /home/cantora/install/git-annex.linux//usr/lib/x86_64-linux-gnu/libstdc++.so.6)
-$
-\"\"\"]]
-
-"""]]
diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_4_6441cf25e6bd62c96d7e766da9bdd7fb._comment b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_4_6441cf25e6bd62c96d7e766da9bdd7fb._comment
deleted file mode 100644
index d7e278416..000000000
--- a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_4_6441cf25e6bd62c96d7e766da9bdd7fb._comment
+++ /dev/null
@@ -1,25 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 4"
- date="2013-07-25T17:38:38Z"
- content="""
-Hmm, that strace exposes the full symmetric encryption key that git-annex has created. Thankfully, it is a single use key which will only be used for this glacier remote, so if you avoid using that remote (which is probably not usable anyway due to initremote not finishing!), the exposure won't matter.
-
-But, it is possible that this part is where it reads your personal gpg private key file. Hopefully the 55 bytes exposed out of the full 616 byte file are before the actual secret key data, or not enough to weaken your key. :/
-
-8268  read(4, \"q\224R\236\341\264\336\23\315FTD\341\253\372\6o\206\326\376\243\326\34L\1\245;\tb\361v\\\"..., 600) = 600
-8268  read(4, \"\2548\332\257\334\237\343\354\23\224\377\377\302\264\352\21\", 16) = 16
-
-It seems to be easier to social engineer people into stracing gpg and exposing data than I'd have hoped. Actually, I didn't plan to do that at all, I just wanted you to attach to gpg after this point.
-
-----
-
-So yeah, your gpg is hanging on stdin after git-annex has sent it the \"passphrase\" (really a symmetric gpg key) on fd 3. 
-
-The reason the directory special remote doesn't hang is because it does not use gpg to encrypt anything during the initremote process.
-
-I think I have a theory of what's going on with your git-annex build. It does not include the assistant, so will be built without -threaded. Using the non-threaded runtime system may be leading to a deadlock when git-annex is supposed to be simulantaneously feeding stdin to gpg and processing its stdout.  I have historically had some trouble around this, and it has probably not been well tested without the threaded runtime.
-
-(The standalone tarball problem is due to this bug, which will hopefully be fixed soon: [[Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable]])
-"""]]
diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_5_72e152294e36bc5f2d78e8e2ebed6a23._comment b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_5_72e152294e36bc5f2d78e8e2ebed6a23._comment
deleted file mode 100644
index 4fe1cfb85..000000000
--- a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_5_72e152294e36bc5f2d78e8e2ebed6a23._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 5"
- date="2013-07-25T17:44:59Z"
- content="""
-I was able to reproduce the bug by building without -threaded
-"""]]
diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_6_890e85df05903795e01efbd7879f9c87._comment b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_6_890e85df05903795e01efbd7879f9c87._comment
deleted file mode 100644
index 352adf714..000000000
--- a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_6_890e85df05903795e01efbd7879f9c87._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 6"
- date="2013-07-25T17:57:31Z"
- content="""
-I've made it always build with -threaded. Did not see anything obvious I could do to not make it hang with the non-threaded runtime, other than forking a separate feeder process. -threaded may make it not build on a few systems with sustandard ghc support (like sparc). 
-"""]]
diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_7_042047f9fcc45abbfa47c3973d79f08e._comment b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_7_042047f9fcc45abbfa47c3973d79f08e._comment
deleted file mode 100644
index cd88ac9ce..000000000
--- a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_7_042047f9fcc45abbfa47c3973d79f08e._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkiAsTXFXZbLE8iyy6yDtvz4MPFbzsk3c0"
- nickname="Tony"
- subject="thanks!"
- date="2013-07-27T05:33:34Z"
- content="""
-thanks it works now (i installed the latest github version using cabal).
-
-btw i created a temporary fake gpg key for the strace i posted, as it seemed likely something would leak from posting it.
-"""]]
diff --git a/doc/bugs/gpg_needs_--use-agent.mdwn b/doc/bugs/gpg_needs_--use-agent.mdwn
deleted file mode 100644
index d9977909b..000000000
--- a/doc/bugs/gpg_needs_--use-agent.mdwn
+++ /dev/null
@@ -1,53 +0,0 @@
-git-annex gpg encryption fails here when GPG_AGENT_INFO is set, it needs to be supplied --use-agent to work.
-
-Output from git-annex:
-
-    copy file (to origin...) (gpg) gpg: can't query passphrase in batch mode
-    gpg: decryption failed: secret key not available
-    Command gpg ["--batch","--no-tty","--quiet","--trust-model","always","--decrypt"] failed; exit code 2
-    
-    git-annex: user error (Command gpg ["--batch","--no-tty","--quiet","--trust-model","always","--decrypt"] failed; exit code 2)
-    failed
-
-Reproduced on command-line:
-
-    [0 zerodogg@browncoats ~]$ echo test > testfile
-    [0 zerodogg@browncoats ~]$ gpg -e testfile
-    [0 zerodogg@browncoats ~]$ gpg --batch --no-tty --quiet --trust-model always --decrypt testfile.gpg 
-    gpg: can't query passphrase in batch mode
-    gpg: decryption failed: secret key not available
-    [2 zerodogg@browncoats ~]$ gpg --use-agent --batch --no-tty --quiet --trust-model always --decrypt testfile.gpg
-    test
-    [0 zerodogg@browncoats ~]$ 
-
-A patch to fix this issue:
-
-
-    From 77cb02d15245e9ad6e127388adcda960000fb3b8 Mon Sep 17 00:00:00 2001
-    From: Eskild Hustvedt <code@zerodogg.org>
-    Date: Fri, 17 Aug 2012 09:21:44 +0200
-    Subject: [PATCH] Explicitly enable agent to ensure decryption works
-    
-    Otherwise gpg will fail when GPG_AGENT_INFO is set in certain cases.
-    ---
-     Utility/Gpg.hs |    2 +-
-     1 file changed, 1 insertion(+), 1 deletion(-)
-    
-    diff --git a/Utility/Gpg.hs b/Utility/Gpg.hs
-    index e13afe5..c28b209 100644
-    --- a/Utility/Gpg.hs
-    +++ b/Utility/Gpg.hs
-    @@ -29,7 +29,7 @@ stdParams params = do
-        b <- getEnv "GPG_BATCH"
-        let batch = if isNothing e && isNothing b
-            then []
-    -       else ["--batch", "--no-tty"]
-    +       else ["--batch", "--no-tty", "--use-agent"]
-        return $ batch ++ defaults ++ toCommand params
-        where
-            -- be quiet, even about checking the trustdb
-    -- 
-    1.7.10.4
-
-> Thanks, [[done]].. I never noticed this since I have use-agent set in
-> gpg.conf. --[[Joey]
diff --git a/doc/bugs/gsha256sum_crashes.mdwn b/doc/bugs/gsha256sum_crashes.mdwn
deleted file mode 100644
index 9989b9866..000000000
--- a/doc/bugs/gsha256sum_crashes.mdwn
+++ /dev/null
@@ -1,92 +0,0 @@
-[[!meta title="SIGILL on Mavericks"]]
-
-### Please describe the problem.
-
-gsha256sum crashes continiously, so that excessive logs must be removed and the notebook is not responsive.
-
-Mac OS Mavericks
-
-### What steps will reproduce the problem?
-
-I cannot reproduce it. My guess is that it has problems with special characters in filenames of my music repository.
-
-### What version of git-annex are you using? On what operating system?
-
-Version: 5.20131221-g00d1673
-Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash 
-
-### Please provide any additional information below.
-
-
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-[2014-01-01 11:50:02 CET] main: starting assistant version 5.20131221-g00d1673
-[2014-01-01 11:53:43 CET] TransferScanner: Syncing with sokrates.local_Musik 
-Already up-to-date.
-
-(scanning...) [2014-01-01 11:53:45 CET] Watcher: Performing startup scan
-Already up-to-date.
-
-
-  The installed version of git is too old for .gitignores to be honored by git-annex.
-To ssh://juh@git-annex-sokrates.local-juh_Musik/~/Musik/
-   0ec1344..c7bc58c  git-annex -> synced/git-annex
-
-.DS_Store
-           0   0%    0.00kB/s    0:00:00
-       21508 100%  238.68kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 42 bytes  received 21602 bytes  14429.33 bytes/sec
-total size is 21508  speedup is 0.99
-[2014-01-01 12:10:03 CET] Transferrer: Downloaded .DS_Store
-[2014-01-01 12:10:03 CET] Pusher: Syncing with sokrates.local_Musik 
-To ssh://juh@git-annex-sokrates.local-juh_Musik/~/Musik/
-   c7bc58c..c3ad19a  git-annex -> synced/git-annex
-(Recording state in git...)
-(started...) [2014-01-01 12:33:25 CET] Committer: Adding 15 - 23 s.. drøm.ogg 04 Cuatro..ielo.flac 05 Compadrón.flac 07 Buscan..dón.flac 10 Adiós..lita.flac 12 Bésam..Boca.flac 14 Nunca ..idar.flac 03 Adiós..ngo).flac 06 Selecc..ngo).flac and 2745 other files
-
-add Edvard Grieg/Grieg Edition/Complete Piano Music/Complete Piano Music, Volume X (feat. piano_ Geir Henning Braaten)/15 - 23 småstykker for klaver, EG 104 No. 7- En drøm.ogg Committer crashed: gsha256sum parse error
-[2014-01-01 12:33:27 CET] Committer: warning Committer crashed: gsha256sum parse error
-
-.DS_Store
-           0   0%    0.00kB/s    0:00:00
-        6148 100%    5.86MB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 42 bytes  received 6242 bytes  4189.33 bytes/sec
-total size is 6148  speedup is 0.98
-[2014-01-01 12:49:45 CET] Transferrer: Downloaded .DS_Store
-[2014-01-01 12:49:45 CET] Pusher: Syncing with sokrates.local_Musik 
-[2014-01-01 12:53:42 CET] NetWatcherFallback: Syncing with sokrates.local_Musik 
-From ssh://git-annex-sokrates.local-juh_Musik/~/Musik
-   0ec1344..c3ad19a  git-annex  -> sokrates.local_Musik/git-annex
-fatal: Unable to create '/home/juh/Musik/.git/refs/heads/synced/git-annex.lock': Die Datei existiert bereits.
-
-If no other git process is currently running, this probably means a
-git process crashed in this repository earlier. Make sure no other git
-process is running and remove the file manually to continue.
-git-annex-shell: git-shell failed
-fatal: The remote end hung up unexpectedly
-fatal: The remote end hung up unexpectedly
-To ssh://juh@git-annex-sokrates.local-juh_Musik/~/Musik/
-   c3ad19a..e6da014  git-annex -> synced/git-annex
-From ssh://git-annex-sokrates.local-juh_Musik/~/Musik
-   c3ad19a..e6da014  git-annex  -> sokrates.local_Musik/git-annex
-Everything up-to-date
-[2014-01-01 13:11:59 CET] UpgradeWatcher: A new version of git-annex has been installed. 
-
-"""]]
-
-I can send you the crash report of hsha256sum if you need it.
-
-> Fine, we'll stop using this on OSX, since git-annex has its own builtin
-> and not even much slower hashers. done--[[Joey]]
-
->> I'm told that other programs, such as wget, also crash with SIGILL.
->> Are there multiple OSX architectures with different instructions sets or
->> what? --[[Joey]]
-
->>> Fixed and confirmed fixed now. gsha256sum etc added back to
->>> OSX app. [[done]] --[[Joey]]
diff --git a/doc/bugs/gsha256sum_crashes/comment_1_8597d8ee29232494b1795526b6a0d8d1._comment b/doc/bugs/gsha256sum_crashes/comment_1_8597d8ee29232494b1795526b6a0d8d1._comment
deleted file mode 100644
index a65b257db..000000000
--- a/doc/bugs/gsha256sum_crashes/comment_1_8597d8ee29232494b1795526b6a0d8d1._comment
+++ /dev/null
@@ -1,81 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnX1msQxnLoSeu7q-i-c9BWghonsN7Qmns"
- nickname="Jan Ulrich"
- subject="Additional infos"
- date="2014-01-01T13:23:45Z"
- content="""
-I am not sure whether this is related. But I now see this in syslog:
-
-[[!format sh \"\"\"
-
-cs_invalid_page(0x10fc36000): p=51598[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:05 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10f60f000): p=51599[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:05 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10f905000): p=51600[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:05 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10b57a000): p=51601[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:05 janulrimacbook2 kernel[0]: nspace-handler-unblock: did not find token 34386
-Jan  1 14:21:05 janulrimacbook2.fritz.box com.apple.mtmd[52]: handler unblock failed. (status=-1/errno=2/token=34386/fd=7)
-Jan  1 14:21:05 janulrimacbook2 kernel[0]: nspace-handler-unblock: did not find token 34384
-Jan  1 14:21:05 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x106c9a000): p=51602[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:05 janulrimacbook2.fritz.box com.apple.mtmd[52]: handler unblock failed. (status=-1/errno=2/token=34384/fd=6)
-Jan  1 14:21:05 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10c334000): p=51603[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:06 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x103397000): p=51608[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:06 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x101417000): p=51609[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:06 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10db10000): p=51610[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:06 janulrimacbook2 kernel[0]: nspace-handler-unblock: did not find token 34391
-Jan  1 14:21:06 janulrimacbook2.fritz.box com.apple.mtmd[52]: handler unblock failed. (status=-1/errno=2/token=34391/fd=6)
-Jan  1 14:21:06 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10db07000): p=51613[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:07 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x103be4000): p=51614[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:07 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10a980000): p=51615[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10ef68000): p=51616[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x101b74000): p=51617[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: nspace-handler-unblock: did not find token 34398
-Jan  1 14:21:08 janulrimacbook2.fritz.box com.apple.mtmd[52]: handler unblock failed. (status=-1/errno=2/token=34398/fd=7)
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x1026fe000): p=51618[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: nspace-handler-unblock: did not find token 34394
-Jan  1 14:21:08 janulrimacbook2.fritz.box com.apple.mtmd[52]: handler unblock failed. (status=-1/errno=2/token=34394/fd=6)
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x1051ed000): p=51623[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10b4c0000): p=51624[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x109b98000): p=51626[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x105972000): p=51628[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x104060000): p=51629[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:08 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10ecb2000): p=51630[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:09 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x107d65000): p=51631[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:09 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10b50c000): p=51632[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:10 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x106bfc000): p=51633[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:10 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x104c53000): p=51634[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:10 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x108998000): p=51635[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:10 janulrimacbook2 kernel[0]: nspace-handler-unblock: did not find token 34409
-Jan  1 14:21:10 janulrimacbook2.fritz.box com.apple.mtmd[52]: handler unblock failed. (status=-1/errno=2/token=34409/fd=6)
-Jan  1 14:21:10 janulrimacbook2 kernel[0]: nspace-handler-unblock: did not find token 34405
-Jan  1 14:21:10 janulrimacbook2.fritz.box com.apple.mtmd[52]: handler unblock failed. (status=-1/errno=2/token=34405/fd=5)
-Jan  1 14:21:10 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10392b000): p=51636[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:10 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x1049ad000): p=51641[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:10 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x109f60000): p=51642[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:10 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10fcd2000): p=51643[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:11 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10590f000): p=51646[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:12 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x1044eb000): p=51647[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:12 janulrimacbook2 kernel[0]: nspace-handler-unblock: did not find token 34416
-Jan  1 14:21:12 janulrimacbook2.fritz.box com.apple.mtmd[52]: handler unblock failed. (status=-1/errno=2/token=34416/fd=5)
-Jan  1 14:21:12 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10f911000): p=51648[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:12 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x1066dc000): p=51649[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:12 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10430a000): p=51655[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:13 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x1099b0000): p=51656[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:13 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10e80a000): p=51657[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:13 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10bf16000): p=51660[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:13 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10240c000): p=51661[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:14 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x103009000): p=51662[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:14 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x108d02000): p=51663[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:14 janulrimacbook2 kernel[0]: nspace-handler-unblock: did not find token 34421
-Jan  1 14:21:14 janulrimacbook2.fritz.box com.apple.mtmd[52]: handler unblock failed. (status=-1/errno=2/token=34421/fd=5)
-Jan  1 14:21:14 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10c7c6000): p=51664[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:14 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10612b000): p=51665[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:14 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x105872000): p=51670[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:14 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10a5b0000): p=51671[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:15 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x1062dc000): p=51672[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:15 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x104963000): p=51675[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:15 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x105b9c000): p=51676[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:15 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x10eb19000): p=51677[git] final status 0x0, allow (remove VALID)ing page
-Jan  1 14:21:16 janulrimacbook2 kernel[0]: CODE SIGNING: cs_invalid_page(0x1094d0000): p=51678[git] final status 0x0, allow (remove VALID)ing page
-
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/gsha256sum_crashes/comment_2_e410fc1998fbc7db8c13081f76acf7fc._comment b/doc/bugs/gsha256sum_crashes/comment_2_e410fc1998fbc7db8c13081f76acf7fc._comment
deleted file mode 100644
index 3977b0b5a..000000000
--- a/doc/bugs/gsha256sum_crashes/comment_2_e410fc1998fbc7db8c13081f76acf7fc._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 2"
- date="2014-01-01T16:48:45Z"
- content="""
-> Exception Type:  EXC_BAD_INSTRUCTION (SIGILL)
-
-So, clearly not related to the filename passed to gsha256sum.
-
-If you run the command \"/Applications/git-annex.app/Contents/MacOS/runshell gsha256sum\", does it also crash then?
-"""]]
diff --git a/doc/bugs/gsha256sum_crashes/comment_3_f796dd49097425148b785bb7b6213df6._comment b/doc/bugs/gsha256sum_crashes/comment_3_f796dd49097425148b785bb7b6213df6._comment
deleted file mode 100644
index 834314fa2..000000000
--- a/doc/bugs/gsha256sum_crashes/comment_3_f796dd49097425148b785bb7b6213df6._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnX1msQxnLoSeu7q-i-c9BWghonsN7Qmns"
- nickname="Jan Ulrich"
- subject="Yes"
- date="2014-01-01T18:18:32Z"
- content="""
-It says:
-
-Illegal instruction: 4
-"""]]
diff --git a/doc/bugs/gsha256sum_crashes/comment_4_1c46b4ad0c981c6105ffb8531223f0b1._comment b/doc/bugs/gsha256sum_crashes/comment_4_1c46b4ad0c981c6105ffb8531223f0b1._comment
deleted file mode 100644
index a188bf6f6..000000000
--- a/doc/bugs/gsha256sum_crashes/comment_4_1c46b4ad0c981c6105ffb8531223f0b1._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.35"
- subject="comment 4"
- date="2014-01-06T16:26:16Z"
- content="""
-So far, only Jan has seen this problem, and it has affected both wget and gsha256sum. 
-
-This makes me wonder if it's somehow a problem with running 64 bit code on his system.
-"""]]
diff --git a/doc/bugs/gsha256sum_crashes/comment_5_3fa106ed7fb30226ee7c48b66edb963c._comment b/doc/bugs/gsha256sum_crashes/comment_5_3fa106ed7fb30226ee7c48b66edb963c._comment
deleted file mode 100644
index 43ca8d31c..000000000
--- a/doc/bugs/gsha256sum_crashes/comment_5_3fa106ed7fb30226ee7c48b66edb963c._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.35"
- subject="comment 5"
- date="2014-01-06T16:47:43Z"
- content="""
-Searching for \"OSX SIGILL\" finds rather a lot of reports of problems like this.
-
-<http://trac.sagemath.org/ticket/12954>
-
-<http://stackoverflow.com/questions/20114920/can-an-exec-bad-instruction-sigill-on-dyld-my-fault>
-
-> My libraries were built using homebrew. By default homebrew optimizes for native architecture, resulting in machine instructions that don't work on older machines.
-
-Suggests to me that the OSX autobuilder probably needs to run the build with PATH set to a directory with un-optimised builds (or fat binary builds?) of all the utilities included in the app. Seems we're lucky and git-annex itself is not built with whatever sort of optimisations (SSE?) is causing this.
-"""]]
diff --git a/doc/bugs/gsha256sum_crashes/comment_6_276b181b2aeb1512e0468b88598e0a84._comment b/doc/bugs/gsha256sum_crashes/comment_6_276b181b2aeb1512e0468b88598e0a84._comment
deleted file mode 100644
index 9c0c40d67..000000000
--- a/doc/bugs/gsha256sum_crashes/comment_6_276b181b2aeb1512e0468b88598e0a84._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.35"
- subject="comment 6"
- date="2014-01-06T18:01:43Z"
- content="""
-I have updated the daily autobuild to use wget and coreutils (for gsha256sum) built using `brew install --build-bottle`. This should mean they are built portably without optimisations for the local CPU.
-
-That seems to be all the software on the build host that was installed using homebrew. So I hope the included rsync, curl xargs, etc are ok without being rebuilt.
-
-This all needs to be tested on a system affected by this problem..
-"""]]
diff --git a/doc/bugs/gsha256sum_crashes/comment_7_c2898422ceb9e103d8acdde866b7a211._comment b/doc/bugs/gsha256sum_crashes/comment_7_c2898422ceb9e103d8acdde866b7a211._comment
deleted file mode 100644
index 7f5fc0805..000000000
--- a/doc/bugs/gsha256sum_crashes/comment_7_c2898422ceb9e103d8acdde866b7a211._comment
+++ /dev/null
@@ -1,34 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw"
- nickname="Carl"
- subject="comment 7"
- date="2014-01-06T22:19:58Z"
- content="""
-I think I have the same problem.
-
-When adding some files using the assistant I see: an orange badge in the webapp that \"Committer crashed: gsha512sum parse error\"
-
-In the log I see:
-
-add Ekonomi/SEB/Portföljsammanställning/2013-07-02_Portföljsammanställning.pdf [2014-01-06 22:59:21 CET] chat: git [\"--git-dir=/Users/carlmod/Annex/.git\",\"--work-tree=/Users/carlmod/Annex\",\"check-attr\",\"-z\",\"--stdin\",\"annex.backend\",\"annex.numcopies\",\"--\"]
-[2014-01-06 22:59:21 CET] read: gsha512sum [\"/Users/carlmod/Annex/.git/annex/tmp/2013-07-02_Portfo\776l4592\"]
-Committer crashed: gsha512sum parse error
-[2014-01-06 22:59:21 CET] Committer: warning Committer crashed: gsha512sum parse error
-
-I am also running Mavericks, but my git-annex is built using homebrew on the computer it is running on.
-Version: 5.20131230 
-Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-
-$ gsha512sum --version
-sha512sum (GNU coreutils) 8.22
-Copyright (C) 2013 Free Software Foundation, Inc.
-License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
-This is free software: you are free to change and redistribute it.
-There is NO WARRANTY, to the extent permitted by law.
-
-Written by Ulrich Drepper, Scott Miller, and David Madore.
-
-$ gsha512sum 2013-07-02_Portföljsammanställning.pdf 
-25e774ed6c9adb4c1a0a68a3c7b907ead93493fc6eb6c4c24975d7d3f4c1d4b8f6c7e4b67a41418e2375d345d25f21775001add5fb5cb10675899eca432b006a  2013-07-02_Portföljsammanställning.pdf
-
-"""]]
diff --git a/doc/bugs/hGetContents:_user_error.mdwn b/doc/bugs/hGetContents:_user_error.mdwn
deleted file mode 100644
index 3f7467037..000000000
--- a/doc/bugs/hGetContents:_user_error.mdwn
+++ /dev/null
@@ -1,38 +0,0 @@
-### Please describe the problem.
-My server is on debian testing.  After an upgrade (git annex: 3.20120629 → 4.20130521) I can't do anything in my repository anymore.  git itself works, but invoking any git-annex command leads to:
-
-    git-annex: fd:6: hGetContents: user error (Pattern match failure in do expression at libraries/base/GHC/Event/Thread.hs:90:3-10)
-
-This repo is handled by a script, which invokes only the following git/git-annex commands:
-
-    $ git annex sync
-    $ git annex add
-    $ git commit -m "…"
-
-I realized this after trying to move files from my server to my local repo.  My local machine runs debian sid.  When trying to transfer files, this happens:
-
-    $ git annex sync
-    → ok
-    $ git annex move --from origin .
-    move x.zip (from origin...) 
-    user@host's password: ← pw ok
-    git-annex-shell: fd:6: hGetContents: user error (Pattern match failure in do expression at libraries/base/GHC/Event/Thread.hs:90:3-10)
-    rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
-    rsync error: error in rsync protocol data stream (code 12) at io.c(605) [Receiver=3.0.9]
-    failed
-
-I updated git-annex on both machines to 4.20130627 (rest of server is still on debian testing), but it didn't change anything.
-
-The server was not down since the last successful transfer, so I can't imagine anything interrupting any git-annex process.
-
-### What steps will reproduce the problem?
-See above.
-
-### What version of git-annex are you using? On what operating system?
-Server: 4.20130521 on debian testing (now: 4.20130627)
-Local: 4.20130621 on debian sid (now: 4.20130627)
-
-[[!meta title="fails to run on Linux with libc 2.17 and old kernel 2.6.32"]]
-
-> Closing this since it's a bad kernel and there is a workaround to build
-> a git-annex that will work with this kernel (see comments).  [[done]] --[[Joey]]
diff --git a/doc/bugs/hGetContents:_user_error/comment_1_30178f151f8c60d2ff856ca543dc506c._comment b/doc/bugs/hGetContents:_user_error/comment_1_30178f151f8c60d2ff856ca543dc506c._comment
deleted file mode 100644
index cc0ba50d2..000000000
--- a/doc/bugs/hGetContents:_user_error/comment_1_30178f151f8c60d2ff856ca543dc506c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 1"
- date="2013-06-30T17:31:26Z"
- content="""
-This looks uncomfortably like a bug in the ghc compiler's threaded runtime.
-
-What architecture is the server?
-"""]]
diff --git a/doc/bugs/hGetContents:_user_error/comment_2_f74eeed4a007058a22183fd678ecd6c6._comment b/doc/bugs/hGetContents:_user_error/comment_2_f74eeed4a007058a22183fd678ecd6c6._comment
deleted file mode 100644
index e718ff90e..000000000
--- a/doc/bugs/hGetContents:_user_error/comment_2_f74eeed4a007058a22183fd678ecd6c6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 2"
- date="2013-06-30T17:33:55Z"
- content="""
-See this upstream bug report: <http://hackage.haskell.org/trac/ghc/ticket/7653>
-"""]]
diff --git a/doc/bugs/hGetContents:_user_error/comment_3_515e562228a89a13d6d857a874f4a468._comment b/doc/bugs/hGetContents:_user_error/comment_3_515e562228a89a13d6d857a874f4a468._comment
deleted file mode 100644
index 70f45e6da..000000000
--- a/doc/bugs/hGetContents:_user_error/comment_3_515e562228a89a13d6d857a874f4a468._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://m-f-k.myopenid.com/"
- ip="84.138.125.150"
- subject="server's architecture"
- date="2013-06-30T23:37:00Z"
- content="""
-It's a i686 virtual server at strato.de.  Running kernel 2.6.32.
-"""]]
diff --git a/doc/bugs/hGetContents:_user_error/comment_4_8c6ed5e459c5c66b77db446c6317114c._comment b/doc/bugs/hGetContents:_user_error/comment_4_8c6ed5e459c5c66b77db446c6317114c._comment
deleted file mode 100644
index f3729d341..000000000
--- a/doc/bugs/hGetContents:_user_error/comment_4_8c6ed5e459c5c66b77db446c6317114c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 4"
- date="2013-07-02T16:41:51Z"
- content="""
-I wonder if this could be a glibc/kernel mismatch somehow. Any chance you can upgrade your kernel to something more recent? 
-"""]]
diff --git a/doc/bugs/hGetContents:_user_error/comment_5_f80bce48c3f96b0cd6892af43ee88a96._comment b/doc/bugs/hGetContents:_user_error/comment_5_f80bce48c3f96b0cd6892af43ee88a96._comment
deleted file mode 100644
index 0d5bf0f52..000000000
--- a/doc/bugs/hGetContents:_user_error/comment_5_f80bce48c3f96b0cd6892af43ee88a96._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://m-f-k.myopenid.com/"
- ip="84.138.125.150"
- subject="comment 5"
- date="2013-07-04T15:24:51Z"
- content="""
-No, I can't.  The kernel is handled by strato. :(
-"""]]
diff --git a/doc/bugs/hGetContents:_user_error/comment_6_69dc09e4ae726856dafbeec34170671c._comment b/doc/bugs/hGetContents:_user_error/comment_6_69dc09e4ae726856dafbeec34170671c._comment
deleted file mode 100644
index 956ae733c..000000000
--- a/doc/bugs/hGetContents:_user_error/comment_6_69dc09e4ae726856dafbeec34170671c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 6"
- date="2013-07-05T15:29:11Z"
- content="""
-Is there any chance I could get an account on this or a similar server, so I can investigate this in detail?
-"""]]
diff --git a/doc/bugs/hGetContents:_user_error/comment_7_3f66b03f773341fad94ec16b4f55edaa._comment b/doc/bugs/hGetContents:_user_error/comment_7_3f66b03f773341fad94ec16b4f55edaa._comment
deleted file mode 100644
index 2a64e57b1..000000000
--- a/doc/bugs/hGetContents:_user_error/comment_7_3f66b03f773341fad94ec16b4f55edaa._comment
+++ /dev/null
@@ -1,32 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.254.222"
- subject="comment 7"
- date="2013-07-07T02:48:05Z"
- content="""
-Thanks for providing me an account.
-
-I was able to reproduce the problem:
-
-<pre>
-$ git-annex-shell recvkey `pwd`
-git-annex-shell: fd:6: hGetContents: user error (Pattern match failure in do expression at libraries/base/GHC/Event/Thread.hs:90:3-10)
-</pre>
-
-Here's another one:
-
-<pre>
-$ git annex init
-
-git-annex: eventfd: unsupported operation (Function not implemented)
-failed
-init  
-git-annex: fd:10: hGetContents: user error (Pattern match failure in do expression at libraries/base/GHC/Event/Thread.hs:90:3-10)
-failed
-</pre>
-
-Aha! I found a more relevant bug in GHC's bug tracker. This has the same error message including the eventfd problem. <http://ghc.haskell.org/trac/ghc/ticket/7926>
-
-After some more digging around, it's definitely a kernel/glibc incompatability. I have filed a bug on glibc: <http://bugs.debian.org/715212>
-
-"""]]
diff --git a/doc/bugs/hGetContents:_user_error/comment_8_a697e2d36abfc999e65c9f587c0de56e._comment b/doc/bugs/hGetContents:_user_error/comment_8_a697e2d36abfc999e65c9f587c0de56e._comment
deleted file mode 100644
index d635ba6a7..000000000
--- a/doc/bugs/hGetContents:_user_error/comment_8_a697e2d36abfc999e65c9f587c0de56e._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.254.222"
- subject="workaround"
- date="2013-07-07T16:38:09Z"
- content="""
-This bug only affects programs built with the threaded haskell runtime. 
-
-git-annex can be built without the threaded runtime, by simply disabling the webapp. So a workaround is to pass the flag -f-WebApp to cabal when building git-annex with cabal.
-"""]]
diff --git a/doc/bugs/hGetContents:_user_error/comment_9_da7c5905a64bb6779970f9394155e629._comment b/doc/bugs/hGetContents:_user_error/comment_9_da7c5905a64bb6779970f9394155e629._comment
deleted file mode 100644
index 1a4e97744..000000000
--- a/doc/bugs/hGetContents:_user_error/comment_9_da7c5905a64bb6779970f9394155e629._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://openid.stackexchange.com/user/7891307e-4b76-4697-8e71-083669c26e9f"
- nickname="MichaelK"
- subject="comment 9"
- date="2013-07-07T16:54:34Z"
- content="""
-Thanks a lot for investigating this!
-
-(myopenid.com seems to be down, so I had to use another account.)
-"""]]
diff --git a/doc/bugs/haskell-dbus_problems_on_OSX___40__or_this_a_general_problem__41__.mdwn b/doc/bugs/haskell-dbus_problems_on_OSX___40__or_this_a_general_problem__41__.mdwn
deleted file mode 100644
index dfc9c4cef..000000000
--- a/doc/bugs/haskell-dbus_problems_on_OSX___40__or_this_a_general_problem__41__.mdwn
+++ /dev/null
@@ -1,113 +0,0 @@
-Building commit 805d50c69d40be97baa28735371778df63b5fed6
-
-<pre>
-x00:git-annex jtang$ cabal install
-Resolving dependencies...
-Configuring dbus-0.10...
-Building dbus-0.10...
-Preprocessing library dbus-0.10...
-[1 of 9] Compiling DBus.Types       ( lib/DBus/Types.hs, dist/build/DBus/Types.o )
-[2 of 9] Compiling DBus.Message     ( lib/DBus/Message.hs, dist/build/DBus/Message.o )
-[3 of 9] Compiling DBus.Wire        ( lib/DBus/Wire.hs, dist/build/DBus/Wire.o )
-[4 of 9] Compiling DBus.Address     ( lib/DBus/Address.hs, dist/build/DBus/Address.o )
-[5 of 9] Compiling DBus             ( lib/DBus.hs, dist/build/DBus.o )
-[6 of 9] Compiling DBus.Introspection ( lib/DBus/Introspection.hs, dist/build/DBus/Introspection.o )
-[7 of 9] Compiling DBus.Transport   ( lib/DBus/Transport.hs, dist/build/DBus/Transport.o )
-
-lib/DBus/Transport.hs:196:72: Not in scope: `getPeerCred'
-cabal: Error: some packages failed to install:
-dbus-0.10 failed during the building phase. The exception was:
-ExitFailure 1
-git-annex-3.20120721 depends on dbus-0.10 which failed to install.
-</pre>
-
-The above isn't a git-annex problem but a dbus problem, at first I thought I didn't have the network package installed, but did. I should probably report this problem to the haskell dbus author.
-
-On a slightly different note, based on the makefile DBUS is not enabled on OSX/BSD so I did not expect the cabal file to use dbus as well, I'm currently interested in poking at the webapp stuff ;)
-
-Although DBUS is available on OSX from macports I get the feeling that the haskell-dbus package might need some poking before it works properly.
-
-To continue, pulling, installing the dependancies (dbus is still boned) and building commit 6cecc26206c4a539999b04664136c6f785211a41
-
-<pre>
-[ 92 of 205] Compiling Utility.Url      ( Utility/Url.hs, tmp/Utility/Url.o )
-
-Utility/Url.hs:39:14: Not in scope: `parseURI'
-
-Utility/Url.hs:73:14: Not in scope: `parseURI'
-
-Utility/Url.hs:88:12: Not in scope: type constructor or class `URI'
-
-Utility/Url.hs:91:30: Not in scope: type constructor or class `URI'
-
-Utility/Url.hs:107:38: Not in scope: `parseURIReference'
-
-Utility/Url.hs:111:95: Not in scope: `relativeTo'
-make: *** [git-annex] Error 1
-</pre>
-
-Which then lead me to doing a "cabal install -f-DBus" which spits out the following when trying to link the binary
-
-<pre>
-[206 of 206] Compiling Main             ( git-annex.hs, dist/build/git-annex/git-annex-tmp/Main.o )
-Linking dist/build/git-annex/git-annex ...
-Undefined symbols for architecture x86_64:
-  "_addfds_kqueue", referenced from:
-      _s16v6_info in Kqueue.o
-  "_init_kqueue", referenced from:
-      _s16v3_info in Kqueue.o
-  "_waitchange_kqueue", referenced from:
-      _UtilityziKqueue_zdwa1_info in Kqueue.o
-ld: symbol(s) not found for architecture x86_64
-collect2: ld returned 1 exit status
-cabal: Error: some packages failed to install:
-git-annex-3.20120721 failed during the building phase. The exception was:
-ExitFailure 1
-</pre>
-
-I then just tried to build commit with 6cecc26206c4a539999b04664136c6f785211a41 (i have the needed dependancies installed), gives me this...
-
-<pre>
-x00:git-annex jtang$ make
-ghc -O2 -threaded -Wall -ignore-package monads-fd -ignore-package monads-tf -outputdir tmp -IUtility -DWITH_ASSISTANT -DWITH_S3 -DWITH_WEBAPP --make git-annex Utility/libdiskfree.o Utility/libmounts.o Utility/libkqueue.o
-
-Assistant/Threads/MountWatcher.hs:39:0:
-     warning: #warning Building without dbus support; will use mtab polling
-[ 92 of 205] Compiling Utility.Url      ( Utility/Url.hs, tmp/Utility/Url.o )
-
-Utility/Url.hs:98:65:
-    Couldn't match expected type `network-2.3.0.13:Network.URI.URI'
-                with actual type `URI'
-    In the second argument of `mkRequest', namely `u'
-    In the expression: mkRequest requesttype u :: Request_String
-    In an equation for `req':
-        req = mkRequest requesttype u :: Request_String
-make: *** [git-annex] Error 1
-</pre>
-
-The latest version of the network package in hackage is network-2.3.0.14 which I have installed, this might also be the reason why dbus is broken. removing network-2.3.0.14 at least makes it happy again.
-
-to remove the network-2.3.0.14 package
-
-<pre>
-ghc-pkg unregister network-2.3.0.14
-</pre>
-
-Hope the above isn't too random of bug/issue report.
-
-----
-
-going through <http://hackage.haskell.org/packages/archive/network/2.3.0.14/doc/html/Network-Socket.html> shows that getPeerCred is only available on systems where SO_PEERCRED is supported, *sigh* OSX isn't supported and thus haskell-dbus is broken. Apparently getpeerid is more portable but it isnt supported in the network package. It looks like dbus support on OSX isn't really going to work too well till haskell-dbus gets fixed on OSX (or BSD?)
-
-> Does OSX acually come with dbus by default, and can you
-> use something like `dbus-monitor` to see events when
-> plugging in removable drives? If so, this might be worth spending time
-> on.
-
->> No OSX does not come with dbus by default, the user must install it
-
-> 
-> Currently though, dbus is not supposed to be built on non-Linux systems.
-> (Well, it might work on Freebsd or something, but I've not tried it.)
-> I've fixed the cabal file to only enable it on Linux. [[done]] --[[Joey]] 
-
diff --git a/doc/bugs/host_with_rysnc_installed__44___not_recognized.mdwn b/doc/bugs/host_with_rysnc_installed__44___not_recognized.mdwn
deleted file mode 100644
index 4513ad9db..000000000
--- a/doc/bugs/host_with_rysnc_installed__44___not_recognized.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-What steps will reproduce the problem?
-Set up a remote server using ssh to a FreeNAS box
-
-What is the expected output? What do you see instead?
-Neither rsync nor git-annex are installed
-rsync is in the path, user with permissions is able to run it
-
-What version of git-annex are you using? On what operating system?
-4.20130227 OSX
-
-Please provide any additional information below.
-ssh keys were installed to allow login, when ssh-askpass was not found on osx version
-
-[[!meta title="webapp rsync probe command failed on FreeNAS box"]]
-[[!tag /design/assistant]]
-
-> [[done]]; based on the error message it's using csh and 
-> the assistant will now wrap its shell commands to work with csh.
-> --[[Joey]]
diff --git a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_1_3ff000eb3efde41426c7b086ae627dcf._comment b/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_1_3ff000eb3efde41426c7b086ae627dcf._comment
deleted file mode 100644
index 6d6fe2ac6..000000000
--- a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_1_3ff000eb3efde41426c7b086ae627dcf._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-18T15:55:05Z"
- content="""
-The git-annex webapp runs some shell commands on the remote it's setting up, in this case the FreeNAS box. It's difficult to do this entirely portably. I have tried to use only POSIX shell compatable commands, that should also work with embedded systems using busybox.
-
-You can try running the probe yourself at the prompt on the FreeNAS and see how it fails. The command run is:
-
-     echo loggedin;if which git-annex-shell; then echo git-annex-shell; fi;if which rsync; then echo rsync; fi
-"""]]
diff --git a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_2_34e592ab057df2df54e13d3f5cae64f0._comment b/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_2_34e592ab057df2df54e13d3f5cae64f0._comment
deleted file mode 100644
index 1616c7c84..000000000
--- a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_2_34e592ab057df2df54e13d3f5cae64f0._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmaygIuV4bIfp-U5IRH51FwKHq-i7_os0c"
- nickname="Mike"
- subject="comment 2"
- date="2013-03-25T02:20:05Z"
- content="""
-I copied and pasted your suggestion into a shell script, and this is what I got back:
-
-    #./test.sh
-
-    loggedin
-    /usr/local/bin/rsync
-    rsync
-"""]]
diff --git a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_3_05ffbae13d8f9b08315f40bb9b206f46._comment b/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_3_05ffbae13d8f9b08315f40bb9b206f46._comment
deleted file mode 100644
index 0dd7a7ee1..000000000
--- a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_3_05ffbae13d8f9b08315f40bb9b206f46._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-03-27T19:22:06Z"
- content="""
-Hmm, the message you got indicates it saw the \"loggedin\", but not the \"rsync\". 
-
-Actually, the command it runs is closer to this:
-
-<pre>
-echo git-annex-probe loggedin;if which git-annex-shell; then echo git-annex-probe git-annex-shell; fi;if which rsync; then echo git-annex-probe rsync; fi
-</pre>
-
-It's possible that ssh is somehow truncating or not running all of that. The ssh command
-would be something like this:
-
-<pre>
-ssh $HOSTNAME -n 'echo git-annex-probe loggedin;if which git-annex-shell; then echo git-annex-probe git-annex-shell; fi;if which rsync; then echo git-annex-probe rsync; fi'
-<pre>
-"""]]
diff --git a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_4_99d1f151263ca3433dd4afa8a928b1fe._comment b/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_4_99d1f151263ca3433dd4afa8a928b1fe._comment
deleted file mode 100644
index ed377251c..000000000
--- a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_4_99d1f151263ca3433dd4afa8a928b1fe._comment
+++ /dev/null
@@ -1,30 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmaygIuV4bIfp-U5IRH51FwKHq-i7_os0c"
- nickname="Mike"
- subject="comment 4"
- date="2013-03-29T04:03:44Z"
- content="""
-running the shell script directly:
-    > ./test.sh                             23:43:25
-
-	git-annex-probe loggedin
-
-	/usr/local/bin/rsync
-
-	git-annex-probe rsync
-
-Running your ssh command:
-
-	git-annex-probe loggedin
-
-	if: Expression Syntax.
-
-Running the shell script through ssh:
-	ssh $HOSTNAME ./test.sh                              23:54:39
-
-	git-annex-probe loggedin
-
-	/usr/local/bin/rsync
-
-	git-annex-probe rsync
-"""]]
diff --git a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_5_6ef1a377b0b4d3efeffdf9693d0b496b._comment b/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_5_6ef1a377b0b4d3efeffdf9693d0b496b._comment
deleted file mode 100644
index b62c8a9ec..000000000
--- a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_5_6ef1a377b0b4d3efeffdf9693d0b496b._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-03-29T16:47:28Z"
- content="""
-Sounds like it may not provide a POSIX shell for interactive use (based on the error message, I think it's csh), in which case this could work:
-
-    ssh $HOSTNAME -n 'sh -c \"echo git-annex-probe loggedin;if which git-annex-shell; then echo git-annex-probe git-annex-shell; fi;if which rsync; then echo git-annex-probe rsync; fi\"'
-
-
-"""]]
diff --git a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_6_d9e36828ad55f3181a1c650010f23d6b._comment b/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_6_d9e36828ad55f3181a1c650010f23d6b._comment
deleted file mode 100644
index 020408e5b..000000000
--- a/doc/bugs/host_with_rysnc_installed__44___not_recognized/comment_6_d9e36828ad55f3181a1c650010f23d6b._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmaygIuV4bIfp-U5IRH51FwKHq-i7_os0c"
- nickname="Mike"
- subject="comment 6"
- date="2013-03-31T03:45:45Z"
- content="""
-i ran your new command, and got this back:
-
-    git-annex-probe loggedin
-
-    /usr/local/bin/rsync
-
-    git-annex-probe rsync
-"""]]
diff --git a/doc/bugs/immediately_drops_files.mdwn b/doc/bugs/immediately_drops_files.mdwn
deleted file mode 100644
index b697c8284..000000000
--- a/doc/bugs/immediately_drops_files.mdwn
+++ /dev/null
@@ -1,224 +0,0 @@
-### Please describe the problem.
-When I `git annex get` files in a certain directory, they are got, then are dropped.
-When I do the same in a different directory, then the files there remains (as expected).
-
-`git annex fsck` also fails on these files, but after that the problem persists.
-
-I'm not really sure where to look to see why this is happening, especially why only on some directories.
-The filesystem (ext4) this is on has several GB free.
-
-Looking at the (broken) symlinks, they are strange:
-
-[[!format sh """
-git annex fsck IMG_4230.JPG > /dev/null
-ls -l IMG_4230.JPG
-lrwxrwxrwx 1 walter walter 207 Aug 13 12:14 IMG_4230.JPG -> ../../../.git/annex/objects/86/KF/SHA256E-s4209479--bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG/SHA256E-s4209479--bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG
-"""]]
-
-But then after getting it (and it being dropped somehow), the symlink is different (the number of ..s)
-
-[[!format sh """
-git annex get IMG_4230.JPG > /dev/null
-ls -l IMG_4230.JPG
-lrwxrwxrwx 1 walter walter 210 Aug 13 12:16 IMG_4230.JPG -> ../../../../.git/annex/objects/86/KF/SHA256E-s4209479--bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG/SHA256E-s4209479--bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG
-"""]]
-
-
-
-### What steps will reproduce the problem?
-
-I'm not really sure; I will test later whether this happens on other computers.
-
-### What version of git-annex are you using? On what operating system?
-    git-annex version: 4.20130812-gc590455
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-On ubuntu 12.10
-
-
---Walter
-
-### Please provide any additional information below.
-
-*output of git annex fsck*
-[[!format sh """
-git annex fsck 2013/08/01/IMG_4230.JPG
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","ls-files","--cached","-z","--","2013/08/01/IMG_4230.JPG"]
-[2013-08-13 12:01:25 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","check-attr","-z","--stdin","annex.backend","annex.numcopies","--"]
-fsck 2013/08/01/IMG_4230.JPG [2013-08-13 12:01:25 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","cat-file","--batch"]
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"]
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..3afd101dade8be4e1ed7ac48fdf4173274d3ecd7","--oneline","-n1"]
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"]
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"]
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"]
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"]
-[2013-08-13 12:01:25 NZST] read: git ["config","--null","--list"]
-ok
-[2013-08-13 12:01:25 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-w","--stdin-paths","--no-filters"]
-[2013-08-13 12:01:25 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"]
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"]
-(Recording state in git...)
-[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","write-tree"]
-[2013-08-13 12:01:25 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit-tree","78aca82f86ffb91bc841a3978f410e55aa6e0efe","-p","refs/heads/git-annex"]
-[2013-08-13 12:01:25 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-ref","refs/heads/git-annex","14908fedbd44917815dd013125b69def1f7f8f7c"]
-
-"""]]
-
-*output of git annex get* (output taken from daemon.log, as output from command does not include the dropping part)
-[[!format sh """
-git annex get 2013/08/01/IMG_4230.JPG
-[2013-08-13 12:03:46 NZST] TransferWatcher: transfer starting: Download UUID "e6bb2ef2-b2b5-11e1-bd1b-3fd40e5e767d" 2013/08/01/IMG_4230.JPG Nothing
-[2013-08-13 12:03:46 NZST] TransferWatcher: transfer starting: Download UUID "e6bb2ef2-b2b5-11e1-bd1b-3fd40e5e767d" 2013/08/01/IMG_4230.JPG Nothing
-[2013-08-13 12:03:46 NZST] TransferWatcher: transfer finishing: Transfer {transferDirection = Download, transferUUID = UUID "e6bb2ef2-b2b5-11e1-bd1b-3fd40e5e767d", transferKey = Key {keyName = "bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG", keyBackendName = "SHA256E", keySize = Just 4209479, keyMtime = Nothing}}
-[2013-08-13 12:03:46 NZST] Watcher: add symlink 01/IMG_4230.JPG
-[2013-08-13 12:03:46 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-t","blob","-w","--stdin","--no-filters"]
-[2013-08-13 12:03:46 NZST] Committer: committing 1 changes
-[2013-08-13 12:03:46 NZST] Committer: Committing changes to git
-[2013-08-13 12:03:46 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"]
-[2013-08-13 12:03:46 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"]
-[2013-08-13 12:03:46 NZST] Pusher: Synok
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-drop 01/IMG_4230.JPG cing with Adata, b(checking cloud...) itbucket 
-[2013-08-13 12:03:46 NZST] Committer: dropped 01/IMG_4230.JPG (from here) (copies now 4) : file renamed
-[2013-08-13 12:03:46 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-w","--stdin-paths","--no-filters"]
-[2013-08-13 12:03:46 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","write-tree"]
-[2013-08-13 12:03:47 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit-tree","f288bfce8d133cc0ce00b65d48ca726809da34e6","-p","refs/heads/git-annex"]
-[2013-08-13 12:03:47 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-ref","refs/heads/git-annex","5a188246bda51207d12adf86c6d87568ca7076d7"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","symbolic-ref","HEAD"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","refs/heads/master"]
-[2013-08-13 12:03:47 NZST] Pusher: pushing to [Remote { name ="Adata" },Remote { name ="bitbucket" }]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"]
-[2013-08-13 12:03:47 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","branch","-f","synced/master"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-13 12:03:47 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master:synced/master"]
-[2013-08-13 12:03:47 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","Adata","git-annex:synced/git-annex","master:synced/master"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5a188246bda51207d12adf86c6d87568ca7076d7","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..3afd101dade8be4e1ed7ac48fdf4173274d3ecd7","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5a188246bda51207d12adf86c6d87568ca7076d7","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..3afd101dade8be4e1ed7ac48fdf4173274d3ecd7","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"]
-[2013-08-13 12:03:47 NZST] Watcher: add symlink 01/IMG_4230.JPG
-[2013-08-13 12:03:47 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-t","blob","-w","--stdin","--no-filters"]
-To /media/walter/327D522A6727FE79/Pictures
-   3afd101..5a18824  git-annex -> synced/git-annex
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"]
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","Adata","git-annex:synced/git-annex","master"]
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5a188246bda51207d12adf86c6d87568ca7076d7","--oneline","-n1"]
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"]
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"]
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"]
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"]
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..3afd101dade8be4e1ed7ac48fdf4173274d3ecd7","--oneline","-n1"]
-[2013-08-13 12:03:48 NZST] Committer: committing 1 changes
-[2013-08-13 12:03:48 NZST] Committer: Committing changes to git
-[2013-08-13 12:03:48 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"]
-[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"]
-To git@bitbucket.org:waltersom/Pictures.git
-   3afd101..5a18824  git-annex -> synced/git-annex
-[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"]
-[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master"]
-[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5a188246bda51207d12adf86c6d87568ca7076d7","--oneline","-n1"]
-[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"]
-[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"]
-[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"]
-[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"]
-[2013-08-13 12:03:58 NZST] Pusher: Syncing with Adata, bitbucket 
-[2013-08-13 12:03:58 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","symbolic-ref","HEAD"]
-[2013-08-13 12:03:58 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","refs/heads/master"]
-[2013-08-13 12:03:58 NZST] Pusher: pushing to [Remote { name ="Adata" },Remote { name ="bitbucket" }]
-[2013-08-13 12:03:58 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","branch","-f","synced/master"]
-[2013-08-13 12:03:58 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","Adata","git-annex:synced/git-annex","master:synced/master"]
-[2013-08-13 12:03:58 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master:synced/master"]
-Everything up-to-date
-[2013-08-13 12:03:58 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","Adata","git-annex:synced/git-annex","master"]
-Everything up-to-date
-[2013-08-13 12:04:02 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master"]
-
-"""
-]]
-
-
-
-I tried removing the USB drive I had plugged in, and was able to get the file from S3, and it wasn't dropped.
-However, checking the logs, I see that it did try to drop the file, but was unable to verify numcopies, so gives up.
-Also odd, is that it doesn't suggest making the USB drive available, but `git annex whereis` knows that the drive does have it. Also, annex.numcopies is 1, and it got it from S3, so why can't it drop it on the computer?
-Or, why does it say that it needs two copies? `git config annex.numcopies` gives 1.
-
-[[!format sh """
-[2013-08-13 16:52:08 NZST] TransferWatcher: transfer starting: Download UUID "be992080-b1db-11e1-8f79-1b10bb4092ef" 01/IMG_4230.JPG Nothing
-[2013-08-13 16:54:06 NZST] TransferWatcher: transfer starting: Download UUID "be992080-b1db-11e1-8f79-1b10bb4092ef" 01/IMG_4230.JPG Just 65504
-[...]
-[2013-08-13 16:54:06 NZST] TransferWatcher: transfer starting: Download UUID "be992080-b1db-11e1-8f79-1b10bb4092ef" 01/IMG_4230.JPG Just 4192256
-[2013-08-13 16:54:06 NZST] TransferWatcher: transfer finishing: Transfer {transferDirection = Download, transferUUID = UUID "be992080-b1db-11e1-8f79-1b10bb4092ef", transferKey = Key {keyName = "bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG", keyBackendName = "SHA256E", keySize = Just 4209479, keyMtime = Nothing}}
-[2013-08-13 16:54:06 NZST] Watcher: add symlink 01/IMG_4230.JPG
-[2013-08-13 16:54:06 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-t","blob","-w","--stdin","--no-filters"]
-[2013-08-13 16:54:06 NZST] Committer: committing 1 changes
-[2013-08-13 16:54:06 NZST] Committer: Committing changes to git
-[2013-08-13 16:54:06 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"]
-[2013-08-13 16:54:06 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"]
-[2013-08-13 16:54:06 
-  Could only verify the existence of 1 out of 2 necessary copies
-
-  Try making some of these repositories available:
-  	416aa28e-b1d4-11e1-9539-c39b14a3f7d2 -- timeline laptop
-   	f42d30a0-b1d2-11e1-8b32-3bdd169e3280 -- my desktop
-
-  (Use --force to override this check, or adjust annex.numcopies.)
-failed
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-drop 01/IMG_4230.JPG NZST] Pusher:(checking cloud...)  Syncing with bitbucket 
-(unsafe) [2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","symbolic-ref","HEAD"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","refs/heads/master"]
-[2013-08-13 16:54:07 NZST] Pusher: pushing to [Remote { name ="bitbucket" }]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"]
-[2013-08-13 16:54:07 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","branch","-f","synced/master"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-13 16:54:07 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master:synced/master"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..7b6b1c6c479a13f9d4ece135bdf3ba31bc484b31","--oneline","-n1"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..11a0c19d7c79f3e574b81295782ab2820caea232","--oneline","-n1"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5ebb3e46b8fc109c2966ceccdd716f469d94fcad","--oneline","-n1"]
-[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-To git@bitbucket.org:waltersom/Pictures.git
-   5ebb3e4..7b6b1c6  git-annex -> synced/git-annex
-[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"]
-[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master"]
-[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"]
-[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..7b6b1c6c479a13f9d4ece135bdf3ba31bc484b31","--oneline","-n1"]
-[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"]
-[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"]
-[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"]
-[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..11a0c19d7c79f3e574b81295782ab2820caea232","--oneline","-n1"]
-[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"]
-"""]]
-
-[[done]]
diff --git a/doc/bugs/immediately_drops_files/comment_1_9ef6e694ef8a8eee7a42f88554475db7._comment b/doc/bugs/immediately_drops_files/comment_1_9ef6e694ef8a8eee7a42f88554475db7._comment
deleted file mode 100644
index 9d630e385..000000000
--- a/doc/bugs/immediately_drops_files/comment_1_9ef6e694ef8a8eee7a42f88554475db7._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 1"
- date="2013-08-24T16:41:04Z"
- content="""
-You are running the git annex assistant, which takes care of getting and dropping files as it's configured to do, and you are then going in and manually running `git annex get`. If the assistant sees a file's content has appeared, and that file is in a directory that it has been configured to not want the content of file in (the `archive` directory by default), it will immediately try to drop it.
-
-The only thing I don't understand is why the number of `..` in the symlink would change.
-"""]]
diff --git a/doc/bugs/immediately_drops_files/comment_2_76e4f8b73ab60b2540dd2a3e5379791d._comment b/doc/bugs/immediately_drops_files/comment_2_76e4f8b73ab60b2540dd2a3e5379791d._comment
deleted file mode 100644
index 274090c63..000000000
--- a/doc/bugs/immediately_drops_files/comment_2_76e4f8b73ab60b2540dd2a3e5379791d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 2"
- date="2013-08-24T16:41:47Z"
- content="""
-BTW if you don't want the assistant to automatically get and drop files in your repository, you can edit the repository in the webapp and select \"manual mode\".
-"""]]
diff --git a/doc/bugs/immediately_drops_files/comment_3_788db083f5ba2e5589c3b952203ec954._comment b/doc/bugs/immediately_drops_files/comment_3_788db083f5ba2e5589c3b952203ec954._comment
deleted file mode 100644
index 9253caa1a..000000000
--- a/doc/bugs/immediately_drops_files/comment_3_788db083f5ba2e5589c3b952203ec954._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ"
- nickname="Walter"
- subject="comment 3"
- date="2013-08-24T21:59:12Z"
- content="""
-I have all of my repositories set to either manual (all the computers), or full backup (the usb drive and s3).
-So, this is happening in a manual repository.
-
-
-Also, I still don't understand why it would be confused over the annex.numcopies setting (why does it claim it needs 2 copies, when numcopies is 1?)
-
-I just tested between desktop and laptop. File is also present in s3.
-
-File on desktop. Copy to laptop --> desktop drops (why? both are set to manual, and both have the other set as manual as well)
-
-Get on desktop. Works, it gets it from laptop. But then, desktop makes laptop drop it (why? again, both are manual repositories)
-
-
-
-"""]]
diff --git a/doc/bugs/immediately_drops_files/comment_4_425b79865eb77d69d0b7a71a14639f81._comment b/doc/bugs/immediately_drops_files/comment_4_425b79865eb77d69d0b7a71a14639f81._comment
deleted file mode 100644
index aacf2f2dc..000000000
--- a/doc/bugs/immediately_drops_files/comment_4_425b79865eb77d69d0b7a71a14639f81._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.2.134"
- subject="comment 4"
- date="2013-09-13T19:27:51Z"
- content="""
-> both are set to manual, and both have the other set as manual as well
-
-I'm not sure what you mean by that. Do you mean that when you run git annex vicfg, it is in group manual?
-"""]]
diff --git a/doc/bugs/immediately_drops_files/comment_5_7c9f660b6bcec31827a44a650e9d4622._comment b/doc/bugs/immediately_drops_files/comment_5_7c9f660b6bcec31827a44a650e9d4622._comment
deleted file mode 100644
index bb2569893..000000000
--- a/doc/bugs/immediately_drops_files/comment_5_7c9f660b6bcec31827a44a650e9d4622._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ"
- nickname="Walter"
- subject="comment 5"
- date="2013-09-13T21:58:30Z"
- content="""
-I had checked in the webapps, and they were all set to manual.
-
-Looking in `git annex vicfg`, the groups are set to manual, and the content is set to standard.
-"""]]
diff --git a/doc/bugs/importfeed_fails__44___bad_feed_content.mdwn b/doc/bugs/importfeed_fails__44___bad_feed_content.mdwn
deleted file mode 100644
index 4ee312be0..000000000
--- a/doc/bugs/importfeed_fails__44___bad_feed_content.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-### Please describe the problem.
-
-I just added a new podcast to my feeds list and it is complaining of "bad feed content" when trying to import.
-
-### What steps will reproduce the problem?
-
-1. git-annex importfeed --fast http://redecentralize.org/podcast/feed.rss
-3. see the sad error "warning: bad feed content"
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version: 4.20130827
-
-### Please provide any additional information below.
-
-[[!format sh """
-greg@x200s:~/annex/Podcasts$ git-annex importfeed --fast http://redecentralize.org/podcast/feed.rss
-(checking known urls...)
-importfeed http://redecentralize.org/podcast/feed.rss 
---2013-09-09 15:05:17--  http://redecentralize.org/podcast/feed.rss
-Resolving redecentralize.org (redecentralize.org)... 204.232.175.78
-Connecting to redecentralize.org (redecentralize.org)|204.232.175.78|:80... connected.
-HTTP request sent, awaiting response... 200 OK
-Length: 4331 (4.2K) [text/xml]
-Saving to: ‘/tmp/feed12649’
-
-100%[==============================================================>] 4,331       --.-K/s   in 0.08s   
-
-2013-09-09 15:05:17 (56.0 KB/s) - ‘/tmp/feed12649’ saved [4331/4331]
-
-
-  warning: bad feed content
-ok
-"""]]
-
-> upstream bug <https://github.com/sof/feed/issues/5> ; [[done]] --[[Joey]]  
diff --git a/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast.mdwn b/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast.mdwn
deleted file mode 100644
index 0d6bcb05c..000000000
--- a/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast.mdwn
+++ /dev/null
@@ -1,77 +0,0 @@
-### Please describe the problem.
-
-importfeed responds with "failed" when using the option --lazy for specific podcast and no symbolic links get created. However when I don't use the --fast option the podcast enclosures do download and links get created as expected.
-
-### What steps will reproduce the problem?
-
-git-annex importfeed --fast http://schoolsucksproject.com/category/podcast/feed/
-
-### What version of git-annex are you using? On what operating system?
-
-    Ubuntu
-    git-annex version: 4.20130802-g1452ac3
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-### Please provide any additional information below.
-
-    git-annex importfeed --fast http://schoolsucksproject.com/category/podcast/feed/
-    (checking known urls...)
-    (Recording state in git...)
-    importfeed http://schoolsucksproject.com/category/podcast/feed/ 
-    --2013-09-28 00:27:25--  http://schoolsucksproject.com/category/podcast/feed/
-    Resolving schoolsucksproject.com (schoolsucksproject.com)... 108.162.199.17, 108.162.198.17
-    Connecting to schoolsucksproject.com (schoolsucksproject.com)|108.162.199.17|:80... connected.
-    HTTP request sent, awaiting response... 200 OK
-    Length: unspecified [text/xml]
-    Saving to: `/tmp/feed16555'
-
-    2013-09-28 00:27:28 (217 KB/s) - `/tmp/feed16555' saved [423071]
-
-    addurl School_Sucks_Project___Podcasts/238f__Presence_and_Productivity__6___Tools_For_A_Freed_Mind_and_A_Voluntary_Life_mp3 
-      unable to access url: http://schoolsucks.podomatic.com/enclosure/2013-09-21T08_21_33-07_00.mp3
-    failed
-    addurl School_Sucks_Project___Podcasts/238e__Presence_and_Productivity__5___Habit_Change_mp3 
-      unable to access url: http://schoolsucks.podomatic.com/enclosure/2013-09-18T20_40_40-07_00.mp3
-    failed
-    addurl School_Sucks_Project___Podcasts/238d__Presence_and_Productivity__4___Next_Actions__Projects__and_Procrastination_mp3 
-      unable to access url: http://schoolsucks.podomatic.com/enclosure/2013-09-16T10_10_06-07_00.mp3
-    failed 
-    ...
-
-> (There is no --lazy option. You seem to mean --fast.)
-> 
-> This fine web server rejects the User-Agent used by curl:
-
-<pre> 
-joey@darkstar:~>curl http://schoolsucks.podomatic.com/enclosure/2013-09-18T20_40_40-07_00.mp3
-Forbidden
-joey@darkstar:~>wget http://schoolsucks.podomatic.com/enclosure/2013-09-18T20_40_40-07_00.mp3
---2013-09-28 11:18:36--  http://schoolsucks.podomatic.com/enclosure/2013-09-18T20_40_40-07_00.mp3
-Resolving schoolsucks.podomatic.com (schoolsucks.podomatic.com)... 38.99.42.46, 38.110.155.212
-Connecting to schoolsucks.podomatic.com (schoolsucks.podomatic.com)|38.99.42.46|:80... connected.
-HTTP request sent, awaiting response... 200 OK
-<pre>
-
-> git-annex always uses curl for checking file sizes. So the workaround
-> is to use `git annex addurl --relaxed` on this url, which will skip
-> the size check. However, if you only had curl installed, `git-annex get`
-> would again try to use curl to get the file, and would still fail.
-> It only happens to successfully download because git-annex chose
-> to use wget and this site has apparently forgotten to block that.
-> 
-> I don't know if it makes sense for git-annex to vary the user-agent
-> to get around such (incredibly stupid) blocking. It could retry
-> with a random user-agent, but that could be construed as abusive
-> behavior; this site has asked us to go away. The only choices
-> that seem really defensible would be to add a --user-agent
-> switch, and/or to make git-annex set a default user agent header
-> of "git-annex", rather than relying on the curl/wget defaults.
-> --[[Joey]] 
-
-> I've [[done]] what's discussed above, and verified it fixes
-> behavior for this specific server too.
-> --[[Joey]] 
diff --git a/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast/comment_1_4ccfabbaf75e139b32f6fa6f7bc6a7fe._comment b/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast/comment_1_4ccfabbaf75e139b32f6fa6f7bc6a7fe._comment
deleted file mode 100644
index 26430ec91..000000000
--- a/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast/comment_1_4ccfabbaf75e139b32f6fa6f7bc6a7fe._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="Remy"
- ip="82.94.186.146"
- subject="Thank you very much"
- date="2013-09-30T08:49:33Z"
- content="""
-Thank you very much for looking into this! This issue was holding me back from using git-annex as my podcatcher. Hope it helps somebody else as well. 
-"""]]
diff --git a/doc/bugs/importfeed_should_allow_pubdate_in_the_template.mdwn b/doc/bugs/importfeed_should_allow_pubdate_in_the_template.mdwn
deleted file mode 100644
index 44d25b02d..000000000
--- a/doc/bugs/importfeed_should_allow_pubdate_in_the_template.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-importfeed is a great feature, but it doesn't allow templating the filename with the publish date.
-
-I would suggest adding pubdate option, which would fix this problem.
-
-> duplicate of [[todo/importfeed: allow ${itemdate} with --template]] [[done]] --[[Joey]] 
diff --git a/doc/bugs/importfeed_uses___34____95__foo__34___as_extension.mdwn b/doc/bugs/importfeed_uses___34____95__foo__34___as_extension.mdwn
deleted file mode 100644
index 5f09e2636..000000000
--- a/doc/bugs/importfeed_uses___34____95__foo__34___as_extension.mdwn
+++ /dev/null
@@ -1,17 +0,0 @@
-### Please describe the problem.
-When running importfeed on gitminutes <http://feeds.gitminutes.com/gitminutes-podcast> git-annex interprets the extension as "_mp3" rather than ".mp3" which means that renaming is needed for various audio players to accept the files.
-
-### What steps will reproduce the problem?
-git annex importfeed http://feeds.gitminutes.com/gitminutes-podcast --fast
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20130802
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-
-on Debian Sid
-
-> Already fixed in git. [[done]] --[[Joey]]
diff --git a/doc/bugs/internal_server_error:_unknown_UUID_on_webapp.mdwn b/doc/bugs/internal_server_error:_unknown_UUID_on_webapp.mdwn
deleted file mode 100644
index 307eed308..000000000
--- a/doc/bugs/internal_server_error:_unknown_UUID_on_webapp.mdwn
+++ /dev/null
@@ -1,147 +0,0 @@
-### Please describe the problem.
-
-I am having trouble using the webapp with a setup I did on the commandline that was working fine.
-
-I have two machines: one, a server called `marcos`, is available on the internetz and I cloned a repo from there into `markov`, a workstation that is hidden behind a NAT connexion (so I can't add it as a remote).
-
-It seems that because the remote is not locally available as a git remote, the webapp is freaking out because it doesn't recognize `markov` as a proper remote.
-
-### What steps will reproduce the problem?
-
-1. setup git annex locally (on `marcos`) in a repository (probably `git annex init; git annex direct; git annex add .` i somewhat followed [[tips/Git_annex_and_Calibre/]])
-2. `git clone` that repo on a remote, unaccessible (NAT'd) server (`markov`)
-3. start doing some git annex get, get tired, run the web app on `markov`
-4. let that run over there, go back to `marcos`
-5. be curious about what is going on on `markov`, run the webapp and enter the path to the repository created in step one when prompted (it's the first time i run the webapp)
-6. it starts up fine, but doesn't seem to detect `markov`, marking transfers as going to the remote named `unknown`
-7. click on the `unknown` link, crash
-8. go back to the dashboard, crash
-
-From there on, the webapp is pretty much crashed, starting it from scratch asks me if i want to create a git annex repo.
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130921-gd4739c5 compiled and installed by hand on debian wheezy.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# Here's everything that has been logged by the git-annex assistant, as well as by programs it has run.
-
-[2013-11-04 22:42:50 EST] main: starting assistant version 4.20130921-gd4739c5
-(merging synced/git-annex into git-annex...)
-(Recording state in git...)
-
-  No known network monitor available through dbus; falling back to polling
-Already up-to-date.
-
-(scanning...) [2013-11-04 22:42:50 EST] Watcher: Performing startup scan
-04/Nov/2013:22:42:51 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:42:52 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:42:52 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-(Recording state in git...)
-(Recording state in git...)
-(started...) 
-
-  metadata.db still has writers, not adding
-[2013-11-04 22:42:59 EST] Committer: Adding cover.jpg Ars Techn..ibre.epub Cyberpres..ibre.epub cover.jpg cover.jpg Ars Techn..ibre.epub cover.jpg Democracy..ibre.epub cover.jpg and 11 other files
-add Calibre/Ars Technica [dim., 03 nov. 2013] (645)/cover.jpg (checksum...) ok
-add Calibre/Ars Technica [dim., 03 nov. 2013] (645)/Ars Technica [dim., 03 nov. 2013] - Calibre.epub (checksum...) ok
-add Calibre/Cyberpresse [lun., 04 nov. 2013] (647)/Cyberpresse [lun., 04 nov. 2013] - Calibre.epub (checksum...) ok
-add Calibre/Cyberpresse [lun., 04 nov. 2013] (647)/cover.jpg (checksum...) ok
-add Calibre/Ars Technica [sam., 02 nov. 2013] (642)/cover.jpg (checksum...) ok
-add Calibre/Ars Technica [sam., 02 nov. 2013] (642)/Ars Technica [sam., 02 nov. 2013] - Calibre.epub (checksum...) ok
-add Calibre/Democracy now! [lun., 04 nov. 2013] (649)/cover.jpg (checksum...) ok
-add Calibre/Democracy now! [lun., 04 nov. 2013] (649)/Democracy now! [lun., 04 nov. 2013] - Calibre.epub (checksum...) ok
-add Calibre/xkcd [lun., 04 nov. 2013] (646)/cover.jpg (checksum...) ok
-add Calibre/xkcd [lun., 04 nov. 2013] (646)/xkcd [lun., 04 nov. 2013] - Calibre.epub (checksum...) ok
-add Calibre/Cyberpresse [dim., 03 nov. 2013] (644)/cover.jpg (checksum...) ok
-add Calibre/Cyberpresse [dim., 03 nov. 2013] (644)/Cyberpresse [dim., 03 nov. 2013] - Calibre.epub (checksum...) ok
-add Calibre/Le Devoir [sam., 02 nov., 2013] (640)/cover.jpg (checksum...) ok
-add Calibre/Le Devoir [sam., 02 nov., 2013] (640)/Le Devoir [sam., 02 nov., 2013] - Calibre.epub (checksum...) ok
-add Calibre/Le Devoir [lun., 04 nov., 2013] (648)/cover.jpg (checksum...) ok
-add Calibre/Le Devoir [lun., 04 nov., 2013] (648)/Le Devoir [lun., 04 nov., 2013] - Calibre.epub (checksum...) ok
-add Calibre/Cyberpresse [sam., 02 nov. 2013] (641)/cover.jpg (checksum...) ok
-add Calibre/Cyberpresse [sam., 02 nov. 2013] (641)/Cyberpresse [sam., 02 nov. 2013] - Calibre.epub (checksum...) ok
-add Calibre/Le Devoir [dim., 03 nov., 2013] (643)/cover.jpg (checksum...) ok
-add Calibre/Le Devoir [dim., 03 nov., 2013] (643)/Le Devoir [dim., 03 nov., 2013] - Calibre.epub (checksum...) [2013-11-04 22:43:01 EST] Committer: Committing changes to git
-ok
-(Recording state in git...)
-(Recording state in git...)
-04/Nov/2013:22:43:51 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:47:24 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:47:24 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:47:24 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:52:29 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:52:30 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:52:30 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:56:47 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-[2013-11-04 22:57:08 EST] Committer: Adding metadata.db-journal
-add metadata.db-journal (checksum...) [2013-11-04 22:57:08 EST] Committer: Committing changes to git
-[2013-11-04 22:57:09 EST] Committer: Adding metadata.db-journal metadata.db
-ok
-(Recording state in git...)
-(Recording state in git...)
-add metadata.db (checksum...) [2013-11-04 22:57:09 EST] Committer: Committing changes to git
-ok
-(Recording state in git...)
-(Recording state in git...)
-04/Nov/2013:22:57:12 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:57:15 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:57:18 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-04/Nov/2013:22:57:20 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5)
-"""]]
-
-> I wonder if this couldn't be related to [[cannot determine uuid for origin]], although in this case the remote is just not added to `.git/config`. --[[anarcat]]
-
-> This was fixed in commit 44e1524be53373ddbf28d643bedf5455433c2b2e
-> on Sep 29th. You should update. [[done]]
-> 
-> (It also sounds like your repository on markov is for some reason not
-> able to push its git repository to marcos. You might need to fix
-> something in your setup to get syncing working) --[[Joey]]
-> 
-> > Humm.. Weird. Upgrading fixes the crash, but `marcos` still sees only
-> > one repository. It sees some syncs going on from `unknown`, and when
-> > I click on that `unknown` link, I get to edit that repository, and
-> > it sees it as `here`. So I am not sure I understand what is going 
-> > on here.
-> >
-> > (As for the repo on `markov`, it does sync properly:
-> > 
-> >     anarcat@desktop008:books$ git annex sync
-> >     commit
-> >     ok
-> >     pull origin
-> >     From anarc.at:/srv/books
-> >        3b4fa7b..c35b13e  git-annex  -> origin/git-annex
-> >     ok
-> > 
-> > Or rather - it doesn't fail. But it doesn't push!
-> > 
-> >     anarcat@desktop008:books$ git push
-> >     Everything up-to-date
-> > 
-> > Note that git on `marcos` is the 1.8.4 backport for some reason.
-> > I know that branch tracking changed with that release, maybe 
-> > that's the problem? --[[anarcat]])
-> > 
-> > > So yep, I confirm that even in 4.20131105-g8efdc1a, the webapp
-> > > doesn't find the `markov` remote properly, even though
-> > > `git annex status` can:
-> > > 
-> > >     $ git annex status
-> > >     repository mode: direct
-> > >     trusted repositories: 0
-> > >     semitrusted repositories: 3
-> > >             00000000-0000-0000-0000-000000000001 -- web
-> > >             a75cbbf7-e055-423e-b375-443e0552c9e2 -- here (anarcat@marcos:/srv/books)
-> > >             aa500f29-42d9-4777-ae02-4a2c3d47db44 -- anarcat@markov:~/books
-> > > 
-> > > I see transfers happening, but they go to "unknown". The link is:
-> > > 
-> > > http://127.0.0.1:56577/config/repository/edit/UUID%20%22aa500f29-42d9-4777-ae02-4a2c3d47db44%22?auth=...
-> > > 
-> > > -- [[anarcat]]
-> > > 
-> > > > I have filed this as a separate bug to close the discussion properly here, sorry for the noise. :) see [[bugs/remote_not_showing_up_in_webapp]] --[[anarcat]]
diff --git a/doc/bugs/internal_server_error_creating_repo_on_ssh_server.mdwn b/doc/bugs/internal_server_error_creating_repo_on_ssh_server.mdwn
deleted file mode 100644
index 7235757bf..000000000
--- a/doc/bugs/internal_server_error_creating_repo_on_ssh_server.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-What steps will reproduce the problem?
-
-I downloaded the os x assistant today.
-
-I'd previously installed it but hadn't linked it to another repo.
-
-I tried to create a remote repo on an ssh server using the assistant.
-
-What is the expected output? What do you see instead?
-
-Creating a remote repo or giving an understandable error message.
-
-What version of git-annex are you using? On what operating system?
-
-3.20121212
-OS X 10.8.2 (Mountain Lion)
-
-The remote machine is running debian stable.
-
-Please provide any additional information below.
-
-Internal Server Error
-user error (gpg ["--quiet","--trust-model","always","--gen-random","--armor","1","512"] exited 127)
-git-annex version 3.20121212
-
-> [[done]], see comments --[[Joey]] 
diff --git a/doc/bugs/internal_server_error_creating_repo_on_ssh_server/comment_1_4a2c9338d5c779496049d78e29cf5cbd._comment b/doc/bugs/internal_server_error_creating_repo_on_ssh_server/comment_1_4a2c9338d5c779496049d78e29cf5cbd._comment
deleted file mode 100644
index 04b25ecc2..000000000
--- a/doc/bugs/internal_server_error_creating_repo_on_ssh_server/comment_1_4a2c9338d5c779496049d78e29cf5cbd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlcxKZHglATIiJXD7jcxfYhkhgeFmcVFqE"
- nickname="James"
- subject="ignore"
- date="2013-01-24T16:33:27Z"
- content="""
-I had downloaded and installed the new version of git annex but not restarted the assistant. I rebooting my computer and started the new version (3.20130114) of the assistant and I was able to create a repo.
-"""]]
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option.mdwn b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option.mdwn
deleted file mode 100644
index d0ffaf083..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-I get this same internal server error when doing the encrypted rsync repo option:
-
-    user error (gpg ["--quiet","--trust-model","always","--gen-random","--armor","1","512"] exited 2)
-
-### What steps will reproduce the problem?
-
-1. click Configuration > repositories
-2. click Remote Server
-3. On "Ready to add remote server" screen click Use an encrypted repo
-
-Error pops up:
-
-Internal Server Error
-
-    user error (gpg ["--quiet","--trust-model","always","--gen-random","--armor","1","512"] exited 2)
-
-### What version of git-annex are you using? On what operating system?
-Currently using the file found here:
-
-http://downloads.kitenet.net/git-annex/OSX/current/10.7.5_Lion/
-
-Using MacOS 10.7.5 Lion
-
-[[!meta title="OSX gpg.conf auto-key-locate cert line breaks gpg in git-annex app"]]
-
-> [[done]]; all OSX builds now include a recent gpg that supports 
-> this option. --[[Joey]] 
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_1_14a2f775f43a86129ce3649a06f8ba0b._comment b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_1_14a2f775f43a86129ce3649a06f8ba0b._comment
deleted file mode 100644
index fd59b3e05..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_1_14a2f775f43a86129ce3649a06f8ba0b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 1"
- date="2013-06-30T20:36:02Z"
- content="""
-There should be a more useful error message in the repository's debug.log, please post it.
-"""]]
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_2_7b277320fcffd8d03e0d3d31398eb571._comment b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_2_7b277320fcffd8d03e0d3d31398eb571._comment
deleted file mode 100644
index a99040871..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_2_7b277320fcffd8d03e0d3d31398eb571._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlpOeCs7zZLR-PBGPxUgjWlg7bwAAzQZyk"
- nickname="Seth"
- subject="comment 2"
- date="2013-06-30T21:32:54Z"
- content="""
-Here it is, with personal info redacted:
-
-(Recording state in git...)
-(encryption setup) gpg: /Users/bokeh/.gnupg/gpg.conf:233: invalid auto-key-locate list
-[2013-06-30 17:31:18 EDT] read: ssh-keygen [\"-F\",\"XXXXXXXXXXXX.com\"]
-[2013-06-30 17:31:18 EDT] read: ssh [\"-oNumberOfPasswordPrompts=0\",\"-n\",\"-p\",\"22\",\"XXXXXXXXXXXX@XXXXXXXXXXXX.com\",\"sh -c 'echo git-annex-probe loggedin;if which git-annex-shell; then echo git-annex-probe git-annex-shell; fi;if which rsync; then echo git-annex-probe rsync; fi;if which ~/.ssh/git-annex-shell; then echo git-annex-probe ~/.ssh/git-annex-shell; fi'\"]
-[2013-06-30 17:31:23 EDT] chat: ssh [\"XXXXXXXXXXXX@XXXXXXXXXXXX.com\",\"sh -c 'mkdir -p '\\"'\\"'annex'\\"'\\"'&&cd '\\"'\\"'annex'\\"'\\"''\"]
-(encryption setup) [2013-06-30 17:31:25 EDT] read: gpg [\"--quiet\",\"--trust-model\",\"always\",\"--gen-random\",\"--armor\",\"1\",\"512\"]
-gpg: /Users/bokeh/.gnupg/gpg.conf:233: invalid auto-key-locate list
-"""]]
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_3_ba9dd8f2cc46640383d4339a3661571f._comment b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_3_ba9dd8f2cc46640383d4339a3661571f._comment
deleted file mode 100644
index 59ac0d158..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_3_ba9dd8f2cc46640383d4339a3661571f._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlpOeCs7zZLR-PBGPxUgjWlg7bwAAzQZyk"
- nickname="Seth"
- subject="comment 3"
- date="2013-06-30T21:36:39Z"
- content="""
-WOO!!! Found a \"solution\" here:
-
-http://eureka.ykyuen.info/2011/10/26/mac-gnupg-installation/
-
-Basically I commented out this line:
-
-    auto-key-locate cert pka ldap hkp://keys.gnupg.net
-
-Any clue why this would solve the problem?
-"""]]
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_4_274ae39d55545bde0be931d7a6c42c94._comment b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_4_274ae39d55545bde0be931d7a6c42c94._comment
deleted file mode 100644
index e89e8449d..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_4_274ae39d55545bde0be931d7a6c42c94._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 4"
- date="2013-07-02T16:52:43Z"
- content="""
-The question is, where did this line in .gnupg/gpg.conf come from?
-
-It seems likely to me that something else put it there, and perhaps that has a version of gpg that supports some of the options, like ldap, while the version of gpg bundled with git-annex for OSX Lion does not.
-
-(I tried enabling that line on a Mountian Lion machine, and the gpg in git-annex accepts it.)
-"""]]
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_5_242291d46acc61bdfc112e3316de528b._comment b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_5_242291d46acc61bdfc112e3316de528b._comment
deleted file mode 100644
index 12277738a..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_5_242291d46acc61bdfc112e3316de528b._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlpOeCs7zZLR-PBGPxUgjWlg7bwAAzQZyk"
- nickname="Seth"
- subject="comment 5"
- date="2013-07-02T18:15:35Z"
- content="""
-Hmm.. well I've used gpg before, so maybe this put it there? https://gpgtools.org/
-
-Installed that well before using git-annex.
-"""]]
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_6_76b936263e82ca6c415a16ed57e770b4._comment b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_6_76b936263e82ca6c415a16ed57e770b4._comment
deleted file mode 100644
index 919027842..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_6_76b936263e82ca6c415a16ed57e770b4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 6"
- date="2013-07-04T08:32:54Z"
- content="""
-Just wondering if its because I have gnupg 1.1.0 on the Lion build machine thats causing the problem. I could try installing gnupg 2.0.19 if that will fix the problem. What version of gnupg is on the Mountain Lion build?
-"""]]
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_7_9ccd3749fd9f32b0906c0b9428cc514f._comment b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_7_9ccd3749fd9f32b0906c0b9428cc514f._comment
deleted file mode 100644
index 57ca6cb79..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_7_9ccd3749fd9f32b0906c0b9428cc514f._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 7"
- date="2013-07-05T15:28:33Z"
- content="""
-@Jimmy it has version 2.0.19 of MacGPG2.
-
-I think an upgrade is a great idea!
-"""]]
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_8_4e8982668b5044b2286d55c90adb9da3._comment b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_8_4e8982668b5044b2286d55c90adb9da3._comment
deleted file mode 100644
index b91884642..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_8_4e8982668b5044b2286d55c90adb9da3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.254.222"
- subject="comment 8"
- date="2013-07-08T18:03:54Z"
- content="""
-Actually MacGPG caused problems on mountian lion and I have switched to gpg 1.4.13 from brew.
-"""]]
diff --git a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_9_aaf0ee250972d737a2ca57de5b5f1c0a._comment b/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_9_aaf0ee250972d737a2ca57de5b5f1c0a._comment
deleted file mode 100644
index 611c3ebb9..000000000
--- a/doc/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/comment_9_aaf0ee250972d737a2ca57de5b5f1c0a._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkfHTPsiAcHEEN7Xl7WxiZmYq-vX7azxFY"
- nickname="Vincent"
- subject="comment 9"
- date="2013-07-24T13:26:07Z"
- content="""
-I was seeing this too in os/x until I upgraded to the version published on 2nd July.
-
-I was and am using macports gnupg, v1.4.13.
-
-Seems to be fixed for me now.
-"""]]
diff --git a/doc/bugs/interrupting_migration_causes_problems.mdwn b/doc/bugs/interrupting_migration_causes_problems.mdwn
deleted file mode 100644
index 68426e54a..000000000
--- a/doc/bugs/interrupting_migration_causes_problems.mdwn
+++ /dev/null
@@ -1,52 +0,0 @@
-Killing a migration from WORM to SHA256 with ^C breaks things; future attempts to do the migration fail:
-
-    #!/bin/bash
-    
-    BASE=/tmp/migrate-bug
-    
-    set -x
-    
-    chmod -R +w $BASE
-    rm -rf $BASE
-    mkdir -p $BASE
-    cd $BASE
-    
-    # create annex
-    git init .
-    git annex init
-    
-    # make a big (sparse) file and add it
-    dd if=/dev/zero of=bigfile bs=1 count=0 seek=1G
-    git annex add --backend WORM bigfile
-    git commit -m 'added bigfile'
-    
-    # look at status
-    git annex status
-    
-    # now migrate it, but kill migration during checksum
-    # Simulate ^C by making a new process group and sending SIGINT
-    setsid git annex migrate --backend SHA256 bigfile &
-    PID=$!
-    sleep 1
-    kill -INT -$PID
-    wait
-    
-    # look at status
-    git annex status
-    
-    # this migration fails
-    git annex migrate --backend SHA256 bigfile
-    
-    # but fsck says everything's OK
-    git annex fsck
-
-The error:
-
-    migrate bigfile 
-    git-annex: /tmp/migrate-bug/.git/annex/objects/K9/V1/WORM-s1073741824-m1321566308--bigfile/WORM-s1073741824-m1321566308--bigfile: createLink: already exists (File exists)
-    failed
-    git-annex: migrate: 1 failed
-
-> Fixed it to delete the stale temp file. [[done]]
-> 
-> Thanks for making such clear test cases, Jim! --[[Joey]] 
diff --git a/doc/bugs/javascript_functions_qouting_issue.mdwn b/doc/bugs/javascript_functions_qouting_issue.mdwn
deleted file mode 100644
index 7f16462f5..000000000
--- a/doc/bugs/javascript_functions_qouting_issue.mdwn
+++ /dev/null
@@ -1,44 +0,0 @@
-**What is the expected output? What do you see instead?**
-
-SyntaxError: missing ( before formal parameters
-
-function longpoll_"sidebar"() {
-
-reposi...c5e0ead (строка 5, столбец 18)
-	
-
-**Please provide any additional information below.**
-
-functions have illegal characters in their names: *function longpoll_"sidebar"*
-
-    <script>function longpoll_"sidebar"() {
-    	longpoll(longpoll_"sidebar"_url, '"sidebar"'
-    		, function() { setTimeout(longpoll_"sidebar", "10"); }
-    		, function() { webapp_disconnected(); }
-    	);
-    }
-    $(function() {
-    	$.get("/notifier/sidebar?auth=bd717e7499f2c42363719c833d3df2d25b77cf42184aacbcd0f969895911a0208ba17fd4f468c4b97274d5e3f7f419260e5df7d83d2e7642524a89325c5e0ead", function(url){
-    		longpoll_"sidebar"_url = url;
-    		setTimeout(longpoll_"sidebar", "10");
-    	});
-    });
-    function longpoll_"repolist"() {
-    	longpoll(longpoll_"repolist"_url, '"repolist"'
-    		, function() { setTimeout(longpoll_"repolist", "10"); }
-    		, function() { webapp_disconnected(); }
-    	);
-    }
-    $(function() {
-    	$.get("/notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True%7D?auth=bd717e7499f2c42363719c833d3df2d25b77cf42184aacbcd0f969895911a0208ba17fd4f468c4b97274d5e3f7f419260e5df7d83d2e7642524a89325c5e0ead", function(url){
-    		longpoll_"repolist"_url = url;
-    		setTimeout(longpoll_"repolist", "10");
-    	});
-    });
-
-> This is already fixed in the 3.20130124 release. [[done]]
-> 
-> (Standalone builds of that release are not yet available for Mountian
-> Lion.
-> 
-> --[[Joey]] 
diff --git a/doc/bugs/journal_commit_error_when_using_annex.mdwn b/doc/bugs/journal_commit_error_when_using_annex.mdwn
deleted file mode 100644
index fe1928229..000000000
--- a/doc/bugs/journal_commit_error_when_using_annex.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-Sorry for the noise - notabug - [[done]]
-
-Setup:
-
-* git-annex version: 3.20120629 on Debian unstable.
-* external RAID1 array connected via usb
-
-I did: <code> git-annex add \<a specific album of ogg files\> </code>
-
-When it gets to the fourth song, there is a long delay and a bunch of "journal commit I/O error" from the kernel start appearing. Then GNOME helpfully tells me that my drive was just connected (implying that it thought it was disconnected momentarily)
-
-Log outputs:
-
-Both trying to add whole album, failing at song 4
-
-* <http://paste.mitechie.com/show/745/>
-* <http://paste.mitechie.com/show/746/>
-
-Just trying to add song 4 individually
-
-* <http://paste.mitechie.com/show/747/> (lots o' journal commit I/O errors that time)
diff --git a/doc/bugs/journal_commit_error_when_using_annex/comment_1_38f60ca3503ea1530c4bd2cde5c9182f._comment b/doc/bugs/journal_commit_error_when_using_annex/comment_1_38f60ca3503ea1530c4bd2cde5c9182f._comment
deleted file mode 100644
index de39249a8..000000000
--- a/doc/bugs/journal_commit_error_when_using_annex/comment_1_38f60ca3503ea1530c4bd2cde5c9182f._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 1"
- date="2012-08-01T23:06:03Z"
- content="""
-That's not a git-annex error, your drive is dying.
-
-I'm sure if you tried just playing the song you'll get the same errors.
-"""]]
diff --git a/doc/bugs/journal_commit_error_when_using_annex/comment_2_6de455a67f37d9ee0a307a78123781bf._comment b/doc/bugs/journal_commit_error_when_using_annex/comment_2_6de455a67f37d9ee0a307a78123781bf._comment
deleted file mode 100644
index dd1e1c92b..000000000
--- a/doc/bugs/journal_commit_error_when_using_annex/comment_2_6de455a67f37d9ee0a307a78123781bf._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://creativecommons.net/greg/identity"
- ip="64.79.125.70"
- subject="comment 2"
- date="2012-08-01T23:22:03Z"
- content="""
-Probably right, the song in question is not playing fully and causing same error.
-
-Time to go into crises mode...
-"""]]
diff --git a/doc/bugs/json_is_broken_for_status.mdwn b/doc/bugs/json_is_broken_for_status.mdwn
deleted file mode 100644
index 0ce9dc7fa..000000000
--- a/doc/bugs/json_is_broken_for_status.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-### Please describe the problem.
-
-bad json produced
-
-### What steps will reproduce the problem?
-
-
-[[!format sh """
-$> git annex status --json
-,"success":true}
-
-in another one
-
-$> git annex status --json
-D hardware/g-box/builds/mine/.#yoh-debug-lastdidnotconnect.txt
-,"success":true}
-"""]]
-
-### What version of git-annex are you using? On what operating system?
-
-Debian sid 5.20140116
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> Not all commands support json. Made this explict by making --json not be
-> a global option. Added --json support to status. [[done]]. --[[Joey]]
diff --git a/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX.mdwn b/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX.mdwn
deleted file mode 100644
index f556d16e9..000000000
--- a/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-What steps will reproduce the problem?
-
-leave the assistant running for multiple days
-
-What is the expected output? 
-
-Glorious git-annex enlightenment
-
-What do you see instead?
-
-After ~2-3 days, there are hundreds of zombied git processes and the system is unable to fork new processes. This has occurred on 3 differently hardware configured mac's (macbooks and imacs) all running Mountain Lion 10.8.2 Build 12C3006
-In each case, once the system gets to this point, the only solution is forcing a reboot by holding down the power button as not even kill can spin up it's process.
-
-What version of git-annex are you using?
-
-    git-annex version: 3.20130122
-
-On what operating system?
-
-Mac OSX 10.8.2 Mountain Lion Build 12C3006
-
-Please provide any additional information below.
-
-I'm really not sure what to look for next. Happy to take suggestions.
-
-[!tag /design/assistant]]
-
-> [[done]], I found the zombie leak; the ConfigMonitor was 
-> leaving one zombie every time it checked a push/pull.
-> Not a fast leak, but over time they would add up. --[[Joey]]
diff --git a/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_1_91c911c29fd126ddc365c561591f627e._comment b/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_1_91c911c29fd126ddc365c561591f627e._comment
deleted file mode 100644
index d4e47b4eb..000000000
--- a/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_1_91c911c29fd126ddc365c561591f627e._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.3.125"
- subject="comment 1"
- date="2013-02-05T19:27:35Z"
- content="""
-Are you sure about that version number? 
-
-A lot of work was done to avoid excessive numbers of zombie processes back in version 3.20111011. There should be no zombies anymore.
-"""]]
diff --git a/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_2_c316aead931a6a2377a4515bbb34ac5b._comment b/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_2_c316aead931a6a2377a4515bbb34ac5b._comment
deleted file mode 100644
index 4172a7ee8..000000000
--- a/doc/bugs/long_running_assistant_causes_resource_starvation_on_OSX/comment_2_c316aead931a6a2377a4515bbb34ac5b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q"
- nickname="Andrew"
- subject="comment 2"
- date="2013-02-05T21:33:12Z"
- content="""
-That was compiled from the source tree in git. I'm letting it run again today to see if I can see it happen.
-"""]]
diff --git a/doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn b/doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn
deleted file mode 100644
index 335581e20..000000000
--- a/doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn
+++ /dev/null
@@ -1,53 +0,0 @@
-I've noticed this to occur occassionally 
-
-<pre>
-laplace:atest jtang$ ls
-1@  2@	3@  4@	5@  readme.txt@
-laplace:atest jtang$ git annex watch -d --foreground
-watch . [2012-07-29 11:49:26 IST] read: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","show-ref","git-annex"] 
-[2012-07-29 11:49:26 IST] read: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","show-ref","--hash","refs/heads/git-annex"] 
-[2012-07-29 11:49:26 IST] read: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","log","refs/heads/git-annex..f85faa60e73efabc2e92f837b19c3918d3ab030f","--oneline","-n1"] 
-[2012-07-29 11:49:26 IST] chat: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","cat-file","--batch"] 
-(scanning...) [2012-07-29 11:49:26 IST] Assistant: all threads started
-[2012-07-29 11:49:26 IST] Merger: watching /Users/jtang/sandbox/atest/.git/refs/heads/synced
-[2012-07-29 11:49:26 IST] TransferWatcher: watching for transfers
-[2012-07-29 11:49:26 IST] read: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","symbolic-ref","HEAD"] 
-[2012-07-29 11:49:26 IST] call: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","add","--update"] 
-[2012-07-29 11:49:26 IST] Merger: merging changes into Just refs/heads/master
-[2012-07-29 11:49:26 IST] call: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","merge","--no-edit","refs/heads/synced/master"] 
-(started...) [2012-07-29 11:49:26 IST] Watcher: watching .
-[2012-07-29 11:49:26 IST] WebApp: running on port 60042
-Already up-to-date.
-[2012-07-29 11:49:26 IST] Watcher: add symlink ./1
-[2012-07-29 11:49:26 IST] chat: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","cat-file","--batch"] 
-[2012-07-29 11:49:26 IST] Watcher: add symlink ./2
-[2012-07-29 11:49:26 IST] Watcher: add symlink ./3
-[2012-07-29 11:49:26 IST] Watcher: add symlink ./4
-[2012-07-29 11:49:26 IST] Watcher: add symlink ./5
-[2012-07-29 11:49:26 IST] Watcher: add symlink ./readme.txt
-[2012-07-29 11:49:27 IST] Committer: committing 6 changes
-(Recording state in git...)
-[2012-07-29 11:49:27 IST] feed: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","update-index","-z","--index-info"] 
-[2012-07-29 11:49:27 IST] call: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","commit","--allow-empty-message","-m","","--allow-empty","--quiet"] 
-[2012-07-29 11:49:28 IST] read: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","symbolic-ref","HEAD"] 
-[2012-07-29 11:49:28 IST] Pusher: pushing to []
-[2012-07-29 11:49:28 IST] call: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","branch","-f","synced/master"] 
-[2012-07-29 11:49:28 IST] read: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","symbolic-ref","HEAD"] 
-[2012-07-29 11:49:28 IST] Merger: merging changes into Just refs/heads/master
-[2012-07-29 11:49:28 IST] call: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","merge","--no-edit","refs/heads/synced/master"] 
-Already up-to-date.
-[2012-07-29 11:49:43 IST] Watcher: file added ./.gitignore
-[2012-07-29 11:49:43 IST] read: lsof ["-F0can","+d","/Users/jtang/sandbox/atest/.git/annex/tmp/"] 
-[2012-07-29 11:49:44 IST] Committer: delaying commit of 0 changes
-[2012-07-29 11:49:45 IST] read: lsof ["-F0can","+d","/Users/jtang/sandbox/atest/.git/annex/tmp/"] 
-[2012-07-29 11:49:46 IST] Committer: delaying commit of 0 changes
-[2012-07-29 11:49:47 IST] read: lsof ["-F0can","+d","/Users/jtang/sandbox/atest/.git/annex/tmp/"] 
-[2012-07-29 11:49:48 IST] Committer: delaying commit of 0 changes
-[2012-07-29 11:49:49 IST] read: lsof ["-F0can","+d","/Users/jtang/sandbox/atest/.git/annex/tmp/"] 
-</pre>
-
-I ran " git annex watch -d --foreground" to watch what was going one, and just created a .gitignore file and the the commiter/lsof thread just loops over and over.... I only noticed as my laptop battery had drained at somepoint when git-annex was running in the background.
-
-[[!meta title="assistant: lsof/committer thread loops occassionally"]]
-
-> Closing this since it doesn't seem reproducible. [[done]] --[[Joey]]
diff --git a/doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_1_f8d1720aa26c719609720acf0772606e._comment b/doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_1_f8d1720aa26c719609720acf0772606e._comment
deleted file mode 100644
index 521d2e0cb..000000000
--- a/doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_1_f8d1720aa26c719609720acf0772606e._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.133"
- subject="probably a kqueue specific problem..."
- date="2012-07-29T18:10:12Z"
- content="""
-I don't think this would eat your battery badly; it's looping for sure, but with a hardcoded 1 second delay I put in to guard against it eating all CPU.
-
-I tried to fix this in commit c4023f785834bc237e5fcdb69e275bbae10dd40b, but I sort of doubt I did.
-I made one more commit that will at least tell us what file it is trying to check over and over with lsof.
-"""]]
diff --git a/doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_2_0527569ea2924721d19dadcf4fe0ec5a._comment b/doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_2_0527569ea2924721d19dadcf4fe0ec5a._comment
deleted file mode 100644
index 438fdcb3c..000000000
--- a/doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_2_0527569ea2924721d19dadcf4fe0ec5a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.84"
- subject="comment 2"
- date="2012-09-19T17:33:20Z"
- content="""
-Have you seen this anymore? 
-"""]]
diff --git a/doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_3_5b67ff08a897ea3d2266ccc910ab4278._comment b/doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_3_5b67ff08a897ea3d2266ccc910ab4278._comment
deleted file mode 100644
index a89b12596..000000000
--- a/doc/bugs/lsof__47__committer_thread_loops_occassionally/comment_3_5b67ff08a897ea3d2266ccc910ab4278._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 3"
- date="2012-09-19T20:17:00Z"
- content="""
-No, I've not noticed this recently, I would consider this issue to be closed for now.
-"""]]
diff --git a/doc/bugs/mac_os_x_10.7_DMG_out_of_date.mdwn b/doc/bugs/mac_os_x_10.7_DMG_out_of_date.mdwn
deleted file mode 100644
index 67805af6b..000000000
--- a/doc/bugs/mac_os_x_10.7_DMG_out_of_date.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-### Please describe the problem.
-
-This URL:
-http://downloads.kitenet.net/git-annex/OSX/current/10.7.5_Lion/git-annex.dmg
-currently points to a DMG with an .app that has ctime/mtime of Dec 29.
-
-After launching the app, the About screen says this:
-
-Version: 5.20131230-g684f2e6 
-
-> Nobody is autobuilding git-annex for old versions of OSX, which 
-> is why the download page says, "**warning: not being updated any longer**"
-> 
-> So, not a bug, and nothing ca be done, unless someone steps up to run an
-> autobuilder. You can of course build it from source yourself. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/make_SHA512E_the_default.mdwn b/doc/bugs/make_SHA512E_the_default.mdwn
deleted file mode 100644
index 46f18130c..000000000
--- a/doc/bugs/make_SHA512E_the_default.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-What steps will reproduce the problem?
-
-As described in
-http://git-annex.branchable.com/backends/#comment-3c1cd45d2a015b4fc412dd813293ad7d
-, sha512 is faster. On my 64-bit system, the speed difference is about
-1.5times.
-
-What is the expected output? What do you see instead?
-
-
-What version of git-annex are you using? On what operating system?
-
-
-Please provide any additional information below.
-
-> You are free to change the default in your own annexes. This is very easy
-> to do: `echo '* annex.backend=SHA512E' > .gitattributes`
-> 
-> I don't anticipate moving to SHA512, because
-> 
-> 1. It makes `ls -l` really ugly. Each symlink takes like 4 lines
->    on an 80 column terminal.
-> 2. There are better hashes coming. Particularly SHA3. That should be
->    faster and/or more secure. And without adding so much length to the
->    hash.
-> 
-> --[[Joey]]
-
-[[done]]
diff --git a/doc/bugs/making_annex-merge_try_a_fast-forward.mdwn b/doc/bugs/making_annex-merge_try_a_fast-forward.mdwn
deleted file mode 100644
index 41a5a2a58..000000000
--- a/doc/bugs/making_annex-merge_try_a_fast-forward.mdwn
+++ /dev/null
@@ -1,35 +0,0 @@
-While merging the git-annex branch, annex-merge does not end up in a fast-forward even when it would be possible.
-But as sometimes annex-merge takes time, it would probably be worth it
-(but maybe I miss something with my workflow...).
-
-> I don't think a fast-forward will make things much faster.
-> 
-> git-annex needs its index file to be updated to reflect the merge.
-> With the union merge it does now, this can be accomplished by using
-> `git-diff-index` to efficiently get a list of files that have changed,
-> and only merge those changes into the index with `git-update-index`.
-> Then the index gets committed, generating the merge.
-> 
-> To fast-forward, it would just reset the git-annex branch to the new
-> head of the remote it's merging to. But then the index needs to be
-> updated to reflect this new head too. To do that needs the same method
-> described above, essentially (with the difference that it can replace
-> files in the index with the version from the git-annex branch, rather
-> than merging in the changes... but only if the index is known to be
-> already committed and have no other changes, which would require both
-> an attempt to commit it first, and
-> locking). 
-> 
-> So will take basically the same amount of time, except
-> it would not need to commit the index at the end of the merge. The
-> most expensive work is the `git-diff-index` and `git-update-index`,
-> which are not avoided.
-> 
-> Although, perhaps fast-forward merge would use slightly
-> less space. --[[Joey]]
-
->> To avoid the ladder-merge between two repositories described at
->> <http://sprunge.us/LOMU>, seems a fast-forward should be detected and
->> written to git, even if the index is still updated the current way.
->> [[done]]
->> --[[Joey]]
diff --git a/doc/bugs/map_not_respecting_annex_ssh_options__63__.mdwn b/doc/bugs/map_not_respecting_annex_ssh_options__63__.mdwn
deleted file mode 100644
index 63dfec4ac..000000000
--- a/doc/bugs/map_not_respecting_annex_ssh_options__63__.mdwn
+++ /dev/null
@@ -1,38 +0,0 @@
-### What steps will reproduce the problem?
-
-1. Have a remote that uses annex-ssh-options to specify an sshkey which is needed to invoke git-annex-shell on that remote.
-2. Run git-annex map.
-
-### What is the expected output? What do you see instead?
-
-I expect to see a map without any errors complaining of commands not recognized.
-
-Instead I see:
-
-    greg@x200s:~/Pictures/Photos$ git-annex map
-    map /home/greg/Pictures/Photos ok
-    map 60justin (sshing...) 
-    ok
-    map rose (sshing...) 
-    fatal: unrecognized command 'cd '/home/greg/Media/Pictures/Photos/' && git config --null --list'
-    git-annex-shell: git-shell failed
-
-relevant part of .git/config:
-
-    [remote "rose"]
-        url = greg@rose.makesad.us:/home/greg/Media/Pictures/Photos/
-        fetch = +refs/heads/*:refs/remotes/rose/*
-        annex-ssh-options = "-i /home/greg/.ssh/annex.x200s_rsa"
-        annex-trustlevel = trusted
-        annex-uuid = c0e4106e-2631-11e2-9749-1bfa37a61069
-
-
-### What version of git-annex are you using? On what operating system?
-
-    git-annex version: 3.20121017
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3
-    upgrade supported from repository versions: 0 1 2
-
-> [[done]], see comment --[[Joey]]
diff --git a/doc/bugs/map_not_respecting_annex_ssh_options__63__/comment_1_c63a1ed5909d53f116f06e60aba74dc6._comment b/doc/bugs/map_not_respecting_annex_ssh_options__63__/comment_1_c63a1ed5909d53f116f06e60aba74dc6._comment
deleted file mode 100644
index 029373945..000000000
--- a/doc/bugs/map_not_respecting_annex_ssh_options__63__/comment_1_c63a1ed5909d53f116f06e60aba74dc6._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.72"
- subject="comment 1"
- date="2012-12-05T17:00:21Z"
- content="""
-To map a remote, it needs to run `git config --list` on the remote, and the remote may be a non-git-annex git remote. So mapping does a regular ssh first, and cannot use annex.ssh-options (because that would dump it into git-annex-shell). If that fails, it *does* fall back to using git-annex-shell, and will then use annex.ssh-options. 
-
-So, not a bug, I believe.
-"""]]
diff --git a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build.mdwn b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build.mdwn
deleted file mode 100644
index 52e724095..000000000
--- a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build.mdwn
+++ /dev/null
@@ -1,38 +0,0 @@
-### Please describe the problem.
-
-1 thumb drive became corrupted when using as a server on raspberry pi, and 2 microSD cards when using as a client in my phone. Both happened during syncing largish repository. (corrupted = permanent input/output error)
-
-* Put git annex on my android phone with a 64GB (FAT) micro SD, fired up git annex, it got reported as corrupted half on hour later, reformatting worked but got reported as corrupted again.
-
-* Put git annex assistant on my raspberry pi, one of the thumbdrives in my LVM (ext4) got corrupted shortly after I began using the assistant. I replaced them with a cheap real SSD drive, and had no problem since.
-
-* Put git annex back on my android phone. Kept it going for an extended sync session, but it never started syncing. I kept it going for an hour or so, and my new 32GB microSD (FAT) got corrupted.
-
-The pattern is nothing like proof, but it seems to be too regular to be completely coincidental. The pattern seems to be: ARM + (SDcard|USBstick) + Assistant = drive corruption.
-
-My guess is that the ARM build might have some kind of unlucky write pattern or loop that causes increased wear, but I know very little of the interna.
-
-### What steps will reproduce the problem?
-
-* Get a raspberry pi and a USB stick, or an android phone and a microSD card
-* Get an [ARM build of the assistant](https://github.com/tradloff/git-annex-RPi)
-* Sync a largish (12GB) repository
-
-### What version of git-annex are you using? On what operating system?
-
-4.20131002 on the pi, 20131024 for the 32GB SD, and 20131015 for the 64GB SD.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-Unfortunately, daemon.log was unrecoverable along with the other files on the SD card.
-
-I can try and autosync the daemon.log somewhere if I happen to come along a bunch of scrap flash storage (not impossible).
-
-# End of transcript or log.
-"""]]
-
-[[done]]
diff --git a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_1_0527581ea60d28bb28504fa2a355ed87._comment b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_1_0527581ea60d28bb28504fa2a355ed87._comment
deleted file mode 100644
index 52324a5a8..000000000
--- a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_1_0527581ea60d28bb28504fa2a355ed87._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U"
- nickname="Carlo"
- subject="salvaged logs"
- date="2013-10-31T10:00:40Z"
- content="""
-The previously corrupt memory drive magically reappeared, so this might indicate a phone bug. In any case, I was able to salvage the logs from the phone.
-
-[Salvaged Logs](http://capocasa.name/android-4.2-lenovo-daemonlog.tar.gz)
-"""]]
diff --git a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_2_926a87b60e20d286d49639c8dad13a1a._comment b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_2_926a87b60e20d286d49639c8dad13a1a._comment
deleted file mode 100644
index 878e8fd7d..000000000
--- a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_2_926a87b60e20d286d49639c8dad13a1a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="correlation does not imply causation"
- date="2013-11-01T16:37:31Z"
- content="""
-I've been using git-annex on thumbdrives for years without problems. It seems more likely to me that you have a general problem with your hardware than that one program that does nothing special is somehow at fault.
-"""]]
diff --git a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_3_c509fba1a9adacfd26a2bd12b4aea988._comment b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_3_c509fba1a9adacfd26a2bd12b4aea988._comment
deleted file mode 100644
index 01ab119d2..000000000
--- a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_3_c509fba1a9adacfd26a2bd12b4aea988._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U"
- nickname="Carlo"
- subject="comment 3"
- date="2013-11-02T17:29:55Z"
- content="""
-True, and good to know. Didn't necessarily want to trigger a big bug hunt here anyway, just some data/logs in case any more correlation comes up.
-"""]]
diff --git a/doc/bugs/minor_bug:_errors_are_not_verbose_enough.mdwn b/doc/bugs/minor_bug:_errors_are_not_verbose_enough.mdwn
deleted file mode 100644
index a6620f425..000000000
--- a/doc/bugs/minor_bug:_errors_are_not_verbose_enough.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-Current:
-
-    % git annex status
-    git-annex: unknown command
-
-Better: 
-
-    % git annex status
-    git-annex: status: unknown command
-
-Current:
-
-    % git annex fsck
-    [...]
-    git-annex: 18 failed
-
-Better:
-
-    % git annex fsck
-    [...]
-    git-annex: fsck: 18 failed
-
-
-etc pp.
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/missing_dependency_in_git-annex-3.20130216.mdwn b/doc/bugs/missing_dependency_in_git-annex-3.20130216.mdwn
deleted file mode 100644
index 7c7664c67..000000000
--- a/doc/bugs/missing_dependency_in_git-annex-3.20130216.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-What steps will reproduce the problem?
-
-build git-annex-3.20130216 on OS X lion
-
-
-What is the expected output? What do you see instead?
-
-successful compile; error was:
-
-```
-Annex/UUID.hs:30:8:
-    Could not find module `System.Random'
-    It is a member of the hidden package `random-1.0.1.1'.
-    Perhaps you need to add `random' to the build-depends in your .cabal file.
-    Use -v to see a list of the files searched for.
-```
-
-
-What version of git-annex are you using? On what operating system?
-
-building git-annex-3.20130216 on OS X Lion
-
-
-Please provide any additional information below.
-
-
-adding 'random' to the BuildDepends in git-annex.cabal does indeed fix the error.
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/missing_kde__47__gnome_menu_item..mdwn b/doc/bugs/missing_kde__47__gnome_menu_item..mdwn
deleted file mode 100644
index c09cdf374..000000000
--- a/doc/bugs/missing_kde__47__gnome_menu_item..mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-What steps will reproduce the problem?
-  apt-get install git-annex
-
-
-
-What is the expected output?
- a menu item at kde or gnome at internet> Git Annex , as
-http://git-annex.branchable.com/assistant/  shows.
-
- What do you see instead? no menu item.
-
-
-What version of git-annex are you using?
-Version: 1:1.7.10.4-1+wheezy1
-
- On what operating system?
-Wheezy
-
-
- Also
-I just installed git-annex on a squeeze system and had the same result.
-
-same with ubuntu precise 12.04
-
-> git-annex ships a /usr/share/applications/git-annex.desktop
-> file that provies the menu item. But there has never been a version
-> 1.7.10. I suspect this is user error; installing a version of git-annex
-> that predates the git-annex assistant and expecting it to have the
-> assistant and its menu item. [[done]] --[[Joey]] 
diff --git a/doc/bugs/network___62____61___2.4.0.1_is_not_in_Haskell_Platform_2012.4.0.0.mdwn b/doc/bugs/network___62____61___2.4.0.1_is_not_in_Haskell_Platform_2012.4.0.0.mdwn
deleted file mode 100644
index 1b90f593f..000000000
--- a/doc/bugs/network___62____61___2.4.0.1_is_not_in_Haskell_Platform_2012.4.0.0.mdwn
+++ /dev/null
@@ -1,12 +0,0 @@
-git-annex requires version 2.4.0.1 or later of the 'network' library. Unfortunately,
-the current version of the Haskell Platform mandates version 2.3.1.0 of that library.
-This means that git-annex cannot be compiled on the Haskell Platform 2012.4.0.0 (which
-is going to remain the HP version of choice until May next year or so).
-
-Do you think it's possible to support *both* versions of the network library, maybe?
-That would increase the portability of git-annex quite a bit.
-
-Thank you for your consideration.
-
-> Ok, I think I've figured out how to use the CPP macros defined by cabal
-> to deal with this. [[done]], will be in next release. --[[Joey]] 
diff --git a/doc/bugs/network___62____61___2.4.0.1_is_not_in_Haskell_Platform_2012.4.0.0/comment_1_2c4b3757bb8de563edca65aeabcbbc5a._comment b/doc/bugs/network___62____61___2.4.0.1_is_not_in_Haskell_Platform_2012.4.0.0/comment_1_2c4b3757bb8de563edca65aeabcbbc5a._comment
deleted file mode 100644
index a6df44da9..000000000
--- a/doc/bugs/network___62____61___2.4.0.1_is_not_in_Haskell_Platform_2012.4.0.0/comment_1_2c4b3757bb8de563edca65aeabcbbc5a._comment
+++ /dev/null
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.27"
- subject="comment 1"
- date="2012-11-11T21:49:10Z"
- content="""
-My code already supports using either, but I don't know how to tell cabal to set -DWITH_OLD_URI to build with the old one, when it's installed. I've in the past tried to deal with this by defining cabal flags, and it didn't work out too well, tending to land users solidly in cabal hell.
-
-You can patch the cabal file like so to make it build with the old network:
-
-<pre>
---- a/git-annex.cabal
-+++ b/git-annex.cabal
-@@ -52,7 +52,7 @@ Flag DNS
- Executable git-annex
-   Main-Is: git-annex.hs
-   Build-Depends: MissingH, hslogger, directory, filepath,
--   unix, containers, utf8-string, network (>= 2.4.0.1), mtl,
-+   unix, containers, utf8-string, network (< 2.4.0.1), mtl,
-    bytestring, old-locale, time,
-    pcre-light, extensible-exceptions, dataenc, SHA, process, json, HTTP,
-    base (>= 4.5 && < 4.7), monad-control, transformers-base, lifted-base,
-@@ -64,6 +64,7 @@ Executable git-annex
-   C-Sources: Utility/libdiskfree.c Utility/libmounts.c
-   Extensions: CPP
-   GHC-Options: -threaded
-+  CPP-Options: -DWITH_OLD_URI
-</pre>
-"""]]
diff --git a/doc/bugs/nfs_mounted_repo_results_in_errors_on_drop_move.mdwn b/doc/bugs/nfs_mounted_repo_results_in_errors_on_drop_move.mdwn
deleted file mode 100644
index 761ee5b25..000000000
--- a/doc/bugs/nfs_mounted_repo_results_in_errors_on_drop_move.mdwn
+++ /dev/null
@@ -1,59 +0,0 @@
-I'm on an nfs mounted filesystem (some netapp somewhere).  This is repeatable, every time.
-
-    git init repo; cd repo;
-    git annex init repo
-    truncate -s 20M big
-    git annex add big
-    git commit -m "annexed file"
-    cd ..
-    git clone repo repo_copy
-    cd repo_copy;
-    git annex get .
-    git annex whereis big
-
-    #whereis big (2 copies) 
-    #   	9310b242-6021-4621-8cef-4548a00907ff -- here
-    #   	b3526e4d-38d7-4781-a9c3-436007899f1b -- origin (repo)
-    #ok
-
-    git annex drop big
-
-    #git-annex: /nfspath/repo_copy/.git/annex/objects/fM/4k/SHA1-s20971520--9674344c90c2f0646f0b78026e127c9b86e3ad77: removeDirectory: unsatisified constraints (Directory not empty)
-    #failed
-    #git-annex: drop: 1 failed
-
-    git annex drop big  # no error second time, I suspect nfs has caught up by now.
-    git annex fsck      # Doesn't know that the second drop succeeded.
-
-    #fsck big (fixing location log) 
-    #  ** Based on the location log, big
-    #  ** was expected to be present, but its content is missing.
-    #failed
-    #git-annex: fsck: 1 failed
-
-    git annex fsck
-
-    #fsck big ok
-
-    git annex whereis big
-
-    #whereis big (1 copy) 
-    #  	b3526e4d-38d7-4781-a9c3-436007899f1b -- origin (repo)
-    #ok
-
-I suspect git-annex is just too fast and optimistic for big slow nfs directories.
-
-> git-annex locks files while it is operating on their content
-> to avoid race conditions with other git-annex processes. 
-> Quite likely this problem (which I can reproduce) is due to
-> NFS having bad (non-POSIX) locking semantics. 
-> 
-> Probably the
-> lock is represented on the NFS server as some form of lock file
-> next to the file being locked, and so when that file is deleted, with
-> the lock still held, the directory, which should then be empty, still
-> contains this lock file.
-> 
-> So, this can be worked around by it not failing when the directory
-> unexpectedly cannot be removed. I've made that change. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/no_git-annex_cli_for_performing_upgrades_or_setting_upgrade_options.mdwn b/doc/bugs/no_git-annex_cli_for_performing_upgrades_or_setting_upgrade_options.mdwn
deleted file mode 100644
index ba8e65a12..000000000
--- a/doc/bugs/no_git-annex_cli_for_performing_upgrades_or_setting_upgrade_options.mdwn
+++ /dev/null
@@ -1,35 +0,0 @@
-### Please describe the problem.
-
-I have to run the webapp to do upgrades...it would be nice to have a CLI.  I would hate for the CLI to be less featured than the webapp.  Unless I've missed it in the man page?
-
-### What steps will reproduce the problem?
-
-
-### What version of git-annex are you using? On what operating system?
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> The CLI for performing upgrades is:
-> 
->	wget http://url/file
->	$unpack file
-> 
-> Where on linux $unpack is "tar xf" and on OSX it's something with hduutil
-> attach dmg.
->
-> Or, even better, it's `apt-get upgrade; apt-get install git-annex` or the
-> fine equivilant provided by your fine OS.
-> 
-> Command-line programs do not typically provide upgrade commands, 
-> because this is up to the OS, or easily handled with other command-line
-> programs. I see no reason for git-annex to be different, so [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/not_possible_to_have_annex_on_a_separate_filesystem.mdwn b/doc/bugs/not_possible_to_have_annex_on_a_separate_filesystem.mdwn
deleted file mode 100644
index 7daf03284..000000000
--- a/doc/bugs/not_possible_to_have_annex_on_a_separate_filesystem.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-I belive I have found a regression.
-
-Inspired by 
-<http://git-annex.branchable.com/forum/performance_improvement:_git_on_ssd__44___annex_on_spindle_disk/>
-I tried to only have .git/annex/objects (also tested moving .git/annex) on NFS while having the rest on local SSD disk.
-
-But when trying to add files i get:
-
-     > git annex add testfile
-    add testfile (checksum...) 
-    git-annex: testfile: rename: unsupported operation (Invalid cross-device link)
-    failed
-    git-annex: add: 1 failed
-
-I have tried both using bind-mount and with a sym-link.
-
-> Grepping for `renameFile` and `createLink` will find all the places
-> in git-annex that assume one filesystem. These would have to be changed
-> to catch errors and fall back to expensive copying.
-> 
-> Putting a separate repository on the file server could work better
-> depending on what you're trying to do. --[[Joey]] 
-
->> I've added support for putting `.git/annex` on a separate filesystem
->> from the rest of the git repository.
->> 
->> Putting individual subdirectories like `.git/annex/objects` on separate
->> filesystems from other subdirectories is not fully supported; it may
->> work but it may be slow and a few things (like `git annex migrate`) are
->> known to fail due to using hard links. I don't think this is worth
->> supporting. [[done]]
->> --[[Joey]]
diff --git a/doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn b/doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn
deleted file mode 100644
index 9d468bdc7..000000000
--- a/doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn
+++ /dev/null
@@ -1,66 +0,0 @@
-Old data isn't listed as unused after migrating backends:
-
-    #!/bin/bash
-    
-    BASE=/tmp/migrate-bug-2
-    set -x
-    chmod -R +w $BASE
-    rm -rf $BASE
-    mkdir -p $BASE
-    cd $BASE
-    
-    # create annex
-    git init .
-    git annex init
-    
-    # make a big (sparse) file and add it
-    dd if=/dev/zero of=bigfile bs=1 count=0 seek=1G
-    git annex add --backend WORM bigfile
-    git commit -m 'added bigfile'
-    
-    # migrate it
-    git annex migrate --backend SHA256 bigfile
-    
-    # status shows 2 keys taking up 2G
-    git annex status
-    
-    # but nothing is unused
-    git annex unused
-
-Output:
-
-    ++ git annex status
-    supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
-    supported remote types: git S3 bup directory rsync web hook
-    known repositories: 
-            ede95a82-1166-11e1-a475-475d55eb0f8f -- here
-    local annex keys: 2
-    local annex size: 2 gigabytes
-    visible annex keys: 1
-    visible annex size: 1 gigabyte
-    backend usage: 
-            WORM: 1
-            SHA256: 1
-    ++ git annex unused
-    unused . (checking for unused data...) (checking master...) ok
-
-The two files are hardlinked, so it's not taking up extra space, but it would be nice to be able to remove the old keys.
-
-> `git annex unused` checks the content of all branches, and assumes that,
-> when a branch contains a file that points to a key, that key is still 
-> used. In this case, the migration has staged a change to the file,
-> but it is not yet committed, so when it checks the master branch, it
-> still finds a file referring to the old key. 
-> 
-> So, slightly surprising, but not a bug. --[[Joey]] [[done]]
-
->> Thanks for the explanation.  In my real repository, it was a bit trickier:
->> the migration was commited to `master`, but other *remote* branches still
->> referenced those keys.  I was just doing a `git pull` from a central repo, but
->> needed a `git remote update` to remove those references from `remotes/foo/master` too.
->> --Jim
-
->>> I have considered making unused ignore remote tracking branches. 
->>> On the one hand, it can be a little bit confusing, and those branches
->>> can be out of date. On the other hand, it can be useful to know you're
->>> not dropping anything that some remote might still refer to. --[[Joey]] 
diff --git a/doc/bugs/on--git-dir_and_--work-tree_options.mdwn b/doc/bugs/on--git-dir_and_--work-tree_options.mdwn
deleted file mode 100644
index 0bcefbb5d..000000000
--- a/doc/bugs/on--git-dir_and_--work-tree_options.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-git-annex does not take into account the --git-dir and --work-tree command line options (while they can be useful when scripting).
-
-    > mkdir /tmp/test
-    > cd /tmp/test
-    > git init
-    Initialized empty Git repository in /tmp/test/.git/
-    > git annex init test
-    init test ok
-    > touch foo
-    > cd
-    > git --git-dir=/tmp/test/.git --work-tree=/tmp/test annex add foo
-    git-annex: Not in a git repository.
-
-regular git add works:
-
-    > git --git-dir=/tmp/test/.git --work-tree=/tmp/test add foo
-    > git --git-dir=/tmp/test/.git --work-tree=/tmp/test status 
-    # On branch master
-    #
-    # Initial commit
-    #
-    # Changes to be committed:
-    #   (use "git rm --cached <file>..." to unstage)
-    #
-    #       new file:   foo
-    #
-
-git-annex version: 3.20110702
-
-> [[done]], git-annex now honors `GIT_DIR` and `GIT_WORK_TREE` like other
-> git commands do. --[[Joey]]
diff --git a/doc/bugs/one_test_fail_on_osx.mdwn b/doc/bugs/one_test_fail_on_osx.mdwn
deleted file mode 100644
index 92f00407f..000000000
--- a/doc/bugs/one_test_fail_on_osx.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-### Please describe the problem.
-
-git-annex test reports: 1 out of 120 tests failed
-
-    ...
-      Unit Tests (indirect)
-    ...
-        lock:                                           FAIL
-          lock --force failed
-    ...
-
-### What version of git-annex are you using? On what operating system?
-
-    $ git-annex version
-    git-annex version: 5.20131221-g00d1673
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 5
-    upgrade supported from repository versions: 0 1 2 4
-
-    $ git --version
-    git version 1.8.4
-
-    System Version: OS X 10.9 (13A603)
-
-> This was a type in the test suite. It's already fixed in git. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/ordering.mdwn b/doc/bugs/ordering.mdwn
deleted file mode 100644
index 536bfce36..000000000
--- a/doc/bugs/ordering.mdwn
+++ /dev/null
@@ -1,12 +0,0 @@
-One would expect "git annex get foo bar" to first retrieve foo, and then
-bar. Actually though, it will operate on them in alphabetical order
-(probably). This is annoying when you wanted to 1st list the most important
-files to get. Maybe you'll run out of time before all can be gotten. The
-workaround of course is to run "git annex get" twice.
-
-This ordering comes from "git ls-files". git-annex passes it all the files
-the user specified. This is a useful optimisation -- earlier it would
-run "git ls-files" once per parameter, and so "git annex get *" could be
-rather slow. But, it produces this ordering problem.
-
-[[done]]
diff --git a/doc/bugs/pages_of_packfile_errors.mdwn b/doc/bugs/pages_of_packfile_errors.mdwn
deleted file mode 100644
index 488bf5ab2..000000000
--- a/doc/bugs/pages_of_packfile_errors.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-### Please describe the problem.
-
-A repair that runs for ages. In the log file, pages and pages and pages of:
-
-error: packfile /Volumes/BandZbackup2/annex/.git/objects/pack/pack-f0ae2f5cc83f11eab406518b9f06a344acf9c93c.pack does not match index
-warning: packfile /Volumes/BandZbackup2/annex/.git/objects/pack/pack-f0ae2f5cc83f11eab406518b9f06a344acf9c93c.pack cannot be accessed
-error: packfile /Volumes/BandZbackup2/annex/.git/objects/pack/pack-f0ae2f5cc83f11eab406518b9f06a344acf9c93c.pack does not match index
-warning: packfile /Volumes/BandZbackup2/annex/.git/objects/pack/pack-f0ae2f5cc83f11eab406518b9f06a344acf9c93c.pack cannot be accessed
-error: packfile /Volumes/BandZbackup2/annex/.git/objects/pack/pack-f0ae2f5cc83f11eab406518b9f06a344acf9c93c.pack does not match index
-warning: packfile /Volumes/BandZbackup2/annex/.git/objects/pack/pack-f0ae2f5cc83f11eab406518b9f06a344acf9c93c.pack cannot be accessed
-error: packfile /Volumes/BandZbackup2/annex/.git/objects/pack/pack-f0ae2f5cc83f11eab406518b9f06a344acf9c93c.pack does not match index
-warning: packfile /Volumes/BandZbackup2/annex/.git/objects/pack/pack-f0ae2f5cc83f11eab406518b9f06a344acf9c93c.pack cannot be accessed
-
-### What steps will reproduce the problem?
-
-Running git-annex, plugging in my external drive
-
-### What version of git-annex are you using? On what operating system?
-
-Auto-updated latest, I thought, but the about page says: Version: 5.20131230-g9a495e6 
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> I think I've fixed this bug. Followup if not.. [[done]] --[[Joey]] 
diff --git a/doc/bugs/pages_of_packfile_errors/comment_1_eb2989112b38bb27ce8f691dd5d318e5._comment b/doc/bugs/pages_of_packfile_errors/comment_1_eb2989112b38bb27ce8f691dd5d318e5._comment
deleted file mode 100644
index d74470ffd..000000000
--- a/doc/bugs/pages_of_packfile_errors/comment_1_eb2989112b38bb27ce8f691dd5d318e5._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.172"
- subject="comment 1"
- date="2014-02-24T18:32:31Z"
- content="""
-Well, you seem to have a corrupt git repository on your removable drive. git-annex seems to be in the process of repairing it, which can take some time.
-
-I don't see a bug here, from what you've described so far..
-"""]]
diff --git a/doc/bugs/pages_of_packfile_errors/comment_2_69fba53035ebea213ae1c11be5326690._comment b/doc/bugs/pages_of_packfile_errors/comment_2_69fba53035ebea213ae1c11be5326690._comment
deleted file mode 100644
index facae6496..000000000
--- a/doc/bugs/pages_of_packfile_errors/comment_2_69fba53035ebea213ae1c11be5326690._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkQafKy7hNSEolLs6TvbgUnkklTctUY9LI"
- nickname="Zellyn"
- subject="sounds good"
- date="2014-02-24T19:39:12Z"
- content="""
-Is it normal for the same error to repeat thousands of times like that in the log?
-"""]]
diff --git a/doc/bugs/pages_of_packfile_errors/comment_3_73b9f574e8ce36d5e0d0f6c6a89006b7._comment b/doc/bugs/pages_of_packfile_errors/comment_3_73b9f574e8ce36d5e0d0f6c6a89006b7._comment
deleted file mode 100644
index f0e6bce0b..000000000
--- a/doc/bugs/pages_of_packfile_errors/comment_3_73b9f574e8ce36d5e0d0f6c6a89006b7._comment
+++ /dev/null
@@ -1,39 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.172"
- subject="comment 3"
- date="2014-02-24T23:39:46Z"
- content="""
-Well, if there's a bug here, it might be that this particular problem has caused the repair process to loop repeatedly trying to unpack a pack file. 
-I don't see how that could happen, looking at the code it will try to unpack each pack file only once.
-
-If you run `git annex repair --debug`, you can see the git commands it runs, and so see if it's somehow looping. When I do this with some corrupt pack files (actually, I swapped one pack file for another one), I see, for example:
-
-<pre>
-[2014-02-24 19:11:42 JEST] feed: git [\"--git-dir=/home/joey/tmp/git/.git\",\"--work-tree=/home/joey/tmp/git\",\"unpack-objects\",\"-r\"]
-error: packfile /home/joey/tmp/git/.git/objects/pack/pack-857c07e35d98e8f063fdae6846d1f6f7453e1312.pack claims to have 862 objects while index indicates 1431 objects
-warning: packfile /home/joey/tmp/git/.git/objects/pack/pack-857c07e35d98e8f063fdae6846d1f6f7453e1312.pack cannot be accessed
-error: packfile /home/joey/tmp/git/.git/objects/pack/pack-857c07e35d98e8f063fdae6846d1f6f7453e1312.pack claims to have 862 objects while index indicates 1431 objects
-warning: packfile /home/joey/tmp/git/.git/objects/pack/pack-857c07e35d98e8f063fdae6846d1f6f7453e1312.pack cannot be accessed
-error: packfile /home/joey/tmp/git/.git/objects/pack/pack-857c07e35d98e8f063fdae6846d1f6f7453e1312.pack claims to have 862 objects while index indicates 1431 objects
-...
-</pre>
-
-Which shows that git-annex only ran `git unpack-objects -r` once, and yet it printed out the same error repeatedly.
-
-One possibility is a problem using `-r`, which makes it keep going on errors. Which seemed like a good idea at the time to unpack as much as possible from a damaged file. It might be that `git unpack-objects` is itself getting stuck in some kind of loop with the -r.
-
-In my case, it did not get stuck; it eventually quit and it moved on to the next pack file, after 900-some repitions of the error message:
-
-<pre>
-[2014-02-24 19:16:47 JEST] feed: git [\"--git-dir=/home/joey/tmp/git/.git\",\"--work-tree=/home/joey/tmp/git\",\"unpack-objects\",\"-r\"]
-error: packfile /home/joey/tmp/git/.git/objects/pack/pack-857c07e35d98e8f063fdae6846d1f6f7453e1312.pack claims to have 862 objects while index indicates 1431 objects
-warning: packfile /home/joey/tmp/git/.git/objects/pack/pack-857c07e35d98e8f063fdae6846d1f6f7453e1312.pack cannot be accessed
-</pre>
-
-Intesting that it's again complaining about the same pack file, despite having moved from one pack file on to the next one. I think what's going on here is while unpacking pack files A..Y (which may all be fine), it's checking pack file Z, which is corrupt, to see if the objects exist in it, and complaining each time.
-
-So, I can improve this a lot by moving *all* the pack files out of the way before trying to unpack any of them. In my test case, that completely eliminated the errors, and probably also sped it up a bit.
-
-If I were you, I'd either try stopping your running git-annex and run `git annex repair --debug` and analize the log like I did above, or get the next daily build which has that change, and see if it helps in your case.
-"""]]
diff --git a/doc/bugs/pasting_into_annex_on_OSX.mdwn b/doc/bugs/pasting_into_annex_on_OSX.mdwn
deleted file mode 100644
index 4ea4851af..000000000
--- a/doc/bugs/pasting_into_annex_on_OSX.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-What steps will reproduce the problem?
-
-Try pasting file into annex directory while assistant is running.
-
-
-What is the expected output? What do you see instead?
-
-Expect file to successfully paste into directory, then be annexed. Instead, see a permissions error, and file disappears.
-
-
-What version of git-annex are you using? On what operating system?
-
-OSX - 10.6. zsh. git-annex version: 3.20120826
-
-Please provide any additional information below.
-
-> Ok, I've put in the one second delay to adding by default on OSX.
-> I consider this bug done, at least for now..
-
->> Reopening since I've heard from someone else that it can still happen.
->> --[[Joey]] 
-
->>> Closing again, since the assistant now makes new repositories on OSX
->>> using direct mode, which should avoid this problem. NB: any existing
->>> repositories you have on OSX should be switched to use direct mode by
->>> manually running `git annex direct` in them. [[done]] --[[Joey]]
-
-[[!tag /design/assistant/OSX]]
diff --git a/doc/bugs/pasting_into_annex_on_OSX/comment_1_4eab52bb6eda92e39bdaa8eee8f31a7f._comment b/doc/bugs/pasting_into_annex_on_OSX/comment_1_4eab52bb6eda92e39bdaa8eee8f31a7f._comment
deleted file mode 100644
index 5c2c64a23..000000000
--- a/doc/bugs/pasting_into_annex_on_OSX/comment_1_4eab52bb6eda92e39bdaa8eee8f31a7f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.60"
- subject="comment 1"
- date="2012-09-18T16:35:36Z"
- content="""
-What is the error message?
-"""]]
diff --git a/doc/bugs/pasting_into_annex_on_OSX/comment_2_f1b58adfec179b75c1fc2bf578a3b5c4._comment b/doc/bugs/pasting_into_annex_on_OSX/comment_2_f1b58adfec179b75c1fc2bf578a3b5c4._comment
deleted file mode 100644
index ed38c2ca2..000000000
--- a/doc/bugs/pasting_into_annex_on_OSX/comment_2_f1b58adfec179b75c1fc2bf578a3b5c4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://www.davidhaslem.com/"
- nickname="David"
- subject="comment 2"
- date="2012-09-18T22:49:09Z"
- content="""
-Exact error message is: \"The operation can’t be completed because you don’t have permission to access some of the items.\" Looks like it starts symlinking and committing before the file is fully copied over.
-"""]]
diff --git a/doc/bugs/pasting_into_annex_on_OSX/comment_3_270aa7680c3b899a92ce6543eaba666a._comment b/doc/bugs/pasting_into_annex_on_OSX/comment_3_270aa7680c3b899a92ce6543eaba666a._comment
deleted file mode 100644
index 51c06ba12..000000000
--- a/doc/bugs/pasting_into_annex_on_OSX/comment_3_270aa7680c3b899a92ce6543eaba666a._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.2.84"
- subject="comment 3"
- date="2012-09-19T17:32:13Z"
- content="""
-I can only guess what this paste operation entails, but as far as I can tell, the error message and the deletion of the file both come from the paste program, not git-annex. 
-
-I know that git-annex assistant will not annex a file while it's still open to be written to. So my hypothesis is that the file is written to, closed, and then the paste program tries to do something else -- perhaps set the mode of the file -- and by that point git-annex has annexed it, and the program deletes the symlink. (So the content is probably buried in the git annex.)
-
-Could you build from git master and in your annex, run:
-
-   git config annex.delayadd 10
-
-That'll add a 10 second grace period for things to finish with files before they get added to the annex.
-Perhaps this will be enough to avoid the problem. Feel free to play with the number of seconds..
-"""]]
diff --git a/doc/bugs/pasting_into_annex_on_OSX/comment_4_ec11a80d5b0f78c7a927f8aa71a6c57a._comment b/doc/bugs/pasting_into_annex_on_OSX/comment_4_ec11a80d5b0f78c7a927f8aa71a6c57a._comment
deleted file mode 100644
index 3f4d9b87c..000000000
--- a/doc/bugs/pasting_into_annex_on_OSX/comment_4_ec11a80d5b0f78c7a927f8aa71a6c57a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://www.davidhaslem.com/"
- nickname="David"
- subject="comment 4"
- date="2012-09-21T04:05:20Z"
- content="""
-Looks like that did it. I started with 5 seconds, which seems to be more than enough - turned it down to 1 and it still seems to work.  The mode change sounds like a likely guess for what it's doing after it is doing writing the file - so even a second is probably more than enough.
-"""]]
diff --git a/doc/bugs/pasting_into_annex_on_OSX/comment_5_1928bd25e5e6874a3b83c2f2adc776f5._comment b/doc/bugs/pasting_into_annex_on_OSX/comment_5_1928bd25e5e6874a3b83c2f2adc776f5._comment
deleted file mode 100644
index 73eb3fa1e..000000000
--- a/doc/bugs/pasting_into_annex_on_OSX/comment_5_1928bd25e5e6874a3b83c2f2adc776f5._comment
+++ /dev/null
@@ -1,7 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- subject="comment 5"
- date="2012-09-21T04:12:54Z"
- content="""
-Ok.. My concern with this kind of \"fix\" is it could theoretically break under heavy load, and I get to pick a tradeoff between a timeout that's unlikely to break and one that'll make git-annex appear sluggish. OTOH, I can't think of anything better to do to address this. How common is \"pasting a file\" on OSX?
-"""]]
diff --git a/doc/bugs/pasting_into_annex_on_OSX/comment_6_0fe288f54b781a0c51395cb32f0e2f9d._comment b/doc/bugs/pasting_into_annex_on_OSX/comment_6_0fe288f54b781a0c51395cb32f0e2f9d._comment
deleted file mode 100644
index a3199d6d8..000000000
--- a/doc/bugs/pasting_into_annex_on_OSX/comment_6_0fe288f54b781a0c51395cb32f0e2f9d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://www.davidhaslem.com/"
- nickname="David"
- subject="comment 6"
- date="2012-09-21T14:06:45Z"
- content="""
-Well, it's not super common - but in the initial import where I'm first trying out git-annex, I'm copy-pasting my files in from my dropbox, keeping them both as separate folders to try out.
-"""]]
diff --git a/doc/bugs/problem_to_addurl_--file_with_ftp.mdwn b/doc/bugs/problem_to_addurl_--file_with_ftp.mdwn
deleted file mode 100644
index 99381b961..000000000
--- a/doc/bugs/problem_to_addurl_--file_with_ftp.mdwn
+++ /dev/null
@@ -1,67 +0,0 @@
-### Please describe the problem.
-I want to addurl using ftp protocol.
-`git annex addurl ftp://...` works fine, but `git annex addurl --file` fails with an error "failed to verify url exists".
-
-### What steps will reproduce the problem?
-
-setting up a new repo
-
-    % alias ga  
-    ga=/home/applis/git-annex.linux/git-annex  
-    % ga init  
-    init  ok  
-    (Recording state in git...)  
-
-addurl --file works with http
-
-    % wget http://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz  
-    [...]  
-    2014-03-27 15:25:06 (10,1 MB/s) - ‘git-annex-standalone-amd64.tar.gz’ saved [30689438/30689438]  
-    % ga add git-annex-standalone-amd64.tar.gz  
-    add git-annex-standalone-amd64.tar.gz ok  
-    (Recording state in git...)  
-    % ga addurl http://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz --file git-annex-standalone-amd64.tar.gz  
-    addurl git-annex-standalone-amd64.tar.gz ok  
-    (Recording state in git...)  
-
-addurl works with ftp:
-
-    % ga addurl ftp://ftp.belnet.be/debian-cd/7.4.0-live/i386/iso-hybrid/debian-live-7.4-i386-lxde-desktop.iso.log  
-    addurl ftp.belnet.be_debian_cd_7.4.0_live_i386_iso_hybrid_debian_live_7.4_i386_lxde_desktop.iso.log (downloading ftp://ftp.belnet.be/debian-cd/7.4.0-live/i386/iso-hybrid/debian-live-7.4-i386-lxde-desktop.iso.log ...)  
-    [...]  
-    2014-03-27 15:27:47 (11,1 MB/s) - ‘/data/annex/.git/annex/tmp/URL--ftp&c%%ftp.belnet.be%debian-cd%7.4.0-live%i386%iso-hybrid%debian-live-7.4-i386-lxde-desktop.iso.log’ saved [1235181]  
-    ok  
-    (Recording state in git...)  
-
-addurl --file doesn't work with ftp
-
-    % wget ftp://ftp.belnet.be/debian-cd/7.4.0-live/i386/iso-hybrid/debian-live-7.4-i386-standard.iso.zsync  
-    [...]  
-    2014-03-27 15:29:32 (19,4 MB/s) - ‘debian-live-7.4-i386-standard.iso.zsync’ saved [1932014]  
-    % ga add debian-live-7.4-i386-standard.iso.zsync  
-    add debian-live-7.4-i386-standard.iso.zsync ok  
-    (Recording state in git...)  
-    % ga addurl ftp://ftp.belnet.be/debian-cd/7.4.0-live/i386/iso-hybrid/debian-live-7.4-i386-standard.iso.zsync --file debian-live-7.4-i386-standard.iso.zsync   
-    addurl debian-live-7.4-i386-standard.iso.zsync   
-      failed to verify url exists: ftp://ftp.belnet.be/debian-cd/7.4.0-live/i386/iso-hybrid/debian-live-7.4-i386-standard.iso.zsync  
-    failed  
-    git-annex: addurl: 1 failed  
-
-### What version of git-annex are you using? On what operating system?
-
-I am using current git-annex binary linux version on Fedora 19.
-
-    % which git ; git --version  
-    /usr/bin/git  
-    git version 1.8.3.1  
-    % which ga ; ga version  
-    ga=/home/applis/git-annex.linux/git-annex  
-    git-annex version: 5.20140320-g63535e3  
-    build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash  
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL  
-    remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external  
-    local repository version: 5  
-    supported repository version: 5  
-    upgrade supported from repository versions: 0 1 2 4  
-
-> [[done]] --[[Joey]]
diff --git a/doc/bugs/problem_to_addurl_--file_with_ftp/comment_1_2bf44f1653069fb2ed0b124cf8581a48._comment b/doc/bugs/problem_to_addurl_--file_with_ftp/comment_1_2bf44f1653069fb2ed0b124cf8581a48._comment
deleted file mode 100644
index f4e98a621..000000000
--- a/doc/bugs/problem_to_addurl_--file_with_ftp/comment_1_2bf44f1653069fb2ed0b124cf8581a48._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.41"
- subject="comment 1"
- date="2014-03-27T17:27:58Z"
- content="""
---file does not change git-annex addurl's network communication in any way. I think this ftp server is sometimes working, and other times failing. It seems to be returning a 350 result code. The FTP spec is not clear what that means, but it does not seem to indicate success.
-"""]]
diff --git a/doc/bugs/problem_to_addurl_--file_with_ftp/comment_2_c85266a9359a9f45e632f31c016a45dc._comment b/doc/bugs/problem_to_addurl_--file_with_ftp/comment_2_c85266a9359a9f45e632f31c016a45dc._comment
deleted file mode 100644
index bab883611..000000000
--- a/doc/bugs/problem_to_addurl_--file_with_ftp/comment_2_c85266a9359a9f45e632f31c016a45dc._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmdbVIGiDH8KarAGAy8y2FHJD_F990JzXI"
- nickname="François"
- subject="comment 2"
- date="2014-04-01T08:55:29Z"
- content="""
-Ok, it works when adding option --relaxed. For some reason there seems to be a problem when checking file size.
-"""]]
diff --git a/doc/bugs/problem_to_addurl_--file_with_ftp/comment_3_5bba62e1dd4118bcf7e1c990c7009239._comment b/doc/bugs/problem_to_addurl_--file_with_ftp/comment_3_5bba62e1dd4118bcf7e1c990c7009239._comment
deleted file mode 100644
index 11265f6db..000000000
--- a/doc/bugs/problem_to_addurl_--file_with_ftp/comment_3_5bba62e1dd4118bcf7e1c990c7009239._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.244"
- subject="comment 3"
- date="2014-04-02T19:18:19Z"
- content="""
-Yes, --relaxed bypasses the code that uses curl to check the file size.
-
-Ok, I have figured out what's going on. 
-
-git annex addurl --file foo ftp://host # this succeeds
-
-run the command a second time, and it fails. Why? Because the file is already present in the annex, and you are running addurl in a different mode. In this mode, it is adding a *new* url to the file in the annex. (In this particular case, the new and old url are the same, but it's possible to see this bug in cases where they are not, too.)
-
-As a sanity check, when adding a new url to an existing file, git-annex wants to check that the new url has the same size as the file. Otherwise it surely has  different content. However, as I noted this ftp server is returning a weird 350 response when curl is used to try to get the size of the url. So that fails, and git-annex cannot add the new url to the file. Which would be pointless in this case anyway, since it's the same as the old url.
-
-So, I can fix two things. I can make it detect when the url it's adding to an existing file in the annex is already a known url of that file, and skip doing anything in this case since it would be a no-op anyway. Done that.
-
-And, I can improve the error message so the user is not confused about what they're asking git-annex to do, and why it's unable to. Fixed that.
-
-This leaves the question of why curl sees a 350 code from this ftp server. But since it doesn't cause problems when using addurl, with or without --file to download the file from it, I think it's best to punt on that one.
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names.mdwn b/doc/bugs/problems_with_utf8_names.mdwn
deleted file mode 100644
index aeeb16be6..000000000
--- a/doc/bugs/problems_with_utf8_names.mdwn
+++ /dev/null
@@ -1,81 +0,0 @@
-This bug is reopened to track some new UTF-8 filename issues caused by GHC
-7.4. In this version of GHC, git-annex's hack to support filenames in any
-encoding no longer works. Even unicode filenames fail to work when
-git-annex is built with 7.4. --[[Joey]]
-
-This bug is now fixed in current master. Once again, git-annex will work
-for all filename encodings, and all system encodings. It will
-only build with the new GHC. [[done]] --[[Joey]] 
-
-----
-
-Old, now fixed bug report follows:
-
-There are problems with displaying filenames in UTF8 encoding, as shown here:
-
-    $ echo $LANG
-    en_GB.UTF-8
-    $ git init
-    $ git annex init test
-    [...]
-    $ touch "Umlaut Ü.txt"
-    $ git annex add Uml*
-    add Umlaut Ã.txt ok
-    (Recording state in git...)
-    $ find -name U\* | hexdump -C
-    00000000  2e 2f 55 6d 6c 61 75 74  20 c3 9c 2e 74 78 74 0a  |./Umlaut ...txt.|
-    00000010
-    $ git annex find | hexdump -C
-    00000000  55 6d 6c 61 75 74 20 c3  83 c2 9c 2e 74 78 74 0a  |Umlaut .....txt.|
-    00000010
-    $
-
-It looks like the common latin1-to-UTF8 encoding. Functionality other than otuput seems not to be affected.
-
-> Yes, I believe that git-annex is reading filename data from git
-> as a stream of char8s, and not decoding unicode in it into logical
-> characters.
-> Haskell then I guess, tries to unicode encode it when it's output to
-> the console.
-> This only seems to matter WRT its output to the console; the data
-> does not get mangled internally and so it accesses the right files
-> under the hood.
-> 
-> I am too new to haskell to really have a handle on how to handle
-> unicode and other encodings issues with it. In general, there are three
-> valid approaches: --[[Joey]] 
-> 
-> 1. Convert all input data to unicode and be unicode clean end-to-end
->    internally. Problimatic here since filenames may not necessarily be
->    encoded in utf-8 (an archive could have historical filenames using
->    varying encodings), and you don't want which files are accessed to
->    depend on locale settings.
->    > I tried to do this by making parts of GitRepo call
->    > Codec.Binary.UTF8.String.decodeString when reading filenames from
->    > git. This seemed to break attempts to operate on the files,
->    > weirdly encoded strings were seen in syscalls in strace.
-> 1. Keep input and internal data un-decoded, but decode it when
->    outputting a filename (assuming the filename is encoded using the
->    user's configured encoding), and allow haskell's output encoding to then
->    encode it according to the user's locale configuration.
->    > This is now implemented. I'm not very happy that I have to watch
->    > out for any place that a filename is output and call `filePathToString`
->    > on it, but there are really not too many such places in git-annex.
->    >
->    > Note that this only affects filenames apparently. 
->    > (Names of files in the annex, and also some places where names
->    > of keys are displayed.) Utf-8 in the uuid.map file etc seems
->    > to be handled cleanly.
-> 1. Avoid encodings entirely. Mostly what I'm doing now; probably
->    could find a way to disable encoding of console output. Then the raw
->    filename would be displayed, which should work ok. git-annex does
->    not really need to pull apart filenames; they are almost entirely
->    opaque blobs. I guess that the `--exclude` option is the exception
->    to that, but it is currently not unicode safe anyway. (Update: tried
->    `--exclude` again, seems it is unicode clean..)
->    One other possible
->    issue would be that this could cause problems if git-annex were
->    translated.
->    > On second thought, I switched to this. Any decoding of a filename
->    > is going to make someone unhappy; the previous approach broke
->    > non-utf8 filenames.
diff --git a/doc/bugs/problems_with_utf8_names/comment_10_c53c309771caa41accab5523cc6998dd._comment b/doc/bugs/problems_with_utf8_names/comment_10_c53c309771caa41accab5523cc6998dd._comment
deleted file mode 100644
index c60168aa0..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_10_c53c309771caa41accab5523cc6998dd._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.43"
- subject="comment 10"
- date="2014-01-13T19:20:29Z"
- content="""
-No, you're wrong: Git-annex supports every filepath encoding. This bug report has been fixed, and closed for 2 years now. git-annex treats filepaths as bytestrings (essentially).
-
-Whatever problem you are having must have some other cause.
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names/comment_1_3c7e3f021c2c94277eecf9c8af6cec5f._comment b/doc/bugs/problems_with_utf8_names/comment_1_3c7e3f021c2c94277eecf9c8af6cec5f._comment
deleted file mode 100644
index 692b5d537..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_1_3c7e3f021c2c94277eecf9c8af6cec5f._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="http://adamspiers.myopenid.com/"
- nickname="Adam"
- subject="Any update on this?"
- date="2011-12-24T01:05:07Z"
- content="""
-I just noticed this issue, and was wondering what the current status is.
-
-    % ls -l 04\ -\ Orixás.mp3
-    -rw-r--r-- 1 adam users 8377816 Jul 12  2007 04 - Orixás.mp3
-    % echo 04\ -\ Orixás.mp3 | od -c
-    0000000   0   4       -       O   r   i   x 303 241   s   .   m   p   3
-    0000020  \n
-    0000021
-    % git annex add 04\ -\ Orixás.mp3
-    git-annex: /home/adam/music/RotC/transcribe/04 - Orixás.mp3: getSymbolicLinkStatus: does not exist (No such file or directory)
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names/comment_2_bad4c4c5f54358d1bc0ab2adc713782a._comment b/doc/bugs/problems_with_utf8_names/comment_2_bad4c4c5f54358d1bc0ab2adc713782a._comment
deleted file mode 100644
index a45706e4a..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_2_bad4c4c5f54358d1bc0ab2adc713782a._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://www.joachim-breitner.de/"
- nickname="nomeata"
- subject="comment 2"
- date="2011-12-24T12:49:40Z"
- content="""
-This (rather longish) thread discusses the current situation, the planned changes for 7.2 and the various issues: http://haskell.org/pipermail/glasgow-haskell-users/2011-November/021115.html
-
-The summary seems to be: From 7.2 on, getDirectoryContents _will_ return proper Strings, i.e. where a Char represents a Unicode code point, and not a Word8, which will fix the problem of outputting them.
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names/comment_3_4f936a5d3f9c7df64c8a87e62b7fbfdc._comment b/doc/bugs/problems_with_utf8_names/comment_3_4f936a5d3f9c7df64c8a87e62b7fbfdc._comment
deleted file mode 100644
index 9fef2eb1f..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_3_4f936a5d3f9c7df64c8a87e62b7fbfdc._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://www.joachim-breitner.de/"
- nickname="nomeata"
- subject="comment 3"
- date="2011-12-24T12:51:43Z"
- content="""
-An alternative that is available from ghc 7.4 on is a pure ByteString based unix API: http://thread.gmane.org/gmane.comp.lang.haskell.libraries/16556
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names/comment_4_93bee35f5fa7744834994bc7a253a6f9._comment b/doc/bugs/problems_with_utf8_names/comment_4_93bee35f5fa7744834994bc7a253a6f9._comment
deleted file mode 100644
index 5e11af6ab..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_4_93bee35f5fa7744834994bc7a253a6f9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 4"
- date="2011-12-24T16:49:13Z"
- content="""
-Adam, this bug was fixed a long time ago, first using option #2 above, but later switching to option #3 -- git-annex treats filenames as opaque binary blobs and never decodes them in any encoding; haskell's normal encoding support for stdio is disabled. 
-
-And it never resulted in a failure like you show. I cannot reproduce your problem, but it is a different bug, please open a new bug report.
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names/comment_5_519cda534c7aea7f5ad5acd3f76e21fa._comment b/doc/bugs/problems_with_utf8_names/comment_5_519cda534c7aea7f5ad5acd3f76e21fa._comment
deleted file mode 100644
index 96b0ffed0..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_5_519cda534c7aea7f5ad5acd3f76e21fa._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk6QAwUsFHpr3Km1yQbg8hf3S7RDYf7hX4"
- nickname="Lauri"
- subject="comment 5"
- date="2012-01-26T22:13:18Z"
- content="""
-I also encountered Adam's bug. The problem seems to be that communication with the git process is done with `Char8`-bytestrings. So, when `L.unpack` is called, all filenames that git outputs (with `ls-files` or `ls-tree`) are interpreted to be in latin-1, which wreaks havoc if they are really in UTF-8.
-
-I suspect that it would be enough to just switch to standard `String`s (or `Data.Text.Text`) instead of bytestrings for textual data, and to `Word8`-bytestrings for pure binary data. GHC should nowadays handle locale-dependent encoding of `String`s transparently.
-
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names/comment_6_52e0bfff2b177b6f92e226b25d2f3ff1._comment b/doc/bugs/problems_with_utf8_names/comment_6_52e0bfff2b177b6f92e226b25d2f3ff1._comment
deleted file mode 100644
index 093616d47..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_6_52e0bfff2b177b6f92e226b25d2f3ff1._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 6"
- date="2012-01-27T21:00:06Z"
- content="""
-Lauri, what version of GHC do you have that behaves this way? 7.0.4 does not. 
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names/comment_7_0cc588f787d6eecfa19a8f6cee4b07b5._comment b/doc/bugs/problems_with_utf8_names/comment_7_0cc588f787d6eecfa19a8f6cee4b07b5._comment
deleted file mode 100644
index 5a929940d..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_7_0cc588f787d6eecfa19a8f6cee4b07b5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawk6QAwUsFHpr3Km1yQbg8hf3S7RDYf7hX4"
- nickname="Lauri"
- subject="comment 7"
- date="2012-01-28T00:21:40Z"
- content="""
-7.2. nomeata already explained the issue. I got utf-8 filenames to work on a utf-8 locale by switching from Char8-bytestrings to UTF8-bytestrings, and adding `hSetEncoding h localeEncoding` to suitable places. Making things work properly with an arbitrary locale encoding would be more complicated.
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names/comment_8_ff5c6da9eadfee20c18c86b648a62c47._comment b/doc/bugs/problems_with_utf8_names/comment_8_ff5c6da9eadfee20c18c86b648a62c47._comment
deleted file mode 100644
index dcfd59bce..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_8_ff5c6da9eadfee20c18c86b648a62c47._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 8"
- date="2012-01-28T19:40:34Z"
- content="""
-Lauri a scratch patch would be very helpful. Encoding stuff makes my head explode.
-
-However, I am very worried by haskell's changes WRT unicode and filenames. Based on user input, git-annex users like to use it on diverse sets of files, with diverse and ill-defined encodings. Faffing about with converting between encodings seems likely to speactacularly fail.
-"""]]
diff --git a/doc/bugs/problems_with_utf8_names/comment_9_f358e617799e5a4e3afc6536d419eb08._comment b/doc/bugs/problems_with_utf8_names/comment_9_f358e617799e5a4e3afc6536d419eb08._comment
deleted file mode 100644
index afaef01e2..000000000
--- a/doc/bugs/problems_with_utf8_names/comment_9_f358e617799e5a4e3afc6536d419eb08._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="Still a problem"
- date="2014-01-09T18:20:55Z"
- content="""
-I can confirm that this is still a problem.  My iTunes Music folder contains songs with Unicode in the file names, and git-annex fails to sync it properly between Mac, ZFS and Linux.
-
-I realize that supporting every filesystem encoding is impossible, but if you used something like `system-filepath` and expected UTF8, it might be better than the current state of affairs.
-"""]]
diff --git a/doc/bugs/quvi_0.9.5_does_not_work_with_git-annex.mdwn b/doc/bugs/quvi_0.9.5_does_not_work_with_git-annex.mdwn
deleted file mode 100644
index 7e760bb70..000000000
--- a/doc/bugs/quvi_0.9.5_does_not_work_with_git-annex.mdwn
+++ /dev/null
@@ -1,87 +0,0 @@
-### Please describe the problem.
-The syntax of quvi has changed somewhat, breaking use in git-annex.
-
-quvi now requires one of four «commands» to be supplied: dump, get, info, scan
-
-### What steps will reproduce the problem?
-Install quvi 0.9.5, attempt to download a video.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 5.20140227-gd872677
-
-On ArchLinux up-to-date as of 28th of February 2014
-
-### Please provide any additional information below.
-
-[[!format text """
-[0 zerodogg@browncoats Dokumentar]$ git annex addurl 'quvi:https://www.youtube.com/watch?v=de20gulo78g' --debug  
-[2014-02-28 09:33:22 CET] read: quvi ["--verbosity","quiet","-c","http","https://www.youtube.com/watch?v=de20gulo78g"]
-error: `--verbosity' is not a quvi command. See 'quvi help'.
-git-annex: quvi failed
-[1 zerodogg@browncoats Dokumentar]$ quvi --version
-quvi v0.9.5
-  built on 2013-11-12 17:02:06 +0000 for x86_64-unknown-linux-gnu
-    with gcc, -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4
-  configuration: --prefix=/usr
-libquvi v0.9.4
-  built on 2013-12-17 11:27:41 +0000 for x86_64-unknown-linux-gnu
-    with gcc, -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4
-  configuration: --prefix=/usr
-libquvi-scripts v0.9.20131130
-  configuration: --prefix=/usr --with-nsfw --with-geoblocked
-
-Copyright (C) 2012,2013  Toni Gundogdu <legatvs@gmail.com>
-quvi comes with ABSOLUTELY NO WARRANTY.  You may redistribute copies of
-quvi under the terms of the GNU Affero General Public License version 3
-or later. For more information, see <http://www.gnu.org/licenses/agpl.html>.
-
-To contact the developers, please mail to <quvi-devel@lists.sourceforge.net>
-[0 zerodogg@browncoats Dokumentar]$  quvi
-Usage: quvi [--version] [--help] COMMAND [ARGS]
-
-quvi commands are:
-  dump    Query and print the property values
-  get     Save media stream to a file
-  info    Inspect the configuration and the script properties
-  scan    Scan and print the found embedded media URLs
-
-See 'quvi help COMMAND' for more information on a specific command.
-[0 zerodogg@browncoats Dokumentar]$ git annex version
-git-annex version: 5.20140227-gd872677
-build flags: Assistant Webapp Pairing S3 Inotify DBus XMPP Feeds Quvi TDFA
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-remote types: git gcrypt S3 bup directory rsync web tahoe glacier hook external
-local repository version: 5
-supported repository version: 5
-upgrade supported from repository versions: 0 1 2 4
-"""]]
-
-quvi dump is probably something you could use
-
-[[!format text """
-[0 zerodogg@browncoats Dokumentar]$ quvi dump 'https://www.youtube.com/watch?v=de20gulo78g'
-QUVI_MEDIA_PROPERTY_THUMBNAIL_URL=https://i1.ytimg.com/vi/de20gulo78g/default.jpg                                                                                        
-QUVI_MEDIA_PROPERTY_TITLE=[Linux.conf.au 2013] - Git-annex
-QUVI_MEDIA_PROPERTY_ID=de20gulo78g
-QUVI_MEDIA_PROPERTY_START_TIME_MS=0
-QUVI_MEDIA_PROPERTY_DURATION_MS=2328000
-QUVI_MEDIA_STREAM_PROPERTY_VIDEO_ENCODING=vp8.0
-QUVI_MEDIA_STREAM_PROPERTY_AUDIO_ENCODING=vorbis
-QUVI_MEDIA_STREAM_PROPERTY_CONTAINER=webm
-QUVI_MEDIA_STREAM_PROPERTY_URL=[Long googlevideo.com URL]
-QUVI_MEDIA_STREAM_PROPERTY_ID=medium_webm_i43_360p
-QUVI_MEDIA_STREAM_PROPERTY_VIDEO_BITRATE_KBIT_S=0
-QUVI_MEDIA_STREAM_PROPERTY_AUDIO_BITRATE_KBIT_S=0
-QUVI_MEDIA_STREAM_PROPERTY_VIDEO_HEIGHT=360
-QUVI_MEDIA_STREAM_PROPERTY_VIDEO_WIDTH=640
-"""]]
-
-It does however output some status messages to STDERR (which it removes later) that doesn't look to be possible to suppress.
-
-[[!format text """
-[0 zerodogg@browncoats Dokumentar]$ quvi dump 'https://www.youtube.com/watch?v=de20gulo78g' >/dev/null 2>stderr
-[0 zerodogg@browncoats Dokumentar]$ cat -v stderr 
-status: o--- resolve <url> ...                                                 ^M                                                                               ^Mstatus: -o-- fetch <url> ...                                                   ^M                                                                               ^M%               [0 zerodogg@browncoats Dokumentar]$              
-""" ]]
-
-> quvi version now probed at runtime. [[done]] --[[Joey]]
diff --git a/doc/bugs/quvi_0.9.5_does_not_work_with_git-annex/comment_1_d0d2bcd97ef5c9bce8a57c4184a176e0._comment b/doc/bugs/quvi_0.9.5_does_not_work_with_git-annex/comment_1_d0d2bcd97ef5c9bce8a57c4184a176e0._comment
deleted file mode 100644
index 9f8650e95..000000000
--- a/doc/bugs/quvi_0.9.5_does_not_work_with_git-annex/comment_1_d0d2bcd97ef5c9bce8a57c4184a176e0._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.146"
- subject="comment 1"
- date="2014-02-28T17:52:07Z"
- content="""
-git-annex supports quvi 0.9.4 since 5.20131127. Unless the syntax has changed in some breaking way between 0.9.4 and 0.9.5, it seems most likely to me that your system is using a git-annex compiled with support for the old quvi, and it just needs to be recompiled to use the new one.
-
-I could do run-time quvi version detection, but there's an obvious performance penalty.
-"""]]
diff --git a/doc/bugs/quvi_0.9.5_does_not_work_with_git-annex/comment_2_ff9661198257b8c5e2e8ca3d85a7471c._comment b/doc/bugs/quvi_0.9.5_does_not_work_with_git-annex/comment_2_ff9661198257b8c5e2e8ca3d85a7471c._comment
deleted file mode 100644
index f05b9b069..000000000
--- a/doc/bugs/quvi_0.9.5_does_not_work_with_git-annex/comment_2_ff9661198257b8c5e2e8ca3d85a7471c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="EskildHustvedt"
- ip="80.202.213.223"
- subject="comment 2"
- date="2014-02-28T17:56:42Z"
- content="""
-That explains it. I'm using the standalone build, which I suppose then is built with the old quvi. I guess I could write a shell script wrapper that converts the old syntax to the new.
-"""]]
diff --git a/doc/bugs/reinject_should_leave_file_in_place_on_checksum_mismatch.mdwn b/doc/bugs/reinject_should_leave_file_in_place_on_checksum_mismatch.mdwn
deleted file mode 100644
index a487b2d3d..000000000
--- a/doc/bugs/reinject_should_leave_file_in_place_on_checksum_mismatch.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-What steps will reproduce the problem?
-
-Run git annex reinject source dest with a file that has the wrong content and thus a wrong checksum.
-
-What is the expected output? What do you see instead?
-
-The file should stay in it's original location. Currently it's moved to .git/annex/bad with a mangled filename.
-
-What version of git-annex are you using? On what operating system?
-
-git-annex version: 3.20120807
-Ubuntu 12.04 updated on Aug 20th
-annex was installed via cabal on Aug 20th, all other packages are from ubuntu.
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/removable_device_configurator_chokes_on_spaces.mdwn b/doc/bugs/removable_device_configurator_chokes_on_spaces.mdwn
deleted file mode 100644
index e114877ec..000000000
--- a/doc/bugs/removable_device_configurator_chokes_on_spaces.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-# What steps will reproduce the problem?
-
-1. Get a removable device and create a filesystem with a label containing a space, e.g.:
-    # mkfs.ext4 -L "Backup Home" /dev/sdb1
-2. Open the webapp and add a new repository on a removabledevice
-3. Select the devices mountpoint, e.g. /media/Backup\ Home
-
-# What is the expected output? What do you see instead?
-
-The configurator should remove spaces for branch names, but it actually seems to call git remote add with "Backup Home" as argument which is invalid.
-
-The assistant produces an internal server error and subsequently crashes completely.
-
-# What version of git-annex are you using? On what operating system?
-
-git-annex 3.20120924 from the Debian package in sid on Debian wheezy, amd64.
-
-> Thanks for reporting this, I've fixed it in git. [[done]] --[[Joey]] 
diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch.mdwn b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch.mdwn
deleted file mode 100644
index c315d4789..000000000
--- a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch.mdwn
+++ /dev/null
@@ -1,81 +0,0 @@
-### Please describe the problem.
-
-On Mac OS X, I tried to switch a repository to direct mode, but there was a
-problem in the middle of the switch (permission denied) and the switch
-aborted, leaving the repository in a half switched state.
-
-I tried different manipulations, one of which was a checkout (oops), switch
-back to indirect, then direct again, and now I have the repository in direct
-mode except one file which caused the permission denied error.
-
-### What steps will reproduce the problem?
-
-Do not know exactly why this file is special. I still have the repository, and
-each time I try to get this file, it fails with the same error message.
-
-### What version of git-annex are you using? On what operating system?
-
-On Umba, git-annex version: 4.20130723, on Mac OS X 10.6.8.
-
-### Please provide any additional information below.
-
-Umba is the Mac OS X, camaar and riva are Debian machines.
-
-[[!format sh """
-Umba$ git annex version
-git-annex version: 4.20130723
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS
-Umba$
-
-Umba$ git annex get --from riva --not --in here
-get 2013-07-31/2013-07-31_180411.jpg (from riva...) 
-Password: 
-SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c
-     2819887 100%  943.08kB/s    0:00:02 (xfer#1, to-check=0/1)
-
-sent 42 bytes  received 2820397 bytes  433913.69 bytes/sec
-total size is 2819887  speedup is 1.00
-failed
-git-annex: get: 1 failed
-Umba$ find . -name SHA256-s2819887-\*
-./.git/annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c
-./.git/annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c.cache
-./.git/annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c.map
-./.git/annex/transfer/failed/download/13fd5d5a-ed97-11e2-9178-574d3b1c0618/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c
-./.git/annex/transfer/failed/download/95443f2e-ed96-11e2-9d3f-8ffa5b1aae7a/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c
-Umba$ git annex fsck
-fsck 2013-07-31/2013-07-31_180411.jpg ok
-(Recording state in git...)
-Umba$ git annex drop 2013-07-31/2013-07-31_180411.jpg 
-Umba$ git annex get --from riva --not --in here
-get 2013-07-31/2013-07-31_180411.jpg (from riva...) 
-Password: 
-SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c
-     2819887 100%  949.58kB/s    0:00:02 (xfer#1, to-check=0/1)
-
-sent 42 bytes  received 2820397 bytes  512807.09 bytes/sec
-total size is 2819887  speedup is 1.00
-failed
-git-annex: get: 1 failed
-Umba$
-
-camaar% git annex copy --to umba --not --in umba
-copy 2013-07-31/2013-07-31_180411.jpg (checking umba...) (to umba...)
-SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c
-     2819887 100%    4.19MB/s    0:00:00 (xfer#1, to-check=0/1)
-git-annex: //Users/nicolas/Pictures/Petites Boutes/.git/annex/tmp/2013-07-31_18041141700.jpg: rename: permission denied (Operation not permitted)
-git-annex-shell: recvkey: 1 failed
-
-sent 2820393 bytes  received 42 bytes  1128174.00 bytes/sec
-total size is 2819887  speedup is 1.00
-rsync error: syntax or usage error (code 1) at main.c(1070) [sender=3.0.9]
-  
-  rsync failed -- run git annex again to resume file transfer
-failed
-git-annex: copy: 1 failed
-camaar%
-"""]]
-
-> Put in a fix that works, although perhaps not ideal as I do not
-> understand how the repo got into the original problem state. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment
deleted file mode 100644
index 1aef52076..000000000
--- a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.80"
- subject="comment 1"
- date="2013-09-30T16:47:42Z"
- content="""
-I was able to cause a permission denied on `git annex direct` if I made the file in .git/annex/objects be owned by an different user than me. I do not know how that could happen in normal operation of git-annex.
-
-
-I have made `git annex direct` catch this exception and continue. So you will get a repository that is switched to direct mode, but with one file that is still a symlink to the content, and if you fix the permissions problem, `git annex fsck` will fix it.
-
-I am curious about any details of how your repository got into the original state..
-"""]]
diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_2_93af8f48a01b6e2d011bd6f60499ccd2._comment b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_2_93af8f48a01b6e2d011bd6f60499ccd2._comment
deleted file mode 100644
index a0e73cc5e..000000000
--- a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_2_93af8f48a01b6e2d011bd6f60499ccd2._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="http://nicolas-schodet.myopenid.com/"
- ip="81.56.19.53"
- subject="comment 2"
- date="2013-11-23T14:38:21Z"
- content="""
-Here are the files in details:
-
-[[!format sh \"\"\"
-Umba:.../.git$ ls -ld $(find . -name SHA256-s2819887-\*) # the bad file
-drwxr-xr-t  4 marie-eve  staff  136 Aug 17 17:05 ./annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c/
--rw-r--r--  1 marie-eve  staff  560 Nov 23 15:25 ./annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c.cache
--rw-------  1 marie-eve  staff   33 Aug 17 17:05 ./annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c.map
--rw-r--r--  1 marie-eve  staff   52 Aug 17 17:06 ./annex/transfer/failed/download/13fd5d5a-ed97-11e2-9178-574d3b1c0618/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c
--rw-r--r--  1 marie-eve  staff   51 Aug 17 10:13 ./annex/transfer/failed/download/95443f2e-ed96-11e2-9d3f-8ffa5b1aae7a/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c
-Umba:.../.git$ ls -ld $(find . -name SHA256-s5066556-\*) # a good file
-dr-xr-xr-x  3 marie-eve  staff      102 Nov 23 15:27 ./annex/objects/Fx/w0/SHA256-s5066556--0e4a47efdc14c884d07c017ba5506a56affb136d87bef5700145774fd9089f25/
--r--r--r--  1 marie-eve  staff  5066556 Nov  6 17:43 ./annex/objects/Fx/w0/SHA256-s5066556--0e4a47efdc14c884d07c017ba5506a56affb136d87bef5700145774fd9089f25/SHA256-s5066556--0e4a47efdc14c884d07c017ba5506a56affb136d87bef5700145774fd9089
-Umba:.../.git$
-\"\"\"]]
-
-No more idea on how it reached this situation.
-"""]]
diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_3_f8fba1955e62360061613e5898b3d74e._comment b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_3_f8fba1955e62360061613e5898b3d74e._comment
deleted file mode 100644
index d7d05da85..000000000
--- a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_3_f8fba1955e62360061613e5898b3d74e._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://nicolas-schodet.myopenid.com/"
- ip="81.56.19.53"
- subject="comment 3"
- date="2013-11-23T15:42:26Z"
- content="""
-The link seems to be special:
-
-[[!format sh \"\"\"
-Umba:2013-07-31$ ls -lO 2013-07-31_180411.jpg 
-lrwxr-xr-x  1 marie-eve  staff  uchg 191 Aug 12 21:45 2013-07-31_180411.jpg@ -> ../.git/annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c
-Umba:2013-07-31$
-\"\"\"]]
-
-I tried the chflags command with no success... I suppose I need a MAC specialist.
-"""]]
diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_4_abffe1fb3b3e684b126e4768089dc5f4._comment b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_4_abffe1fb3b3e684b126e4768089dc5f4._comment
deleted file mode 100644
index 890648d16..000000000
--- a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_4_abffe1fb3b3e684b126e4768089dc5f4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 4"
- date="2013-12-12T20:17:26Z"
- content="""
-It looks like the symlink may have some form of immutable attribute set on it. I assume that the \"uchg\" in the ls output means something like \"unchangable\".
-"""]]
diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_5_bccc53d2d6f659f21965042a057358f5._comment b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_5_bccc53d2d6f659f21965042a057358f5._comment
deleted file mode 100644
index cd662bc9e..000000000
--- a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_5_bccc53d2d6f659f21965042a057358f5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://nicolas-schodet.myopenid.com/"
- ip="2a01:e35:1381:3350:1e4b:d6ff:fe78:1ddb"
- subject="comment 5"
- date="2013-12-20T20:19:05Z"
- content="""
-Yes, right, but symbolic links are not supposed to have flags... so the chflags does nothing...
-"""]]
diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_6_ac8b3b042b882680f0eb0d53ade1ce15._comment b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_6_ac8b3b042b882680f0eb0d53ade1ce15._comment
deleted file mode 100644
index 6232a77f8..000000000
--- a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_6_ac8b3b042b882680f0eb0d53ade1ce15._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://nicolas-schodet.myopenid.com/"
- ip="2a01:e35:1381:3350:1e4b:d6ff:fe78:1ddb"
- subject="comment 6"
- date="2013-12-20T20:28:10Z"
- content="""
-I finally managed to fix my repository by using this command:
-
-    SetFile -P -a l 2013-07-31_180411.jpg
-
-This removes the \"locked\" attribute.  After this command, the uchg flag is no longer set and I manage to use the repository normally.
-
-Still no idea on why it was set and whether this need a git-annex fix or not.
-"""]]
diff --git a/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote.mdwn b/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote.mdwn
deleted file mode 100644
index c2ca43da5..000000000
--- a/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-# What steps will reproduce the problem?
-
-1. Use assistant to setup a local repository (client group) and a remote repository (via ssh, backup group).
-
-2. Add some big files and wait for them to be syncronized.
-
-3. Manually switch to indirect mode (to make 'drop' work)
-
-4. Drop the file's content from the local repository.
-
-5. Rename the file using any file manager or mv on the command line.
-
-
-# What is the expected output? What do you see instead?
-
-* Expected outcome was the file being renamed and that name change being propagated to the remote repository without re-transferring the whole file. I didn't drop it for nothing!
-
-* Instead, the file was renamed and the file's content was retrieved from the remote repository.
-
-
-# What version of git-annex are you using? On what operating system?
-
-Git-Annex 3.20130102
-
-Arch Linux on x64.
-
-[[done]]; was not a bug and also the webapp now offers a "manual mode" option that can be chosen instead of "client" to get the desired behavior. --[[Joey]] 
diff --git a/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote/comment_1_d6aad1831674586fe4cdf61dd2a4bbb9._comment b/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote/comment_1_d6aad1831674586fe4cdf61dd2a4bbb9._comment
deleted file mode 100644
index 21954076e..000000000
--- a/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote/comment_1_d6aad1831674586fe4cdf61dd2a4bbb9._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.211"
- subject="comment 1"
- date="2013-01-08T18:35:58Z"
- content="""
-Since your local repository is in the client group, this behavior is actually as intended. Client group means the [[preferred_content]] settings will try to get the content of all files, unlless they're in a directory named \"archive\". This happens not just when you rename a dropped file, but on startup, when the network comes up, or even just periodically it'll notice if some file's content is missing and download it.
-
-So, your choices are
-
-1. Make an `archive` directory, and move files into it when you don't want them available locally. The assistant will even automatically drop them when you move them.
-2. Use `git annex vicfg` to set up your own [[preferred content]] expression that makes it behave how you want. For example, you could use `present` to make the assistant not prefer to have the content of files, unless the content is already present, and then manually `git annex get` and `git annex drop` files as desired.
-
-(BTW, you can use \"drop\" in direct mode with yesterday's release.)
-"""]]
diff --git a/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote/comment_2_8591e174c1a8cddfae9371407a58ff1c._comment b/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote/comment_2_8591e174c1a8cddfae9371407a58ff1c._comment
deleted file mode 100644
index 5dc891c46..000000000
--- a/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote/comment_2_8591e174c1a8cddfae9371407a58ff1c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnjjCyhVEcTRM5m4iIBqL3ZCooPx7ZYB_E"
- nickname="Marcus"
- subject="comment 2"
- date="2013-01-08T21:27:39Z"
- content="""
-Thank you for your answer. In the mean time I already changed the preferred content setting to \"present\" and it's good to know that this issue should be resolved by that as well. Will check later.
-
-Ciao, Marcus
-"""]]
diff --git a/doc/bugs/repair_fails_when_home_on_seperate_partition.mdwn b/doc/bugs/repair_fails_when_home_on_seperate_partition.mdwn
deleted file mode 100644
index 19780c7de..000000000
--- a/doc/bugs/repair_fails_when_home_on_seperate_partition.mdwn
+++ /dev/null
@@ -1,60 +0,0 @@
-### Please describe the problem.
-
-
-### What steps will reproduce the problem?
-
-(1) Place a broken repo on a different mount point than the root partition.
-
-(2) Run
-    git annex repair.
-
-### What version of git-annex are you using? On what operating system?
-
- 5.20131118-gc7e5cde on Ubuntu 12.04
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-$ git annex repair --force
-
-Running git fsck ...
-git fsck found 74 broken objects.
-Unpacking all pack files.
-Unpacking objects: 100% (2307/2307), done.
-Unpacking objects: 100% (241565/241565), done.
-Re-running git fsck to see if it finds more problems.
-Initialized empty Git repository in /tmp/tmprepo.0/.git/
-Trying to recover missing objects from remote pi.fritz.box__var_lib_store_annex
-Trying to recover missing objects from remote pi.fritz.box__var_lib_store_annex
-74 missing objects could not be recovered!
-
-
-Deleted remote branch pi.fritz.box__var_lib_store_annex/master (was dffa056).
-error: Could not read 4e01bbdc7ce31247ad66ab13ca46925ac2c8db9a
-fatal: Failed to traverse parents of commit 718525a48b4d6b3404eda5e189332d73c968a2be
-Deleted remote branch pi.fritz.box__var_lib_store_annex/synced/git-annex (was 718525a).
-Deleted remote branch pi.fritz.box__var_lib_store_annex/synced/master (was 9aedf69).
-Deleted remote branch pi.fritz.box_annex/synced/master (was 92b1042).
-Deleted remote branch store/master (was b059380).
-removed 5 remote tracking branches that referred to missing objects
-fatal: bad object refs/heads/git-annex
-fatal: bad object refs/heads/git-annex
-fatal: bad object refs/heads/git-annex
-error: remote branch 'git-annex' not found.
-
-git-annex: /tmp/packed-refs19813: rename: unsupported operation (Invalid cross-device link)
-failed
-git-annex: repair: 1 failed
-
-
-# End of transcript or log.
-"""]]
-
-> Thanks for reporting. As far as I can see, this was fixed
-> accidentially, when I rewrote the packed refs file handling code to not
-> re-write the file. It had been using a temp file, and renaming it, thus
-> the problem. I checked the repair code and can find no other probems
-> of this sort currently in it. [[done]] --[[Joey]]
diff --git a/doc/bugs/restart_daemon_required.mdwn b/doc/bugs/restart_daemon_required.mdwn
deleted file mode 100644
index fe765e24f..000000000
--- a/doc/bugs/restart_daemon_required.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-Git annex refuses to get/drop files until it's manually relaunched.
-
-I'm trying to setup a basic dropbox like system where a couple of computers sync with a local server I have constantly running ubuntu with ssh.
-
-I think I've setup git annex correctly: when I put files in the repo folder they get uploaded to the bare git repo on the server over ssh automatically and the other computer updates with a broken alias to the file. However the file does not then download from the server despite it being available without a manual restart of the daemon or a git-annex get command from the terminal.
-
-Additionally, files inside archive folders do not get dropped once uploaded to the server without a restart of the daemon.
-
-
-My computers are each setup with the ssh server as a 2nd repository (fullarchive), they are both OSX, and running Version: 4.20130521-g25dba9d according to the webapp. I have also entered my gmail/jabber account on each mac which I believe allows them to communicate indirectly when using the ssh repo.
-
-
-I don't know if this is a setup/misconfiguration error or a bug but I can't see how I've setup the assistant wrong, I did manually change the remote url in the config file, as the assistant was having issues connecting  (I'm sshing on 21 for various reasons, although I thought this was supported and I no longer receive errors in the webapp now I've specified my remote.
-
-Should I put the corresponding computers as a repositories of each other? I thought each syncing independently with a centralised git would be a more reliable/simple situation than a potential 3 way sync?
-
-
-I hope this is enough information, I'm usually good at working out issues myself, however this is just frustrating me and the git-annex solution is so nearly perfect if it would work reliably that I can't bring myself to give up on it!
-
-Thanks!
-
-> [[done]], release notes updated; see my comment --[[Joey]]
diff --git a/doc/bugs/restart_daemon_required/comment_1_f79ac16cc9f1e3b08cd121bf5efb29c3._comment b/doc/bugs/restart_daemon_required/comment_1_f79ac16cc9f1e3b08cd121bf5efb29c3._comment
deleted file mode 100644
index bd3fc74c8..000000000
--- a/doc/bugs/restart_daemon_required/comment_1_f79ac16cc9f1e3b08cd121bf5efb29c3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-31T18:15:03Z"
- content="""
-Enabling debugging, and send a log. XMPP may not be working.
-"""]]
diff --git a/doc/bugs/restart_daemon_required/comment_2_50c1b268a3cc4514681059eabca674e3._comment b/doc/bugs/restart_daemon_required/comment_2_50c1b268a3cc4514681059eabca674e3._comment
deleted file mode 100644
index 439d7ae1a..000000000
--- a/doc/bugs/restart_daemon_required/comment_2_50c1b268a3cc4514681059eabca674e3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-05-31T18:20:26Z"
- content="""
-You could also try upgrading to a current nightly build. There have been a lot of XMPP improvements recently.
-"""]]
diff --git a/doc/bugs/restart_daemon_required/comment_3_1716e0f3c7c44dc77ebf7f00fdd8f9e3._comment b/doc/bugs/restart_daemon_required/comment_3_1716e0f3c7c44dc77ebf7f00fdd8f9e3._comment
deleted file mode 100644
index 61423066a..000000000
--- a/doc/bugs/restart_daemon_required/comment_3_1716e0f3c7c44dc77ebf7f00fdd8f9e3._comment
+++ /dev/null
@@ -1,310 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmxns2UBAMDbTwrwHq_Lx1sNKrVVayq1X4"
- nickname="Darren"
- subject="comment 3"
- date="2013-06-01T01:19:02Z"
- content="""
-Thanks Joey for the quick reply, I've just updated both clients to the latest versions I could find, one is running Lion so the version is slightly behind as the autobuilds are currently failing to compile. The mountain lion system I believe is running one of the latest builds.
-
-I've captured the error here as best I can, I didn't know what to leave out so apologies for the length of the logs.
-
-===
-Sending Repo (added sync.mov)
-===
-
-    [2013-06-01 01:59:56 BST] main: starting assistant version 4.20130522-g933ba09
-    [2013-06-01 01:59:56\"_xmpp-client._tcp.gmail.com\"
-     BST] TransferScanner: Syncing with Cloud 
-    Already up-to-date.
-    Just [(20,0,5222,\"alt1.xmpp.l.google.com.\"),(20,0,5222,\"alt2.xmpp.l.google.com.\"),(20,0,5222,\"alt3.xmpp.l.google.com.\"),(20,0,5222,\"alt4.xmpp.l.google.com.\"),(5,0,5222,\"xmpp.l.google.com.\")]
-
-    (scanning...) [2013-06-01 01:59:56 BST] Watcher: Performing startup scan
-    Already up-to-date.
-    Everything up-to-date
-
-    (started...) [2013-06-01 01:59:58 BST] Committer: Committing changes to git
-    [2013-06-01 01:59:58 BST] Pusher: Syncing with Cloud 
-    Everything up-to-date
-    From ssh://cloud.rhymeorange.com:21/tank/git-annex/projects
-       da9a4d5..4142ae6  synced/git-annex -> Cloud/synced/git-annex
-    [2013-06-01 02:00:56 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"]
-    [2013-06-01 02:01:19 BST] Watcher: add direct /Volumes/StoragePool/Projects/init/sync.mov
-    [2013-06-01 02:01:19 BST] read: lsof [\"-F0can\",\"+d\",\"/Volumes/StoragePool/Projects/init/.git/annex/tmp/\"]
-    [2013-06-01 02:01:19 BST] Committer: Adding sync.mov
-
-    (Recording state in git...)
-    (merging Cloud/synced/git-annex into git-annex...)
-    add /Volumes/StoragePool/Projects/init/sync.mov (checksum...) [2013-06-01 02:01:19 BST] read: sha256sum [\"/Volumes/StoragePool/Projects/init/.git/annex/tmp/sync1693.mov\"]
-    recv: resource vanished (Connection reset by peer)
-    [2013-06-01 02:01:20 BST] chat: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"hash-object\",\"-t\",\"blob\",\"-w\",\"--stdin\"]
-    [2013-06-01 02:01:20 BST] Committer: committing 1 changes
-    [2013-06-01 02:01:20 BST] Committer: Committing changes to git
-    [2013-06-01 02:01:20 BST] feed: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"update-index\",\"-z\",\"--index-info\"]
-    [2013-06-01 02:01:20 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"commit\",\"--allow-empty-message\",\"--no-edit\",\"-m\",\"\",\"--quiet\",\"--no-verify\"]
-    [2013-06-01 02:01:20 BST] Pusher: Syncing with Cloud 
-    [2013-06-01 02:01:20 BST] Committer: queued Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Nothing : new file created
-    [2013-06-01 02:01:20 rBeScTv]:  Trreasnosufrecrer evra:n iTsrhaends f(eCrorninnegc:t iUopnl oraeds eUtU IbDy  \"pee3e9r3)d
-    45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Nothing
-    [2013-06-01 02:01:20 BST] chat: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"hash-object\",\"-w\",\"--stdin-paths\"]
-    [2013-06-01 02:01:20 BST] call: /Applications/git-annex.app/Contents/MacOS/git-annex [\"transferkeys\",\"--readfd\",\"82\",\"--writefd\",\"81\"]
-    [2013-06-01 02:01:20 BST] feed: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"update-index\",\"-z\",\"--index-info\"]
-    [2013-06-01 02:01:20 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:20 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"write-tree\"]
-    [2013-06-01 02:01:20 BST] chat: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"commit-tree\",\"181162ed25fb1bec4d077e359a5f0e60344e735e\",\"-p\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:20 BST] call: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"update-ref\",\"refs/heads/git-annex\",\"ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\"]
-    [2013-06-01 02:01:20 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:20 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:20 BST] Pusher: pushing to [Remote { name =\"Cloud\" }]
-    [2013-06-01 02:01:20 BST] call: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"branch\",\"-f\",\"synced/master\"]
-    [2013-06-01 02:01:20 BST] call: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"push\",\"Cloud\",\"git-annex:synced/git-annex\",\"master:synced/master\"]
-    [2013-06-01 02:01:20 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Nothing
-    [2013-06-01 02:01:20 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Nothing
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-
-    sync.mov
-           32768   0%    0.00kB/s    0:00:00
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git-annex..ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git-annex..4142ae6e3befdff987748a92feb65a11aecf4b63\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:21 BST] Merger: merging refs/heads/synced/master into refs/heads/master
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:21 BST] call: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init/.git/annex/merge/\",\"merge\",\"--no-edit\",\"refs/heads/synced/master\"]
-    To ssh://darren@cloud.rhymeorange.com:21/tank/git-annex/projects/
-       4142ae6..ef8dc3b2 git-annex -> synced/git-annex
-       1723064..75aa568  master -> synced/master
-    [2013-06-01 02:01:21 BST] XMPPClient: sending: NotifyPush [UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\"]
-    Already up-to-date.
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"diff-tree\",\"-z\",\"--raw\",\"--no-renames\",\"-l0\",\"-r\",\"75aa568fb7f484609a36abdf6afd84ab5aeb0f06\",\"75aa568fb7f484609a36abdf6afd84ab5aeb0f06\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git     7602176  11%    7.17MB/s    0:00:08
-    -annex..ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 7602176
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:22 BST] Merger: merging refs/remotes/Cloud/synced/master into refs/heads/master
-    [2013-06-01 02:01:22 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 7602176
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:22 BST] call: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init/.git/annex/merge/\",\"merge\",\"--no-edit\",\"refs/remotes/Cloud/synced/master\"]
-    Already up-to-date.
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"diff-tree\",\"-z\",\"--raw\",\"--no-renames\",\"-l0\",\"-r\",\"75aa568fb7f484609a36abdf6afd84ab5aeb0f06\",\"75aa568fb7f484609a36abdf6afd84ab5aeb0f06\"]
-        12943360  19%    6.11MB/s    0:00:08
-    [2013-06-01 02:01:23 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 12943360
-    [2013-06-01 02:01:23 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 12943360
-        18710528  27%    5.90MB/s    0:00:08
-    [2013-06-01 02:01:24 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 18710528
-    [2013-06-01 02:01:24 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 18710528
-        24477696  36%    5.79MB/s    0:00:07
-    [2013-06-01 02:01:25 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 24477696
-    [2013-06-01 02:01:25 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 24477696
-        30375936  44%    5.39MB/s    0:00:06
-    [2013-06-01 02:01:26 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 30375936
-    [2013-06-01 02:01:26 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 30375936
-        36143104  53%    5.49MB/s    0:00:05
-    [2013-06-01 02:01:27 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 36143104
-    [2013-06-01 02:01:27 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 36143104
-        42008576  61%    5.51MB/s    0:00:04
-    [2013-06-01 02:01:28 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 42008576
-    [2013-06-01 02:01:28 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 42008576
-        47906816  70%    5.52MB/s    0:00:03
-    [2013-06-01 02:01:29 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 47906816
-    [2013-06-01 02:01:29 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 47906816
-        53805056  79%    5.51MB/s    0:00:02
-    [2013-06-01 02:01:30 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 53805056
-        59572224  87%    5.52MB/s    0:00:01
-    [2013-06-01 02:01:31 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 59572224
-        65339392  96%    5.50MB/s    0:00:00
-    [2013-06-01 02:01:32 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 65339392
-        67924272 100%    5.61MB/s    0:00:11 (xfer#1, to-check=0/1)
-    [2013-06-01 02:01:33 BST] TransferWatcher: transfer starting: Upload UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\" /Volumes/StoragePool/Projects/init/sync.mov Just 67924272
-
-    sent 67932633 bytes  received 31 bytes  5032049.19 bytes/sec
-    total size is 67924272  speedup is 1.00
-    [2013-06-01 02:01:33 BST] Transferrer: Uploaded sync.mov
-    [2013-06-01 02:01:33 BST] Pusher: Syncing with Cloud 
-    [2013-06-01 02:01:33 BST] chat: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"hash-object\",\"-w\",\"--stdin-paths\"]
-    [2013-06-01 02:01:33 BST] feed: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"update-index\",\"-z\",\"--index-info\"]
-    [2013-06-01 02:01:33 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:33 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"write-tree\"]
-    [2013-06-01 02:01:33 BST] chat: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"commit-tree\",\"45ae1694ed9a7f54bab38405fa963859fd1c1918\",\"-p\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:33 BST] call: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"update-ref\",\"refs/heads/git-annex\",\"c22f52548a6fa05418d655906d8f182fb2d1bced\"]
-    [2013-06-01 02:01:33 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:33 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:33 BST] Pusher: pushing to [Remote { name =\"Cloud\" }]
-    [2013-06-01 02:01:33 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:33 BST] call: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"branch\",\"-f\",\"synced/master\"]
-    [2013-06-01 02:01:33 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:33 BST] call: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"push\",\"Cloud\",\"git-annex:synced/git-annex\",\"master:synced/master\"]
-    [2013-06-01 02:01:33 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git-annex..c22f52548a6fa05418d655906d8f182fb2d1bced\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:33 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:33 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git-annex..ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\",\"--oneline\",\"-n1\"]
-    To ssh://darren@cloud.rhymeorange.com:21/tank/git-annex/projects/
-       ef8dc3b2..c22f525 git-annex -> synced/git-annex
-    [2013-06-01 02:01:34 BST] XMPPClient: sending: NotifyPush [UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\"]
-    [2013-06-01 02:01:34 BST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID \"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\", transferKey = Key {keyName = \"48acd7e4d52f823c679d5adc2a1f52d18a8d1e05faecd779ec362d2f50c521dd.mov\", keyBackendName = \"SHA256E\", keySize = Just 67924272, keyMtime = Nothing}}
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git-annex..c22f52548a6fa05418d655906d8f182fb2d1bced\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:56 BST] read: git [\"--git-dir=/Volumes/StoragePool/Projects/init/.git\",\"--work-tree=/Volumes/StoragePool/Projects/init\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"]
-
-
-
-
-
-
-
-
-
-
-====
-Receiving Repo (recognises sync.mov but does not download)
-====
-
-
-    [2013-06-01 02:00:04 BST] main: starting assistant version 4.20130530-g8100cad
-
-    [2013-06-01 02:00:04 BST] TransferScanner: Syncing with Cloud 
-    Already up-to-date.
-
-    (scanning...) [2013-06-01 02:00:04 BST] Watcher: Performing startup scan
-    Already up-to-date.
-    Already up-to-date.
-    Already up-to-date.
-    Already up-to-date.
-    [2013-06-01 02:00:05 BST] Committer: Committing changes to git
-    Already up-to-date.
-    Already up-to-date.
-    To ssh://darren@cloud.rhymeorange.com:21/tank/git-annex/projects/
-       da9a4d5..4142ae6  git-annex -> synced/git-annex
-
-
-
-
-
-    (Recording state in git...)
-
-    (started...) [2013-06-01 02:00:06 BST] Pusher: Syncing with Cloud 
-    Everything up-to-date
-    [2013-06-01 02:00:07 BST] Committer: Committing changes to git
-    [2013-06-01 02:00:08 BST] Pusher: Syncing with Cloud 
-    Everything up-to-date
-    [2013-06-01 02:01:04 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"]
-    [2013-06-01 02:01:21 BST] XMPPClient: received: [\"Presence from d15/BB5939E1 Just (Element {elementName = Name {nameLocalName = \\"git-annex\\", nameNamespace = Just \\"git-annex\\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \\"push\\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \\"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\\"])], elementNodes = []})\",\"NotifyPush [UUID \\"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\\"]\"]
-    [2013-06-01 02:01:21 BST] XMPPClient: push notification for e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:21 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:21 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"fetch\",\"Cloud\"]
-    From ssh://cloud.rhymeorange.com:21/tank/git-annex/projects
-       4142ae6..ef8dc3b2 synced/git-annex -> Cloud/synced/git-annex
-       1723064..75aa568  synced/master -> Cloud/synced/master
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..4142ae6e3befdff987748a92feb65a11aecf4b63\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..3ddff95f0fdc37a75e0124ba5f965606b2f81bea\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..5e6dd0a555a5f67879e66ca1d83fe1312e87a0e1\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8a0e3fb46d23acdfe9a30e6e85823b37bfae182c\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] feed: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"update-index\",\"-z\",\"--index-info\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"diff-index\",\"--raw\",\"-z\",\"-r\",\"--no-renames\",\"-l0\",\"--cached\",\"ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"ef8dc3b251fbf6baa8149ed077703b2363b3dbc9..refs/heads/git-annex\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"update-ref\",\"refs/heads/git-annex\",\"ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..3ddff95f0fdc37a75e0124ba5f965606b2f81bea\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:22 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..5e6dd0a555a5f67879e66ca1d83fe1312e87a0e1\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8a0e3fb46d23acdfe9a30e6e85823b37bfae182c\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:23 BST] feed: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"update-index\",\"-z\",\"--index-info\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"diff-index\",\"--raw\",\"-z\",\"-r\",\"--no-renames\",\"-l0\",\"--cached\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:23 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/Cloud/master\"]
-    [2013-06-01 02:01:23 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/Cloud/synced/master\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/synced/master..refs/remotes/Cloud/synced/master\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:23 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects/.git/annex/merge/\",\"merge\",\"--no-edit\",\"refs/remotes/Cloud/synced/master\"]
-    Updating 1723064..75aa568
-    Fast-forward
-     sync.mov | 1 +
-     1 file changed, 1 insertion(+)
-     create mode 120000 sync.mov
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"diff-tree\",\"-z\",\"--raw\",\"--no-renames\",\"-l0\",\"-r\",\"172306459777930560a2cbbfd5c39ad596d93a0e\",\"75aa568fb7f484609a36abdf6afd84ab5aeb0f06\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:23 BST] Merger: merging refs/remotes/Cloud/synced/master into refs/heads/master
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:23 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects/.git/annex/merge/\",\"merge\",\"--no-edit\",\"refs/remotes/Cloud/synced/master\"]
-    Already up-to-date.
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"diff-tree\",\"-z\",\"--raw\",\"--no-renames\",\"-l0\",\"-r\",\"75aa568fb7f484609a36abdf6afd84ab5aeb0f06\",\"75aa568fb7f484609a36abdf6afd84ab5aeb0f06\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..3ddff95f0fdc37a75e0124ba5f965606b2f81bea\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..5e6dd0a555a5f67879e66ca1d83fe1312e87a0e1\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:23 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8a0e3fb46d23acdfe9a30e6e85823b37bfae182c\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] XMPPClient: received: [\"Presence from d15/BB5939E1 Just (Element {elementName = Name {nameLocalName = \\"git-annex\\", nameNamespace = Just \\"git-annex\\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \\"push\\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \\"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\\"])], elementNodes = []})\",\"NotifyPush [UUID \\"e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae\\"]\"]
-    [2013-06-01 02:01:34 BST] XMPPClient: push notification for e393d45e-c8b7-11e2-a1f9-f7c95b1b45ae
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:34 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"fetch\",\"Cloud\"]
-    From ssh://cloud.rhymeorange.com:21/tank/git-annex/projects
-       ef8dc3b2..c22f525 synced/git-annex -> Cloud/synced/git-annex
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..ef8dc3b251fbf6baa8149ed077703b2363b3dbc9\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..c22f52548a6fa05418d655906d8f182fb2d1bced\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..3ddff95f0fdc37a75e0124ba5f965606b2f81bea\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..5e6dd0a555a5f67879e66ca1d83fe1312e87a0e1\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8a0e3fb46d23acdfe9a30e6e85823b37bfae182c\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] feed: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"update-index\",\"-z\",\"--index-info\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"diff-index\",\"--raw\",\"-z\",\"-r\",\"--no-renames\",\"-l0\",\"--cached\",\"c22f52548a6fa05418d655906d8f182fb2d1bced\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"c22f52548a6fa05418d655906d8f182fb2d1bced..refs/heads/git-annex\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"update-ref\",\"refs/heads/git-annex\",\"c22f52548a6fa05418d655906d8f182fb2d1bced\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..c22f52548a6fa05418d655906d8f182fb2d1bced\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..3ddff95f0fdc37a75e0124ba5f965606b2f81bea\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:34 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..5e6dd0a555a5f67879e66ca1d83fe1312e87a0e1\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8a0e3fb46d23acdfe9a30e6e85823b37bfae182c\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:35 BST] feed: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"update-index\",\"-z\",\"--index-info\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"diff-index\",\"--raw\",\"-z\",\"-r\",\"--no-renames\",\"-l0\",\"--cached\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:35 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/Cloud/master\"]
-    [2013-06-01 02:01:35 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/Cloud/synced/master\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/synced/master..refs/remotes/Cloud/synced/master\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"symbolic-ref\",\"HEAD\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"refs/heads/master\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:35 BST] call: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects/.git/annex/merge/\",\"merge\",\"--no-edit\",\"refs/remotes/Cloud/synced/master\"]
-    Already up-to-date.
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/master\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"diff-tree\",\"-z\",\"--raw\",\"--no-renames\",\"-l0\",\"-r\",\"75aa568fb7f484609a36abdf6afd84ab5aeb0f06\",\"75aa568fb7f484609a36abdf6afd84ab5aeb0f06\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"git-annex\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..c22f52548a6fa05418d655906d8f182fb2d1bced\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8c35b10f8f42367fddc5c12fe39b30014358cd4d\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..3ddff95f0fdc37a75e0124ba5f965606b2f81bea\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..5e6dd0a555a5f67879e66ca1d83fe1312e87a0e1\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:01:35 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"log\",\"refs/heads/git-annex..8a0e3fb46d23acdfe9a30e6e85823b37bfae182c\",\"--oneline\",\"-n1\"]
-    [2013-06-01 02:02:04 BST] read: git [\"--git-dir=/Users/darren/Projects/.git\",\"--work-tree=/Users/darren/Projects\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"]
-    [2013-06-01 02:02:05 BST] XMPPClient: received: [\"Unknown message\"]
-"""]]
diff --git a/doc/bugs/restart_daemon_required/comment_4_3ce776786eca83fcb8ff94c8f6ff3eb9._comment b/doc/bugs/restart_daemon_required/comment_4_3ce776786eca83fcb8ff94c8f6ff3eb9._comment
deleted file mode 100644
index 1163fcbcf..000000000
--- a/doc/bugs/restart_daemon_required/comment_4_3ce776786eca83fcb8ff94c8f6ff3eb9._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 4"
- date="2013-06-10T21:31:04Z"
- content="""
-Darren, I'm sorry about the delay getting back to you -- I've been on vacation.
-
-> XMPPClient: received: [\"Unknown message\"]
-
-This and the versions tell me what the problem is. Version 4.20130601 made a backwards-incompatable change in its XMPP protocol.
-You need to upgrade the one that's using 4.20130522, and that'll solve that. The current build for Lion is 4.20130601, which will do. (The Lion autobuild is also building again for some time.)
-
-I forgot to mention this protocol change in the release notes, it was only in the changelog. Am doing that now.
-"""]]
diff --git a/doc/bugs/rsync_remote_shows_no_progress.mdwn b/doc/bugs/rsync_remote_shows_no_progress.mdwn
deleted file mode 100644
index 0192291f2..000000000
--- a/doc/bugs/rsync_remote_shows_no_progress.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-What steps will reproduce the problem?
-Init a annex, add rsync remote (with or without encryption, does not matter), launch annex assistant
-
-What is the expected output? What do you see instead?
-In the dashboard, no progress is recorded for the transfer. Each file stays at 0% and then disappears as it is fully transfered. I expect the progressbar to move and show the actual transfer progress.
-
-What version of git-annex are you using? On what operating system?
-git head of today, Ubuntu 12.04
-
-Please provide any additional information below.
-I looked in the source code and found some hints that the rsync progress should actually be evaluated and shown, I'm opening a bug report for this reason.
-
-[[!meta title="assistant: No progress bars for file uploads"]]
-
-> now upload progress bars work! [[done]] --[[Joey]]
diff --git a/doc/bugs/rsync_remote_shows_no_progress/comment_1_a7f5d646a924c462b987561cf6fc4318._comment b/doc/bugs/rsync_remote_shows_no_progress/comment_1_a7f5d646a924c462b987561cf6fc4318._comment
deleted file mode 100644
index 09afec65a..000000000
--- a/doc/bugs/rsync_remote_shows_no_progress/comment_1_a7f5d646a924c462b987561cf6fc4318._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.30"
- subject="comment 1"
- date="2012-09-09T20:01:53Z"
- content="""
-Yes, progress bars for uploads are not implemented yet. See [[design/assistant/progressbars]]
-"""]]
diff --git a/doc/bugs/scp_interrupt_to_background.mdwn b/doc/bugs/scp_interrupt_to_background.mdwn
deleted file mode 100644
index 381f5cd73..000000000
--- a/doc/bugs/scp_interrupt_to_background.mdwn
+++ /dev/null
@@ -1,2 +0,0 @@
-When getting a file with scp, SIGINT is blocked, exposing the git
-subcommand fork to background bug again. [[done]]
diff --git a/doc/bugs/show_version_without_having_to_be_in_a_git_repo.mdwn b/doc/bugs/show_version_without_having_to_be_in_a_git_repo.mdwn
deleted file mode 100644
index 98b9ced22..000000000
--- a/doc/bugs/show_version_without_having_to_be_in_a_git_repo.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-It'd be nice to be able to run "git annex version" -- and maybe some other
-commands, like "git annex" itself for the help text, without having to be
-inside a git repo. Right now it requires you to be in a git repo even if
-it's not a git-annex repo.
-
-> You need a newer verison of git-annex. --[[Joey]] 
-
-	joey@gnu:/>git annex version
-	git-annex version: 3.20120124
-
-[[done]]
diff --git a/doc/bugs/smarter_flood_filling.mdwn b/doc/bugs/smarter_flood_filling.mdwn
deleted file mode 100644
index 47b6942c7..000000000
--- a/doc/bugs/smarter_flood_filling.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-The assistant performs a flood fill, sending every file to every remote
-that will have it. This is naive, but it's a good way to ensure the file
-gets to every corner of the repo network that it possibly can.
-
-However, this means that locally paired computers will still upload files
-to a transfer repo, even when they're next to each other and that
-is a massive waste of bandwidth.
-
-It occurred to me this morning that there is a simple change that can avoid
-this.
-
-1. Ensure that locally paired computers have a lower cost than network
-   transfer remotes. (done)
-2. When queuing uploads, queue transfers to the lowest cost remotes first.
-   (already done)
-3. Just before starting a transfer, re-check if the transfer is still wanted.
-   (done)
-
-> [[done]]
-
-Now, unnecessary transfers to tranfer repos are avoided if it can send
-the file locally instead.
-
-It doesn't solve it for all network topologies of course. If there
-are three computers paired in a line "A --- B --- C", and all 3 share
-a transfer repo, A will still send to both B and the transfer repo
-even though B can reach C via a faster route.
-
-See also: [[assistant does not always use repo cost info when queueing downloads]]
-
-[[!tag /design/assistant]]
diff --git a/doc/bugs/softlink_mtime.mdwn b/doc/bugs/softlink_mtime.mdwn
deleted file mode 100644
index 33c0170ed..000000000
--- a/doc/bugs/softlink_mtime.mdwn
+++ /dev/null
@@ -1,57 +0,0 @@
-When adding files to git annex, softlinks are created with current atime (and ctime, etc). Instead, the atime of the added file should be used and added to the meta-data, restoring it everywhere an annex is cloned to. -- RichiH
-
-Optionally, editing the meta-data should change the times in all annexes.
-
-> Thing is, git does not preserve file timestamps much at all. 
-> It's not uncommon for a `git checkout` to or `git update` to
-> mess up timestamps. This is why things like metastore exist (and
-> metastore should work ok with git annexed files too). Trying to 
-> make annexed file symlinks have better timestamp handling than regular
-> files in git seems pointless. --[[Joey]]
-
-> > Improving an area where git is (not yet?) good at still makes sense, imo. Photos and the like need absolute timestamps more than source code which is fine with relative timestamps (local builds & updates). Maintaining global timestamps for source code could even cause a lot of unwanted effects. As it is, this issue is the only, but a major, blocker for me before I can start adapting git-annex. As I have three different use cases for it, this is a shame. Unfortunately, I don't speak any Haskell so scratching my own itch isn't do-able (without major effort and not soon, at least). Is there a realistic chance that you will tackle this nonetheless or is this WONTFIX? -- RichiH
-
->>> Not quite WONTFIX. git-annex should at least, when adding new files,
->>> preserve their timestamp in the symlink it creates.
->>>
->>> Since it doesn't have anything to do with maintaining the symlinks
->>> during an update, or a clone, etc, maintaining the permissions of them 
->>> is also out of scope, and it's best to just use metastore if you need
->>> it. Otherwise, git-annex would have to reimplement metastore, and is
->>> unlikely to do it better.
-
->>>> OK, thanks for the clarification. Would it be acceptable for you to put the timestamps into the metastore with vanilla git? If such an option existed, everyone would be able to benefit and not just me. -- RichiH
-
->>>>> I've now committed to git changes to make git-annex add make
->>>>> symlinks that reflect the original file's mtime. (It's not possible
->>>>> to set the ctime of a symlink; nor would you want to as messing with
->>>>> ctimes can break backup software ... and atime doesn't much matter.)
->>>>> 
->>>>> So all you have to do is make the pre-commit hook call
->>>>> [metastore](http://david.hardeman.nu/software.php). The hook
->>>>> would look like this: ---[[Joey]]
-
-	#!/bin/sh
-	git annex pre-commit .
-	metastore --save
-	git add .metadata
-
->>>>>> Thanks a lot. Doing this in a new git-annex repo from the start should at least ensure local consistency and I assume I can simply add a post-pull hook to restore the mtimes on all all other repositories? -- RichiH
-
->>>>>>> This is even better:
-
-    #!/bin/sh
-    if ! type metastore >/dev/null; then echo "$0: metastore is not installed; exiting"; exit 1; fi
-    git annex pre-commit .
-    metastore --save
-    git add .metadata
-
->>>>>>> -- RichiH
-
->>>>>>>> After getting to actually play with this from different machines with a bare git as central instance for several distributed repos, the metastore trick does not work. The .metadata is causing merge conflicts for every pull. I removed the "done" tag from this issue. -- RichiH
-
->>>>>>>>> softbox sounds _really_ nice. File systems need to preserve mtimes. Oviously, it would be nice if git-annex exposed this to the upper layer instead of relying on this FUSE implementation, or the next, or the other totally cool thing around the corner to implement it again and again. 
->>>>>>>>> I talked to the author of metastore; he is aware that the format is merge-unfriendly but never needed merges for himself. He is aware that this is not ideal for something like git. He does not have the time to implement a text storage instead of binary and I lack the skills to do it. If metastore is used, all it would need to do is introduce a new version of the store (it's versioned, apparently) and save metadata in text, one file per line. xattr would need to be ASCII-armoured, the rest could be plain text. I still think storing this directly in git-annex would make the most sense. Introducing a metadata storage file per storage object in .git/annex and using the object file's name as index is impossible because several softlinks might point to one object so it would need to be done per-softlink :/ -- RichiH
-
-> I think this is fixed by metamonger or something? Anyway, it's out of
-> scope for git-annex, so [[done]] --[[Joey]]
diff --git a/doc/bugs/ssh-askpass_locks_me_out_of_x_console.mdwn b/doc/bugs/ssh-askpass_locks_me_out_of_x_console.mdwn
deleted file mode 100644
index b8fd59edc..000000000
--- a/doc/bugs/ssh-askpass_locks_me_out_of_x_console.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-### Please describe the problem.
-
-Can't access X console after returning to work overnight.
-
-### What steps will reproduce the problem?
-
-1. Create git-annex remote repository, with git annex assistance, connected via ssh, using ssh-agent key for authentication.
-2. "ssh-add -D" to delete the ssh key when not attending computer. Forget to kill git-annex assistant.
-3. Lock screen with xscreeensaver.
-4. Return to work. Unlock screen. Find keyboard and mouse not responding. However there are no dialog boxes on screen.
-5. Open up text console, kill the numerous ssh-askpass processes. Find more ssh-askpass processes. Kill the git-annex processes, then kill the ssh-askpass processes. Find I can access the x console again.
-
-### What version of git-annex are you using? On what operating system?
-
-Version 5.20140320~bpo70+1 in Debian backports.
-
-### Please provide any additional information below.
-
-This isn't git-annex's fault, but it is a serious problem with using git-annex assistant.
-
-Suspect ssh-askpass isn't displaying dialog properly as it conflicts with xscreensaver, which is running at the time.
-
-Not really sure what the solution is.
-
-Unfortunately, Out of time for today, will double check this report makes sense tomorrow.
-
-> [[done]] per my comment. --[[Joey]]
diff --git a/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_1_1def05a57e25b6765b881f22bc6d82a2._comment b/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_1_1def05a57e25b6765b881f22bc6d82a2._comment
deleted file mode 100644
index 457d945d2..000000000
--- a/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_1_1def05a57e25b6765b881f22bc6d82a2._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.114"
- subject="comment 1"
- date="2014-05-01T13:56:32Z"
- content="""
-This will be fixed by [[design/assistant/sshpassword]], assuming I make it bypass the OS's IMHO superior ssh-askpass and use its own. 
-
-It would be better to file a bug on the actual program you had problems with though, which is not git-annex.
-"""]]
diff --git a/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_2_cd4869faf350c81deb1de6fa25f32876._comment b/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_2_cd4869faf350c81deb1de6fa25f32876._comment
deleted file mode 100644
index 80751a4da..000000000
--- a/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_2_cd4869faf350c81deb1de6fa25f32876._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.114"
- subject="comment 2"
- date="2014-05-01T14:04:12Z"
- content="""
-Actually, no, that is only going to handle ssh password prompting the one time needed to set up a passwordless dedicated ssh key.
-
-It may be that it makes sense to *always* set up such a key, which would bypass the normal key handling, and so avoid this problem. Currently, the assumption is that if you have gone to the bother to already set up a login to a host, without a password being needed, it makes sense for the assistant to use that configuration.
-"""]]
diff --git a/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_3_87c980feb28a05d12a259fb2b3091cdf._comment b/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_3_87c980feb28a05d12a259fb2b3091cdf._comment
deleted file mode 100644
index deface16f..000000000
--- a/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_3_87c980feb28a05d12a259fb2b3091cdf._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://johan.kiviniemi.name/"
- nickname="Johan"
- subject="comment 3"
- date="2014-05-01T20:46:18Z"
- content="""
-+1 for always setting up a key. I have had to temporarily disable a key and set up an account password or replicate what git-annex does (generate key, add pseudo host to .ssh/config, add remote, add entry to remote:.ssh/authorized_keys) manually when adding remotes a number of times.
-"""]]
diff --git a/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_4_33a367dbeb5c7bf8692a414f20d8de69._comment b/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_4_33a367dbeb5c7bf8692a414f20d8de69._comment
deleted file mode 100644
index aaddb60be..000000000
--- a/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_4_33a367dbeb5c7bf8692a414f20d8de69._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 4"
- date="2014-05-15T19:22:21Z"
- content="""
-The webapp now has a dropdown menu, which defaults to using a password you enter in the form. It still has the option to use an already configured ssh key, but this won't just happen without the user explicitly choosing it.
-
-I think that's enough to close this bug, so will do so in the sshpassword branch.
-"""]]
diff --git a/doc/bugs/ssh_connection_caching_broken_on_NTFS.mdwn b/doc/bugs/ssh_connection_caching_broken_on_NTFS.mdwn
deleted file mode 100644
index fc3168e0f..000000000
--- a/doc/bugs/ssh_connection_caching_broken_on_NTFS.mdwn
+++ /dev/null
@@ -1,66 +0,0 @@
-TL;DNR ssh connection caching seems to cause git-annex to not work on NTFS volumes.  Setting `annex.sshcaching` to `false` seems to solve the problem.
-
-## What version of git-annex are you using? On what operating system? Please provide any additional information below.
-
-* git-annex version: 3.20120629 on Debian Testing.
-* `the-repo` is located on an NTFS volume on a USB HDD.
-* `the-remote` is on the server `example.com`.
-* `example.com` is running gitolite3 v3.2-19-gb9bbb78, git 1.7.2.5, and git-annex 3.20120629~bpo60+2
-
-
-## What steps will reproduce the problem? What is the expected output? What do you see instead?
-
-Create or clone a repo onto an NTFS volume.  
-Make sure `git annex` is initialized.  
-Run some regular git operations.  These always seem to work.  
-Try git-annex operations.  
-
-Some operations work despite the error messages:
-
-    $ git annex sync
-    Control socket connect(/media/NTFSVOL/the-repo/.git/annex/ssh/git@example.com): Connection refused
-    Failed to connect to new control master
-    Command ssh ["-S","/media/NTFSVOL/the-repo/.git/annex/ssh/git@example.com","-o","ControlMaster=auto","-o","ControlPersist=yes","git@example.com","git-annex-shell 'configlist' '/~/the-repo.git'"] failed; exit code 255
-    Control socket connect(/media/NTFSVOL/the-repo/.git/annex/ssh/git@example.com): Connection refused
-    Failed to connect to new control master
-    Command ssh ["-S","/media/NTFSVOL/the-repo/.git/annex/ssh/git@example.com","-o","ControlMaster=auto","-o","ControlPersist=yes","git@example.com","git-annex-shell 'configlist' '/~/the-repo'"] failed; exit code 255
-    commit  
-    # On branch master
-    nothing to commit (working directory clean)
-    ok
-    pull the-remote 
-    ok
-    pull origin 
-    ok
-
-Other operations fail:
-
-    $ git annex copy -t the-remote the-file.jpg
-    Control socket connect(/media/NTFSVOL/the-repo/.git/annex/ssh/git@example.com): Connection refused
-    Failed to connect to new control master
-    Command ssh ["-S","/media/NTFSVOL/the-repo/.git/annex/ssh/git@example.com","-o","ControlMaster=auto","-o","ControlPersist=yes","git@example.com","git-annex-shell 'configlist' '/~/the-repo.git'"] failed; exit code 255
-    Control socket connect(/media/NTFSVOL/the-repo/.git/annex/ssh/git@example.com): Connection refused
-    Failed to connect to new control master
-    Command ssh ["-S","/media/NTFSVOL/the-repo/.git/annex/ssh/git@example.com","-o","ControlMaster=auto","-o","ControlPersist=yes","git@example.com","git-annex-shell 'configlist' '/~/the-repo'"] failed; exit code 255
-    copy the-file.jpg (checking the-remote...) Control socket connect(/media/NTFSVOL/the-repo/.git/annex/ssh/git@example.com): Connection refused
-    Failed to connect to new control master
-    (unable to check the-remote) failed
-    git-annex: copy: 1 failed
-
-Some googling revealed the errors to be stale socket files.  
-- [Three SSH Tips](http://shallowsky.com/blog/tags/ssh/)  
-- [Improving SSH (OpenSSH) connection speed with shared connections](http://protempore.net/~calvins/howto/ssh-connection-sharing/#section-03)  
-
-It appears that SSH connection caching was implemented in response to this wishlist item:  
-[wishlist: Prevent repeated password prompts for one command](http://git-annex.branchable.com/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command/)
-
-However ssh connection caching breaks things on NTFS volumes.  If I turn off connection caching, it seems to work fine
-
-    $ git config annex.sshcaching false
-
-but it would be nifty if git-annex could detect the filesystem type and do The Right Thing.
-
-Thanks for all the work on git-annex -- it's an awesome project!
-
-> [[done]], `git annex init` now probes for fifo support and disables ssh
-> connection caching if it cannot make one. --[[Joey]] 
diff --git a/doc/bugs/ssh_connection_caching_broken_on_NTFS/comment_1_54e7e12514f4c109fd57a4eb744b731a._comment b/doc/bugs/ssh_connection_caching_broken_on_NTFS/comment_1_54e7e12514f4c109fd57a4eb744b731a._comment
deleted file mode 100644
index 9219e96d3..000000000
--- a/doc/bugs/ssh_connection_caching_broken_on_NTFS/comment_1_54e7e12514f4c109fd57a4eb744b731a._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-16T20:47:02Z"
- content="""
-This failed because ssh connection caching needs fifos,
-which are not supported on NTFS. Also, the linux NTFS code behaves most strangly when asked to make a fifo; creating an empty file instead and then failing with EEXIST.
-
-In more recent versions of git-annex, you can set the `GIT_ANNEX_TMP_DIR` to point somewhere that supports fifos.
-
-Recent versions also try to detect crippled filesystems, and disable use of unix sockets along with symlinks etc.
-However, since ntfs supports symlinks, and it does not probe specially for fifo support, this won't help.
-"""]]
diff --git a/doc/bugs/ssh_keys_have_wrong_permissions___40__Ubuntu_12.04_LTS__44___current_linux_build_as_of_Mar_6th___39__14__41__.mdwn b/doc/bugs/ssh_keys_have_wrong_permissions___40__Ubuntu_12.04_LTS__44___current_linux_build_as_of_Mar_6th___39__14__41__.mdwn
deleted file mode 100644
index d03943da6..000000000
--- a/doc/bugs/ssh_keys_have_wrong_permissions___40__Ubuntu_12.04_LTS__44___current_linux_build_as_of_Mar_6th___39__14__41__.mdwn
+++ /dev/null
@@ -1,10 +0,0 @@
-### Please describe the problem.
-git annex webapp created SSH keys for remote directory. SSH keys have wrong permission (chmod 600 fixed it) and thus the key-based login to the remote fails. 
-
-### What steps will reproduce the problem?
-Creating a SSH remote using the git annex webapp. 
-
-### What version of git-annex are you using? On what operating system?
-'current linux build for amd64', downloaded Mar 6th 2014, on Ubuntu 12.04.4 LTS.
-
-> [[done]]
diff --git a/doc/bugs/ssh_keys_have_wrong_permissions___40__Ubuntu_12.04_LTS__44___current_linux_build_as_of_Mar_6th___39__14__41__/comment_1_462c377dca2484e5598a0b71d91ab64a._comment b/doc/bugs/ssh_keys_have_wrong_permissions___40__Ubuntu_12.04_LTS__44___current_linux_build_as_of_Mar_6th___39__14__41__/comment_1_462c377dca2484e5598a0b71d91ab64a._comment
deleted file mode 100644
index 92dbf283c..000000000
--- a/doc/bugs/ssh_keys_have_wrong_permissions___40__Ubuntu_12.04_LTS__44___current_linux_build_as_of_Mar_6th___39__14__41__/comment_1_462c377dca2484e5598a0b71d91ab64a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.244"
- subject="comment 1"
- date="2014-04-02T19:53:04Z"
- content="""
-This is a duplicate of [[bugs/ssh:_unprotected_private_key_file]], which was fixed on March 14th.
-"""]]
diff --git a/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__.mdwn b/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__.mdwn
deleted file mode 100644
index b6b7646c4..000000000
--- a/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__.mdwn
+++ /dev/null
@@ -1,50 +0,0 @@
-### Please describe the problem.
-
-- Add remote ssh repository (from add more repositories menu)
-- Repos sync even files, but remote repo is marked (metadata only) - there is Fail on sync with this repository.
-
-The actual issue is that UUID was not found. I checked the logs and it's obvious that git-annex-shell was not found on the remote.
-
-### What steps will reproduce the problem?
-
-I have
-Linux box with (ZSH as a primary shell) where ~/.zshrc contains "export PATH=/path/to/annex:$PATH)
-MacOSX box with (ZSH as a primary shell) where ~/.zshrc and ~/.bash contains  "export PATH=/path/to/annex:$PATH)
-
-The issue appears both directions.
-When I use ssh to connect remote host git-annex-shell is on PATH and works.
-
-I guess you don't have full shell context of the user.
-Worth to mention, that add remote repo (using a discovery - local computer) works well in the same repo.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex version 5.20140420-ga25b8bb
-
-### Please provide any additional information below.
-
-
-Can't find the original original log, but once repo created it contains "zsh:1: git-annex-shell not found" so it later switch repository to (metadata only) mode.
-
-This frequently repeat in the log:
-
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-Please make sure you have the correct access rights
-and the repository exists.
-Permission denied, please try again.
-Permission denied, please try again.
-Permission denied (publickey,password).
-fatal: Could not read from remote repository.
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; user fixed their problem and I have 
-> [[bugs/standalone_tarball_symlink_to_PATH_broken]] 
-> for the general problem. I have also improved the message git-annex
-> prints in this situation.
diff --git a/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_1_6203563196a70b8356102a48927e4ccd._comment b/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_1_6203563196a70b8356102a48927e4ccd._comment
deleted file mode 100644
index cbfa962d0..000000000
--- a/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_1_6203563196a70b8356102a48927e4ccd._comment
+++ /dev/null
@@ -1,44 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmTIL7ubr5opWM69Q5VtCxuxC2H0SSnzic"
- nickname="Petr"
- subject="Additional info"
- date="2014-04-29T05:07:26Z"
- content="""
-Not the above was done using git-annex webapp. I have also tried the same from cmdline with the same results:
-
-
-[[!format sh \"\"\"
-#Once remote added
-
-➜  test_move_bp git:(annex/direct/master) git annex enableremote macrepo
-zsh:1: command not found: git-annex-shell
-
-  Remote macrepo does not have git-annex installed; setting annex-ignore
-git-annex: Unknown special remote name.
-(No special remotes are currently known; perhaps use initremote instead?)
-
-
-#However the ssh works fine:
-
-➜  test_move_bp git:(annex/direct/master) ssh pmichalec@ape-mac-mini.local
-Last login: Tue Apr 29 06:19:29 2014
-➜  ~  which git-annex-shell
-/Applications/git-annex.app/Contents/MacOS/git-annex-shell
-➜  ~  /Applications/git-annex.app/Contents/MacOS/git-annex-shell
-git-annex-shell: bad parameters
-
-Usage: git-annex-shell [-c] command [parameters ...] [option ...]
-
-Plumbing commands:
-
-commit        DIRECTORY          commits any staged changes to the git-annex branch
-configlist    DIRECTORY          outputs relevant git configuration
-dropkey       DIRECTORY KEY ...  drops annexed content for specified keys
-gcryptsetup   DIRECTORY VALUE    sets up gcrypt repository
-inannex       DIRECTORY KEY ...  checks if keys are present in the annex
-notifychanges DIRECTORY          sends notification when git refs are changed
-recvkey       DIRECTORY KEY      runs rsync in server mode to receive content
-sendkey       DIRECTORY KEY      runs rsync in server mode to send content
-transferinfo  DIRECTORY KEY      updates sender on number of bytes of content received
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_2_cee9428c651e6574f93effed31d83fb9._comment b/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_2_cee9428c651e6574f93effed31d83fb9._comment
deleted file mode 100644
index b98420c83..000000000
--- a/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_2_cee9428c651e6574f93effed31d83fb9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.114"
- subject="comment 2"
- date="2014-04-29T21:03:41Z"
- content="""
-You need to fix your system so that git-annex-shell in in PATH automatically wheneven you ssh into it, and then it will work.
-
-I'm sorry, but I can't help you do so. I suggest you read the documentation for your login shell.
-"""]]
diff --git a/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_3_9d8f9346b8c931815fa4967835b67560._comment b/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_3_9d8f9346b8c931815fa4967835b67560._comment
deleted file mode 100644
index 03843c2a2..000000000
--- a/doc/bugs/ssh_remote_sync_only_metadata___40__git-annex-shell_not_found__41__/comment_3_9d8f9346b8c931815fa4967835b67560._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmTIL7ubr5opWM69Q5VtCxuxC2H0SSnzic"
- nickname="Petr"
- subject="SOLVED"
- date="2014-04-29T21:42:39Z"
- content="""
-You were right. 
-When executed command over SSH it does not perform login (so .**rc files are not necessarily loaded). 
-
-Zsh:
-.zprofile or rather .zshenv (is loaded, use these to set PATH)
-Note: .profile is not loaded at all (it's Bash stuff)
-
-Bash:
-.bashrc is said to be loaded but not .profile
-
-See:
-http://shreevatsa.wordpress.com/2008/03/30/zshbash-startup-files-loading-order-bashrc-zshrc-etc/
-http://superuser.com/questions/187639/zsh-not-hitting-profile
-https://wiki.archlinux.org/index.php/zsh
-"""]]
diff --git a/doc/bugs/standalone_tarball_symlink_to_PATH_broken.mdwn b/doc/bugs/standalone_tarball_symlink_to_PATH_broken.mdwn
deleted file mode 100644
index 975ea4e76..000000000
--- a/doc/bugs/standalone_tarball_symlink_to_PATH_broken.mdwn
+++ /dev/null
@@ -1,9 +0,0 @@
-Using the standalone build, on Linux, ln -s git-annex.linux/git-annex
-/usr/local/bin doesn't work, it looks at $0 and sees /usr/local/bin and
-does not find git-annex there. 
-
-I think that there is documentation or at least past advice of symlinking
-this way to install it into PATH. So need to do something about this.
-Perhaps have an installation script? --[[Joey]]
-
-[[done]]
diff --git a/doc/bugs/standalone_tarball_symlink_to_PATH_broken/comment_1_c9b41b957df03fadf76d93b23508b85e._comment b/doc/bugs/standalone_tarball_symlink_to_PATH_broken/comment_1_c9b41b957df03fadf76d93b23508b85e._comment
deleted file mode 100644
index 4bfe563be..000000000
--- a/doc/bugs/standalone_tarball_symlink_to_PATH_broken/comment_1_c9b41b957df03fadf76d93b23508b85e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 1"
- date="2014-05-16T17:20:22Z"
- content="""
-Also note that bash goes out of its way to make it stupidly hard for users to add things to PATH. There are different dotfiles that it reads in different situations, and no dotfile it reads in all situations. In particular, \"ssh somebox git-annex-shell\" will avoid reading any dotfiles that could set PATH, AFAICS.
-"""]]
diff --git a/doc/bugs/standalone_tarball_symlink_to_PATH_broken/comment_2_0cf22fe2518a52245ca4a8977aa3ed78._comment b/doc/bugs/standalone_tarball_symlink_to_PATH_broken/comment_2_0cf22fe2518a52245ca4a8977aa3ed78._comment
deleted file mode 100644
index 98a358ce5..000000000
--- a/doc/bugs/standalone_tarball_symlink_to_PATH_broken/comment_2_0cf22fe2518a52245ca4a8977aa3ed78._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 2"
- date="2014-05-16T20:25:40Z"
- content="""
-I've fixed this for Linux, as long as readlink -f is supported by the host system. Not fixed for OSX though, and needing to manually symlink things to install is really rather crap.
-"""]]
diff --git a/doc/bugs/submodule_path_problem.mdwn b/doc/bugs/submodule_path_problem.mdwn
deleted file mode 100644
index 664e246bc..000000000
--- a/doc/bugs/submodule_path_problem.mdwn
+++ /dev/null
@@ -1,56 +0,0 @@
-If a submodule isn't toplevel, git-annex breaks
-
-**What steps will reproduce the problem?**
-
-Make two non-empty repositories:
-
-    mkdir submod
-    cd submod
-    git init
-    touch README && git add README
-    git commit -a -m "first import of submodule"
-    cd ..
-
-    mkdir test
-    cd test
-    git init
-    touch README && git add README
-    git commit -a -m "first import of master"
-
-Add first repository as a non-toplevel submodule:
-
-    git submodule add ../submod lib/submod
-    
-Setup git-annex for the submodule inside the other repository:
-
-    cd lib/submod
-    git annex init
-
-**What is the expected output? What do you see instead?**
-
-Expected:
-
-    init  ok
-    (Recording state in git...)
-
-Got:
-
-    init  fatal: Could not switch to '../../../../lib': No such file or directory
-    git-annex: git config [Param "annex.uuid",Param "55D974D1-73E8-489E-B454-03D164664C82"] failed
-
-
-**What version of git-annex are you using? On what operating system?**
-
-3.20121011 compiled from git on Mac OS X 10.8
-
-
-**Please provide any additional information below.**
-
-* git-annex read the path from the "worktree" variable in the git config.
-* The git config for a submodule is storen in the main repository, e.g. "../../.git/modules/lib/submod/config"
-* The path in that config is relative to the config file: "worktree = ../../../../lib/submod"
-* Git-annex expect the path to be relative to the current directory, which is why it fails.
-
-> Impressive analysis, thanks. I've fixed handling of relative
-> core.worktree. [[done]] --[[Joey]]
-
diff --git a/doc/bugs/submodule_path_problem/comment_1_69aec9207d2e9da4bc042d3f4963d80e._comment b/doc/bugs/submodule_path_problem/comment_1_69aec9207d2e9da4bc042d3f4963d80e._comment
deleted file mode 100644
index 1ff33e36a..000000000
--- a/doc/bugs/submodule_path_problem/comment_1_69aec9207d2e9da4bc042d3f4963d80e._comment
+++ /dev/null
@@ -1,48 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkywesyg6tKBZcmxJ2EMUO89DZL1LZ7Sng"
- nickname="Peter"
- subject="comment 1"
- date="2012-10-16T12:02:27Z"
- content="""
-Not quite there yet.
-
-git-annex init works now, but there is still a problem with paths:
-
-Using the same setup as previously, git-annex init now works: 
-
-    cd lib/submod
-    git annex init
-
-But adding a file failes:
-
-    git annex add big-file
-
-Output:
-
-    add big-file (checksum...) 
-    git-annex: big-file: getFileStatus: does not exist (No such file or directory)
-    failed
-    (Recording state in git...)
-    git-annex: add: 1 failed
-
-Debug:
-
-
-[2012-10-16 13:59:26 CEST] read: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"ls-files\",\"--others\",\"--exclude-standard\",\"-z\",\"--\",\"big-file\"]
-[2012-10-16 13:59:26 CEST] read: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"diff\",\"--name-only\",\"--diff-filter=T\",\"-z\",\"--\",\"big-file\"]
-add big-file [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"check-attr\",\"-z\",\"--stdin\",\"annex.backend\",\"annex.numcopies\",\"--\"]
-(checksum...) [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"cat-file\",\"--batch\"]
-
-git-annex: big-file: getFileStatus: does not exist (No such file or directory)
-failed
-
-    [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"hash-object\",\"-w\",\"--stdin-paths\"]
-    [2012-10-16 13:59:26 CEST] feed: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"update-index\",\"-z\",\"--index-info\"]
-    [2012-10-16 13:59:26 CEST] read: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"]
-    (Recording state in git...)
-    [2012-10-16 13:59:26 CEST] read: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"write-tree\"]
-    [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"commit-tree\",\"ed2f98d7105deed7482b3dde43426c177b360131\",\"-p\",\"refs/heads/git-annex\"]
-    [2012-10-16 13:59:26 CEST] call: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"update-ref\",\"refs/heads/git-annex\",\"df49e7bef8409dff450ce549c40f4ab429ea3144\"]
-    [2012-10-16 13:59:26 CEST] chat: git [\"--git-dir=../../.git/modules/lib/submod\",\"--work-tree=/Users/ptx/tmp/test-annex/test/lib/submod\",\"cat-file\",\"--batch\"]
-    git-annex: add: 1 failed
-"""]]
diff --git a/doc/bugs/submodule_path_problem/comment_2_53d9eb28cb70b51637470175a80ddf35._comment b/doc/bugs/submodule_path_problem/comment_2_53d9eb28cb70b51637470175a80ddf35._comment
deleted file mode 100644
index a60a096e8..000000000
--- a/doc/bugs/submodule_path_problem/comment_2_53d9eb28cb70b51637470175a80ddf35._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 2"
- date="2012-10-16T20:28:03Z"
- content="""
-Cute, it was making the wrong symlink and then noticed it was broken and reverted the add. At least my error unwind works! Anyway, fixed this too.
-"""]]
diff --git a/doc/bugs/submodule_path_problem/comment_3_aa5e0f99000a5b4988bccbb2ca28353b._comment b/doc/bugs/submodule_path_problem/comment_3_aa5e0f99000a5b4988bccbb2ca28353b._comment
deleted file mode 100644
index 3f446a777..000000000
--- a/doc/bugs/submodule_path_problem/comment_3_aa5e0f99000a5b4988bccbb2ca28353b._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkywesyg6tKBZcmxJ2EMUO89DZL1LZ7Sng"
- nickname="Peter"
- subject="comment 3"
- date="2012-10-17T11:41:54Z"
- content="""
-One step closer, but still not perfect:
-
-    git annex add big-file
-    > add big-file (checksum...) ok
-    > (Recording state in git...)
-
-    git commit -a -m \"Added file\"
-    > git-annex: /Users/ptx/tmp/test-annex/test/.git/lib/submod: changeWorkingDirectory: does not exist (No such file or directory)
-
-So when applying the post-hook, git-annex is getting the wrong directory.
-
-`test/.git/lib/submod` should be `test/.git/modules/lib/submod`
-
-"""]]
diff --git a/doc/bugs/submodule_path_problem/comment_4_ab1508a5a04e2106aad5e7985775a6fa._comment b/doc/bugs/submodule_path_problem/comment_4_ab1508a5a04e2106aad5e7985775a6fa._comment
deleted file mode 100644
index c46eedf8e..000000000
--- a/doc/bugs/submodule_path_problem/comment_4_ab1508a5a04e2106aad5e7985775a6fa._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 4"
- date="2012-10-17T18:29:24Z"
- content="""
-Ok, fixed that.
-"""]]
diff --git a/doc/bugs/submodule_path_problem/comment_5_8c7539d1c11b81f5d46aa8e1c61745ae._comment b/doc/bugs/submodule_path_problem/comment_5_8c7539d1c11b81f5d46aa8e1c61745ae._comment
deleted file mode 100644
index 088517c5b..000000000
--- a/doc/bugs/submodule_path_problem/comment_5_8c7539d1c11b81f5d46aa8e1c61745ae._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkywesyg6tKBZcmxJ2EMUO89DZL1LZ7Sng"
- nickname="Peter"
- subject="comment 5"
- date="2012-11-08T10:32:26Z"
- content="""
-Great!
-
-Everything is working now, unfortunately the package in cabal and the prebuild linux packages are one day too old.
-
-Are you going to release a newer build soon?
-
-/ptx
-"""]]
diff --git a/doc/bugs/submodule_path_problem/comment_6_cacc91afcb1739dfca3a60590bb70356._comment b/doc/bugs/submodule_path_problem/comment_6_cacc91afcb1739dfca3a60590bb70356._comment
deleted file mode 100644
index 1cae4ea98..000000000
--- a/doc/bugs/submodule_path_problem/comment_6_cacc91afcb1739dfca3a60590bb70356._comment
+++ /dev/null
@@ -1,67 +0,0 @@
-[[!comment format=mdwn
- username="konubinix"
- ip="82.243.233.186"
- subject="Git annexed files symlink are wrong when submodule is not in the same path "
- date="2013-08-08T06:36:10Z"
- content="""
-Hi,
-
-First, thanks for the great tool that is git-annex!
-
-I have a problem with submodules when the git repository is not a submodule everywhere.
-
-    $ git-annex version
-    git-annex version: 4.20130802
-    ...
-
-    $ git --version
-    git version 1.8.3.2
-
-I try to have a repository has a submodule of another.
-
-    # creating the master repository
-    mkdir annex_master
-    cd annex_master/
-    git init
-    # hack: adding a file to create the master branch
-    touch start
-    git add start
-    git commit -m \"start\"
-    cd ..
-    # create another repository
-    mkdir annex_sub
-    cd annex_sub/
-    git init
-    # hack: adding a file to create the master branch
-    touch start
-    git add start
-    git commit -m \"start\"
-    # it is a annexed repository
-    git annex init sub
-    # add the other repository as submodule of the master one
-    cd ../annex_master/
-    git submodule add ../annex_sub/ module
-    cd module/
-    git annex init sub_module
-    git annex sync origin
-    # add an annexed file
-    echo test > test
-    git annex add
-    git annex sync
-    # go back to the origin repository
-    cd ../../annex_sub/
-    git annex sync
-    ls -l
-
-This returns
-test -> ../.git/modules/module/annex/objects/w8/pv/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2
-
-Actually, the file committed is correct. But the fact it points to '../.git/modules/module/...' makes the link work only if the repository is also a submodule and if this submodule is also located in the modules folder in the parent git repository.
-
-I would expect, since this repository is not an annex:
-test -> .git/annex/objects/w8/pv/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2
-
-Do you think that is possible?
-
-Thanks.
-"""]]
diff --git a/doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__.mdwn b/doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__.mdwn
deleted file mode 100644
index 3a50256db..000000000
--- a/doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__.mdwn
+++ /dev/null
@@ -1,50 +0,0 @@
-I've just come across a subtle build issue (as haskell-platform just
-got updated, I thought I might give it a try) The scenario is
-
-* OSX 10.7 (everything is up to date with xcode etc... the usual)
-* The 32bit version of Haskell Platform 2012.2
-
-The issue is when libdiskfree.c is compiled and linked to git-annex, 
-OSX defaults to a 64bit binary, thus...
-
-        Linking git-annex ...
-        ld: warning: ignoring file Utility/libdiskfree.o, file was built for unsupported file format which is not the architecture being linked (i386)
-        Undefined symbols for architecture i386:
-          "_diskfree", referenced from:
-              _UtilityziDiskFree_zdwa_info in DiskFree.o
-        ld: symbol(s) not found for architecture i386
-        collect2: ld returned 1 exit status
-        make: *** [git-annex] Error 1
-
-You can either compile up the c library in a 32bit mode if you have the 32bit 
-version of Haskell Platform installed as in the following example
-
-        laplace:git-annex jtang$ cc  -m32  -c -o Utility/libdiskfree.o Utility/libdiskfree.c
-        Utility/libdiskfree.c: In function ‘diskfree’:
-        Utility/libdiskfree.c:61: warning: ‘statfs64’ is deprecated (declared at /usr/include/sys/mount.h:379)
-        laplace:git-annex jtang$ make
-        ghc -O2 -Wall -ignore-package monads-fd -outputdir tmp -IUtility -DWITH_S3 --make git-annex Utility/libdiskfree.o
-
-        Utility/Touch.hs:1:12:
-            Warning: -#include and INCLUDE pragmas are deprecated: They no longer have any effect
-
-        Utility/Touch.hs:2:12:
-            Warning: -#include and INCLUDE pragmas are deprecated: They no longer have any effect
-
-        Utility/Touch.hs:3:12:
-            Warning: -#include and INCLUDE pragmas are deprecated: They no longer have any effect
-
-        Utility/Touch.hs:4:12:
-            Warning: -#include and INCLUDE pragmas are deprecated: They no longer have any effect
-        Linking git-annex ...
-
-Or else just install the 64bit haskell platform. I'm not too sure where
-you would but the intelligence to detect 32 or 64 outputs from the
-different compilers. I suspect checking what ghc outputs then putting in
-the appropriate -m32 or -m64 for the c compiler is the right thing to do. 
-Or just telling users to use the 64bit version of the haskell platform?
-It may also be possible to get osx's c compiler to output a universal binary 
-to give you everything, but that be going down the _being too platform 
-specific route_.
-
-> [[done]], it'll detect this and force -m32. --[[Joey]]
diff --git a/doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__/comment_1_6208e70a21a048d5423926d16e32d421._comment b/doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__/comment_1_6208e70a21a048d5423926d16e32d421._comment
deleted file mode 100644
index 11d135251..000000000
--- a/doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__/comment_1_6208e70a21a048d5423926d16e32d421._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- subject="comment 1"
- date="2012-06-04T20:02:23Z"
- content="""
-Seems you built it using `make` .. could you try instead building with cabal, ie run `cabal install git-annex` or `cabal build` in the source tree. I think cabal will probably do the right thing.
-
-I could fix the Makefile, I suppose. What does this say: `ghc -e 'print System.Info.arch'
-"""]]
diff --git a/doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__/comment_2_8765b6190e79251637bb59ba28f245c1._comment b/doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__/comment_2_8765b6190e79251637bb59ba28f245c1._comment
deleted file mode 100644
index cad802a88..000000000
--- a/doc/bugs/subtle_build_issue_on_OSX_10.7_and_Haskell_Platform___40__if_you_have_the_32bit_version_installed__41__/comment_2_8765b6190e79251637bb59ba28f245c1._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 2"
- date="2012-06-05T14:07:26Z"
- content="""
-FYI, (the follow is on OSX 10.7 on two different machines)
-
-On my 64bit install of haskell platform...
-
-    laplace:~ jtang$ ghc -e 'print System.Info.arch'
-    \"x86_64\"
-
-On my 32bit install of haskell platform...
-
-     x00:git-annex jtang$ ghc -e 'print System.Info.arch'
-    \"i386\"
-
-Running _cabal build_ or _cabal install git-annex_ as you suggest with the 32bit install does do the right thing.
-
-"""]]
diff --git a/doc/bugs/sync_--content_tries_to_copy_content_to_metadata_only_repos.mdwn b/doc/bugs/sync_--content_tries_to_copy_content_to_metadata_only_repos.mdwn
deleted file mode 100644
index 4714eac7a..000000000
--- a/doc/bugs/sync_--content_tries_to_copy_content_to_metadata_only_repos.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-### Please describe the problem.
-
-
-### What steps will reproduce the problem?
-
-git annex sync --content
-
-
-### What version of git-annex are you using? On what operating system?
-
-Mac OSX Maverics
-
-git-annex version: 5.20140127
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-
-### Please provide any additional information below.
-
-[[!format sh """
-copy Books/Paperless - Agile Bits Edition/Paperless Video/5-4 PDFpen for iPad.m4v (to origin...)
-FATAL: suspicious characters loitering about 'git-annex-shell 'recvkey' '/~/users/akraut/annex-home' 'SHA256E-s98445427--5fb5fd6e082eec4a805261764ef982aa8f12d76e07e86a6abb05e7675762ac49.m4v' '--' 'remoteuuid=03ac7aa9-d14c-4b60-adae-02e4a5ec0fa8' 'direct=' 'associatedfile=Books/Paperless - Agile Bits Edition/Paperless Video/5-4 PDFpen for iPad.m4v' '--' dummy rsync --server -v --inplace .'
-rsync: connection unexpectedly closed (0 bytes received so far) [sender]
-rsync error: the --max-delete limit stopped deletions (code 25) at /SourceCache/rsync/rsync-42/rsync/io.c(452) [sender=2.6.9]
-
-  rsync failed -- run git annex again to resume file transfer
-failed
-"""]]
-
-> From the error message, I can see that your origin repository
-> has an annex.uuid set (to "03ac7aa9-d14c-4b60-adae-02e4a5ec0fa8").
-> So, I assume that, if you don't want git-annex sync to use it,
-> you must have remote.origin.annex-ignore set to true. So, I think I fixed
-> this a day or two ago when I made sync --content honor the annex-ignore
-> setting. [[done]] --[[Joey]] 
diff --git a/doc/bugs/sync_command_tries_to_connect_new_remote_despite_not_being_asked_to.mdwn b/doc/bugs/sync_command_tries_to_connect_new_remote_despite_not_being_asked_to.mdwn
deleted file mode 100644
index 34b52213c..000000000
--- a/doc/bugs/sync_command_tries_to_connect_new_remote_despite_not_being_asked_to.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-### Please describe the problem.
-When adding a new remote which is not accessible (hence still unsynced) git annex tries to connect to it at each remote operation, even if a specific other remote is given for the command.
-
-### What steps will reproduce the problem?
-<pre>
-git init 1
-
-cd 1
-git annex init
-touch file
-git annex add file
-git commit -m"a file"
-
-git clone . ../2
-
-git remote add 2 ../2
-git annex sync 2
-</pre>
-At this point annex syncs with remote "2" and nothing else
-
-But if adding a (currently) unaccessible remote
-<pre>
-git remote add bad nobody@offline.local:nothing
-git annex sync 2
-</pre>
-gives
-<pre>
-ssh: Could not resolve hostname offline.local: Name or service not known
-ssh: Could not resolve hostname offline.local: Name or service not known
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-commit  ok
-pull 2 
-ok
-push 2 
-Everything up-to-date
-ok
-</pre>
-so annex tries to sync with the "bad" remote, even though the command tells it to only sync from "2". I would expect it to only sync with remote "2" in this case.
-### What version of git-annex are you using? On what operating system?
-git-annex version: 5.20131221
-Debian Sid
-
-> Behaving as intended. [[done]] --[[Joey]]
diff --git a/doc/bugs/sync_command_tries_to_connect_new_remote_despite_not_being_asked_to/comment_1_dcd52b57192e83fe365f21dc12461008._comment b/doc/bugs/sync_command_tries_to_connect_new_remote_despite_not_being_asked_to/comment_1_dcd52b57192e83fe365f21dc12461008._comment
deleted file mode 100644
index 57b70b47c..000000000
--- a/doc/bugs/sync_command_tries_to_connect_new_remote_despite_not_being_asked_to/comment_1_dcd52b57192e83fe365f21dc12461008._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 1"
- date="2013-12-27T18:03:11Z"
- content="""
-git-annex needs to know the uuid of a remote in order to operate. So at startup, if there is a remote that does not have an annex.uuid set, nearly any git-annex command will try to connect the the remote and query it for its uuid.
-
-To prevent this being done for a remote, `git config remote.bad.annex-ignore true`
-"""]]
diff --git a/doc/bugs/test_suite_failure_on_samba_mount.mdwn b/doc/bugs/test_suite_failure_on_samba_mount.mdwn
deleted file mode 100644
index 4bd7843a1..000000000
--- a/doc/bugs/test_suite_failure_on_samba_mount.mdwn
+++ /dev/null
@@ -1,281 +0,0 @@
-### Please describe the problem.
-
-`git annex test` show multiple failures on a samba mounted partition.
-
-### What steps will reproduce the problem?
-
-just run `git annex test` (in the mounted dir)
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130521, built for architecture `armhf` by the Raspbian maintainers ("jessie" suite at the time of writing)
-
-### Please provide any additional information below.
-
-Here are the last lines of `git annex test` output; AFAICT they are the only lines mentioning failures. Before them the output mentions `+++ OK, passed 100 tests.`.
-
-[[!format text """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-Cases: 1  Tried: 0  Errors: 0  Failures: 0----------------------------------------------------------------------
-Now, some broader checks ...
-  (Do not be alarmed by odd output here; it's normal.
-   wait for the last line to see how it went.)
-----------------------------------------------------------------------
-init
-  Detected a crippled filesystem.
-  Enabling direct mode.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-                                          Cases: 1  Tried: 1  Errors: 0  Failures: 0
-Cases: 3  Tried: 0  Errors: 0  Failures: 0Cases: 3  Tried: 1  Errors: 0  Failures: 0----------------------------------------------------------------------
-add
-  Detected a crippled filesystem.
-  Enabling direct mode.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-Cases: 3  Tried: 2  Errors: 0  Failures: 0  Detected a crippled filesystem.
-  Enabling direct mode.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-error: unable to create temporary sha1 filename : No such file or directory
-
-git-annex: user error (git ["--git-dir=/media/freebox/.t/tmprepo0/.git","--work-tree=/media/freebox/.t/tmprepo0","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] exited 1)
-                                          ### Failure in: git-annex add:2
-git annex init failed
-Cases: 3  Tried: 3  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0----------------------------------------------------------------------
-reinject
-  Detected a crippled filesystem.
-  Enabling direct mode.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-  Detected a crippled filesystem.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-                                          Cases: 1  Tried: 1  Errors: 0  Failures: 0
-Cases: 2  Tried: 0  Errors: 0  Failures: 0not supported in direct mode; skipping
-----------------------------------------------------------------------
-unannex
-  Detected a crippled filesystem.
-  Enabling direct mode.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-error: unable to create temporary sha1 filename : No such file or directory
-
-git-annex: user error (git ["--git-dir=/media/freebox/.t/tmprepo1/.git","--work-tree=/media/freebox/.t/tmprepo1","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] exited 1)
-                                          ### Failure in: git-annex unannex:0:no content
-git annex init failed
-Cases: 2  Tried: 1  Errors: 0  Failures: 1  Detected a crippled filesystem.
-  Enabling direct mode.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-  Detected a crippled filesystem.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-                                          Cases: 2  Tried: 2  Errors: 0  Failures: 1
-Cases: 3  Tried: 0  Errors: 0  Failures: 0not supported in direct mode; skipping
-----------------------------------------------------------------------
-drop
-  Detected a crippled filesystem.
-  Enabling direct mode.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-error: unable to create temporary sha1 filename : No such file or directory
-
-git-annex: user error (git ["--git-dir=/media/freebox/.t/tmprepo2/.git","--work-tree=/media/freebox/.t/tmprepo2","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] exited 1)
-                                          ### Failure in: git-annex drop:0:no remotes
-git annex init failed
-Cases: 3  Tried: 1  Errors: 0  Failures: 1  Detected a crippled filesystem.
-  Enabling direct mode.
-  Detected a filesystem without fifo support.
-  Disabling ssh connection caching.
-Cases: 3  Tried: 2  Errors: 0  Failures: 1/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex drop:2:untrusted remote
-git clone failed
-Cases: 3  Tried: 3  Errors: 0  Failures: 2
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex get
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex move
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex copy
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex unlock/lock
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 2  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex edit/commit:0
-git clone failed
-Cases: 2  Tried: 1  Errors: 0  Failures: 1/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex edit/commit:1
-git clone failed
-Cases: 2  Tried: 2  Errors: 0  Failures: 2
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex fix
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex trust/untrust/semitrust/dead
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 4  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex fsck:0
-git clone failed
-Cases: 4  Tried: 1  Errors: 0  Failures: 1/media/freebox/.t/tmprepo3/refs: No such file or directory
-                                          ### Failure in: git-annex fsck:1
-git clone failed
-Cases: 4  Tried: 2  Errors: 0  Failures: 2/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex fsck:2
-git clone failed
-Cases: 4  Tried: 3  Errors: 0  Failures: 3/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex fsck:3
-git clone failed
-Cases: 4  Tried: 4  Errors: 0  Failures: 4
-Cases: 2  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex migrate:0
-git clone failed
-Cases: 2  Tried: 1  Errors: 0  Failures: 1/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex migrate:1
-git clone failed
-Cases: 2  Tried: 2  Errors: 0  Failures: 2
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex unused/dropunused
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex describe
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex find
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex merge
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex status
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex version
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex sync
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: union merge regression
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: automatic conflict resolution
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex map
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex uninit
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex upgrade
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex whereis
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex hook remote
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex directory remote
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex rsync remote
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex bup remote
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-Cases: 1  Tried: 0  Errors: 0  Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory
-                                          ### Failure in: git-annex crypto
-git clone failed
-Cases: 1  Tried: 1  Errors: 0  Failures: 1
-----------------------------------------------------------------------
-get
-----------------------------------------------------------------------
-move
-----------------------------------------------------------------------
-copy
-----------------------------------------------------------------------
-lock
-----------------------------------------------------------------------
-edit
-----------------------------------------------------------------------
-fix
-----------------------------------------------------------------------
-trust
-----------------------------------------------------------------------
-fsck
-----------------------------------------------------------------------
-migrate
-----------------------------------------------------------------------
- unused
-----------------------------------------------------------------------
-describe
-----------------------------------------------------------------------
-find
-----------------------------------------------------------------------
-merge
-----------------------------------------------------------------------
-status
-----------------------------------------------------------------------
-version
-----------------------------------------------------------------------
-sync
-----------------------------------------------------------------------
-union merge regression
-----------------------------------------------------------------------
-conflict resolution
-----------------------------------------------------------------------
-map
-----------------------------------------------------------------------
-uninit
-----------------------------------------------------------------------
-upgrade
-----------------------------------------------------------------------
-whereis
-----------------------------------------------------------------------
-hook remote
-----------------------------------------------------------------------
-directory remote
-----------------------------------------------------------------------
-rsync remote
-----------------------------------------------------------------------
-bup remote
-----------------------------------------------------------------------
-crypto
-git-annex: .t/repo/.git/annex: removeDirectory: unsatisified constraints (Directory not empty)
-
-# End of transcript or log.
-"""]]
-
-> Since this is a git bug (or a samba bug) and not a git-annex bug, I am
-> closing it. [[done]] --[[Joey]] 
diff --git a/doc/bugs/test_suite_failure_on_samba_mount/comment_1_e074b20801b921ee2661025a050a8af2._comment b/doc/bugs/test_suite_failure_on_samba_mount/comment_1_e074b20801b921ee2661025a050a8af2._comment
deleted file mode 100644
index 623028c80..000000000
--- a/doc/bugs/test_suite_failure_on_samba_mount/comment_1_e074b20801b921ee2661025a050a8af2._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="seems like a general git problem"
- date="2013-08-24T19:55:56Z"
- content="""
-\"unable to create temporary sha1 filename\" is a git error message. I don't actually see any git-annex failure here, just a git failure that seems to lead to a cascade of other failures. 
-
-I'm not sure if the \"/media/freebox/.t/tmprepo3/.git: No such file or directory\" is because git clone has failed due to the other errors, or if git clone somehow failed to set up the .git directory.
-
-It would probably be helpful to have a play around with git on this filesystem and see what breaks. Alternatively, you can use git-annex with `--debug` to see the git commands it's running that fail, and try them yourself and perhaps strace or gdb them or something to see where they go wrong.
-"""]]
diff --git a/doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn b/doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn
deleted file mode 100644
index 2f486ad65..000000000
--- a/doc/bugs/test_suite_shouldn__39__t_fail_silently.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-When the test suite cannot be compiled, the build just fails silenty. This means that in automated builds there is no easy way to ensure that the generated binaries have passed the test suite, because it may not even have been run! IMHO, "make test" should fail (i.e. return a non-zero exit code) when it can't succeeed.
-
-> Ok, fixed. --[[Joey]] [[done]]
diff --git a/doc/bugs/tests_fail_when_there_is_no_global_.gitconfig_for_the_user.mdwn b/doc/bugs/tests_fail_when_there_is_no_global_.gitconfig_for_the_user.mdwn
deleted file mode 100644
index b90b501e3..000000000
--- a/doc/bugs/tests_fail_when_there_is_no_global_.gitconfig_for_the_user.mdwn
+++ /dev/null
@@ -1,50 +0,0 @@
-Make test fails when git doesn't know what identity to give to commits
-
-<pre>
-
-Testing 1:blackbox:0:git-annex init
-Cases: 30  Tried: 7  Errors: 0  Failures: 0
-*** Please tell me who you are.
-
-Run
-
-  git config --global user.email "you@example.com"
-  git config --global user.name "Your Name"
-
-to set your account's default identity.
-Omit --global to set the identity only in this repository.
-
-fatal: empty ident  <jtang@lenny.localdomain> not allowed
-### Failure in: 1:blackbox:0:git-annex init
-init failed
-Testing 1:blackbox:1:git-annex add:0
-Cases: 30  Tried: 8  Errors: 0  Failures: 1
-*** Please tell me who you are.
-</pre>
-
-I guess most users testing git-annex probably have a .gitconfig sitting in their home directories already so the above never cropped up. This failure was initially found in a clean and fresh install of a virtual machine with archlinux and repeated again on my archlinux laptop.
-
-Update: I pulled the master on my rhel5 test machine and moved my .gitconfig out of the way, the tests passes and continues but I still get a "warning message" from git. 
-
-<pre>
-Testing 1:blackbox:3:git-annex unannex:1:with content                         
-Cases: 30  Tried: 12  Errors: 0  Failures: 0[master fce0cde] content removed from git annex
- Committer: Jimmy Tang <jtang@removed.removed.tcd.ie>
-Your name and email address were configured automatically based
-on your username and hostname. Please check that they are accurate.
-You can suppress this message by setting them explicitly:
-
-    git config --global user.name "Your Name"
-    git config --global user.email you@example.com
-
-After doing this, you may fix the identity used for this commit with:
-
-    git commit --amend --reset-author
-
- 2 files changed, 1 insertions(+), 2 deletions(-)
- delete mode 120000 foo
-</pre>
-
-I guess it also depends a bit on how git figures out who it is is committing and how the machine in question is configured with hostnames and domain names.
-
-> Fixed that. [[done]] --[[Joey]] 
diff --git a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform.mdwn b/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform.mdwn
deleted file mode 100644
index 4088162e7..000000000
--- a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-I updated haskell platform, and now
-
-<pre>
-[jtang@x00 git-annex (master)]$ make test
-
-Assistant/Threads/NetWatcher.hs:26:2:
-     warning: #warning Building without dbus support; will poll for network connection changes [-Wcpp]
-
-Assistant/Threads/MountWatcher.hs:33:2:
-     warning: #warning Building without dbus support; will use mtab polling [-Wcpp]
-
-test.hs:11:8:
-    Could not find module `Test.HUnit.Tools'
-    Perhaps you meant Test.HUnit.Text (from HUnit-1.2.5.1)
-    Use -v to see a list of the files searched for.
-** failed to build the test suite
-make: *** [test] Error 1
-</pre>
-
-Looks like a missing dep somewhere with testpack or quickcheck... I haven't had time to figure it out yet, its not git-annex specific but I thought I might log it as a reminder for myself just in case if the osxapp is more borked than usual, I probably need to flush my .cabal directory of installed userland dependancies.
-
-> The testpack library has been broken by some other library changes. I
-> made changes in git yesterday to avoid using it. [[done]] --[[Joey]]
diff --git a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_1_20a6fe046111e9ae56fd4d9c9f41f536._comment b/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_1_20a6fe046111e9ae56fd4d9c9f41f536._comment
deleted file mode 100644
index cff4254c9..000000000
--- a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_1_20a6fe046111e9ae56fd4d9c9f41f536._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.117"
- subject="comment 1"
- date="2012-12-10T19:18:59Z"
- content="""
-Test.HUnit.Tools is part of testpack: <http://hackage.haskell.org/package/testpack>
-"""]]
diff --git a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_2_6fdc5f8b07908c6eda8a97690408f44e._comment b/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_2_6fdc5f8b07908c6eda8a97690408f44e._comment
deleted file mode 100644
index a8ed998cd..000000000
--- a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_2_6fdc5f8b07908c6eda8a97690408f44e._comment
+++ /dev/null
@@ -1,45 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 2"
- date="2012-12-11T08:29:07Z"
- content="""
-yea its a problem with testpack rather than git-annex's test suite,
-
-<pre>
-[jtang@laplace git-annex (master)]$ cabal install testpack
-Resolving dependencies...
-Configuring testpack-2.1.2...
-Building testpack-2.1.2...
-Preprocessing library testpack-2.1.2...
-[1 of 3] Compiling Test.QuickCheck.Instances ( src/Test/QuickCheck/Instances.hs, dist/build/Test/QuickCheck/Instances.o )
-[2 of 3] Compiling Test.QuickCheck.Tools ( src/Test/QuickCheck/Tools.hs, dist/build/Test/QuickCheck/Tools.o )
-
-src/Test/QuickCheck/Tools.hs:33:9:
-    Warning: Fields of `MkResult' not initialised: abort
-    In the expression:
-      MkResult
-        {ok = Just (expected == actual), expect = True,
-         interrupted = False,
-         reason = \"Result: expected \"
-                  ++ show expected ++ \", got \" ++ show actual,
-         stamp = [], callbacks = []}
-    In an equation for `@=?':
-        expected @=? actual
-          = MkResult
-              {ok = Just (expected == actual), expect = True,
-               interrupted = False,
-               reason = \"Result: expected \"
-                        ++ show expected ++ \", got \" ++ show actual,
-               stamp = [], callbacks = []}
-[3 of 3] Compiling Test.HUnit.Tools ( src/Test/HUnit/Tools.hs, dist/build/Test/HUnit/Tools.o )
-
-src/Test/HUnit/Tools.hs:131:57:
-    `maxDiscard' is not a (visible) constructor field name
-
-src/Test/HUnit/Tools.hs:177:40: Not in scope: `maxDiscard'
-cabal: Error: some packages failed to install:
-testpack-2.1.2 failed during the building phase. The exception was:
-ExitFailure 1
-</pre>
-"""]]
diff --git a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_3_014474a133c7ff0131029d8721afc710._comment b/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_3_014474a133c7ff0131029d8721afc710._comment
deleted file mode 100644
index 58bbbd91f..000000000
--- a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_3_014474a133c7ff0131029d8721afc710._comment
+++ /dev/null
@@ -1,46 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn7gQ1zZDdWhXy9H51W2krZYShNmKL3qfM"
- nickname="Karsten"
- subject="Testpack install fails on ubuntu 12.04"
- date="2013-02-28T10:42:36Z"
- content="""
-The current release (git-annex-4.20130227, via cabal) fails to install because testpack-2.1.2 fails to install:
-
-    karsten@vdr1:~$ cabal install --bindir $HOME/bin git-annex
-    Resolving dependencies...
-    Configuring testpack-2.1.2...
-    Building testpack-2.1.2...
-    Preprocessing library testpack-2.1.2...
-    [1 of 3] Compiling Test.QuickCheck.Instances ( src/Test/QuickCheck/Instances.hs, dist/build/Test/QuickCheck/Instances.o )
-    [2 of 3] Compiling Test.QuickCheck.Tools ( src/Test/QuickCheck/Tools.hs, dist/build/Test/QuickCheck/Tools.o )
-    
-    src/Test/QuickCheck/Tools.hs:33:9:
-        Warning: Fields of `MkResult' not initialised: abort
-        In the expression:
-          MkResult
-            {ok = Just (expected == actual), expect = True,
-             interrupted = False,
-             reason = \"Result: expected \"
-                      ++ show expected ++ \", got \" ++ show actual,
-             stamp = [], callbacks = []}
-        In an equation for `@=?':
-            expected @=? actual
-              = MkResult
-                  {ok = Just (expected == actual), expect = True,
-                   interrupted = False,
-                   reason = \"Result: expected \"
-                            ++ show expected ++ \", got \" ++ show actual,
-                   stamp = [], callbacks = []}
-    [3 of 3] Compiling Test.HUnit.Tools ( src/Test/HUnit/Tools.hs, dist/build/Test/HUnit/Tools.o )
-    
-    src/Test/HUnit/Tools.hs:131:57:
-        `maxDiscard' is not a (visible) constructor field name
-    
-    src/Test/HUnit/Tools.hs:177:40: Not in scope: `maxDiscard'
-    cabal: Error: some packages failed to install:
-    git-annex-4.20130227 depends on testpack-2.1.2 which failed to install.
-    testpack-2.1.2 failed during the building phase. The exception was:
-    ExitFailure 1
-
-Manually installing testpack gives Version testpack-2.1.2.1 which installs correctly. Maybe the dependencies should be updated?
-"""]]
diff --git a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_4_9c537e251dc99667fe87870804d802c2._comment b/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_4_9c537e251dc99667fe87870804d802c2._comment
deleted file mode 100644
index 0a122efaf..000000000
--- a/doc/bugs/tests_failed_to_build_-_after_an_update_of_haskell_platform/comment_4_9c537e251dc99667fe87870804d802c2._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 4"
- date="2013-02-28T19:40:11Z"
- content="""
-This is a closed bug from 2 months ago, it's the wrong place to report current problems.
-
-Anyway, I made changes in git last night to avoid using testpack, so breakage with it is no longer a concern.
-"""]]
diff --git a/doc/bugs/the_tip_at_commit_6cecc26206c4a539999b04664136c6f785211a41_disables_the_watch_command_on_OSX.mdwn b/doc/bugs/the_tip_at_commit_6cecc26206c4a539999b04664136c6f785211a41_disables_the_watch_command_on_OSX.mdwn
deleted file mode 100644
index 1ee4781d1..000000000
--- a/doc/bugs/the_tip_at_commit_6cecc26206c4a539999b04664136c6f785211a41_disables_the_watch_command_on_OSX.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-The recent commit 6cecc26206c4a539999b04664136c6f785211a41 seems to have disabled the watch command on OSX, this certainly is the case when I try to run the webapp.
-
-The following fixes the makefile
-
-<pre>
-x00:git-annex jtang$ git diff
-diff --git a/Makefile b/Makefile
-index 9f312dc..4a74e71 100644
---- a/Makefile
-+++ b/Makefile
-@@ -27,7 +27,7 @@ endif
- endif
- 
- PREFIX=/usr
--GHCFLAGS=-O2 $(BASEFLAGS) $(FEATURES)
-+GHCFLAGS=-O2 $(BASEFLAGS) $(FEATURES) $(OPTFLAGS)
- 
- ifdef PROFILE
- GHCFLAGS=-prof -auto-all -rtsopts -caf-all -fforce-recomp $(BASEFLAGS) $(FEATURES) $(OPTFLAGS)
-</pre>
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/three_character_directories_created.mdwn b/doc/bugs/three_character_directories_created.mdwn
deleted file mode 100644
index 658ad3c20..000000000
--- a/doc/bugs/three_character_directories_created.mdwn
+++ /dev/null
@@ -1,56 +0,0 @@
-What steps will reproduce the problem?
-
-I don't know how, but this happened already a second time, I don't know how to reproduce this yet.
-
-What is the expected output? What do you see instead?
-
-There are many three character name directories created that look like the parts of a hash - and each contains a logfile.
-
-    % ls
-    027
-    1d1
-    1e3
-    232
-    36e
-    583
-    5f6
-    69c
-    9ea
-    bd7
-    c46
-    d20
-    d48
-    f31
-    f88
-    uuid.log
-    [+the intended data directories]
-
-    % find 027/
-    027/
-    027//b73
-    027//b73/SHA256-s10108928--3c3766aed8b66de9d0ef37820e0ddfba25f9463b37f30e25ceb5ce3cdf12db36.log
-
-     % cat f88/7c3/SHA256-s4100608--903530747dfdc7bc9d487d7cbd8ab09ddc1ffad52c08849d049c8a5ff5cfb854.log
-    1351711677.187589s 1 2efd46d2-0e32-11e2-95fe-f73f09c6615e
-    1351971337.667243s 1 ab50cd8a-11c0-11e2-934c-87e45f64e5c6
-
-What version of git-annex are you using? On what operating system?
-
-% git-annex version
-git-annex version: 3.20121017
-local repository version: 3
-default repository version: 3
-supported repository versions: 3
-upgrade supported from repository versions: 0 1 2
-
-OS X 10.6.8
-
-Please provide any additional information below.
-
-I use a symlink to the repository to change into it.
-
-> Closing this bug as user error. If the `git-annex` branch
-> gets merged into master by the user, then that adds all its log files
-> to master, and so they're visible as regular files. Solution: Don't do
-> that, or if you do that, use `git log --stat` to find the commit that
-> adds all those files, and `git revery` the commit. [[done]] --[[Joey]]
diff --git a/doc/bugs/three_character_directories_created/comment_1_dd91de24dab4f2eaded1f7d659869d4d._comment b/doc/bugs/three_character_directories_created/comment_1_dd91de24dab4f2eaded1f7d659869d4d._comment
deleted file mode 100644
index 158fa8e9e..000000000
--- a/doc/bugs/three_character_directories_created/comment_1_dd91de24dab4f2eaded1f7d659869d4d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.27"
- subject="comment 1"
- date="2012-11-10T00:36:49Z"
- content="""
-The three character directories, as well as the uuid.log file are supposed to stay in the git-annex branch. Perhaps you have somehow merged that branch into your master branch? I recommend you look at the history of your git repository to see how it happened. It seems very unlikely that git-annex did this.
-"""]]
diff --git a/doc/bugs/three_character_directories_created/comment_2_f6375964a6c8bb1e6c5b7238effca66d._comment b/doc/bugs/three_character_directories_created/comment_2_f6375964a6c8bb1e6c5b7238effca66d._comment
deleted file mode 100644
index 800a276f2..000000000
--- a/doc/bugs/three_character_directories_created/comment_2_f6375964a6c8bb1e6c5b7238effca66d._comment
+++ /dev/null
@@ -1,62 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmmPHsszTlpa3s3x_LEzmEYkZfEmqq7IjU"
- nickname="Jan"
- subject="happened again"
- date="2012-11-12T15:57:20Z"
- content="""
-It just happened again to me, on another computer:
-
-<pre>
-    % git annex sync
-    (merging synced/git-annex into git-annex...)
-    commit  
-    add PATH/FILE (checksum...) ok
-    ok
-    add PATH/SUBPATH/FILE (checksum...) ok
-    ok
-    (Recording state in git...)
-    [master 93c4526] git-annex automatic sync
-    2 files changed, 2 insertions(+), 2 deletions(-)
-    ok
-    merge synced/master 
-    CONFLICT (modify/delete): PATH/FILE deleted in refs/heads/synced/master and modified in HEAD. Version HEAD of PATH/FILE left in tree.
-    Automatic merge failed; fix conflicts and then commit the result.
-    failed
-    pull origin 
-    remote: Counting objects: 71, done.
-    remote: Compressing objects: 100% (51/51), done.
-    remote: Total 64 (delta 25), reused 52 (delta 13)
-    Unpacking objects: 100% (64/64), done.
-    From host:git/repo
-      03d4b1f..c800e83  master     -> origin/master
-      61239fb..6d8ae6b  git-annex  -> origin/git-annex
-      69914b0..61239fb  synced/git-annex -> origin/synced/git-annex
-      03d4b1f..2137ab9  synced/master -> origin/synced/master
-
-    error: 'merge' is not possible because you have unmerged files.
-    hint: Fix them up in the work tree,
-    hint: and then use 'git add/rm <file>' as
-    hint: appropriate to mark resolution and make a commit,
-    hint: or use 'git commit -a'.
-    fatal: Exiting because of an unresolved conflict.
-    failed
-    push origin 
-    Counting objects: 26, done.
-    Delta compression using up to 4 threads.
-    Compressing objects: 100% (14/14), done.
-    Writing objects: 100% (17/17), 1.47 KiB, done.
-    Total 17 (delta 5), reused 0 (delta 0)
-    To host:git/repo.git
-      6d8ae6b..37eb875  git-annex -> git-annex
-    ! [rejected]        master -> synced/master (non-fast-forward)
-    error: failed to push some refs to 'host:git/repo.git'
-    To prevent you from losing history, non-fast-forward updates were rejected
-    Merge the remote changes (e.g. 'git pull') before pushing again.  See the
-    'Note about fast-forwards' section of 'git push --help' for details.
-    failed
-    git-annex: sync: 3 failed
-</pre>
-
-git status was showing all the 3 character directories and new files. I commited to git the path I actually wanted to commit, ran a git annex sync again and now my status is clean, but the directories are there. Am I doing something wrong this way?
-
-"""]]
diff --git a/doc/bugs/three_character_directories_created/comment_3_776e0a9b938d8b260a5111594b442536._comment b/doc/bugs/three_character_directories_created/comment_3_776e0a9b938d8b260a5111594b442536._comment
deleted file mode 100644
index 92f8f8892..000000000
--- a/doc/bugs/three_character_directories_created/comment_3_776e0a9b938d8b260a5111594b442536._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn9JRcJ_69McoLFe5-dvTMdfS9rJpGy6JI"
- nickname="Warren"
- subject="this just happened to me as well"
- date="2013-03-29T23:28:05Z"
- content="""
-I was trying to undo some changes from another bare repo, and then all of a sudden the three letter directories popped up.  I think the way I did this was to hard reset the master and git-annex branches to the same commit.  I take it that was the wrong thing to do?  I take it the git-annex and master branch should never be merged?
-"""]]
diff --git a/doc/bugs/three_character_directories_created/comment_4_e288bacdb336c4886adb6eeb4dca1e92._comment b/doc/bugs/three_character_directories_created/comment_4_e288bacdb336c4886adb6eeb4dca1e92._comment
deleted file mode 100644
index b7ca8bc03..000000000
--- a/doc/bugs/three_character_directories_created/comment_4_e288bacdb336c4886adb6eeb4dca1e92._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn9JRcJ_69McoLFe5-dvTMdfS9rJpGy6JI"
- nickname="Warren"
- subject="solved the problem"
- date="2013-03-30T00:13:29Z"
- content="""
-Just wanted to let future searchers know that I solved this problem by finding the most recent commit of the master that was not merged with the git-annex branch and hard resetting to that.  I hard reset the git-annex branch to its most recent separate commit and now things seem to working again.  By hard reset I mean the command \"git reset --hard <commit>\".
-"""]]
diff --git a/doc/bugs/three_character_directories_created/comment_5_359b80948ac92a0f1eb695599456486c._comment b/doc/bugs/three_character_directories_created/comment_5_359b80948ac92a0f1eb695599456486c._comment
deleted file mode 100644
index 6942efe52..000000000
--- a/doc/bugs/three_character_directories_created/comment_5_359b80948ac92a0f1eb695599456486c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-03-30T18:01:28Z"
- content="""
-Clearly this can happen if the git-annex branch is merged into the master branch. I cannot think of any valid reason to want to do that. reset --hard git-annex would also do it; ditto.
-
-Inclined to close this bug as user error; I'm pretty sure git-annex does not contain a bug that makes it merge in the git-annex branch on its own. Basically the only change that could be made to git-annex to prevent this kind of user error is to move the git-annex branch so it's not under refs/heads, and so is not a visible branch. But then `git push` would not push it either, which needs to happen.
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber.mdwn b/doc/bugs/three_way_sync_via_S3_and_Jabber.mdwn
deleted file mode 100644
index e67291ca9..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber.mdwn
+++ /dev/null
@@ -1,119 +0,0 @@
-## What steps will reproduce the problem?
-
-I wanted to setup a `~/Desktop/annex` synchronised between three machines, my home desktop (`dagon`), my work desktop (`zakaz`) and my laptop (`hastur`).
-
-I set this up via the annex interface, using my gmail account and Amazon S3.
-
-## What is the expected output? What do you see instead?
-
-I expected that anything dropped into `~/Desktop/annex` on any of the three machines would be synced to the other 2.
-
-I ran:
-<pre>
-    $ echo Created on `hostname` > `hostname`.txt on each of the three machines.
-</pre>
-
-What I ended up with was:
-
-* Home desktop (`dagon`): dagon.txt (ok)
-* Work desktop (`zakaz`): zakaz.txt (ok) and hastur.txt (broken link)
-* Laptop (`hastur`): hastur.txt (ok) and zakaz.txt (broken link)
-
-In each case the local file had been detected and annexed -- "(ok)" means it is a symlink to the annex.
-
-Manually running `git annex sync` on any of the machines didn't change anything. Running `git annex copy --auto --from=DesktopAnnex` on the Work desktop synced the broken hastur.txt but dagon.txt didn't appear. Running the same on my laptop did nothing. Likewise on my home desktop it did nothing. (I'm not sure if running stuff from the CLI is valid when the assistant is running, but I couldn't see a "force refresh" option in the UI)
-
-In the `git log --oneline` my laptop and Work machines both have:
-<pre>
-3f541e5 Merge commit 'refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/master'
-cbee12b 
-dddc4f0 
-d8854e7 Merge commit 'refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/master'
-</pre>
-
-While my home desktop has:
-<pre>
-43a80d5 git-annex automatic sync
-46328db 
-d8854e7 Merge commit 'refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/master'
-</pre>
-
-There are other commits prior to d8854e7 which appear to be the same on all hosts. d8854e7 was committed in December when I first played with this stuff. All the commits after that were made today as part of the experiment above, with the exception of 43a80d5 on my home desktop with was the removal of a "Test.txt" created last year. This removal also didn't sync to the other two machines.
-
-git-annex status on my home desktop (dagon) shows:
-<pre>
-semitrusted repositories: 5
-	00000000-0000-0000-0000-000000000001 -- web
- 	1167ef76-4791-11e2-9bfe-4319f44b8a5f -- annex on hastur
- 	54f6febc-4791-11e2-952f-13bd7a1c79f1 -- here (annex on dagon)
- 	552d29fe-4a86-11e2-819a-9f61585ee7a2 -- ian.james.campbell (annex on zakaz)
- 	ad5c6a4c-4791-11e2-b9f0-53f8af10a9e6 -- DesktopAnnex
-</pre>
-(DesktopAnnex is the S3 remote, ian.james.campbell is my gmail username)
-
-However the webapp only shows 3 repos:
-<pre>
-	here (annex on dagon)
-	ian.james.campbell (annex on zakaz)
-	DesktopAnnex
-</pre>
-
-git-annex status on my laptop (hastur) shows only:
-<pre>
-	00000000-0000-0000-0000-000000000001 -- web
- 	1167ef76-4791-11e2-9bfe-4319f44b8a5f -- here (ijc@hastur:~/Desktop/annex)
- 	54f6febc-4791-11e2-952f-13bd7a1c79f1 -- ian.james.campbell (ijc@dagon:~/Desktop/annex)
- 	ad5c6a4c-4791-11e2-b9f0-53f8af10a9e6 -- DesktopAnnex
-</pre>
-
-while the webapp shows:
-<pre>
-	here (ijc@hastur:~/Desktop/annex)
-	ian.james.campbell (ijc@dagon:~/Desktop/annex)
-	DesktopAnnex
-</pre>
-
-Lastly on my work desktop (zakaz) annex status shows:
-<pre>
-	00000000-0000-0000-0000-000000000001 -- web
- 	1167ef76-4791-11e2-9bfe-4319f44b8a5f -- annex on hastur
- 	54f6febc-4791-11e2-952f-13bd7a1c79f1 -- ian.james.campbell (annex on dagon)
- 	552d29fe-4a86-11e2-819a-9f61585ee7a2 -- here (annex on zakaz)
- 	ad5c6a4c-4791-11e2-b9f0-53f8af10a9e6 -- DesktopAnnex
-</pre>
-
-The webapp shows:
-<pre>
- 	here (annex on zakaz)
- 	ian.james.campbell (annex on dagon)
- 	DesktopAnnex 
-</pre>
-
-git-annex sync on any of them shows:
-<pre>
-$ git annex sync
-commit  
-# On branch master
-nothing to commit (working directory clean)
-ok
-pull ian.james.campbell 
-fatal: Unable to find remote helper for 'xmpp'
-failed
-push ian.james.campbell 
-fatal: Unable to find remote helper for 'xmpp'
-failed
-git-annex: sync: 2 failed
-</pre>
-
-## What version of git-annex are you using? On what operating system?
-
-3.20121211 on Debian Sid. All machines are amd64
-
-## Please provide any additional information below.
-
-I'm not 100% sure this sort of multiway synching is supposed to work, so maybe this is just as expected. If this isn't a bug you could consider it a feature request though ;-)
-
-This issue also made me wonder about how one would go about syncing multiple unrelated annexes via XMPP. Would you need a different gmail account for each? Maybe there is a trick similar to the email local+foo@ thing?
-
-> [[done]], turned out I left XMPP git push working,
-> but had not done all the stuff around it to get reliable syncing. Now have. --[[Joey]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_10_fc5ec5505f141bb9135e772d1094bc4d._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_10_fc5ec5505f141bb9135e772d1094bc4d._comment
deleted file mode 100644
index c611b7d6e..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_10_fc5ec5505f141bb9135e772d1094bc4d._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 10"
- date="2013-03-06T20:35:43Z"
- content="""
-I've been revisiting the XMPP stuff this week, and today I fixed at least 3 problems that would keep XMPP sync from happening reliably. This would affect machines that are using XMPP and are sometimes disconnected from the net (or suspended). Nothing caused a sync to happen when restarting the assistant, or resuming from a network disconnection. This could result in both files not showing up, and file contents not being transferred, depending on the case hit.
-
-I think it explains everything in this bug report, hopefully.
-
-(All XMPP nodes sync with all other nodes, BTW.)
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_11_0df2210c30dec6d88d7858d93eec19a3._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_11_0df2210c30dec6d88d7858d93eec19a3._comment
deleted file mode 100644
index 0ed43cc41..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_11_0df2210c30dec6d88d7858d93eec19a3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhjlfoU21OiXKH_MXw75Uq5EsX7LJW5p0"
- nickname="Ian"
- subject="comment 11"
- date="2013-03-10T08:33:26Z"
- content="""
-Thanks Joey! I'll hopefully manage to give the new version a try after my current batch of traveling.
-
-From the sounds of things I can expect it to just work now, rather than requiring some manual step to kick it out of its current state?
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_1_41682b2e72e657e0f23af244f8345e85._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_1_41682b2e72e657e0f23af244f8345e85._comment
deleted file mode 100644
index 382dcee6a..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_1_41682b2e72e657e0f23af244f8345e85._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 1"
- date="2013-01-12T14:34:34Z"
- content="""
-    fatal: Unable to find remote helper for 'xmpp'
-
-is probably why things are not working for you. git annex sync is not actually syncing because of that.
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_2_c7b4ea9aea6839763eb8b89e8d6a5ad5._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_2_c7b4ea9aea6839763eb8b89e8d6a5ad5._comment
deleted file mode 100644
index 5eea53d19..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_2_c7b4ea9aea6839763eb8b89e8d6a5ad5._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhjlfoU21OiXKH_MXw75Uq5EsX7LJW5p0"
- nickname="Ian"
- subject="comment 2"
- date="2013-01-12T14:47:07Z"
- content="""
-@Justin,
-
-It seems to be synching a least something over this channel, e.g. my work desktop and laptop seem to be keeping the git side in sync at least (I think the broken symlinks appearing and the copy --from working show this?).
-
-In the pairing window (under Config->Share with a friend) it shows ian.james.campbell as being \"paired\" on all three machines.
-
-I have a feeling there isn't supposed to be a remote helper for xmpp and the assistant is expected to take care of this through other means, IOW I shouldn't be running `git annex sync` by hand at all.
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_3_063f5e5e554ad6710f16394906d87616._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_3_063f5e5e554ad6710f16394906d87616._comment
deleted file mode 100644
index fd129a468..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_3_063f5e5e554ad6710f16394906d87616._comment
+++ /dev/null
@@ -1,33 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.7.238"
- subject="comment 3"
- date="2013-01-14T17:40:51Z"
- content="""
-`git annex sync` cannot sync xmpp remotes. Only the assistant can do that. So that's a red herring indeed..
-
-I've replicated the same setup with 3 repositories all paired using a single jabber account.
-In my test, all 3 stay in sync, with any change to one git repository being synced to the other 2.
-
-I checked the XMPP sync protocol, and it doesn't use the UUIDs at all for XMPP syncing, so the fact that `.git/config` only has the UUID of one of the two repositories that is accessible via XMPP in this case, should not matter. That is, though, why the webapp only shows one of the other two repositories; it's using that UUID information.
-
-Dagon seems to be where the problem is occuring; it's not managing to sync out its changes via XMPP.
-I think the thing to do is create another new file on dagon, and look at its `.git/annex/daemon.log`.
-You should see two xmpp pushes happen, which would look rather like this:
-
-<pre>
-To xmpp::you@gmail.com
-   a7549be..011ccc2  git-annex -> refs/synced/9346f5a8-5e63-11e2-bd8b-77356d7f5bd0/git-annex
-   3acca89..5123067  master -> refs/synced/9346f5a8-5e63-11e2-bd8b-77356d7f5bd0/master
-Counting objects: 12, done.
-Delta compression using up to 2 threads.
-Compressing objects: 100% (6/6), done.
-Writing objects: 100% (7/7), 622 bytes, done.
-Total 7 (delta 3), reused 0 (delta 0)
-To xmpp::you@gmail.com
-   a7549be..011ccc2  git-annex -> refs/synced/9346f5a8-5e63-11e2-bd8b-77356d7f5bd0/git-annex
-   3acca89..5123067  master -> refs/synced/9346f5a8-5e63-11e2-bd8b-77356d7f5bd0/master
-</pre>
-
-If you don't see both pushes, maybe you'll see a useful error message.
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_4_197ad39b4a46936afeeb04eb26cf1ef3._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_4_197ad39b4a46936afeeb04eb26cf1ef3._comment
deleted file mode 100644
index 113e5f911..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_4_197ad39b4a46936afeeb04eb26cf1ef3._comment
+++ /dev/null
@@ -1,138 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhjlfoU21OiXKH_MXw75Uq5EsX7LJW5p0"
- nickname="Ian"
- subject="comment 4"
- date="2013-01-14T19:52:16Z"
- content="""
-Looking at the annex on dagon this evening (before trying the experiment you suggested) I see that dagon.txt and hastur.txt are present and correct while zakaz.txt is a broken symlink. On both hastur and zakaz dagon.txt has appeared as a broken link. The git history is now in sync across all three devices (according to `git log`)
-
-I hadn't touched anything since I reported the bug. Looking in the .git/annex/daemon.log on dagon I see:
-
-<pre>
-scanning...) (started...) 
-  No known network monitor available through dbus; falling back to polling
-Already up-to-date.
-Already up-to-date.
-Already up-to-date.
-fatal: unresolved deltas left after unpacking
-fatal: Unable to find remote helper for 'xmpp'
-To xmpp::ian.james.campbell@gmail.com
-   794532e..ea12017  git-annex -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex
-   d8854e7..43a80d5  master -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/master
-(merging refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex into git-annex...)
-Updating 43a80d5..81afdca
-Fast-forward
- hastur.txt |    1 +
- zakaz.txt  |    1 +
- 2 files changed, 2 insertions(+)
- create mode 120000 hastur.txt
- create mode 120000 zakaz.txt
-(Recording state in git...)
-# On branch master
-nothing to commit (working directory clean)
-Already up-to-date.
-(Recording state in git...)
-# On branch master
-nothing to commit (working directory clean)
-To xmpp::ian.james.campbell@gmail.com
-   ea12017..a6efff5  git-annex -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex
-   43a80d5..81afdca  master -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/master
-(Recording state in git...)
-To xmpp::ian.james.campbell@gmail.com
-   a6efff5..931c11b  git-annex -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex
-fatal: Unable to find remote helper for 'xmpp'
-Everything up-to-date
-fatal: Unable to find remote helper for 'xmpp'
-Everything up-to-date
-fatal: Unable to find remote helper for 'xmpp'
-Everything up-to-date
-fatal: Unable to find remote helper for 'xmpp'
-git-annex: /home/ijc/Desktop/annex/.git/annex/tmp/xmppgit/git-remote-xmpp: openFile: resource busy (file is locked)
-fatal: The remote end hung up unexpectedly
-error: Ref refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex is at 931c11bc8f974934026f005ac63596d078e044ea but expected 8da50426cced18713b1deb8ea6bb0420cadf1076
-error: Ref refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/master is at 81afdca7c69e689d34cc3fc729e1e4ec5d0fcc33 but expected 3f541e58b726ef2f46bd55bfb8e955e1418b33cb
-Already up-to-date.
-fatal: Unable to find remote helper for 'xmpp'
-fatal: cannot exec 'git-remote-xmpp': Text file busy
-fatal: The remote end hung up unexpectedly
-error: Ref refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex is at 931c11bc8f974934026f005ac63596d078e044ea but expected 8da50426cced18713b1deb8ea6bb0420cadf1076
-error: Ref refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/master is at 81afdca7c69e689d34cc3fc729e1e4ec5d0fcc33 but expected 3f541e58b726ef2f46bd55bfb8e955e1418b33cb
-fatal: Unable to find remote helper for 'xmpp'
-Everything up-to-date
-fatal: Unable to find remote helper for 'xmpp'
-Everything up-to-date
-fatal: Unable to find remote helper for 'xmpp'
-git-annex: <socket: 8>: hWaitForInput: resource vanished (Connection reset by peer)
-fatal: Unable to find remote helper for 'xmpp'
-git-annex: <socket: 8>: hPutBuf: resource vanished (Broken pipe)
-git-annex: forkProcess: interrupted
-</pre>
-
-I also notice that the annex assistant doesn't seem to be running on dagon any more and the webapp window says \"git annex has shutdown, you can now close this window\". The assistant is running on zakaz and hastur.
-
-On dagon I ran `/usr/bin/git-annex assistant --autostart`. THe daemon.log now contains:
-<pre>
-(scanning...) (started...) 
-  No known network monitor available through dbus; falling back to polling
-Already up-to-date.
-Already up-to-date.
-Already up-to-date.
-drop DesktopAnnex hastur.txt (gpg) ok
-</pre>
-I suppose this makes sense since hastur.txt is the only file present on all three devices, so it makes sense to remove it from the transfer repo.
-
-On zakaz the daemon.log is full of things like:
-<pre>
-gpg: cannot open tty `/dev/tty': No such device or address
-Already up-to-date.
-gpg: cannot open tty `/dev/tty': No such device or address
-fatal: protocol error: expected sha/ref, got '^A000eunpack ok
-0042ok refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex
-003fok refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/master
-0000'
-send-pack: protocol error: bad band #56
-fatal: The remote end hung up unexpectedly
-fatal: The remote end hung up unexpectedly
-fatal: Unable to find remote helper for 'xmpp'
-gpg: cannot open tty `/dev/tty': No such device or address
-gpg: cannot open tty `/dev/tty': No such device or address
-fatal: The remote end hung up unexpectedly
-</pre>
-There are lots of the tty message and also some `git-annex: fd:97: hClose: resource vanished (Broken pipe)`.
-
-Hastur doesn't seem to have a daemon.log, although the daemon is running AFAICT.
-
-BTW something else I noticed is that there are quite a few defunct git children of the annex processes.
-
-e.g. on dagon `ps auxf | grep [g]it`:
-<pre>
-ijc       8792  0.0  0.3 157396 29752 ?        Sl   19:40   0:00 git-annex assistant
-ijc       8795  0.0  0.0      0     0 ?        Z    19:40   0:00  \_ [git] <defunct>
-ijc       8817  0.0  0.0      0     0 ?        Z    19:40   0:00  \_ [git] <defunct>
-ijc       8874  0.0  0.0  14156  1332 ?        S    19:41   0:00  \_ git --git-dir=/home/ijc/Desktop/annex/.git --work-tree=/home/ijc/Desktop/annex cat-file --batch
-ijc       8875  0.0  0.0  14132  1100 ?        S    19:41   0:00  \_ git --git-dir=/home/ijc/Desktop/annex/.git --work-tree=/home/ijc/Desktop/annex check-attr -z --stdin annex.backend annex.numcopies --
-ijc       8908  0.0  0.0      0     0 ?        Z    19:41   0:00  \_ [git] <defunct>
-</pre>
-
-(I only restarted the daemon just now)
-
-On zakaz:
-<pre>
-ianc     32004  0.0  0.5 229620 21708 ?        Sl   Jan12   3:04 git-annex assistant
-ianc     32007  0.0  0.0      0     0 ?        Z    Jan12   0:00  \_ [git] <defunct>
-ianc     32021  0.0  0.0      0     0 ?        Z    Jan12   0:00  \_ [git] <defunct>
-ianc     32106  0.0  0.0      0     0 ?        Z    Jan12   0:00  \_ [git] <defunct>
-ianc     32107  0.0  0.0  13652   924 ?        S    Jan12   0:00  \_ git --git-dir=/home/ianc/Desktop/annex/.git --work-tree=/home/ianc/Desktop/annex check-attr -z --stdin annex.backend annex.numcopies --
-ianc     32113  0.0  0.0  13652  1156 ?        S    Jan12   0:00  \_ git --git-dir=/home/ianc/Desktop/annex/.git --work-tree=/home/ianc/Desktop/annex cat-file --batch
-ianc     32258  0.0  0.0      0     0 ?        Z    Jan12   0:00  \_ [git] <defunct>
-ianc     32377  0.0  0.0      0     0 ?        Z    Jan12   0:00  \_ [git] <defunct>
-ianc       453  0.0  0.0      0     0 ?        Z    Jan12   0:00  \_ [git] <defunct>
-ianc       530  0.0  0.0      0     0 ?        Z    Jan12   0:00  \_ [git] <defunct>
-ianc      6681  0.0  0.0      0     0 ?        Z    Jan13   0:00  \_ [git] <defunct>
-ianc      6697  0.0  0.0      0     0 ?        Z    Jan13   0:00  \_ [git] <defunct>
-ianc     32232  0.0  0.4 128952 16340 ?        Sl   Jan12   0:00 git-annex xmppgit
-ianc     32239  0.0  0.4 128952 16340 ?        Sl   Jan12   0:00 git-annex xmppgit
-</pre>
-
-I'm going to create a new file on dagon as requested now. I'll post the results in a separate comment.
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_5_0b0d829ccd255be0177ae9d8f6b10e63._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_5_0b0d829ccd255be0177ae9d8f6b10e63._comment
deleted file mode 100644
index 045139544..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_5_0b0d829ccd255be0177ae9d8f6b10e63._comment
+++ /dev/null
@@ -1,61 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhjlfoU21OiXKH_MXw75Uq5EsX7LJW5p0"
- nickname="Ian"
- subject="comment 5"
- date="2013-01-14T20:04:02Z"
- content="""
-Here is the result of running `echo Foo > ~/Desktop/annex/dagon2.txt` on dagon.
-
-In dagon's daemon.log:
-<pre>
-add dagon2.txt (checksum...) (Recording state in git...)
-(Recording state in git...)
-Already up-to-date.
-To xmpp::ian.james.campbell@gmail.com
-   0bf7dc2..0182e26  git-annex -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex
-   c1e1f70..2711f11  master -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/master
-(merging refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/git-annex into git-annex...)
-Already up-to-date.
-</pre>
-
-Nothing appeared in zakaz's log. As I mentioned in the previous comment hastur doesn't seem to have a log (should this worry me?).
-
-The new file appeared on dagon and hastur but not zakaz (not even as a broken link).
-
-I tried a couple more times (dagon3 and dagon4) with the same effect.
-
-Since zakaz now appears to be the host which is playing up I then tried `echo Foo > zakaz2.2txt` on zakaz.
-
-The log on zakaz said:
-<pre>
-add zakaz2.2txt (checksum...) gpg: cannot open tty `/dev/tty': No such device or address
-gpg: cannot open tty `/dev/tty': No such device or address
-(Recording state in git...)
-(Recording state in git...)
-gpg: cannot open tty `/dev/tty': No such device or address
-gpg: cannot open tty `/dev/tty': No such device or address
-</pre>
-
-and dagon:
-<pre>
-(merging refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex into git-annex...)
-(Recording state in git...)
-Merge made by the 'recursive' strategy.
- zakaz2.2txt |    1 +
- 1 file changed, 1 insertion(+)
- create mode 120000 zakaz2.2txt
-(Recording state in git...)
-# On branch master
-nothing to commit (working directory clean)
-(merging refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/git-annex into git-annex...)
-(Recording state in git...)
-Already up-to-date!
-Merge made by the 'recursive' strategy.
-Already up-to-date.
-To xmpp::ian.james.campbell@gmail.com
-   d220ce6..4e8647f  git-annex -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex
-   b2a84e4..ef0a200  master -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/master
-</pre>
-
-However zakaz2.2txt is a broken symlink on both hastur and dagon.
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_6_37a8e19440c764317589bc4248cbccdf._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_6_37a8e19440c764317589bc4248cbccdf._comment
deleted file mode 100644
index 827ca8f63..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_6_37a8e19440c764317589bc4248cbccdf._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhjlfoU21OiXKH_MXw75Uq5EsX7LJW5p0"
- nickname="Ian"
- subject="comment 6"
- date="2013-01-14T20:14:57Z"
- content="""
-FYI I've waited a bit and zakaz2.2txt hasn't been syned to either of the other two machines (as appeared to happen after the initial report). Obviously I could wait longer 
-
-Just thought I'd mention it since I'm going offline now which is going to involve hibernating hastur (I suppose I should have mentioned that I do this quite regularly in case it matters). dagon and zakaz will remain on and connected to the net (just me and hastur which are going offline).
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_7_12eb333327d31ca2bfee3f3c5e26d641._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_7_12eb333327d31ca2bfee3f3c5e26d641._comment
deleted file mode 100644
index e93738bd9..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_7_12eb333327d31ca2bfee3f3c5e26d641._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhjlfoU21OiXKH_MXw75Uq5EsX7LJW5p0"
- nickname="Ian"
- subject="comment 7"
- date="2013-01-28T19:51:06Z"
- content="""
-I've upgraded to 3.20130124 and everything appears to be fine now.
-
-However .git/annex/daemon.log has loads of 
-<pre>
-usage: git rm [options] [--] <file>...
-
-    -n, --dry-run         dry run
-    -q, --quiet           do not list removed files
-    --cached              only remove from the index
-    -f, --force           override the up-to-date check
-    -r                    allow recursive removal
-    --ignore-unmatch      exit with a zero status even if nothing matched
-
-user error (xargs [\"-0\",\"git\",\"--git-dir=/home/ianc/Desktop/annex/.git\",\"--work-tree=/home/ianc/Desktop/annex\",\"rm\",\"--quiet\",\"-f\",\"--\"] exited 123)
-</pre>
-
-I suspect you might want xargs --no-run-if-empty?
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_8_e6b1084b2f18d8e536c8692e165754a3._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_8_e6b1084b2f18d8e536c8692e165754a3._comment
deleted file mode 100644
index 0e91f47fb..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_8_e6b1084b2f18d8e536c8692e165754a3._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.3.125"
- subject="comment 8"
- date="2013-02-05T19:13:34Z"
- content="""
-I don't know of anything that changed in XMPP handling between 3.20121211 and 3.20130124, so am hesitant to close this bug report.
-
-
-
-(I did put in a fix to avoid it queueing `git rm` when there were no files to remove.)
-"""]]
diff --git a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_9_2120a1c3e5f490a55f68bb1bef5efd0d._comment b/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_9_2120a1c3e5f490a55f68bb1bef5efd0d._comment
deleted file mode 100644
index 78ec89935..000000000
--- a/doc/bugs/three_way_sync_via_S3_and_Jabber/comment_9_2120a1c3e5f490a55f68bb1bef5efd0d._comment
+++ /dev/null
@@ -1,183 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhjlfoU21OiXKH_MXw75Uq5EsX7LJW5p0"
- nickname="Ian"
- subject="comment 9"
- date="2013-02-07T21:11:39Z"
- content="""
-It seems I may have spoken to soon, currently zakaz (the work machine) is out of sync with the other two again.
-
-daemon.log has a bunch of these:
-<pre>
-    [2013-02-07 19:42:56 GMT] NetWatcherFallback: Syncing with ian.james.campbell DesktopAnnex web 
-    fatal: Unable to find remote helper for 'xmpp'
-</pre>
-on zakaz and dagon.
-
-hastur does not have these messages in daemon.log but I just had to restart the assistant because it seems to have crashed. daemon.log.1 ends:
-<pre>
-    [2013-02-03 14:07:51 GMT] NetWatcherFallback: Syncing with ian.james.campbell DesktopAnnex web 
-    fatal: Unable to find remote helper for 'xmpp'
-    git-annex: <socket: 99>: hPutBuf: resource vanished (Broken pipe)
-    git-annex: forkProcess: interrupted
-</pre>
-
-zakaz is stuck at commit 81768b7, dagon and hastur have 8240e2b, with a few commits in between:
-<pre>
-$ git log --oneline 81768b74892ee5ec7f5a9ae15fb65d81c8a4d29d^..master
-8240e2b Merge commit 'refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/master'
-e6ae87e Merge commit 'refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/master'
-7bee777 
-3871031 
-c86bed3 
-81768b7 
-</pre>
-
-Before all the \"cannot find remote helper messages\" in zakaz's daemon.log I see:
-<pre>
-[2013-01-30 14:54:29 GMT] Pusher: Syncing with ian.james.campbell
-(Recording state in git...)
-
-Already up-to-date.
-To xmpp::ian.james.campbell@gmail.com
-   871b9c0..4585d72  git-annex -> refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex
-   6dadc6d..81768b7  master -> refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/master
-To xmpp::ian.james.campbell@gmail.com
-   871b9c0..4585d72  git-annex -> refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex
-   6dadc6d..81768b7  master -> refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/master
-(merging refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex into git-annex...)
-
-Already up-to-date.
-(merging refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex into git-annex...)
-[2013-01-30 15:48:10 GMT] NetWatcherFallback: Syncing with ian.james.campbell DesktopAnnex web 
-fatal: Unable to find remote helper for 'xmpp'
-fatal: The remote end hung up unexpectedly
-To xmpp::ian.james.campbell@gmail.com
-   4585d72..7d0d48f  git-annex -> refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex
-error: failed to push some refs to 'xmpp::ian.james.campbell@gmail.com'
-[2013-01-30 16:48:10 GMT] NetWatcherFallback: Syncing with ian.james.campbell DesktopAnnex web 
-fatal: Unable to find remote helper for 'xmpp'
-Everything up-to-date
-</pre>
-
-The last 3 lines are repeated, interspersed with the daily sanity checks (no errors).
-
-On hastur I see:
-<pre>
-[2013-01-30 15:33:44 GMT] NetWatcherFallback: Syncing with ian.james.campbell DesktopAnnex web 
-fatal: Unable to find remote helper for 'xmpp'
-To xmpp::ian.james.campbell@gmail.com
-   cec23e5..4585d72  git-annex -> refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/git-annex
-To xmpp::ian.james.campbell@gmail.com
-   871b9c0..4585d72  git-annex -> refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/git-annex
-   6dadc6d..81768b7  master -> refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/master
-fatal: The remote end hung up unexpectedly
-[2013-01-31 10:46:18 GMT] NetWatcherFallback: Syncing with ian.james.campbell DesktopAnnex web 
-fatal: Unable to find remote helper for 'xmpp'
-[2013-01-31 10:46:25 GMT] NetWatcher: Syncing with ian.james.campbell DesktopAnnex web 
-fatal: Unable to find remote helper for 'xmpp'
-(Recording state in git...)
-(Recording state in git...)
-(Recording state in git...)
-
-(merging refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex into git-annex...)
-
-git-annex: <socket: 52>: hWaitForInput: resource vanished (Connection reset by peer)
-</pre>
-
-and on dagon
-<pre>
-[2013-01-30 14:28:41 GMT] NetWatcherFallback: Syncing with ian.james.campbell DesktopAnnex web 
-fatal: Unable to find remote helper for 'xmpp'
-Everything up-to-date
-fatal: The remote end hung up unexpectedly
-Updating 6dadc6d..81768b7
-Fast-forward
- 2013-02-fosdem-evolving-xen-paravirtualisation.txt |    1 +
- 1 file changed, 1 insertion(+)
- create mode 120000 2013-02-fosdem-evolving-xen-paravirtualisation.txt
-[2013-01-30 14:56:34 GMT] Committer: Committing changes to git
-# On branch master
-nothing to commit (working directory clean)
-[2013-01-30 14:56:36 GMT] Pusher: Syncing with ian.james.campbell
-[2013-01-30 14:56:36 GMT] Transferr: Downloaded 2013-02-f..ation.txt
-[2013-01-30 14:56:38 GMT] Pusher: Syncing with ian.james.campbell
-fatal: Unable to create '/home/ijc/Desktop/annex/.git/refs/heads/synced/master.lock': File exists.
-
-If no other git process is currently running, this probably means a
-git process crashed in this repository earlier. Make sure no other git
-process is running and remove the file manually to continue.
-(merging refs/synced/552d29fe-4a86-11e2-819a-9f61585ee7a2/git-annex into git-annex...)
-
-(Recording state in git...)
-(Recording state in git...)
-git-annex: failed to update refs/heads/synced/master
-fatal: Unable to create '/home/ijc/Desktop/annex/.git/refs/heads/synced/master.lock': File exists.
-If no other git process is currently running, this probably means a
-git process crashed in this repository earlier. Make sure no other git
-process is running and remove the file manually to continue.
-fatal: Unable to create '/home/ijc/Desktop/annex/.git/refs/heads/synced/master.lock': File exists.
-
-If no other git process is currently running, this probably means a
-git process crashed in this repository earlier. Make sure no other git
-process is running and remove the file manually to continue.
-git-annex: failed to update refs/heads/synced/master
-git-annex: failed to update refs/heads/synced/master
-Already up-to-date.
-To xmpp::ian.james.campbell@gmail.com
-   871b9c0..8b8b935  git-annex -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex
-   6dadc6d..81768b7  master -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/master
-
-drop DesktopAnnex ./2013-02-fosdem-evolving-xen-paravirtualisation.txt (gpg) [2013-01-30 15:28:41 GMT] NetWatcherFallback: Syncing with ian.james.campbell DesktopAnnex web 
-fatal: Unable to find remote helper for 'xmpp'
-To xmpp::ian.james.campbell@gmail.com
-   8b8b935..7d0d48f  git-annex -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex
-Already up-to-date.
-</pre>
-
-It seems like something was up here but it recovered? All 3 managed to sync on 81768b7.
-
-Next on hastur I see:
-<pre>
-[2013-02-01 10:43:18 GMT] Committer: Committing changes to git
-[2013-02-01 10:43:18 GMT] Pusher: Syncing with ian.james.campbell
-Already up-to-date.
-[2013-02-01 10:43:19 GMT] Committer: Committing changes to git
-To xmpp::ian.james.campbell@gmail.com
-   81768b7..3871031  master -> refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/master
-[2013-02-01 10:43:20 GMT] Pusher: Syncing with ian.james.campbell
-Already up-to-date.
-To xmpp::ian.james.campbell@gmail.com
-   3871031..7bee777  master -> refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/master
-Updating 7bee777..8240e2b
-Fast-forward
- Xen at FOSDEM.docx |    1 +
- 1 file changed, 1 insertion(+)
- create mode 120000 Xen at FOSDEM.docx
-</pre>
-
-And on dagon
-<pre>
-[2013-02-01 10:45:52 GMT] Committer: Committing changes to git
-(Recording state in git...)
-# On branch master
-nothing to commit (working directory clean)
-[2013-02-01 10:45:53 GMT] Pusher: Syncing with ian.james.campbell
-To xmpp::ian.james.campbell@gmail.com
-   fc4ad88..70a6877  git-annex -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/git-annex
-   5e83708..8240e2b  master -> refs/synced/54f6febc-4791-11e2-952f-13bd7a1c79f1/master
-
-Already up-to-date.
-Everything up-to-date
-(merging refs/synced/1167ef76-4791-11e2-9bfe-4319f44b8a5f/git-annex into git-annex...)
-
-Already up-to-date.
-
-</pre>
-(5e83708 is 81768b7~2)
-
-However there is nothing in the logs on zakaz about moving on from 81768b7. The last interesting message is the \"[2013-01-30 15:48:10 GMT\" one above.
-
-is the XMPP peering supposed to be fully connected (i.e. each node is talking to both the others) or would it be expected that one of the nodes would be in the middle of the other two acting as a relay?
-
-I'm wondering about that because hastur is frequently suspended. I can't quite remember but I think when I set this up I peered dagon<->hastur at home and then while I was at work I peered zakaz<->hastur.  That would seem to suggest that hastur would have ended up as the man in the middle. TBH I can't quite recall what the setup process involves, so maybe I'm talking nonsense. I think I went into the \"Share with a friend\" page and shared with myself.
-"""]]
diff --git a/doc/bugs/tmp_file_handling.mdwn b/doc/bugs/tmp_file_handling.mdwn
deleted file mode 100644
index 9db932e57..000000000
--- a/doc/bugs/tmp_file_handling.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-git-annex deletes all tmp files on shutdown, if everything succeeded.
-This presents 2 problems:
-
-1. If git-annex is rsyncing something and another one is run, it will
-   delete the running instance's tmp files.
-2. If a long-running rsync transfer is interrupted partway through, the
-   tmp file was expensive to obtain, and one needs to avoid running
-   git-annex to do anything else until that transfer can be resumed and
-   finished.
-
---[[Joey]] 
-
-[[done]]
diff --git a/doc/bugs/tmp_file_handling/comment_1_0300c11ee3f94a9e7c832671e16f5511._comment b/doc/bugs/tmp_file_handling/comment_1_0300c11ee3f94a9e7c832671e16f5511._comment
deleted file mode 100644
index 244e580b2..000000000
--- a/doc/bugs/tmp_file_handling/comment_1_0300c11ee3f94a9e7c832671e16f5511._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://www.openid.albertlash.com/openid/"
- ip="74.96.185.87"
- subject="What to do?"
- date="2012-10-24T15:47:16Z"
- content="""
-I've got a stale .git/annex/tmp/rsynctmp file that just won't go away, and I think its because I cancelled an in-progress rsync, then did something else, as you describe.
-
-Is it ok to manually remove the file?
-
-Thanks!
-Albert
-"""]]
diff --git a/doc/bugs/tmp_file_handling/comment_2_cc14c7a79a544e47654e4cd8abc85edd._comment b/doc/bugs/tmp_file_handling/comment_2_cc14c7a79a544e47654e4cd8abc85edd._comment
deleted file mode 100644
index d6ae5bcf0..000000000
--- a/doc/bugs/tmp_file_handling/comment_2_cc14c7a79a544e47654e4cd8abc85edd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.23"
- subject="comment 2"
- date="2012-10-24T15:50:40Z"
- content="""
-`rsynctmp` is only used when sending files to a rsync special remote. You can certainly delete it if you got a stale one, but the next time a file is sent to a rsync special remote it should delete it anyway.
-"""]]
diff --git a/doc/bugs/transferkey_fails_due_to_gpg.mdwn b/doc/bugs/transferkey_fails_due_to_gpg.mdwn
deleted file mode 100644
index 26bd0443e..000000000
--- a/doc/bugs/transferkey_fails_due_to_gpg.mdwn
+++ /dev/null
@@ -1,51 +0,0 @@
-What steps will reproduce the problem?
-Create a new annex, add a new repository:
-
-  git annex initremote vserver2 type=rsync rsyncurl=vserver.dbruhn.de:/annex encryption=dominik@dbruhn.de
-
-Add some files, add them to annex, try to transfer them:
-  git annex transferkey SHA256-s6486446--df84b11a0e9543134224d0ac1e0f2567bcd79d86605117c5af008a1b133cee3a --to vserver2 --file MKBD/OB.mp3 --debug
-
-What is the expected output? What do you see instead?
-
-I expect the file to be transfered to my remote server. Instead I see a 'gpg>' prompt with nothing happening. When pressing CTRL+C, the following mesage is shown:
-
-gpg: Interrupt caught ... exiting
-
-There must be some faults when interfacing gpg. The other console-output is:
-
------
-    [2012-09-08 18:50:12 CEST] read: git ["--git-dir=/home/dominik/Annex/.git","--work-tree=/home/dominik/Annex","show-ref","git-annex"] 
-    [2012-09-08 18:50:12 CEST] read: git ["--git-dir=/home/dominik/Annex/.git","--work-tree=/home/dominik/Annex","show-ref","--hash","refs/heads/git-annex"] 
-    [2012-09-08 18:50:12 CEST] read: git ["--git-dir=/home/dominik/Annex/.git","--work-tree=/home/dominik/Annex","log","refs/heads/gitannex..245fa80db6733dbbeff6c40d46bd65ed00811548","--oneline","-n1"] 
-    [2012-09-08 18:50:12 CEST] chat: git ["--git-dir=/home/dominik/Annex/.git","--work-tree=/home/dominik/Annex","cat-file","--batch"] 
-    (gpg) [2012-09-08 18:50:12 CEST] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--decrypt"] 
-    [2012-09-08 18:50:12 CEST] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--passphrase-fd","8","--symmetric","--force-mdc"] 
-    sdgdg
-    dsgdgs
-    ^C
-    gpg: Interrupt caught ... exiting
------
-
-What version of git-annex are you using? On what operating system?
-git-annex version: 3.20120826
-Ubuntu 12.04, GHC 7.4.1
-gpg is 'gpg (GnuPG) 1.4.11'
-
-Please provide any additional information below.
-
-The key which is used for the remote is password protected. The GnuPG Agent asks me for the password, so this seems to work. I do not know what content the gpg expects but does not recieve. The .git/config entry for the remote looks reasonable:
-
-    [remote "vserver2"]
-        annex-rsyncurl = vserver.dbruhn.de:/annex
-        annex-uuid = ea3d6acc-716c-48e8-9b6b-993b90dcc1db
-
-When adding a new rsync-remote with encryption set to 'none' (therefore disabled), everything works, so it really seems a gpg issue.
-
-How can I help debugging?
-
-> Thanks, I reproduced a deadlock in the gpg code, which was introduced
-> with some of my earlier changes to use threading. No released version of
-> git-annex was affected, and I have developed a fix, which works for me
-> and is now committed to master. Marking this [[done]]; please do check
-> that my fix works for you! --[[Joey]]
diff --git a/doc/bugs/transferkey_fails_due_to_gpg/comment_1_f6434400d528a0fa59c056995ff2e6f3._comment b/doc/bugs/transferkey_fails_due_to_gpg/comment_1_f6434400d528a0fa59c056995ff2e6f3._comment
deleted file mode 100644
index 1fb9d2a0b..000000000
--- a/doc/bugs/transferkey_fails_due_to_gpg/comment_1_f6434400d528a0fa59c056995ff2e6f3._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.30"
- subject="comment 1"
- date="2012-09-09T16:45:20Z"
- content="""
-This is very strange behavior for gpg, it's being told several ways not to be interactive (--batch, --no-tty, --passphrase-fd); the mode it's being run in should, even without those options, only prompt for a password.
-
-I'm left wondering what settings you have in gpg.conf, and even wondering if you have some kind of wrapper around gpg that makes it more interactive, or some odd gpg agent that's interactive, or something.
-
-(I'm also confused that you mention a \"gpg>\" prompt, but your transcript doesn't show one.)
-"""]]
diff --git a/doc/bugs/transferkey_fails_due_to_gpg/comment_2_c540b05b62a3186a87efcb180ea2a52d._comment b/doc/bugs/transferkey_fails_due_to_gpg/comment_2_c540b05b62a3186a87efcb180ea2a52d._comment
deleted file mode 100644
index 7203f45df..000000000
--- a/doc/bugs/transferkey_fails_due_to_gpg/comment_2_c540b05b62a3186a87efcb180ea2a52d._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.30"
- subject="comment 2"
- date="2012-09-09T16:50:40Z"
- content="""
-Perhaps you mistook the \"(gpg)\" that git-annex prints out for a gpg prompt? If your transcript is accurate, things seem to be stalled, and gpg is not behaving like you're at a prompt when you type stuff to it, just the terminal is echoing back what you typed.
-
-This then looks like it might be the same bug someone else mentioned here <http://git-annex.branchable.com/design/assistant/blog/day_70__adding_ssh_remotes/#comment-048f7fad45dc545f9d5a560491b275a1>
-
-I have not managed to reproduce that problem. Are you seeing stalls with any particular size of file? Does it happen with very small files?
-"""]]
diff --git a/doc/bugs/transferkey_fails_due_to_gpg/comment_3_9ad2ef73169dbd2866da2f4259ab0f00._comment b/doc/bugs/transferkey_fails_due_to_gpg/comment_3_9ad2ef73169dbd2866da2f4259ab0f00._comment
deleted file mode 100644
index 3838e70f0..000000000
--- a/doc/bugs/transferkey_fails_due_to_gpg/comment_3_9ad2ef73169dbd2866da2f4259ab0f00._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.8.30"
- subject="comment 3"
- date="2012-09-09T16:55:02Z"
- content="""
-I've replicated a stall with current git-annex head and gpg. Doesn't happen with an older build. bisecting..
-"""]]
diff --git a/doc/bugs/transferkey_fails_due_to_gpg/comment_4_7631b8842efba6a4aad87386ce9443a7._comment b/doc/bugs/transferkey_fails_due_to_gpg/comment_4_7631b8842efba6a4aad87386ce9443a7._comment
deleted file mode 100644
index 6c7a3f2d4..000000000
--- a/doc/bugs/transferkey_fails_due_to_gpg/comment_4_7631b8842efba6a4aad87386ce9443a7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://www.dbruhn.de/"
- nickname="Dominik"
- subject="comment 4"
- date="2012-09-09T19:45:07Z"
- content="""
-Thanks, your recent changes fixed the bug! 
-"""]]
diff --git a/doc/bugs/tweaks_to_directory_special_remote_doco.mdwn b/doc/bugs/tweaks_to_directory_special_remote_doco.mdwn
deleted file mode 100644
index 10861b45f..000000000
--- a/doc/bugs/tweaks_to_directory_special_remote_doco.mdwn
+++ /dev/null
@@ -1,80 +0,0 @@
-### Please describe the problem.
-
-I found the discussion in [directory](/special_remotes/directory) quite confusing until I looked at it the right way. Some tweaking of the documentation might help.
-
-### What steps will reproduce the problem?
-
-Possible method - get a newbie to read the page.
-
-### What version of git-annex are you using? On what operating system?
-
-n/a
-
-### Please provide any additional information below.
-
-Below is an untested patch that I think would make the documentation more helpful to me on a first reading.
-
-      Tweaks to doc/special_remotes/directory.mdwn
-      
-        * document the 'directory' option (!)
-        * try to make it clearer what is different about this remote,
-          including giving an example of how the directory structure looks.
-        * grammar fix in opening paragraph
-      
-      ---
-       doc/special_remotes/directory.mdwn | 16 +++++++++++++++-
-       1 file changed, 15 insertions(+), 1 deletion(-)
-      
-      diff --git a/doc/special_remotes/directory.mdwn b/doc/special_remotes/directory.mdwn
-      index 4d72e8b..7f076b3 100644
-      --- a/doc/special_remotes/directory.mdwn
-      +++ b/doc/special_remotes/directory.mdwn
-      @@ -1,10 +1,12 @@
-       This special remote type stores file contents in directory.
-       
-       One use case for this would be if you have a removable drive that
-      -you want to use it to sneakernet files between systems (possibly with
-      +you want to use to sneakernet files between systems (possibly with
-       \[[encrypted|encryption]] contents). Just set up both systems to use
-       the drive's mountpoint as a directory remote.
-       
-      +Note that directory remotes have a special directory structure
-      +(by design, the same as the \[[rsync|rsync]] remote).
-       If you just want two copies of your repository with the files "visible"
-       in the tree in both, the directory special remote is not what you want.
-       Instead, you should use a regular `git clone` of your git-annex repository.
-      @@ -14,6 +16,8 @@ Instead, you should use a regular `git clone` of your git-annex repository.
-       These parameters can be passed to `git annex initremote` to configure the
-       remote:
-       
-      +* `directory` - The path to directory in which the remote resides
-      +
-       * `encryption` - One of "none", "hybrid", "shared", or "pubkey".
-         See \[[encryption]].
-       
-      @@ -31,3 +35,13 @@ Setup example:
-       
-        # git annex initremote usbdrive type=directory directory=/media/usbdrive/ encryption=none
-        # git annex describe usbdrive "usb drive on /media/usbdrive/"
-      +
-      +Usage example:
-      + # git annex copy mycoolfile.mp4 --to usbdrive
-      + # ls -aF /media/usbdrive
-      +        ./  ../  42b/  .git/  tmp/
-      + # git annex whereis mycoolfile.mp4
-      + whereis mycoolfile.mp4 (2 copies)
-      +         320053d5-892f-46d2-89f0-d6e9d09e6398 -- here
-      +         6747a48b-fad2-41a7-9033-8d8daa35c5f8 -- usbdrive
-      + ok
-      -- 
-      1.8.5.2
-
-
-
-# End of transcript or log.
-
-> Largely applied (except example at the end). I agree these
-> changes make it much clearer, especially adding the missing documentation
-> of the directory parameter. So, [[done]]. Note that this website is a
-> wiki and users like you are welcome to edit pages directly to improve the
-> documentation. --[[Joey]]
diff --git a/doc/bugs/typo_in___34__ready_to_add_remote_server__34___message.mdwn b/doc/bugs/typo_in___34__ready_to_add_remote_server__34___message.mdwn
deleted file mode 100644
index 9d370b640..000000000
--- a/doc/bugs/typo_in___34__ready_to_add_remote_server__34___message.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-What steps will reproduce the problem?
-Add a ssh remote to an existing git annex repository. The word "sensitive" is misspelled.
-
-What is the expected output? What do you see instead?
-I expect to see:
-"The contents of your files will be stored, fully encrypted, on the server. The server will not store other information about your git repository. This is the best choice if you don't run the server yourself, or have sensitive data."
-
-But instead I see:
-"The contents of your files will be stored, fully encrypted, on the server. The server will not store other information about your git repository. This is the best choice if you don't run the server yourself, or have sensative data."
-
-What version of git-annex are you using? On what operating system?
-3.20130102, Fedora 17 x86_64
-
-Please provide any additional information below.
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/unable_to_sync_complains_of_missing_git-upload_and_receive_pack.mdwn b/doc/bugs/unable_to_sync_complains_of_missing_git-upload_and_receive_pack.mdwn
deleted file mode 100644
index 777c4f6e8..000000000
--- a/doc/bugs/unable_to_sync_complains_of_missing_git-upload_and_receive_pack.mdwn
+++ /dev/null
@@ -1,208 +0,0 @@
-### Please describe the problem.
-Syncing two standalones: amd64 and armel.
-
-Sync works from armel to amd64.
-
-Sync fails (missing git-upload-pack, git-receive-pack) from amd64 to armel.
-
-### What steps will reproduce the problem?
-git-annex sync :)
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 5.20131224-g6ca5271 on both
-
-### Please provide any additional information below.
-
-#### on server "rose" (amd64)
-
-[[!format sh """
-$ git-annex version
-git-annex version: 5.20131224-g6ca5271
-build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 5
-upgrade supported from repository versions: 0 1 2 4
-
-$ git-annex sync
-(merging synced/git-annex into git-annex...)
-commit  ok
-pull synology   
-ash: git-upload-pack: not found
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-failed
-push synology 
-ash: git-receive-pack: not found
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-
-  Pushing to synology failed.
-
-  (non-fast-forward problems can be solved by setting receive.denyNonFastforwards to false in the remote\'s git config)
-failed
-git-annex: sync: 2 failed
-$ cat .git/config
-[core]
-        repositoryformatversion = 0
-        filemode = true
-        bare = false
-        logallrefupdates = true
-[branch "master"]
-[annex]
-        uuid = c0e4106e-2631-11e2-9749-1bfa37a61069
-        version = 3
-[remote "synology"]
-        url = greg@server:/volume1/photo/
-        fetch = +refs/heads/*:refs/remotes/synology/*
-        annex-ssh-options = "-i /home/greg/.ssh/annex.rose_rsa"
-        annex-uuid = ca735977-973c-44bc-9257-915b2c875e39
-
-greg@rose:~/.ssh$ cat authorized_keys
-command="/home/greg/.ssh/git-annex-shell" ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDT1yE96E/JQNPt0ziiNYJRvndCvLK4uG5h/SNYoAIBF1uH6L7VYAt3HWVqSyi3BcV70WDZ/yWgtNzbrcir46JpvEHMcvYaXLbANwoDGNjG/gsz7kP/8VUxZ6hG3P3ICuwnqVum5+rYXm6oj3xzWPfTRhhRoDZLOQdevSNpdGNaa/lSg8Vuq2suHwjQlQb8AIUuCZmS5cm6XwoUq/jJtN4LTuTPqMjzA6NkdhWM2Kigi9jPQBFborkYBPMphmZwBZiVnhsH1XpaOff+mP03D2gF/huC+b1vbWQstjuehUbY59rvJ4ijbOW8Uq2ep7dwLagmILtX5GbL+GS64pAn9sIP annex-DiskStation
-
-greg@rose:~/.ssh$ cat git-annex-shell   
-#!/bin/sh  
-set -e  
-exec /home/greg/bin/git-annex.linux/runshell git-annex-shell -c "$SSH_ORIGINAL_COMMAND"
-
-greg@rose:~/bin/git-annex.linux$ ls
-bin          gconvdir   git-annex.MANIFEST  git-core          lib      LICENSE   README    templates
-etc          git        git-annex-shell     git-receive-pack  lib64    linker    runshell  usr
-favicon.png  git-annex  git-annex-webapp    git-upload-pack   libdirs  logo.svg  shimmed
-"""]]
-
-#### on "synology" (armel)
-
-[[!format sh """
-/volume1/downloads/git-annex.linux $ ./runshell
-$ git-annex version
-git-annex version: 5.20131224-g6ca5271
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-local repository version: 5
-default repository version: 3
-supported repository versions: 3 5
-upgrade supported from repository versions: 0 1 2 4
-
-$ which git-receive-pack
-/volume1/downloads/git-annex.linux/bin/git-receive-pack
-
-$ which git-upload-pack
-/volume1/downloads/git-annex.linux/bin/git-upload-pack
-
-$ git-annex sync
-commit  (Recording state in git...)
-ok
-pull rose 
-From server:/home/greg/Media/Pictures/Photos
-   d761e6e..4454a51  git-annex  -> rose/git-annex
-   c4f0719..a4c73e4  master     -> rose/master
-ok
-push rose 
-Counting objects: 134, done.
-Compressing objects: 100% (58/58), done.
-Writing objects: 100% (58/58), 4.81 KiB | 0 bytes/s, done.
-Total 58 (delta 38), reused 0 (delta 0)
-warning: There are too many unreachable loose objects; run 'git prune' to remove them.
-To greg@server:/home/greg/Media/Pictures/Photos
-   4454a51..812c393  git-annex -> synced/git-annex
-ok
-
-$ cat .git/config
-[core]
-        repositoryformatversion = 0
-        filemode = true
-        bare = true
-        logallrefupdates = true
-[branch "master"]
-[annex]
-        uuid = ca735977-973c-44bc-9257-915b2c875e39
-        version = 5
-        direct = true
-[remote "rose"]
-        url = greg@server:/home/greg/Media/Pictures/Photos
-        fetch = +refs/heads/*:refs/remotes/rose/*
-        annex-ssh-options = "-i /var/services/homes/greg/.ssh/annex_rsa"
-        annex-trustlevel = trusted
-        annex-uuid = c0e4106e-2631-11e2-9749-1bfa37a61069
-
-$ cat /volume1/homes/greg/.ssh/authorized_keys
-...partial...
-command="/var/services/homes/greg/.ssh/git-annex-shell" ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCYvOZK2rO+3cF1wxxxrXptZ/QbRaOy36p9RtFmE5MKxgBRJ7n/8nMfBGaj3KDXcdJG+dTUsmLY5VeULuM4omtfJrF2MFYZDw2N0Qgq1bnYZ+q4OlpHfI3h77dAxyvM1MXYJvewXsjh8XoQJYqE8Pj4C05YsAJrqQJqqQqVZceD4TPvbKgnQhQIE2mCVXfItucJv0TOOBmKguOQGUB4Jp00IvFsnxpCLDeLFIODjRpXQqcMX9cZ9/6OYLznTck/MdbA5KTev1gVwiGwtYFGqY/DJ7q6zqfE+UU2aKS/M0r0Qjvr2+Q4+CuzVYc+hPURC8phmdP+HjtFcVsEcpsl6p79 annex-rose
-
-/volume1/homes/greg/.ssh $ cd /volume1/homes/greg/.ssh/
-/volume1/homes/greg/.ssh
-/volume1/homes/greg/.ssh $ ls        
-annex_rsa        authorized_keys  id_rsa           known_hosts
-annex_rsa.pub    git-annex-shell  id_rsa.pub
-/volume1/homes/greg/.ssh $ cd /var/services/homes/greg/.ssh/
-/volume1/homes/greg/.ssh $ pwd
-/var/services/homes/greg/.ssh
-
-/volume1/homes/greg/.ssh $ cat git-annex-shell 
-#!/bin/sh
-set -e
-exec /volume1/downloads/git-annex.linux/runshell git-annex-shell -c "$SSH_ORIGINAL_COMMAND"
-
-/volume1/downloads/git-annex.linux $ ls
-LICENSE             git-annex-shell     linker
-README              git-annex-webapp    logo.svg
-bin                 git-annex.MANIFEST  runshell
-etc                 git-core            shimmed
-favicon.png         git-receive-pack    templates
-gconvdir            git-upload-pack     usr
-git                 lib
-git-annex           libdirs
-"""]]
-
-
-
-
-
-### After some debugging with Joey...
-12:24 <     joeyh> git does not use annex-ssh-options
-12:24 <     joeyh> the way the assistant sets this up is it makes up a new hostname, and in .ssh/config, makes that hostname use the real domain name, and the key
-12:25 <     joeyh> there's clearly a bug here.. the assistant only does that when there is no passwordless ssh key already set up. But in this wacky way of installing git and git-annex on a server, it needs to always do it
-12:26 <     joeyh> probably the assistant should probe if ssh server git-receive-pack works, and if not, always set up its special config
-12:26 <     joeyh> alternatively, the standalone tarball could have an actual installation step, rather than just being unpacked
-
-Based on that I added (on the amd64/rose machine):
-[[!format sh """
-greg@rose:~/.ssh$ cat config
-Host synology
-    HostName yep.org #obviously redacted
-    IdentityFile /home/greg/.ssh/annex.rose_rsa
-
-$ git remote show -n synology
-* remote synology
-  Fetch URL: greg@synology:/volume1/photo/
-  Push  URL: greg@synology:/volume1/photo/
-  HEAD branch: (not queried)
-  Local ref configured for 'git push' (status not queried):
-    (matching) pushes to (matching)
-"""]]
-
-Now, to do a simple test with git:
-
-[[!format sh """
-$ git remote show synology
-git-annex-shell: git-shell failed
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-"""]]
-
-> [[done]]; `git push` and `git pull` don't use annex-ssh-options,
-> and so that's not a good way to configure the dedicated key. 
-> Instead, set it up like the assistant does, with a dummy hostname in the
-> url that is configured in .ssh/config to use the real domain and the
-> dedicated key. --[[Joey]]
diff --git a/doc/bugs/unable_to_sync_complains_of_missing_git-upload_and_receive_pack/comment_1_8b0302bba2b99df0842dfead649080e7._comment b/doc/bugs/unable_to_sync_complains_of_missing_git-upload_and_receive_pack/comment_1_8b0302bba2b99df0842dfead649080e7._comment
deleted file mode 100644
index 0301f58c5..000000000
--- a/doc/bugs/unable_to_sync_complains_of_missing_git-upload_and_receive_pack/comment_1_8b0302bba2b99df0842dfead649080e7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 1"
- date="2013-12-27T20:11:09Z"
- content="""
-Seems there really is a bug here, `git-shell` needs to be added to the top of the bundle. I've done so, but not tested it.
-"""]]
diff --git a/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken.mdwn b/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken.mdwn
deleted file mode 100644
index c31205ede..000000000
--- a/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken.mdwn
+++ /dev/null
@@ -1,17 +0,0 @@
-git's index broke and I was unable to restore it. While this is not git-annex' problem, it should still be possible to get my data in an un-annexed state.
-
-    % git status
-    fatal: index file smaller than expected
-    % git annex unannex foo
-    fatal: index file smaller than expected
-    % git annex uninit
-    fatal: index file smaller than expected
-    uninit  
-      pre-commit hook (/path/to/git-annex/.git/hooks/pre-commit) contents modified; not deleting. Edit it to remove call to git annex.
-    ok
-    %
-
-Ttbomk, the softlinks and objects are enough to un-annex the files; side-stepping git's index if necessary.
-
-> `git annex repair` can now repair broken index files and other
-> git repository corruption. [[done]] --[[Joey]]
diff --git a/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken/comment_1_1931e733f0698af5603a8b92267203d4._comment b/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken/comment_1_1931e733f0698af5603a8b92267203d4._comment
deleted file mode 100644
index 84b68bb7b..000000000
--- a/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken/comment_1_1931e733f0698af5603a8b92267203d4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-04-03T01:40:50Z"
- content="""
-They rely on git-ls-files to get a list of files that are checked into git, in order to tell what to unannex.
-"""]]
diff --git a/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken/comment_2_40920b88537b7715395808d8aa94bf03._comment b/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken/comment_2_40920b88537b7715395808d8aa94bf03._comment
deleted file mode 100644
index 215619043..000000000
--- a/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken/comment_2_40920b88537b7715395808d8aa94bf03._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2011-04-03T08:55:18Z"
- content="""
-Given that the softlinks contain all needed information (if the object exists, locally), an emergency way to get files \"out\" of git-annex would be nice. I am aware that one can script it, but a canonical way is always better, especially when things go south.
-"""]]
diff --git a/doc/bugs/unannex_command_doesn__39__t_all_files.mdwn b/doc/bugs/unannex_command_doesn__39__t_all_files.mdwn
deleted file mode 100644
index a6500c377..000000000
--- a/doc/bugs/unannex_command_doesn__39__t_all_files.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-    $ git init ; git annex init test ; dd if=/dev/urandom of=file1 count=128 ; cp file1 file2 ; git annex add --backend=SHA1 file? ; git commit -m init ; git annex unannex ; ls -l
-    Initialized empty Git repository in /tmp/annex/.git/
-    init test ok
-    128+0 records in
-    128+0 records out
-    65536 bytes (66 kB) copied, 0.007173 s, 9.1 MB/s
-    add file1 (checksum...) ok
-    add file2 (checksum...) ok
-    (Recording state in git...)
-    [master (root-commit) 2177b10] init
-     2 files changed, 2 insertions(+), 0 deletions(-)
-     create mode 120000 file1
-     create mode 120000 file2
-    unannex file1 ok
-    (Recording state in git...)
-    [master bef78b1] content removed from git annex
-     1 files changed, 0 insertions(+), 1 deletions(-)
-     delete mode 120000 file1
-    total 72
-    -rw-r--r-- 1 simons users 65536 Jul 15 17:29 file1
-    lrwxrwxrwx 1 simons users   132 Jul 15 17:29 file2 -> .git/annex/objects/jp/Fk/SHA1-s65536--795b58cc4e5190b02e7026fd9e94a10c98c6475f/SHA1-s65536--795b58cc4e5190b02e7026fd9e94a10c98c6475f
-
-> This was recently discussed in
-> [[annex_unannex__47__uninit_should_handle_copies]] and `unannex --fast`
-> added to leave contents behind in the annex, which allows handling
-> copies. But needs manual cleanup later with dropunused. --[[Joey]] 
-
-> This is basically a dup of [[Large unannex operations result in stale symlinks and data loss]],
-> or at least the ideas in there will also deal with this. Closing as dupe.
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others.mdwn b/doc/bugs/unannex_removes_object_even_if_referred_to_by_others.mdwn
deleted file mode 100644
index 874e5c27f..000000000
--- a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-##What steps will reproduce the problem?
-
-    echo text > foo
-    echo text > bar
-    git annex add foo bar
-    git annex unannex foo
-
-##What is the expected output? What do you see instead?
-
-I would expect that the object behind 'bar' remained intact, what happens is that the object is moved out of the annex and 'bar' is left as a dangling symlink, if you are unlucky and don't spot this, it could be potentially dangerous, since you can easily lose data.
-
-##What version of git-annex are you using? On what operating system?
-
-git-annex built from git on Tue Mar 12 15:58:36 2013 -0400
-
-From commit: 70b7555eaf9ac5f88bb137985d93bed8d5a434e8
-
-On Debian Sid
-
-> [[done]]; duplicate bug report
diff --git a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_1_0ce72d0f67082f202cfa58b7c00f2fd3._comment b/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_1_0ce72d0f67082f202cfa58b7c00f2fd3._comment
deleted file mode 100644
index da80a8f01..000000000
--- a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_1_0ce72d0f67082f202cfa58b7c00f2fd3._comment
+++ /dev/null
@@ -1,39 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="git annex uninit does this too..."
- date="2013-07-27T07:55:49Z"
- content="""
-Here are my files from a backup...
-
-    fozz@cobol:/mnt/store/Music/Jukebox/Markus Schulz/Miami'05 Euro Trance $ md5sum AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg AlbumArtSmall.jpg
-    9cfd8347becf87da8b1c5962e77267ad  AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg
-    9cfd8347becf87da8b1c5962e77267ad  AlbumArtSmall.jpg
-
-Here is how git annex unannex left my files...
-
-    fozz@markdown:/exports/music$ ls -alh Jukebox/Markus\ Schulz/Miami\'05\ Euro\ Trance/
-    total 127M
-    drwxr-x---+ 2 fozz audio 4.0K Jul 27 03:04 .
-    drwxr-x---+ 9 fozz audio 4.0K Feb  8 20:03 ..
-    -rwxr-x---+ 1 fozz audio  13M Mar 24  2008 01 - Hydroid  Blue Tubes (Intro Mix).mp3
-    -rwxr-x---+ 1 fozz audio 9.8M Mar 24  2008 02 - Interstate  I Found U (Harry Lemon Remix).mp3
-    -rwxr-x---+ 1 fozz audio  15M Mar 24  2008 03 - Kalafut & Fygle  '3579 Km.mp3
-    -rwxr-x---+ 1 fozz audio  11M Mar 24  2008 04 - Hammer & Bennett  Baltic Sea.mp3
-    -rwxr-x---+ 1 fozz audio  11M Mar 24  2008 05 - Fluid In Motion  Soul Dimension.mp3
-    -rwxr-x---+ 1 fozz audio  12M Mar 24  2008 06 - Keo  Close Enough (Noel Sanger Mix).mp3
-    -rwxr-x---+ 1 fozz audio 9.4M Mar 24  2008 08 - Lens  Let The Light In.mp3
-    -rwxr-x---+ 1 fozz audio  11M Mar 24  2008 09 - Aronek  Free Yourself.mp3
-    -rwxr-x---+ 1 fozz audio  14M Mar 24  2008 10 - Ava Mea  In The End.mp3
-    -rwxr-x---+ 1 fozz audio  13M Mar 24  2008 11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3
-    -rwxr-x---+ 1 fozz audio  12M Mar 24  2008 12 - Max Graham Feat- Jessica Jacobs  Gone.mp3
-    -rwxr-x---+ 1 fozz audio 6.9K Mar 24  2008 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg
-    lrwxrwxrwx  1 fozz fozz   191 Mar 24  2008 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg -> ../../../.git/annex/objects/ZZ/86/SHA256-s2067--   b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a/SHA256-s2067--b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a
-    -rwxr-x---+ 1 fozz audio 2.1K Mar 24  2008 AlbumArtSmall.jpg
-    -rwxr-x---+ 1 fozz audio  361 Mar 24  2008 desktop.ini
-    lrwxrwxrwx  1 fozz fozz   191 Mar 24  2008 Folder.jpg -> ../../../.git/annex/objects/k7/xp/SHA256-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f/SHA256-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f
-
-The symlinks are now broken links
-
-
-"""]]
diff --git a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_2_647f49ffcaa348660659f9954a59b3ae._comment b/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_2_647f49ffcaa348660659f9954a59b3ae._comment
deleted file mode 100644
index 041d700dd..000000000
--- a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_2_647f49ffcaa348660659f9954a59b3ae._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="comment 2"
- date="2013-07-27T08:14:33Z"
- content="""
-Sorry, that was an unannex . not a uninit, which I used first briefly. Version information:
-
-    git-annex version: 4.20130725-gd10dfef
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-
-"""]]
diff --git a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_3_3f7f4b55b7ec2641a70109788e0b5672._comment b/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_3_3f7f4b55b7ec2641a70109788e0b5672._comment
deleted file mode 100644
index 890e96fea..000000000
--- a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_3_3f7f4b55b7ec2641a70109788e0b5672._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.110"
- subject="comment 3"
- date="2013-07-27T23:51:38Z"
- content="""
-uninit does not do this. Nor does unannex --fast FWIW.
-
-
-"""]]
diff --git a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_4_313d393c416495aa0f8573113e41c2f7._comment b/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_4_313d393c416495aa0f8573113e41c2f7._comment
deleted file mode 100644
index 0f691059d..000000000
--- a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_4_313d393c416495aa0f8573113e41c2f7._comment
+++ /dev/null
@@ -1,431 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="Yes it does"
- date="2013-07-28T12:04:18Z"
- content="""
-I think it does, I just tested it with Ubuntu default version and the newest linux tarball on your site...
-
-See Log:
-
-    fozz@cobol:~ $ cd /tmp
-    
-    fozz@cobol:/tmp $ tar -zxf ~/Downloads/git-annex-standalone-amd64.tar.gz 
-    
-    fozz@cobol:/tmp $ export PATH=/tmp/git-annex.linux/:$PATH
-    
-    fozz@cobol:/tmp $ cp -R /mnt/store/Music/Jukebox/Markus\ Schulz/
-    Amsterdam 08/                                   Progression/
-    Do You Dream/                                   Thoughts Become Things II/
-    June 2005 Promo Mix/                            Track/
-    Miami'05 Euro Trance/                           Without You Near/
-    Mysteryland 2007 Haarlemmermeermeer 25-08-2007/ 
-    
-    fozz@cobol:/tmp $ cp -R /mnt/store/Music/Jukebox/Markus\ Schulz/Miami\'05\ Euro\ Trance/ .
-    
-    fozz@cobol:/tmp $ cd Miami\'05\ Euro\ Trance/
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ ls -alh
-    total 127M
-    drwx------  2 fozz fozz 4.0K Jul 28 12:52 .
-    drwxrwxrwt 23 root root 4.0K Jul 28 12:52 ..
-    -rwx------  1 fozz fozz  13M Jul 28 12:52 01 - Hydroid  Blue Tubes (Intro Mix).mp3
-    -rwx------  1 fozz fozz 9.8M Jul 28 12:52 02 - Interstate  I Found U (Harry Lemon Remix).mp3
-    -rwx------  1 fozz fozz  15M Jul 28 12:52 03 - Kalafut & Fygle  '3579 Km.mp3
-    -rwx------  1 fozz fozz  11M Jul 28 12:52 04 - Hammer & Bennett  Baltic Sea.mp3
-    -rwx------  1 fozz fozz  11M Jul 28 12:52 05 - Fluid In Motion  Soul Dimension.mp3
-    -rwx------  1 fozz fozz  12M Jul 28 12:52 06 - Keo  Close Enough (Noel Sanger Mix).mp3
-    -rwx------  1 fozz fozz 9.4M Jul 28 12:52 08 - Lens  Let The Light In.mp3
-    -rwx------  1 fozz fozz  11M Jul 28 12:52 09 - Aronek  Free Yourself.mp3
-    -rwx------  1 fozz fozz  14M Jul 28 12:52 10 - Ava Mea  In The End.mp3
-    -rwx------  1 fozz fozz  13M Jul 28 12:52 11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3
-    -rwx------  1 fozz fozz  12M Jul 28 12:52 12 - Max Graham Feat- Jessica Jacobs  Gone.mp3
-    -rwx------  1 fozz fozz 6.9K Jul 28 12:52 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg
-    -rwx------  1 fozz fozz 2.1K Jul 28 12:52 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg
-    -rwx------  1 fozz fozz 2.1K Jul 28 12:52 AlbumArtSmall.jpg
-    -rwx------  1 fozz fozz  361 Jul 28 12:52 desktop.ini
-    -rwx------  1 fozz fozz 6.9K Jul 28 12:52 Folder.jpg
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ mkdir Files
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ mv * Files/
-    mv: cannot move ‘Files’ to a subdirectory of itself, ‘Files/Files’
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ ls
-    Files
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ git annex version
-    git-annex version: 4.20130725-g8140f7c
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ git init 
-    Initialised empty Git repository in /tmp/Miami'05 Euro Trance/.git/
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ git annex init TEST
-    init TEST error: Malformed value for push.default: simple
-    error: Must be one of nothing, matching, tracking or current.
-    fatal: bad config file line 19 in /home/fozz/.gitconfig
-    error: Malformed value for push.default: simple
-    error: Must be one of nothing, matching, tracking or current.
-    fatal: bad config file line 19 in /home/fozz/.gitconfig
-    git-annex: failed to read sha from git write-tree
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ vim ~/.gitconfig 
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ git annex init TEST
-    init TEST ok
-    (Recording state in git...)
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ git annex add .
-    add Files/01 - Hydroid  Blue Tubes (Intro Mix).mp3 (checksum...) ok
-    add Files/02 - Interstate  I Found U (Harry Lemon Remix).mp3 (checksum...) ok
-    add Files/03 - Kalafut & Fygle  '3579 Km.mp3 (checksum...) ok
-    add Files/04 - Hammer & Bennett  Baltic Sea.mp3 (checksum...) ok
-    add Files/05 - Fluid In Motion  Soul Dimension.mp3 (checksum...) ok
-    add Files/06 - Keo  Close Enough (Noel Sanger Mix).mp3 (checksum...) ok
-    add Files/08 - Lens  Let The Light In.mp3 (checksum...) ok
-    add Files/09 - Aronek  Free Yourself.mp3 (checksum...) ok
-    add Files/10 - Ava Mea  In The End.mp3 (checksum...) ok
-    add Files/11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3 (checksum...) ok
-    add Files/12 - Max Graham Feat- Jessica Jacobs  Gone.mp3 (checksum...) ok
-    add Files/AlbumArtSmall.jpg (checksum...) ok
-    add Files/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg (checksum...) ok
-    add Files/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg (checksum...) ok
-    add Files/Folder.jpg (checksum...) ok
-    add Files/desktop.ini (checksum...) ok
-    (Recording state in git...)
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ ls
-    Files
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ ls Files
-    01 - Hydroid  Blue Tubes (Intro Mix).mp3
-    02 - Interstate  I Found U (Harry Lemon Remix).mp3
-    03 - Kalafut & Fygle  '3579 Km.mp3
-    04 - Hammer & Bennett  Baltic Sea.mp3
-    05 - Fluid In Motion  Soul Dimension.mp3
-    06 - Keo  Close Enough (Noel Sanger Mix).mp3
-    08 - Lens  Let The Light In.mp3
-    09 - Aronek  Free Yourself.mp3
-    10 - Ava Mea  In The End.mp3
-    11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3
-    12 - Max Graham Feat- Jessica Jacobs  Gone.mp3
-    AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg
-    AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg
-    AlbumArtSmall.jpg
-    desktop.ini
-    Folder.jpg
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ git annex uninit .
-    fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
-    Use '--' to separate paths from revisions
-    git-annex: This command takes no parameters.
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ git annex uninit 
-    fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
-    Use '--' to separate paths from revisions
-    unannex Files/01 - Hydroid  Blue Tubes (Intro Mix).mp3 ok
-    unannex Files/02 - Interstate  I Found U (Harry Lemon Remix).mp3 ok
-    unannex Files/03 - Kalafut & Fygle  '3579 Km.mp3 ok
-    unannex Files/04 - Hammer & Bennett  Baltic Sea.mp3 ok
-    unannex Files/05 - Fluid In Motion  Soul Dimension.mp3 ok
-    unannex Files/06 - Keo  Close Enough (Noel Sanger Mix).mp3 ok
-    unannex Files/08 - Lens  Let The Light In.mp3 ok
-    unannex Files/09 - Aronek  Free Yourself.mp3 ok
-    unannex Files/10 - Ava Mea  In The End.mp3 ok
-    unannex Files/11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3 ok
-    unannex Files/12 - Max Graham Feat- Jessica Jacobs  Gone.mp3 ok
-    unannex Files/AlbumArtSmall.jpg ok
-    unannex Files/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg ok
-    unannex Files/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg ok
-    unannex Files/Folder.jpg ok
-    unannex Files/desktop.ini ok
-    Deleted branch git-annex (was 1b098e2).
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ ls
-    Files
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ ls -alh Files
-    total 127M
-    drwxrwxr-x 2 fozz fozz 4.0K Jul 28 12:54 .
-    drwx------ 4 fozz fozz 4.0K Jul 28 12:53 ..
-    -rwx------ 1 fozz fozz  13M Jul 28 12:52 01 - Hydroid  Blue Tubes (Intro Mix).mp3
-    -rwx------ 1 fozz fozz 9.8M Jul 28 12:52 02 - Interstate  I Found U (Harry Lemon Remix).mp3
-    -rwx------ 1 fozz fozz  15M Jul 28 12:52 03 - Kalafut & Fygle  '3579 Km.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:52 04 - Hammer & Bennett  Baltic Sea.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:52 05 - Fluid In Motion  Soul Dimension.mp3
-    -rwx------ 1 fozz fozz  12M Jul 28 12:52 06 - Keo  Close Enough (Noel Sanger Mix).mp3
-    -rwx------ 1 fozz fozz 9.4M Jul 28 12:52 08 - Lens  Let The Light In.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:52 09 - Aronek  Free Yourself.mp3
-    -rwx------ 1 fozz fozz  14M Jul 28 12:52 10 - Ava Mea  In The End.mp3
-    -rwx------ 1 fozz fozz  13M Jul 28 12:52 11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3
-    -rwx------ 1 fozz fozz  12M Jul 28 12:52 12 - Max Graham Feat- Jessica Jacobs  Gone.mp3
-    -rwx------ 2 fozz fozz 6.9K Jul 28 12:52 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg
-    -rwx------ 2 fozz fozz 2.1K Jul 28 12:52 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg
-    -rwx------ 2 fozz fozz 2.1K Jul 28 12:52 AlbumArtSmall.jpg
-    -rwx------ 1 fozz fozz  361 Jul 28 12:52 desktop.ini
-    -rwx------ 2 fozz fozz 6.9K Jul 28 12:52 Folder.jpg
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ ls
-    Files
-    
-    fozz@cobol:/tmp/Miami'05 Euro Trance $ cd ../
-    
-    fozz@cobol:/tmp $ mkdir TEST2
-    
-    fozz@cobol:/tmp $ cd TEST2
-    
-    fozz@cobol:/tmp/TEST2 $ echo $PATH
-    /tmp/git-annex.linux/:node_modules/.bin:node_modules/.bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/fozz/.scripts:/home/fozz/.bin:/sbin:/usr/sbin:/usr/local/sbin:/home/fozz/.scripts:/home/fozz/.bin:/sbin:/usr/sbin:/usr/local/sbin
-    
-    fozz@cobol:/tmp/TEST2 $ export PATH=node_modules/.bin:node_modules/.bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/fozz/.scripts:/home/fozz/.bin:/sbin:/usr/sbin:/usr/local/sbin:/home/fozz/.scripts:/home/fozz/.bin:/sbin:/usr/sbin:/usr/local/sbin
-    
-    fozz@cobol:/tmp/TEST2 $ git annex version
-    git-annex version: 3.20121112ubuntu2
-    
-    fozz@cobol:/tmp/TEST2 $ cp -R /mnt/store/Music/Jukebox/Markus\ Schulz/Miami\'05\ Euro\ Trance/ .
-    
-    fozz@cobol:/tmp/TEST2 $ ls
-    Miami'05 Euro Trance
-    
-    fozz@cobol:/tmp/TEST2 $ git init
-    Initialised empty Git repository in /tmp/TEST2/.git/
-    
-    fozz@cobol:/tmp/TEST2 $ git annex init TEST2
-    init TEST2 ok
-    (Recording state in git...)
-    
-    fozz@cobol:/tmp/TEST2 $ git add .
-    
-    fozz@cobol:/tmp/TEST2 $ ls
-    Miami'05 Euro Trance
-    
-    fozz@cobol:/tmp/TEST2 $ ls -alh Miami\'05\ Euro\ Trance/
-    total 127M
-    drwx------ 2 fozz fozz 4.0K Jul 28 12:56 .
-    drwxrwxr-x 4 fozz fozz 4.0K Jul 28 12:56 ..
-    -rwx------ 1 fozz fozz  13M Jul 28 12:56 01 - Hydroid  Blue Tubes (Intro Mix).mp3
-    -rwx------ 1 fozz fozz 9.8M Jul 28 12:56 02 - Interstate  I Found U (Harry Lemon Remix).mp3
-    -rwx------ 1 fozz fozz  15M Jul 28 12:56 03 - Kalafut & Fygle  '3579 Km.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:56 04 - Hammer & Bennett  Baltic Sea.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:56 05 - Fluid In Motion  Soul Dimension.mp3
-    -rwx------ 1 fozz fozz  12M Jul 28 12:56 06 - Keo  Close Enough (Noel Sanger Mix).mp3
-    -rwx------ 1 fozz fozz 9.4M Jul 28 12:56 08 - Lens  Let The Light In.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:56 09 - Aronek  Free Yourself.mp3
-    -rwx------ 1 fozz fozz  14M Jul 28 12:56 10 - Ava Mea  In The End.mp3
-    -rwx------ 1 fozz fozz  13M Jul 28 12:56 11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3
-    -rwx------ 1 fozz fozz  12M Jul 28 12:56 12 - Max Graham Feat- Jessica Jacobs  Gone.mp3
-    -rwx------ 1 fozz fozz 6.9K Jul 28 12:56 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg
-    -rwx------ 1 fozz fozz 2.1K Jul 28 12:56 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg
-    -rwx------ 1 fozz fozz 2.1K Jul 28 12:56 AlbumArtSmall.jpg
-    -rwx------ 1 fozz fozz  361 Jul 28 12:56 desktop.ini
-    -rwx------ 1 fozz fozz 6.9K Jul 28 12:56 Folder.jpg
-    
-    fozz@cobol:/tmp/TEST2 $ cd ../
-    
-    fozz@cobol:/tmp $ mkdir TEST3
-    
-    fozz@cobol:/tmp $ cd TEST3
-    
-    fozz@cobol:/tmp/TEST3 $ cp -R /mnt/store/Music/Jukebox/Markus\ Schulz/Miami\'05\ Euro\ Trance/ .
-    
-    fozz@cobol:/tmp/TEST3 $ git init
-    Initialised empty Git repository in /tmp/TEST3/.git/
-    
-    fozz@cobol:/tmp/TEST3 $ git annex init TEST3
-    init TEST3 ok
-    (Recording state in git...)
-    
-    fozz@cobol:/tmp/TEST3 $ git annex add .
-    add Miami'05 Euro Trance/01 - Hydroid  Blue Tubes (Intro Mix).mp3 (checksum...) ok
-    add Miami'05 Euro Trance/02 - Interstate  I Found U (Harry Lemon Remix).mp3 (checksum...) ok
-    add Miami'05 Euro Trance/03 - Kalafut & Fygle  '3579 Km.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/04 - Hammer & Bennett  Baltic Sea.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/05 - Fluid In Motion  Soul Dimension.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/06 - Keo  Close Enough (Noel Sanger Mix).mp3 (checksum...) ok
-    add Miami'05 Euro Trance/08 - Lens  Let The Light In.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/09 - Aronek  Free Yourself.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/10 - Ava Mea  In The End.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/12 - Max Graham Feat- Jessica Jacobs  Gone.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/AlbumArtSmall.jpg (checksum...) ok
-    add Miami'05 Euro Trance/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg (checksum...) ok
-    add Miami'05 Euro Trance/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg (checksum...) ok
-    add Miami'05 Euro Trance/Folder.jpg (checksum...) ok
-    add Miami'05 Euro Trance/desktop.ini (checksum...) ok
-    (Recording state in git...)
-    
-    fozz@cobol:/tmp/TEST3 $ md5sum Miami\'05\ Euro\ Trance/*
-    d764c06c5fc26f600842f4a9f2270696  Miami'05 Euro Trance/01 - Hydroid  Blue Tubes (Intro Mix).mp3
-    79879d4343a159fb391bd7eef691be03  Miami'05 Euro Trance/02 - Interstate  I Found U (Harry Lemon Remix).mp3
-    cc440d6dfaa0f6ef736b51b972f91c8d  Miami'05 Euro Trance/03 - Kalafut & Fygle  '3579 Km.mp3
-    ff0e52278bb69b2e8e44aa318e486ca7  Miami'05 Euro Trance/04 - Hammer & Bennett  Baltic Sea.mp3
-    73ec88f2f09b825bef3d9b876e0fc876  Miami'05 Euro Trance/05 - Fluid In Motion  Soul Dimension.mp3
-    d7790cde98696eb7f5e6a8b1d6949e1d  Miami'05 Euro Trance/06 - Keo  Close Enough (Noel Sanger Mix).mp3
-    0734d432e0ae67155c4b0363d2336bfa  Miami'05 Euro Trance/08 - Lens  Let The Light In.mp3
-    527335f6b173e13dacfa66f458df1a29  Miami'05 Euro Trance/09 - Aronek  Free Yourself.mp3
-    b859ead1712e144a1e3fd64c1e36e493  Miami'05 Euro Trance/10 - Ava Mea  In The End.mp3
-    a7771b91fbe8f0593e5c6ac51ccba4d8  Miami'05 Euro Trance/11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3
-    b167beaafe3fd95b06a1aa574affa355  Miami'05 Euro Trance/12 - Max Graham Feat- Jessica Jacobs  Gone.mp3
-    900bb78b629eab30c16d565562b3880a  Miami'05 Euro Trance/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg
-    9cfd8347becf87da8b1c5962e77267ad  Miami'05 Euro Trance/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg
-    9cfd8347becf87da8b1c5962e77267ad  Miami'05 Euro Trance/AlbumArtSmall.jpg
-    00e8488c206ad9a7ccb6d7f4bc66d05e  Miami'05 Euro Trance/desktop.ini
-    900bb78b629eab30c16d565562b3880a  Miami'05 Euro Trance/Folder.jpg
-    
-    fozz@cobol:/tmp/TEST3 $ git annex unadd .
-    git-annex: Unknown command 'unadd'
-    
-    Did you mean one of these?
-    	unused
-    	unannex
-    	upgrade
-    
-    
-    fozz@cobol:/tmp/TEST3 $ git annex unannex .
-    unannex Miami'05 Euro Trance/01 - Hydroid  Blue Tubes (Intro Mix).mp3 ok
-    unannex Miami'05 Euro Trance/02 - Interstate  I Found U (Harry Lemon Remix).mp3 ok
-    unannex Miami'05 Euro Trance/03 - Kalafut & Fygle  '3579 Km.mp3 ok
-    unannex Miami'05 Euro Trance/04 - Hammer & Bennett  Baltic Sea.mp3 ok
-    unannex Miami'05 Euro Trance/05 - Fluid In Motion  Soul Dimension.mp3 ok
-    unannex Miami'05 Euro Trance/06 - Keo  Close Enough (Noel Sanger Mix).mp3 ok
-    unannex Miami'05 Euro Trance/08 - Lens  Let The Light In.mp3 ok
-    unannex Miami'05 Euro Trance/09 - Aronek  Free Yourself.mp3 ok
-    unannex Miami'05 Euro Trance/10 - Ava Mea  In The End.mp3 ok
-    unannex Miami'05 Euro Trance/11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3 ok
-    unannex Miami'05 Euro Trance/12 - Max Graham Feat- Jessica Jacobs  Gone.mp3 ok
-    unannex Miami'05 Euro Trance/AlbumArtSmall.jpg ok
-    unannex Miami'05 Euro Trance/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg ok
-    unannex Miami'05 Euro Trance/desktop.ini ok
-    (Recording state in git...)
-    
-    fozz@cobol:/tmp/TEST3 $ ls -alh 
-    total 16K
-    drwxrwxr-x  4 fozz fozz 4.0K Jul 28 12:57 .
-    drwxrwxrwt 25 root root 4.0K Jul 28 12:56 ..
-    drwxrwxr-x  9 fozz fozz 4.0K Jul 28 12:57 .git
-    drwx------  2 fozz fozz 4.0K Jul 28 12:57 Miami'05 Euro Trance
-    
-    fozz@cobol:/tmp/TEST3 $ ls -alh Miami\'05\ Euro\ Trance/
-    total 127M
-    drwx------ 2 fozz fozz 4.0K Jul 28 12:57 .
-    drwxrwxr-x 4 fozz fozz 4.0K Jul 28 12:57 ..
-    -rwx------ 1 fozz fozz  13M Jul 28 12:56 01 - Hydroid  Blue Tubes (Intro Mix).mp3
-    -rwx------ 1 fozz fozz 9.8M Jul 28 12:56 02 - Interstate  I Found U (Harry Lemon Remix).mp3
-    -rwx------ 1 fozz fozz  15M Jul 28 12:56 03 - Kalafut & Fygle  '3579 Km.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:56 04 - Hammer & Bennett  Baltic Sea.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:56 05 - Fluid In Motion  Soul Dimension.mp3
-    -rwx------ 1 fozz fozz  12M Jul 28 12:56 06 - Keo  Close Enough (Noel Sanger Mix).mp3
-    -rwx------ 1 fozz fozz 9.4M Jul 28 12:56 08 - Lens  Let The Light In.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:56 09 - Aronek  Free Yourself.mp3
-    -rwx------ 1 fozz fozz  14M Jul 28 12:56 10 - Ava Mea  In The End.mp3
-    -rwx------ 1 fozz fozz  13M Jul 28 12:56 11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3
-    -rwx------ 1 fozz fozz  12M Jul 28 12:56 12 - Max Graham Feat- Jessica Jacobs  Gone.mp3
-    -rwx------ 1 fozz fozz 6.9K Jul 28 12:56 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg
-    lrwxrwxrwx 1 fozz fozz  195 Jul 28 12:56 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg -> ../.git/annex/objects/QF/JK/SHA256E-s2067--b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a.jpg/SHA256E-s2067--b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a.jpg
-    -rwx------ 1 fozz fozz 2.1K Jul 28 12:56 AlbumArtSmall.jpg
-    -rwx------ 1 fozz fozz  361 Jul 28 12:56 desktop.ini
-    lrwxrwxrwx 1 fozz fozz  195 Jul 28 12:56 Folder.jpg -> ../.git/annex/objects/1f/Xk/SHA256E-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f.jpg/SHA256E-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f.jpg
-    
-    fozz@cobol:/tmp/TEST3 $ cd ../
-    
-    fozz@cobol:/tmp $ mkdir TEST4
-    
-    fozz@cobol:/tmp $ cd TEST4
-    
-    fozz@cobol:/tmp/TEST4 $ export PATH=/tmp/git-annex.linux/:$PATH
-    
-    fozz@cobol:/tmp/TEST4 $ git annex version
-    git-annex version: 4.20130725-g8140f7c
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-    
-    fozz@cobol:/tmp/TEST4 $ cp -R /mnt/store/Music/Jukebox/Markus\ Schulz/Miami\'05\ Euro\ Trance/ .
-    
-    fozz@cobol:/tmp/TEST4 $ git init
-    Initialised empty Git repository in /tmp/TEST4/.git/
-    
-    fozz@cobol:/tmp/TEST4 $ git annex init TEST4
-    init TEST4 ok
-    (Recording state in git...)
-    
-    fozz@cobol:/tmp/TEST4 $ git annex add .
-    add Miami'05 Euro Trance/01 - Hydroid  Blue Tubes (Intro Mix).mp3 (checksum...) ok
-    add Miami'05 Euro Trance/02 - Interstate  I Found U (Harry Lemon Remix).mp3 (checksum...) ok
-    add Miami'05 Euro Trance/03 - Kalafut & Fygle  '3579 Km.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/04 - Hammer & Bennett  Baltic Sea.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/05 - Fluid In Motion  Soul Dimension.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/06 - Keo  Close Enough (Noel Sanger Mix).mp3 (checksum...) ok
-    add Miami'05 Euro Trance/08 - Lens  Let The Light In.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/09 - Aronek  Free Yourself.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/10 - Ava Mea  In The End.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/12 - Max Graham Feat- Jessica Jacobs  Gone.mp3 (checksum...) ok
-    add Miami'05 Euro Trance/AlbumArtSmall.jpg (checksum...) ok
-    add Miami'05 Euro Trance/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg (checksum...) ok
-    add Miami'05 Euro Trance/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg (checksum...) ok
-    add Miami'05 Euro Trance/Folder.jpg (checksum...) ok
-    add Miami'05 Euro Trance/desktop.ini (checksum...) ok
-    (Recording state in git...)
-    
-    fozz@cobol:/tmp/TEST4 $ ls -alh Miami\'05\ Euro\ Trance/
-    total 72K
-    drwx------ 2 fozz fozz 4.0K Jul 28 12:59 .
-    drwxrwxr-x 4 fozz fozz 4.0K Jul 28 12:59 ..
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 01 - Hydroid  Blue Tubes (Intro Mix).mp3 -> ../.git/annex/objects/6k/g1/SHA256E-s13016103--3eb29d6f0a529ccb2717b6e2b108c8adb681c47430bdcd45526279fabcfd1be4.mp3/SHA256E-s13016103--3eb29d6f0a529ccb2717b6e2b108c8adb681c47430bdcd45526279fabcfd1be4.mp3
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 02 - Interstate  I Found U (Harry Lemon Remix).mp3 -> ../.git/annex/objects/5X/5J/SHA256E-s10172374--12a9af95efbb5c4928b1ce0750eb25b85b2889a74798cac24165be5b0a085e38.mp3/SHA256E-s10172374--12a9af95efbb5c4928b1ce0750eb25b85b2889a74798cac24165be5b0a085e38.mp3
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 03 - Kalafut & Fygle  '3579 Km.mp3 -> ../.git/annex/objects/6g/FX/SHA256E-s15400659--adce5bdcc75242c3e996dcac7df309fcd2cc32fd5ed04ddcfbbf3c82147de85d.mp3/SHA256E-s15400659--adce5bdcc75242c3e996dcac7df309fcd2cc32fd5ed04ddcfbbf3c82147de85d.mp3
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 04 - Hammer & Bennett  Baltic Sea.mp3 -> ../.git/annex/objects/jV/z0/SHA256E-s10980459--d1ea5664b2c093dcf964f02760a76e8b23b4cadbd7d9e372281f1888b6813c95.mp3/SHA256E-s10980459--d1ea5664b2c093dcf964f02760a76e8b23b4cadbd7d9e372281f1888b6813c95.mp3
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 05 - Fluid In Motion  Soul Dimension.mp3 -> ../.git/annex/objects/q4/5m/SHA256E-s10850525--250366b97e4383fdcc34ffdfa4f5d4231471da4beb600e16c7fb994341241b94.mp3/SHA256E-s10850525--250366b97e4383fdcc34ffdfa4f5d4231471da4beb600e16c7fb994341241b94.mp3
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 06 - Keo  Close Enough (Noel Sanger Mix).mp3 -> ../.git/annex/objects/mW/kF/SHA256E-s11686327--b6fd86d3db9b3ea47338c968f8ba00e8ed263f4c6d17ae148f25802edfc0d743.mp3/SHA256E-s11686327--b6fd86d3db9b3ea47338c968f8ba00e8ed263f4c6d17ae148f25802edfc0d743.mp3
-    lrwxrwxrwx 1 fozz fozz  201 Jul 28 12:59 08 - Lens  Let The Light In.mp3 -> ../.git/annex/objects/Mx/Wv/SHA256E-s9854587--29c1bf00c9bf9076770a1be5c6d697f50a606ad4fcd4a2ada638a12984b38137.mp3/SHA256E-s9854587--29c1bf00c9bf9076770a1be5c6d697f50a606ad4fcd4a2ada638a12984b38137.mp3
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 09 - Aronek  Free Yourself.mp3 -> ../.git/annex/objects/6j/X5/SHA256E-s11110678--9b4744767261bc373c310d423dbd8eeebe8bf88355d88229a5ff1e7036fa845b.mp3/SHA256E-s11110678--9b4744767261bc373c310d423dbd8eeebe8bf88355d88229a5ff1e7036fa845b.mp3
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 10 - Ava Mea  In The End.mp3 -> ../.git/annex/objects/gf/5w/SHA256E-s14527761--ee711177de4d2d3375edf6d1b25c5b0adcb22c16b89dc0ed1bcca5e65e9d916b.mp3/SHA256E-s14527761--ee711177de4d2d3375edf6d1b25c5b0adcb22c16b89dc0ed1bcca5e65e9d916b.mp3
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3 -> ../.git/annex/objects/g7/j8/SHA256E-s12639172--1e348a80570a09d0df8ea5c1ca66743529b6c79b358aae8a661f536a6c6fd412.mp3/SHA256E-s12639172--1e348a80570a09d0df8ea5c1ca66743529b6c79b358aae8a661f536a6c6fd412.mp3
-    lrwxrwxrwx 1 fozz fozz  203 Jul 28 12:59 12 - Max Graham Feat- Jessica Jacobs  Gone.mp3 -> ../.git/annex/objects/0g/g7/SHA256E-s12031267--85094321ce9f272935bcf370d7a6fb9d4f8d3f02d0dffaa30edcf7199b3b1929.mp3/SHA256E-s12031267--85094321ce9f272935bcf370d7a6fb9d4f8d3f02d0dffaa30edcf7199b3b1929.mp3
-    lrwxrwxrwx 1 fozz fozz  195 Jul 28 12:59 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg -> ../.git/annex/objects/1f/Xk/SHA256E-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f.jpg/SHA256E-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f.jpg
-    lrwxrwxrwx 1 fozz fozz  195 Jul 28 12:59 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg -> ../.git/annex/objects/QF/JK/SHA256E-s2067--b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a.jpg/SHA256E-s2067--b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a.jpg
-    lrwxrwxrwx 1 fozz fozz  195 Jul 28 12:59 AlbumArtSmall.jpg -> ../.git/annex/objects/QF/JK/SHA256E-s2067--b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a.jpg/SHA256E-s2067--b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a.jpg
-    lrwxrwxrwx 1 fozz fozz  193 Jul 28 12:59 desktop.ini -> ../.git/annex/objects/Kk/Fj/SHA256E-s361--9762858358f71b43e0dc89f54cf53342ec1c626ee17922b80fa4f981d0bc3a1b.ini/SHA256E-s361--9762858358f71b43e0dc89f54cf53342ec1c626ee17922b80fa4f981d0bc3a1b.ini
-    lrwxrwxrwx 1 fozz fozz  195 Jul 28 12:59 Folder.jpg -> ../.git/annex/objects/1f/Xk/SHA256E-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f.jpg/SHA256E-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f.jpg
-    
-    fozz@cobol:/tmp/TEST4 $ git annex unannex .
-    unannex Miami'05 Euro Trance/01 - Hydroid  Blue Tubes (Intro Mix).mp3 ok
-    unannex Miami'05 Euro Trance/02 - Interstate  I Found U (Harry Lemon Remix).mp3 ok
-    unannex Miami'05 Euro Trance/03 - Kalafut & Fygle  '3579 Km.mp3 ok
-    unannex Miami'05 Euro Trance/04 - Hammer & Bennett  Baltic Sea.mp3 ok
-    unannex Miami'05 Euro Trance/05 - Fluid In Motion  Soul Dimension.mp3 ok
-    unannex Miami'05 Euro Trance/06 - Keo  Close Enough (Noel Sanger Mix).mp3 ok
-    unannex Miami'05 Euro Trance/08 - Lens  Let The Light In.mp3 ok
-    unannex Miami'05 Euro Trance/09 - Aronek  Free Yourself.mp3 ok
-    unannex Miami'05 Euro Trance/10 - Ava Mea  In The End.mp3 ok
-    unannex Miami'05 Euro Trance/11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3 ok
-    unannex Miami'05 Euro Trance/12 - Max Graham Feat- Jessica Jacobs  Gone.mp3 ok
-    unannex Miami'05 Euro Trance/AlbumArtSmall.jpg ok
-    unannex Miami'05 Euro Trance/AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg ok
-    unannex Miami'05 Euro Trance/desktop.ini ok
-    (Recording state in git...)
-    
-    fozz@cobol:/tmp/TEST4 $ ls -alh Miami\'05\ Euro\ Trance/
-    total 127M
-    drwx------ 2 fozz fozz 4.0K Jul 28 13:00 .
-    drwxrwxr-x 4 fozz fozz 4.0K Jul 28 12:59 ..
-    -rwx------ 1 fozz fozz  13M Jul 28 12:59 01 - Hydroid  Blue Tubes (Intro Mix).mp3
-    -rwx------ 1 fozz fozz 9.8M Jul 28 12:59 02 - Interstate  I Found U (Harry Lemon Remix).mp3
-    -rwx------ 1 fozz fozz  15M Jul 28 12:59 03 - Kalafut & Fygle  '3579 Km.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:59 04 - Hammer & Bennett  Baltic Sea.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:59 05 - Fluid In Motion  Soul Dimension.mp3
-    -rwx------ 1 fozz fozz  12M Jul 28 12:59 06 - Keo  Close Enough (Noel Sanger Mix).mp3
-    -rwx------ 1 fozz fozz 9.4M Jul 28 12:59 08 - Lens  Let The Light In.mp3
-    -rwx------ 1 fozz fozz  11M Jul 28 12:59 09 - Aronek  Free Yourself.mp3
-    -rwx------ 1 fozz fozz  14M Jul 28 12:59 10 - Ava Mea  In The End.mp3
-    -rwx------ 1 fozz fozz  13M Jul 28 12:59 11 - Sean Walsh Pres- Jagermaestro  Quarter Century.mp3
-    -rwx------ 1 fozz fozz  12M Jul 28 12:59 12 - Max Graham Feat- Jessica Jacobs  Gone.mp3
-    -rwx------ 1 fozz fozz 6.9K Jul 28 12:59 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Large.jpg
-    lrwxrwxrwx 1 fozz fozz  195 Jul 28 12:59 AlbumArt_{85E86538-46E1-412C-9D94-A67FC108ED97}_Small.jpg -> ../.git/annex/objects/QF/JK/SHA256E-s2067--b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a.jpg/SHA256E-s2067--b870f34a1eee9fdfae8a488626b51d17f25f17788655fe8924d598109a95104a.jpg
-    -rwx------ 1 fozz fozz 2.1K Jul 28 12:59 AlbumArtSmall.jpg
-    -rwx------ 1 fozz fozz  361 Jul 28 12:59 desktop.ini
-    lrwxrwxrwx 1 fozz fozz  195 Jul 28 12:59 Folder.jpg -> ../.git/annex/objects/1f/Xk/SHA256E-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f.jpg/SHA256E-s7024--8d5778605b211e0971824df9a970f16b38dee97a6a529f41113c31378ef83f3f.jpg
-
-Obviously the remaining symlinks in TEST3 and TEST4 are now broken and show up red on my terminal.
-
-"""]]
diff --git a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_5_c0e7742672db2629bd906cebefe74f72._comment b/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_5_c0e7742672db2629bd906cebefe74f72._comment
deleted file mode 100644
index 4b6ae9349..000000000
--- a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_5_c0e7742672db2629bd906cebefe74f72._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.21"
- subject="comment 5"
- date="2013-07-30T18:39:58Z"
- content="""
-Your transcript shows unannex without --fast having the problem, and uninit not having the problem. Which is just what I said. Although I had to spend 15 minutes reading and replicating your transcript to figure that out.
-
-This has been previously reported and discussed at [[Large_unannex_operations_result_in_stale_symlinks_and_data_loss]]. There does not seem to be a single entirely satesfactory solution. unannex --fast seems to be what you're looking for.
-"""]]
diff --git a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_6_c56171665db3ed14109a09097d49ac5d._comment b/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_6_c56171665db3ed14109a09097d49ac5d._comment
deleted file mode 100644
index 692813fbd..000000000
--- a/doc/bugs/unannex_removes_object_even_if_referred_to_by_others/comment_6_c56171665db3ed14109a09097d49ac5d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="comment 6"
- date="2013-07-30T19:01:31Z"
- content="""
-You're right, sorry, I missed the \"--fast\", I'd spent all morning replicating the n~ bug on my phone and recovering from unannex wasn't a short job either.
-"""]]
diff --git a/doc/bugs/unannex_vs_unlock_hook_confusion.mdwn b/doc/bugs/unannex_vs_unlock_hook_confusion.mdwn
deleted file mode 100644
index c03990c20..000000000
--- a/doc/bugs/unannex_vs_unlock_hook_confusion.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-See [[forum/unannex_alternatives]] for problem description.
-
-If an unannex is followed by a "git add; git commit", git-annex's hook thinks
-that you have used git annex unlock on the file and are
-now committing a changed version, and the right thing to do there is to add the
-new content to the annex and update the symlink accordingly.
-
-Can we tell the difference between an unannexed file that has yet to be committed
-and has been re-added as a normal file, vs an unlocked file? --[[Joey||
-
-> Hmm, not really. An unannexed file's content will have been dropped from
-> the backend, but that's about the only difference. Perhaps unannex should
-> just commit the removal of the file itself? --[[Joey]]
-
-> [[done]], staged changes committed at end.
diff --git a/doc/bugs/unfinished_repos_in_webapp.mdwn b/doc/bugs/unfinished_repos_in_webapp.mdwn
deleted file mode 100644
index b3e667c61..000000000
--- a/doc/bugs/unfinished_repos_in_webapp.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-### Please describe the problem.
-
-Hi,  all excited that the new release fixes the unknown UUID issue in the Webapp I hurridly installed the latest versions.  
-
-Some progress in that the webapp now reports my missing/non-existent repo as an "unfinished repository" in the process of being setup.  I see a check status box that when clicked says "in progress please be patient".  Also I see the ssh config has changed to use IdentitiesOnly option.
-
-I had a go a deleting details via git-annex vicfg and directly editing the git-annex branch log files as detailed [here](http://git-annex.branchable.com/forum/Reappearing_repos_in_webapp_and_vicfg/).  But still no joy.  
-
-Any hints on what to do?  Nothing in the log seems to help...
-
-### What steps will reproduce the problem?
-
-Not sure anymore.
-
-### What version of git-annex are you using? On what operating system?
-
-Latest.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> This seems to be [[done]], at least the bug reporter didn't feel the need
-> to follow up with the info I asked for and says the problem does not
-> affect him. --[[Joey]]
diff --git a/doc/bugs/unfinished_repos_in_webapp/comment_1_9628b100e39489be9f28ef75276a7341._comment b/doc/bugs/unfinished_repos_in_webapp/comment_1_9628b100e39489be9f28ef75276a7341._comment
deleted file mode 100644
index e17c1b899..000000000
--- a/doc/bugs/unfinished_repos_in_webapp/comment_1_9628b100e39489be9f28ef75276a7341._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 1"
- date="2013-08-07T16:07:56Z"
- content="""
-It seems to me that it has already finished applying the workaround. That IdentitiesOnly change could only be made
-if you clicked on a Retry button once it detected a problem.
-
-You may be experiencing a different problem that it cannot recover from. Paste your .git/config file.
-"""]]
diff --git a/doc/bugs/unfinished_repos_in_webapp/comment_2_ba0fbff536b1d067c4098db401dc49f2._comment b/doc/bugs/unfinished_repos_in_webapp/comment_2_ba0fbff536b1d067c4098db401dc49f2._comment
deleted file mode 100644
index 8170a0175..000000000
--- a/doc/bugs/unfinished_repos_in_webapp/comment_2_ba0fbff536b1d067c4098db401dc49f2._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU"
- nickname="Matt"
- subject="comment 2"
- date="2013-08-08T08:33:32Z"
- content="""
-Hi, I've sorted this now.  The IP address of my laptop had changed on the local network.  Fixing it then let the new fix fully work and the in-progress status of the bad repo went away.
-
-Is it right that in the UI I don't see the local LAN configured branch (which I setup for speed) - it all seems to come under the jabber account now and makes an appropriate choice?
-"""]]
diff --git a/doc/bugs/unfinished_repos_in_webapp/comment_3_fd554aa7d93117177784a29270ccf790._comment b/doc/bugs/unfinished_repos_in_webapp/comment_3_fd554aa7d93117177784a29270ccf790._comment
deleted file mode 100644
index cd21af092..000000000
--- a/doc/bugs/unfinished_repos_in_webapp/comment_3_fd554aa7d93117177784a29270ccf790._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawniayrgSdVLUc3c6bf93VbO-_HT4hzxmyo"
- nickname="Tobias"
- subject="comment 3"
- date="2013-08-08T12:22:28Z"
- content="""
-I also see `unfinished repository` in the assistant, but only at git remotes which don't have git-annex installed (f.e. gitlab). annex-ignore is set to true: `git config remote.gitlab.annex-ignore true`.
-
-Clicking on `check status` says `Setting up this repository seems to have stalled! Make sure the remote system is available and retry`
-
-git-annex version: 4.20130802-g1452ac3
-"""]]
diff --git a/doc/bugs/unhappy_without_UTF8_locale.mdwn b/doc/bugs/unhappy_without_UTF8_locale.mdwn
deleted file mode 100644
index 8d22b9ee4..000000000
--- a/doc/bugs/unhappy_without_UTF8_locale.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-Try unsetting LANG and passing git-annex unicode filenames.
-
-	joey@gnu:~/tmp/aa>git annex add ./Üa
-	add add add add git-annex: <stdout>: commitAndReleaseBuffer: invalid
-	argument (Invalid or incomplete multibyte or wide character)
-
-> Interestingly, I can get the same crash in the de_DE.UTF-8 locale
-> with certian input filenames, while in en_US.UTF-8, it's ok.
-> The workaround below avoided the problem in de_DE.UTF-8. --[[Joey]]
-
-> Put in the utf-8 forcing workaround for now. [[done]] --[[Joey]] 
-
-## underlying haskell problem and workaround
-
-The same problem can be seen with a simple haskell program:
-
-	import System.Environment
-	import Codec.Binary.UTF8.String
-	main = do
-	        args <- getArgs
-	        putStrLn $ decodeString $ args !! 0
-
-	joey@gnu:~/src/git-annex>LANG= runghc ~/foo.hs Ü
-	foo.hs: <stdout>: hPutChar: invalid argument (Invalid or incomplete multibyte or wide character)
-
-(The call to `decodeString` is necessary to make the input
-unicode string be displayed properly in a utf8 locale, but
-does not contribute to this problem.)
-
-I guess that haskell is setting the IO encoding to latin1, which
-is [documented](http://haskell.org/ghc/docs/latest/html/libraries/base/System-IO.html#v:latin1)
-to error out on characters > 255. 
-
-So this program doesn't have the problem -- but may output garbage
-on non-utf-8 capable terminals:
-
-	import System.IO
-	main = do
- 		hSetEncoding stdout utf8
-	        args <- getArgs
-	        putStrLn $ decodeString $ args !! 0
diff --git a/doc/bugs/unicode_tags.mdwn b/doc/bugs/unicode_tags.mdwn
deleted file mode 100644
index ff3c78666..000000000
--- a/doc/bugs/unicode_tags.mdwn
+++ /dev/null
@@ -1,49 +0,0 @@
-### Please describe the problem.
-
-Add unicode tags, encoding is not right
-
-### What steps will reproduce the problem?
-
-    $ git annex metadata --tag '你好' FOSDEM/2014/AW1120/Saturday/Panel.webm
-    metadata FOSDEM/2014/AW1120/Saturday/Panel.webm
-      lastchanged=2014-05-26@14-53-03
-      tag=`}
-      tag-lastchanged=2014-05-26@14-53-03
-    ok
-    (Recording state in git...)
-    
-    $ git annex metadata --tag test FOSDEM/2014/AW1120/Saturday/Panel.webm
-    metadata FOSDEM/2014/AW1120/Saturday/Panel.webm
-      lastchanged=2014-05-26@14-54-07
-      tag=`}
-      tag=test
-      tag-lastchanged=2014-05-26@14-54-07
-    ok
-    (Recording state in git...)
-
-### What version of git-annex are you using? On what operating system?
-
-OS X 10.9
-
-    $ git annex version
-    git-annex version: 5.20140517-g0aed6d9
-    build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash
-    key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-    remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external
-    local repository version: 5
-    supported repository version: 5
-    upgrade supported from repository versions: 0 1 2 4
-    
-    $ locale
-    LANG="en_US.UTF-8"
-    LC_COLLATE="en_US.UTF-8"
-    LC_CTYPE="en_US.UTF-8"
-    LC_MESSAGES="en_US.UTF-8"
-    LC_MONETARY="en_US.UTF-8"
-    LC_NUMERIC="en_US.UTF-8"
-    LC_TIME="en_US.UTF-8"
-    LC_ALL=
-
-> All strings written to the git-annex branch were truncated to 8 bits.
-> I've fixed this, and this example works now (of course data written with
-> an old git-annex remains truncated). [[done]] --[[Joey]]
diff --git a/doc/bugs/uninit_and_indirect_don__39__t_work_on_android.mdwn b/doc/bugs/uninit_and_indirect_don__39__t_work_on_android.mdwn
deleted file mode 100644
index b3a2ba37c..000000000
--- a/doc/bugs/uninit_and_indirect_don__39__t_work_on_android.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-### Please describe the problem.
-I am unable to restore a git-annex dir to its pre init state.
-
-### What steps will reproduce the problem?
-init a git-annex dir on android with a file system with out symlinks.
-use for a while.
-Run: "git-annex uninit" -> You cannot run this command in a direct mode repository.
-Run: "git-annex indirect" -> Git is configured to not use symlinks, so you must use direct mode.
-
-### What version of git-annex are you using? On what operating system?
-git-annex version: 4.20130601-g7483ca4
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; added support for direct mode --[[Joey]] 
diff --git a/doc/bugs/uninit_and_indirect_don__39__t_work_on_android/comment_1_fec69c4c41987b9469eaa8f745c0a124._comment b/doc/bugs/uninit_and_indirect_don__39__t_work_on_android/comment_1_fec69c4c41987b9469eaa8f745c0a124._comment
deleted file mode 100644
index e310c1afd..000000000
--- a/doc/bugs/uninit_and_indirect_don__39__t_work_on_android/comment_1_fec69c4c41987b9469eaa8f745c0a124._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 1"
- date="2013-07-20T23:20:48Z"
- content="""
-There's no way to make indirect mode work on a filesystem w/o symlinks, but it should be possible to make unannex (required for uninit) work in direct mode. Just has not been done yet.
-"""]]
diff --git a/doc/bugs/uninit_and_indirect_don__39__t_work_on_android/comment_2_54c3fa77a069b36d03c41aad08fee9af._comment b/doc/bugs/uninit_and_indirect_don__39__t_work_on_android/comment_2_54c3fa77a069b36d03c41aad08fee9af._comment
deleted file mode 100644
index ad6d65191..000000000
--- a/doc/bugs/uninit_and_indirect_don__39__t_work_on_android/comment_2_54c3fa77a069b36d03c41aad08fee9af._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm_cen0223TLcWCTPwCPecCQC5JxGnPO04"
- nickname="Eric"
- subject="comment 2"
- date="2013-07-20T23:26:23Z"
- content="""
-unannex an uninit are the main thing, so that people have an exit strategy for git-annex on android.
-"""]]
diff --git a/doc/bugs/uninit_does_not_abort_when_hard_link_creation_fails.mdwn b/doc/bugs/uninit_does_not_abort_when_hard_link_creation_fails.mdwn
deleted file mode 100644
index 2d98929ab..000000000
--- a/doc/bugs/uninit_does_not_abort_when_hard_link_creation_fails.mdwn
+++ /dev/null
@@ -1,47 +0,0 @@
-> What steps will reproduce the problem?
-
-Issue the following commands on a file system where hard links are disabled:
-
-    $ touch foo
-    
-    $ ln foo bar # just to check that hard links are disabled
-    ln: failed to create hard link `bar' => `foo': Operation not permitted
-    
-    $ git init && git annex init
-    
-    $ git annex add .
-    
-    $ git annex uninit
-    unannex foo 
-    git-annex: [...]: createLink: permission denied (Operation not permitted)
-    failed
-    Deleted branch git-annex [...].
-
-    $ echo $? # exit status of last command
-    0
-    
-    $ ls foo
-    ls: cannot access foo: No such file or directory
-
-
-> What is the expected output? What do you see instead?
-
-`git annex uninit` should abort and exit with a non-`0` return code. Instead, `git annex uninit` cleans up git-annex objects and exits with return code `0`.
-
-
-> What version of git-annex are you using? On what operating system?
-
-3.20120406 on Ubuntu 12.04.1.
-
-
-> Please provide any additional information below.
-
-git-annex should probably not be used on a file system where hard links are disabled.
-
-However, if the user is not aware that he's using git-annex on such a filesystem, he will accidently delete his annexed files by issuing a `git annex uninit` command.
-
-> git-annex needs a POSIX filesystem, which includes the ability to create
-> hard links. The `git annex add` in the example above will fail
-> trying to create a hard link with current versions.
-> 
-> I've made uninit fall back to a non-hard link mode. [[done]] --[[Joey]]
diff --git a/doc/bugs/uninit_does_not_work_in_old_repos.mdwn b/doc/bugs/uninit_does_not_work_in_old_repos.mdwn
deleted file mode 100644
index d3df06148..000000000
--- a/doc/bugs/uninit_does_not_work_in_old_repos.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-As uninit does not need to actually write out any data, just remove it, it should be possible to uninit in old stores.
-
-    % git annex uninit
-    git-annex: Repository version 2 is not supported. Upgrade this repository: git-annex upgrade
-
-If the repo happens to be broken, this essentially locks in data.
-
-> No, because you can always check out the version of git-annex you need
-> for that repository.
-> 
-> uninit, as implemented, runs unannex on every file and then does some
-> cleanup. The cleanup does not need to write state, but the unannex does.
-> And it depends on the object directory layout, which has changed between
-> versions. So supporting old versions in this code would complicate it
-> quite a lot. I don't want to go there. --[[Joey]]
-
->>Requiring a version upgrade for unannex is fine. Yet, I see a problem when a git repo is broken; you are stuck without being able to uninit. In this case an uninit that does nothing but undo the symlinking would be useful. -- Richard
-
->>> As I said, version 2 of git-annex is still there for people who need
->>> it for whatever reason. [[done]] --[[Joey]]
diff --git a/doc/bugs/uninit_does_not_work_in_old_repos/comment_1_bc0619c6e17139df74639448aa6a0f72._comment b/doc/bugs/uninit_does_not_work_in_old_repos/comment_1_bc0619c6e17139df74639448aa6a0f72._comment
deleted file mode 100644
index 7a1ea582b..000000000
--- a/doc/bugs/uninit_does_not_work_in_old_repos/comment_1_bc0619c6e17139df74639448aa6a0f72._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-10-29T15:30:09Z"
- content="""
-After upgrading the repo, I still have to commit the changes, else git-annex won't let me uninit. Arguably a Good Thing, but I wanted to document it here.
-"""]]
diff --git a/doc/bugs/uninit_loses_data_if_git-annex_add_didn__39__t_complete.mdwn b/doc/bugs/uninit_loses_data_if_git-annex_add_didn__39__t_complete.mdwn
deleted file mode 100644
index 61cfa89a5..000000000
--- a/doc/bugs/uninit_loses_data_if_git-annex_add_didn__39__t_complete.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-* Create a git-annex repo where a lot of files live.
-* Start an annex add.
-* Kill it.
-* git-annex uninit
-
-Now, whatever files were annexed (ie: moved to .git/annex/objects/) but not committed are lost as the .git/annex directory was deleted.
-
-I know there are two conflicting issues here:
-
-1. if there is legitimately unused data in .git/annex then that shouldn't be unannexed
-2. the above case where some files were annexed but not committed should be unannexed
-
-Maybe uninit could check to see if all symlinks currently in the repo pointing to something under .git/annex/objects are committed. If not, commit them then uninit, or just de-annex them.
-
-> Added a check for this, [[done]] --[[Joey]] 
diff --git a/doc/bugs/uninit_should_not_run_when_branch_git-annex_is_checked_out.mdwn b/doc/bugs/uninit_should_not_run_when_branch_git-annex_is_checked_out.mdwn
deleted file mode 100644
index e4e407ec8..000000000
--- a/doc/bugs/uninit_should_not_run_when_branch_git-annex_is_checked_out.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-Running `git annex uninit` in a repo which has branch git-annex checked out will result in:
-
-    error: Cannot delete the branch 'git-annex' which you are currently on.
-    git-annex: git [Param "-D",Param "git-annex"] failed
-
-and trying to checkout branch master afterwards results in:
-
-    error: The following untracked working tree files would be overwritten by checkout:
-
-Both of which is logical. The best thing would be if git-annex refused to run uninit while in branch git-annex.
-
-
-Richard
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/unlock_fails_silently_with_directory_symlinks.mdwn b/doc/bugs/unlock_fails_silently_with_directory_symlinks.mdwn
deleted file mode 100644
index 9b9bb6342..000000000
--- a/doc/bugs/unlock_fails_silently_with_directory_symlinks.mdwn
+++ /dev/null
@@ -1,53 +0,0 @@
-What steps will reproduce the problem?
-
-+    ```~/``` is tracked by git and git annex
-+    ```~/text/books/foo``` is annexed
-+    ```~/books``` is a symlink to ```text/books```
-+    from ```~/``` execute: ```git annex unlock books/foo```
-+    which returns immediately with zero exit code and does not unlock foo.
-
-What is the expected output? What do you see instead?
-
-+    I expect ```~/text/books/foo`` to be unlocked
-
-+    I think ```git annex unlock``` should resolve the symlinks and realize that this is a tracked file.
-
-What version of git-annex are you using? On what operating system?
-
-+    3.20121112 in debian unstable
-
-Please provide any additional information below.
-
-+    I can unlock foo if I provide the full path, eg:
-from ```~/``` execute: ```git annex unlock text/books/foo```
-
-+    Interestingly, the following _does_ successfully unlock the file: ```cd ~/books && git annex unlock foo```
-
-     So it seems that symlinks in $PWD are being resolved, but not those in file paths passed as arguments.
-
-Thank you, thank you!
-
-      - Jason
-
-jason@jasonwoof.com
-
-> I'm afraid this is not a bug. Here's why: If you run "git mv books/foo
-> books/bar", git will complain:
->
->> fatal: not under version control, source=books/foo, destination=books/bar
->
-> So git-annex is just following git's lead (indeed, it's just running
-> `git ls-files` to find files to act on), and git doesn't
-> recognise this path as a file that's in git. --[[Joey]] 
-
-+    Also, I think ```git annex unlock``` should emit an error message if a file explicitly addressed on the commandline can not be acted upon.
-
-> I'm beginning to think perhaps it should. Users seem to find the current
-> behavior to be sometimes confusing.
-> 
-> However, it's actually a very difficult change to make. Several commands
-> have multiple seek stages that act on different types of files, so
-> any warning printed by an earlier stage may be premature if a later
-> stage comes along and deals with a file. --[[Joey]]
-
->> Figured out a non-invasive way to add that warning. [[done]] --[[Joey]] 
diff --git a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_.mdwn b/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_.mdwn
deleted file mode 100644
index 3704334f3..000000000
--- a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-What steps will reproduce the problem?
-
-    try to unlock a file in a git annex checkout
-
-What is the expected output? What do you see instead?
-
-    % git annex unlock FILENAME
-    unlock FILENAME (copying...) cp: illegal option -- -
-    usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvX] source_file target_file
-           cp [-R [-H | -L | -P]] [-fi | -n] [-apvX] source_file ... target_directory
-    git-annex: copy failed!
-
-    (should unlock the file)
-
-What version of git-annex are you using? On what operating system?
-
-    latest git annex osx build as of yesterday (12-11-03)
-
-
-> I've made the `cp` command be included in the OSX standalone build, 
-> so it will use the same one it's built with. So the next time we get
-> an OSX build this will be fixed. [[done]] --[[Joey]]
diff --git a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_1_a634a9f1c023bf836183de64abab1224._comment b/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_1_a634a9f1c023bf836183de64abab1224._comment
deleted file mode 100644
index 3e322a0b6..000000000
--- a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_1_a634a9f1c023bf836183de64abab1224._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.194"
- subject="comment 1"
- date="2012-11-04T20:03:47Z"
- content="""
-Did you build this git-annex yourself? On the same machine?
-
-What does it say if you add the `--debug` option?
-"""]]
diff --git a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_2_d9ae61a7c3f1eb243ca650945b40f21d._comment b/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_2_d9ae61a7c3f1eb243ca650945b40f21d._comment
deleted file mode 100644
index 98d42e59d..000000000
--- a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_2_d9ae61a7c3f1eb243ca650945b40f21d._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmmPHsszTlpa3s3x_LEzmEYkZfEmqq7IjU"
- nickname="Jan"
- subject="comment 2"
- date="2012-11-05T01:23:41Z"
- content="""
-Thanks for the quick response :)
-I think the problem is that the os x cp does not support ''--reflink\" (and gnu long options). I guess I could install gnu coreutils through homebrew, though those will be prefixed with a g in the name.
-My OS version is 10.6.8 btw.
-
-    % git annex --debug unlock FILENAME
-    [2012-11-04 20:17:47 EST] read: git [\"--git-dir=/PATH/.git\",\"--work-tree=/PATH\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"FILENAME\"]
-    unlock FILENAME (copying...) [2012-11-04 20:17:47 EST] call: cp [\"--reflink=auto\",\"-a\",\"/PATH/.git/annex/objects/8P/Qp/SHA256-s7173120--33c3482bf70807bb5caede9859d10a73bda9279f08340556188c93dea7e5be05/SHA256-s7173120--33c3482bf70807bb5caede9859d10a73bda9279f08340556188c93dea7e5be05\",\"/PATH/.git/annex/tmp/SHA256-s7173120--33c3482bf70807bb5caede9859d10a73bda9279f08340556188c93dea7e5be05\"]
-    cp: illegal option -- -
-    usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvX] source_file target_file
-           cp [-R [-H | -L | -P]] [-fi | -n] [-apvX] source_file ... target_directory
-    git-annex: copy failed!
-
-"""]]
diff --git a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_3_fe229c03c14e8eb2b57389e0e193ed99._comment b/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_3_fe229c03c14e8eb2b57389e0e193ed99._comment
deleted file mode 100644
index 576202d92..000000000
--- a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_3_fe229c03c14e8eb2b57389e0e193ed99._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmmPHsszTlpa3s3x_LEzmEYkZfEmqq7IjU"
- nickname="Jan"
- subject="comment 3"
- date="2012-11-05T01:24:32Z"
- content="""
-Ah, forgot to mention: I am running the latest build downloaded from the website (as mentioned above), so no, I did not build it myself.
-"""]]
diff --git a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_4_fa12afe295de63c4aa7eb043b715325a._comment b/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_4_fa12afe295de63c4aa7eb043b715325a._comment
deleted file mode 100644
index d96a469d9..000000000
--- a/doc/bugs/unlock_not_working_on_os_x_10.6_-_cp:_illegal_option_--_-_/comment_4_fa12afe295de63c4aa7eb043b715325a._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmmPHsszTlpa3s3x_LEzmEYkZfEmqq7IjU"
- nickname="Jan"
- subject="exact version"
- date="2012-11-05T01:34:29Z"
- content="""
-    % git annex version
-    git-annex version: 3.20121017
-    local repository version: 3
-    default repository version: 3
-    supported repository versions: 3
-    upgrade supported from repository versions: 0 1 2
-
-Also, while browsing the archive for another problem (can not add files because shasum256 is missing and I get a \"dyld: Library not loaded: /opt/local/lib/libintl.8.dylib\" for it's execution when I add the path for /Applications/git-annex.app/Contents/MacOS/bin/sha256sum) I [saw](http://git-annex.branchable.com/install/OSX/old_comments/#comment-94b0f0ba446ca2f1ebd6af44c7afd3be) that it should fall back on haskell code - which it doesn't, so maybe its an old version?
-"""]]
diff --git a/doc/bugs/unlock_then_lock_of_uncommitted_file_loses_it.mdwn b/doc/bugs/unlock_then_lock_of_uncommitted_file_loses_it.mdwn
deleted file mode 100644
index 9c093de38..000000000
--- a/doc/bugs/unlock_then_lock_of_uncommitted_file_loses_it.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-Add a file (do not commit), then unlock it, and then lock it.
-There is an error and the symlink gets deleted.
-
-The file will still be staged in the index, and the file content is still
-in the annex. --[[Joey]] 
-
-[[done]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again.mdwn b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again.mdwn
deleted file mode 100644
index 2517fa647..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again.mdwn
+++ /dev/null
@@ -1,434 +0,0 @@
-### Please describe the problem.
-
-recently upgraded to a git snapshot; restarted assistant and found my disk space disappearing.  Checked webapp and there were a bunch of transfers queued.  Restarted assistant in --debug mode to get some logs.
-
-Transfers should not have happened, because I'm on a "client" machine, they are in an archive subdirectory, and there are adequate copies elsewhere (a ssh remote and a USB drive) to satisfy "numcopies=2."  (Note that the USB drive was not connected at the time, but that hasn't mattered in the past)
-
-### What steps will reproduce the problem?
-
-As noted above. I don't know that this is reproducible in a fresh repo; I was hoping that a bug report with the log would do.  Can try if that would help.
-
-### What version of git-annex are you using? On what operating system?
-
-checkout hash is:
-
-70ba425 2013-04-07
-
-OS X Lion.
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/debug.log
-
-
-[13:13:55 PM]$ cat daemon.log
-[2013-04-26 12:59:09 EDT] main: starting assistant version 4.20130406
-[2013-04-26 12:59:09 EDT] TransferScanner: Syncing with toshiba, homeworld 
-[2013-04-26 12:59:09 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:09 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:09 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 12:59:09 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:09 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:09 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..bfa73167b1cd90bbb2213a2c9bad64fbb1befe00","--oneline","-n1"]
-[2013-04-26 12:59:09 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","symbolic-ref","HEAD"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","refs/heads/master"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..bfa73167b1cd90bbb2213a2c9bad64fbb1befe00","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-[2013-04-26 12:59:10 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","fetch","toshiba"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","symbolic-ref","HEAD"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","refs/heads/master"]
-[2013-04-26 12:59:10 EDT] Merger: merging refs/heads/synced/master into refs/heads/master
-[2013-04-26 12:59:10 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","merge","--no-edit","refs/heads/synced/master"]
-fatal: '/Volumes/TOSHIBAEXT/annex' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-[2013-04-26 12:59:10 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","fetch","homeworld"]
-Already up-to-date.
-
-(scanning...) [2013-04-26 12:59:10 EDT] Watcher: Performing startup scan
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..bfa73167b1cd90bbb2213a2c9bad64fbb1befe00","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..bfa73167b1cd90bbb2213a2c9bad64fbb1befe00","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","symbolic-ref","HEAD"]
-[2013-04-26 12:59:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","refs/heads/master"]
-[2013-04-26 12:59:10 EDT] Merger: merging refs/remotes/homeworld/synced/master into refs/heads/master
-[2013-04-26 12:59:10 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","merge","--no-edit","refs/remotes/homeworld/synced/master"]
-Already up-to-date.
-[2013-04-26 12:59:11 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:11 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:11 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 12:59:11 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:11 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:11 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..bfa73167b1cd90bbb2213a2c9bad64fbb1befe00","--oneline","-n1"]
-[2013-04-26 12:59:11 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:12 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:12 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:12 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:12 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 12:59:13 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:13 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:13 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..bfa73167b1cd90bbb2213a2c9bad64fbb1befe00","--oneline","-n1"]
-[2013-04-26 12:59:13 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:14 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:14 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:14 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:14 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 12:59:14 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:14 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:14 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..bfa73167b1cd90bbb2213a2c9bad64fbb1befe00","--oneline","-n1"]
-[2013-04-26 12:59:14 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:14 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:15 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","symbolic-ref","HEAD"]
-[2013-04-26 12:59:15 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","refs/heads/master"]
-[2013-04-26 12:59:15 EDT] Merger: merging refs/remotes/toshiba/synced/master into refs/heads/master
-[2013-04-26 12:59:15 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--verify","-q","refs/remotes/toshiba/master"]
-[2013-04-26 12:59:15 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/master..refs/remotes/toshiba/master","--oneline","-n1"]
-[2013-04-26 12:59:20 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--verify","-q","refs/remotes/toshiba/synced/master"]
-[2013-04-26 12:59:20 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/synced/master..refs/remotes/toshiba/synced/master","--oneline","-n1"]
-[2013-04-26 12:59:20 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","merge","--no-edit","refs/remotes/toshiba/synced/master"]
-Already up-to-date.
-[2013-04-26 12:59:20 EDT] Merger: watching /Users/ed/annex/.git/refs
-[2013-04-26 12:59:20 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--verify","-q","refs/remotes/homeworld/master"]
-[2013-04-26 12:59:20 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/master..refs/remotes/homeworld/master","--oneline","-n1"]
-[2013-04-26 12:59:20 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--verify","-q","refs/remotes/homeworld/synced/master"]
-[2013-04-26 12:59:20 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/synced/master..refs/remotes/homeworld/synced/master","--oneline","-n1"]
-[2013-04-26 12:59:20 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","symbolic-ref","HEAD"]
-[2013-04-26 12:59:21 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","refs/heads/master"]
-[2013-04-26 12:59:21 EDT] TransferScanner: pushing to [Remote { name ="toshiba" },Remote { name ="homeworld" }]
-[2013-04-26 12:59:21 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","branch","-f","synced/master"]
-[2013-04-26 12:59:21 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","push","toshiba","git-annex:synced/git-annex","master:synced/master"]
-fatal: '/Volumes/TOSHIBAEXT/annex' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-[2013-04-26 12:59:21 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","push","homeworld","git-annex:synced/git-annex","master:synced/master"]
-[2013-04-26 12:59:21 EDT] TransferWatcher: watching for transfers
-To ssh://ed@homeworld/srv/mybook/annex
-   bfa7316..9a8e676  git-annex -> synced/git-annex
-[2013-04-26 12:59:36 EDT] TransferScanner: trying manual pull to resolve failed pushes
-[2013-04-26 12:59:36 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","fetch","toshiba"]
-fatal: '/Volumes/TOSHIBAEXT/annex' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-[2013-04-26 12:59:36 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:36 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:36 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 12:59:36 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:36 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:37 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--verify","-q","refs/remotes/toshiba/master"]
-[2013-04-26 12:59:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/master..refs/remotes/toshiba/master","--oneline","-n1"]
-[2013-04-26 12:59:37 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--verify","-q","refs/remotes/toshiba/synced/master"]
-[2013-04-26 12:59:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/synced/master..refs/remotes/toshiba/synced/master","--oneline","-n1"]
-[2013-04-26 12:59:37 EDT] TransferScanner: pushing to [Remote { name ="toshiba" }]
-[2013-04-26 12:59:37 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","branch","-f","synced/master"]
-[2013-04-26 12:59:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:37 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","push","toshiba","git-annex:synced/git-annex","master:synced/master"]
-[2013-04-26 12:59:37 EDT] read: git ["--git-dir=/Users/ed/annex/fatal: '/Volumes/TOSHIBAEXT/annex' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:37 EDT] TransferScanner: fallback pushing to [Remote { name ="toshiba" }]
-[2013-04-26 12:59:37 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","push","toshiba","git-annex:refs/synced/fa2bd02e-3ce2-11e2-a675-47389975a32e/git-annex","refs/heads/master:refs/synced/fa2bd02e-3ce2-11e2-a675-47389975a32e/master"]
-[2013-04-26 12:59:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-fatal: '/Volumes/TOSHIBAEXT/annex' does not appear to be a git repository
-fatal: Could not read from remote repository.
-
-Please make sure you have the correct access rights
-and the repository exists.
-[2013-04-26 12:59:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:38 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:38 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:38 EDT] 127.0.0.1 GET / Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:39 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 12:59:39 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 12:59:39 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 12:59:39 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 12:59:39 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 12:59:39 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 12:59:39 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 12:59:39 EDT] chat: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","cat-file","--batch"]
-[2013-04-26 12:59:39 EDT] read: git ["config","--null","--list"]
-[2013-04-26 12:59:40 EDT] TransferScanner: starting scan of [Remote { name ="toshiba" },Remote { name ="homeworld" }]
-[2013-04-26 12:59:40 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","ls-files","--cached","-z","--"]
-[2013-04-26 12:59:40 EDT] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:40 EDT] chat: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","check-attr","-z","--stdin","annex.backend","annex.numcopies","--"]
-[2013-04-26 12:59:41 EDT] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:41 EDT] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:41 EDT] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:41 EDT] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:41 EDT] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:41 EDT] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:41 EDT] 127.0.0.1 GET /static/jquery.ui.core.js Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:41 EDT] 127.0.0.1 GET /static/jquery.ui.widget.js Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /static/jquery.ui.mouse.js Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /static/jquery.ui.sortable.js Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /notifier/transfers Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%200)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:42 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:43 EDT] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:43 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 12:59:43 EDT] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%200)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-[2013-04-26 13:00:27 EDT] TransferScanner: queued Download UUID "429af61a-3cf6-11e2-af0a-170be35d46b6" Books/archive/Art books/John Gadsby Chapman - American Drawing-Book - A Manual for the Amateur.pdf.part Nothing : expensive scan found missing object
-[2013-04-26 13:00:27 EDT] TransferScanner: queued Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/John Gadsby Chapman - American Drawing-Book - A Manual for the Amateur.pdf.part Nothing : expensive scan found missing object
-[2013-04-26 13:00:27 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:27 EDT] Transferrer: Transferring: Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/John Gadsby Chapman - American Drawing-Book - A Manual for the Amateur.pdf.part Nothing
-[2013-04-26 13:00:27 EDT] call: /Users/ed/bin/git-annex ["transferkeys","--readfd","34","--writefd","31"]
-[2013-04-26 13:00:27 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:27 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:27 EDT] TransferScanner: queued Download UUID "429af61a-3cf6-11e2-af0a-170be35d46b6" Books/archive/Art books/L.A. Doust - A Manual on Drawing the Human Figure.pdf.part Nothing : expensive scan found missing object
-[2013-04-26 13:00:27 EDT] TransferScanner: queued Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/L.A. Doust - A Manual on Drawing the Human Figure.pdf.part Nothing : expensive scan found missing object
-[2013-04-26 13:00:27 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:28 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:28 EDT] TransferScanner: queued Download UUID "429af61a-3cf6-11e2-af0a-170be35d46b6" Books/archive/Art books/Michael D. Mattesi - Force. The Key to Capturing Life Through Drawing.pdf Nothing : expensive scan found missing object
-[2013-04-26 13:00:28 EDT] TransferScanner: queued Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/Michael D. Mattesi - Force. The Key to Capturing Life Through Drawing.pdf Nothing : expensive scan found missing object
-[2013-04-26 13:00:28 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:28 EDT] TransferScanner: queued Download UUID "429af61a-3cf6-11e2-af0a-170be35d46b6" Books/archive/Art books/Richard G. Hatton - Figure Drawing.pdf Nothing : expensive scan found missing object
-[2013-04-26 13:00:28 EDT] TransferScanner: queued Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/Richard G. Hatton - Figure Drawing.pdf Nothing : expensive scan found missing object
-[2013-04-26 13:00:28 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:28 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:28 EDT] TransferScanner: queued Download UUID "429af61a-3cf6-11e2-af0a-170be35d46b6" Books/archive/Art books/The Figure in Repose.pdf Nothing : expensive scan found missing object
-Control socket connect(/Users/ed/annex/.git/annex/ssh/ed@homeworld): Connection refused
-[2013-04-26 13:00:28 EDT] TransferWatcher: transfer starting: Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/John Gadsby Chapman - American Drawing-Book - A Manual for the Amateur.pdf.part Nothing
-[2013-04-26 13:00:28 EDT] TransferScanner: queued Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/The Figure in Repose.pdf Nothing : expensive scan found missing object
-[2013-04-26 13:00:28 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:28 EDT] TransferWatcher: transfer starting: Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/John Gadsby Chapman - American Drawing-Book - A Manual for the Amateur.pdf.part Nothing
-[2013-04-26 13:00:28 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:28 EDT] TransferScanner: queued Download UUID "429af61a-3cf6-11e2-af0a-170be35d46b6" Books/archive/Art books/Torrent downloaded from Demonoid.com.txt Nothing : expensive scan found missing object
-[2013-04-26 13:00:28 EDT] TransferScanner: queued Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/Torrent downloaded from Demonoid.com.txt Nothing : expensive scan found missing object
-[2013-04-26 13:00:29 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:29 EDT] TransferScanner: queued Download UUID "429af61a-3cf6-11e2-af0a-170be35d46b6" Books/archive/Art books/Victor Perard - Drawing and Anatomy.pdf Nothing : expensive scan found missing object
-[2013-04-26 13:00:29 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:29 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-ControlSocket /Users/ed/annex/.git/annex/ssh/ed@homeworld already exists, disabling multiplexing
-
-SHA256E-s568690--ec5aaaf0320739ab91e4efa9a0bfd372a92ca436e96a5182a3d072ba409691b5.pdf.part
-[2013-04-26 13:00:31 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:33 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-      568690 100%  185.12kB/s    0:00:03 (xfer#1, to-check=0/1)
-
-sent 42 bytes  received 568933 bytes  87534.62 bytes/sec
-total size is 568690  speedup is 1.00
-[2013-04-26 13:00:34 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:35 EDT] Transferrer: Downloaded John Gads...pdf.part
-[2013-04-26 13:00:35 EDT] TransferWatcher: transfer finishing: Transfer {transferDirection = Download, transferUUID = UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720", transferKey = Key {keyName = "ec5aaaf0320739ab91e4efa9a0bfd372a92ca436e96a5182a3d072ba409691b5.pdf.part", keyBackendName = "SHA256E", keySize = Just 568690, keyMtime = Nothing}}
-[2013-04-26 13:00:35 EDT] Pusher: Syncing with homeworld 
-[2013-04-26 13:00:35 EDT] TransferScanner: queued Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/Victor Perard - Drawing and Anatomy.pdf Nothing : expensive scan found missing object
-[2013-04-26 13:00:35 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:35 EDT] Transferrer: Transferring: Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/L.A. Doust - A Manual on Drawing the Human Figure.pdf.part Nothing
-[2013-04-26 13:00:35 EDT] chat: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","hash-object","-w","--stdin-paths"]
-[2013-04-26 13:00:35 EDT] feed: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","update-index","-z","--index-info"]
-[2013-04-26 13:00:35 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:35 EDT] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:35 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-Control socket connect(/Users/ed/annex/.git/annex/ssh/ed@homeworld): Connection refused
-[2013-04-26 13:00:35 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 13:00:35 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","write-tree"]
-[2013-04-26 13:00:35 EDT] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:36 EDT] chat: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","commit-tree","24ad0c0244cd209b4689b2b3877645971fe88084","-p","refs/heads/git-annex"]
-[2013-04-26 13:00:36 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","update-ref","refs/heads/git-annex","726dd240a1e79cf0ce481f9875b5358b56c250b7"]
-[2013-04-26 13:00:36 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","symbolic-ref","HEAD"]
-[2013-04-26 13:00:36 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","refs/heads/master"]
-[2013-04-26 13:00:36 EDT] Pusher: pushing to [Remote { name ="homeworld" }]
-[2013-04-26 13:00:36 EDT] TransferWatcher: transfer starting: Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/L.A. Doust - A Manual on Drawing the Human Figure.pdf.part Nothing
-[2013-04-26 13:00:36 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","branch","-f","synced/master"]
-[2013-04-26 13:00:36 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","push","homeworld","git-annex:synced/git-annex","master:synced/master"]
-[2013-04-26 13:00:36 EDT] TransferWatcher: transfer starting: Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/L.A. Doust - A Manual on Drawing the Human Figure.pdf.part Nothing
-[2013-04-26 13:00:36 EDT] TransferScanner: queued Download UUID "429af61a-3cf6-11e2-af0a-170be35d46b6" Books/archive/Art books/Willy Pogany - Art of Drawing.pdf Nothing : expensive scan found missing object
-[2013-04-26 13:00:36 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:36 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-ControlSocket /Users/ed/annex/.git/annex/ssh/ed@homeworld already exists, disabling multiplexing
-[2013-04-26 13:00:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 13:00:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 13:00:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..726dd240a1e79cf0ce481f9875b5358b56c250b7","--oneline","-n1"]
-[2013-04-26 13:00:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 13:00:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 13:00:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..9a8e676d552905528b25e29ae9c56b5e50c35f70","--oneline","-n1"]
-[2013-04-26 13:00:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 13:00:37 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-
-SHA256E-s3733003--1536ff33f9a59112d40ff816f731f3fd96554f0c42acc9df758e59350176d616.pdf.part
-[2013-04-26 13:00:38 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:39 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:41 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:43 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:44 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:44 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","ls-files","--deleted","-z","--","/Users/ed/annex"]
-
-
-(Recording state in git...)
-(started...) [2013-04-26 13:00:44 EDT] Watcher: watching .
-[2013-04-26 13:00:44 EDT] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:46 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:47 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:48 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:50 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-To ssh://ed@homeworld/srv/mybook/annex09
-   9a8e676..726dd24  git-annex -> synced/git-annex
-[2013-04-26 13:00:50 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 13:00:50 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 13:00:50 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..726dd240a1e79cf0ce481f9875b5358b56c250b7","--oneline","-n1"]
-[2013-04-26 13:00:50 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 13:00:50 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 13:00:50 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 13:00:51 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 13:00:51 EDT] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:51 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:53 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:54 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:56 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:57 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-     3733003 100%  175.37kB/s    0:00:20 (xfer#1, to-check=0/1)
-[2013-04-26 13:00:59 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-
-sent 42 bytes  received 3733631 bytes  152394.82 bytes/sec
-total size is 3733003  speedup is 1.00
-[2013-04-26 13:00:59 EDT] Transferrer: Downloaded L.A. Dous...pdf.part
-[2013-04-26 13:00:59 EDT] Pusher: Syncing with homeworld 
-[2013-04-26 13:00:59 EDT] chat: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","hash-object","-w","--stdin-paths"]
-[2013-04-26 13:00:59 EDT] feed: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","update-index","-z","--index-info"]
-[2013-04-26 13:00:59 EDT] TransferWatcher: transfer finishing: Transfer {transferDirection = Download, transferUUID = UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720", transferKey = Key {keyName = "1536ff33f9a59112d40ff816f731f3fd96554f0c42acc9df758e59350176d616.pdf.part", keyBackendName = "SHA256E", keySize = Just 3733003, keyMtime = Nothing}}
-[2013-04-26 13:00:59 EDT] TransferScanner: queued Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/Willy Pogany - Art of Drawing.pdf Nothing : expensive scan found missing object
-[2013-04-26 13:00:59 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:59 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 13:00:59 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","write-tree"]
-[2013-04-26 13:00:59 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:59 EDT] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:59 EDT] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:59 EDT] chat: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","commit-tree","2b93aa36603e01e699d332fb277874488ab21c1f","-p","refs/heads/git-annex"]
-[2013-04-26 13:00:59 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","update-ref","refs/heads/git-annex","58f45e4a8453d7bb3c1612bd910410eee0e2c72a"]
-[2013-04-26 13:00:59 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","symbolic-ref","HEAD"]
-[2013-04-26 13:00:59 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","refs/heads/master"]
-[2013-04-26 13:00:59 EDT] Pusher: pushing to [Remote { name ="homeworld" }]
-[2013-04-26 13:00:59 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","branch","-f","synced/master"]
-[2013-04-26 13:00:59 EDT] call: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","push","homeworld","git-annex:synced/git-annex","master:synced/master"]
-[2013-04-26 13:00:59 EDT] Transferrer: Transferring: Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/Michael D. Mattesi - Force. The Key to Capturing Life Through Drawing.pdf Nothing
-[2013-04-26 13:00:59 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:59 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:00:59 EDT] TransferScanner: queued Download UUID "429af61a-3cf6-11e2-af0a-170be35d46b6" Books/archive/Magic  in china.PDF Nothing : expensive scan found missing object
-Control socket connect(/Users/ed/annex/.git/annex/ssh/ed@homeworld): Connection refused
-[2013-04-26 13:00:59 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:00 EDT] TransferWatcher: transfer starting: Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/Michael D. Mattesi - Force. The Key to Capturing Life Through Drawing.pdf Nothing
-[2013-04-26 13:01:00 EDT] TransferWatcher: transfer starting: Download UUID "d16d0d1a-3cdd-11e2-9161-67c83599f720" Books/archive/Art books/Michael D. Mattesi - Force. The Key to Capturing Life Through Drawing.pdf Nothing
-[2013-04-26 13:01:00 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:00 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:00 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 13:01:00 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 13:01:00 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..58f45e4a8453d7bb3c1612bd910410eee0e2c72a","--oneline","-n1"]
-[2013-04-26 13:01:00 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 13:01:00 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 13:01:00 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..726dd240a1e79cf0ce481f9875b5358b56c250b7","--oneline","-n1"]
-ControlSocket /Users/ed/annex/.git/annex/ssh/ed@homeworld already exists, disabling multiplexing
-[2013-04-26 13:01:00 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 13:01:00 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-
-SHA256E-s41718677--71d082deb0cdac45ae5556322cc5fa9245dafe477d3f3b7186fd19876e12e335.pdf
-[2013-04-26 13:01:02 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-To ssh://ed@homeworld/srv/mybook/annex12
-   726dd24..58f45e4  git-annex -> synced/git-annex
-[2013-04-26 13:01:03 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","git-annex"]
-[2013-04-26 13:01:03 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","show-ref","--hash","refs/heads/git-annex"]
-[2013-04-26 13:01:03 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..58f45e4a8453d7bb3c1612bd910410eee0e2c72a","--oneline","-n1"]
-[2013-04-26 13:01:03 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..c19f5f18ea26d43b735de8fbdb67d4f85987d171","--oneline","-n1"]
-[2013-04-26 13:01:03 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..7077e8c56be8c84fee214456bb2c951ef5b2202e","--oneline","-n1"]
-[2013-04-26 13:01:03 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..f7a2f8f189db99c7f9f4bacc2fc935d63737287e","--oneline","-n1"]
-[2013-04-26 13:01:04 EDT] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:04 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","log","refs/heads/git-annex..be505749576a7064cca1eaf9fc241b450cdaadc6","--oneline","-n1"]
-[2013-04-26 13:01:04 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:05 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:07 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:08 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:10 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:10 EDT] read: git ["--git-dir=/Users/ed/annex/.git","--work-tree=/Users/ed/annex","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"]
-[2013-04-26 13:01:11 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:13 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:14 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:16 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:17 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:18 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:20 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:21 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:23 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:24 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:26 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:27 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:29 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:30 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:32 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:33 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:35 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:36 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:38 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:39 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:41 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:42 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:43 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:45 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:46 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-[2013-04-26 13:01:48 EDT] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0
-recv: resource vanished (Connection reset by peer)
-    41718677 100%  173.12kB/s    0:03:55 (xfer#1, to-check=0/1)
-
-sent 42 bytes  received 41723941 bytes  174943.32 bytes/sec
-total size is 41718677  speedup is 1.00
-
-git-annex: <file descriptor: 31>: hFlush: resource vanished (Broken pipe)
-failed
-(Recording state in git...)
-git-annex: transferkeys: 1 failed
-~/annex/.git/annex (GIT_DIR!)
-[13:14:08 PM]$ 
-
-# End of transcript or log.
-"""]]
-
-Here is the typical status of a file queued for download:
-
-whereis Art books/The Figure in Repose.pdf (2 copies) 
-  	429af61a-3cf6-11e2-af0a-170be35d46b6 -- toshiba (toshiba external hd)
-   	d16d0d1a-3cdd-11e2-9161-67c83599f720 -- homeworld
-
-This is with "numcopies=2"  homeworld is trusted, backup, standard.  toshiba is semitrusted, backup, standard.  here is client, semitrusted, standard.
-
-[[done]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_10_51097a6b84edcc607abc0e6e21ca21f2._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_10_51097a6b84edcc607abc0e6e21ca21f2._comment
deleted file mode 100644
index 3e4e39e24..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_10_51097a6b84edcc607abc0e6e21ca21f2._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 10"
- date="2013-04-28T18:12:30Z"
- content="""
-oh, but to answer your earlier question,  \"(archive + smallarchive >= numcopies)\" would be exactly what I needed to get the behavior I want and have the others be archive directories.
-"""]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_1_c34a4009213c410bba3c147ae0552029._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_1_c34a4009213c410bba3c147ae0552029._comment
deleted file mode 100644
index e85829179..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_1_c34a4009213c410bba3c147ae0552029._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="173.162.44.162"
- subject="comment 1"
- date="2013-04-26T17:46:50Z"
- content="""
-Tried again with the usb drive plugged in; still kept trying to transfer archive content, which was present in 2 other places (that usb drive and the ssh remote), down from the ssh remote.
-
-Tried disabling syncing from the ssh remote in the webapp; the assistant finished the last transfer from it and queued up a bunch of transfers from the USB remote instead.
-
-Turned assistant off completely; tried a \"git annex drop --auto\".  (with the USB drive still plugged in.)  Nothing dropped.
-
-Tried a \"git annex drop --in=here '*/archive/*'\" -- it dropped all the content from my archive directories.  whew!
-
-"""]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_2_634542867fd28962c47b7bc3ea022175._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_2_634542867fd28962c47b7bc3ea022175._comment
deleted file mode 100644
index 5f69f10d0..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_2_634542867fd28962c47b7bc3ea022175._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 2"
- date="2013-04-27T05:45:53Z"
- content="""
-update -- compiled a fresh copy of git annex from master ( 1bdfec9 2013-04-24 ) -- same effect; archived content is pulled down to the client from one of the backups, despite numcopies being satisfied by the backups.
-"""]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_3_301f3ff2d203ac4c58a037e553b2c14d._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_3_301f3ff2d203ac4c58a037e553b2c14d._comment
deleted file mode 100644
index f69cef333..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_3_301f3ff2d203ac4c58a037e553b2c14d._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-04-27T19:35:15Z"
- content="""
-Are either the USB drive or the ssh remote configured to be in the archive or smallarchive group?
-
-If not, there was a recent change to how archive directories are handled, which would explain this behavior:
-
-<pre>
-  * Adjust preferred content expressions so that content in archive
-    directories is preferred until it has reached an archive or smallarchive
-    repository.
-</pre>
-
-The solution would be to make the USB drive be in the archive group, probably..
-"""]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_4_82ecdc88ccc1f87386b128adc4ff9af4._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_4_82ecdc88ccc1f87386b128adc4ff9af4._comment
deleted file mode 100644
index f7c701922..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_4_82ecdc88ccc1f87386b128adc4ff9af4._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 4"
- date="2013-04-27T20:51:03Z"
- content="""
-They are both \"backup\" not \"archive.\"  I had thought that backups pretty much counted as archives, but I guess this new behavior requires actual *archive* directories to do its job.
-
-Not sure what would be the best way to achieve my goals now, which are \"the usb and ssh remote want everything, the client wants to get rid of what's in archive directories if it's backed up in two backup directories.\"
-
-I can probably write a custom preferred content expression to do the job (I could copy the existing \"client\" one and replace \"archive\" with \"backup\" for example), but if there's a good way to do it with standard expressions I'd be curious to know.
-
-Thanks for the explanation!
-"""]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_6_158b2ba3da815910505899606177d415._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_6_158b2ba3da815910505899606177d415._comment
deleted file mode 100644
index cdd39bf3f..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_6_158b2ba3da815910505899606177d415._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 6"
- date="2013-04-27T21:26:11Z"
- content="""
-I'm glad this wasn't a nasty bug!
-
-I'm not really sold on its current behavior WRT archive directories and backups.  It seemed to make sense at the time.. The differences between archives and backups are subtle enough that I'd sort of like to avoid confusing them by making backups be sorta treated like archives.
-
-Nor am I entirely thrilled with the current hardcoded \"(copies=archive:1 or copies=smallarchive:1)\" that makes any given file be stored in only 1 archive repository. What's really wanted, but cannot currently be expressed with preferred content syntax is \"(archive + smallarchive >= numcopies)\"
-
-If it did that, sounds like you could convert your usb and ssh remotes to be archives and not need anything custom?
-
-I think that, as things stand, the only way to get what you want without a custom expression is to set one of the remotes, perhaps the SSH remote, to be an archive repository. Then files will be copies to both SSH (because it's the only archive), and to the USB backup (because backups want all files). And once both have a copy, numcopies will be satisfied, and files in archive/ directories will be archived, so the client will drop them.
-"""]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_6_b068924802f3917e3e005350cb0cc2a2._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_6_b068924802f3917e3e005350cb0cc2a2._comment
deleted file mode 100644
index c48e8c429..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_6_b068924802f3917e3e005350cb0cc2a2._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 6"
- date="2013-04-27T21:44:19Z"
- content="""
-I *think* that'd work... the only thing would be that the SSH remote wouldn't get any files that *weren't* in archive directories, right?  They'd migrate from the client to the backup to satisfy numcopies, and that would be it, two copies and we're done.  Since it's not in an archive directory, the ssh remote doesn't want it.
-"""]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_7_f4772858c927d4a62edc3caf59b5da10._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_7_f4772858c927d4a62edc3caf59b5da10._comment
deleted file mode 100644
index 709305098..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_7_f4772858c927d4a62edc3caf59b5da10._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 7"
- date="2013-04-27T21:56:24Z"
- content="""
-Nope, you're thinking of smallarchive. archive wants files in any directory. Should work.
-"""]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_8_d0923d2950357f4444c5ef94ff196ba3._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_8_d0923d2950357f4444c5ef94ff196ba3._comment
deleted file mode 100644
index b0211e106..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_8_d0923d2950357f4444c5ef94ff196ba3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 8"
- date="2013-04-28T05:59:53Z"
- content="""
-Just set it up that way.  Looking good so far!  I'll check in again later when I'm sure things are better.
-"""]]
diff --git a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_9_7fb30cb80aecc60e48c64846aa185206._comment b/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_9_7fb30cb80aecc60e48c64846aa185206._comment
deleted file mode 100644
index 26b903823..000000000
--- a/doc/bugs/upgraded_annex__44___suddenly_trying_to_grab_archive_content_onto_client_again/comment_9_7fb30cb80aecc60e48c64846aa185206._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://edheil.wordpress.com/"
- ip="99.54.57.201"
- subject="comment 9"
- date="2013-04-28T17:01:29Z"
- content="""
-Yeah that did it.  Thanks!  I'm not sure why I wasn't using Archive all along!
-
-"""]]
diff --git a/doc/bugs/utf8.mdwn b/doc/bugs/utf8.mdwn
deleted file mode 100644
index 73b9bd9a9..000000000
--- a/doc/bugs/utf8.mdwn
+++ /dev/null
@@ -1,192 +0,0 @@
-### Please describe the problem.
-
-Git Annex stumbles and does not transfer files with special characters...
-
-
-### What steps will reproduce the problem?
-
-Added the file "Freddie_Mercury/Barcelona_[+video]/B00921KHNS_(disc_1)_04_-_Ensueño_(New_Orchestrated_Version).mp3" to Git Annex on my Galaxy Nexus (Android), which was committed successfully but not gettable.
-
-
-### What version of git-annex are you using? On what operating system?
-
-Phone: 4.20130709-g339d1eo
-Transfer Server: 3.20120406 (which it did not get to)
-Desktop: 3.20120629
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-fozz@cobol:~/Phone $ git annex get
-get Freddie_Mercury/Barcelona_[+video]/B00921KHNS_(disc_1)_04_-_Ensueño_(New_Orchestrated_Version).mp3 (not available) 
-  Try making some of these repositories available:
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-failed
-get Freddie_Mercury/Barcelona_[+video]/B00921KKSA_(disc_2)_05_-_Ensueño_(Monsterrat's_Live_Takes).mp3 (not available) 
-  Try making some of these repositories available:
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-failed
-get Freddie_Mercury/Barcelona_[+video]/B00921KMYW_(disc_3)_04_-_Ensueno_(Orchestral_Version).mp3 (not available) 
-  Try making some of these repositories available:
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-failed
-get Freddie_Mercury/Barcelona_[+video]/B00921KMYW_(disc_3)_04_-_Ensueño_(Orchestral_Version).mp3 (not available) 
-  Try making some of these repositories available:
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-failed
-git-annex: get: 4 failed
-
-===============
-
-fozz@cobol:~/Phone $ git annex whereis Freddie_Mercury/
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KGRK_(disc_1)_01_-_Barcelona_(New_Orchestrated_Version.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KH5G_(disc_1)_02_-_La_Japonaise_(New_Orchestrated_Vers.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KHD8_(disc_1)_03_-_The_Fallen_Priest_(New_Orchestrated.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KHNS_(disc_1)_04_-_Ensueño_(New_Orchestrated_Version).mp3 (1 copy) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KHY2_(disc_1)_05_-_The_Golden_Boy_(New_Orchestrated_Ve.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KI9G_(disc_1)_06_-_Guide_Me_Home_(New_Orchestrated_Ver.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KIIW_(disc_1)_07_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KITG_(disc_1)_08_-_Exercises_In_Free_Love_(New_Orchest.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KJ22_(disc_1)_09_-_Overture_Piccante_(New_Orchestrated.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KJB8_(disc_1)_10_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KJMW_(disc_2)_01_-_Exercises_In_Free_Love_(1987_B-Side.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KJVI_(disc_2)_02_-_Barcelona_(Early_Version__Freddie's.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KK5I_(disc_2)_03_-_La_Japonaise_(Early_Version__Freddi.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KKHQ_(disc_2)_04_-_Rachmaninov's_Revenge_(The_Fallen_P.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KKSA_(disc_2)_05_-_Ensueño_(Monsterrat's_Live_Takes).mp3 (1 copy) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KL2U_(disc_2)_06_-_The_Golden_Boy_(Early_Version__Fred.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KLBQ_(disc_2)_07_-_Guide_Me_Home_(Alternative_Version).mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KLJI_(disc_2)_08_-_How_Can_I_Go_On_(Alternative_Versio.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KLUC_(disc_2)_09_-_How_Can_I_Go_On_(Alternative_Piano_.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KM3I_(disc_3)_01_-_Barcelona_(Orchestral_Version).mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KMBU_(disc_3)_02_-_La_Japonaise_(Orchestral_Version).mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KMM4_(disc_3)_03_-_The_Fallen_Priest_(Orchestral_Versi.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KMYW_(disc_3)_04_-_Ensueno_(Orchestral_Version).mp3 (1 copy) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KMYW_(disc_3)_04_-_Ensueño_(Orchestral_Version).mp3 (1 copy) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KNAK_(disc_3)_05_-_The_Golden_Boy_(Orchestral_Version).mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KNUA_(disc_3)_06_-_Guide_Me_Home_(Orchestral_Version).mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KOVI_(disc_3)_07_-_How_Can_I_Go_On_(Orchestral_Version.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KPP8_(disc_3)_08_-_Exercises_In_Free_Love_(Orchestral_.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-whereis Freddie_Mercury/Barcelona_[+video]/B00921KQJ8_(disc_3)_09_-_Overture_Piccante_(Orchestral_Versi.mp3 (3 copies) 
-  	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-   	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-   	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-ok
-
-
-# End of transcript or log.
-"""]]
-
-> We seem to have reached a point of confusion, lack of information,
-> and/or diminishing returns with this bug report. I have fixed
-> it as best I can. If you have any problems, please file a new bug report
-> with as complete information as possible. [[done]] --[[Joey]]
diff --git a/doc/bugs/utf8/comment_10_f298b8b480d3ab2dd9c279589afcd0ea._comment b/doc/bugs/utf8/comment_10_f298b8b480d3ab2dd9c279589afcd0ea._comment
deleted file mode 100644
index 7a61fc0d5..000000000
--- a/doc/bugs/utf8/comment_10_f298b8b480d3ab2dd9c279589afcd0ea._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="Ooops"
- date="2013-07-26T21:28:46Z"
- content="""
-Hi Joey,
-
-I started replicating it today but managed to make annex a directory structure I did not mean to through my own silly fault and it's taking ages to unannex, I'll have another go over the weekend, this time with not so fat fingers!
-"""]]
diff --git a/doc/bugs/utf8/comment_11_a8864a46f8154680beeea27449ac6f09._comment b/doc/bugs/utf8/comment_11_a8864a46f8154680beeea27449ac6f09._comment
deleted file mode 100644
index 50822a094..000000000
--- a/doc/bugs/utf8/comment_11_a8864a46f8154680beeea27449ac6f09._comment
+++ /dev/null
@@ -1,142 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="Replicated, I think"
- date="2013-07-27T10:02:32Z"
- content="""
-I think I have it replicated, I did not do _exactly_ the same thing, no renaming of the tilde-n file but I still got the ControlPath error.
-
-    # On phone - Copy folder into Git Annex... wait till done
-    # On Server with new Git Annex: git annex sync
-    fozz@markdown:~/tmp/zzz$ git annex get .
-    get Freddie_Mercury/Barcelona_[+video]/B00921KGRK_(disc_1)_01_-_Barcelona_(New_Orchestrated_Version.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KH5G_(disc_1)_02_-_La_Japonaise_(New_Orchestrated_Vers.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KHD8_(disc_1)_03_-_The_Fallen_Priest_(New_Orchestrated.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KHNS_(disc_1)_04_-_Ensueño_(New_Orchestrated_Version).mp3 (not available)
-      Try making some of these repositories available:
-            bc0525c4-cf9e-45da-a8e1-19003dee1dcb -- u0_a84@localhost:/sdcard/annex
-    failed
-    get Freddie_Mercury/Barcelona_[+video]/B00921KHY2_(disc_1)_05_-_The_Golden_Boy_(New_Orchestrated_Ve.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KI9G_(disc_1)_06_-_Guide_Me_Home_(New_Orchestrated_Ver.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KIIW_(disc_1)_07_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3 ^[[A^[[A^[[A^[[A^[[A^[[A(from origin...) ^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[Aok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KITG_(disc_1)_08_-_Exercises_In_Free_Love_(New_Orchest.mp3 ^[[A^[[A^[[A^[[A^[[A^[[A(from origin...) ^[[A^[[A^[[A^[[A^[[A^[[Aok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KJ22_(disc_1)_09_-_Overture_Piccante_(New_Orchestrated.mp3 ^C
-    fozz@markdown:~/tmp/zzz$ git annex get .
-    get Freddie_Mercury/Barcelona_[+video]/B00921KHNS_(disc_1)_04_-_Ensueño_(New_Orchestrated_Version).mp3 (not available)
-      Try making some of these repositories available:
-            bc0525c4-cf9e-45da-a8e1-19003dee1dcb -- u0_a84@localhost:/sdcard/annex
-    failed
-    get Freddie_Mercury/Barcelona_[+video]/B00921KJ22_(disc_1)_09_-_Overture_Piccante_(New_Orchestrated.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KJB8_(disc_1)_10_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KJMW_(disc_2)_01_-_Exercises_In_Free_Love_(1987_B-Side.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KJVI_(disc_2)_02_-_Barcelona_(Early_Version__Freddie's.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KK5I_(disc_2)_03_-_La_Japonaise_(Early_Version__Freddi.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KKHQ_(disc_2)_04_-_Rachmaninov's_Revenge_(The_Fallen_P.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KKSA_(disc_2)_05_-_Ensueño_(Monsterrat's_Live_Takes).mp3 (not available)
-      Try making some of these repositories available:
-            bc0525c4-cf9e-45da-a8e1-19003dee1dcb -- u0_a84@localhost:/sdcard/annex
-    failed
-    get Freddie_Mercury/Barcelona_[+video]/B00921KL2U_(disc_2)_06_-_The_Golden_Boy_(Early_Version__Fred.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KLBQ_(disc_2)_07_-_Guide_Me_Home_(Alternative_Version).mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KLJI_(disc_2)_08_-_How_Can_I_Go_On_(Alternative_Versio.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KLUC_(disc_2)_09_-_How_Can_I_Go_On_(Alternative_Piano_.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KM3I_(disc_3)_01_-_Barcelona_(Orchestral_Version).mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KMBU_(disc_3)_02_-_La_Japonaise_(Orchestral_Version).mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KMM4_(disc_3)_03_-_The_Fallen_Priest_(Orchestral_Versi.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KMYW_(disc_3)_04_-_Ensueño_(Orchestral_Version).mp3 (not available)
-      Try making some of these repositories available:
-            bc0525c4-cf9e-45da-a8e1-19003dee1dcb -- u0_a84@localhost:/sdcard/annex
-    failed
-    get Freddie_Mercury/Barcelona_[+video]/B00921KNAK_(disc_3)_05_-_The_Golden_Boy_(Orchestral_Version).mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KNUA_(disc_3)_06_-_Guide_Me_Home_(Orchestral_Version).mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KOVI_(disc_3)_07_-_How_Can_I_Go_On_(Orchestral_Version.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KPP8_(disc_3)_08_-_Exercises_In_Free_Love_(Orchestral_.mp3 (from origin...) ok
-    get Freddie_Mercury/Barcelona_[+video]/B00921KQJ8_(disc_3)_09_-_Overture_Piccante_(Orchestral_Versi.mp3 (from origin...) ok
-    (Recording state in git...)
-    git-annex: get: 3 failed
-    
-    fozz@markdown:~/tmp/zzz$ git annex whereis Freddie_Mercury/Barcelona_\[+video\]/B00921KMYW_\(disc_3\)_04_-_Ensueño_\(Orchestral_Version\).mp3 
-    whereis Freddie_Mercury/Barcelona_[+video]/B00921KMYW_(disc_3)_04_-_Ensueño_(Orchestral_Version).mp3 (1 copy) 
-            bc0525c4-cf9e-45da-a8e1-19003dee1dcb -- u0_a84@localhost:/sdcard/annex
-    		ok
-    
-    # On phone
-    Falling back to hardcoded app location; cannot find expected files in /data/app-lib
-    git annex webapp
-    u0_a84@android:/sdcard/git-annex.home $ git annex webapp
-    
-      Detected a crippled filesystem.
-    
-      Enabling direct mode.
-    fozz@markdown.lang.speechmarks.com's password:
-    fozz@markdown.lang.speechmarks.com's password:
-    ^Z[1] + Stopped              git annex webapp
-    u0_a84@android:/sdcard/git-annex.home $ bg
-    [1] git annex webapp
-    u0_a84@android:/sdcard/git-annex.home $ cd ../annex/
-    u0_a84@android:/sdcard/annex $ ls
-    Freddie_Mercury
-    u0_a84@android:/sdcard/annex $ git remote -v
-    markdown.lang.speechmarks.com_phoneannex        ssh://fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex/~/phone-annex/ (fetch)
-    markdown.lang.speechmarks.com_phoneannex        ssh://fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex/~/phone-annex/ (push)
-    u0_a84@android:/sdcard/annex $ git annex copy . --to markdown.lang.speechmarks.com_phoneannex
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KGRK_(disc_1)_01_-_Barcelona_(New_Orchestrated_Version.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.IdWwlXHtSsjVUMcq\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KH5G_(disc_1)_02_-_La_Japonaise_(New_Orchestrated_Vers.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.WisPICyIHiMGEO3k\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KHD8_(disc_1)_03_-_The_Fallen_Priest_(New_Orchestrated.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.hYyDKddvBHgjW4AI\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KHNS_(disc_1)_04_-_Ensueo_(New_Orchestrated_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.PR2s7Btep0Vklpr1\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KHY2_(disc_1)_05_-_The_Golden_Boy_(New_Orchestrated_Ve.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.GuiE6O9sVgvAsPjv\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KI9G_(disc_1)_06_-_Guide_Me_Home_(New_Orchestrated_Ver.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.MNE7Nrd4rTe59BpR\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KIIW_(disc_1)_07_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.MtXCKPHds4ma0iPl\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KITG_(disc_1)_08_-_Exercises_In_Free_Love_(New_Orchest.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.6iovvzKR6HE4nZwz\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KJ22_(disc_1)_09_-_Overture_Piccante_(New_Orchestrated.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.wZy825TDcYvHhDUx\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KJB8_(disc_1)_10_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.RQLLAcX2MGpLvJC5\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KJMW_(disc_2)_01_-_Exercises_In_Free_Love_(1987_B-Side.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.kiQQXvKBLNSP3cRO\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KJVI_(disc_2)_02_-_Barcelona_(Early_Version__Freddie's.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.CIdY4uFDFCIboOpG\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KK5I_(disc_2)_03_-_La_Japonaise_(Early_Version__Freddi.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.sza5nEOnJ4qnh6op\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KKHQ_(disc_2)_04_-_Rachmaninov's_Revenge_(The_Fallen_P.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.PXT6QfTHojjPvlBM\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KKSA_(disc_2)_05_-_Ensueo_(Monsterrat's_Live_Takes).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.LaHS26WonwTUqBDO\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KL2U_(disc_2)_06_-_The_Golden_Boy_(Early_Version__Fred.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.rw9hP3fjehIAJc1P\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KLBQ_(disc_2)_07_-_Guide_Me_Home_(Alternative_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.aJOWNwtRBDG6pecN\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KLJI_(disc_2)_08_-_How_Can_I_Go_On_(Alternative_Versio.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.fOFCaugrRAzzHAMZ\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KLUC_(disc_2)_09_-_How_Can_I_Go_On_(Alternative_Piano_.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.onG8CR4YP9x5c3ZK\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KM3I_(disc_3)_01_-_Barcelona_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.KgOqB8Rg1ZZI1fzP\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KMBU_(disc_3)_02_-_La_Japonaise_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.xN1FqoX79hSxwQS7\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KMM4_(disc_3)_03_-_The_Fallen_Priest_(Orchestral_Versi.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.YpZgAo1LVawkOIBd\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KMYW_(disc_3)_04_-_Ensueo_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.TDvJl5gPqOFTbqgF\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KNAK_(disc_3)_05_-_The_Golden_Boy_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.CYBfRJuMZTYUgTnN\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KNUA_(disc_3)_06_-_Guide_Me_Home_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.VjyVTH1bRjeRl7fE\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KOVI_(disc_3)_07_-_How_Can_I_Go_On_(Orchestral_Version.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.SfA8ZMsoaea1JqZm\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KPP8_(disc_3)_08_-_Exercises_In_Free_Love_(Orchestral_.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.uYsVLhxvYZl1F7Dj\" too long for Unix domain socket
-    ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KQJ8_(disc_3)_09_-_Overture_Piccante_(Orchestral_Versi.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ControlPath \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.NRAFY6O124W6tAdG\" too long for Unix domain socket
-    ok
-    (Recording state in git...)
-    u0_a84@android:/sdcard/annex $
-
-"""]]
diff --git a/doc/bugs/utf8/comment_12_2202c3479d19d306f31aac5a47b55e7d._comment b/doc/bugs/utf8/comment_12_2202c3479d19d306f31aac5a47b55e7d._comment
deleted file mode 100644
index 50adfd847..000000000
--- a/doc/bugs/utf8/comment_12_2202c3479d19d306f31aac5a47b55e7d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.110"
- subject="comment 12"
- date="2013-07-27T17:46:11Z"
- content="""
-Ok, I think if you upgrade to the current build for Android, you'll find that the problem goes away. I put in a fix several days ago that makes it use much shorter controlpaths.
-
-The question remains why it ever used a path of \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.IdWwlXHtSsjVUMcq\". This is 110 bytes; the code checks for a path of longer than 99 bytes. It should have disabled ssh connection caching when it was unable to construct a short enough path.
-"""]]
diff --git a/doc/bugs/utf8/comment_13_7044d2c5bb1c91ee37eb9868963a1ff2._comment b/doc/bugs/utf8/comment_13_7044d2c5bb1c91ee37eb9868963a1ff2._comment
deleted file mode 100644
index 651e43438..000000000
--- a/doc/bugs/utf8/comment_13_7044d2c5bb1c91ee37eb9868963a1ff2._comment
+++ /dev/null
@@ -1,41 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.110"
- subject="comment 13"
- date="2013-07-27T20:46:01Z"
- content="""
-I've verified that the (old) code correctly returned no path when it's too long:
-
-<pre>
-*Annex.Ssh System.Directory System.Posix.Directory Annex Git.Construct Git.Config System.Posix.Env Utility.Env>  eval (newState r') $ changeGitConfig (\c -> c  { annexCrippledFileSystem = True  }) >> sshInfo (\"fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.IdWwlXHtSsjVUMcq\", Nothing)
-(Nothing,[])
-</pre>
-
-In case the problem was somehow related to calculating the length on Android (ie, Data.Bits.Utils broken), I built a small program that calculated the length of the string the same way
-
-[[!format haskell \"\"\"
-import Utility.FileSystemEncoding
-
-main = do
-	let s = \"/data/data/ga.androidterm/tmp/fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.IdWwlXHtSsjVUMcq\"
-	let ws = decodeW8 s
-	print (length ws)
-\"\"\"]]
-
-Outputs 110 on Android as expected.
-
-Finally, using git-annex 4.20130721-g002de3e on Android (a newer version than the bug reporter's but with no changes to Annex.Ssh), I manually set up a repository using the same hostname:
-
-<pre>
-[remote \"foo\"]
-	url = ssh://fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.IdWwlXHtSsjVUMcq
-	fetch = +refs/heads/*:refs/remotes/foo/*
-	annex-uuid = dummy
-</pre>
-
-And still cannot replicate the bug; as expected it does not use the socket since it's too long:
-
-copy foo (checking foo...) [2013-07-27 16:40:42 EDT] call: ssh [\"-T\",\"fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex.IdWwlXHtSsjVUMcq\",\"git-annex-shell 'inannex' '' 'SHA256E-s29--093429efb0d1427753d1f038f5279ec4df66785a1b2429b3fa5e3a01bcb75bd8' --uuid 111\"]
-
-So, I don't understand how this could have happened. Although my recent changes mean it'll use a 62 byte path max on Android now, which certainly should avoid the problem, even if there's some actual bug here that I cannot reproduce.
-"""]]
diff --git a/doc/bugs/utf8/comment_14_656b3caa16ae93b092fb5804fa575a3b._comment b/doc/bugs/utf8/comment_14_656b3caa16ae93b092fb5804fa575a3b._comment
deleted file mode 100644
index 6c858013b..000000000
--- a/doc/bugs/utf8/comment_14_656b3caa16ae93b092fb5804fa575a3b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="Will give the new version a got tomorrow..."
- date="2013-07-27T21:45:29Z"
- content="""
-But do you have any idea why it didn't transfer the filename with the ~ above the n?
-"""]]
diff --git a/doc/bugs/utf8/comment_15_25b3d4c47c45b72129b17b171a45c5f9._comment b/doc/bugs/utf8/comment_15_25b3d4c47c45b72129b17b171a45c5f9._comment
deleted file mode 100644
index 8fb44eebd..000000000
--- a/doc/bugs/utf8/comment_15_25b3d4c47c45b72129b17b171a45c5f9._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.110"
- subject="comment 15"
- date="2013-07-27T21:50:32Z"
- content="""
-AFAICS it was failing to transfer every file, no matter what the name, due to the socket length too long problem.
-"""]]
diff --git a/doc/bugs/utf8/comment_16_2aaab9253bbc75012292c7b5a7d55696._comment b/doc/bugs/utf8/comment_16_2aaab9253bbc75012292c7b5a7d55696._comment
deleted file mode 100644
index e10b8f85a..000000000
--- a/doc/bugs/utf8/comment_16_2aaab9253bbc75012292c7b5a7d55696._comment
+++ /dev/null
@@ -1,173 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="Not completely..."
- date="2013-07-28T11:44:40Z"
- content="""
-So done a bit of testing this morning...
-
-I upgraded the Git Annex on my phone and added a text file called \"mañnequin\" into my Git Annex. The assistant web app did not do anything and it did not appear on my desktop when I sync'd... So I went to my phone manually added it and synced. Which then did make it appear on my desktop when I did a sync.
-
-Phone Log:
-
-    Falling back to hardcoded app location; cannot find expected files in /data/app-lib
-    git annex webapp
-    u0_a84@android:/sdcard/git-annex.home $ git annex webapp
-    ^Z[1] + Stopped              git annex webapp
-    u0_a84@android:/sdcard/git-annex.home $ bg
-    [1] git annex webapp
-    u0_a84@android:/sdcard/git-annex.home $ cd ../annex/
-    u0_a84@android:/sdcard/annex $ git remote -v
-    markdown.lang.speechmarks.com_phoneannex        ssh://fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex/~/phone-annex/ (fetch)
-    markdown.lang.speechmarks.com_phoneannex        ssh://fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex/~/phone-annex/ (push)
-    u0_a84@android:/sdcard/annex $ git-annex version
-    git-annex version: 4.20130723-ged05a63
-    build flags: Assistant Webapp Testsuite S3 WebDAV Inotify XMPP DNS
-    local repository version: 4
-    default repository version: 3
-    supported repository versions: 3 4
-    upgrade supported from repository versions: 0 1 2
-    u0_a84@android:/sdcard/annex $ git annex copy . --to markdown.lang.speechmarks.com_phoneannex
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KGRK_(disc_1)_01_-_Barcelona_(New_Orchestrated_Version.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KH5G_(disc_1)_02_-_La_Japonaise_(New_Orchestrated_Vers.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KHD8_(disc_1)_03_-_The_Fallen_Priest_(New_Orchestrated.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KHNS_(disc_1)_04_-_Ensueo_(New_Orchestrated_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KHY2_(disc_1)_05_-_The_Golden_Boy_(New_Orchestrated_Ve.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KI9G_(disc_1)_06_-_Guide_Me_Home_(New_Orchestrated_Ver.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KIIW_(disc_1)_07_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KITG_(disc_1)_08_-_Exercises_In_Free_Love_(New_Orchest.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KJ22_(disc_1)_09_-_Overture_Piccante_(New_Orchestrated.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KJB8_(disc_1)_10_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KJMW_(disc_2)_01_-_Exercises_In_Free_Love_(1987_B-Side.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KJVI_(disc_2)_02_-_Barcelona_(Early_Version__Freddie's.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KK5I_(disc_2)_03_-_La_Japonaise_(Early_Version__Freddi.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KKHQ_(disc_2)_04_-_Rachmaninov's_Revenge_(The_Fallen_P.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KKSA_(disc_2)_05_-_Ensueo_(Monsterrat's_Live_Takes).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KL2U_(disc_2)_06_-_The_Golden_Boy_(Early_Version__Fred.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KLBQ_(disc_2)_07_-_Guide_Me_Home_(Alternative_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KLJI_(disc_2)_08_-_How_Can_I_Go_On_(Alternative_Versio.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KLUC_(disc_2)_09_-_How_Can_I_Go_On_(Alternative_Piano_.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KM3I_(disc_3)_01_-_Barcelona_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KMBU_(disc_3)_02_-_La_Japonaise_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KMM4_(disc_3)_03_-_The_Fallen_Priest_(Orchestral_Versi.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KMYW_(disc_3)_04_-_Ensueo_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KNAK_(disc_3)_05_-_The_Golden_Boy_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KNUA_(disc_3)_06_-_Guide_Me_Home_(Orchestral_Version).mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KOVI_(disc_3)_07_-_How_Can_I_Go_On_(Orchestral_Version.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KPP8_(disc_3)_08_-_Exercises_In_Free_Love_(Orchestral_.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    copy Freddie_Mercury/Barcelona_[+video]/B00921KQJ8_(disc_3)_09_-_Overture_Piccante_(Orchestral_Versi.mp3 (checking markdown.lang.speechmarks.com_phoneannex...) ok
-    u0_a84@android:/sdcard/annex $ ls
-    Freddie_Mercury
-    u0_a84@android:/sdcard/annex $ ls
-    ls     lsattr lsmod  lsof   lspci  lsusb
-    rcury/Barcelona_\[+video]/B00921K                                                                <
-    B00921KGRK_(disc_1)_01_-_Barcelona_(New_Orchestrated_Version.mp3
-    B00921KH5G_(disc_1)_02_-_La_Japonaise_(New_Orchestrated_Vers.mp3
-    B00921KHD8_(disc_1)_03_-_The_Fallen_Priest_(New_Orchestrated.mp3
-    B00921KHNS_(disc_1)_04_-_Ensueo_(New_Orchestrated_Version).mp3
-    B00921KHY2_(disc_1)_05_-_The_Golden_Boy_(New_Orchestrated_Ve.mp3
-    B00921KI9G_(disc_1)_06_-_Guide_Me_Home_(New_Orchestrated_Ver.mp3
-    B00921KIIW_(disc_1)_07_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3
-    B00921KITG_(disc_1)_08_-_Exercises_In_Free_Love_(New_Orchest.mp3
-    B00921KJ22_(disc_1)_09_-_Overture_Piccante_(New_Orchestrated.mp3
-    B00921KJB8_(disc_1)_10_-_How_Can_I_Go_On_(New_Orchestrated_V.mp3
-    B00921KJMW_(disc_2)_01_-_Exercises_In_Free_Love_(1987_B-Side.mp3
-    B00921KJVI_(disc_2)_02_-_Barcelona_(Early_Version__Freddie's.mp3
-    B00921KK5I_(disc_2)_03_-_La_Japonaise_(Early_Version__Freddi.mp3
-    B00921KKHQ_(disc_2)_04_-_Rachmaninov's_Revenge_(The_Fallen_P.mp3
-    B00921KKSA_(disc_2)_05_-_Ensueo_(Monsterrat's_Live_Takes).mp3
-    B00921KL2U_(disc_2)_06_-_The_Golden_Boy_(Early_Version__Fred.mp3
-    B00921KLBQ_(disc_2)_07_-_Guide_Me_Home_(Alternative_Version).mp3
-    B00921KLJI_(disc_2)_08_-_How_Can_I_Go_On_(Alternative_Versio.mp3
-    B00921KLUC_(disc_2)_09_-_How_Can_I_Go_On_(Alternative_Piano_.mp3
-    B00921KM3I_(disc_3)_01_-_Barcelona_(Orchestral_Version).mp3
-    B00921KMBU_(disc_3)_02_-_La_Japonaise_(Orchestral_Version).mp3
-    B00921KMM4_(disc_3)_03_-_The_Fallen_Priest_(Orchestral_Versi.mp3
-    B00921KMYW_(disc_3)_04_-_Ensueo_(Orchestral_Version).mp3
-    B00921KNAK_(disc_3)_05_-_The_Golden_Boy_(Orchestral_Version).mp3
-    B00921KNUA_(disc_3)_06_-_Guide_Me_Home_(Orchestral_Version).mp3
-    B00921KOVI_(disc_3)_07_-_How_Can_I_Go_On_(Orchestral_Version.mp3
-    B00921KPP8_(disc_3)_08_-_Exercises_In_Free_Love_(Orchestral_.mp3
-    B00921KQJ8_(disc_3)_09_-_Overture_Piccante_(Orchestral_Versi.mp3
-    rcury/Barcelona_\[+video]/B00921K                                                                <
-    ls: Freddie_Mercury/Barcelona_[+video]/B00921K: No such file or directory
-    1|u0_a84@android:/sdcard/annex $
-    1|u0_a84@android:/sdcard/annex $
-    1|u0_a84@android:/sdcard/annex $
-    1|u0_a84@android:/sdcard/annex $
-    1|u0_a84@android:/sdcard/annex $
-    1|u0_a84@android:/sdcard/annex $ fg
-    git annex webapp
-    bg
-    ^Z[1] + Stopped              git annex webapp
-    u0_a84@android:/sdcard/annex $ bg
-    [1] git annex webapp
-    u0_a84@android:/sdcard/annex $ ls
-    Freddie_Mercury  ma??nequin
-    u0_a84@android:/sdcard/annex $ git annex add manequin
-    Freddie_Mercury/   manequin
-    u0_a84@android:/sdcard/annex $ git annex add manequin
-    add manequin (checksum...) ok
-    (Recording state in git...)
-    u0_a84@android:/sdcard/annex $ git annex sync
-    commit
-    ok
-    pull markdown.lang.speechmarks.com_phoneannex
-    remote: Counting objects: 12, done.
-    remote: Compressing objects: 100% (6/6), done.
-    remote: Total 8 (delta 4), reused 0 (delta 0)
-    Unpacking objects: 100% (8/8), done.
-    From ssh://git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex/~/phone-annex
-       c709e47..d2678a5  synced/git-annex -> markdown.lang.speechmarks.com_phoneannex/synced/git-annex
-    ok
-    (merging markdown.lang.speechmarks.com_phoneannex/synced/git-annex into git-annex...)
-    (Recording state in git...)
-    (Recording state in git...)
-    push markdown.lang.speechmarks.com_phoneannex
-    warning: no threads support, ignoring --threads
-    Counting objects: 15, done.
-    Compressing objects: 100% (11/11), done.
-    Writing objects: 100% (12/12), 1.19 KiB, done.
-    Total 12 (delta 4), reused 0 (delta 0)
-    To ssh://fozz@git-annex-markdown.lang.speechmarks.com-fozz_phone.2Dannex/~/phone-annex/
-       d2678a5..577fa92  git-annex -> synced/git-annex
-       c829a0a..2aa892f  master -> synced/master
-    ok
-    u0_a84@android:/sdcard/annex $
-
-I have no idea in this log why it is wrote \"manequin\" not \"mañnequin\" but this is what the command completion gave me ( I don't know how to type that letter ), but as you can see later it came over correctly later.
-
-Desktop:
-
-    fozz@cobol:~/phone-annex $ git annex sync
-    commit
-    # On branch master
-    nothing to commit, working directory clean
-    ok
-    pull origin
-    remote: Counting objects: 15, done.
-    remote: Compressing objects: 100% (11/11), done.
-    remote: Total 12 (delta 4), reused 0 (delta 0)
-    Unpacking objects: 100% (12/12), done.
-    From ssh://markdown.lang.speechmarks.com/home/fozz/phone-annex
-       c829a0a..2aa892f  master     -> origin/master
-       d2678a5..577fa92  synced/git-annex -> origin/synced/git-annex
-       c829a0a..2aa892f  synced/master -> origin/synced/master
-    
-    Updating c829a0a..2aa892f
-    Fast-forward
-     \"ma\303\261nequin\" | 1 +
-     1 file changed, 1 insertion(+)
-     create mode 120000 \"ma\303\261nequin\"
-    
-    Already up-to-date.
-    ok
-    (merging origin/synced/git-annex into git-annex...)
-    push origin
-    Everything up-to-date
-    ok
-
-I have since gone through and replicated this with \"mañnequin.txt\" from scratch with a completely empty repository and it did an identical thing again. I then added a backup of my KeePass.kdb database and it went over fine. So it seems that git-annex has no problem with the \"ñ\" file now, but the assistant does not see it at all.
-
-I have left the repository on my phone / desktop / server in this state so if you want further output please let me know.
-"""]]
diff --git a/doc/bugs/utf8/comment_1_416ad6fb5f7379732129dc5283a7e550._comment b/doc/bugs/utf8/comment_1_416ad6fb5f7379732129dc5283a7e550._comment
deleted file mode 100644
index 0df4c2aa5..000000000
--- a/doc/bugs/utf8/comment_1_416ad6fb5f7379732129dc5283a7e550._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="Renaming files"
- date="2013-07-21T10:08:16Z"
- content="""
-Renaming the files does not fix it, Git annex on all computers knows that those files are only in my phone, but the assistant is refusing to transfer the contents, it does not seem to know that it needs to...
-
-    whereis Freddie_Mercury/Barcelona_[+video]/B00921KMM4_(disc_3)_03_-_The_Fallen_Priest_(Orchestral_Versi.mp3 (3 copies) 
-      	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-       	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-       	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-    ok
-    whereis Freddie_Mercury/Barcelona_[+video]/B00921KMYW_(disc_3)_04_-_Ensueno_(Orchestral_Version).mp3 (1 copy) 
-      	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-    ok
-    whereis Freddie_Mercury/Barcelona_[+video]/B00921KNAK_(disc_3)_05_-_The_Golden_Boy_(Orchestral_Version).mp3 (3 copies) 
-      	1f368162-f02f-4794-af0c-1b5489e099b3 -- u0_a84@localhost:/sdcard/annex
-       	53f03d06-f1e3-11e2-8519-1b41c09abecd -- here (Cobol: Phone)
-       	cb6240e0-f1df-11e2-836a-7f4323e50c49 -- origin (Markdown: Phone)
-    ok
-
-"""]]
diff --git a/doc/bugs/utf8/comment_2_cd55f6bbeb145fd554f331dcff64f5e1._comment b/doc/bugs/utf8/comment_2_cd55f6bbeb145fd554f331dcff64f5e1._comment
deleted file mode 100644
index ff2a5363d..000000000
--- a/doc/bugs/utf8/comment_2_cd55f6bbeb145fd554f331dcff64f5e1._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="git annex copy --to won't get them across either..."
- date="2013-07-21T10:12:03Z"
- content="""
-git annex copy . --to markdown.DOMAIN_phoneannex responds with
-
-    ControlPath \"/data/data/ga.androidterm/tmp/fozz@...somethingthatlookslikeahash\" too long for Unix domain socket
-"""]]
diff --git a/doc/bugs/utf8/comment_3_bb583a419d6fa4e33e5364c4468b35c6._comment b/doc/bugs/utf8/comment_3_bb583a419d6fa4e33e5364c4468b35c6._comment
deleted file mode 100644
index ecdee070c..000000000
--- a/doc/bugs/utf8/comment_3_bb583a419d6fa4e33e5364c4468b35c6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="seems to not involve utf8 at all.."
- date="2013-07-21T18:17:00Z"
- content="""
-Can you please show me the actual filename, that you obfuscated as \"/data/data/ga.androidterm/tmp/fozz@...somethingthatlookslikeahash\" ?
-"""]]
diff --git a/doc/bugs/utf8/comment_4_cd8a22cfb70d9d21f0a5339ccc52ee93._comment b/doc/bugs/utf8/comment_4_cd8a22cfb70d9d21f0a5339ccc52ee93._comment
deleted file mode 100644
index 12bf4c5a6..000000000
--- a/doc/bugs/utf8/comment_4_cd8a22cfb70d9d21f0a5339ccc52ee93._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="GLITTAH"
- ip="37.130.227.133"
- subject="comment 4"
- date="2013-07-21T19:36:16Z"
- content="""
-This sounds like a bug I ran into a while ago that got fixed.
-
->What version of git-annex are you using? On what operating system?
->
->Phone: 4.20130709-g339d1eo Transfer Server: 3.20120406 (which it did not get to) Desktop: 3.20120629
-
-Maybe try upgrading your server and desktop versions?  Those look old enough to still have the utf-8 bug.
-"""]]
diff --git a/doc/bugs/utf8/comment_5_14eefd4bee283802e9c462fa20b7835c._comment b/doc/bugs/utf8/comment_5_14eefd4bee283802e9c462fa20b7835c._comment
deleted file mode 100644
index 22ec33481..000000000
--- a/doc/bugs/utf8/comment_5_14eefd4bee283802e9c462fa20b7835c._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="Darn it..."
- date="2013-07-21T20:29:33Z"
- content="""
-Hi,
-
-Sorry, it was on my phone and very long and I didn't think it'd be important... Sheesh Users eh!
-
-I think the error happened for every file or at least lots, not just the one with the strange tilde above the \"n\".
-Eventually, it might have been after a phone reboot, it sorted itself and continued.
-
-I can try and recreate it if it'll help, though it won't be till Wednesday / Thursday as I'm going away for a few days and I still need to pack.
-
-Sorry for the bad bug report, I know how annoying they are.
-
-It's not so easy for me to upgrade because one's an Ubuntu LTS and one is a Mint Debian Edition, both are the repository versions.
-"""]]
diff --git a/doc/bugs/utf8/comment_6_58d8b5bdb9f11e8c344e86a675a075dd._comment b/doc/bugs/utf8/comment_6_58d8b5bdb9f11e8c344e86a675a075dd._comment
deleted file mode 100644
index bb97d0fa4..000000000
--- a/doc/bugs/utf8/comment_6_58d8b5bdb9f11e8c344e86a675a075dd._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmkBwMWvNKZZCge_YqobCSILPMeK6xbFw8"
- nickname="develop"
- subject="comment 6"
- date="2013-07-21T20:31:50Z"
- content="""
-As much i myself personally would hate it. You really should go with the standalone builds provided on this site then.
-
-Just download the zip, extract on both machines. Make sure the PATH is correct, and it should Just Work(TM)
-
-"""]]
diff --git a/doc/bugs/utf8/comment_7_00fa9672ce55b6bfa885b8a13287ac25._comment b/doc/bugs/utf8/comment_7_00fa9672ce55b6bfa885b8a13287ac25._comment
deleted file mode 100644
index 925067989..000000000
--- a/doc/bugs/utf8/comment_7_00fa9672ce55b6bfa885b8a13287ac25._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.1.10"
- subject="comment 7"
- date="2013-07-22T18:34:55Z"
- content="""
-The only version of git-annex that matters is the one installed on the Android device. Which is fine.
-
-I reiterate my request for the actual thing that got obfuscated as \"/data/data/ga.androidterm/tmp/fozz@...somethingthatlookslikeahash\". Once I have that peice of information I should be able to fix this bug in short order. I understand exactly what's going on, except I don't know what the actual length of the filename that is causing the problem is.
-"""]]
diff --git a/doc/bugs/utf8/comment_8_a01e26fa0fafbc291020f53dbfdf6443._comment b/doc/bugs/utf8/comment_8_a01e26fa0fafbc291020f53dbfdf6443._comment
deleted file mode 100644
index dfb3570b6..000000000
--- a/doc/bugs/utf8/comment_8_a01e26fa0fafbc291020f53dbfdf6443._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0"
- nickname="Matthew"
- subject="I will give recreating the bug a go in about 3 days time..."
- date="2013-07-22T19:26:44Z"
- content="""
-I will give recreating the bug a go in about 3 days time when I get back off holiday.
-
-Thanks
-"""]]
diff --git a/doc/bugs/utf8/comment_9_b7c084be01ce985be51e48503fcba468._comment b/doc/bugs/utf8/comment_9_b7c084be01ce985be51e48503fcba468._comment
deleted file mode 100644
index f2c42a6bd..000000000
--- a/doc/bugs/utf8/comment_9_b7c084be01ce985be51e48503fcba468._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.246.110"
- subject="comment 9"
- date="2013-07-26T21:09:36Z"
- content="""
-Any luck reproducing this bug and getting the info I need to know exactly what's going on?
-"""]]
diff --git a/doc/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.mdwn b/doc/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.mdwn
deleted file mode 100644
index a84d8cb56..000000000
--- a/doc/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-Since uuid.log, trust.log and remote.log are union merged, it's possible
-for any given item in them to have multiple values after a merge.
-This would happen, for example, if the value was changed in different ways
-in two repos which were then merged. git-annex will use an arbitrary
-one of the multiple values.
-
-A workaround if this should happen to you is to use `git annex describe`
-or other commands to re-set the value you want. The process of setting
-the value will remove the multiple lines.
-
-To fix this the file format needs to be changed to include a timestamp
-as is done with the other log files, then git-annex can consistently
-pick the newest value -- which is as close to the "right" value as can be
-determined in this situation.
-
-----
-
-File format backwards-compatability is the issue. Ideally, old git-annex
-would keep working, ignoring the timestamp.
-
-- uuid.log: "uuid description timestamp" would work; old git-annex 
-  would just treat the timestamp as part of the description which would be
-  ok
-  > update: converted! --[[Joey]] 
-- trust.log: "uuid trustlevel timestamp" would work; old git-annex
-  ignores trailing words
-  > update: converted! --[[Joey]] 
-- remote.log: "uuid key=value ... timestamp" is on the edge but does work
-  (old git-annex will include the timestamp in the key/value map it builds,
-  but that should not break anything really)
-  > update: converted! --[[Joey]] 
-
-Appending "timestamp=xxxxx" would be good for clarity, and make
-it easier to parse the timestamp out from lines that have it.
-
-> [[done]] --[[Joey]] 
diff --git a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash.mdwn b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash.mdwn
deleted file mode 100644
index 9bc891100..000000000
--- a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-After (probably, doesn't hepl anymore) adding the same file into multiple clones and syncing them back, I get a couple of these `.variant-` files. The target of these symlinks is different, but the actual file contents of the real data is the same.
-
-[[!format txt """
-jkt@svist /mnt/storage5/fotky[master] $ ls -al 2011-02-05\ Svatba\ Maruška\ Pavel/jkt/cam1/IMG_8962*variant*
-lrwxrwxrwx 1 jkt jkt 335 Mar  3 02:08 2011-02-05 Svatba Maruška Pavel/jkt/cam1/IMG_8962.JPG.variant-847f.cam ->
-../../../.git/annex/objects/P4/F7/SHA512E-s5534099--bf29fad838adb755b98351477e9a57c456b66ca393652f3b5df2093fc5448b3eeb0235420a715bfb84fb0cccfbbcea4514d4558467b64a39dc7daaf43c045672.cam/SHA512E-s5534099--bf29fad838adb755b98351477e9a57c456b66ca393652f3b5df2093fc5448b3eeb0235420a715bfb84fb0cccfbbcea4514d4558467b64a39dc7daaf43c045672.cam
-lrwxrwxrwx 1 jkt jkt 343 Mar  3 02:08 2011-02-05 Svatba Maruška Pavel/jkt/cam1/IMG_8962.JPG.variant-c8d0.cam ->
-../../../.git/annex/objects/38/pG/SHA512E-s5534099--bf29fad838adb755b98351477e9a57c456b66ca393652f3b5df2093fc5448b3eeb0235420a715bfb84fb0cccfbbcea4514d4558467b64a39dc7daaf43c045672.JPG.cam/SHA512E-s5534099--bf29fad838adb755b98351477e9a57c456b66ca393652f3b5df2093fc5448b3eeb0235420a715bfb84fb0cccfbbcea4514d4558467b64a39dc7daaf43c045672.JPG.cam
-"""]]
-
-I don't know what determines the `P4/F7/` vs `38/pG/` directory names, but I would prefer if these duplicates were not created.
-
-> I guess I'm going to close this as not a bug. [[done]] --[[Joey]] 
diff --git a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_1_ffc5f79368b8927817e0e35a7a8f057b._comment b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_1_ffc5f79368b8927817e0e35a7a8f057b._comment
deleted file mode 100644
index 3d3531fce..000000000
--- a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_1_ffc5f79368b8927817e0e35a7a8f057b._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.146"
- subject="comment 1"
- date="2014-03-03T21:58:20Z"
- content="""
-You have 2 different keys, so get variant files. This is expected behavior.
-
-You're right that the 2 files have the same content. But two different keys were generated for them when they were added in their respective repositories. This can happen when you use the SHA512E (or SHA256E) backend, because it uses the extension as part of the key. One of the files you added had an extension of \".cam\", and the other \".JPG.cam\"
-
-If there is any bug here, it's perhaps that the \"E\" backends are smart about multi-component file extensions, so will treat eg .tar.gz as an extension, rather than just .gz. If this was not done, both files would have had a .cam extension, and the conflict would not have occurred. But while being less smart would have avoided it in this case, it won't in other cases where files can have different extensions but the same content (for example, \".jpeg\" vs \".jpg\").
-"""]]
diff --git a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_2_1382b486d198d707db760ae119f33ad1._comment b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_2_1382b486d198d707db760ae119f33ad1._comment
deleted file mode 100644
index 1ee533347..000000000
--- a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_2_1382b486d198d707db760ae119f33ad1._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlmOvQXLmGkQAUOIkPBQtsd9d45NqcX80M"
- nickname="Jan"
- subject="comment 2"
- date="2014-03-04T11:01:12Z"
- content="""
-I indeed use the SHA512E backend, but the files got the same name -- `IMG_8962.JPG.cam`.
-"""]]
diff --git a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_3_3c4074a1d4d7f63f6c07a05ca9717ce8._comment b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_3_3c4074a1d4d7f63f6c07a05ca9717ce8._comment
deleted file mode 100644
index 0f20d9164..000000000
--- a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_3_3c4074a1d4d7f63f6c07a05ca9717ce8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.146"
- subject="comment 3"
- date="2014-03-05T16:56:14Z"
- content="""
-Older versions of git-annex did not preserve more than the very end of the extension when using SHA*E backends, so I guess you added the respective files using two different versions.
-"""]]
diff --git a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_4_deb848e50f6767d8a5f4348137744ec2._comment b/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_4_deb848e50f6767d8a5f4348137744ec2._comment
deleted file mode 100644
index e53e5c2dd..000000000
--- a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_4_deb848e50f6767d8a5f4348137744ec2._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlmOvQXLmGkQAUOIkPBQtsd9d45NqcX80M"
- nickname="Jan"
- subject="comment 4"
- date="2014-03-05T17:07:05Z"
- content="""
-Ah, so it's a matter of `.JPG.cam` vs `.cam` as an extension -- that makes sense, I do use different versions on these two remotes. Is there some easy way of getting them back to a single underlying content apart from doing that by hand?
-"""]]
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
deleted file mode 100644
index c50d75476..000000000
--- a/doc/bugs/variant-_files_are_created_even_though_the_content_has_the_same_hash/comment_5_b426c4569b7a788fbf963f787590e051._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!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.
-"""]]
diff --git a/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working.mdwn b/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working.mdwn
deleted file mode 100644
index 64e83526f..000000000
--- a/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-### Please describe the problem.
-on [[tips/downloading_podcasts/]] it says to look for "Feeds" in the output of version to see if you have the importfeeds support. I have importfeeds support but "Feeds" is not listed when doing version.
-
-### What steps will reproduce the problem?
-# git-annex version
-# git-annex importfeed <someurl>
-
-### What version of git-annex are you using? On what operating system?
-4.20130802 on Debian unstable
-
-### Please provide any additional information below.
-
-[[!format sh """
-greg@x200s:~/annextest$ git-annex version
-git-annex version: 4.20130802
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 4
-upgrade supported from repository versions: 0 1 2
-
-greg@x200s:~/annextest$ git-annex importfeed http://feeds.feedburner.com/OpenMetalcast/ogg
-(checking known urls...)
-importfeed http://feeds.feedburner.com/OpenMetalcast/ogg 
-....<downloads the episodes etc>
-"""]]
-
-> Forgot I had to manually add that. [[done]] (really this time!) --[[Joey]]
diff --git a/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working/comment_1_ce06ba4f65f322362b23797f6190c7c3._comment b/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working/comment_1_ce06ba4f65f322362b23797f6190c7c3._comment
deleted file mode 100644
index 8b156f822..000000000
--- a/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working/comment_1_ce06ba4f65f322362b23797f6190c7c3._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="http://a-or-b.myopenid.com/"
- ip="203.45.2.230"
- subject="comment 1"
- date="2013-09-04T01:36:46Z"
- content="""
-This still is not fixed.  :-(
-
-    $ git annex version
-    git-annex version: 4.20130827
-    build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS
-
-
-...but the ```importfeed``` functionality works.
-
-I know this isn't a particularly high priority bug...
-"""]]
diff --git a/doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex.mdwn b/doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex.mdwn
deleted file mode 100644
index 0b9c54039..000000000
--- a/doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-### Please describe the problem.
-I tried to setup a fresh local repository and got an error:
-> Internal Server Error
-> user error (git ["--git-dir=/home/jana/Bilder/Fotos/.git","--work-tree=/home/jana/Bilder/Fotos","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] exited 128)
-
-When clicking on "View logs", I get the following error:
-
-> Internal Server Error
-> internal liftAnnex
-
-### What steps will reproduce the problem?
-1. Run git-annex from programs menu
-2. Click "Make repository"
-
-### What version of git-annex are you using? On what operating system?
-- git-annex 4.20130627 on Ubuntu 13.10, installed from debian unstable (sid) repository.
-- git version 1.8.1.2
-
-> I've made it detect systems that lack a FQDN and set user.email
-> automatically. [[done]] --[[Joey]] 
diff --git a/doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex/comment_1_57547f9a480df2c3f7b3997b0fb7039a._comment b/doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex/comment_1_57547f9a480df2c3f7b3997b0fb7039a._comment
deleted file mode 100644
index 44807b62f..000000000
--- a/doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex/comment_1_57547f9a480df2c3f7b3997b0fb7039a._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://cweiske.de/"
- nickname="cweiske"
- subject="comment 1"
- date="2013-07-04T20:20:15Z"
- content="""
-Running git-annex from the command line shows me:
-
-> fatal: unable to auto-detect email address (got 'jana@sybo.(none)')
-
-Setting user.email and user.name fixed the error.
-"""]]
diff --git a/doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex/comment_2_99f12da3ef01141dc7a9105fcf966793._comment b/doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex/comment_2_99f12da3ef01141dc7a9105fcf966793._comment
deleted file mode 100644
index 61a725060..000000000
--- a/doc/bugs/view_logs_fails:_Internal_Server_Error__internal_liftAnnex/comment_2_99f12da3ef01141dc7a9105fcf966793._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 2"
- date="2013-07-05T15:30:37Z"
- content="""
-Ok, the liftAnnex part of this is just because most of the webapp, including viewing logs, requires a repo to be set up, and it's not gotten past the early setup part where this happens before it, apparently, crashed because of the email misconfiguration problem.
-
-So, I should really detect and deal with this rather annoyingly common misconfiguration of user's computers..
-"""]]
diff --git a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android.mdwn b/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android.mdwn
deleted file mode 100644
index afdf6b270..000000000
--- a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-### Please describe the problem.
-The first time I open the webapp on Android I see the following warning :
-
-`WebApp crashed:<file descriptor 15>: hPutStr: illegal operation(handle_is_closed)`
-
-See screen capture : [http://i.imgur.com/K0wkk2n.png](http://i.imgur.com/K0wkk2n.png)
-
-### What steps will reproduce the problem?
-1. Close git-annex if running
-2. Open the WebApp
-
-### What version of git-annex are you using? On what operating system?
-It says 1.0.52 in the Android settings but I'm using the daily build that I downloaded around 2013-05-29 13:10:00 (Eastern Time)
-
-### Please provide any additional information below.
-
-Git annex still syncs with `box.com` even if the warning is showing.
-
-I'm using a Nexus 4 (4.2.2)
-
-I didn't find `daemon.log`.
-
-> [[done]]; the android app no longer uses `am`, so no longer needs to 
-> display a message when `am` fails. --[[Joey]]
diff --git a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_1_e8866dc15f8fc049229e7451addad1d5._comment b/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_1_e8866dc15f8fc049229e7451addad1d5._comment
deleted file mode 100644
index 3aaa01e06..000000000
--- a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_1_e8866dc15f8fc049229e7451addad1d5._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-30T15:57:41Z"
- content="""
-This is an intriguing screenshot, since it shows the webapp reporting a crash of the webapp! I think what's going on is that the web server thread run by the webapp is still running, although the webapp's own thread has crashed.
-
-The log should be in `/sdcard/DCIM/.git/annex/daemon.log`. I would be interested to see it.
-
-Does the webapp continue to update and function despite saying it crashed?
-"""]]
diff --git a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_2_ee616b0251ffaace9844cfd7af896c35._comment b/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_2_ee616b0251ffaace9844cfd7af896c35._comment
deleted file mode 100644
index b19fbf584..000000000
--- a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_2_ee616b0251ffaace9844cfd7af896c35._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-05-30T16:07:59Z"
- content="""
-Could you please get me a screenshot of git-annex's terminal window after this has occurred? 
-
-The most likely thing seems to be that it's crashing while trying to open the web browser. How did you get the web browser open on the webapp? Using the new menu item to do it, or did it automatically open?
-"""]]
diff --git a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_3_6b8bd314b647ea3a485f5faf4856f9a9._comment b/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_3_6b8bd314b647ea3a485f5faf4856f9a9._comment
deleted file mode 100644
index 88a99684a..000000000
--- a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_3_6b8bd314b647ea3a485f5faf4856f9a9._comment
+++ /dev/null
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkGCmVc5qIJaQQgG82Hc5zzBdAVdhe2JEM"
- nickname="Bruno"
- subject="comment 3"
- date="2013-05-30T16:30:31Z"
- content="""
-Here's the screen capture : [http://i.imgur.com/owmuIKa.png](http://i.imgur.com/owmuIKa.png)
-
-I used the menu item to open the WebApp. Nothing appeared in the git-annex's terminal window when I opened the WebApp. The error message is the one that appears when I start Git Annex.
-
-The WebApp seems to be working. It synced a picture I took when the WebApp was already running. See : [http://i.imgur.com/Bcu4iAE.png](http://i.imgur.com/Bcu4iAE.png)
-
-I think I have this bug since the Android version is out. I thought maybe it was normal in the beginning.
-
-Here's the log :
-
-    [2013-05-30 12:15:36 EDT] main: starting assistant version 4.20130529-g6b9b452
-    \"_xmpp-client._tcp.gmail.com\"
-    Just [(5,0,5222,\"xmpp.l.google.com.\"),(20,0,5222,\"alt1.xmpp.l.google.com.\"),(20,0,5222,\"alt3.xmpp.l.google.com.\"),(20,0,5222,\"alt4.xmpp.l.google.com.\"),(20,0,5222,\"alt2.xmpp.l.google.com.\")]
-    (scanning...) [2013-05-30 12:15:37 EDT] Watcher: Performing startup scan
-    WebApp crashed: <file descriptor: 15>: hPutStr: illegal operation (handle is closed)
-    [2013-05-30 12:15:37 EDT] WebApp: warning WebApp crashed: <file descriptor: 15>: hPutStr: illegal operation (handle is closed)
-    (started...) [2013-05-30 12:22:02 EDT] Committer: Adding IMG_20130..22201.jpg
-
-    add Camera/IMG_20130530_122201.jpg (checksum...) [2013-05-30 12:22:02 EDT] Committer: Committing changes to git
-    [2013-05-30 12:22:13 EDT] Committer: Adding IMG_20130..22201.jpg
-    ok
-    (Recording state in git...)
-    (Recording state in git...)
-    add Camera/IMG_20130530_122201.jpg (checksum...) [2013-05-30 12:22:14 EDT] Committer: Committing changes to git
-    (gpg) 
-    [...]
-                            
-    [2013-05-30 12:22:50 EDT] Transferrer: Uploaded IMG_20130..22201.jpg
-"""]]
diff --git a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_4_7009b6727ba40bc9bd1b1f939e75d093._comment b/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_4_7009b6727ba40bc9bd1b1f939e75d093._comment
deleted file mode 100644
index eba3baedc..000000000
--- a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_4_7009b6727ba40bc9bd1b1f939e75d093._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 4"
- date="2013-05-30T19:18:50Z"
- content="""
-Seems it's crashing while trying to print out a message telling you to use the menu to open the webapp. I'm not sure why, but I have updated the android autobuild to try to work around this. If you can test and tell me if that fixes it or not, it'll help me tell what's going on.
-"""]]
diff --git a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_5_00ddf7ade6cca758afa838be0b9588cb._comment b/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_5_00ddf7ade6cca758afa838be0b9588cb._comment
deleted file mode 100644
index 04de2d3de..000000000
--- a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_5_00ddf7ade6cca758afa838be0b9588cb._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkGCmVc5qIJaQQgG82Hc5zzBdAVdhe2JEM"
- nickname="Bruno"
- subject="comment 5"
- date="2013-05-30T19:38:59Z"
- content="""
-I still have the problem :(
-
-    [2013-05-30 15:36:31 EDT] main: starting assistant version 4.20130530-g2e0f464
-    Already up-to-date.
-    WebApp crashed: <file descriptor: 14>: hPutStr: illegal operation (handle is closed)
-    [2013-05-30 15:36:32 EDT] WebApp: warning WebApp crashed: <file descriptor: 14>: hPutStr: illegal operation (handle is closed)
-
-    (scanning...) [2013-05-30 15:36:32 EDT] Watcher: Performing startup scan
-    Already up-to-date.
-    [2013-05-30 15:36:35 EDT] Committer: Committing changes to git
-
-    (Recording state in git...)
-    (started...) [2013-05-30 15:36:44 EDT] Committer: Committing changes to git
-"""]]
diff --git a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_6_6137ef0ad01d5600dab6fccbeed9a88b._comment b/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_6_6137ef0ad01d5600dab6fccbeed9a88b._comment
deleted file mode 100644
index 79606cb09..000000000
--- a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_6_6137ef0ad01d5600dab6fccbeed9a88b._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 6"
- date="2013-05-30T19:45:30Z"
- content="""
-Changed to fd 14 and not 15, so my change to use the dupped stdout did take effect.
-
-Interesting. Either dup() is just failing (silently!), or the `am` command is somehow closing the assistant's fds (not sure if that's possible).
-
-In either case, it's only happening on your device, not on mine.
-
-I suppose this will just need to wait until I sort out better the opening of the webapp on android. The \"crash\" does not seem like it will affect the actual functioning of the webapp.
-"""]]
diff --git a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_7_4b79d7ea338d9f70eb80b8cc2c5a21e4._comment b/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_7_4b79d7ea338d9f70eb80b8cc2c5a21e4._comment
deleted file mode 100644
index 03fe1cf8b..000000000
--- a/doc/bugs/warning_-_WebApp_crashed:___60__file_descriptor_15__62__:_hPutStr:_illegal_operation___40__handle_is_closed__41___on_Android/comment_7_4b79d7ea338d9f70eb80b8cc2c5a21e4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 7"
- date="2013-05-30T19:48:14Z"
- content="""
-Actually, the dupped stdout is open and working before `am` is run, so `am` must somehow be messing with it. Can't be a dupping problem. Need to stop using this `am` nonsense clearly.
-"""]]
diff --git a/doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo.mdwn b/doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo.mdwn
deleted file mode 100644
index c598bb4d7..000000000
--- a/doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-I had started a fresh repo to test out the watch command again on OSX and noticed that it's borked, I'm not sure when it was broken.
-
-The snippet of the log message and command is
-
-<pre>
-$ git annex watch --foreground -d -v
-watch . read: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","show-ref","git-annex"] 
-read: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","show-ref","--hash","refs/heads/git-annex"] 
-read: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","log","refs/heads/git-annex..6702e5361146450800ae5af0b63e97bd9c55d70b","--oneline","-n1"] 
-chat: git ["--git-dir=/Users/jtang/sandbox/atest/.git","--work-tree=/Users/jtang/sandbox/atest","cat-file","--batch"] 
-(scanning...) call: git ["--git-dir=/Users/jtan
-</pre>
-
-I had run git-annex with a new repo with just doing a git init and git annex init, I just threw in one or two small text files to see if it was working. It just hangs and does nothing. I had also tried it out on one of my bigger repos and it does the same thing it just hangs at _(scanning...)_ There isn't much to go on, I wonder if it's hitting the [[Issue on OSX with some system limits]] or if its just a thread/fork issue on OSX.
-
-It still hangs on the small repo even if I do
-
-    $ sudo sysctl -w kern.maxfilesperproc=400000
-    $ ulimit -n 2000
-
-Also, just in case if you need it still (on a clean OSX 10.7 system)
-
-<pre>
-$ ulimit -a
-core file size          (blocks, -c) 0
-data seg size           (kbytes, -d) unlimited
-file size               (blocks, -f) unlimited
-max locked memory       (kbytes, -l) unlimited
-max memory size         (kbytes, -m) unlimited
-open files                      (-n) 256
-pipe size            (512 bytes, -p) 1
-stack size              (kbytes, -s) 8192
-cpu time               (seconds, -t) unlimited
-max user processes              (-u) 709
-virtual memory          (kbytes, -v) unlimited
-</pre>
-
-Please close or merge this report if it's a duplicate.
-
-> I've fixed this, it works in my (so far limited) tests. [[done]]
-> --[[Joey]] 
diff --git a/doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo/comment_1_63f04694610839db0c2381005b15da35._comment b/doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo/comment_1_63f04694610839db0c2381005b15da35._comment
deleted file mode 100644
index 1b9fe9a4a..000000000
--- a/doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo/comment_1_63f04694610839db0c2381005b15da35._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="98.65.205.24"
- subject="comment 1"
- date="2012-07-20T18:17:04Z"
- content="""
-I see this too, on OSX, and it's another one of the hangs with the threaded runtime I've been battling recently. Removing -threaded from the Makefile or git-annex.cabal (whichever you're using) makes it work.
-
-Seems likely this one is specific to my kqueue code. Indeed, I see it entering the kqueue code and then hanging, when it should be noticing changes. Interestingly, all threads seem to get blocked, too.
-
-AHA! I had the FFI functions marked unsafe. Marking safe seems to fix that. I need to go re-read up on the FFI and when it's safe to mark functions threadsafe.
-
-Thanks as always for the OSX eyes Jimmy!
-"""]]
diff --git a/doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo/comment_2_8afe4720e301cf7ccf11ff0a23261936._comment b/doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo/comment_2_8afe4720e301cf7ccf11ff0a23261936._comment
deleted file mode 100644
index 1c97338f1..000000000
--- a/doc/bugs/watch_command_on_OSX_--_hangs_with_a_small_repo/comment_2_8afe4720e301cf7ccf11ff0a23261936._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 2"
- date="2012-07-20T19:31:11Z"
- content="""
-Glad that I can help ;) Alas if it weren't for the learning curve of haskell, I'd fix it myself.
-"""]]
diff --git a/doc/bugs/watch_command_on_OSX_10.7.mdwn b/doc/bugs/watch_command_on_OSX_10.7.mdwn
deleted file mode 100644
index 1348c1155..000000000
--- a/doc/bugs/watch_command_on_OSX_10.7.mdwn
+++ /dev/null
@@ -1,37 +0,0 @@
-Running the tip of the watch branch on OSX in an annex'ed directory.
-
-The watch command detects the changes, does _something_, see the output below.
-
-Output from watch command
-
-<pre>
-(Recording state in git...)
-Added "./KeePass2.18.dmg"
-Added "./KeePassX-0.4.3.dmg"
-add ./KeePass2.18.dmg (checksum...) ok
-add ./KeePassX-0.4.3.dmg (checksum...) ok
-</pre>
-
-State of the annex
-
-<pre>
-laplace:annex jtang$ git status
-# On branch master
-# Untracked files:
-#   (use "git add <file>..." to include in what will be committed)
-#
-#	KeePass2.18.dmg
-#	KeePassX-0.4.3.dmg
-nothing added to commit but untracked files present (use "git add" to track)
-</pre>
-
-It seems to not do a git add and commit after the creation of the symlinks, manually doing this makes it all happy again till more files are added.
-
-note: i had posted a comment in the blog post, but posting the issue here is probably more appropriate.
-
-> Yeah, this is the issue I was struggling with last night. 
-> I think it's fixed in 57cf65eb6d811ba7fd19eb62a54e3b83a0c2dfa7,
-> but the kqueue watch still needs a lot of work. --[[Joey]]
-
->> Confirmed this is fixed, but do note the known kqueue bugs in 
->> [[design/assistant/inotify]]! [[done]] --[[Joey]]
diff --git a/doc/bugs/watcher_commits_unlocked_files.mdwn b/doc/bugs/watcher_commits_unlocked_files.mdwn
deleted file mode 100644
index 37e50fca0..000000000
--- a/doc/bugs/watcher_commits_unlocked_files.mdwn
+++ /dev/null
@@ -1,37 +0,0 @@
-When having "git annex watch" running, unlocking files causes the watcher
-to immediately lock/commit them.
-
-----
-
-Possible approaches:
-
-* The watcher could detect unlocked files by checking if newly added files
-  are a typechange of a file already in git. But this would add git overhead
-  to every file add.
-* `git annex unlock` could add some type of flag file, which the assistant
-  could check. This would work fine, for users who want to use `git annex
-  unlock` with the assistant. That's probably not simple enough for most
-  users, though.
-* There could be a UI in the assistant to pick a file and unlock it.
-  The assistant would have its own list of files it knows are unlocked.
-  But I'm trying to avoid mandatory UI to use the assistant.
-* Perhaps instead, have a directory, like "edit". The assistant could notice
-  when files move into this special directory, and automatically unlock them.
-  Then when they're moved out, automatically commit them.
-* Alternatively, files that are moved out of the repository entirely could be
-  automatically unlocked, and then when they're moved back in, it would
-  automatically do the right thing. This may be worth implementing in
-  combination with the "edit" directory, as different use cases would work
-  better with one or the other. However, I don't currently get inotify
-  events when files are moved out of the repository (well, I do, but it
-  just says "file moved", with no forwarding address, so I don't know 
-  how to find the file to unlock it.
-
-[[!meta title="assistant: watcher_commits_unlocked_files"]]
-
-> [[done]]; I just tested and somehow this no longer happens;
-> the watcher/assistant leaves the unlocked file alone, and then
-> as soon as it's modified re-adds it.
-> 
-> Also, of course, there is direct mode, which avoids needing to unlock...
-> --[[Joey]]
diff --git a/doc/bugs/watcher_commits_unlocked_files/comment_1_f70e1912fde0eee59e208307df06b503._comment b/doc/bugs/watcher_commits_unlocked_files/comment_1_f70e1912fde0eee59e208307df06b503._comment
deleted file mode 100644
index a06b8fe82..000000000
--- a/doc/bugs/watcher_commits_unlocked_files/comment_1_f70e1912fde0eee59e208307df06b503._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 1"
- date="2012-06-28T13:39:18Z"
- content="""
-That is a known problem/bug which is listed at [[design/assistant/inotify]]
-"""]]
diff --git a/doc/bugs/webapp_hang.mdwn b/doc/bugs/webapp_hang.mdwn
deleted file mode 100644
index a1d296893..000000000
--- a/doc/bugs/webapp_hang.mdwn
+++ /dev/null
@@ -1,144 +0,0 @@
-Occasionally, clicking on a link in the webapp will hang. When this
-happens, which has only been seen in Chromium so far, the tab will spin
-forever, without anything loading. Other tabs can be opened with
-middle-click on links in the webapp, and work fine. Stopping and reloading
-in the tab tends to hang again, although eventually this will clear the
-hang up.
-
--------
-
-My best procedure to replicate this, about 25% of the time:
-
-* have 2 large files and a libreoffice spreadsheet
-* start webapp, make repository
-* open file browser using button in webapp
-* move files into repository
-* make media subdir; move media into it
-* open spreadsheet, modify, save
-* click on New Repository button for the hang
-
-Running recordmydesktop at the same time may also help.. Or giving a
-presentation in Australia. :/
-
--------
-
-Hypotheses:
-
-* Warp's slowloris protection could be triggering. Possibly by the
-  repeated hits to update the alerts? I added a settingsOnException handler
-  that logs all exceptions, and ThreadKilled is happening several times.
-  The only place in Warp that kills threads is due to a timeout installed
-  for that. 
-
-  **Verified** Bug filed upstream:  <https://github.com/yesodweb/wai/issues/146>
-
-  ** workaround in place **
-
-* Something deep in git-annex, such as the inotidy code, could be
-  preventing a web server thread from running. But then why do other
-  tabs and other web browsers work while it's stuck?
-  It would have to affect only 1 thread.
-
--------
-
-I captured a clean protocol dump of this happening. It includes only the
-final, hanging http request and subsequent traffic, not the setup.
-
-We can see the web browser send a request. The server ACKs it at the TCP
-level, but never sends any reply. The web browser continues sending TCP
-keep-alive packets, which are acked by the server. This continued as long
-as the browser tab was left open.
-
-Question: Did the browser send a complete & valid request? The last part
-sent is a cookie and "\r\n\r\n".. So it seems complete. Unless warp is
-expecting a request body?
-
-<pre>
-17:22:30.533079 IP localhost.localdomain.53239 > localhost.localdomain.45836: Flags [P.], seq 4237976899:4237977772, ack 2608808926, win 2048, options [nop,nop,TS val 4895706 ecr 4885760], length 873
-	0x0000:  4500 039d be84 4000 4006 7ad4 7f00 0001  E.....@.@.z.....
-	0x0010:  7f00 0001 cff7 b30c fc9a 6543 9b7f 43de  ..........eC..C.
-	0x0020:  8018 0800 0192 0000 0101 080a 004a b3da  .............J..
-	0x0030:  004a 8d00 4745 5420 2f63 6f6e 6669 672f  .J..GET./config/
-	0x0040:  7265 706f 7369 746f 7279 3f61 7574 683d  repository?auth=
-	0x0050:  6437 6266 3037 3438 6663 3863 3031 3965  d7bf0748fc8c019e
-	0x0060:  6230 3966 3530 3631 6164 6663 3861 3563  b09f5061adfc8a5c
-	0x0070:  3430 3437 3633 6562 3736 6630 6163 3533  404763eb76f0ac53
-	0x0080:  3663 3362 6230 3066 3835 6663 6361 3233  6c3bb00f85fcca23
-	0x0090:  6235 3639 3764 3332 3464 3737 3930 3063  b5697d324d77900c
-	0x00a0:  3739 3532 6430 6165 3235 3166 6331 6337  7952d0ae251fc1c7
-	0x00b0:  3532 3632 6330 3233 6265 3936 3066 3563  5262c023be960f5c
-	0x00c0:  3364 6135 6532 6262 6234 3639 3863 3035  3da5e2bbb4698c05
-	0x00d0:  2048 5454 502f 312e 310d 0a48 6f73 743a  .HTTP/1.1..Host:
-	0x00e0:  2031 3237 2e30 2e30 2e31 3a34 3538 3336  .127.0.0.1:45836
-	0x00f0:  0d0a 436f 6e6e 6563 7469 6f6e 3a20 6b65  ..Connection:.ke
-	0x0100:  6570 2d61 6c69 7665 0d0a 4163 6365 7074  ep-alive..Accept
-	0x0110:  3a20 7465 7874 2f68 746d 6c2c 6170 706c  :.text/html,appl
-	0x0120:  6963 6174 696f 6e2f 7868 746d 6c2b 786d  ication/xhtml+xm
-	0x0130:  6c2c 6170 706c 6963 6174 696f 6e2f 786d  l,application/xm
-	0x0140:  6c3b 713d 302e 392c 2a2f 2a3b 713d 302e  l;q=0.9,*/*;q=0.
-	0x0150:  380d 0a55 7365 722d 4167 656e 743a 204d  8..User-Agent:.M
-	0x0160:  6f7a 696c 6c61 2f35 2e30 2028 5831 313b  ozilla/5.0.(X11;
-	0x0170:  204c 696e 7578 2069 3638 3629 2041 7070  .Linux.i686).App
-	0x0180:  6c65 5765 624b 6974 2f35 3337 2e31 3720  leWebKit/537.17.
-	0x0190:  284b 4854 4d4c 2c20 6c69 6b65 2047 6563  (KHTML,.like.Gec
-	0x01a0:  6b6f 2920 4368 726f 6d65 2f32 342e 302e  ko).Chrome/24.0.
-	0x01b0:  3133 3132 2e36 3820 5361 6661 7269 2f35  1312.68.Safari/5
-	0x01c0:  3337 2e31 370d 0a52 6566 6572 6572 3a20  37.17..Referer:.
-	0x01d0:  6874 7470 3a2f 2f31 3237 2e30 2e30 2e31  http://127.0.0.1
-	0x01e0:  3a34 3538 3336 2f3f 6175 7468 3d64 3762  :45836/?auth=d7b
-	0x01f0:  6630 3734 3866 6338 6330 3139 6562 3039  f0748fc8c019eb09
-	0x0200:  6635 3036 3161 6466 6338 6135 6334 3034  f5061adfc8a5c404
-	0x0210:  3736 3365 6237 3666 3061 6335 3336 6333  763eb76f0ac536c3
-	0x0220:  6262 3030 6638 3566 6363 6132 3362 3536  bb00f85fcca23b56
-	0x0230:  3937 6433 3234 6437 3739 3030 6337 3935  97d324d77900c795
-	0x0240:  3264 3061 6532 3531 6663 3163 3735 3236  2d0ae251fc1c7526
-	0x0250:  3263 3032 3362 6539 3630 6635 6333 6461  2c023be960f5c3da
-	0x0260:  3565 3262 6262 3436 3938 6330 350d 0a41  5e2bbb4698c05..A
-	0x0270:  6363 6570 742d 456e 636f 6469 6e67 3a20  ccept-Encoding:.
-	0x0280:  677a 6970 2c64 6566 6c61 7465 2c73 6463  gzip,deflate,sdc
-	0x0290:  680d 0a41 6363 6570 742d 4c61 6e67 7561  h..Accept-Langua
-	0x02a0:  6765 3a20 656e 2d55 532c 656e 3b71 3d30  ge:.en-US,en;q=0
-	0x02b0:  2e38 0d0a 4163 6365 7074 2d43 6861 7273  .8..Accept-Chars
-	0x02c0:  6574 3a20 4953 4f2d 3838 3539 2d31 2c75  et:.ISO-8859-1,u
-	0x02d0:  7466 2d38 3b71 3d30 2e37 2c2a 3b71 3d30  tf-8;q=0.7,*;q=0
-	0x02e0:  2e33 0d0a 436f 6f6b 6965 3a20 5f53 4553  .3..Cookie:._SES
-	0x02f0:  5349 4f4e 3d45 3363 7455 496c 7341 5451  SION=E3ctUIlsATQ
-	0x0300:  3631 694c 6d54 6954 7131 6f37 6465 7830  61iLmTiTq1o7dex0
-	0x0310:  3361 6f57 3049 4b63 7663 467a 5838 4344  3aoW0IKcvcFzX8CD
-	0x0320:  5432 7666 4b31 6c42 416d 6279 3166 764f  T2vfK1lBAmby1fvO
-	0x0330:  4643 7952 7863 6f5a 6277 5633 6a4b 4971  FCyRxcoZbwV3jKIq
-	0x0340:  6b35 6958 4674 7557 5261 6b48 6944 6132  k5iXFtuWRakHiDa2
-	0x0350:  7769 3075 2f53 6430 5a49 7a75 4464 7947  wi0u/Sd0ZIzuDdyG
-	0x0360:  774f 6a31 7838 3130 356a 772f 5a2b 355a  wOj1x8105jw/Z+5Z
-	0x0370:  6f4b 6f48 396e 6779 6e4b 5366 5839 742f  oKoH9ngynKSfX9t/
-	0x0380:  6862 4b79 435a 6966 7739 4148 3053 6d4b  hbKyCZifw9AH0SmK
-	0x0390:  436e 4c38 5358 513d 3d0d 0a0d 0a         CnL8SXQ==....
-17:22:30.571152 IP localhost.localdomain.45836 > localhost.localdomain.53239: Flags [.], ack 873, win 2048, options [nop,nop,TS val 4895716 ecr 4895706], length 0
-	0x0000:  4500 0034 f15b 4000 4006 4b66 7f00 0001  E..4.[@.@.Kf....
-	0x0010:  7f00 0001 b30c cff7 9b7f 43de fc9a 68ac  ..........C...h.
-	0x0020:  8010 0800 fe28 0000 0101 080a 004a b3e4  .....(.......J..
-	0x0030:  004a b3da                                .J..
-17:22:35.803152 IP localhost.localdomain.53240 > localhost.localdomain.45836: Flags [.], ack 2157632553, win 2048, options [nop,nop,TS val 4897024 ecr 4885760], length 0
-	0x0000:  4500 0034 3a63 4000 4006 025f 7f00 0001  E..4:c@.@.._....
-	0x0010:  7f00 0001 cff8 b30c 7533 e963 809a dc29  ........u3.c...)
-	0x0020:  8010 0800 fe28 0000 0101 080a 004a b900  .....(.......J..
-	0x0030:  004a 8d00                                .J..
-17:22:35.803213 IP localhost.localdomain.45836 > localhost.localdomain.53240: Flags [.], ack 1, win 2048, options [nop,nop,TS val 4897024 ecr 4840696], length 0
-	0x0000:  4500 0034 10e5 4000 4006 2bdd 7f00 0001  E..4..@.@.+.....
-	0x0010:  7f00 0001 b30c cff8 809a dc29 7533 e964  ...........)u3.d
-	0x0020:  8010 0800 fe28 0000 0101 080a 004a b900  .....(.......J..
-	0x0030:  0049 dcf8                                .I..
-17:23:15.611193 IP localhost.localdomain.53239 > localhost.localdomain.45836: Flags [.], ack 1, win 2048, options [nop,nop,TS val 4906976 ecr 4895716], length 0
-	0x0000:  4500 0034 be85 4000 4006 7e3c 7f00 0001  E..4..@.@.~<....
-	0x0010:  7f00 0001 cff7 b30c fc9a 68ab 9b7f 43de  ..........h...C.
-	0x0020:  8010 0800 fe28 0000 0101 080a 004a dfe0  .....(.......J..
-	0x0030:  004a b3e4                                .J..
-17:23:15.611290 IP localhost.localdomain.45836 > localhost.localdomain.53239: Flags [.], ack 873, win 2048, options [nop,nop,TS val 4906976 ecr 4895706], length 0
-	0x0000:  4500 0034 f15c 4000 4006 4b65 7f00 0001  E..4.\@.@.Ke....
-	0x0010:  7f00 0001 b30c cff7 9b7f 43de fc9a 68ac  ..........C...h.
-	0x0020:  8010 0800 fe28 0000 0101 080a 004a dfe0  .....(.......J..
-	0x0030:  004a b3da                                .J..
-</pre>
-
-[[!tag /design/assistant]]
-[[done]]
diff --git a/doc/bugs/webapp_hang/comment_1_08aa908a64d0fe2d50438d01545c3f01._comment b/doc/bugs/webapp_hang/comment_1_08aa908a64d0fe2d50438d01545c3f01._comment
deleted file mode 100644
index 66822d759..000000000
--- a/doc/bugs/webapp_hang/comment_1_08aa908a64d0fe2d50438d01545c3f01._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://gdr.name/"
- nickname="gdr.name"
- subject="Not only Chrome"
- date="2013-03-09T10:55:57Z"
- content="""
-It happened to me numerous times with Opera. I was never able to repeat it hence no bug report.
-"""]]
diff --git a/doc/bugs/webapp_hang/comment_2_2a21ac5657128a454f9deb77c4d18057._comment b/doc/bugs/webapp_hang/comment_2_2a21ac5657128a454f9deb77c4d18057._comment
deleted file mode 100644
index ece1aa358..000000000
--- a/doc/bugs/webapp_hang/comment_2_2a21ac5657128a454f9deb77c4d18057._comment
+++ /dev/null
@@ -1,21 +0,0 @@
-[[!comment format=mdwn
- username="http://crosstwine.com/dd/"
- ip="88.65.128.43"
- subject="chrome://net-internals/"
- date="2013-03-09T20:10:54Z"
- content="""
-Hi Joey,
-
-I see that you have found the cause and a workaround for this particular
-problem, but would like to point out that `chrome://net-internals/` can be
-very useful for diagnosing such issues.
-
-(I once hit the `SOCKET_POOL_STALLED_MAX_SOCKETS_PER_GROUP` problem
-mentioned in
-<https://code.google.com/p/chromium/issues/detail?id=27324>, which can
-cause Chromium to keep spinning while not issuing any new requests to a
-specific web server.)
-
-Cheers,  
-Damien Diederen
-"""]]
diff --git a/doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo.mdwn b/doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo.mdwn
deleted file mode 100644
index b7ecdebbf..000000000
--- a/doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-What steps will reproduce the problem?
-
-Fresh install on a 12.40 xubuntu with
-
-    cabal install git-annex --bindir=$HOME/bin
-
-What is the expected output? What do you see instead?
-
-I launched the git-annex webapp (the assistant) and the system proposed to create a git-annex repository: I choose ~/annex/ and clicked on "Make repositiry" but I got:
-
-    Internal Server Error
-
-    user error (git ["--git-dir=/home/m/annex/.git","--work-tree=/home/m/annex","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] exited 128)
-
-    git-annex version 3.20130102
- 
-What version of git-annex are you using? On what operating system?
-
-git-annex version 3.20130102 on Xubuntu 12.04, installed with cabal (got no errors).
-
-Please provide any additional information below.
-
-I do not know if there is any log, or any info about the reason of the failure. Something useful could be that  ~/annex/ now contains an empty git repository, so "something" happened despite the error.
-
-> Made assistant detect misconfigured system and set enough environment
-> variables so git will work. [[done]] --[[Joey]]
diff --git a/doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo/comment_1_1bcf0f565eacac851bd21cd428c8e0a5._comment b/doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo/comment_1_1bcf0f565eacac851bd21cd428c8e0a5._comment
deleted file mode 100644
index fbf63a97c..000000000
--- a/doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo/comment_1_1bcf0f565eacac851bd21cd428c8e0a5._comment
+++ /dev/null
@@ -1,33 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.211"
- subject="comment 1"
- date="2013-01-06T17:00:40Z"
- content="""
-There should be an error message on either the terminal where you started git-annex, or in ~/.xsession-errors if you started it from a GUI menu. 
-
-Without the error message, this seems most likely to be another case of git commit failing due to not being able to determine the user's full name. For example, if I delete my full name out of /etc/passwd, 
-
-<pre>
-describe . ok
-(Recording state in git...)
-
-*** Please tell me who you are.
-
-Run
-
-  git config --global user.email \"you@example.com\"
-  git config --global user.name \"Your Name\"
-
-to set your account's default identity.
-Omit --global to set the identity only in this repository.
-
-fatal: empty ident  joey@gnu.kitenet.net
-  not allowed
-
-git-annex: user error (git [\"--git-dir=/home/joey/tmp/r/.git\",\"--work-tree=/home/joey/tmp/r\",\"commit-tree\",\"5316749be9efffeee538051b576166291c516472\",\"-p\",\"refs/heads/git-annex\"] exited 128)
-failed
-</pre>
-
-I'm perfectly comfortable with command-line git-annex not working if the system is so misconfigured; after all git tells the user one way to fix it. Perhaps though it's worth the assistant holding the user's hand here and detecting this problem.
-"""]]
diff --git a/doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo/comment_2_7dd2483b5b07df8f3b37a34651c05962._comment b/doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo/comment_2_7dd2483b5b07df8f3b37a34651c05962._comment
deleted file mode 100644
index 5459af2e6..000000000
--- a/doc/bugs/webapp_raise_an_internal_server_error_upon_creating_the_initial_repo/comment_2_7dd2483b5b07df8f3b37a34651c05962._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="m"
- ip="79.98.40.98"
- subject="thanks"
- date="2013-01-11T01:23:25Z"
- content="""
-exactly, it was an error on the git configuration 
-"""]]
diff --git a/doc/bugs/webapp_requires_reload_for_notification_bubbles.mdwn b/doc/bugs/webapp_requires_reload_for_notification_bubbles.mdwn
deleted file mode 100644
index f8ea8ad39..000000000
--- a/doc/bugs/webapp_requires_reload_for_notification_bubbles.mdwn
+++ /dev/null
@@ -1,41 +0,0 @@
-What steps will reproduce the problem?
-
-> Open Webapp on Mac OSX Mountain Lion
-
-What is the expected output? What do you see instead?
-
-> I expect notification bubbles and transfer progress bars to show and update on the fly, as well as notifications to disappear when I click the X.
-> 
-> Instead, I have to reload the page after clicking an X or to see new bubbles and progress bar updates.
-
-What version of git-annex are you using? On what operating system?
-
->     git-annex version: 3.20130107
->     local repository version: 3
->     default repository version: 3
->     supported repository versions: 3
->     upgrade supported from repository versions: 0 1 2
-> 
-> Mac OS X 10.8.2 Build 12C3006
-> 
-> Chrome Version 23.0.1271.101
-
-Please provide any additional information below.
-
-Javascript console error log says "Syntax error on localhost:5" which is this line:
-
-    <link rel="stylesheet" href="/static/css/bootstrap.css"><link rel="stylesheet" href="/static/css/bootstrap-responsive.css"><style>body{padding-top:60px;padding-bottom:40px}.sidebar-nav{padding:9px 0}</style><script src="/static/jquery.full.js"></script><script src="/static/js/bootstrap-dropdown.js"></script><script src="/static/js/bootstrap-modal.js"></script><script src="/static/js/bootstrap-collapse.js"></script><script src="/static/longpolling.js"></script><script>function longpoll_"sidebar"() {
-
-> And the bug is the quoting inside the function name.
-> 
-> I believe this affects all builds done using shakespeare-js 1.0.0.2.
-> It may be that some browsers manage to run the javascript despite the
-> quoting. Otherwise, I don't know why noone has reported this bug
-> before now.
-> 
-> I've fixed this bug in git. Your testing with tomorrow's
-> autobuild would be appreciated. --[[Joey]]
-
->> There was a second issue as noted. I fixed that last week,
->> and the fix is in the autobuilds if you'd like to test before
->> the next release. [[done]] again --[[Joey]]
diff --git a/doc/bugs/webapp_requires_reload_for_notification_bubbles/comment_1_b15480e5dec1ffbebb8cde1ca8d7c9d5._comment b/doc/bugs/webapp_requires_reload_for_notification_bubbles/comment_1_b15480e5dec1ffbebb8cde1ca8d7c9d5._comment
deleted file mode 100644
index 4544f1efb..000000000
--- a/doc/bugs/webapp_requires_reload_for_notification_bubbles/comment_1_b15480e5dec1ffbebb8cde1ca8d7c9d5._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q"
- nickname="Andrew"
- subject="comment 1"
- date="2013-01-19T06:53:19Z"
- content="""
-Just got around to testing both the git-annex.app and the latest build from cabal 3.20130114 and still no go. Neither notification bubbles nor progress bars will update without reloading the page. However the errors have changed:
-
-    Uncaught Error: Syntax error, unrecognized expression: #\"sidebar\"
-
-"""]]
diff --git a/doc/bugs/webapp_requires_reload_for_notification_bubbles/comment_2_8dad57a852e1db804aa38f90f3bb398b._comment b/doc/bugs/webapp_requires_reload_for_notification_bubbles/comment_2_8dad57a852e1db804aa38f90f3bb398b._comment
deleted file mode 100644
index de4c4842a..000000000
--- a/doc/bugs/webapp_requires_reload_for_notification_bubbles/comment_2_8dad57a852e1db804aa38f90f3bb398b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q"
- nickname="Andrew"
- subject="comment 2"
- date="2013-01-20T02:04:01Z"
- content="""
-I just built git-annex fresh from the git repo and the new build seems to have fixed it. [[done]] indeed. :)
-"""]]
diff --git a/doc/bugs/webapp_shows___34__Added_x_files__34___a_bit_ugly.mdwn b/doc/bugs/webapp_shows___34__Added_x_files__34___a_bit_ugly.mdwn
deleted file mode 100644
index 51e157c19..000000000
--- a/doc/bugs/webapp_shows___34__Added_x_files__34___a_bit_ugly.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-### Please describe the problem.
-When adding a folder with some 80.000 files, the sidebar with "Added x files" gets updated in batches. After some time, it shows (also see attached screenshot):
-
-> Added 6496 files 5781 files 8633 files 7363 files 6159 files
-
-This is a bit ugly. There could a newline after "files".
-
-### What steps will reproduce the problem?
-Add a folder with many files and subfolders in it.
-
-### What version of git-annex are you using? On what operating system?
-4.20130627 
-
-> I have improved the display, now it will just show a single ongoing count,
-> and the most recent 10 or so files added. [[done]] --[[Joey]]
diff --git a/doc/bugs/webapp_takes_100__37___of_the_cpu.mdwn b/doc/bugs/webapp_takes_100__37___of_the_cpu.mdwn
deleted file mode 100644
index 463de781b..000000000
--- a/doc/bugs/webapp_takes_100__37___of_the_cpu.mdwn
+++ /dev/null
@@ -1,46 +0,0 @@
-### Please describe the problem.
-
-I just started git-annex, and I can hear the fan of my CPU. That doesn't happen unless the CPU is maxed, and indeed:
-
-[[!format txt """
-top - 10:09:53 up 2 days, 13:13, 10 users,  load average: 2,49, 2,41, 1,59
-Tasks: 306 total,   3 running, 302 sleeping,   0 stopped,   1 zombie
-%Cpu(s): 57,2 us,  7,9 sy,  1,2 ni, 32,1 id,  1,3 wa,  0,0 hi,  0,3 si,  0,0 st
-KiB Mem:   8162960 total,  7480272 used,   682688 free,  1107616 buffers
-KiB Swap:  4022268 total,    23384 used,  3998884 free,  3469028 cached
-
-  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
-27841 anarcat   20   0  191m  45m  20m S  92,3  0,6   4:32.68 /usr/local/bin/git-annex webapp
-"""]]
-
-### What steps will reproduce the problem?
-
-I am not sure. I just started the webapp, and it seems to be scanning two huge repositories (160GB and 800GB) with lots of files. The larger one is also in the process of being sync'd to the backup drive.
-
-### What version of git-annex are you using? On what operating system?
-
-My usual bastard build from hell:
-
-[[!format txt """
-git-annex version: 5.20131109-gf2cb5b9
-build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash
-key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
-remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
-local repository version: 3
-default repository version: 3
-supported repository versions: 3 5
-upgrade supported from repository versions: 0 1 2 4
-"""]]
-
-### Please provide any additional information below.
-
-Note that I had to close the chromium tab that was displaying the actual webapp UI, because that was taking another 50% of a CPU (I have a dual core).
-
-Note also that things calmed down since git-annex started transfering larger files - the webapp only takes 75% of the CPU now. ;) And chromium is negligible. But there clearly seems to be a degenerate case where a lot of small files get transfered that seem to freakout the web UI. -- [[anarcat]]
-
-Oh, and just copying the files using `git annex copy --to backup` doesn't use 100% of the CPU.
-
-> Anarcat also files a bug about the assistant using too much CPU, and that
-> turned out to be due to a bug in the fsck scheduler that made it spin.
-> I suspect this is the same bug, which is fixed now, so closing. [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/webapp_takes_100__37___of_the_cpu/comment_1_6312860de9f30cbb05762cd67edc705a._comment b/doc/bugs/webapp_takes_100__37___of_the_cpu/comment_1_6312860de9f30cbb05762cd67edc705a._comment
deleted file mode 100644
index 3ec9c52eb..000000000
--- a/doc/bugs/webapp_takes_100__37___of_the_cpu/comment_1_6312860de9f30cbb05762cd67edc705a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 1"
- date="2013-12-31T19:38:24Z"
- content="""
-The webapp pushes a changed html div to the browser when eg, updating the progress bar. This is inneficient, which doesn't usually matter, since git-annex is not generally used with a large number of small files
-"""]]
diff --git a/doc/bugs/webapp_usability:_put_the_notices_on_the_right.mdwn b/doc/bugs/webapp_usability:_put_the_notices_on_the_right.mdwn
deleted file mode 100644
index 54f6c3a4f..000000000
--- a/doc/bugs/webapp_usability:_put_the_notices_on_the_right.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-### Please describe the problem.
-
-The colored notices on the left of the screen are a little off. When they disappear, it also leaves a huge gap on the left side.
-
-### What steps will reproduce the problem?
-
-Click the `X` on all the messages on the left.
-
-### What version of git-annex are you using? On what operating system?
-
-4.20130815~bpo70+1 on Debian Wheezy, with Chromium Version 29.0.1547.57 Debian 7.1 (217859)
-
-### Please provide any additional information below.
-
-This is admittedly a very mild problem, but from a usability perspective, it would be less confusing to show those on the right. When they were gone, I thought git-annex was broken somewhat... -- [[anarcat]]
-
-> [[done]], although I'm not sure I'm sold on their being on the right
-> being better. --[[Joey]]
diff --git a/doc/bugs/webapp_usability:_put_the_notices_on_the_right/comment_1_ec7a444e09a028b5225bd41fb83442e8._comment b/doc/bugs/webapp_usability:_put_the_notices_on_the_right/comment_1_ec7a444e09a028b5225bd41fb83442e8._comment
deleted file mode 100644
index a494c5326..000000000
--- a/doc/bugs/webapp_usability:_put_the_notices_on_the_right/comment_1_ec7a444e09a028b5225bd41fb83442e8._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.255.110"
- subject="comment 1"
- date="2013-09-09T04:36:12Z"
- content="""
-They're on the left hand side because that's where Bootstrap puts its sidebar.
-If someone knows how to make it put its sidebar on the right I'll happily do so.
-"""]]
diff --git a/doc/bugs/webdav_special_remote_fails_on_android___40__box.com__41__.mdwn b/doc/bugs/webdav_special_remote_fails_on_android___40__box.com__41__.mdwn
deleted file mode 100644
index 8d21a67c9..000000000
--- a/doc/bugs/webdav_special_remote_fails_on_android___40__box.com__41__.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-### Please describe the problem.
-
-The Box.com/WebDAV special remote fails with this error on my Android tablet:
-
-    WebDAV failed to write file: InternalIOException user error (Network.Socket.setSocketOption: socket option NoDelay unsupported on this system): user error
-
-### What steps will reproduce the problem?
-
- 1. Install the Android beta from the download page.
- 2. Create a repository (using the assistant)
- 3. (At this point I configured XMPP, if that's relevant.)
- 4. Configure a Box.com repository using the assistant
-
-The repository will fail to add with the above error message.
-
-### What version of git-annex are you using? On what operating system?
-
-git-annex 5.20131221-gf8c928d
-
-Android 4.0.4<br>
-Kernel 2.6.35-palm-tenderloin<br>
-CyanogenMod 9-20121202-NIGHTLY-tenderloin (HP Touchpad)
-
-### Please provide any additional information below.
-
-I have successfully set up the same Box.com account via the assistant on another machine.
-
-I don't see any mention of WebDAV in daemon.log and friends.  
-
-It seems like NODELAY should be optional, as it's just a performance optimization (and disabling packet coalescing may be battery-hostile on a mobile device, too).
-
-> Should be fixed in the last release, [[done]] --[[Joey]]
diff --git a/doc/bugs/webdav_special_remote_fails_on_android___40__box.com__41__/comment_1_f57757b4bcc4ace73bf660419d944c33._comment b/doc/bugs/webdav_special_remote_fails_on_android___40__box.com__41__/comment_1_f57757b4bcc4ace73bf660419d944c33._comment
deleted file mode 100644
index a4e94643c..000000000
--- a/doc/bugs/webdav_special_remote_fails_on_android___40__box.com__41__/comment_1_f57757b4bcc4ace73bf660419d944c33._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 1"
- date="2013-12-29T21:31:49Z"
- content="""
-Yeah, I have patched haskell network library to not do anything for NODELAY on Android, but I have to re-bootstrap my entire haskell dev environment due to that change. With luck, I will have a fixed build to try in around 16 hours.
-"""]]
diff --git a/doc/bugs/weird_local_clone_confuses.mdwn b/doc/bugs/weird_local_clone_confuses.mdwn
deleted file mode 100644
index aa838f167..000000000
--- a/doc/bugs/weird_local_clone_confuses.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-See
-<http://www.git.code-experiments.com/blog/2011/01/manage-large-files-with-git-annex-by-joey-hess.html>
-
-If a local repo is cloned with "git clone orig/.git new", then git-annex in
-new cannot see origin. 
-
-the .git/config has "url=/.../orig/.git". Apparently git is ok with that
-weird construction; probably it treats it as a bare git repo. But git-annex
-just sees a directory w/o a .git subdir, and gives up.
-
----
-
-Just tested, and the new support for bare repositories didn't solve this.
-(Because config.bare is not set.)
-
-I think this is not something git-annex should go out of its way to
-support. [[done]]
---[[Joey]] 
-
-Later.. Fixed this after all. --[[Joey]] 
diff --git a/doc/bugs/wget_tarball_over_https_complains.mdwn b/doc/bugs/wget_tarball_over_https_complains.mdwn
deleted file mode 100644
index c318a1b4a..000000000
--- a/doc/bugs/wget_tarball_over_https_complains.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-### Please describe the problem.
-Can't download new tarball via wget on remote machine without passing '--no-check-certificate'.
-
-### What steps will reproduce the problem?
-
-[[!format sh """
-greg@rose:~/bin$ wget https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz
---2014-05-14 15:55:59--  https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz
-Resolving downloads.kitenet.net... 107.170.31.195
-Connecting to downloads.kitenet.net|107.170.31.195|:443... connected.
-ERROR: certificate common name "kitenet.net" doesn\'t match requested host name "downloads.kitenet.net".
-To connect to downloads.kitenet.net insecurely, use '--no-check-certificate'.
-"""]]
-
-> [[done]]: Per joey's comment, I'll investigate my broken wget
diff --git a/doc/bugs/wget_tarball_over_https_complains/comment_1_4227a75f2eb0de6a2422efe8d791e130._comment b/doc/bugs/wget_tarball_over_https_complains/comment_1_4227a75f2eb0de6a2422efe8d791e130._comment
deleted file mode 100644
index 7f8c906a1..000000000
--- a/doc/bugs/wget_tarball_over_https_complains/comment_1_4227a75f2eb0de6a2422efe8d791e130._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 1"
- date="2014-05-15T19:56:53Z"
- content="""
-I don't know why this would happen. The https cert for downloads.kitenet.net is a wildcard cert for *.kitenet.net.
-
-Also, I cannot reproduce it with wget on either debian stable or unstable. So it seems more likely to be a bug in your wget than anything..
-"""]]
diff --git a/doc/bugs/wget_tarball_over_https_complains/comment_2_25fb35b2e707b174f255a1dafca8eff9._comment b/doc/bugs/wget_tarball_over_https_complains/comment_2_25fb35b2e707b174f255a1dafca8eff9._comment
deleted file mode 100644
index e2ef20fd8..000000000
--- a/doc/bugs/wget_tarball_over_https_complains/comment_2_25fb35b2e707b174f255a1dafca8eff9._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.36"
- subject="comment 2"
- date="2014-05-24T17:48:16Z"
- content="""
-I reproduced this on a debian 6.0 system. Eep that's old. Probably *was* a wget bug.
-
-After downloading with --no-check-certificate, I tried with the wget bundled in the git-annex tarball. That works.
-"""]]
diff --git a/doc/bugs/windows_fails_test___34__recoverEncode__34__.mdwn b/doc/bugs/windows_fails_test___34__recoverEncode__34__.mdwn
deleted file mode 100644
index 0413bb55d..000000000
--- a/doc/bugs/windows_fails_test___34__recoverEncode__34__.mdwn
+++ /dev/null
@@ -1,39 +0,0 @@
-### Please describe the problem.
-
-My windows install (2013-09-09) fails "quick checks" when running "git annex test".  See below the errors from two seperate runs of the test in two fresh empty directories:
-
-*** Failed! Exception: 'recoverEncode: invalid argument (invalid character)' (after 13 tests): 
-Key {keyName = "\140\DEL\159/\RS'", keyBackendName = "WQACSWJDVY", keySize = Just 6, keyMtime = Just 3}
-prop_idempotent_configEscape
-
-*** Failed! Exception: 'recoverEncode: invalid argument (invalid character)' (after 4 tests): 
-Key {keyName = "\130", keyBackendName = "Y", keySize = Nothing, keyMtime = Nothing}
-prop_idempotent_configEscape
-
-### What steps will reproduce the problem?
-
-create a directory
-cd to it in cmd or Git Bash
-run "git annex test"
-
-
-### What version of git-annex are you using? On what operating system?
-
-OS Name:                   Microsoft Windows 7 Professional (64bit)
-OS Version:                6.1.7601 Service Pack 1 Build 7601
-
-Install Git-1.8.3-preview20130601 (third option to add git and tools to path)
-Install git-annex-installer (2013-09-09)
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-
-# End of transcript or log.
-"""]]
-
-> I've released a fix for this problem. Thanks for reporting! [[done]]
-> --[[Joey]]
diff --git a/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_1_424b3536e21e02f192f7f2b8e833ed18._comment b/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_1_424b3536e21e02f192f7f2b8e833ed18._comment
deleted file mode 100644
index e94608921..000000000
--- a/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_1_424b3536e21e02f192f7f2b8e833ed18._comment
+++ /dev/null
@@ -1,67 +0,0 @@
-[[!comment format=mdwn
- username="gary"
- ip="82.112.140.250"
- subject="Thanks for the fix"
- date="2013-09-12T07:20:12Z"
- content="""
-Hi the fix works fine, all the tests pass now.  However I am having issues when trying to sync two directories.  I have had this working in direct mode in fedora but not in the previously mentioned windows install
-
-2 directories d1 and d2.
-
-SETUP:
-
-cd d1
-
-mkdir annex
-
-cd annex
-
-cp someFile . (as get branch issue if empty)
-
-git init
-
-git annex init d1
-
-cp someFile . (as get branch issue if empty)
-
-git annex add .
-
-git annex sync
-
-cd ..\..\d2
-
-git clone ..\..\d1\annex
-
-cd annex
-
-git annex init d2
-
-git remote add d1 ..\..\d1\annex
-
-cd ..\..\d1\annex
-
-git remote add d2 ..\..\d2\annex
-
-
-SYNCING
-
-cd d1\annex
-
-cp someFiles .
-
-git annex add .
-
-git annex sync
-
-cd ..\..\d2\annex
-
-git annex sync
-
-git annex mirror --from d1
-
-It looks like the files copy across but when I look at them in explorer they are still just the place holders.
-
-any ideas on what may be going on.  Does the work flow look correct?
-
-(ps typo on all slashes but 
-"""]]
diff --git a/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_2_78db183aa401e2023d7faec5f7a4a573._comment b/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_2_78db183aa401e2023d7faec5f7a4a573._comment
deleted file mode 100644
index f186a0d81..000000000
--- a/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_2_78db183aa401e2023d7faec5f7a4a573._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.2.134"
- subject="comment 2"
- date="2013-09-13T17:04:26Z"
- content="""
-That is an unrelated bug. You got very lucky that I saw your followup comment. 
-
-I was able to reproduce it, and found bug in git annex fsck that prevented it from finding and fixing this problem on Windows. Am still investigating why the problem occurs in the first place..
-"""]]
diff --git a/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_3_ed2da19eaf0bd0864f6b28816a79bc23._comment b/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_3_ed2da19eaf0bd0864f6b28816a79bc23._comment
deleted file mode 100644
index a8f7c0a02..000000000
--- a/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_3_ed2da19eaf0bd0864f6b28816a79bc23._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.2.134"
- subject="comment 3"
- date="2013-09-13T17:44:04Z"
- content="""
-I have now diagnosed and fixed the underlying problem on Windows.
-"""]]
diff --git a/doc/bugs/windows_port_-_can__39__t_directly_access_files.mdwn b/doc/bugs/windows_port_-_can__39__t_directly_access_files.mdwn
deleted file mode 100644
index cb2e650d0..000000000
--- a/doc/bugs/windows_port_-_can__39__t_directly_access_files.mdwn
+++ /dev/null
@@ -1,250 +0,0 @@
-### Please describe the problem.
-Using the windows port of git annex, I'm unable to directly access files that are retrieved from a remote ssh repository. Instead, the file contains a reference to ../.git/annex/objects....
-
-**Update** This appears to be a problem with remote bare repositories only. I was able to get from a remote regular git repository without the stand-in symlinks. The stand-in symlink file gets replaced with the real content on "get" using a non-base repository.
-
-### What steps will reproduce the problem?
-
-[[!format sh """
-** on ssh server **
-
-git init --bare annex.git
-cd annex.git
-git annex init origin
-
-** on windows laptop - add content main repository ** 
-git init annex
-cd annex
-git annex init laptop
-
-git remote add origin ssh://xxxxx/~/annex.git
-echo hello > foo.txt
-git annex add .
-git commit -m "done"
-git annex sync
-git annex copy --to origin
-git annex sync
-git annex whereis foo.txt
-
-** on windows laptop - backup repository **
-
-cd ..
-git init annex.backup
-cd annex.backup
-git annex init "backup"
-git remote add origin ssh://joebo@xxxxx.com/~/annex.git
-git fetch origin
-git merge origin/synced/master
-git annex sync
-git annex get .
-find . | xargs grep hello
-./.git/annex/objects/d91/b11/SHA256E-s6--5891b5b522d5df086d0ff0b110fbd9d21bb4fc7
-163af34d08286a2e846f6be03.txt/SHA256E-s6--5891b5b522d5df086d0ff0b110fbd9d21bb4fc
-7163af34d08286a2e846f6be03.txt:hello
-
-** updating the file from windows laptop **
-cd ..\annex
-echo hello2 > foo.txt
-git annex add .
-git commit -m "updated"
-git annex sync
-git annex copy --to origin
-git annex sync	
-
-cd ..\annex.backup
-git fetch origin
-git merge origin/synced/master
-get annex sync
-git annex get .
-find . | xargs grep hello2
-./.git/annex/objects/7ed/895/SHA256E-s9--3f70947299d2926028fd0107c4309e65ca33a9a
-e0175fc4bc57792ca17240d18.txt/SHA256E-s9--3f70947299d2926028fd0107c4309e65ca33a9
-ae0175fc4bc57792ca17240d18.txt:hello2
-"""]]
-
-
-
-### What version of git-annex are you using? On what operating system?
-
-	git-annex version: 4.20130601-gc01f842
-	build flags: Pairing Testsuite S3 WebDAV DNS
-	local repository version: 4
-	default repository version: 3
-	supported repository versions: 3 4
-	upgrade supported from repository versions: 2
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-joebo@joebo:~$ sudo rm -rf annex.git
-joebo@joebo:~$ git init --bare annex.git
-Initialized empty Git repository in /home/joebo/annex.git/
-joebo@joebo:~$ cd annex.git
-joebo@joebo:~/annex.git$ git annex init origin
-init origin ok
-
-
-
-C:\Users\joebo>cd annex
-
-C:\Users\joebo\annex>git annex init laptop
-init laptop
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-ok
-(Recording state in git...)
-
-C:\Users\joebo\annex>
-C:\Users\joebo\annex>git remote add origin ssh://joebo@xxxxx.com/~
-cho hello > foo.txt
-
-C:\Users\joebo\annex>git annex add .
-add foo.txt (checksum...) ok
-(Recording state in git...)
-
-C:\Users\joebo\annex>git commit -m "done"
-[master (root-commit) 7f54efa] done
- 1 file changed, 1 insertion(+)
- create mode 120000 foo.txt
-
-C:\Users\joebo\annex>git annex sync
-commit
-ok
-pull origin
-warning: no common commits
-remote: Counting objects: 5, done.
-remote: Compressing objects: 100% (3/3), done.
-remote: Total 5 (delta 1), reused 0 (delta 0)
-Unpacking objects: 100% (5/5), done.
-From ssh://xxxxx.com/~/annex
- * [new branch]      git-annex  -> origin/git-annex
-ok
-(merging origin/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 18, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (12/12), done.
-Writing objects: 100% (16/16), 1.48 KiB, done.
-Total 16 (delta 1), reused 0 (delta 0)
-To ssh://joebo@xxxxx.com/~/annex.git
- * [new branch]      git-annex -> synced/git-annex
- * [new branch]      master -> synced/master
-ok
-
-C:\Users\joebo\annex>git annex copy --to origin
-copy foo.txt (checking origin...) (to origin...)
-foo.txt
-           0 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 67 bytes  received 31 bytes  65.33 bytes/sec
-total size is 0  speedup is 0.00
-ok
-(Recording state in git...)
-
-C:\Users\joebo\annex>git annex sync
-commit
-ok
-pull origin
-ok
-push origin
-Counting objects: 9, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (4/4), done.
-Writing objects: 100% (5/5), 446 bytes, done.
-Total 5 (delta 1), reused 0 (delta 0)
-To ssh://joebo@xxxxx.com/~/annex.git
-   ed1a701..c4c9cd0  git-annex -> synced/git-annex
-ok
-
-C:\Users\joebo\annex>git annex whereis foo.txt
-whereis foo.txt (2 copies)
-        03573d86-d460-11e2-8500-ebab2910b225 -- origin
-        3b6b60fb-0979-4869-98de-38208182ab92 -- here (laptop)
-ok
-
-
-C:\Users\joebo\annex>cd ..
-
-C:\Users\joebo>git init annex.backup
-Initialized empty Git repository in C:/Users/joebo/annex.backup/.git/
-
-C:\Users\joebo>cd annex.backup
-
-C:\Users\joebo\annex.backup>git annex init "backup"
-init backup
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-ok
-(Recording state in git...)
-
-C:\Users\joebo\annex.backup>git remote add origin ssh://joebo@xxxxx.com/~/anne
-x.git
-
-C:\Users\joebo\annex.backup>git fetch origin
-warning: no common commits
-remote: Counting objects: 25, done.
-remote: Compressing objects: 100% (19/19), done.
-remote: Total 25 (delta 4), reused 0 (delta 0)
-Unpacking objects: 100% (25/25), done.
-From ssh://xxxxx.com/~/annex
- * [new branch]      git-annex  -> origin/git-annex
- * [new branch]      synced/git-annex -> origin/synced/git-annex
- * [new branch]      synced/master -> origin/synced/master
-
-C:\Users\joebo\annex.backup>git merge origin/synced/master
-
-C:\Users\joebo\annex.backup>git annex sync
-(merging origin/git-annex origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-commit
-ok
-pull origin
-ok
-push origin
-Counting objects: 12, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (6/6), done.
-Writing objects: 100% (8/8), 818 bytes, done.
-Total 8 (delta 2), reused 0 (delta 0)
-To ssh://joebo@xxxxx.com/~/annex.git
-   c4c9cd0..f403560  git-annex -> synced/git-annex
-ok
-
-C:\Users\joebo\annex.backup>git annex get .
-get foo.txt (from origin...)
-SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.txt
-
-           0 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 30 bytes  received 145 bytes  116.67 bytes/sec
-total size is 0  speedup is 0.00
-ok
-(Recording state in git...)
-
-C:\Users\joebo\annex.backup>cat foo.txt
-.git/annex/objects/fW/Gk/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649
-b934ca495991b7852b855.txt/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e464
-9b934ca495991b7852b855.txt
-C:\Users\joebo\annex.backup>ls
-foo.txt
-
-
-# End of transcript or log.
-"""]]
-
-> [[done]]; see my comment. --[[Joey]] 
diff --git a/doc/bugs/windows_port_-_can__39__t_directly_access_files/comment_1_03ef9d33839173044dcc4f2b37f575d2._comment b/doc/bugs/windows_port_-_can__39__t_directly_access_files/comment_1_03ef9d33839173044dcc4f2b37f575d2._comment
deleted file mode 100644
index ad41694b0..000000000
--- a/doc/bugs/windows_port_-_can__39__t_directly_access_files/comment_1_03ef9d33839173044dcc4f2b37f575d2._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA"
- nickname="Joe"
- subject="Closed - not a bug"
- date="2013-06-14T13:23:24Z"
- content="""
-It was a user error. I needed to have git-shell in my path. I had added it to the end of .bashrc and it needed to be before the part that returned if not interactive: http://stackoverflow.com/questions/940533/how-do-i-set-path-such-that-ssh-userhost-command-works
-"""]]
diff --git a/doc/bugs/windows_port_-_can__39__t_directly_access_files/comment_2_c65e5491c82908af46fe2c97e048d210._comment b/doc/bugs/windows_port_-_can__39__t_directly_access_files/comment_2_c65e5491c82908af46fe2c97e048d210._comment
deleted file mode 100644
index 3368e3a31..000000000
--- a/doc/bugs/windows_port_-_can__39__t_directly_access_files/comment_2_c65e5491c82908af46fe2c97e048d210._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 2"
- date="2013-06-14T15:40:04Z"
- content="""
-Your transcript shows `git annex get` apparently receiving the file. I don't see how that could possibly have worked if git-annex-shell were not in the path on the server, since that is the command it runs to send the file. Also, `git annex copy` is earlier used to send the file to origin, which again should not work if git-annex-shell was not in the path. I think this whole git-annex-shell not in path thing is a red herring.
-
-What actually appears to be going on is this:
-
-1. You create a new empty repository. Since this is Windows, it's forced into direct mode.
-2. You manually merge origin/synced/master into this repository. Bypassing `git annex sync` in this way means that direct mode mappings are not updated for the files contained in that branch.
-3. You run `git annex get` on a file from that branch. The file is retrieved. Since no direct mode mapping exists for the object it just retrieved, it stashes it in .git/annex/objects and the file is left with the fake symlink git uses on windows.
-
-The manual merge in step 2 is the cause of the problem. The [[direct_mode]] documentation advises against using git commands that update the repository tree because it can lead to this kind of problem (as well as more serious data loss).
-
-Of course, you had no choice but to merge from origin/synced/master, because git annex sync didn't push to origin/master, so simply cloning the bare repository wouldn't work. However, I did fix that a few days ago.
-
-I see this as more evidence of there needing to be a [[todo/direct_mode_guard]] to block users from running unsafe git commands in direct mode repositories. This bug probably can be closed, assuming I correctly understand what happened.
-"""]]
diff --git a/doc/bugs/windows_port_-_git_annex_add_hangs_when_adding_17_files_at_once_or_more_.mdwn b/doc/bugs/windows_port_-_git_annex_add_hangs_when_adding_17_files_at_once_or_more_.mdwn
deleted file mode 100644
index 50f020b19..000000000
--- a/doc/bugs/windows_port_-_git_annex_add_hangs_when_adding_17_files_at_once_or_more_.mdwn
+++ /dev/null
@@ -1,197 +0,0 @@
-### Please describe the problem.
-git annex add hangs on the windows port when adding many files at once. It seems like the magic number is 17. 17 and greater hangs
-
-Running in debug, it hangs on this:
-
-    [2013-06-14 13:59:46 Eastern Daylight Time] feed: git ["--git-dir=C:\\temp\\backup\\q10\\.git","--work-tree=C:\\temp\\backup\\q10","update-index","-z","--index-info"]
-
-
-### What steps will reproduce the problem?
-
-[[!format sh """
-git init t17
-cd t17
-git annex init
-for /l %a in (1,1,17) do @echo %a > %a.txt
-
-git annex add .
-add 1.txt (checksum...) ok
-add 10.txt (checksum...) ok
-add 11.txt (checksum...) ok
-add 12.txt (checksum...) ok
-add 13.txt (checksum...) ok
-add 14.txt (checksum...) ok
-add 15.txt (checksum...) ok
-add 16.txt (checksum...) ok
-add 17.txt (checksum...) ok
-add 2.txt (checksum...) ok
-add 3.txt (checksum...) ok
-add 4.txt (checksum...) ok
-add 5.txt (checksum...) ok
-add 6.txt (checksum...) ok
-add 7.txt (checksum...) ok
-add 8.txt (checksum...) ok
-add 9.txt (checksum...) ok
-(Recording state in git...)
-
-** gets stuck here
-
-"""]]
-
-### What version of git-annex are you using? On what operating system?
-
-	git-annex version: 4.20130601-gc01f842
-	build flags: Pairing Testsuite S3 WebDAV DNS
-	local repository version: 4
-	default repository version: 3
-	supported repository versions: 3 4
-	upgrade supported from repository versions: 2
-
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-** 16 works fine
-git init t16
-cd t16
-for /l %a in (1,1,16) do @echo %a > %a.txt
-git annex init
-git annex add .
-
-
-** not 17
-git init t18
-cd t18
-for /l %a in (1,1,17) do @echo %a > %a.txt
-
-C:\temp\backup\t18>git annex init
-init
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-ok
-(Recording state in git...)
-
-C:\temp\backup\t18>git annex add . --debug
-[2013-06-14 14:05:28 Eastern Daylight Time] read: git ["--git-dir=C:\\temp\\back
-up\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","ls-files","--others","--excl
-ude-standard","-z","--","."]
-[2013-06-14 14:05:28 Eastern Daylight Time] read: git ["--git-dir=C:\\temp\\back
-up\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","ls-files","--modified","-z",
-"--","."]
-[2013-06-14 14:05:28 Eastern Daylight Time] chat: git ["--git-dir=C:\\temp\\back
-up\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","cat-file","--batch"]
-add 1.txt [2013-06-14 14:05:28 Eastern Daylight Time] chat: git ["--git-dir=C:\\
-temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","check-attr","-z","
---stdin","annex.backend","annex.numcopies","--"]
-(checksum...) [2013-06-14 14:05:28 Eastern Daylight Time] chat: git ["--git-dir=
-C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","cat-file","--b
-atch"]
-[2013-06-14 14:05:28 Eastern Daylight Time] chat: git ["--git-dir=C:\\temp\\back
-up\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash-object","-t","blob","-w
-","--stdin"]
-ok
-add 10.txt (checksum...) [2013-06-14 14:05:28 Eastern Daylight Time] chat: git [
-"--git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","has
-h-object","-t","blob","-w","--stdin"]
-ok
-add 11.txt (checksum...) [2013-06-14 14:05:28 Eastern Daylight Time] chat: git [
-"--git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","has
-h-object","-t","blob","-w","--stdin"]
-ok
-add 12.txt (checksum...) [2013-06-14 14:05:28 Eastern Daylight Time] chat: git [
-"--git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","has
-h-object","-t","blob","-w","--stdin"]
-ok
-add 13.txt (checksum...) [2013-06-14 14:05:28 Eastern Daylight Time] chat: git [
-"--git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","has
-h-object","-t","blob","-w","--stdin"]
-ok
-add 14.txt (checksum...) [2013-06-14 14:05:28 Eastern Daylight Time] chat: git [
-"--git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","has
-h-object","-t","blob","-w","--stdin"]
-ok
-add 15.txt (checksum...) [2013-06-14 14:05:28 Eastern Daylight Time] chat: git [
-"--git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","has
-h-object","-t","blob","-w","--stdin"]
-ok
-add 16.txt (checksum...) [2013-06-14 14:05:28 Eastern Daylight Time] chat: git [
-"--git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","has
-h-object","-t","blob","-w","--stdin"]
-ok
-add 17.txt (checksum...) [2013-06-14 14:05:29 Eastern Daylight Time] chat: git [
-"--git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","has
-h-object","-t","blob","-w","--stdin"]
-ok
-add 2.txt (checksum...) [2013-06-14 14:05:29 Eastern Daylight Time] chat: git ["
---git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash
--object","-t","blob","-w","--stdin"]
-ok
-add 3.txt (checksum...) [2013-06-14 14:05:29 Eastern Daylight Time] chat: git ["
---git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash
--object","-t","blob","-w","--stdin"]
-ok
-add 4.txt (checksum...) [2013-06-14 14:05:29 Eastern Daylight Time] chat: git ["
---git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash
--object","-t","blob","-w","--stdin"]
-ok
-add 5.txt (checksum...) [2013-06-14 14:05:29 Eastern Daylight Time] chat: git ["
---git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash
--object","-t","blob","-w","--stdin"]
-ok
-add 6.txt (checksum...) [2013-06-14 14:05:29 Eastern Daylight Time] chat: git ["
---git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash
--object","-t","blob","-w","--stdin"]
-ok
-add 7.txt (checksum...) [2013-06-14 14:05:29 Eastern Daylight Time] chat: git ["
---git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash
--object","-t","blob","-w","--stdin"]
-ok
-add 8.txt (checksum...) [2013-06-14 14:05:29 Eastern Daylight Time] chat: git ["
---git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash
--object","-t","blob","-w","--stdin"]
-ok
-add 9.txt (checksum...) [2013-06-14 14:05:29 Eastern Daylight Time] chat: git ["
---git-dir=C:\\temp\\backup\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash
--object","-t","blob","-w","--stdin"]
-ok
-(Recording state in git...)
-[2013-06-14 14:05:29 Eastern Daylight Time] feed: git ["--git-dir=C:\\temp\\back
-up\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","update-index","-z","--index-
-info"]
-[2013-06-14 14:05:29 Eastern Daylight Time] chat: git ["--git-dir=C:\\temp\\back
-up\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","hash-object","-w","--stdin-p
-aths"]
-[2013-06-14 14:05:29 Eastern Daylight Time] feed: git ["--git-dir=C:\\temp\\back
-up\\t18\\.git","--work-tree=C:\\temp\\backup\\t18","update-index","-z","--index-
-info"]
-
-
-**gets stuck here and never finishes**
-
-
-# End of transcript or log.
-"""]]
-
-> Reproduced this, and git update-index was in fact not hanging. 
-> Instead, after that was done, it tried to stop the git hash-object
-> process, and this hung. 
-> 
-> It seems that the use of runInteractiveProcess is at fault somehow,
-> and I guess it must be due to it opening a pipe for stderr, which
-> I don't need or want. Perhaps I need to ensure I read from that pipe,
-> or windows keeps the process from terminating. (Unix would just toss the piped
-> data away.)
-> 
-> That was the only place runInteractiveProcess was used, so I replaced
-> it with an alternative that lets stderr be inherited. With this change,
-> I have successfully added 1000 files to the annex in one go, with no
-> hang. Provisionally [[done]]. --[[Joey]] 
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_.mdwn b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_.mdwn
deleted file mode 100644
index 76c05aa72..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_.mdwn
+++ /dev/null
@@ -1,559 +0,0 @@
-### Please describe the problem.
-
-Using a centralized remote repository, new files that are added to the repository after it's pulled cannot be directly accessed - instead are pulled as symlinks.
-
-The workaround is to create a new remote repository that clones from the source. That repo can pull all files correctly
-
-### What steps will reproduce the problem?
-
-The following script works fine when everything is run on a linux box. If the same script is run on the windows box, it will not show foo2.txt in the repository clone. foo.txt is still valid.
-
-a file, testrepo.sh is set up on the server to simplify the creation of the repo for testing
-
-**testrepo.sh**
-[[!format sh """
-
-rm -rf repo.git
-git init --bare repo.git
-cd repo.git
-git annex init origin
-git annex sync
-
-
-"""]]
-
-**test script**
-[[!format sh """
-
-ssh joebo@xxxxx sh testrepo.sh
-
-
-rm -rf repo
-git init repo
-cd repo
-
-git annex init
-git remote add origin ssh://joebo@xxxxx/~/repo.git
-echo hello > foo.txt
-git annex add .
-git commit -m "initial commit"
-git annex sync
-git annex copy --to origin
-git annex sync
-
-cd ..
-rm -rf repo-bak
-git init repo-bak
-cd repo-bak
-git remote add origin ssh://joebo@xxxxx/~/repo.git
-git fetch origin
-git merge origin/synced/master
-git annex sync
-git annex get .
-cat foo.txt #works just fine!
-
-cd ..
-cd repo
-echo foo2 > foo2.txt
-git annex add .
-git commit -m "another"
-git annex sync
-git annex copy --to origin
-git annex sync
-
-cd ..
-cd repo-bak
-git annex sync
-
-## throws a fastforward error:
-commit
-ok
-pull origin
-remote: Counting objects: 21, done.
-remote: Compressing objects: 100% (14/14), done.
-remote: Total 16 (delta 3), reused 0 (delta 0)
-Unpacking objects: 100% (16/16), done.
-From ssh://xxxx.com/~/repo
-   c5ed8e1..7ea5586  synced/git-annex -> origin/synced/git-annex
-   a8402ae..1a72b3d  synced/master -> origin/synced/master
-ok
-(merging origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 15, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (7/7), done.
-Writing objects: 100% (8/8), 844 bytes, done.
-Total 8 (delta 2), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   7ea5586..5df3c85  git-annex -> synced/git-annex
- ! [rejected]        master -> synced/master (non-fast-forward)
-error: failed to push some refs to 'ssh://joebo@xxx.com/~/repo.git'
-hint: Updates were rejected because a pushed branch tip is behind its remote
-hint: counterpart. Check out this branch and merge the remote changes
-hint: (e.g. 'git pull') before pushing again.
-hint: See the 'Note about fast-forwards' in 'git push --help' for details.
-failed
-git-annex: sync: 1 failed
-"""]]
-
-If I try to work around it by merging, then I get the symlink in the file after getting
-
-
-[[!format sh """
-
-C:\joe\backup\repo-bak>git merge origin/synced/master
-Updating f586b6a..fcae7bc
-Fast-forward
- foo2.txt | 1 +
- 1 file changed, 1 insertion(+)
- create mode 120000 foo2.txt
-
-C:\joe\backup\repo-bak>git annex get foo2.txt
-get foo2.txt (from origin...)
-SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bbece05f.txt
-
-           7 100%    6.84kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 30 bytes  received 156 bytes  124.00 bytes/sec
-total size is 7  speedup is 0.04
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo-bak\.git\annex\journa
-l\fba_8bb_SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bb
-ece05f.txt.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo-bak>cat foo2.txt
-.git/annex/objects/3V/kM/SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd
-78762e80a45f0bbece05f.txt/SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5cc
-d78762e80a45f0bbece05f.txt
-
-"""]]
-
-removing the backup repository and starting over works:
-
-[[!format sh """
-
-C:\joe\backup>git init repo-bak
-Initialized empty Git repository in C:/joe/backup/repo-bak/.git/
-
-C:\joe\backup>cd repo-bak
-
-C:\joe\backup\repo-bak>git remote add origin ssh://joebo@xxxx.com/~/repo.git
-
-C:\joe\backup\repo-bak>git fetch origin
-remote: Counting objects: 57, done.
-remote: Compressing objects: 100% (48/48), done.
-remote: Total 57 (delta 20), reused 0 (delta 0)
-Unpacking objects: 100% (57/57), done.
-From ssh://xxxx.com/~/repo
- * [new branch]      git-annex  -> origin/git-annex
- * [new branch]      synced/git-annex -> origin/synced/git-annex
- * [new branch]      synced/master -> origin/synced/master
-
-C:\joe\backup\repo-bak>git merge origin/synced/master
-
-C:\joe\backup\repo-bak>git annex sync
-
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-warning: LF will be replaced by CRLF in C:\joe\backup\repo-bak\.git\annex\journa
-l\uuid.log.
-The file will have its original line endings in your working directory.
-(merging origin/git-annex origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-commit
-ok
-pull origin
-ok
-push origin
-Counting objects: 9, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (4/4), done.
-Writing objects: 100% (5/5), 533 bytes, done.
-Total 5 (delta 3), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   5038806..67d6383  git-annex -> synced/git-annex
-ok
-
-C:\joe\backup\repo-bak>git annex get .
-get foo.txt (from origin...)
-SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691cd51a87.txt
-
-           8 100%    7.81kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 30 bytes  received 157 bytes  124.67 bytes/sec
-total size is 8  speedup is 0.04
-ok
-get foo2.txt (from origin...)
-SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bbece05f.txt
-
-           7 100%    6.84kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 30 bytes  received 156 bytes  124.00 bytes/sec
-total size is 7  speedup is 0.04
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo-bak\.git\annex\journa
-l\fba_8bb_SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bb
-ece05f.txt.log.
-The file will have its original line endings in your working directory.
-warning: LF will be replaced by CRLF in C:\joe\backup\repo-bak\.git\annex\journa
-l\ae4_1e9_SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691c
-d51a87.txt.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo-bak>cat *
-hello
-foo2
-
-C:\joe\backup\repo-bak>ls -lah
-total 5.0k
-drwxr-xr-x    1 jbogner  Administ        0 Jun 15 08:44 .
-drwxr-xr-x   23 jbogner  Administ     4.0k Jun 15 08:43 ..
-drwxr-xr-x    1 jbogner  Administ     4.0k Jun 15 08:44 .git
--rw-r--r--    1 jbogner  Administ        8 Jun 15 08:44 foo.txt
--rw-r--r--    1 jbogner  Administ        7 Jun 15 08:44 foo2.txt
-
-C:\joe\backup\repo-bak>
-
-"""]]
-
-### What version of git-annex are you using? On what operating system?
-
-Windows:
-
-	C:\joe\backup\repo-bak>git annex version
-	git-annex version: 4.20130614-g3a93e24
-	build flags: Pairing Testsuite S3 WebDAV DNS
-	local repository version: 4
-	default repository version: 3
-	supported repository versions: 3 4
-	upgrade supported from repository versions: 2
-
-
-Linux:
-
-        git-annex version: 4.20130531-g5df09b5
-	build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP
-
-
-### Please provide any additional information below.
-
-[[!format sh """
-# If you can, paste a complete transcript of the problem occurring here.
-# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
-
-C:\joe\backup>cd repo
-
-C:\joe\backup\repo>git annex init
-init
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\uu
-id.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo>git remote add origin ssh://joebo@xxxx.com/~/repo.git
-
-C:\joe\backup\repo>echo hello  1>foo.txt
-
-C:\joe\backup\repo>git annex add .
-add foo.txt (checksum...) ok
-(Recording state in git...)
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\ae
-4_1e9_SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691cd51a
-87.txt.log.
-The file will have its original line endings in your working directory.
-
-C:\joe\backup\repo>git commit -m "initial commit"
-[master (root-commit) 47c05ea] initial commit
- 1 file changed, 1 insertion(+)
- create mode 120000 foo.txt
-
-C:\joe\backup\repo>git annex sync
-commit
-ok
-pull origin
-warning: no common commits
-remote: Counting objects: 5, done.
-remote: Compressing objects: 100% (3/3), done.
-remote: Total 5 (delta 1), reused 0 (delta 0)
-Unpacking objects: 100% (5/5), done.
-From ssh://xxxx.com/~/repo
- * [new branch]      git-annex  -> origin/git-annex
-ok
-(merging origin/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 18, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (12/12), done.
-Writing objects: 100% (16/16), 1.40 KiB, done.
-Total 16 (delta 3), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
- * [new branch]      git-annex -> synced/git-annex
- * [new branch]      master -> synced/master
-ok
-
-C:\joe\backup\repo>git annex copy --to origin
-copy foo.txt (checking origin...) (to origin...)
-foo.txt
-           8 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 79 bytes  received 31 bytes  73.33 bytes/sec
-total size is 8  speedup is 0.07
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\ae
-4_1e9_SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691cd51a
-87.txt.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo>git annex sync
-commit
-ok
-pull origin
-ok
-push origin
-Counting objects: 9, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (4/4), done.
-Writing objects: 100% (5/5), 450 bytes, done.
-Total 5 (delta 1), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   bd52e5f..02a0a4a  git-annex -> synced/git-annex
-ok
-
-C:\joe\backup\repo>cd ..
-
-C:\joe\backup>rm -rf repo-bak
-
-C:\joe\backup>git init repo-bak
-Initialized empty Git repository in C:/joe/backup/repo-bak/.git/
-
-C:\joe\backup>cd repo-bak
-
-C:\joe\backup\repo-bak>git remote add origin ssh://joebo@xxxx.com/~/repo.git
-
-C:\joe\backup\repo-bak>git fetch origin
-remote: Counting objects: 25, done.
-remote: Compressing objects: 100% (19/19), done.
-remote: Total 25 (delta 6), reused 0 (delta 0)
-Unpacking objects: 100% (25/25), done.
-From ssh://xxxx.com/~/repo
- * [new branch]      git-annex  -> origin/git-annex
- * [new branch]      synced/git-annex -> origin/synced/git-annex
- * [new branch]      synced/master -> origin/synced/master
-
-C:\joe\backup\repo-bak>git merge origin/synced/master
-
-C:\joe\backup\repo-bak>git annex sync
-
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-warning: LF will be replaced by CRLF in C:\joe\backup\repo-bak\.git\annex\journa
-l\uuid.log.
-The file will have its original line endings in your working directory.
-(merging origin/git-annex origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-commit
-ok
-pull origin
-ok
-push origin
-Counting objects: 9, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (4/4), done.
-Writing objects: 100% (5/5), 610 bytes, done.
-Total 5 (delta 1), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   02a0a4a..88d19ce  git-annex -> synced/git-annex
-ok
-
-C:\joe\backup\repo-bak>git annex get .
-get foo.txt (from origin...)
-SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691cd51a87.txt
-
-           8 100%    7.81kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 30 bytes  received 157 bytes  124.67 bytes/sec
-total size is 8  speedup is 0.04
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo-bak\.git\annex\journa
-l\ae4_1e9_SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691c
-d51a87.txt.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo-bak>cat foo.txt
-hello
-
-C:\joe\backup\repo-bak>cd ..
-
-C:\joe\backup>cd repo
-
-C:\joe\backup\repo>echo foo2  1>foo2.txt
-
-C:\joe\backup\repo>git annex add .
-add foo2.txt (checksum...) ok
-(Recording state in git...)
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\fb
-a_8bb_SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bbece0
-5f.txt.log.
-The file will have its original line endings in your working directory.
-
-C:\joe\backup\repo>git commit -m "another"
-[master 76a9e44] another
- 1 file changed, 1 insertion(+)
- create mode 120000 foo2.txt
-
-C:\joe\backup\repo>git annex sync
-commit
-ok
-pull origin
-remote: Counting objects: 9, done.
-remote: Compressing objects: 100% (4/4), done.
-remote: Total 5 (delta 1), reused 0 (delta 0)
-Unpacking objects: 100% (5/5), done.
-From ssh://xxxx.com/~/repo
-   02a0a4a..88d19ce  synced/git-annex -> origin/synced/git-annex
-ok
-(merging origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 16, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (10/10), done.
-Writing objects: 100% (11/11), 1.11 KiB, done.
-Total 11 (delta 2), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   88d19ce..f47091a  git-annex -> synced/git-annex
-   47c05ea..76a9e44  master -> synced/master
-ok
-
-C:\joe\backup\repo>git annex copy --to origin
-copy foo.txt (checking origin...) ok
-copy foo2.txt (checking origin...) (to origin...)
-foo2.txt
-           7 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 79 bytes  received 31 bytes  73.33 bytes/sec
-total size is 7  speedup is 0.06
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\fb
-a_8bb_SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bbece0
-5f.txt.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo>git annex sync
-commit
-ok
-pull origin
-ok
-push origin
-Counting objects: 9, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (4/4), done.
-Writing objects: 100% (5/5), 477 bytes, done.
-Total 5 (delta 1), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   f47091a..98082cb  git-annex -> synced/git-annex
-ok
-
-C:\joe\backup\repo>cd ..
-
-C:\joe\backup>cd repo-bak
-
-C:\joe\backup\repo-bak>git annex sync
-commit
-ok
-pull origin
-remote: Counting objects: 21, done.
-remote: Compressing objects: 100% (14/14), done.
-remote: Total 16 (delta 4), reused 0 (delta 0)
-Unpacking objects: 100% (16/16), done.
-From ssh://xxxx.com/~/repo
-   88d19ce..98082cb  synced/git-annex -> origin/synced/git-annex
-   47c05ea..76a9e44  synced/master -> origin/synced/master
-ok
-(merging origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 15, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (7/7), done.
-Writing objects: 100% (8/8), 843 bytes, done.
-Total 8 (delta 2), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   98082cb..2537203  git-annex -> synced/git-annex
- ! [rejected]        master -> synced/master (non-fast-forward)
-error: failed to push some refs to 'ssh://joebo@xxxx.com/~/repo.git'
-hint: Updates were rejected because a pushed branch tip is behind its remote
-hint: counterpart. Check out this branch and merge the remote changes
-hint: (e.g. 'git pull') before pushing again.
-hint: See the 'Note about fast-forwards' in 'git push --help' for details.
-failed
-git-annex: sync: 1 failed
-
-C:\joe\backup\repo-bak>git annex get foo2.txt
-git-annex: foo2.txt not found
-
-C:\joe\backup\repo-bak>cat foo2.txt
-cat: foo2.txt: No such file or directory
-C:\joe\backup\repo-bak>git pull origin synced/master
-From ssh://xxxx.com/~/repo
- * branch            synced/master -> FETCH_HEAD
-Updating 47c05ea..76a9e44
-Fast-forward
- foo2.txt | 1 +
- 1 file changed, 1 insertion(+)
- create mode 120000 foo2.txt
-
-C:\joe\backup\repo-bak>git annex get foo2.txt
-get foo2.txt (from origin...)
-SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bbece05f.txt
-
-           7 100%    6.84kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 30 bytes  received 156 bytes  124.00 bytes/sec
-total size is 7  speedup is 0.04
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo-bak\.git\annex\journa
-l\fba_8bb_SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bb
-ece05f.txt.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo-bak>cat foo2.txt
-.git/annex/objects/3V/kM/SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd
-78762e80a45f0bbece05f.txt/SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5cc
-d78762e80a45f0bbece05f.txt
-C:\joe\backup\repo-bak>
-
-
-
-# End of transcript or log.
-"""]]
-
-> Apparently the last of the issues discussed here is fixed.
-> Closing this bug report before it grows a new issue. ;) [[done]] --[[Joey]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_10_b4f5e2d6a0d690f6b0089fa80a3c920b._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_10_b4f5e2d6a0d690f6b0089fa80a3c920b._comment
deleted file mode 100644
index 71cc02668..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_10_b4f5e2d6a0d690f6b0089fa80a3c920b._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA"
- nickname="Joe"
- subject="comment 10"
- date="2013-06-19T00:44:44Z"
- content="""
-The latest build is working again. Thanks!
-"""]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_1_c2092add1430667108a3fdc5e1c9b5f5._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_1_c2092add1430667108a3fdc5e1c9b5f5._comment
deleted file mode 100644
index 52bb21ae3..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_1_c2092add1430667108a3fdc5e1c9b5f5._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-06-15T18:50:45Z"
- content="""
-Joe, you need to carefully read [[direct_mode]]. When you manually run `git merge` in a direct mode repository, you defeat associated file tracking, with the resulting behavior you describe. This is why there is a [[todo/direct_mode_guard]] todo item.
-"""]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_2_f0ea453951daf84dbddc653ac64822b6._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_2_f0ea453951daf84dbddc653ac64822b6._comment
deleted file mode 100644
index 2c45f6b58..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_2_f0ea453951daf84dbddc653ac64822b6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA"
- nickname="Joe"
- subject="comment 2"
- date="2013-06-15T19:39:09Z"
- content="""
-joey, Thank you for the reply. I have read that and also read about the direct mode guard. I only used git merge because I was stuck and didn't know what else to do. I assume the proper way to refresh my backup repo is to git annex sync. That's what's failing with the non-fast-forward error. I don't know what to do from there. Thank you for any help.
-"""]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_3_35a8be5ecc9d1b72c38f8ddb47678160._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_3_35a8be5ecc9d1b72c38f8ddb47678160._comment
deleted file mode 100644
index c723d85bb..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_3_35a8be5ecc9d1b72c38f8ddb47678160._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA"
- nickname="Joe"
- subject="comment 3"
- date="2013-06-16T13:27:36Z"
- content="""
-Making some progress. It looks like it needs a .map file for the newly added file when I pull in the backup repo.  I'm tracing the various places addAssociatedFile gets called. It looks like sync should do it. I think that's what sets up the map. If I copy the map file from another repo, I'm able to call get annex get foo2.txt. So the key is getting that map file created.
-"""]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_4_29e72997b88f91f84639587b4cede34c._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_4_29e72997b88f91f84639587b4cede34c._comment
deleted file mode 100644
index c785ff77b..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_4_29e72997b88f91f84639587b4cede34c._comment
+++ /dev/null
@@ -1,76 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA"
- nickname="Joe"
- subject="comment 4"
- date="2013-06-16T17:27:18Z"
- content="""
-I have a workaround that requires a small patch. I'm not sure why it's not creating the mapping, but I noticed that git annex fsck has a verifyDirectMapping which will create the mapping if it doesn't exist. 
-
-git annex fsck will throw an error on fixLinks and won't proceed to verifyDirectMapping if the map file doesn't exist. So, I needed a way to call verifyDirectMapping directly. My hack is to add an argument to git annex fsck to call verifyDirectMapping. 
-
-My workflow is this:
-
-**repo1**:
-[[!format  sh \"\"\"
-echo a > new.txt
-git annex add .
-git commit -m \"add a\"
-git copy --to origin
-git annex sync
-\"\"\"]]
-
-**repo2**:
-[[!format  sh \"\"\"
-git annex sync
-git annex pull origin synced/master
-git annex fsck --verifyDirectMapping
-git annex get .
-\"\"\"]]
-
-The new file comes down cleanly.
-
-I'm sure there's a better way to do this to fix the core issue, but here's how I patched Fsck.hs as a minimal workaround
-
-[[!format  diff \"\"\"
-
-diff --git a/Command/Fsck.hs b/Command/Fsck.hs
-old mode 100644
-new mode 100755
-index 9af6a4a..97aabb8
---- a/Command/Fsck.hs
-+++ b/Command/Fsck.hs
-@@ -59,12 +60,16 @@ incrementalScheduleOption :: Option
- incrementalScheduleOption = Option.field [] \"incremental-schedule\" paramTime
- 	\"schedule incremental fscking\"
- 
-+verifyDirectMappingOption :: Option
-+verifyDirectMappingOption = Option.flag [] \"verifyDirectMapping\" \"verifies direct mappings are consistent\"
-+
- options :: [Option]
- options = 
- 	[ fromOption
- 	, startIncrementalOption
- 	, moreIncrementalOption
- 	, incrementalScheduleOption
-+	, verifyDirectMappingOption
- 	]
- 
- seek :: [CommandSeek]
-@@ -107,18 +112,23 @@ withIncremental = withValue $ do
- start :: Maybe Remote -> Incremental -> FilePath -> (Key, Backend) -> CommandStart
- start from inc file (key, backend) = do
- 	numcopies <- numCopies file
--	case from of
--		Nothing -> go $ perform key file backend numcopies
--		Just r -> go $ performRemote key file backend numcopies r
-+	verify <- Annex.getFlag (Option.name verifyDirectMappingOption)
-+	if verify
-+		then go $ verifyDirectMapping key file
-+		else
-+			case from of
-+				Nothing -> go $ perform key file backend numcopies
-+				Just r -> go $ performRemote key file backend numcopies r
-
-
-\"\"\"]]
-"""]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_5_2de7f6532de4cbc21737ce53a89d6525._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_5_2de7f6532de4cbc21737ce53a89d6525._comment
deleted file mode 100644
index a08bd2899..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_5_2de7f6532de4cbc21737ce53a89d6525._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 5"
- date="2013-06-18T00:09:58Z"
- content="""
-I have followed the transcript (on my linux system), and cannot reproduce the non-fast-forward problem.
-
-What error does fsck throw in fixLink?
-"""]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_6_80d130b5af829763be77c61a9c5ca306._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_6_80d130b5af829763be77c61a9c5ca306._comment
deleted file mode 100644
index 6c05e5665..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_6_80d130b5af829763be77c61a9c5ca306._comment
+++ /dev/null
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA"
- nickname="Joe"
- subject="comment 6"
- date="2013-06-18T00:25:53Z"
- content="""
-The transcript also works fine on my linux machine.
-
-This is the git annex fsck error:
-
-[[!format sh \"\"\"
-
-(fixing content location) looking for mapping\"C:\\joe\\backup\\repo-bak\\.git\\a
-nnex\\objects\\fba\\8bb\\SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd
-78762e80a45f0bbece05f.txt\\SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5c
-cd78762e80a45f0bbece05f.txt.map\"
-
-git-annex: C:\joe\backup\repo-bak\.git/annex/objects/3V/kM/SHA256E-s7--eef0e2920
-0a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bbece05f.txt/SHA256E-s7--eef0e292
-00a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bbece05f.txt: renameFile: does n
-ot exist (No such file or directory)
-failed
-git-annex: fsck: 1 failed
-
-
-\"\"\"]]
-
-As such it can't get to verifyDirectMapping to corrrect the missing mapping
-"""]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_7_ec199db851952b40e8b18922da574ea4._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_7_ec199db851952b40e8b18922da574ea4._comment
deleted file mode 100644
index 9f5dc052d..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_7_ec199db851952b40e8b18922da574ea4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 7"
- date="2013-06-18T01:38:05Z"
- content="""
-There were at least 4 windows port bugs here. (Including `git annex sync` not committing on Windows, I think!) Should now have fixed them all. This includes fixing my earlier fix to make git annex sync push to master in a bare repository, which was not working on Windows.
-"""]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_8_d269fcadea9d5a668e3c6d6cf019f56a._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_8_d269fcadea9d5a668e3c6d6cf019f56a._comment
deleted file mode 100644
index feda63b4a..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_8_d269fcadea9d5a668e3c6d6cf019f56a._comment
+++ /dev/null
@@ -1,353 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA"
- nickname="Joe"
- subject="comment 8"
- date="2013-06-18T02:14:01Z"
- content="""
-Thanks joey - I pulled the latest and built it. I don't think everything is working, or maybe my steps need to be updated. On the positive side, git annex fsck no longer errors out. However, I still get the fast-forward message and get annex get . gives me an error about repositories not being available.
-
-This is running my test script:
-
-[[!format sh \"\"\"
-
-C:\joe\backup>ssh joebo@xxxx.com sh testrepo.sh
-Initialized empty Git repository in /home/joebo/repo.git/
-init origin ok
-(Recording state in git...)
-commit
-ok
-git-annex: no branch is checked out
-
-C:\joe\backup>rm -rf repo
-
-C:\joe\backup>git init repo
-Initialized empty Git repository in C:/joe/backup/repo/.git/
-
-C:\joe\backup>cd repo
-
-C:\joe\backup\repo>git annex init
-init
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\uu
-id.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo>git remote add origin ssh://joebo@xxxx.com/~/repo.git
-
-C:\joe\backup\repo>echo hello  1>foo.txt
-
-C:\joe\backup\repo>git annex add .
-add foo.txt (checksum...) ok
-(Recording state in git...)
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\ae
-4_1e9_SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691cd51a
-87.txt.log.
-The file will have its original line endings in your working directory.
-
-C:\joe\backup\repo>git commit -m \"initial commit\"
-[master (root-commit) 4450966] initial commit
- 1 file changed, 1 insertion(+)
- create mode 120000 foo.txt
-
-C:\joe\backup\repo>git annex sync
-commit
-ok
-pull origin
-warning: no common commits
-remote: Counting objects: 5, done.
-remote: Compressing objects: 100% (3/3), done.
-remote: Total 5 (delta 1), reused 0 (delta 0)
-Unpacking objects: 100% (5/5), done.
-From ssh://xxxx.com/~/repo
- * [new branch]      git-annex  -> origin/git-annex
-ok
-(merging origin/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 18, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (12/12), done.
-Writing objects: 100% (16/16), 1.41 KiB, done.
-Total 16 (delta 3), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
- * [new branch]      git-annex -> synced/git-annex
- * [new branch]      master -> synced/master
-ok
-
-C:\joe\backup\repo>git annex copy --to origin
-copy foo.txt (checking origin...) (to origin...)
-foo.txt
-           8 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 79 bytes  received 31 bytes  31.43 bytes/sec
-total size is 8  speedup is 0.07
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\ae
-4_1e9_SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691cd51a
-87.txt.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo>git annex sync
-commit
-ok
-pull origin
-remote: Counting objects: 6, done.
-remote: Compressing objects: 100% (4/4), done.
-remote: Total 5 (delta 0), reused 0 (delta 0)
-Unpacking objects: 100% (5/5), done.
-From ssh://xxxx.com/~/repo
-   dd2afc8..fcccfa3  git-annex  -> origin/git-annex
-ok
-(merging origin/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 21, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (9/9), done.
-Writing objects: 100% (11/11), 896 bytes, done.
-Total 11 (delta 4), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   a093010..10a7c3a  git-annex -> synced/git-annex
-ok
-
-C:\joe\backup\repo>git push origin master
-Everything up-to-date
-
-C:\joe\backup\repo>cd ..
-
-C:\joe\backup>rm -rf repo-bak
-
-C:\joe\backup>git init repo-bak
-Initialized empty Git repository in C:/joe/backup/repo-bak/.git/
-
-C:\joe\backup>cd repo-bak
-
-C:\joe\backup\repo-bak>git remote add origin ssh://joebo@xxxx.com/~/repo.git
-
-C:\joe\backup\repo-bak>git fetch origin
-remote: Counting objects: 36, done.
-remote: Compressing objects: 100% (28/28), done.
-remote: Total 36 (delta 11), reused 0 (delta 0)
-Unpacking objects: 100% (36/36), done.
-From ssh://xxxx.com/~/repo
- * [new branch]      git-annex  -> origin/git-annex
- * [new branch]      master     -> origin/master
- * [new branch]      synced/git-annex -> origin/synced/git-annex
- * [new branch]      synced/master -> origin/synced/master
-
-C:\joe\backup\repo-bak>git merge origin/synced/master
-
-C:\joe\backup\repo-bak>git annex sync
-
-  Detected a crippled filesystem.
-
-  Enabling direct mode.
-
-  Detected a filesystem without fifo support.
-
-  Disabling ssh connection caching.
-warning: LF will be replaced by CRLF in C:\joe\backup\repo-bak\.git\annex\journa
-l\uuid.log.
-The file will have its original line endings in your working directory.
-(merging origin/git-annex origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-commit
-ok
-pull origin
-ok
-push origin
-Counting objects: 18, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (6/6), done.
-Writing objects: 100% (8/8), 695 bytes, done.
-Total 8 (delta 4), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   10a7c3a..dbf4a72  git-annex -> synced/git-annex
-ok
-
-C:\joe\backup\repo-bak>git annex get .
-get foo.txt (not available)
-  Try making some of these repositories available:
-        608d7025-8d33-459e-875b-84de43946980
-        608d7025-8d33-459e-875b-84de43946980
-        def09afe-da97-4f07-ae90-90ea116eb8c4
-failed
-git-annex: get: 1 failed
-
-C:\joe\backup\repo-bak>cat foo.txt
-.git/annex/objects/6k/Mf/SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf5
-32b064df4bc691cd51a87.txt/SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf
-532b064df4bc691cd51a87.txt
-C:\joe\backup\repo-bak>cd ..
-
-C:\joe\backup>cd repo
-
-C:\joe\backup\repo>echo foo2  1>foo2.txt
-
-C:\joe\backup\repo>git annex add .
-add foo2.txt (checksum...) ok
-(Recording state in git...)
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\fb
-a_8bb_SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bbece0
-5f.txt.log.
-The file will have its original line endings in your working directory.
-
-C:\joe\backup\repo>git commit -m \"another\"
-[master 438409c] another
- 1 file changed, 1 insertion(+)
- create mode 120000 foo2.txt
-
-C:\joe\backup\repo>git annex sync
-commit
-ok
-pull origin
-remote: Counting objects: 18, done.
-remote: Compressing objects: 100% (6/6), done.
-remote: Total 8 (delta 4), reused 0 (delta 0)
-Unpacking objects: 100% (8/8), done.
-From ssh://xxxx.com/~/repo
-   10a7c3a..dbf4a72  synced/git-annex -> origin/synced/git-annex
-ok
-(merging origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 25, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (12/12), done.
-Writing objects: 100% (14/14), 1.32 KiB, done.
-Total 14 (delta 3), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   dbf4a72..79c01f2  git-annex -> synced/git-annex
-   4450966..438409c  master -> synced/master
-ok
-
-C:\joe\backup\repo>git annex copy --to origin
-copy foo.txt (checking origin...) ok
-copy foo2.txt (checking origin...) (to origin...)
-foo2.txt
-           7 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
-
-sent 79 bytes  received 31 bytes  220.00 bytes/sec
-total size is 7  speedup is 0.06
-ok
-warning: LF will be replaced by CRLF in C:\joe\backup\repo\.git\annex\journal\fb
-a_8bb_SHA256E-s7--eef0e29200a3194851e5fb4ff77d0d0aec5cd3f5ccd78762e80a45f0bbece0
-5f.txt.log.
-The file will have its original line endings in your working directory.
-(Recording state in git...)
-
-C:\joe\backup\repo>git annex sync
-commit
-ok
-pull origin
-remote: Counting objects: 6, done.
-remote: Compressing objects: 100% (4/4), done.
-remote: Total 5 (delta 0), reused 0 (delta 0)
-Unpacking objects: 100% (5/5), done.
-From ssh://xxxx.com/~/repo
-   fcccfa3..eb065b0  git-annex  -> origin/git-annex
-ok
-(merging origin/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 33, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (13/13), done.
-Writing objects: 100% (17/17), 1.27 KiB, done.
-Total 17 (delta 8), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   79c01f2..7ecf368  git-annex -> synced/git-annex
-ok
-
-C:\joe\backup\repo>cd ..
-
-C:\joe\backup>cd repo-bak
-
-C:\joe\backup\repo-bak>git annex sync
-commit
-ok
-pull origin
-remote: Counting objects: 52, done.
-remote: Compressing objects: 100% (29/29), done.
-remote: Total 36 (delta 13), reused 0 (delta 0)
-Unpacking objects: 100% (36/36), done.
-From ssh://xxxx.com/~/repo
-   fcccfa3..eb065b0  git-annex  -> origin/git-annex
-   4450966..438409c  master     -> origin/master
-   dbf4a72..7ecf368  synced/git-annex -> origin/synced/git-annex
-   4450966..438409c  synced/master -> origin/synced/master
-ok
-(merging origin/git-annex origin/synced/git-annex into git-annex...)
-(Recording state in git...)
-push origin
-Counting objects: 30, done.
-Delta compression using up to 4 threads.
-Compressing objects: 100% (7/7), done.
-Writing objects: 100% (9/9), 732 bytes, done.
-Total 9 (delta 5), reused 0 (delta 0)
-To ssh://joebo@xxxx.com/~/repo.git
-   7ecf368..7895f60  git-annex -> synced/git-annex
- ! [rejected]        master -> synced/master (non-fast-forward)
-error: failed to push some refs to 'ssh://joebo@xxxx.com/~/repo.git'
-hint: Updates were rejected because a pushed branch tip is behind its remote
-hint: counterpart. Check out this branch and merge the remote changes
-hint: (e.g. 'git pull') before pushing again.
-hint: See the 'Note about fast-forwards' in 'git push --help' for details.
-failed
-git-annex: sync: 1 failed
-
-C:\joe\backup\repo-bak>git pull origin synced/master
-From ssh://xxxx.com/~/repo
- * branch            synced/master -> FETCH_HEAD
-Updating 4450966..438409c
-Fast-forward
- foo2.txt | 1 +
- 1 file changed, 1 insertion(+)
- create mode 120000 foo2.txt
-
-C:\joe\backup\repo-bak>git annex sync
-commit
-ok
-pull origin
-ok
-push origin
-Everything up-to-date
-ok
-
-C:\joe\backup\repo-bak>cat foo.txt
-.git/annex/objects/6k/Mf/SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf5
-32b064df4bc691cd51a87.txt/SHA256E-s8--f873eef4f852e335da367d76ce7f1973c15b8ffebf
-532b064df4bc691cd51a87.txt
-C:\joe\backup\repo-bak>git annex get foo.txt
-get foo.txt (not available)
-  Try making some of these repositories available:
-        608d7025-8d33-459e-875b-84de43946980
-        608d7025-8d33-459e-875b-84de43946980
-        608d7025-8d33-459e-875b-84de43946980
-        608d7025-8d33-459e-875b-84de43946980
-        def09afe-da97-4f07-ae90-90ea116eb8c4
-        def09afe-da97-4f07-ae90-90ea116eb8c4
-failed
-git-annex: get: 1 failed
-
-C:\joe\backup\repo-bak>
-C:\joe\backup\repo-bak>git annex fsck foo.txt
-fsck foo.txt ok
-
-C:\joe\backup\repo-bak>
-
-\"\"\"]]
-
-Perhaps I need to change my transcript to reflect the new fixes?
-
-Reverting back to my patched version, I can run the script and run git annex fsck --verifyDirectMapping and get the file cleanly. Do I need to update the server version? (I assume not)
-"""]]
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_9_908d1b981d56107f29d8972bf11aefc8._comment b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_9_908d1b981d56107f29d8972bf11aefc8._comment
deleted file mode 100644
index 0f9eaeb6f..000000000
--- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_/comment_9_908d1b981d56107f29d8972bf11aefc8._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA"
- nickname="Joe"
- subject="comment 9"
- date="2013-06-18T09:58:41Z"
- content="""
-The regression appears to behere: $ git diff d80a0f62a4aa5a2a3566f29dd6bda619b1a7eabd..64f8819ae47cc27b164eb69aa846dfb0f7cc6ef3 Process.hs
-
-I rewound each commit until I no longer had the regression. This commit was clean: d80a0f62a4aa5a2a3566f29dd6bda619b1a7eabd. Something with the changes to Process.hs is causing my error.
-
-I validated by building using git checkout d80a0f62a4aa5a2a3566f29dd6bda619b1a7eabd Process.hs and the error went away.
-"""]]
diff --git a/doc/bugs/wrong_program_path_in___126____47__.config__47__git-annex__47__program.mdwn b/doc/bugs/wrong_program_path_in___126____47__.config__47__git-annex__47__program.mdwn
deleted file mode 100644
index d145fa6e6..000000000
--- a/doc/bugs/wrong_program_path_in___126____47__.config__47__git-annex__47__program.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-## What steps will reproduce the problem?
-
-install the latest linux snapshot of git-annex (https://downloads.kitenet.net/git-annex/linux/3.20121127/git-annex-standalone-amd64.tar.gz)
-
-## What is the expected output? What do you see instead?
-
-I would expect `~/.config/git-annex/program` to contain `/home/thedward/tmp/git-annex.linux/runshell`
-
-Instead it contains `/home/thedward/tmp/git-annex.linuxrunshell`, which causes a problem next time I start the webapp (unless I manually fix it first).
-
-## What version of git-annex are you using? On what operating system?
-
-git-annex=3.20121127 on Ubuntu 12.04 LTS
-
-
-## Please provide any additional information below.
-
-Otherwise it is working great. 
-
-> I've fixed this. [[done]] --[[Joey]] 
diff --git a/doc/bugs/wrong_program_path_in___126____47__.config__47__git-annex__47__program/comment_1_44c11918d00ead38d40556aade98c0af._comment b/doc/bugs/wrong_program_path_in___126____47__.config__47__git-annex__47__program/comment_1_44c11918d00ead38d40556aade98c0af._comment
deleted file mode 100644
index 297eea157..000000000
--- a/doc/bugs/wrong_program_path_in___126____47__.config__47__git-annex__47__program/comment_1_44c11918d00ead38d40556aade98c0af._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkvSZ1AFJdY_1FeutZr_KWeqtzjZta1PNE"
- nickname="Thedward"
- subject="comment 1"
- date="2012-11-28T22:14:12Z"
- content="""
-Sweet!
-
-That's the fastest I've ever had a bug I reported closed. 
-
-Thanks for all your hard work on this. :-)
-"""]]
diff --git a/doc/bugs/xdg-user-dir_error.mdwn b/doc/bugs/xdg-user-dir_error.mdwn
deleted file mode 100644
index 5a8ed52d7..000000000
--- a/doc/bugs/xdg-user-dir_error.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-Run *git annex webapp* in Debian Sid with KDE.
-
-It opens the web browser with this error: **Internal Server Error** *xdg-user-dir ["DESKTOP"] exited 127*.
-
-I've tried to changing the xdg-user-dir config with no success.
-
-> This is fixed in my master branch. Workaround: Install the xdg-user-dirs
-> package. [[done]] --[[Joey]]
diff --git a/doc/bugs/xmpp_needs_one_account_per_distinct_repository.mdwn b/doc/bugs/xmpp_needs_one_account_per_distinct_repository.mdwn
deleted file mode 100644
index c917cc3d2..000000000
--- a/doc/bugs/xmpp_needs_one_account_per_distinct_repository.mdwn
+++ /dev/null
@@ -1,107 +0,0 @@
-The way [[XMPP pairing|design/assistant/XMPP]] currently works, each
-separate repository needs to use a different XMPP account. If two
-repositories use the same XMPP account, then they will be combined together
-when XMPP pairing takes place.
-
-There are two different UIs for XMPP pairing. While the same protocol
-is running behind the scenes, these UIs should be considered separately.
-
-## Share with your other devices
-
-Here, I think it makes sense to require the user to use the same XMPP
-account on all their devices (otherwise it's pairing with a friend), and
-automatically combine repositories of devices that use the same XMPP
-account.
-
-The UI is pretty clear about this:
-
-	If you have multiple devices, all running git-annex, and using #
-	your Jabber account #{account}, you can configure them to share #
-	your files between themselves.
-
-Doing it this way avoids needing to confirm pair requests coming from the same
-XMPP account. Which means that, for example, you can have a device at home,
-and one at work, and pair them by simply initiating a pair request from one
-to the other. You don't have to travel between home and work to confirm 
-the request.
-
-(Also, when you have a lot of devices, this avoids a combinatorial explosion
-of pair request confirmations.)
-
-The only problem with this is that users who want multiple repositories
-need to find multiple XMPP accounts. However, I'm inclined to think this is
-a reasonable requirement.
-
-## Share with a friend
-
-Suppose that Alice wants to share with Bob. Bob is using the same XMPP
-account for two separate repositories (B1 and B2), that are not
-themselves paired.
-
-When Alice chooses to share with Bob, a XMPP pair request is sent.
-Both of Bob's repositories see it, and both ask him to confirm.
-Bob can choose to only confirm the request in B1, and 
-not in B2. This should work ok.
-
-* The UI for this only says "Pair request received from #{name}",
-  it does not indicate which repository of Alice's is being paired
-  with. This could be improved. If Alice has two repositories as well,
-  she and Bob will want to coordinate pairing the right ones together.
-  Could be fixed by just displaying the description of Alice's repository
-  to Bob.
-
------
-
-Now, suppose that Alice makes a second, distinct repository (A2),
-and chooses to share it with Bob (intending to share with B2). This
-sends an XMPP pair request to both of Bob's repositories.
-
-B1 has already paired with Alice, so it assumes this
-new pair request is from a different device belonging to Alice, and it
-automatically ACKs the pair request. 
-
-The result is that Alice's new A2 repository combines with B1,
-which is already combined with A1. Effectively combining all of A1, A2, B1,
-and B2, unexpectedly. **This is a bug**.
-
-Some possible fixes:
-
-1. Stop auto-accepting pair requests
-   from friends we're already paired with. Require another confirmation.
-2. Or, only auto-accept pair requests from friends we're already paired with
-   when they come from a repository whose UUID we already know. This
-   enhancment to fix #1 makes it easier to build more robust networks of
-   repositories. **done**
-
-Hmm, I don't think those fixes are sufficient. Suppose they're in place.
-Then when Alice shares A2 with Bob, both his repositories will ask him to
-confirm the pair request. He confirms in B2, and pairing proceeds.
-
-But, XMPP git push is broadcast to all clients of an XMPP account.
-So when B2 sends a push, A1 sees it, and happily merges away. The
-repositories still combine!
-
-So, we need another fix:
-
-* Send UUID in XMPP git push protocol messages. Only respond to git push
-  messages from a known UUID, and ignore all others. (XMPP pairing
-  already sends the UUID, so it will be known.) **done**
-
-----
-
-* Alternatively, we could say that the problem is that Bob has two 
-  distinct repositories using the same XMPP account, and try to prevent
-  him from doing that in the first place. 
-   
-  One way to do this would be, when configuring the
-  XMPP account, scan for other repositories using the same account, and
-  don't let it be used unless the user confirms they want to pair them.
-  But, this doesn't seem viable because if the other repository is on
-  another device, which is turned off, this check wouldn't see it.
-
-  Or there could be a warning about account reuse. Doesn't seem likely to
-  be effective.
-
------
-
-> [[done]]. I've put in the fixes around pairing with friends. --[[Joey]]
diff --git a/doc/bugs/xmpp_needs_one_account_per_distinct_repository/comment_1_820732c4dcb15186b4f635c50fdb0805._comment b/doc/bugs/xmpp_needs_one_account_per_distinct_repository/comment_1_820732c4dcb15186b4f635c50fdb0805._comment
deleted file mode 100644
index eec708362..000000000
--- a/doc/bugs/xmpp_needs_one_account_per_distinct_repository/comment_1_820732c4dcb15186b4f635c50fdb0805._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="fmarier"
- ip="121.98.93.240"
- subject="My current XMPP setup"
- date="2013-04-28T22:16:50Z"
- content="""
-Here's the way I currently use XMPP (Google Talk) on my devices:
-
-* I have a separate XMPP/Google account on each device (device1@gmail.com, device2@gmail.com, etc.). I keep them separate to protect the credentials of the other devices in case I lose one of the devices.
-* I setup git-annex to sync with a \"friend\" and have device1@gmail.com and device2@gmail.com sync with each other.
-
-I have three different repositories I'd like to manage with git-annex assistant:
-
- * R1: things I want everywhere
- * R2: things I only want on personal laptop and desktop
- * R3: things I only want on personal and work laptops
-
-So it would be great if there was a way to easily keep things separate.
-"""]]
diff --git a/doc/bugs/yesod-default_is_needed_as_a_dependancy.mdwn b/doc/bugs/yesod-default_is_needed_as_a_dependancy.mdwn
deleted file mode 100644
index 28727f97f..000000000
--- a/doc/bugs/yesod-default_is_needed_as_a_dependancy.mdwn
+++ /dev/null
@@ -1,10 +0,0 @@
-Seems like there is a needed dependancy, yesod-default is needed on OSX.
-
-<pre>
-Utility/Yesod.hs:10:8:
-    Could not find module `Yesod.Default.Util'
-    Use -v to see a list of the files searched for.
-make: *** [git-annex] Error 1
-</pre>
-
-> Only on OSX apparently. Weird. Added. [[done]] --[[Joey]] 
diff --git a/doc/bugs/yesod-form_missing.mdwn b/doc/bugs/yesod-form_missing.mdwn
deleted file mode 100644
index ad92bd040..000000000
--- a/doc/bugs/yesod-form_missing.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-What steps will reproduce the problem?
-
-build using cabal from a git checkout
-
-What is the expected output? What do you see instead?
-
-successful build; error message is:
-
-Assistant/WebApp/Form.hs:15:8:
-    Could not find module `Yesod.Form.Fields'
-    It is a member of the hidden package `yesod-form-1.2.0'.
-    Perhaps you need to add `yesod-form' to the build-depends in your .cabal file.
-
-
-What version of git-annex are you using? On what operating system?
-
-git checkout commit 90b62db1defdd223294935ec0bbaac883cd20c04 on OS X Lion
-
-Please provide any additional information below.
-
-adding yesod-form to the build depends in git-annex.cabal does indeed fix the problem!
-
-> [[done]] --[[Joey]] 
diff --git a/doc/todo/Allow_syncing_only_selected_branches.mdwn b/doc/todo/Allow_syncing_only_selected_branches.mdwn
deleted file mode 100644
index 78766e4df..000000000
--- a/doc/todo/Allow_syncing_only_selected_branches.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-It seems that currently, syncing will result in every branch winding
-up everywhere within the network of git annex nodes. It would be great
-if one could keep some branches purely local.
-
-The «fetch» part of «sync» seems to respect the fetch refspec in the
-git config, but the push part seems to always push everything.
-
-> [[done]]
diff --git a/doc/todo/Allow_syncing_only_selected_branches/comment_1_bb687b1a50d8a926abd16ada639140e1._comment b/doc/todo/Allow_syncing_only_selected_branches/comment_1_bb687b1a50d8a926abd16ada639140e1._comment
deleted file mode 100644
index 00f18cf72..000000000
--- a/doc/todo/Allow_syncing_only_selected_branches/comment_1_bb687b1a50d8a926abd16ada639140e1._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 1"
- date="2014-05-15T19:51:48Z"
- content="""
-No, it does not:
-
-<pre>
-push wren 
-[2014-05-15 15:50:33 JEST] call: git [\"--git-dir=/home/joey/lib/big/.git\",\"--work-tree=/home/joey/lib/big\",\"push\",\"wren\",\"+git-annex:synced/git-annex\",\"master:synced/master\"]
-[2014-05-15 15:50:39 JEST] read: git [\"--git-dir=/home/joey/lib/big/.git\",\"--work-tree=/home/joey/lib/big\",\"push\",\"wren\",\"master\"]
-</pre>
-
-That is the entirity of what's pushed: The git-annex branch, and the currently checked out branch. 
-
-I don't see a bug here.
-"""]]
diff --git a/doc/todo/Allow_syncing_only_selected_branches/comment_2_46d27fe74b4adac2e740fa555f549459._comment b/doc/todo/Allow_syncing_only_selected_branches/comment_2_46d27fe74b4adac2e740fa555f549459._comment
deleted file mode 100644
index 49b939f13..000000000
--- a/doc/todo/Allow_syncing_only_selected_branches/comment_2_46d27fe74b4adac2e740fa555f549459._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="zardoz"
- ip="92.227.51.179"
- subject="comment 2"
- date="2014-05-16T08:40:47Z"
- content="""
-Joey, thanks for clearing that up. In my test-case I only had two
-branches, and I mistook it for pushing everything. Actually, what I
-wanted to achieve was the following:
-
-Have a main repo M with branches A and A-downstream, and have a
-downstream repo D with just A-downstream. What confused me was that
-the main repo always pushed A to D. I suppose if I just have the two
-branches, I would achieve the desired effect by not using «annex
-sync», and instead just pushing the git-annex branch manually; would
-that be the way to go?
-
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM.mdwn b/doc/todo/Build_for_Synology_DSM.mdwn
deleted file mode 100644
index 650500756..000000000
--- a/doc/todo/Build_for_Synology_DSM.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-It would be wonderful if a pre-built package would be available for Synology NAS. Basically, this is an ARM-based Linux. It has most of the required shell commands either out of the box or easily available (through ipkg). But I think it would be difficult to install the Haskell compiler and all the required modules, so it would probably be better to cross-compile targeting ARM.
-
-> [[done]]; the standalone armel tarball has now been tested working on
-> Synology. --[[Joey]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_10_e351084d9a83db3fd6d9d983227a6410._comment b/doc/todo/Build_for_Synology_DSM/comment_10_e351084d9a83db3fd6d9d983227a6410._comment
deleted file mode 100644
index b62a929d7..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_10_e351084d9a83db3fd6d9d983227a6410._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA"
- nickname="Franck"
- subject="comment 10"
- date="2013-06-02T17:23:43Z"
- content="""
-I updated the C program to simplify it so it uses a static path for `_chrooter`. In the previous version, I suspect that one can play with symlinks and use it to get a root shell. So, if `_chrooter` is not installed in `/opt/bin` this file has to be edited too before compilation.
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_11_cc67a584f5c460a6fb63cf099c20e573._comment b/doc/todo/Build_for_Synology_DSM/comment_11_cc67a584f5c460a6fb63cf099c20e573._comment
deleted file mode 100644
index 324fa8423..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_11_cc67a584f5c460a6fb63cf099c20e573._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA"
- nickname="Franck"
- subject="comment 11"
- date="2013-06-03T09:55:54Z"
- content="""
-A last update and I stop spamming this thread: I've implemented access control and simplified customisation. All this has been moved to https://bitbucket.org/franckp/gasp 
-
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_12_94023593d294b9cf69090fcfd6ca0e5a._comment b/doc/todo/Build_for_Synology_DSM/comment_12_94023593d294b9cf69090fcfd6ca0e5a._comment
deleted file mode 100644
index 39c243ec4..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_12_94023593d294b9cf69090fcfd6ca0e5a._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlJEI45rGczFAnuM7gRSj4C6s9AS9yPZDc"
- nickname="Kevin"
- subject="SynoCommunity"
- date="2013-06-26T18:12:39Z"
- content="""
-Creating an installable git-annex package available via [SynoCommunity](http://www.synocommunity.com/) would be awesome.  They have created [cross-compilation tools](https://github.com/SynoCommunity/spksrc) to help build the packages and integrate the start/stop scripts with the package manager.
-
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_13_314255fd503d125b5aeae2f62acfd592._comment b/doc/todo/Build_for_Synology_DSM/comment_13_314255fd503d125b5aeae2f62acfd592._comment
deleted file mode 100644
index 3c54a9271..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_13_314255fd503d125b5aeae2f62acfd592._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnrP-0DGtHDJbWSXeiyk0swNkK1aejoN3c"
- nickname="sebastien"
- subject="comment 13"
- date="2013-08-06T12:18:35Z"
- content="""
-I post an issue to github synocommunity for that, i hope somenone have some time to package this great features.
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_15_9525cd0d75ff4c15182d10a855774b69._comment b/doc/todo/Build_for_Synology_DSM/comment_15_9525cd0d75ff4c15182d10a855774b69._comment
deleted file mode 100644
index c3edf99e2..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_15_9525cd0d75ff4c15182d10a855774b69._comment
+++ /dev/null
@@ -1,30 +0,0 @@
-[[!comment format=mdwn
- username="lorenzo"
- ip="84.75.27.69"
- subject="Running Debian squeeze binaries on libc 2.5 based NAS"
- date="2013-10-27T23:56:26Z"
- content="""
-Following the suggestions in this page I tried to run the binaries that debian provides on my Lacie NetworkSpace which is another one of these NAS devices with old libc. After uploading the binaries and required libraries and using `LD_LIBRARY_PATH` to force the loader to use the version I uploaded of the libraries I was still having a segfault (similar to what Franck was experiencing) while running git-annex in a chroot was working.
-
-It turns out that it is possible to solve the problem without having to use chroot by not loading the binary directly but by substituting it with a  script that calls the correct `ld-linux.so.3`. Assume you have uncompressed the files from the deb packages in `/opt/git-annex`. 
-
-First create a directory `/opt/git-annex/usr/bin/git-annex.exec` and copy the executable `/opt/git-annex/usr/bin/git-annex` there.
-
-Then create script `/opt/git-annex/usr/bin/git-annex` with the following contents:
-
-    #!/bin/bash
-    
-    PREFIX=/opt/git-annex
-    
-    export GCONV_PATH=$PREFIX/usr/lib/gconv 
-        
-    exec $PREFIX/lib/ld-linux.so.3 --library-path $PREFIX/lib/:$PREFIX/usr/lib/ $PREFIX/usr/bin/git-annex.exec/git-annex \"$@\"
-
-The `GCONV_PATH` setting is important to prevent the app from failing with the message:
-
-    git-annex.exec: mkTextEncoding: invalid argument (Invalid argument)
-   
-The original executable is moved to a different directory instead of being simply renamed to make sure that `$0` is correct when the executable starts. The parameter for the linker `--library-path` is used instead of the environment variable `LD_LIBRARY_PATH` to make sure that the programs exec'ed by git-annex do not have the variable set.
-
-Some more info about the approach: [[http://www.novell.com/coolsolutions/feature/11775.html]]
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_15_c12f525ef4cbe42cdf20fec0d53c8d86._comment b/doc/todo/Build_for_Synology_DSM/comment_15_c12f525ef4cbe42cdf20fec0d53c8d86._comment
deleted file mode 100644
index 007199f5b..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_15_c12f525ef4cbe42cdf20fec0d53c8d86._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 15"
- date="2013-12-16T05:55:29Z"
- content="""
-Following the example of @lorenzo, I have made all the git-annex Linux standalone builds include glibc and shims to make the linker use it.
-
-Now that there's a [[forum/new_linux_arm_tarball_build]], it may *just work* on Synology.
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_1_4059016fa8da6af7a3eba8966821e8eb._comment b/doc/todo/Build_for_Synology_DSM/comment_1_4059016fa8da6af7a3eba8966821e8eb._comment
deleted file mode 100644
index 074ba998c..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_1_4059016fa8da6af7a3eba8966821e8eb._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-05-24T15:55:42Z"
- content="""
-There are already git-annex builds for arm available from eg, Debian. There's a good chance that, assuming you match up the arm variant (armel, armhf, etc) and that the NAS uses glibc and does not have too old a version, that the binary could just be copied in, possibly with some other libraries, and work. This is what's done for the existing Linux standalone builds.
-
-So, I look at this bug report as \"please add a standalone build for arm\", not as a request to support a specific NAS which I don't have ;)
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_2_8900c2985ab68b3b566c9f5d326471d6._comment b/doc/todo/Build_for_Synology_DSM/comment_2_8900c2985ab68b3b566c9f5d326471d6._comment
deleted file mode 100644
index 40e6398f0..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_2_8900c2985ab68b3b566c9f5d326471d6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA"
- nickname="Franck"
- subject="comment 2"
- date="2013-05-24T21:31:44Z"
- content="""
-I tried to run the binary from the Debian package, unfortunately, after installing tons of libraries, git-annex fails complaining that GLIBC is not recent enough. Perhaps a static build for ARM (armel) can solve the problem? Thanks again for your help!
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_3_f2b77368473d42b7f21e9d51d6415b58._comment b/doc/todo/Build_for_Synology_DSM/comment_3_f2b77368473d42b7f21e9d51d6415b58._comment
deleted file mode 100644
index 651edacd7..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_3_f2b77368473d42b7f21e9d51d6415b58._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 3"
- date="2013-05-25T04:42:22Z"
- content="""
-Which Debian package? Different ones link to different libcs.
-
-(It's not really possible to statically link something with as many dependencies as git-annex on linux anymore, unfortunately.)
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_4_a55fea734044c270ceb10adf9c8d9a76._comment b/doc/todo/Build_for_Synology_DSM/comment_4_a55fea734044c270ceb10adf9c8d9a76._comment
deleted file mode 100644
index 50ae82ca0..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_4_a55fea734044c270ceb10adf9c8d9a76._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA"
- nickname="Franck"
- subject="comment 4"
- date="2013-05-25T07:40:13Z"
- content="""
-I've actually tried several ones: 4.20130521 on sid, 3.20120629~bpo60+2 on squeeze-backports, 3.20120629 on wheezy and jessie, plus a package for Ubuntu 11.02. All of them try to load GLIBC 2.6/2.7 while my system has 2.5 only... I'll try a different approach: install Debian in a chroot on the NAS and extract all the required files, including all libraries.
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_5_59865ada057c640ac29855c65cf45dd9._comment b/doc/todo/Build_for_Synology_DSM/comment_5_59865ada057c640ac29855c65cf45dd9._comment
deleted file mode 100644
index 725025283..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_5_59865ada057c640ac29855c65cf45dd9._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA"
- nickname="Franck"
- subject="comment 5"
- date="2013-05-25T10:03:24Z"
- content="""
-Unfortunately, chroot approach does not work either. While git-annex works fine when I'm in the chroot, it doesn't work any more outside. If I don't copy libc, I get a version error (just like before so this is normal):
-
-    git-annex: /lib/libc.so.6: version `GLIBC_2.7' not found (required by /opt/share/git-annex/bin/git-annex)
-    git-annex: /lib/libc.so.6: version `GLIBC_2.6' not found (required by /opt/share/git-annex/bin/git-annex)
-    git-annex: /lib/libc.so.6: version `GLIBC_2.7' not found (required by /opt/share/git-annex/lib/libgmp.so.10)
-
-When I copy libc from the Debian chroot, then, it complains about libpthread:
-
-    git-annex: relocation error: /lib/libpthread.so.0: symbol __default_rt_sa_restorer, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
-
-If then I copy libpthread also, I get:
-
-    Illegal instruction (core dumped)
-
-So, I'm stuck...  :-(
-I'll try to find a way using the version in the chroot instead of trying to export it to the host system...
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_6_6d860b1ad8816077b5fa596a71b12d5c._comment b/doc/todo/Build_for_Synology_DSM/comment_6_6d860b1ad8816077b5fa596a71b12d5c._comment
deleted file mode 100644
index 417293db3..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_6_6d860b1ad8816077b5fa596a71b12d5c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog"
- nickname="Michael"
- subject="bind mount"
- date="2013-05-25T15:55:52Z"
- content="""
-You could bind-mount (e.g. mount -o bind /data /chroot/data ) your main Synology fs into the chroot for git-annex to use.
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_7_19ef2d293ba3bc7ece443d7278371c3f._comment b/doc/todo/Build_for_Synology_DSM/comment_7_19ef2d293ba3bc7ece443d7278371c3f._comment
deleted file mode 100644
index 47d092331..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_7_19ef2d293ba3bc7ece443d7278371c3f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA"
- nickname="Franck"
- subject="comment 7"
- date="2013-05-25T19:01:29Z"
- content="""
-This is indeed what I'm doing. But I need to make a wrapper that will call the command in the chroot. Thanks for the tip anyway. :-) 
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_8_609b7ad87dfbba49ec1f8c6fc2739ccd._comment b/doc/todo/Build_for_Synology_DSM/comment_8_609b7ad87dfbba49ec1f8c6fc2739ccd._comment
deleted file mode 100644
index 8a3490956..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_8_609b7ad87dfbba49ec1f8c6fc2739ccd._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmqz6wCn-Q1vzrsHGvEJHOt_T5ZESilxhc"
- nickname="Sören"
- subject="comment 8"
- date="2013-05-26T13:50:31Z"
- content="""
-I have a Synology NAS too, so I thought I could try to run git-annex in a Debian chroot.
-As it [turns out](http://forum.synology.com/wiki/index.php/What_kind_of_CPU_does_my_NAS_have), my model (DS213+) runs on a PowerPC CPU instead of ARM. Unfortunately, it isn't compatible with PPC in Debian either because it is a different PowerPC variant.
-There is an unofficial Debian port called [powerpcspe](http://wiki.debian.org/PowerPCSPEPort), but ghc doesn't build there yet for [some reason](http://buildd.debian-ports.org/status/package.php?p=git-annex&suite=sid).
-
-Any chance that there will be a build for this architecture at some point in the future or should I better look for another NAS? ;-)
-"""]]
diff --git a/doc/todo/Build_for_Synology_DSM/comment_9_d94a73b9a07c5cadf191005f817fd59a._comment b/doc/todo/Build_for_Synology_DSM/comment_9_d94a73b9a07c5cadf191005f817fd59a._comment
deleted file mode 100644
index c8b45fc60..000000000
--- a/doc/todo/Build_for_Synology_DSM/comment_9_d94a73b9a07c5cadf191005f817fd59a._comment
+++ /dev/null
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA"
- nickname="Franck"
- subject="comment 9"
- date="2013-06-02T13:14:56Z"
- content="""
-Hi, I finally succeeded! :-)
-
-Here are the main steps:
-
- 1. install `debian-chroot` on the NAS
- 2. create an account `gitannex` in Debian
- 3. configure git on this account (this is important otherwise git complains and fails) `git config --global user.email YOUR_EMAIL` and `git config --global user.name YOUR_NAME`
- 4. install `gcc` on the NAS (using `ipkg`)
- 5. download the files here: https://www.dropbox.com/sh/b7z68a730aj3mnm/95nFOzE1QP
- 6. edit `_chrooter` to fit your settings (probably there is nothing to change if your Debian is freshly installed)
- 7. run `make install`, everything goes to `/opt/bin`, if you change this, you should also edit line 17 in file `gasp`
- 8. create an account `gitannex` on the NAS (doesn't need to be the same name as in Debian, but I feel it is easier)
- 9. edit its `.ssh/authorized_keys` to prefix lines as follows `command=\"gasp\" THE_PUBLIC_KEY_AS_USUAL`
- 10. it should work
- 11. the repositories will be in the Debian account, but it's easy to symlink them in the NAS account if you wish
-
-The principle is as follows: `command=\"gasp\"` allows to launch `gasp` on SSH connexion instead of the original command given to `ssh`. This command is retrieved by `gasp` and prefixed with `chrooter-` (so, eg, running `ssh git` on the client results in running `chrooter-git` on the NAS). `chrooter-*` commands are symlinks to `chrooter`, this is a setuid root binary that launches `_chrooter`. (This intermediary binary is necessary because `_chrooter` is a script which cannot be setuid, and setuid is required for the chroot and identity change.) Finally, `_chrooter` starts the `debian-chroot` service, chroot to the target dir, changes identity and eventually launches the original command as if it was lauched directly by `gitannex` user in Debian. `_chrooter` and `gasp` are Python scripts, I did not use shell in order to avoid error-prone issues with spaces in arguments (that need to be passed around several times in the process).
-
-I'll try now to add command-line parameters to `gasp` in order to restrict the commands that can be run through SSH and the repositories allowed.
-
-Cheers,
-Franck
-"""]]
diff --git a/doc/todo/Check_if_an_upgrade_is_available_in_the_webapp.mdwn b/doc/todo/Check_if_an_upgrade_is_available_in_the_webapp.mdwn
deleted file mode 100644
index e102606ca..000000000
--- a/doc/todo/Check_if_an_upgrade_is_available_in_the_webapp.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-Especially on Mac OSX (and Windows, and maybe Android), it would be great to be able to check in the webapp if an upgrade is available. A deeper integration with these OS would be even better: for example on Mac OSX, an icon on the status bar list available upgrades for some programs, including LibreOffice and others which are not installed by default.
-
-Also, it would be great to be able to download and install git-annex upgrades directly from the webapp.
-
-> comprehensively [[done]]; [[design/assistant/upgrading]] --[[Joey]]
diff --git a/doc/todo/Check_if_an_upgrade_is_available_in_the_webapp/comment_1_c904182f6bff8b1a42070bbc038eb34e._comment b/doc/todo/Check_if_an_upgrade_is_available_in_the_webapp/comment_1_c904182f6bff8b1a42070bbc038eb34e._comment
deleted file mode 100644
index 750e3b83a..000000000
--- a/doc/todo/Check_if_an_upgrade_is_available_in_the_webapp/comment_1_c904182f6bff8b1a42070bbc038eb34e._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.246"
- subject="comment 1"
- date="2013-11-15T20:51:18Z"
- content="""
-I have thought about doing this, especially if there is ever a security hole in git-annex.
-
-All it needs is a file containing the version number to be written along-side the git-annex build, and git-annex knowing if it was built as a standalone build, and should check that.
-
-As for actually performing the upgrade:
-
-* Easy on Linux
-* Not sure on OSX.. Is it possible to use hdiutil attach to replace a dmg while a program contained in it is currently running?
-* Probably impossible on Android, at least not without using double the space. Probably better to get git-annex into an app store.
-* Doable on Windows, but would need git-annex to be distributed in a form that was not a installer.exe.
-"""]]
diff --git a/doc/todo/Check_if_an_upgrade_is_available_in_the_webapp/comment_2_ebe7a75ca291e7f749bfe9f46d10909d._comment b/doc/todo/Check_if_an_upgrade_is_available_in_the_webapp/comment_2_ebe7a75ca291e7f749bfe9f46d10909d._comment
deleted file mode 100644
index d06fe3961..000000000
--- a/doc/todo/Check_if_an_upgrade_is_available_in_the_webapp/comment_2_ebe7a75ca291e7f749bfe9f46d10909d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlzlNQbf6wBgv9j6-UqfpXcQyAYMF8S3t4"
- nickname="Tim"
- subject="comment 2"
- date="2014-01-12T09:19:31Z"
- content="""
-I am pretty sure you know about it, but have you seen https://f-droid.org/?  I was rather surprised that git-annex isn't yet listed in that \"store\".
-"""]]
diff --git a/doc/todo/Enhancement:_git_annex_whereis_KEY.mdwn b/doc/todo/Enhancement:_git_annex_whereis_KEY.mdwn
deleted file mode 100644
index 604bc5566..000000000
--- a/doc/todo/Enhancement:_git_annex_whereis_KEY.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-### Please describe the problem.
-
-Great work on git annex! One possible enhancement occured to me: It would be very useful though if the "whereis" command would support looking up the location of files by arbitrary keys. This way one could inspect the location of old content which is not currently checked-out in the tree.
-
-In a related vein, the "unused" command could report old filenames or describe the associated commits. Tracking old versions is a great feature of your git-based approach, but currently, tasks such as pruning selected content seem unwiedly. Though I might be missing existing solutions. You can easily "cut-off" the history by forcing a drop of all unused content. It would be cool if one could somehow "address" old versions by filename and commit/date and selectively drop just these. The same could go for the "whereis" command, where one could e.g. query which remote holds content which was stored under some filename at some specific date.
-
-Thanks Cheers!
-
-> I agree that it's useful to run whereis on a specific key. This can
-> now be done using `git annex whereis --key KEY`
-> [[done]] --[[Joey]]
-> 
-> To report old filenames, unused would have to search back through the
-> contents of symlinks in old versions of the repo, to find symlinks that
-> referred to a key. The best way I know how to do that is `git log -S$KEY`,
-> which is what unused suggests you use. But this is slow --
-> searching for a single key in one of my repos takes 25 seconds.
-> That's why it doesn't do it for you.
-> 
diff --git a/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment b/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment
deleted file mode 100644
index eb60a25d3..000000000
--- a/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_1_5d768ab0065e6ecbc8ea25d66c226758._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="zardoz"
- ip="92.227.51.179"
- subject="comment 1"
- date="2014-05-13T20:34:33Z"
- content="""
-I suppose that makes sense. Is it more affordable to just retrieve the most recent filename? That would seem to be enough for many practical purposes. But I guess this would still possibly have to go through many revisions. I wonder if such a restricted search can be done by git though. Maybe using non-porcelain commands.
-"""]]
diff --git a/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_2_4189d9e91208a59381100613e254e731._comment b/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_2_4189d9e91208a59381100613e254e731._comment
deleted file mode 100644
index e5645884e..000000000
--- a/doc/todo/Enhancement:_git_annex_whereis_KEY/comment_2_4189d9e91208a59381100613e254e731._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="zardoz"
- ip="134.147.14.84"
- subject="comment 2"
- date="2014-05-15T13:03:47Z"
- content="""
-Okay, I suppose one way of doing a search that works like that would do a «git log --stat -S'KEY' $commit», starting with HEAD and then walking the parents.
-"""]]
diff --git a/doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp.mdwn b/doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp.mdwn
deleted file mode 100644
index e224215fc..000000000
--- a/doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-One Problem I am having is that I could never get the xmpp pairing to work so whenever I switch machines I have to manually run sync once on the command line to get the changes. Is it possible to have a sync now button of some sort that will trigger a sync on the repos?
-
-> moved from forum; [[done]] --[[Joey]] 
diff --git a/doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp/comment_1_0d5c90eb0e8fe61b82a19c5fea343613._comment b/doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp/comment_1_0d5c90eb0e8fe61b82a19c5fea343613._comment
deleted file mode 100644
index a5f631d50..000000000
--- a/doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp/comment_1_0d5c90eb0e8fe61b82a19c5fea343613._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnR6E5iUghMWdUGlbA9CCs8DKaoigMjJXw"
- nickname="Efraim"
- subject="comment 1"
- date="2014-03-06T20:37:36Z"
- content="""
-not quite a sync button, but when I want to force sync now I turn off and turn on sync for one of the repos from the webapp and then it syncs.
-"""]]
diff --git a/doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp/comment_2_196552002d70390e8b52b4af61dca903._comment b/doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp/comment_2_196552002d70390e8b52b4af61dca903._comment
deleted file mode 100644
index 41e05bf6e..000000000
--- a/doc/todo/Feature_Request:_Sync_Now_Button_in_Webapp/comment_2_196552002d70390e8b52b4af61dca903._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.146"
- subject="comment 2"
- date="2014-03-06T22:12:27Z"
- content="""
-I've added a \"Sync now\" to the menu for each remote. So can be used to sync with an individual remote, or if picked from the menu for the local repository, it causes it to try to sync with every one if its remotes at once.
-"""]]
diff --git a/doc/todo/Limit_file_revision_history.mdwn b/doc/todo/Limit_file_revision_history.mdwn
deleted file mode 100644
index 48b44dea2..000000000
--- a/doc/todo/Limit_file_revision_history.mdwn
+++ /dev/null
@@ -1,117 +0,0 @@
-Hi, I am assuming to use git-annex-assistant for two usecases, but I would like to ask about the options or planed roadmap for dropped/removed files from the repository.
-
-Usecases:
-
-1. sync working directory between laptop, home computer, work komputer
-2. archive functionality for my photograps
-
-Both usecases have one common factor. Some files might become obsolate and
-in long time frame nobody is interested to keep their revisions. Let's
-assume photographs. Usuall workflow I take is to import all photograps to
-filesystem, then assess (select) the good ones I want to keep and then
-process them what ever way.
-
-Problem with git-annex(-assistant) I have is that it start to revision all
-of the files at the time they are added to directory. This is welcome at
-first but might be an issue if you are used to put 80% of the size of your
-imported files to trash.
-
-I am aware of what git-annex is not. I have been reading documentation for
-"git-annex drop" and "unused" options including forums. I do understand
-that I am actually able to delete all revisions of the file if I will drop
-it, remove it and if I will run git annex unused 1..###. (on all synced
-repositories).
-
-I actually miss the option to have above process automated/replicated to the other synced repositories.
-
-I would formulate the 'use case' requirements for git-annex as:
-
-* command to drop an file including revisions from all annex repositories?
-  (for example like moving a file to /trash folder) that will schedulle
-  it's deletition)
-* option to keep like max. 10 last revisions of the file?
-* option to keep only previous revisions if younger than 6 months from now?
-
-Finally, how to specify a feature request for git-annex?
-
-> By moving it here ;-) --[[Joey]] 
-
-> So, let's spec out a design.
-> 
-> * Add preferred content terminal to configure whether a repository wants
->   to hang on to unused content. Simply `unused`.
->   (It cannot include a timestamp, because there's
->   no way repos can agree on about when a key became unused.) **done**
-> * In order to quickly match that terminal, the Annex monad will need
->   to keep a Set of unused Keys. This should only be loaded on demand.
->   **done**  
->   NB: There is some potential for a great many unused Keys to cause
->   memory usage to balloon.
-> * Client repositories will end their preferred content with
->   `and (not unused)`. Transfer repositories too, because typically
->   only client repos connect to them, and so otherwise unused files
->   would build up there. Backup repos would want unused files. I
->   think that archive repos would too. **done**
-> * Make the assistant check for unused files periodically. Exactly
->   how often may need to be tuned, but once per day seems reasonable
->   for most repos. Note that the assistant could also notice on the
->   fly when files are removed and mark their keys as unused if that was
->   the last associated file. (Only currently possible in direct mode.)
->   **done**
-> * After scanning for unused files, it makes sense for the
->   assistant to queue transfers of unused files to any remotes that
->   do want them (eg, backup remotes). If the files can successfully be
->   sent to a remote, that will lead to them being dropped locally as
->   they're not wanted.
-> * Add a git config setting like annex.expireunused=7d. This causes
->   *deletion* of unused files after the specified time period if they are
->   not able to be moved to a repo that wants them.
->   (The default should be annex.expireunused=false.)
-> * How to detect how long a file has been unused? We can't look at the
->   time stamp of the object; we could use the mtime of the .map file,
->   that that's direct mode only and may be replaced with a database
->   later. Seems best to just keep a unused log file with timestamps.
->   **done**
-> * After the assistant scans for unused files, if annex.expireunused
->   is not set, and there is some significant quantity of unused files
->   (eg, more than 1000, or more than 1 gb, or more than the amount of
->   remaining free disk space),
->   it can pop up a webapp alert asking to configure it. **done**
-> * Webapp interface to configure annex.expireunused. Reasonable values
->   are no expiring, or any number of days. **done**
-> 
-> [[done]] This does not cover every use case that was requested.
-> But I don't see a cheap way to ensure it keeps eg the past 10 versions of
-> a file. I guess that if you care about that, you leave
-> annex.expireunused=false, and set up a backup repository where the unused
-> files will be moved to.
-> 
-> Note that since the assistant uses direct mode by default, old versions
-> of modififed files are not guaranteed to be retained. But they very well
-> might be. For example, if a file is replicated to 2 clients, and one
-> client directly edits it, or deletes it, it loses the old version,
-> but the other client will still be storing that old version.
-> 
-> ## Stability analysis for unused in preferred content expressions
-> 
-> This is tricky, because two repos that are otherwise entirely
-> in sync may have differing opinons about whether a key is unused,
-> depending on when each last scanned for unused keys.
-> 
-> So, this preferred content terminal is *not stable*.
-> It may be possible to write preferred content expressions 
-> that constantly moved such keys around without reaching a steady state.
-> 
-> Example:
-> 
-> A and B are clients directly connected, and both also connected
-> to BACKUP.
-> 
-> A deletes F. B syncs with A, and runs unused check; decides F
-> is unused. B sends F to BACKUP. B will then think A doesn't want F,
-> and will drop F from A. Next time A runs a full transfer scan, it will
-> *not* find F (because the file was deleted!). So it won't get F back from
-> BACKUP.
-> 
-> So, it looks like the fact that unused files are not going to be
-> looked for on the full transfer scan seems to make this work out ok.
diff --git a/doc/todo/Option_for_browser_to_launch_webapp_with.mdwn b/doc/todo/Option_for_browser_to_launch_webapp_with.mdwn
deleted file mode 100644
index dae601169..000000000
--- a/doc/todo/Option_for_browser_to_launch_webapp_with.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-Firefox is my default browser, but as we all know, it doesn't load quickly.  If I don't have Firefox running but I want to access the git-annex webapp, I'd rather launch the webapp in some small, quick browser like QupZilla than wait for Firefox to load.
-
-Could git-annex have a setting, maybe a "webapp --browser" option and/or a setting in the config file, to specify the browser to launch?
-
-> git-annex uses the standard `git config web.browser` if you set it.
-> [[done]]
-> --[[Joey]]
diff --git a/doc/todo/Please_abort_build_if___34__make_test__34___fails.mdwn b/doc/todo/Please_abort_build_if___34__make_test__34___fails.mdwn
deleted file mode 100644
index 592b5e077..000000000
--- a/doc/todo/Please_abort_build_if___34__make_test__34___fails.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-A failure during "make test" should be signalled to the caller by means of
-a non-zero exit code. Without that signal, it's very hard to run the
-regression test suite in an automated fashion.
-
-> git-annex used to have a Makefile that ignored make test exit status,
-> but that was fixed in commit dab5bddc64ab4ad479a1104748c15d194e138847,
-> in October 6th. [[done]] --[[Joey]] 
diff --git a/doc/todo/Please_add_support_for_monad-control_0.3.x.mdwn b/doc/todo/Please_add_support_for_monad-control_0.3.x.mdwn
deleted file mode 100644
index f82224991..000000000
--- a/doc/todo/Please_add_support_for_monad-control_0.3.x.mdwn
+++ /dev/null
@@ -1,9 +0,0 @@
-Git-annex doesn't compile with the latest version of monad-control. Would it be hard to support that new version?
-
-> I have been waiting for it to land in Debian before trying to 
-> deal with its changes.
-> 
-> There is now a branch in git called `new-monad-control` that will build
-> with the new monad-control. --[[Joey]]
-
->> Now merged to master. [[done]] --[[Joey]]
diff --git a/doc/todo/Provide_a___34__git_annex_satisfy__95__num__95__copies__34___command.mdwn b/doc/todo/Provide_a___34__git_annex_satisfy__95__num__95__copies__34___command.mdwn
deleted file mode 100644
index cbd01181f..000000000
--- a/doc/todo/Provide_a___34__git_annex_satisfy__95__num__95__copies__34___command.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-Please provide a command that basically performs something like: 
-
-git get --auto
-for i in `git remote`; do git copy -to $i --auto; done
-
-
-The use case is this:
-I have a very large repo (300.000 files) in three places. Now I want the fastest possible way to ensure, that every file exists in annex.numcopies. This should scan every file one time and then get it or copy it to other repos as needed. Right now, I make one "git annex get --auto" in every repo, which is is a waste of time, since most of the files never change anyway!
-
-> Now `git annex sync --content` does effectivly just what the shown for
-> loop does. [[done]]
-> 
-> The only difference is that copy --auto proactively downloads otherwise
-> unwanted files to satisfy numcopies, and sync --content does not.
-> We need a [[preferred_content_numcopies_check]] to solve that.
-> --[[Joey]]
diff --git a/doc/todo/S3.mdwn b/doc/todo/S3.mdwn
deleted file mode 100644
index 7e417336f..000000000
--- a/doc/todo/S3.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-Support Amazon S3 as a file storage backend.
-
-There's a haskell library that looks good. Not yet in Debian.
-
-Multiple ways of using S3 are possible. Currently implemented as 
-a special type of git remote.
-
-Before this can be close, I need to fix:
-
-## encryption
-
-TODO
-
-## unused checking
-
-One problem is `git annex unused`. Currently it only looks at the local
-repository, not remotes. But if something is dropped from the local repo,
-and you forget to drop it from S3, cruft can build up there.
-
-This could be fixed by adding a hook to list all keys present in a remote.
-Then unused could scan remotes for keys, and if they were not used locally,
-offer the possibility to drop them from the remote.
-
-[[done]]
diff --git a/doc/todo/Sync_repo_names__63__.mdwn b/doc/todo/Sync_repo_names__63__.mdwn
deleted file mode 100644
index d3bb59f04..000000000
--- a/doc/todo/Sync_repo_names__63__.mdwn
+++ /dev/null
@@ -1,10 +0,0 @@
-It's very confusing to me that the same repo viewed from different client systems can have different names and descriptions.  This implies that making changes to a remote repo from one system only affects how that system sees the repo, but it seems to affect how the entire git-annex "pair" or "network of repos" sees it.
-
-I think it would be good if the names and descriptions of repos were synced across clients.
-
-> The descriptions of repositories are synced. (They're stored in git-annex:uuid.log)
-> 
-> git allows for the same repository to be referred to using as many different remote names as you want to set up. git-annex inherits this,
-> and I can't see this changing; there are very good reasons for remotes to
-> have this flexability. [[done]]
-> --[[Joey]] 
diff --git a/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn b/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn
deleted file mode 100644
index 48c136b26..000000000
--- a/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-This is just an idea, and I have no idea if it would work (that's why I'm asking):
-
-**Would it be possible to use ASICs made for Bitcoin mining inside git-annex to offload the hashing of files?**
-
-I got the idea, because I have two RaspberryPis here: 
-
-- one runs my git-annex archive. It is really slow at hashing, so I resorted to using the WORM backend
-- another one runs 2 old-ish ASIC miners. They are just barely "profitable" right now, so in a few months they will be obsolete
-
-Both devices to some kind of `SHA256`. I have a feeling this is either extremely easy or extremely complicated to do… :)
-
-> git-annex uses binaries such as `sha256sum` for hashing large files (large is
-> currently hardcoded as bigger than 1MB). If you insert a binary with the same
-> interface as `sha256sum` into your `$PATH`, git-annex will automatically use
-> it. If you want to use ASIC hashing even for small files, you need to tweak
-> `Backend/Hash.hs`. --[[HelmutGrohne]]
-
->> [[done]] --[[Joey]]
diff --git a/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__/comment_1_a93805a8088402c6dc32d2b9785fcc7d._comment b/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__/comment_1_a93805a8088402c6dc32d2b9785fcc7d._comment
deleted file mode 100644
index 952978834..000000000
--- a/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__/comment_1_a93805a8088402c6dc32d2b9785fcc7d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.172"
- subject="comment 1"
- date="2014-02-20T17:42:10Z"
- content="""
-I feel that Helmut has the right approach to this general type of thing.
-
-I doubt that bitcoin ASICs feature a fast data transfer bus, because bitcoin is a pretty low-data-volume protocol. Additionally AIUI, bitcoin ASICs get their speed by hashing in parallel, which allows them to try many variations of a block at once. So they probably rely on most of the data remaining the same and only a small amount changing. So it's doubtful this would be a win.
-"""]]
diff --git a/doc/todo/Wishlist:_Import_youtube_playlists.mdwn b/doc/todo/Wishlist:_Import_youtube_playlists.mdwn
deleted file mode 100644
index 4826d9d24..000000000
--- a/doc/todo/Wishlist:_Import_youtube_playlists.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-Hi,
-
-it would be great if the importfeed command would be able to read feeds generated by youtube (like for playlists). The youtube playlist feed contains links to separate youtube video pages, which quvi handles just fine. Currently I use the following python script:
-
-    #!/usr/bin/env python
-    import feedparser
-    import sys
-    d = feedparser.parse('http://gdata.youtube.com/feeds/api/playlists/%s' % sys.argv[1])
-    for entry in d.entries:
-        print entry.link
-
-and then 
-
-    kasimon@pc:~/annex/YouTube/debconf13$ youtube-playlist-urls PLz8ZG1e9MPlzefklz1Gv79icjywTXycR- | xargs git annex addurl --fast 
-    addurl Welcome_talk.webm ok
-    addurl Bits_from_the_DPL.webm ok
-    addurl Debian_Cosmology.webm ok
-    addurl Bits_from_the_DPL.webm ok
-    addurl Debian_Cosmology.webm ok
-    addurl Debian_on_Google_Compute_Engine.webm ok
-    ^C
-
-to create a backup of youtube media I'd like to keep.
-
-It would be great if this functionality could be integrated directly into git annex.
-
-Best
-Karsten
-
-> [[done]] --[[Joey]] 
diff --git a/doc/todo/Wishlist:_Import_youtube_playlists/comment_1_4235cbbb0c6f9d83524c970c4588cb2e._comment b/doc/todo/Wishlist:_Import_youtube_playlists/comment_1_4235cbbb0c6f9d83524c970c4588cb2e._comment
deleted file mode 100644
index 3e3c4be82..000000000
--- a/doc/todo/Wishlist:_Import_youtube_playlists/comment_1_4235cbbb0c6f9d83524c970c4588cb2e._comment
+++ /dev/null
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 1"
- date="2013-12-29T18:21:32Z"
- content="""
-Ok, so importfeed looks for items in a feed with enclosures, but this feed is not a podcast feed. So it needs to look for some of the `<links>`
-to find pages that quvi supports. (There might be other links that are not video pages, for all I know. Looks like `getItemLink` finds the right links and then I just need to filter through quvi.
-"""]]
diff --git a/doc/todo/__96__git_annex_import_--lazy__96___--_Delete_everything_that__39__s_in_the_source_directory_and_also_in_the_target_annex.mdwn b/doc/todo/__96__git_annex_import_--lazy__96___--_Delete_everything_that__39__s_in_the_source_directory_and_also_in_the_target_annex.mdwn
deleted file mode 100644
index 996c03461..000000000
--- a/doc/todo/__96__git_annex_import_--lazy__96___--_Delete_everything_that__39__s_in_the_source_directory_and_also_in_the_target_annex.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-As per IRC
-
-    22:13:10 < RichiH> joeyh: btw, i have been pondering a `git annex import --lazy` or some such which basically goes through a directory and deletes everything i find in the annex it run from
-    22:50:39 < joeyh> not sure of the use case
-    23:41:06 < RichiH> joeyh: the use case is "i have important a ton of data into my annexes. now, i am going through the usual crud of cp -ax'ed, rsync'ed, and other random 'new disk, move stuff around and just put a full dump over there' file dumps and would like to delete everything that's annexed already"
-    23:41:33 < RichiH> joeyh: that would allow me to spend time on dealing with the files which are not yet annexed
-    23:41:54 < RichiH> instead of verifying file after file which has been imported already
-    23:43:19 < joeyh> have you tried just running git annex import in a subdirectory and then deleting the dups?
-    23:45:34 < joeyh> or in a separate branch for that matter, which you could then merge in, etc
-    23:54:08 < joeyh> Thinking anout it some more, it would need to scan the whole work tree to see what keys were there, and populate a lookup table. I prefer to avoid things that need git-annex to do such a large scan and use arbitrary amounts of memory.
-    00:58:11 < RichiH> joeyh: that would force everything into the annex, though
-    00:58:20 < RichiH> a plain import, that is
-    00:58:53 < RichiH> in a usual data dump directory, there's tons of stuff i will never import
-    00:59:00 < RichiH> i want to delete large portions of it
-    00:59:32 < RichiH> but getting rid of duplicates first allows me to spend my time focused on stuff humans are good at: deciding
-    00:59:53 < RichiH> whereas the computer can focus on stuff it's good at: mindless comparision of bits
-    01:00:15 < RichiH> joeyh: as you're saying this is complex, maybe i need to rephrase
-    01:01:40 < RichiH> what i envision is git annex import --foo to 1) decide what hashing algorithm should be used for this file 2) hash that file 3) look into the annex if that hash is annexed 3a) optionally verify numcopies within the annex 4) delete the file in the source directory
-    01:01:47 < RichiH> and then move on to the next file
-    01:02:00 < RichiH> if the hash does not exist in the annex, leave it alone
-    01:02:50 < RichiH> if the hash exists in annex, but numcopies is not fulfilled, just import it as a normal import would
-    01:03:50 < RichiH> that sounds quite easy, to me; in fact i will prolly script it if you decide not to implement it
-    01:04:07 < RichiH> but i think it's useful for a _lot_ of people who migrate tons of data into annexes
-    01:04:31 < RichiH> thus i would rather see this upstream and not hacked locally
-
-The only failure mode I see in the above is "file has been dropped elsewhere, numcopies not fulfilled, but that info is not synched to the local repo, yet" -- This could be worked around by always importing the data.
-
-> [[done]] as `git annex import --deduplicate`.
-> --[[Joey]]
diff --git a/doc/todo/__96__git_annex_import_--lazy__96___--_Delete_everything_that__39__s_in_the_source_directory_and_also_in_the_target_annex/comment_1_0cc16eb17151309113cec6d1cccf203d._comment b/doc/todo/__96__git_annex_import_--lazy__96___--_Delete_everything_that__39__s_in_the_source_directory_and_also_in_the_target_annex/comment_1_0cc16eb17151309113cec6d1cccf203d._comment
deleted file mode 100644
index 0b4e22e7c..000000000
--- a/doc/todo/__96__git_annex_import_--lazy__96___--_Delete_everything_that__39__s_in_the_source_directory_and_also_in_the_target_annex/comment_1_0cc16eb17151309113cec6d1cccf203d._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2013-08-06T14:22:03Z"
- content="""
-To expand a bit on the use case:
-
-I have several migration directories which I simply moved to new systems or disks with the help of `cp -ax` or `rsync`.
-As I don't _need_ the data per se and merely want to hold on to it in case I ever happen to need it again and as disk space is laughably cheap, I have a lot of duplicates.
-While I can at least detect bit flips with the help of checksum lists, cleaning those duplicates of duplicated duplicates is quite some effort.
-To make things worse, photos, music, videos, letter and whatnot are thrown into the same container directories.
-
-All in all, getting data out of those data dumps and into a clean structure is quite an effort.
-`git annex import --lazy` would help with this effort as I could start with the first directory, sort stuff by hand, and annex it.
-As soon as data lives in any of my annexes, I could simply run `git annex import --lazy` to get rid of all duplicates while retaining the unannexed files.
-Iterating through this process a few times, I will be left with clean annexes on the one hand and stuff I can simply delete on the other hand.
-
-I could script all this by hand on my own machine, but I am _certain_ that others would find easy, integrated, and unit tested support for whittling down data dumps over time useful.
-"""]]
diff --git a/doc/todo/__96__git_annex_status__47__version__96___should_print_the_local_OS.mdwn b/doc/todo/__96__git_annex_status__47__version__96___should_print_the_local_OS.mdwn
deleted file mode 100644
index 9c2afecb4..000000000
--- a/doc/todo/__96__git_annex_status__47__version__96___should_print_the_local_OS.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-That would make assessing weird reports like [[bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/]] easier and quicker.
-
-> No, if people want to file a bug report, it's up to them to tell me
-> relevant details about their OS. I'm not going down the rathole
-> of making git-annex muck about trying to gather such information.
-> [[done]] --[[Joey]]
diff --git a/doc/todo/__96__git_annex_sync_--auto__96___or___96__git_annex_auto__96___--_synchronize_symlinks__44___tracking_info__44___and_actual_data.mdwn b/doc/todo/__96__git_annex_sync_--auto__96___or___96__git_annex_auto__96___--_synchronize_symlinks__44___tracking_info__44___and_actual_data.mdwn
deleted file mode 100644
index ae0894955..000000000
--- a/doc/todo/__96__git_annex_sync_--auto__96___or___96__git_annex_auto__96___--_synchronize_symlinks__44___tracking_info__44___and_actual_data.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-As per DebConf13: Introduce a one-shot command to synchronize everything,
-including data, with the other remotes.
-
-Especially useful for the debconf annex.
-
-> [[done]]; `git annex sync --content` --[[Joey]]
diff --git a/doc/todo/add_--exclude_option_to_git_annex_find.mdwn b/doc/todo/add_--exclude_option_to_git_annex_find.mdwn
deleted file mode 100644
index a797e97f5..000000000
--- a/doc/todo/add_--exclude_option_to_git_annex_find.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-Seems pretty self-explanatory.
-
-> This was already implemented, the --exclude option can be used
-> for find as well as most any other subcommand. --[[Joey]] [[done]]
diff --git a/doc/todo/add_-all_option.mdwn b/doc/todo/add_-all_option.mdwn
deleted file mode 100644
index 2f25759c2..000000000
--- a/doc/todo/add_-all_option.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-`--all` would make git-annex operate on either every key with content
-present (or in some cases like `get` and `copy --from` on 
-every keys with content not present).
-
-This would be useful when a repository has a history with deleted files
-whose content you want to keep (so you're not using `dropunused`).
-Or when you have a lot of branches and just want to be able to fsck
-every file referenced in any branch (or indeed, any file referenced in any
-ref). It could also be useful (or even a
-good default) in a bare repository.
-
-A problem with the idea is that `.gitattributes` values for keys not
-currently in the tree would not be available (without horrific anounts of
-grubbing thru history to find where/when the key used to exist). So
-`numcopies` set via `.gitattributes` would not work. This would be a
-particular problem for `drop` and for `--auto`.
-
---[[Joey]]
-
-> [[done]]. The .gitattributes problem was solved simply by not
-> supporting `drop --all`. `--auto` also cannot be mixed with --all for
-> similar reasons. --[[Joey]] 
diff --git a/doc/todo/add_a_git_backend.mdwn b/doc/todo/add_a_git_backend.mdwn
deleted file mode 100644
index 2b224710e..000000000
--- a/doc/todo/add_a_git_backend.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-There should be a backend where the file content is stored.. in a git
-repository!
-
-This way, you know your annexed content is safe & versioned, but you only
-have to deal with the pain of git with large files in one place, and can
-use all of git-annex's features everywhere else.
-
-> Speaking as a future user, do very, very much want. -- RichiH
-
->> Might also be interesting to use `bup` in the git backend, to work
->> around git's big file issues there. So git-annex would pull data out
->> of the git backend using bup. --[[Joey]] 
-
->>> Very much so. Generally speaking, having one or more versioned storage back-ends with current data in the local annexes sounds incredibly useful. Still being able to get at old data in via the back-end and/or making offline backups of the full history are excellent use cases. -- RichiH
-
-[[done]], the bup special remote type is written! --[[Joey]] 
-
-> Yay! -- RichiH
diff --git a/doc/todo/add_an_icon_for_the_.desktop_file.mdwn b/doc/todo/add_an_icon_for_the_.desktop_file.mdwn
deleted file mode 100644
index 56428ff4b..000000000
--- a/doc/todo/add_an_icon_for_the_.desktop_file.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-Maybe add the icon /usr/share/doc/git-annex/html/logo.svg to the .desktp file.
-
-> [[done]] long ago.. --[[Joey]] 
diff --git a/doc/todo/add_metadata_to_annexed_files.mdwn b/doc/todo/add_metadata_to_annexed_files.mdwn
deleted file mode 100644
index 3d81677cb..000000000
--- a/doc/todo/add_metadata_to_annexed_files.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-I would like to attach metadata to annexed files (objects) without
-cluttering the workdir with files containing this metadata. A common use
-case would be to add titles to my photo collection that could than end up
-in a generated photo album.
-
-Depending on the implementation it might also be possible to use the metadata facility for a threaded commenting system.
-
-The first question is whether the metadata is attached to the objects and
-thus shared by all paths pointing to the same data object or to paths in
-the worktree. I've no preference here at this point.
-
-> This is [[done]]; see [[design/metadata]].
-> The metadata is attached to objects, not to files.
-> --[[Joey]] 
diff --git a/doc/todo/add_metadata_to_annexed_files/comment_1_38af9b352020194e9ace34d7dde188cf._comment b/doc/todo/add_metadata_to_annexed_files/comment_1_38af9b352020194e9ace34d7dde188cf._comment
deleted file mode 100644
index 8460300a7..000000000
--- a/doc/todo/add_metadata_to_annexed_files/comment_1_38af9b352020194e9ace34d7dde188cf._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 1"
- date="2013-08-24T19:58:54Z"
- content="""
-I don't know if git-annex is the right vehicle to fix this. It seems that a more generic fix that would work in non-git-annex repos would be better.
-
-I can answer your question though: The metadata such as urls and locations that git-annex stores in the git-annex branch is attached to objects, and not to work tree paths.
-"""]]
diff --git a/doc/todo/assistant_git_sync_laddering.mdwn b/doc/todo/assistant_git_sync_laddering.mdwn
deleted file mode 100644
index 7dbc6480a..000000000
--- a/doc/todo/assistant_git_sync_laddering.mdwn
+++ /dev/null
@@ -1,10 +0,0 @@
-When the [[design/assistant]] is running on a pair of remotes, I've seen
-them get out of sync, such that every pull and merge results in a conflict,
-that then has to be auto-resolved. 
-
-This seems similar to the laddering problem described in this old bug:
-[[bugs/making_annex-merge_try_a_fast-forward]]
-
---[[Joey]]
-
-Think I've fixed this. [[done]] --[[Joey]]
diff --git a/doc/todo/assistant_smarter_archive_directory_handling.mdwn b/doc/todo/assistant_smarter_archive_directory_handling.mdwn
deleted file mode 100644
index fa5a3e4fc..000000000
--- a/doc/todo/assistant_smarter_archive_directory_handling.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-Client repos do not want files in archive directories. This can turn
-out to be confusing to users who are using archive directories for their
-own purposes and not aware of this special case in the assistant. It can
-seem like the assistant is failing to sync their files.
-
-I thought, first, that it should have a checkbox to enable the archive
-directory behavior.
-
-However, I think I have a better idea. Change the preferred content
-expression for clients, so they want files in archive directories, *until*
-those files land in an archive.
-
-This way, only users who set up an archive repo get this behavior. And they
-asked for it by setting up that repo!
-
-Also, the new behavior will mean that files in archive directories still
-propigate around to clients. Consider this topology:
-
-	client A ---- client B ---- archive
-
-If a file is created in client A, and moved to an archive directory before
-it syncs to B, it will never get to the archive, and will continue wasting
-space on A. With the new behavior, A and B serve as effectively, transfer
-repositories for archived content.
-
-Something vaguely like this should work as the preferred content
-expression for the clients:
-
-	exclude=archive/* or (include=archive/* and (not (copies=archive:1 or copies=smallarchive:1)))
-
-> [[done]] --[[Joey]]
diff --git a/doc/todo/assistant_threaded_runtime.mdwn b/doc/todo/assistant_threaded_runtime.mdwn
deleted file mode 100644
index 03ba66acf..000000000
--- a/doc/todo/assistant_threaded_runtime.mdwn
+++ /dev/null
@@ -1,40 +0,0 @@
-The [[design/assistant]] would be better if git-annex used ghc's threaded
-runtime (`ghc -threaded`).
-
-Currently, whenever the assistant code runs some external command, all
-threads are blocked waiting for it to finish.
-
-For transfers, the assistant works around this problem by forking separate
-upload processes, and not waiting on them until it sees an indication that
-they have finished the transfer. While this works, it's messy.. threaded
-would be better.
-
-When pulling, pushing, and merging, the assistant runs external git
-commands, and this does block all other threads. The threaded runtime would
-really help here.
-
-[[done]]; the assistant now builds with the threaded runtime.
-Some work still remains to run certian long-running external git commands
-in their own threads to prevent them blocking things, but that is easy to
-do, now. --[[Joey]] 
-
----
-
-Currently, git-annex seems unstable when built with the threaded runtime.
-The test suite tends to hang when testing add. `git-annex` occasionally
-hangs, apparently in a futex lock. This is not the assistant hanging, and
-git-annex does not otherwise use threads, so this is surprising. --[[Joey]]
-
-> I've spent a lot of time debugging this, and trying to fix it, in the
-> "threaded" branch. There are still deadlocks. --[[Joey]]
-
->> Fixed, by switching from `System.Cmd.Utils` to `System.Process`
->> --[[Joey]] 
-
----
-
-It would be possible to not use the threaded runtime. Instead, we could
-have a child process pool, with associated continuations to run after a
-child process finishes. Then periodically do a nonblocking waitpid on each
-process in the pool in turn (waiting for any child could break anything not
-using the pool!). This is probably a last resort...
diff --git a/doc/todo/auto_remotes.mdwn b/doc/todo/auto_remotes.mdwn
deleted file mode 100644
index 715dea720..000000000
--- a/doc/todo/auto_remotes.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-It should be possible for clones to learn about how to contact
-each other without remotes needing to always be explicitly set
-up. Say that `.git-annex/remote.log` is maintained by git-annex
-to contain:
-
-	UUID hostname URI
-
-The URI comes from configured remotes and maybe from 
-`file://$(pwd)`, or even `ssh://$(hostname -f)`
-for the current repo. This format will merge without
-conflicts or data loss.
-
-Then when content is belived to be in a UUID, and no
-configured remote has it, the remote.log can be consulted and
-URIs that look likely tried. (file:// ones if the hostname
-is the same (or maybe always -- a removable drive might tend
-to be mounted at the same location on different hosts),
-otherwise ssh:// ones.)
-
-Question: When should git-annex update the remote.log? 
-(If not just on init.) Whenever it reads in a repo's remotes?
-
-> This sounds useful and the log should be updated every time any remote is being accessed. A counter or timestamp (yes, distributed times may be wrong/different) could be used to auto-prune old entries via a global and per-remote config setting. -- RichiH
-
----
-
-I no longer think I'd use this myself, I find that my repositories quickly
-grow the paths I actually use, somewhat organically. Unofficial paths
-across university quads come to mind. [[done]] --[[Joey]] 
diff --git a/doc/todo/auto_remotes/discussion.mdwn b/doc/todo/auto_remotes/discussion.mdwn
deleted file mode 100644
index b9e1522a8..000000000
--- a/doc/todo/auto_remotes/discussion.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-Remotes log should probably be stored in ".git/annex/remote.log"
-instead of ".git-annex/remote.log" to prevent leaking credentials.
-
-> The idea is to distribute the info between repositories, which is
-> why it'd go in `.git-annex`. Of course that does mean that repository
-> location information would be included, and if that'd not desirable
-> this feature would need to be turned off. --[[Joey]] 
diff --git a/doc/todo/automatic_bookkeeping_watch_command.mdwn b/doc/todo/automatic_bookkeeping_watch_command.mdwn
deleted file mode 100644
index 28b02aff2..000000000
--- a/doc/todo/automatic_bookkeeping_watch_command.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-A "git annex watch" command would help make git-annex usable by users who
-don't know how to use git, or don't want to bother typing the git commands. 
-It would run, in the background, watching via inotify for changes, and
-automatically annexing new files, etc.
-
-The blue sky goal would be something automated like dropbox, except fully
-distributed. All files put into the repository would propagate out
-to all the other clones of it, as network links allow. Note that while
-dropbox allows modifying files, git-annex freezes them upon creation,
-so this would not be 100% equivalent to dropbox. --[[Joey]]
-
-This is a big project with its own [[design pages|design/assistant]].
-
-> [[done]].. at least, we have a watch command an an assistant, which
-> is still being developed. --[[Joey]] 
diff --git a/doc/todo/avoid_unnecessary_union_merges.mdwn b/doc/todo/avoid_unnecessary_union_merges.mdwn
deleted file mode 100644
index 5cd4b6437..000000000
--- a/doc/todo/avoid_unnecessary_union_merges.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-Some commands cause a union merge unnecessarily. For example, `git annex add`
-modifies the location log, which first requires reading the current log (if
-any), which triggers a merge.
-
-Would be good to avoid these unnecessary union merges. First because it's
-faster and second because it avoids a possible delay when a user might
-ctrl-c and leave the repo in an inconsistent state. In the case of an add,
-the file will be in the annex, but no location log will exist for it (fsck
-fixes that).
-
-It may be that all that's needed is to modify Annex.Branch.change
-to read the current value, without merging. Then commands like `get`, that
-query the branch, will still cause merges, and commands like `add` that
-only modify it, will not. Note that for a command like `get`, the merge
-occurs before it has done anything, so ctrl-c should not be a problem
-there.
-
-This is a delicate change, I need to take care.. --[[Joey]]
-
-> [[done]] (assuming I didn't miss any cases where this is not safe!) --[[Joey]] 
diff --git a/doc/todo/backendSHA1.mdwn b/doc/todo/backendSHA1.mdwn
deleted file mode 100644
index 8c16b75ad..000000000
--- a/doc/todo/backendSHA1.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-This backend is not finished.
-
-In particular, while files can be added using it, git-annex will not notice
-when their content changes, and will not create a new key for the new sha1
-of the net content.
-
-[[done]]; use unlock subcommand and commit changes with git
diff --git a/doc/todo/branching.mdwn b/doc/todo/branching.mdwn
deleted file mode 100644
index f65849584..000000000
--- a/doc/todo/branching.mdwn
+++ /dev/null
@@ -1,159 +0,0 @@
-[[done]] !!!
-
-The use of `.git-annex` to store logs means that if a repo has branches 
-and the user switched between them, git-annex will see different logs in
-the different branches, and so may miss info about what remotes have which
-files (though it can re-learn). 
-
-An alternative would be to store the log data directly in the git repo
-as `pristine-tar` does. Problem with that approach is that git won't merge
-conflicting changes to log files if they are not in the currently checked
-out branch.
-
-It would be possible to use a branch with a tree like this, to avoid
-conflicts:
-
-key/uuid/time/status
-
-As long as new files are only added, and old timestamped files deleted,
-there would be no conflicts.
-
-A related problem though is the size of the tree objects git needs to
-commit. Having the logs in a separate branch doesn't help with that.
-As more keys are added, the tree object size will increase, and git will
-take longer and longer to commit, and use more space. One way to deal with
-this is simply by splitting the logs among subdirectories. Git then can
-reuse trees for most directories. (Check: Does it still have to build
-dup trees in memory?)
-
-Another approach would be to have git-annex *delete* old logs. Keep logs
-for the currently available files, or something like that. If other log
-info is needed, look back through history to find the first occurance of a
-log. Maybe even look at other branches -- so if the logs were on master,
-a new empty branch could be made and git-annex would still know where to
-get keys in that branch. 
-
-Would have to be careful about conflicts when deleting and bringing back
-files with the same name. And would need to avoid expensive searching thru
-all history to try to find an old log file.
-
-## fleshed out proposal
-
-Let's use one branch per uuid, named git-annex/$UUID.
-
-- I came to realize this would be a good idea when thinking about how
-  to upgrade. Each individual annex will be upgraded independantly,
-  so each will want to make a branch, and if the branches aren't distinct,
-  they will merge conflict for sure.
-- TODO: What will need to be done to git to make it push/pull these new
-  branches?
-- A given repo only ever writes to its UUID branch. So no conflicts.
-  - **problem**: git annex move needs to update log info for other repos!
-    (possibly solvable by having git-annex-shell update the log info
-    when content is moved using it)
-- (BTW, UUIDs probably don't compress well, and this reduces the bloat of having
-  them repeated lots of times in the tree.)
-- Per UUID branches mean that if it wants to find a file's location
-  among configured remotes, it can examine only their branches, if
-  desired.
-- It's important that the per-repo branches propigate beyond immediate
-  remotes. If there is a central bare repo, that means push --all. Without
-  one, it means that when repo B pulls from A, and then C pulls from B,
-  C needs to get A's branch -- which means that B should have a tracking
-  branch for A's branch.
-
-In the branch, only one file is needed. Call it locationlog. git-annex
-can cache location log changes and write them all to locationlog in
-a single git operation on shutdown.
-
-- TODO: what if it's ctrl-c'd with changes pending? Perhaps it should
-  collect them to .git/annex/locationlog, and inject that file on shutdown?
-- This will be less overhead than the current staging of all the log files.
-
-The log is not appended to, so in git we have a series of commits each of
-which replaces the log's entire contens.
-
-To find locations of a key, all (or all relevant) branches need to be
-examined, looking backward through the history of each until a log
-with a indication of the presense/absense of the key is found.
-
-- This will be less expensive for files that have recently been added
-  or transfered.
-- It could get pretty slow when digging deeper.
-- Only 3 places in git-annex will be affected by any slowdown: move --from,
-  get and drop. (Update: Now also unused, whereis, fsck) 
-
-## alternate
-
-As above, but use a single git-annex branch, and keep the per-UUID
-info in their own log files. Hope that git can auto-merge as long as
-each observing repo only writes to its own files. (Well, it can, but for
-non-fast-forward merges, the git-annex branch would need to be checked out,
-which is problimatic.)
-
-Use filenames like:
-
-	<observing uuid>/<location uuid>
-
-That allows one repo to record another's state when doing a
-`move`.
-
-## outside the box approach
-
-If the problem is limited to only that the `.git-annex/` files make
-branching difficult (and not to the related problem that commits to them
-and having them in the tree are sorta annoying), then a simple approach
-would be to have git-annex look in other branches for location log info
-too.
-
-The problem would then be that any locationlog lookup would need to look in
-all other branches (any branch could have more current info after all),
-which could get expensive.
-
-## way outside the box approach
-
-Another approach I have been mulling over is keeping the log file
-branch checked out in .git/annex/logs/ -- this would be a checkout of a git
-repository inside a git repository, using "git fake bare" techniques. This
-would solve the merge problem, since git auto merge could be used. It would
-still mean all the log files are on-disk, which annoys some. It would
-require some tighter integration with git, so that after a pull, the log
-repo is updated with the data pulled. --[[Joey]] 
-
-> Seems I can't use git fake bare exactly. Instead, the best option
-> seems to be `git clone --shared` to make a clone that uses
-> `.git/annex/logs/.git` to hold its index etc, but (mostly) uses
-> objects from the main repo. There would be some bloat,
-> as commits to the logs made in there would not be shared with the main
-> repo. Using `GIT_OBJECT_DIRECTORY` might be a way to avoid that bloat.
-
-## notes
-
-Another approach could be to use git-notes. It supports merging branches
-of notes, with union merge strategy (a hook would have to do this after
-a pull, it's not done automatically). 
-
-Problem: Notes are usually attached to git
-objects, and there are no git objects corresponding to git-annex keys.
-
-Problem: Notes are not normally copied when cloning.
-
-------
-
-## elminating the merge problem
-
-Most of the above options are complicated by the problem of how to merge
-changes from remotes. It should be possible to deal with the merge
-problem generically. Something like this:
-
-* We have a local branch `B`.
-* For remotes, there are also `origin/B`, `otherremote/B`, etc.
-* To merge two branches `B` and `foo/B`, construct a merge commit that
-  makes each file have all lines that were in either version of the file,
-  with duplicates removed (probably). Do this without checking out a tree.
-  -- now implemented as git-union-merge
-* As a `post-merge` hook, merge `*/B` into `B`. This will ensure `B`
-  is always up-to-date after a pull from a remote.
-* When pushing to a remote, nothing need to be done, except ensure
-  `B` is either successfully pushed, or the push fails (and a pull needs to
-  be done to get the remote's changes merged into `B`).
diff --git a/doc/todo/checkout.mdwn b/doc/todo/checkout.mdwn
deleted file mode 100644
index 50da2d62e..000000000
--- a/doc/todo/checkout.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-The checkout subcommand replaces the symlink that normally points at a
-file's content, with a copy of the file. Once you've checked a file out,
-you can edit it, and `git commit` it. On commit, git-annex will detect
-if the file has been changed, and if it has, `add` its content to the
-annex.
-
-> Internally, this will need to store the original symlink to the file, in 
-> `.git/annex/checkedout/$filename`.
-> 
-> * git-annex uncheckout moves that back
-> * git-annex pre-commit hook checks each file being committed to see if
->   it has a symlink there, and if so, removes the symlink and adds the new
->   content to the annex. 
-> 
-> And it seems the file content should be copied, not moved or hard linked:
-> 
-> * Makes sure other annexes can find it if transferring it from
->   this annex.
-> * Ensures it's always available for uncheckout.
-> * Avoids the last copy of a file's content being lost when
->   the checked out file is modified.
-
-[[done]]
diff --git a/doc/todo/direct_mode_guard.mdwn b/doc/todo/direct_mode_guard.mdwn
deleted file mode 100644
index bb7f90897..000000000
--- a/doc/todo/direct_mode_guard.mdwn
+++ /dev/null
@@ -1,105 +0,0 @@
-Currently [[/direct_mode]] allows the user to point many normally safe
-git commands at his foot and pull the trigger. At LCA2013, a git-annex
-user suggested modifying direct mode to make this impossible.
-
-One way to do it would be to move the .git directory. Instead, make there
-be a .git-annex directory in direct mode repositories. git-annex would know
-how to use it, and would be extended to support all known safe git
-commands, passing parameters through, and in some cases verifying them.
-
-So, for example, `git annex commit` would run `git commit --git-dir=.git-annex`
-
-However, `git annex commit -a` would refuse to run, or even do something
-intelligent that does not involve staging every direct mode file.
-
-----
-
-One source of problems here is that there is some overlap between git-annex
-and git commands. Ie, `git annex add` cannot be a passthrough for `git
-add`. The git wrapper could instead be another program, or it could be
-something like `git annex git add`
-
---[[Joey]]
-
-----
-
-Or, no git wrapper could be provided. Limit the commands to only git-annex
-commands. This should be all that is needed to manage a direct mode
-repository simply, and if the user is doing something complicated that
-needs git access, they can set `GIT_DIR=.git-annex` and be careful not to
-shoot off their foot. (Or can just switch to indirect mode!)
-
-This wins on simplicity, and if it's the wrong choice a git wrapper
-can be added later. --[[Joey]]
-
----
-
-Implementation: Pretty simple really. Already did the hard lifting to
-support `GIT_DIR`, so only need to override the default git directory
-in direct mode when that's not set to `.git-annex`.
-
-A few things hardcode ".git", including Assistant.Threads.Watcher.ignored
-and `Seek.withPathContents`, and parts of `Git.Construct`.
-
----
-
-Transition: git-annex should detect when it's in a direct mode repository
-with a .git directory and no .git-annex directory, and transparently
-do the move to transition to the new scheme. (And remember that `git annex
-indirect` needs to move it back.)
-
-# alternative approach: move index
-
-Rather than moving .git, maybe move .git/index?
-
-This would cause git to think that all files in the tree were deleted.
-So git commit -a would make a commit that removes them from git history.
-But, the files in the work tree are not touched by this.
-
-Also, git checkout, git merge, and other things that manipulate the work
-tree refuse to do anything if they'd change a file that they think is
-untracked.
-
-Hmm, this does't solve the user accidentially running git add on an annexed
-file; the whole file still gets added.
-
-# alternative approach: fake bare repo
-
-Set core.bare to true.  This prevents all work tree operations, 
-so prevents any foot shooting. It still lets the user run commands like
-git log, even on files in the tree, and git fetch, and push, and git
-config, etc.
-
-Even better, it integrates with other tools, like `mr`, so they know
-it's a git repo.
-
-This seems really promising. But of course, git-annex has its own set of
-behaviors in a bare repo, so will need to recognise that this repo is not
-really bare, and avoid them.
-
-> [[done]]!!  --[[Joey]]
-
-(Git may also have some bare repo behaviors that are unwanted. One example
-is that git allows pushes to the current branch in a bare repo, 
-even when `receive.denyCurrentBranch` is set.)
-
-> This is indeed a problem. Indeed, `git annex sync` successfully
-> pushes changes to the master branch of a fake bare direct mode repo.
-> 
-> And then, syncing in the repo that was pushed to causes the changes
-> that were pushed to the master branch to get reverted! This happens
-> because sync commits; commit sees that files are staged in index
-> differing from the (pushed) master, and commits the "changes"
-> which revert it.
-> 
-> Could fix this using an update hook, to reject the updated of the master
-> branch. However, won't work on crippled filesystems! (No +x bit)
-> 
-> Could make git annex sync detect this. It could reset the master
-> branch to the last one committed, before committing. Seems very racy
-> and hard to get right!
->
-> Could make direct mode operate on a different branch, like
-> `annex/direct/master` rather than `master`. Avoid pushing to that
-> branch (`git annex sync` can map back from it to `master` and push there
-> instead). A bit clumsy, but works.
diff --git a/doc/todo/direct_mode_guard/comment_1_431b6e1577bbd30b07dce9002a8fe1a2._comment b/doc/todo/direct_mode_guard/comment_1_431b6e1577bbd30b07dce9002a8fe1a2._comment
deleted file mode 100644
index 01cddc8a3..000000000
--- a/doc/todo/direct_mode_guard/comment_1_431b6e1577bbd30b07dce9002a8fe1a2._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawn-KDr_Z4CMkjS0v_TxQ08SzAB5ecHG3K0"
- nickname="Glen"
- subject="This sounds good"
- date="2013-06-25T10:30:07Z"
- content="""
-I think we might have been talking about this feature.. Seems like a good idea to me.
-
-Glen
-"""]]
diff --git a/doc/todo/direct_mode_guard/comment_2_85bdb9dc601b87bd7c77150d7b0a5cde._comment b/doc/todo/direct_mode_guard/comment_2_85bdb9dc601b87bd7c77150d7b0a5cde._comment
deleted file mode 100644
index 7cf37a917..000000000
--- a/doc/todo/direct_mode_guard/comment_2_85bdb9dc601b87bd7c77150d7b0a5cde._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawm7AuSfii_tCkLyspL6Mr0ATlO6OxLNYOo"
- nickname="Georg"
- subject="comment 2"
- date="2013-09-20T11:29:04Z"
- content="""
-Maybe make a git sub-namespace of commands. Yeah, I know, something like git annex git-add sounds a bit on the verbose side, but it would allow access to possibly all git commands regardless of name clashes. 
-"""]]
diff --git a/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__.mdwn b/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__.mdwn
deleted file mode 100644
index 09123cb4c..000000000
--- a/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-I've an external USB hard disc attached to my (fritzbox) router that is only accessible through SMB/CIFS. I'd like have all my annexed files on this drive in kind of direct-mode so that I can also access the files without git-annex.
-
-I tried to put a direct-mode repo on the drive but this is painfully slow. The git-annex process than runs on my desktop and accesses the repo over SMB over the slow fritzbox over USB.
-
-I'd wish that git-annex could be told to just use a (mounted) folder as a direct-mode remote.
-
-> [[done]]; dup. --[[Joey]] 
diff --git a/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_1_5ed9a2336b432b842c1805add6d96509._comment b/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_1_5ed9a2336b432b842c1805add6d96509._comment
deleted file mode 100644
index bff1b2fcd..000000000
--- a/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_1_5ed9a2336b432b842c1805add6d96509._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 1"
- date="2013-11-23T19:03:58Z"
- content="""
-It's not clear to me what you are requesting here.
-
-You seem to say that running git-annex inside a mountpoint is slow. Ok. So, what possible changes to git-annex could make it fast, given that the bottleneck is the SMB/USB?
-"""]]
diff --git a/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_2_e6ba58c5c31ba23a4575f1189689946f._comment b/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_2_e6ba58c5c31ba23a4575f1189689946f._comment
deleted file mode 100644
index d60cb2d4d..000000000
--- a/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_2_e6ba58c5c31ba23a4575f1189689946f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnR6E5iUghMWdUGlbA9CCs8DKaoigMjJXw"
- nickname="Efraim"
- subject="comment 2"
- date="2013-11-26T09:26:53Z"
- content="""
-perhaps he's looking to be able to expand the addurl option to include file://path/to/video.mp4, or for over smb://... , to import a file without changing its location to being inside the annex.
-"""]]
diff --git a/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_3_e53cbc5765819de2d3c742e6cd4d77cd._comment b/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_3_e53cbc5765819de2d3c742e6cd4d77cd._comment
deleted file mode 100644
index 23b59574f..000000000
--- a/doc/todo/dumb_plaindir_remote___40__e.g._for_NAS_mounts__41__/comment_3_e53cbc5765819de2d3c742e6cd4d77cd._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmicVKRM8vJX4wPuAwlLEoS2cjmFXQkjkE"
- nickname="Thomas"
- subject="never mind"
- date="2013-12-01T18:34:05Z"
- content="""
-grossmeier.net did a much better job to explain what I want:
-[[New special remote suggeston - clean directory]]
-
-Please close this issue as duplicate of the above.
-"""]]
diff --git a/doc/todo/exclude_files_on_a_given_remote.mdwn b/doc/todo/exclude_files_on_a_given_remote.mdwn
deleted file mode 100644
index e8bb357d3..000000000
--- a/doc/todo/exclude_files_on_a_given_remote.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-Say I have some files on remote A. But I'm away from it, and transferring
-files from B to C. I'd like to avoid transferring any files I already have
-on A. 
-
-Something like:
-
-	git annex copy --to C --exclude-on A
-
-This would not contact A, just use its cached location log info.
-
-I suppose I might also sometime want to only act on files that are
-thought/known to be on A.
-
-	git annex drop --only-on A
-
---[[Joey]] 
-
-[[done]]
diff --git a/doc/todo/faster_gnupg_cipher.mdwn b/doc/todo/faster_gnupg_cipher.mdwn
deleted file mode 100644
index f5ff062d2..000000000
--- a/doc/todo/faster_gnupg_cipher.mdwn
+++ /dev/null
@@ -1,9 +0,0 @@
-Apparently newer gnupg has support for hardware-accelerated AES-NI. It
-would be good to have an option to use that. I also wonder if using the
-same symmetric key for many files presents a security issues (and whether
-using GPG keys directly would be more secure).
-
-> [[done]]; you can now use encryption=pubkey when setting up a special
-> remote to use pure public keys without the hybrid symmetric key scheme.
-> Which you choose is up to you. Also,  annex.gnupg-options can configure
-> the ciphers used. --[[Joey]]
diff --git a/doc/todo/faster_gnupg_cipher/comment_1_8f61f7c724a8224e61c015be68f43db7._comment b/doc/todo/faster_gnupg_cipher/comment_1_8f61f7c724a8224e61c015be68f43db7._comment
deleted file mode 100644
index 1bf550cdf..000000000
--- a/doc/todo/faster_gnupg_cipher/comment_1_8f61f7c724a8224e61c015be68f43db7._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.145"
- subject="comment 1"
- date="2013-08-01T17:10:56Z"
- content="""
-There is a remote.name.annex-gnupg-options git-config setting that can be used to pass options to gpg on a per-remote basis.
-
-> also wonder if using the same symmetric key for many files presents a security issues (and whether using GPG keys directly would be more secure).
-
-I am not a cryptographer, but I have today run this question by someone with a good amount of crypo knowledge. My understanding is that reusing a symmetric key is theoretically vulnerable to eg known-plaintext or chosen-plaintext attacks. And that modern ciphers like AES and CAST (gpg default) are designed to resist such attacks.
-
-If someone was particularly concerned about these attack vectors, it would be pretty easy to add a mode where git-annex uses public key encryption directly. With the disadvantage, of course, that once a file was sent to a special remote and encrypted for a given set of public keys, other keys could not later be granted access to it.
-"""]]
diff --git a/doc/todo/faster_gnupg_cipher/comment_2_36e1f227a320527653500b445f7c001c._comment b/doc/todo/faster_gnupg_cipher/comment_2_36e1f227a320527653500b445f7c001c._comment
deleted file mode 100644
index 08f69d6b8..000000000
--- a/doc/todo/faster_gnupg_cipher/comment_2_36e1f227a320527653500b445f7c001c._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2013-08-02T07:21:50Z"
- content="""
-Using symmetric keys is significantly cheaper, computation-wise.
-
-The scheme of encrypting symmetric keys with asymmetric ones is ancient, well-proven, and generally accepted as a good approach.
-
-Using per-key files makes access control more fine-grained and is only a real performance issue once while creating the private key and a little bit every time more than one file needs to be decrypted as more than one symmetric key needs to be taken care of.
-"""]]
diff --git a/doc/todo/faster_gnupg_cipher/comment_3_bd0c975494333dfe558de048d888ace8._comment b/doc/todo/faster_gnupg_cipher/comment_3_bd0c975494333dfe558de048d888ace8._comment
deleted file mode 100644
index d0b98b7f6..000000000
--- a/doc/todo/faster_gnupg_cipher/comment_3_bd0c975494333dfe558de048d888ace8._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.209"
- subject="comment 3"
- date="2013-08-19T13:44:35Z"
- content="""
-AES-NI acceleration will be used by default providing you're using
-the new modularized GnuPG (v2.x) and libgcrypt ≥ 1.5.0. Of course it
-only speeds up AES encryption, while GnuPG uses CAST by default; you can
-either set `personal-cipher-preferences` to AES or AES256 in your
-`gpg.conf` or, as joeyh hinted at, set `remote.<name>.annex-gnupg-options`
-as described in the manpage.
-
-By the way, I observed a significant speed up when using `--compress-algo none`.
-Image, music and video files are typically hard to compress further, and it seems
-that's where gpg spent most of its time, at least on the few files I benchmarked.
-"""]]
diff --git a/doc/todo/faster_rsync_remotes.mdwn b/doc/todo/faster_rsync_remotes.mdwn
deleted file mode 100644
index 8c40b2816..000000000
--- a/doc/todo/faster_rsync_remotes.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-Using an rsync remote is currently very slow when there are a lot of files, since rsync appears to be called for each file copied.  It would be awesome if each call to rsync was amortized to copy many files; rsync is very good at copying many small files quickly.
-
-> [[done]]; bug submitter was apparently not using a version 
-> with rsync connection caching. --[[Joey]]
diff --git a/doc/todo/faster_rsync_remotes/comment_1_0bc3ee0ae563357675eeccf42461e59a._comment b/doc/todo/faster_rsync_remotes/comment_1_0bc3ee0ae563357675eeccf42461e59a._comment
deleted file mode 100644
index 2f320fee2..000000000
--- a/doc/todo/faster_rsync_remotes/comment_1_0bc3ee0ae563357675eeccf42461e59a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.145"
- subject="comment 1"
- date="2013-08-01T16:06:42Z"
- content="""
-I cannot see a way to do this using rsync's current command-line interface. Ideas how to do it welcomed.
-"""]]
diff --git a/doc/todo/faster_rsync_remotes/comment_2_ccf6f75450c89ca498c8130054f8d32d._comment b/doc/todo/faster_rsync_remotes/comment_2_ccf6f75450c89ca498c8130054f8d32d._comment
deleted file mode 100644
index 67b5feab0..000000000
--- a/doc/todo/faster_rsync_remotes/comment_2_ccf6f75450c89ca498c8130054f8d32d._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawln4uCaqZRd5_nRQ-iLcJyGctIdw8ebUiM"
- nickname="Edward"
- subject="Just put multiple source files"
- date="2013-08-01T16:29:04Z"
- content="""
-It seems like you can just put multiple source files on the command line:
-
-    ed@ed-Ubu64 /tmp$ touch a b c d
-    ed@ed-Ubu64 /tmp$ mkdir test
-    ed@ed-Ubu64 /tmp$ rsync -avz a b c d test
-    sending incremental file list
-    a
-    b
-    c
-    d
-    
-    sent 197 bytes  received 88 bytes  570.00 bytes/sec
-    total size is 0  speedup is 0.00
-    ed@ed-Ubu64 /tmp$ ls test
-    a  b  c  d
-
-It also appears to work with remote transfers too.
-"""]]
diff --git a/doc/todo/faster_rsync_remotes/comment_3_2f6a9d23cb8351fbf0f60ed93752e76e._comment b/doc/todo/faster_rsync_remotes/comment_3_2f6a9d23cb8351fbf0f60ed93752e76e._comment
deleted file mode 100644
index 1911048be..000000000
--- a/doc/todo/faster_rsync_remotes/comment_3_2f6a9d23cb8351fbf0f60ed93752e76e._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.145"
- subject="comment 3"
- date="2013-08-01T16:58:49Z"
- content="""
-git-annex needs to build a specific directory structure on the rsync remote though. It seems it would need to build the whole tree locally, containing only the files it wants to send.
-
-When using encryption, it would need to encrypt all the files it's going to send and store them locally until it's built the tree. That could use a lot of disk space.
-
-Also, there's the problem of checking which files are already present in the remote, to avoid re-encrypting and re-sending them. Currently this is done by running rsync with the url of the file, and checking its exit code. rsync does not seem to have an interface that would allow checking multiple files in one call. So any optimisation of the number of rsync calls would only eliminate 1/2 of the current number.
-
-When using ssh:// urls, the rsync special remote already uses ssh connection caching, which I'd think would eliminate most of the overhead. (If you have a version of git-annex older than 4.20130417, you should upgrade to get this feature.) It should not take very long to start up a new rsync over a cached ssh connection. rsync:// is probably noticably slower.
-"""]]
diff --git a/doc/todo/faster_rsync_remotes/comment_4_3a2f45defebae3dde336ee5f40c26d7e._comment b/doc/todo/faster_rsync_remotes/comment_4_3a2f45defebae3dde336ee5f40c26d7e._comment
deleted file mode 100644
index 44d7d5511..000000000
--- a/doc/todo/faster_rsync_remotes/comment_4_3a2f45defebae3dde336ee5f40c26d7e._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawln4uCaqZRd5_nRQ-iLcJyGctIdw8ebUiM"
- nickname="Edward"
- subject="Thanks"
- date="2013-08-01T17:03:23Z"
- content="""
-I am using an old version of git-annex.  I'll try the newer one and see if the connection caching helps!
-"""]]
diff --git a/doc/todo/file_copy_progress_bar.mdwn b/doc/todo/file_copy_progress_bar.mdwn
deleted file mode 100644
index 847c1d1eb..000000000
--- a/doc/todo/file_copy_progress_bar.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-Find a way to copy a file with a progress bar, while still preserving
-stat. Easiest way might be to use pv and fix up the permissions etc
-after?
-
-[[done]]
diff --git a/doc/todo/fsck.mdwn b/doc/todo/fsck.mdwn
deleted file mode 100644
index 1dcaad9a5..000000000
--- a/doc/todo/fsck.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-add a git annex fsck that finds keys that have no referring file
-
-(done)
-
-* Need per-backend fsck support. sha1 can checksum all files in the annex.
-  WORM can check filesize.
-
-* Both can check that annex.numcopies is satisfied. Probably only
-  querying the locationlog, not doing an online verification.
-
-[[done]]
diff --git a/doc/todo/fsck_special_remotes.mdwn b/doc/todo/fsck_special_remotes.mdwn
deleted file mode 100644
index 7196baafe..000000000
--- a/doc/todo/fsck_special_remotes.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-`git annex fsck --from remote`
-
-Basically, this needs to receive each file in turn from the remote, to a
-temp file, and then run the existing fsck code on it. Could be quite
-expensive, but sometimes you really want to check.
-
-An unencrypted directory special remote could be optimised, by not actually
-copying the file, just dropping a symlink, etc.
-
-The WORM backend doesn't care about file content, so it would be nice to
-avoid transferring the content at all, and only send the size.
-
-> [[done]] --[[Joey]] 
diff --git a/doc/todo/git-annex-shell.mdwn b/doc/todo/git-annex-shell.mdwn
deleted file mode 100644
index a9e3b43ed..000000000
--- a/doc/todo/git-annex-shell.mdwn
+++ /dev/null
@@ -1,15 +0,0 @@
-[[done]]
-
-I've been considering adding a `git-annex-shell` command. This would
-be similar to `git-shell` (and in fact would pass unknown commands off to
-`git-shell`).
-
-## Reasons
-
-* Allows locking down an account to only be able to use git-annex (and
-  git).
-* Avoids needing to construct complex shell commands to run on the remote
-  system. (Mostly already avoided by the plumbing level commands.)
-* Could possibly allow multiple things to be done with one ssh connection
-  in future.
-* Allows expanding `~` and `~user` in repopath on the remote system.
diff --git a/doc/todo/git-annex_unused_eats_memory.mdwn b/doc/todo/git-annex_unused_eats_memory.mdwn
deleted file mode 100644
index 760a6ccf5..000000000
--- a/doc/todo/git-annex_unused_eats_memory.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-`git-annex unused` has to compare large sets of data
-(all keys with content present in the repository,
-with all keys used by files in the repository), and so
-uses more memory than git-annex typically needs.
-
-It used to be a lot worse (hundreds of megabytes).
-
-Now it only needs enough memory to store a Set of all Keys that currently
-have content in the annex. On a lightly populated repository, it runs in
-quite low memory use (like 8 mb) even if the git repo has 100 thousand
-files. On a repository with lots of file contents, it will use more.
-
-Still, I would like to reduce this to a purely constant memory use,
-as running in constant memory no matter the repo size is a git-annex design
-goal.
-
-One idea is to use a bloom filter. 
-For example, construct a bloom filter of all keys used by files in
-the repository. Then for each key with content present, check if it's
-in the bloom filter. Since there can be false positives, this might
-miss finding some unused keys. The probability/size of filter
-could be tunable.
-
-> Fixed in `bloom` branch in git. --[[Joey]] 
->> [[done]]! --[[Joey]] 
-
-Another way might be to scan the git log for files that got removed
-or changed what key they pointed to. Correlate with keys with content
-currently present in the repository (possibly using a bloom filter again),
-and that would yield a shortlist of keys that are probably not used. 
-Then scan thru all files in the repo to make sure that none point to keys
-on the shortlist.
diff --git a/doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn b/doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn
deleted file mode 100644
index be7e2dacc..000000000
--- a/doc/todo/git_annex_init_:_include_repo_description_and__47__or_UUID_in_commit_message.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-Would help alot when having to add large(ish) amounts of remotes.
-
-Maybe detect this kind of commit message and ask user whether to automatically add them? See [[auto_remotes]]:
-> Question: When should git-annex update the remote.log? (If not just on init.) Whenever it reads in a repo's remotes?
-
-----
-
-I'm not sure that the above suggestion is going down a path that really
-makes sense. If you want a list of repository UUIDs and descriptions,
-it's there in machine-usable form in `.git-annex/uuid.log`, there is no
-need to try to pull this info out of git commit messages. --[[Joey]]
-
-[[done]]
diff --git a/doc/todo/gitolite_and_gitosis_support.mdwn b/doc/todo/gitolite_and_gitosis_support.mdwn
deleted file mode 100644
index 2fca83986..000000000
--- a/doc/todo/gitolite_and_gitosis_support.mdwn
+++ /dev/null
@@ -1,39 +0,0 @@
-gitosis and gitolite should support git-annex being used to send/receive
-files from the repositories they manage. Users with read-only access
-could only get files, while users with write access could also put and drop
-files.
-
-Doing this right requires modifying both programs, to add [[git-annex-shell]]
-to the list of things they can run, and only allow through appropriate
-git-annex-shell subcommands to read-only users.
-
-I have posted an RFC for modifying gitolite to the
-[gitolite mailing list](http://groups.google.com/group/gitolite?lnk=srg).
-
-> I have not developed a patch yet, but all that git-annex needs is a way
-> to ssh to the server and run the git-annex-shell command there.
-> git-annex-shell is very similar to git-shell. So, one way to enable
-> it is simply to set GL_ADC_PATH to a directory containing git-annex-shell.
-> 
-> But, that's not optimal, since git-annex-shell will send off receive-pack
-> commands to git, which would bypass gitolite's permissions checking.
-> Also, it makes sense to limit readonly users to only download, not
-> upload/delete files from git-annex. Instead, I suggest adding something
-> like this to gitolite's config:
- 
-	# If set, users with W access can write file contents into the git-annex,
-	# and users with R access can read file contents from the git-annex.
-	$GL_GIT_ANNEX = 0;
-
-> If this makes sense, I'm sure I can put a patch together for your
-> review. It would involve modifying gl-auth-command so it knows how
-> to run git-annex-shell, and how to parse out the "verb" from a
-> git-annex-shell command line, and modifying R_COMMANDS and W_COMMANDS.
-
-As I don't write python, someone else is needed to work on gitosis.
---[[Joey]] 
-
-> [[done]]; support for gitolite is in its `pu` branch, and some changes
-> made to git-annefor gitolite is in its `pu` branch, and some changes
-> made to git-annex. Word is gitosis is not being maintained so I won't
-> worry about try to support it. --[[Joey]] 
diff --git a/doc/todo/gitrm.mdwn b/doc/todo/gitrm.mdwn
deleted file mode 100644
index e41c33462..000000000
--- a/doc/todo/gitrm.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-how to handle git rm file? (should try to drop keys that have no
-referring file, if it seems safe..)
-
-[[done]] -- I think that git annex unused and dropunused are the best
-solution to this.
diff --git a/doc/todo/http_git_annex_404_retry.mdwn b/doc/todo/http_git_annex_404_retry.mdwn
deleted file mode 100644
index 69680f0a1..000000000
--- a/doc/todo/http_git_annex_404_retry.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-A repository like http://annex.debconf.org/debconf-share/ has a git repo
-published via http. When getting files from such a repo, git-annex tries
-two urls. One url would be used by a bare repo, and the other by a non-bare
-repo. (This is due to the directory hashing change.) Result is every file
-download from a non-bare http repo starts with a 404 and then it retries
-with the right url.
-
-Since git-annex already downloads the .git/config to find the uuid of the
-http repo, it could also look at it to see if the repo is bare. If not,
-set a flag, and try the two urls in reverse order, which would almost
-always avoid this 404 problem.
-
-(The real solution is probably to flag day and get rid of the old-style
-directory hashing, but that's been discussed elsewhere.)
-
---[[Joey]]
-
-[[done]]
diff --git a/doc/todo/http_headers.mdwn b/doc/todo/http_headers.mdwn
deleted file mode 100644
index 9f61bdc93..000000000
--- a/doc/todo/http_headers.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-The IA would find it useful to be able to control the http headers
-git-annex get, addurl, etc uses. This will allow setting cookies, for
-example.
-
-* annex-web-headers=blah 
-* Perhaps also annex-web-headers-command=blah
-
-[[done]]
diff --git a/doc/todo/immutable_annexed_files.mdwn b/doc/todo/immutable_annexed_files.mdwn
deleted file mode 100644
index b26838e95..000000000
--- a/doc/todo/immutable_annexed_files.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-> josh: Do you do anything in git-annex to try to make the files immutable?
-> For instance, removing write permission, or even chattr?
-> joey: I don't, but that's a very good idea
-> josh: Oh, I just thought of another slightly crazy but handy idea.
-> josh: I'd hate to run into a program which somehow followed the symlink and then did an unlink to replace the file.
-> josh: To break that, you could create a new directory under annex's internal directory for each file, and make the directory have no write permission.
-
-[[done]] and done --[[Joey]] 
diff --git a/doc/todo/incremental_fsck.mdwn b/doc/todo/incremental_fsck.mdwn
deleted file mode 100644
index 7c56328b9..000000000
--- a/doc/todo/incremental_fsck.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-Justin Azoff realized git-annex should have an incremental fsck.
-
-This requires storing the last fsck time of each object.
-
-I would not be strongly opposed to sqlite, but I think there are other
-places the data could be stored. One possible place is the mode or mtime
-of the .git/annex/objects/xx/yy/$key directories (the parent directories
-of where the content is stored). Perhaps the sticky bit could be used to
-indicate the content has been fsked, and the mtime indicate the time
-of last fsck. Anything that dropped or put in content would need to
-clear the sticky bit. --[[Joey]] 
-
-> Basic incremental fsck is done now.
-> 
-> Some enhancements would include:
-> 
-> * --max-age=30d  Once the incremental fsck completes and was started 30 days ago,
->   start a new one.
-> * --time-limit --size-limit --file-limit: Limit how long the fsck runs.
-
->> Calling this [[done]]. The `--incremental-schedule` option
->> allows scheduling time between incremental fscks. `--time-limit` is
->> done. I implemented `--smallerthan` independently. Not clear what
->> `--file-limit` would be. --[[Joey]]
diff --git a/doc/todo/incremental_fsck/comment_1_609b21141dd5686b2c0eaef2b8d63229._comment b/doc/todo/incremental_fsck/comment_1_609b21141dd5686b2c0eaef2b8d63229._comment
deleted file mode 100644
index 709ba078c..000000000
--- a/doc/todo/incremental_fsck/comment_1_609b21141dd5686b2c0eaef2b8d63229._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 1"
- date="2012-09-20T14:11:57Z"
- content="""
-I have a [proof of concept written in python](https://github.com/JustinAzoff/git-annex-background-fsck/blob/master/git-annex-background-fsck).
-
-You can run it and point it the root of an annex or to a subdirectory.  In my brief testing it seems to work :-)
-
-the goal would be to have options like
-
-    git annex fsck /data/annex --check-older-than 1w --check-for 2h --max-load-avg 0.5
-"""]]
diff --git a/doc/todo/link_file_to_remote_repo_feature.mdwn b/doc/todo/link_file_to_remote_repo_feature.mdwn
deleted file mode 100644
index d6b41e805..000000000
--- a/doc/todo/link_file_to_remote_repo_feature.mdwn
+++ /dev/null
@@ -1,52 +0,0 @@
-I have two repos, using SHA1 backend and both using git.
-The first one is a laptop, the second one is a usb drive.
-
-When I drop a file on the laptop repo, the file is not available on that repo until I run *git annex get*
-But when the usb drive is plugged in the file is actually available.
-
-How about adding a feature to link some/all files to the remote repo?
-
-e.g. 
-We have *railscasts/196-nested-model-form-part-1.mp4* file added to git, and only available on the usb drive:
-
-      $ git annex whereis 196-nested-model-form-part-1.mp4 
-         whereis 196-nested-model-form-part-1.mp4 (1 copy) 
-  	   a7b7d7a4-2a8a-11e1-aebc-d3c589296e81 -- origin (Portable usb drive)
-
-I can see the link with:
-
-    $ cd railscasts
-    $ ls -ls 196*
-    8 lrwxr-xr-x  1 framallo  staff  193 Dec 20 05:49 196-nested-model-form-part-1.mp4 -> ../.git/annex/objects/Wz/6P/SHA256-s16898930--43679c67cd968243f58f8f7fb30690b5f3f067574e318d609a01613a2a14351e/SHA256-s16898930--43679c67cd968243f58f8f7fb30690b5f3f067574e318d609a01613a2a14351e
-
-I save this in a variable just to make the example more clear:
-
-    ID=".git/annex/objects/Wz/6P/SHA256-s16898930--43679c67cd968243f58f8f7fb30690b5f3f067574e318d609a01613a2a14351e/SHA256-s16898930--43679c67cd968243f58f8f7fb30690b5f3f067574e318d609a01613a2a14351e"
-
-The file doesn't exist on the local repo:
-
-    $ ls ../$ID
-    ls: ../$ID: No such file or directory
-
-however I can create a link to access that file on the remote repo.
-First I create a needed dir:
-
-    $ mkdir ../.git/annex/objects/Wz/6P/SHA256-s16898930--43679c67cd968243f58f8f7fb30690b5f3f067574e318d609a01613a2a14351e/
-
-Then I link to the remote file:
-
-    $ ln -s /mnt/usb_drive/repo_folder/$ID ../$ID
-
-now I can open the file in the laptop repo.
-
-
-I think it could be easy to implement. Maybe It's a naive approach, but looks apealing.
-Checking if it's a real file or a link shouldn't impact on performance.
-The limitation is that it would work only with remote repos on local dirs
-
-Also allows you to have one directory structure like AFS or other distributed FS. If the file is not local I go to the remote server. 
-Which is great for apps like Picasa, Itunes, and friends that depends on the file location.
-
-> This is a duplicate of [[union_mounting]]. So closing it: [[done]]. 
-> 
-> It's a good idea, but making sure git-annex correctly handles these links in all cases is a subtle problem that has not yet been tackled. --[[Joey]]
diff --git a/doc/todo/make___34__itemdate__34___valid_importfeed_template_option.mdwn b/doc/todo/make___34__itemdate__34___valid_importfeed_template_option.mdwn
deleted file mode 100644
index 9b6f6ce7c..000000000
--- a/doc/todo/make___34__itemdate__34___valid_importfeed_template_option.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-Some podcasts don't include a sortable date as the first thing in their episode title, which makes listening to them in order challenging if not impossible.
-
-The date the item was posted is part of the RSS standard, so we should parse that and provide a new importfeed template option "itemdate".
-
-(For the curious, I tried "itemid" thinking that might give me something close, but it doesn't. I used --template='${feedtitle}/${itemid}-${itemtitle}${extension}' and get:
-
-    http___openmetalcast.com__p_1163-Open_Metalcast_Episode__93__Headless_Chicken.ogg
-
-or
-
-    http___www.folkalley.com_music_podcasts__name_2013_08_21_alleycast_6_13.mp3-Alleycast___06.13.mp3
-
-that "works" but is ugly :)
-
-Would love to be able to put a YYYYMMDD at the beginning and then the title.
-
-> [[done]]; itempubdate will use form YYYY-MM-DD (or the raw date string
-> if the feed does not use a parsable form). --[[Joey]]
diff --git a/doc/todo/make___34__itemdate__34___valid_importfeed_template_option/comment_1_9fa523d1eabb6e029a91413770e9af72._comment b/doc/todo/make___34__itemdate__34___valid_importfeed_template_option/comment_1_9fa523d1eabb6e029a91413770e9af72._comment
deleted file mode 100644
index c9cf2ba51..000000000
--- a/doc/todo/make___34__itemdate__34___valid_importfeed_template_option/comment_1_9fa523d1eabb6e029a91413770e9af72._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://grossmeier.net/"
- nickname="greg"
- subject="Without knowing Haskell"
- date="2014-04-06T04:55:31Z"
- content="""
-Maybe this just requires adding:
-
-    , fieldMaybe \"itemdate\" $ getFeedPubDate $ item i
-
-on line 214 in Command/ImportFeed.hs ??
-
-It is supported by [Text.Feed.Query](http://hackage.haskell.org/package/feed-0.3.9.2/docs/Text-Feed-Query.html)
-
-I have no haskell dev env so I can't test this, but if my suggestion is true, I might set one up :)
-"""]]
diff --git a/doc/todo/make___34__itemdate__34___valid_importfeed_template_option/comment_2_9090bb66713f48fbdd1e2a3f1292b7ba._comment b/doc/todo/make___34__itemdate__34___valid_importfeed_template_option/comment_2_9090bb66713f48fbdd1e2a3f1292b7ba._comment
deleted file mode 100644
index 8ebc5fcd7..000000000
--- a/doc/todo/make___34__itemdate__34___valid_importfeed_template_option/comment_2_9090bb66713f48fbdd1e2a3f1292b7ba._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.244"
- subject="comment 2"
- date="2014-04-07T19:51:27Z"
- content="""
-https://github.com/sof/feed/issues/6
-"""]]
diff --git a/doc/todo/makefile:_respect___36__PREFIX.mdwn b/doc/todo/makefile:_respect___36__PREFIX.mdwn
deleted file mode 100644
index 995ef809f..000000000
--- a/doc/todo/makefile:_respect___36__PREFIX.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-The `Makefile` should respect a `PREFIX` passed on the commandline so git-annex can be installed in (say) `$HOME`.
-
-Simple patch:
-
-[[!format diff """
-diff --git a/Makefile b/Makefile
-index b8995b2..5b1a6d4 100644
---- a/Makefile
-+++ b/Makefile
-@@ -3,7 +3,7 @@ all=git-annex $(mans) docs
-
- GHC?=ghc
- GHCMAKE=$(GHC) $(GHCFLAGS) --make
--PREFIX=/usr
-+PREFIX?=/usr
- CABAL?=cabal # set to "./Setup" if you lack a cabal program
-
- # Am I typing :make in vim? Do a fast build.
-"""]]
-
---[[anarcat]]
-
-> [[done]] --[[Joey]]
-
-> > thanks! ;) --[[anarcat]]
diff --git a/doc/todo/mdwn2man:_make_backticks_bold.mdwn b/doc/todo/mdwn2man:_make_backticks_bold.mdwn
deleted file mode 100644
index 21707a309..000000000
--- a/doc/todo/mdwn2man:_make_backticks_bold.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-The traditionnal way of marking commandline flags in a manpage is with a `.B` (for Bold, I guess). It doesn't seem to be used by mdwn2man, which makes the manpage look a little more dull than it could.
-
-The following patch makes those options come out more obviously:
-
-[[!format diff """
-diff --git a/Build/mdwn2man b/Build/mdwn2man
-index ba5919b..7f819ad 100755
---- a/Build/mdwn2man
-+++ b/Build/mdwn2man
-@@ -8,6 +8,7 @@ print ".TH $prog $section\n";
-
- while (<>) {
-        s{(\\?)\[\[([^\s\|\]]+)(\|[^\s\]]+)?\]\]}{$1 ? "[[$2]]" : $2}eg;
-+       s/\`([^\`]*)\`/\\fB$1\\fP/g;
-        s/\`//g;
-        s/^\s*\./\\&./g;
-        if (/^#\s/) {
-"""]]
-
-I tested it against the git-annex manpage and it seems to work well. --[[anarcat]]
-
-> [[done]], thanks --[[Joey]]
diff --git a/doc/todo/network_remotes.mdwn b/doc/todo/network_remotes.mdwn
deleted file mode 100644
index 42efa832f..000000000
--- a/doc/todo/network_remotes.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-Support for remote git repositories (ssh:// specifically can be made to
-work, although the other end probably needs to have git-annex
-installed..)
-
-[[done]], at least get and put work..
diff --git a/doc/todo/nicer_whereis_output.mdwn b/doc/todo/nicer_whereis_output.mdwn
deleted file mode 100644
index 871eee01a..000000000
--- a/doc/todo/nicer_whereis_output.mdwn
+++ /dev/null
@@ -1,100 +0,0 @@
-We had some informal discussions on IRC about improving the output of the `whereis` command.
-
-[[!toc levels=2]]
-
-First version: columns
-======================
-
-[[mastensg]] started by implementing a [simple formatter](https://gist.github.com/mastensg/6500982) that would display things in columns [screenshot](http://www.ping.uio.no/~mastensg/whereis.png)
-
-Second version: Xs
-==================
-
-After some suggestions from [[joey]], [[mastensg]] changed the format slightly ([screenshot](http://www.ping.uio.no/~mastensg/whereis2.png)):
-
-[[!format txt """
-17:01:34 <joeyh> foo
-17:01:34 <joeyh> |bar
-17:01:34 <joeyh> ||baz (untrusted)
-17:01:34 <joeyh> |||
-17:01:34 <joeyh> XXx 3?  img.png
-17:01:36 <joeyh> _X_ 1!  bigfile
-17:01:37 <joeyh> XX_ 2   zort
-17:01:39 <joeyh> __x 1?! maybemissing
-17:02:09 * joeyh does a s/\?/+/ in the above
-17:02:24 <joeyh> and decrements the counters for untrusted
-17:03:37 <joeyh> __x 0+! maybemissing
-"""]]
-
-Third version: incremental
-==========================
-
-Finally, [[anarcat]] worked on making it run faster on large repositories, in a [fork](https://gist.github.com/anarcat/6502988) of that first gist. Then paging was added (so headers are repeated). 
-
-Fourth version: tuning and blocked
-==================================
-
-[[TobiasTheViking]] provided some bugfixes, and the next step was to implement the trusted/untrusted detection, and have a counter.
-
-This required more advanced parsing of the remotes, and instead of starting to do some JSON parsing, [[anarcat]] figured it was time to learn some Haskell instead.
-
-Current status: needs merge
-===========================
-
-So right now, the most recent version of the python script is in [anarcat's gist](https://gist.github.com/anarcat/6502988) and works reasonably well. However, it doesn't distinguish between trusted and untrusted repos and so on.
-
-Furthermore, we'd like to see this factored into the `whereis` command directly. A [raw.hs](http://codepad.org/miVJb5oK) file has been programmed by `mastensg`, and is now available in the above gist. It fits the desired output and prototypes, and has been `haskellized` thanks to [[guilhem]].
-
-Now we just need to merge those marvelous functions in `Whereis.hs` - but I can't quite figure out where to throw that code, so I'll leave it to someone more familiar with the internals of git-annex. The most recent version is still in [anarcat's gist](https://gist.github.com/anarcat/6502988). --[[anarcat]]
-
-Desired output
---------------
-
-The output we're aiming for is:
-
-    foo
-    |bar
-    ||baz (untrusted)
-    |||
-    XXx 2+  img.png
-    _X_ 1!  bigfile
-    XX_ 2   zort
-    __x 0+! maybemissing
-
-Legend:
-
- * `_` - file missing from repo
- * `x` - file may be present in untrusted repo
- * `X` - file is present in trusted repo
- * `[0-9]` - number of copies present in trusted repos
- * `+` - indicates there may be more copies present
- * `!` - indicates only one copy is left
-
-Implementation notes
---------------------
-
-[[!format txt """
-20:48:18 <joeyh> if someone writes me a headerWhereis ::  [(RemoteName, TrustLevel)] -> String  and a formatWhereis :: [(RemoteName, TrustLevel, UUID)] -> [UUD] -> FileName -> String   , I can do the rest ;)
-20:49:22 <joeyh> make that second one formatWhereis :: [(RemoteName, TrueLevel, Bool)] -> FileName -> String
-20:49:37 <joeyh> gah, typos
-20:49:45 <joeyh> suppose you don't need the RemoteName either
-"""]]
-
-> So, I incorporated this, in a new remotes command.
-> Showing all known repositories seemed a bit much
-> (I have 30-some known repositories in some cases),
-> so just showing configured remotes seems a good simplification.
-> [[done]]
-> --[[Joey]]
-
-> > I would have prefered this to be optional since I don't explicitely configure all remotes in git, especially if I can't reach them all the time (e.g. my laptop). It seems to me this should at least be an option, but I am confused as to why `Remote.List.remoteList` doesn't list all remotes the same way `Remote.remote_list` does... Also, it's unfortunate that the +/!/count flags have been dropped, it would have been useful... Thanks for the merge anyways! --[[done]]
-> > 
-> > The more I look at this, the more i think there are a few things wrong with the new `remotes` command.
-> > 
-> >  1. the name is confusing: being a git addict, I would expect the `git annex remote` command to behave like the `git remote` command: list remotes, add remotes, remove remotes and so on. it would actually be useful to have such a command (which would replace `initremote`, I guess). i recommend replacing the current `whereis` command, even if enabled through a special flag
-> > 
-> >  2. its behavior is inconsistent with other git annex commands: `git annex status`, for example, lists information about all remotes, regardless of whether they are configured in git. `remotes` (whatever it's called), should do the same, or at least provide an option to allow the user to list files on all remotes. The way things stand, there is no way to list files on non-git remotes, even if they are added explicitely as a remote, if the remote is not actually reachable: the files are just marked as absent (even thought `whereis` actually finds them). i recommend showing all remotes regardless, either opt-in or opt-out using a flag.
-> > 
-> >  3. having the `!` flag, at least, would be useful because it would allow users to intuitively grep for problematic files without having to learn extra syntax. same with + and having an explicit count.
-> > 
-> > thanks. --[[anarcat]]
diff --git a/doc/todo/object_dir_reorg_v2.mdwn b/doc/todo/object_dir_reorg_v2.mdwn
deleted file mode 100644
index 49666ddc7..000000000
--- a/doc/todo/object_dir_reorg_v2.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-Several things suggest now would be a good time to reorgaize the object
-directory. This would be annex.version=2. It will be slightly painful for
-all users, so this should be the *last* reorg in the forseeable future.
-
-1. Remove colons from filenames, for [[bugs/fat_support]]
-
-2. Add hashing, since some filesystems do suck (like er, fat at least :)
-   [[forum/hashing_objects_directories]]
-   (Also, may as well hash .git-annex/* while at it -- that's what
-   really gets big.)
-
-3. Add filesize metadata for [[bugs/free_space_checking]]. (Currently only
-   present in WORM, and in an ad-hoc way.)
-
-4. Perhaps use a generic format that will allow further metadata to be
-   added later. For example,
-   "bSHA1,s101111,kf3101c30bb23467deaec5d78c6daa71d395d1879"
-
-   (Probably everything after ",k" should be part of the key, even if it
-   contains the "," separator character. Otherwise an escaping mechanism
-   would be needed.)
-
-[[done]] now! 
-
-Although [[bugs/free_space_checking]] is not quite there --[[Joey]] 
diff --git a/doc/todo/object_dir_reorg_v2/comment_1_ba03333dc76ff49eccaba375e68cb525._comment b/doc/todo/object_dir_reorg_v2/comment_1_ba03333dc76ff49eccaba375e68cb525._comment
deleted file mode 100644
index 261c2a51f..000000000
--- a/doc/todo/object_dir_reorg_v2/comment_1_ba03333dc76ff49eccaba375e68cb525._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-03-16T01:16:48Z"
- content="""
-If you support generic meta-data, keep in mind that you will need to do conflict resolution. Timestamps may not be synched across all systems, so keeping a log of old metadata could be used, sorting by history and using the latest. Which leaves the situation of two incompatible changes. This would probably mean manual conflict resolution. You will probably have thought of this already, but I still wanted to make sure this is recorded. -- RichiH
-"""]]
diff --git a/doc/todo/object_dir_reorg_v2/comment_2_81276ac309959dc741bc90101c213ab7._comment b/doc/todo/object_dir_reorg_v2/comment_2_81276ac309959dc741bc90101c213ab7._comment
deleted file mode 100644
index 9785f1989..000000000
--- a/doc/todo/object_dir_reorg_v2/comment_2_81276ac309959dc741bc90101c213ab7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2011-03-16T01:19:25Z"
- content="""
-Hmm, I added quite a few comments at work, but they are stuck in moderation. Maybe I forgot to log in before adding them. I am surprised this one appeared immediately. -- RichiH
-"""]]
diff --git a/doc/todo/object_dir_reorg_v2/comment_3_79bdf9c51dec9f52372ce95b53233bb2._comment b/doc/todo/object_dir_reorg_v2/comment_3_79bdf9c51dec9f52372ce95b53233bb2._comment
deleted file mode 100644
index 886941be7..000000000
--- a/doc/todo/object_dir_reorg_v2/comment_3_79bdf9c51dec9f52372ce95b53233bb2._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-03-15T14:08:41Z"
- content="""
-What is the potential time-frame for this change? As I am not using git-annex for production yet, I can see myself waiting to avoid any potential hassle.
-
-Supporting generic metadata seems like a great idea. Though if you are going this path, wouldn't it make sense to avoid metastore for mtime etc and support this natively without outside dependencies?
-
--- RichiH
-"""]]
diff --git a/doc/todo/object_dir_reorg_v2/comment_4_93aada9b1680fed56cc6f0f7c3aca5e5._comment b/doc/todo/object_dir_reorg_v2/comment_4_93aada9b1680fed56cc6f0f7c3aca5e5._comment
deleted file mode 100644
index 475359abb..000000000
--- a/doc/todo/object_dir_reorg_v2/comment_4_93aada9b1680fed56cc6f0f7c3aca5e5._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 4"
- date="2011-03-16T03:22:45Z"
- content="""
-Well, I spent a few hours playing this evening in the 'reorg' branch in git. It seems to be shaping up pretty well; type-based refactoring in haskell makes these kind of big systematic changes a matter of editing until it compiles. And it compiles and test suite passes. But, so far I've only covered 1. 3. and 4. on the list, and have yet to deal with upgrades.
-
-I'd recommend you not wait before using git-annex. I am committed to provide upgradability between annexes created with all versions of git-annex, going forward. This is important because we can have offline archival drives that sit unused for years. Git-annex will upgrade a repository to current standard the first time it sees it, and I hope the upgrade will be pretty smooth. It was not bad for the annex.version 0 to 1 upgrade earlier. The only annoyance with upgrades is that it will result in some big commits to git, as every symlink in the repo gets changed, and log files get moved to new names.
-
-(The metadata being stored with keys is data that a particular backend can use, and is static to a given key, so there are no merge issues (and it won't be used to preserve mtimes, etc).)
-"""]]
diff --git a/doc/todo/object_dir_reorg_v2/comment_5_821c382987f105da72a50e0a5ce61fdc._comment b/doc/todo/object_dir_reorg_v2/comment_5_821c382987f105da72a50e0a5ce61fdc._comment
deleted file mode 100644
index 2032bce3c..000000000
--- a/doc/todo/object_dir_reorg_v2/comment_5_821c382987f105da72a50e0a5ce61fdc._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 5"
- date="2011-03-16T15:51:30Z"
- content="""
-Hashing & segmenting seems to be around the corner, which is nice :)
-
-Is there a chance that you will optionally add mtime to your native metadata store? If yes, I'd rather wait for v2 to start with the native system from the start. If not, I will probably set it up tonight.
-
-PS: While posting from work, my comments are held for moderation once again. I am somewhat confused as to why this happens when I can just submit directly from home. And yes, I am using the same auth provider and user in both cases.
-"""]]
diff --git a/doc/todo/object_dir_reorg_v2/comment_6_8834c3a3f1258c4349d23aff8549bf35._comment b/doc/todo/object_dir_reorg_v2/comment_6_8834c3a3f1258c4349d23aff8549bf35._comment
deleted file mode 100644
index ff86e3970..000000000
--- a/doc/todo/object_dir_reorg_v2/comment_6_8834c3a3f1258c4349d23aff8549bf35._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 6"
- date="2011-03-16T16:32:52Z"
- content="""
-The mtime cannot be stored for all keys. Consider a SHA1 key. The mtime is irrelevant; 2 files with different mtimes, when added to the SHA1 backend, should get the same key.
-
-Probably our spam filter doesn't like your work IP.
-"""]]
diff --git a/doc/todo/object_dir_reorg_v2/comment_7_42501404c82ca07147e2cce0cff59474._comment b/doc/todo/object_dir_reorg_v2/comment_7_42501404c82ca07147e2cce0cff59474._comment
deleted file mode 100644
index fc866c57a..000000000
--- a/doc/todo/object_dir_reorg_v2/comment_7_42501404c82ca07147e2cce0cff59474._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 7"
- date="2011-03-16T21:05:38Z"
- content="""
-Ah, OK. I assumed the metadata would be attached to a key, not part of the key. This seems to make upgrades/extensions down the line harder than they need to be, but you are right that this way, merges are not, and never will be, an issue.
-
-Though with the SHA1 backend, changing files can be tracked. This means that tracking changes in mtime or other is possible. It also means that there are potential merge issues. But I won't argue the point endlessly. I can accept design decisions :)
-
-The prefix at work is from a university netblock so yes, it might be on a few hundred proxy lists etc.
-"""]]
diff --git a/doc/todo/optinally_transfer_file_unencryptedly.mdwn b/doc/todo/optinally_transfer_file_unencryptedly.mdwn
deleted file mode 100644
index ef27dc521..000000000
--- a/doc/todo/optinally_transfer_file_unencryptedly.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-I have a git-annex repository on a NSLU 2, and transfers are much slower over ssh compared to unencrypted transfers (no wonder at that CPU speed). For the files that I am transferring, no encryption would be necessary. Unfortunately, ssh in Debian does not support "-c none" to disable encryption.
-
-It would be nice if git-annex would have a way of conveniently transferring files in another way than SSH. I’m not sure what a good way would be – maybe launching a one-shot HTTP-server on the sending end? Haskell libraries for that would be available... Of course it is not always the case that the host reachable with "ssh foo" is also reachable via TCP at "foo:1234"... And there are surely more problem. But still, it would be nice :-)
-
-> Setting `remote.name.annex-rsync-transport = rsh` will now
-> make rsync special remotes use rsh instead of ssh. [[done]]
diff --git a/doc/todo/optinally_transfer_file_unencryptedly/comment_1_4be47e7ac85d0f4e7029a96b615545a7._comment b/doc/todo/optinally_transfer_file_unencryptedly/comment_1_4be47e7ac85d0f4e7029a96b615545a7._comment
deleted file mode 100644
index 948845b23..000000000
--- a/doc/todo/optinally_transfer_file_unencryptedly/comment_1_4be47e7ac85d0f4e7029a96b615545a7._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="guilhem"
- ip="129.16.20.212"
- subject="rsh?"
- date="2013-04-09T16:11:50Z"
- content="""
-I don't use it myself, but rsync can be used with others remote shells, among which rsh supports unencrypted streams. You probably want to set up a secure authorization mechanism to deny access to intruders, and for that kerberos comes to the rescue :-) I didn't try the combination, but it should work over git-annex already.
-"""]]
diff --git a/doc/todo/preferred_content_numcopies_check.mdwn b/doc/todo/preferred_content_numcopies_check.mdwn
deleted file mode 100644
index 2e007460f..000000000
--- a/doc/todo/preferred_content_numcopies_check.mdwn
+++ /dev/null
@@ -1,86 +0,0 @@
-The assistant and git annex sync --content do not try to proactively
-download content that is not otherwise wanted in order to get numcopies
-satisfied. (Unlike get --auto, which does take numcopies into account.)
-
-Should these automated systems try to proactively satisfy numcopies? I
-don't feel they should. It could result in surprising results. For example,
-a transfer repository, which is of limited size, could start being filled
-up with lots of content that all clients have, just because numcopies was
-set to a larger number than the total number of clients. Another example,
-a source repository on eg an Android phone, should never have content in it
-that was not created on that device.
-
-However, it would make sense for some specific 
-types of repositories to proactively get content to satisfy numcopies. 
-Currently some types of repositories use "or (not copies=semitrusted+:1)",
-to ensure that if the only copy of a file is on a dead repository, they
-will try to get that file before the repo goes away. This is done
-by client repositories, and backup, and archive. Probably the same set
-would make sense to proactively satisfy numcopies.
-
-So, a new type of preferred content expression is called for. Such as, for
-example, "numcopiesneeded=1". Which indicates that at least 1 more copy 
-is needed to satifsy numcopies. 
-
-(Note that it should only count semittrusted and higher trust
-level repos as satisfying numcopies.)
-
-But, preferred content expressions can only operate on info stored in the
-git repo, or they will fail to be stable. Ie, repo A needs to be able to
-calculate whether a file is preferred content by repo B and get the same
-result as when repo B calculates that.
-
-numcopies is currently configured in 3 places:
-
-* .git/config `annex.numcopies` (global, stored only locally)
-* .gitattributes `annex.numcopies` (per file, stored in git repo)
-* --numcopies (not relevant)
-
-So, need to add a global numcopies setting that is stored in the git repo.
-That could either be a file in the git-annex branch, or just
-`* annex.numcopies=2` in the toplevel .gitattributes. Note that the
-assistant needs to be able to query and set it, which I think argues
-against using .gitattributes for it. Also arguing against that is that the
-.git/config numcopies valie applies even to objects with no file in the
-work tree, which gitattributes settings do not.
-
-Conclusion:
-
-* Add to the git-annex branch a numcopies file that holds the global
-  numcopies default if present. **done**
-* Modify the assistant to use it when configuring numcopies. **done**
-* To deprecate .git/config's annex.numcopies, only make it take effect
-  when there is no numcopies file in the git-annex branch. **done**
-* Add "numcopiesneeded=N" preferred content expression using the git-annex
-  branch numcopies setting, overridden by any .gitattributes numcopies setting
-  for a particular file. It should ignore the other ways to specify
-  numcopies, particularly git config annex.numcopies. **done**
-* Make the repo groups that currently end with "or (not copies=semitrusted+:1)"
-  to instead end with "or numcopiesneeded=1" **done**
-* See if "numcopiesneeded=N" can check .gitattributes without getting
-  a lot slower. If now, perhaps add a "numcopiesneededaccurate=N" that
-  checks it. **done**
-
-[[done]] 
-
-## Stability analysis
-
-If a remote prefers eg, "blah or numcopiesneeded=1", and
-file $foo does not match blah, but needs more copies, then then the
-expression will match.
-
-So, git-annex will get $foo, adding a copy. Which means that the 
-numcopiesneeded=1 will no longer match, so the file is no longer wanted
-now that it has been downloaded.
-
-Now there are two cases for what can happen:
-
-* git-annex tries to drop $foo, but fails because it cannot find enough
-  other copies
-* git-annex copies $foo to some other remote that wants it, and then
-  manages to drop $foo from the local remote.
-
-This seems ok. Files flow through repos and they act like transfer
-repos when there are not enough copies.
-
---[[Joey]]
diff --git a/doc/todo/pushpull.mdwn b/doc/todo/pushpull.mdwn
deleted file mode 100644
index 6828b35b2..000000000
--- a/doc/todo/pushpull.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
---push/--pull should take a reponame and files, and push those files
-  to that repo; dropping them from the current repo
-
-[[done]] (move --from/--to)
diff --git a/doc/todo/quvi_0.9_support.mdwn b/doc/todo/quvi_0.9_support.mdwn
deleted file mode 100644
index 36280452a..000000000
--- a/doc/todo/quvi_0.9_support.mdwn
+++ /dev/null
@@ -1,8 +0,0 @@
-quvi 0.9 has a completely different interface; git-annex needs to be made
-to detect and use it.
-
-I have already fixed the worst problem, which caused git-annex addurl to
-think that every url was a valid quvi url. --[[Joey]]
-
-> [[done]], 0.9 is supported, although the version is detected at build
-> time. --[[Joey]]
diff --git a/doc/todo/rsync.mdwn b/doc/todo/rsync.mdwn
deleted file mode 100644
index 3353f19c4..000000000
--- a/doc/todo/rsync.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-Transferring a file from a ssh:// remote should use rsync to allow resuming
-of a prior transfer.
-
-[[done]]
diff --git a/doc/todo/separate_rsync_bwlimit_options_for_upload_and_download.mdwn b/doc/todo/separate_rsync_bwlimit_options_for_upload_and_download.mdwn
deleted file mode 100644
index 2b93ad2d6..000000000
--- a/doc/todo/separate_rsync_bwlimit_options_for_upload_and_download.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-The bandwidth for upload and download are often different.  It would be useful to have different settings for upload and download limits.
-As it is, I have to keep changing annex-rsync-options options between uploads and downloads.
-
-> [[done]] --[[Joey]]
diff --git a/doc/todo/special_remote_for_amazon_glacier.mdwn b/doc/todo/special_remote_for_amazon_glacier.mdwn
deleted file mode 100644
index 9b8b9d74e..000000000
--- a/doc/todo/special_remote_for_amazon_glacier.mdwn
+++ /dev/null
@@ -1,30 +0,0 @@
-Amazon's new glacier service would be a nice special remote to support for
-long-term archival.
-
-The main difficulty is that glacier is organized into vaults, and accessing
-a file in a vault takes ~4 hours. A naive implementation would make `git
-annex get` wait for 4 hours, which is certainly not reasonable.
-
-One approach I am pondering is to make each glacier vault a separate
-special remote. You could then request git-annex to spin up a remote, and
-come back later, and be able to access the data stored in it (need to check
-if glacier would also allow adding new data to it then). This is
-conceptually similar to using git-annex with offline removable drives,
-except with glacier, you have a controllable robot to get them plugged in. :)
-
-Ideally, git-annex would arrange for glacier to send it a message when the
-vault becomes available, and the user could queue a list of commands to
-run, or files to transfer, at that point.
-
---[[Joey]]
-
-> [[done]]! --[[Joey]]
-
------
-
-> In the coming months, Amazon S3 will introduce an option that will allow customers to seamlessly move data between Amazon S3 and Amazon Glacier based on data lifecycle policies.
-
--- <http://aws.amazon.com/glacier/faqs/#How_should_I_choose_between_Amazon_Glacier_and_Amazon_S3>
-
->> They did, but it's IMHO not very useful for git-annex. It's rather
->> intended to allow aging S3 storage out to Glacier. --[[Joey]] 
diff --git a/doc/todo/special_remote_for_amazon_glacier/comment_1_68f129441eefcbfebf7a9db680f52759._comment b/doc/todo/special_remote_for_amazon_glacier/comment_1_68f129441eefcbfebf7a9db680f52759._comment
deleted file mode 100644
index 68593be42..000000000
--- a/doc/todo/special_remote_for_amazon_glacier/comment_1_68f129441eefcbfebf7a9db680f52759._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://mike.magin.org/"
- nickname="mmagin"
- subject="comment 1"
- date="2012-09-14T04:19:53Z"
- content="""
-When I first heard about Glacier, it sounded great for a cheap backup copy, and I was thinking about writing a \"hook\" remote, but once I read some better analysis of the pricing (e.g. [[http://www.daemonology.net/blog/2012-09-04-thoughts-on-glacier-pricing.html]]) I rapidly lost interest.
-"""]]
diff --git a/doc/todo/special_remote_for_amazon_glacier/comment_2_c5eeaf8ceee414fa0379831ca52e290c._comment b/doc/todo/special_remote_for_amazon_glacier/comment_2_c5eeaf8ceee414fa0379831ca52e290c._comment
deleted file mode 100644
index 701047f91..000000000
--- a/doc/todo/special_remote_for_amazon_glacier/comment_2_c5eeaf8ceee414fa0379831ca52e290c._comment
+++ /dev/null
@@ -1,7 +0,0 @@
-[[!comment format=mdwn
- username="basak"
- subject="comment 2"
- date="2012-09-21T22:21:04Z"
- content="""
-I've created a glacier command line interface that integrates with git-annex [here](https://github.com/basak/glacier-cli), currently using the hook special remote mechanism. To get around the time delay, operations which require a job submission will submit the job and then fail. Retrying again four hours later should then succeed. It seems to work pretty well with git-annex.
-"""]]
diff --git a/doc/todo/speed_up_fsck.mdwn b/doc/todo/speed_up_fsck.mdwn
deleted file mode 100644
index 5d5e867f8..000000000
--- a/doc/todo/speed_up_fsck.mdwn
+++ /dev/null
@@ -1,40 +0,0 @@
-moving to the git-annex branch has slowed down fsck worse than most
-commands. Actually, some commands have sped up, while others like get
-are slightly slower but are swamped by the normal runtime. 
-
-For fsck though, it has to pull each file's location log info out of git.
-And, it's typically run on the entire tree.
-
-Another slow one in `git annex copy --from`.
-
-It would be possible to run a single `git cat-file --batch` and pass it
-sha1s of location logs for file that is going to be fsked (gotten via
-`read-tree`). Then just read its output until the next requested sha1 to
-chunk it, and pass this in to fsck in a closure.
-
-The difficulty, besides writing that is that everything that works with
-location logs now reads them out of git, would need to find a way to
-provide the info on a side channel of some sort.
-
-If this is implemented, the same infrastructure could be used for other
-commands like whereis and add. --[[Joey]]
-
-> Updated plan:
-> 
-> Run `git ls-file --batch`, and cache its stdin and out handles in Branch
-> state.
-> 
-> To see a git-annex branch file, send it something like
-> "git-annex:uuid.log", and read the content fron stdout handle.
-> 
-> To detect the end of content, send "TOKEN\n", and look for 
-> "TOKEN missing" in its output. A good choice for TOKEN is anything
-> that will never exist in the repo; 40 0's would be a fairly good choice,
-> but even better seems to be something completely invalid and impossible
-> to have as a sha1 or filename or ref: "".
-> 
-> Hmm, except that's actually an error message sent to stderr. Unless
-> stderr is connected to stdout, it might be better to look for a known,
-> empty object. Could just add a git-annex:empty file to that end.
-
-[[done]] --[[Joey]] 
diff --git a/doc/todo/support-non-utf8-locales.mdwn b/doc/todo/support-non-utf8-locales.mdwn
deleted file mode 100644
index da40118d5..000000000
--- a/doc/todo/support-non-utf8-locales.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-Currenty, git-annex forces output, particularly of filenames, in a utf-8
-locale.
-
-Note that this does not mean it cannot be used with filenames in other
-encodings. git-annex is entirely encoding agnostic when it comes to 
-manipulating filenames. It just *displays* their names always converted to
-utf-8, which  may not look right when you have a non-utf8 locale.
-
-This had to be done to work around some bugs with haskell's handling
-of filename encodings. In particular,
-
-* [[bugs/unhappy_without_UTF8_locale]]: haskell crashes when told to output 
-  a string with characters > 255 in a non-utf8 locale.
-* [[bugs/problems_with_utf8_names]]: On many OSs, haskell expects
-  non-decoded raw char8 in FilePaths. In order to display a filename,
-  though, it needs to first be decoded, and git-annex currently assumes
-  it was encoded as utf8.
-
-git-annex's behavior is unlikely to improve much until haskell's
-support for utf8 filenames improves. --[[Joey]]
-
-> [[done]] -- I just turned off all encoding handling on stdout and stderr,
-> which avoids these problems nicely. Git-annex now displays just what it
-> input, at least on platforms where haskell does not decode unicode in
-> FilePaths. This will later be a problem when it gets localized, but for
-> now works great. --[[Joey]]
diff --git a/doc/todo/support_for_lossy_remotes.mdwn b/doc/todo/support_for_lossy_remotes.mdwn
deleted file mode 100644
index 23083b2d7..000000000
--- a/doc/todo/support_for_lossy_remotes.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-I'm curious if there's a possibility to support lossy remotes. It may be handy to support syncing to special remotes that do lossy compression on the files (e.g., videos and images). For example, one could imagine having a YouTube special remote that only syncs video files. The original files wouldn't be available for download due to the transcoding and compression that YouTube does, so they wouldn't count towards the number of copies. In this YouTube example, the user gains:
-
-1. an online place that their videos are available from
-2. a worst-case scenario "backup"
-3. a remote that they could download smaller video files
-
-> [[done]]; lossy remotes are supported as seen with `git annex addurl
-> --fast` and also with the new addurl support for using quvi to get
-> videos fro youtube. Just make a key with a URL or something in it, and 
-> no size or checksum, and any content will be assumed to be the right
-> content. --[[Joey]]
diff --git a/doc/todo/support_for_lossy_remotes/comment_1_f5cd9f9deab13ab2d2290ad763906dd3._comment b/doc/todo/support_for_lossy_remotes/comment_1_f5cd9f9deab13ab2d2290ad763906dd3._comment
deleted file mode 100644
index 1e895944c..000000000
--- a/doc/todo/support_for_lossy_remotes/comment_1_f5cd9f9deab13ab2d2290ad763906dd3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.90"
- subject="comment 1"
- date="2013-07-16T19:16:54Z"
- content="""
-There is already one example of a lossy remote: If you use `git annex addurl --relaxed` it generates a key that just uses the url, without its size. When retreiving such a key, any content will be accepted.
-"""]]
diff --git a/doc/todo/support_for_writing_external_special_remotes.mdwn b/doc/todo/support_for_writing_external_special_remotes.mdwn
deleted file mode 100644
index 1732f77ea..000000000
--- a/doc/todo/support_for_writing_external_special_remotes.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-It would be good to have something in between the hook special remote and
-the built-in special remotes. The hook is easy to set up, but its simple
-interface misses some features that a more full-features interface could
-provide to a third-party program that wants to provide the best possible
-special remote it can w/o being written in haskell:
-
-* No way to send progress updates when uploading, so no progress bars for uploads from hook special remotes in the webapp.
-* No way to verify the `initremote` parameters include all needed configuration, and do any initalization needed.
-* No way to query and/or set the remote.log while it's running. (Well, technically, `git annex enableremote` can set values..)
-* No way to store per-key information to the git-annex branch.
-* No (easy) way to split files into chunks.
-
-Some of these features could be added to git-annex as subcommands. Which would
-improve the general programmability and flexability of git-annex. OTOH,
-running `git-annex upload-progress` repeatedly is pretty ugly. Or the
-interface could provide a channel for the program and git-annex to
-communicate back and forth on. Maybe a mix of the two?
-
-A final feature such an interface should provide is the ability to drop a
-program into PATH and have it just work, without the user needing to do any
-configuration beyond `initremote`. So, `git annex initremote foo type=$bar`
-should look for `git-annex-remote-$bar` in PATH if that's not a built-in
-special remote name.
-
---[[Joey]]
-
-[[done]]
diff --git a/doc/todo/support_fsck_in_bare_repos.mdwn b/doc/todo/support_fsck_in_bare_repos.mdwn
deleted file mode 100644
index 32ced467e..000000000
--- a/doc/todo/support_fsck_in_bare_repos.mdwn
+++ /dev/null
@@ -1,17 +0,0 @@
-What is says on the tin:
-
-    22:56:54 < RichiH> joeyh_: by the way, i have been thinking about fsck on bare repos
-    22:57:37 < RichiH> joeyh_: the best i could come with is to have a bare and a non-bare access the same repo store
-    22:58:00 < RichiH> joeyh_: alternatively, with the SHA* backend, you have all the information to verify that the local data is correct
-    22:58:41 < RichiH> and verifying that would already be a plus. if there  really _is_ a problem, having the SHA is enough to track issues down
-    23:09:50 < joeyh_> oh, I think I have code that fsck could use on bare repos already.. just a matter of wiring it up
-    23:10:42 < joeyh_> feel free to reopen a bug or whatever so I remember.. the unused command's branch content enumeration could be used in a bare repo
-    23:14:51 < joeyh_> unused/dropunused could work in bare repos too btw
-
-> Also `status`'s total annex keys/size could be handled for bare repos. --[[Joey]] 
-
->> Fsck is done. Rest not done yet. --[[Joey]]
-
->>> all [[done]]! --[[Joey]] 
-
-[[!meta title="support unused, dropunused in bare repos"]]
diff --git a/doc/todo/symlink_farming_commit_hook.mdwn b/doc/todo/symlink_farming_commit_hook.mdwn
deleted file mode 100644
index 3e93cb34b..000000000
--- a/doc/todo/symlink_farming_commit_hook.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-TODO: implement below
-
-git-annex does use a lot of symlinks. Specicially, relative symlinks,
-that are checked into git. To allow you to move those around without
-annoyance, git-annex can run as a post-commit hook. This way, you can `git mv`
-a symlink to an annexed file, and as soon as you commit, it will be fixed
-up.
-
-`git annex init` tries to set up a post-commit hook that is itself a symlink
-back to git-annex. If you want to have your own shell script in the post-commit
-hook, just make it call `git annex` with no parameters. git-annex will detect
-when it's run from a git hook and do the necessary fixups.
-
-[[done]]
diff --git a/doc/todo/symlink_git-annex_binaries_to___126____47__.local__47__bin_for_prebuilt_package.mdwn b/doc/todo/symlink_git-annex_binaries_to___126____47__.local__47__bin_for_prebuilt_package.mdwn
deleted file mode 100644
index 627143924..000000000
--- a/doc/todo/symlink_git-annex_binaries_to___126____47__.local__47__bin_for_prebuilt_package.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-Instead of changing the `PATH`, it should be possible to symlink the binaries to the `~/.local/bin` directory.
-
-Here is a script I put on the prebuilt package (its basename is unimportant but it must be placed along with the git-annex script):
-
-    #!/bin/sh
-    link="$(readlink "$0")"
-    base="$(cd "$(dirname "$0")"; cd "$(dirname "$link")"; echo "$PWD")"
-    name="$(basename "$0")"
-    exec "$base/$name" "$@"
-
-Symlink this script to `~/.local/bin/git-annex`, `~/.local/bin/git-annex-shell` and `~/.local/bin/git-annex-webapp`. on my system I have:
-
-    lrwxrwxrwx. 1 mildred mildred 36 Dec 13 12:12 git-annex -> ../opt/git-annex.linux/run-git-annex
-    lrwxrwxrwx. 1 mildred mildred 36 Dec 13 12:12 git-annex-shell -> ../opt/git-annex.linux/run-git-annex
-    lrwxrwxrwx. 1 mildred mildred 36 Dec 13 12:12 git-annex-webapp -> ../opt/git-annex.linux/run-git-annex
-
-The script will detect the installation directory using `readlink`. Both absolute and relative links works. Then it starts the correct script depending on the basename of the link.
-
-It should be possible to link the `git-annex`, `git-annex-webapp` and `git-annex-shell` scripts instead if they used `readlink` to find out the location of the prebuilt package.
-
-> I've made the scripts look at readlink, so [[done]]. 
-> --[[Joey]] 
diff --git a/doc/todo/untracked_remotes.mdwn b/doc/todo/untracked_remotes.mdwn
deleted file mode 100644
index f538c7560..000000000
--- a/doc/todo/untracked_remotes.mdwn
+++ /dev/null
@@ -1,27 +0,0 @@
-Seems that a fairly common desire in some use cases is to be able to make a
-clone of a repository and be able to get files, without updating the
-location tracking information. (And without even recording a uuid in the
-remote.log.) Use cases include wanting to have temporary
-clones without cluttering history, and centralized development where the
-developers don't care to know about one-another's systems.
-
-It seems that such an untracked repository would need to automatically
-consider itself untrusted. Is that enough to avoid losing data?
-
-> [[done]]; set remote.<name>.annex-readonly=true to prevent
-> git-annex from pushing changes to the remote, or modifying the contents
-> of the remote in any way.
-> 
-> Note that I am intentionally not making this feature be about security.
-> The remote can still tell if you're connecting to it, and indeed if it
-> really wants to, and git-annex-shell is being used on the remote, it can
-> determine your local repository's uuid.
-> 
-> This allows for some complicated setups. For example, a public repository
-> P can be a readonly remote of a clone on your laptop L, and L in turn has
-> another, non-readonly remote D on a removable drive. This allows L and D
-> to keep track of which files one-another have, without leaking this info
-> to P. But note that if L adds P as a remote, it also has to mark it
-> readonly, to avoid leaking data.
-> 
-> --[[Joey]]
diff --git a/doc/todo/untracked_remotes/comment_1_ccc743554cf9270e1db5275273b28265._comment b/doc/todo/untracked_remotes/comment_1_ccc743554cf9270e1db5275273b28265._comment
deleted file mode 100644
index bab26dc10..000000000
--- a/doc/todo/untracked_remotes/comment_1_ccc743554cf9270e1db5275273b28265._comment
+++ /dev/null
@@ -1,43 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2014-01-01T21:32:56Z"
- content="""
-Such a class of repositories would be very useful, indeed.
-
-A good name would probably be, in descending order:
-
-* ephemeral
-* volatile
-* transient
-* fleeting
-
-It would be somewhere in between 'untrusted' and 'dead'.
-
-I can see two approaches working nicely, here:
-
-1. Local location log
-2. Local location log in another branch / directory
-3. No location log
-
-In the first case, location data would be added to the local location log, but any `git annex sync` or similar would parse the location log and strip out all mentions of the UUID in question.
-This would be somewhat slower when synching, but would ensure that all operations which rely on local logs operate normally.
-
-In the second case, location data would be kept in a different location.
-This would have the benefit of a clean separation and quicker merges, but induces overhead for lookups.
-On the other hand, if those lookups are wrapped cleanly, only those functions would need to know about the different locations.
-
-In the last case, no local logs would be kept.
-
-
-All in all, I think I would prefer the first option.
-
-The one thing that's hard/impossible by design is for other remotes to strip out the data.
-As the repository would not be known to other remotes, they would simply continue the carry the data.
-This can be worked around by setting the repository to "dead".
-Ephemeral repositories would not correct "dead" info about themselves; they _would_ start behaving normally once set to trusted, semit-trusted, or untrusted, though.
-
-
-Richard
-"""]]
diff --git a/doc/todo/untracked_remotes/comment_2_48cc5d0e2282fa53625e0037a035fee3._comment b/doc/todo/untracked_remotes/comment_2_48cc5d0e2282fa53625e0037a035fee3._comment
deleted file mode 100644
index 1233a4379..000000000
--- a/doc/todo/untracked_remotes/comment_2_48cc5d0e2282fa53625e0037a035fee3._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 2"
- date="2014-01-01T22:30:07Z"
- content="""
-3. doesn't work because there could be a special remote or another repository that an untracked repo communicates with (forming their own little subnet hidden from the main network), and so it needs to use remote.log and location tracking for that in the usual way.
-
-It might suffice to make `git annex sync` not push any branches from an untracked repo to its remotes. Its git-annex branch would thus diverge locally, but still contain the global state. There is probably a way to make git refuse to push a branch (at least when naively running `git push` -- I never completely understand how git tracking branches work). Or a pre-push hook could be installed to block an accidential push.
-
-The uuid of an untracked repo would also leak out in the remoteuuid parameter passed to git-annex-shell. That may not matter (as long as it's not used to update the location log, which it doesn't seem to be; the remoteuuid is only used for displaying transfers AFAICS).
-
-----
-
-I'm still be worried about handling numcopies though. Suppose an untracked repo runs `git annex drop --from publicrepo`. We don't want to end up with the numcopies satisfied by the untracked repo and the other remotes that only it can access, because this would seem to make a file vanish from the public network's perspective. `git annex move` is even worse a problem, and even setting the untracked repo to untrusted or dead wouldn't help if the only copies of files are moved to it. 
-
-It seems that an untracked repo should refuse to remove content from the repositories it's \"hiding\" from, and if it's never going to git push to it, there is also no point in uploading annexed objects to it either. So, perhaps make `git.<remote>.annex-read-only = true` be used to configure a remote as read-only, and refuse to push any git branches to a read-only remote, as well as prohibit storekey and removekey being used with any read-only remote (which might be a special remote).
-"""]]
diff --git a/doc/todo/untracked_remotes/comment_3_0d07c5bc8d42f35351c11411eaca88df._comment b/doc/todo/untracked_remotes/comment_3_0d07c5bc8d42f35351c11411eaca88df._comment
deleted file mode 100644
index 946eeaa6c..000000000
--- a/doc/todo/untracked_remotes/comment_3_0d07c5bc8d42f35351c11411eaca88df._comment
+++ /dev/null
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 3"
- date="2014-01-02T00:26:14Z"
- content="""
-Regarding 1.: If two untracked repositories are talking to each other, they should not be tracked at all, so I don't see any issue there.
-If an untracked repository communicates with a tracked one, the untracked one should still send updates for the tracked one when synching.
-The solution might really simply be a specific untracked location log distinct from the rest.
-This would even allow merging changes back into the main log if the user decides to track a repository after all.
-
-Regarding pushing to tracking branches: This behavior will change soon and you can override it; see the manpage for `git-config(1)` at push.default.
-
-Location leaks could be solved by passing `00000000-0000-0000-0000-000000000002` as UUID.
-Using that UUID might also be the solution for all untracked repos as it's trivial to special case for this, but:
-* What happens when you switch a known repo to untracked? What happens to its UUID in various logs? Maybe introduce a specific discard log which tries to get rid of all data concerning those UUIDs?
-* What happens when you switch a repo from untracked to tracked? Simply generate (reactivate?) a UUID and switch all local occurences of `00000000-0000-0000-0000-000000000002` to the new UUID?
-
-`git annex drop --from publicrepo` is not allowed to take local copies into account to satisfy `numcopies`, simple as that.
-IMO, this is the only valid approach, as that mirrors the global view from all other repos.
-For all intents and purposes, an untracked repo does not exist.
-
-
-The complement, a read-only repo, would also be very useful.
-Such a repo would hold data, but it would never accept location data of anywhere besides itself and the web remote.
-
-
-Richard
-"""]]
diff --git a/doc/todo/untracked_remotes/comment_4_75ae13c2135a2951b2af548139cb25cd._comment b/doc/todo/untracked_remotes/comment_4_75ae13c2135a2951b2af548139cb25cd._comment
deleted file mode 100644
index fd9397531..000000000
--- a/doc/todo/untracked_remotes/comment_4_75ae13c2135a2951b2af548139cb25cd._comment
+++ /dev/null
@@ -1,46 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 4"
- date="2014-01-02T01:15:40Z"
- content="""
-Another use case of read-only repos:
-
-Instead of merging pull requests or anything, with git-annex, it makes most sense to simply set up the other party as a remote and `git annex sync`.
-This will attempt to push to the other remote.
-
-In this specific case:
-
-    % git annex sync
-    commit  
-    ok
-    pull origin 
-    ok
-    pull greggrossmeier 
-    ok
-    push origin 
-    Counting objects: 113, done.
-    Delta compression using up to 4 threads.
-    Compressing objects: 100% (84/84), done.
-    Writing objects: 100% (98/98), 25.16 KiB | 0 bytes/s, done.
-    Total 98 (delta 17), reused 1 (delta 0)
-    To git@github.com:RichiH/conference_proceedings.git
-     * [new branch]      git-annex -> synced/git-annex
-     * [new branch]      master -> synced/master
-    ok
-    push greggrossmeier 
-    Username for 'https://github.com': 
-    Password for 'https://github.com': 
-    remote: Anonymous access to greggrossmeier/conference_proceedings.git denied.
-    fatal: Authentication failed for 'https://github.com/greggrossmeier/conference_proceedings.git/'
-    Username for 'https://github.com': 
-    Password for 'https://github.com': 
-    
-      Pushing to greggrossmeier failed.
-    
-      (non-fast-forward problems can be solved by setting receive.denyNonFastforwards to false in the remote's git config)
-    failed
-    git-annex: sync: 1 failed
-    %
-
-"""]]
diff --git a/doc/todo/use_cp_reflink.mdwn b/doc/todo/use_cp_reflink.mdwn
deleted file mode 100644
index 39518abf1..000000000
--- a/doc/todo/use_cp_reflink.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-The unlock command needs to copy a file, and it would be great to use this:
-	cp --reflink=auto src dst
-
-O(1) overhead on BTRFS. Needs coreutils 7.6; and remember that git-annex
-may be used on systems without coreutils..
-
-[[done]]
diff --git a/doc/todo/using_url_backend.mdwn b/doc/todo/using_url_backend.mdwn
deleted file mode 100644
index 1f3cd5628..000000000
--- a/doc/todo/using_url_backend.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-There is no way to `git annex add` a file using the URL [[backend|backends]].
-
-For now, we have to manually make the symlink. Something like this:
-
-	ln -s .git/annex/URL:http:%%www.example.com%foo.tar.gz
-
-Note the escaping of slashes.
-
-A `git annex register <url>` command could do this..
-
-[[done]]
diff --git a/doc/todo/whishlist:_git_annex_drop_--dry-run.mdwn b/doc/todo/whishlist:_git_annex_drop_--dry-run.mdwn
deleted file mode 100644
index 6bbfd7a4d..000000000
--- a/doc/todo/whishlist:_git_annex_drop_--dry-run.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-It'd be useful to be able to see what `git annex drop` would do *before* asking it to drop any files.
-
-For example, I just set up my preferred contents expressions, and I don't know if I got them right. Before dropping anything from this repo, it'd be nice to check what would happen. I know git annex drop will only drop files that are above their minimum numcopies, but I'd still like to avoid heavyweight copying in case I got my preferred contents expressions wrong.
-
-> [[done]]; added --want-get and --want-drop. --[[Joey]]
diff --git a/doc/todo/whishlist:_git_annex_drop_--dry-run/comment_1_20ecfa8ffa52c238d21b904076ac69a2._comment b/doc/todo/whishlist:_git_annex_drop_--dry-run/comment_1_20ecfa8ffa52c238d21b904076ac69a2._comment
deleted file mode 100644
index 098d399e3..000000000
--- a/doc/todo/whishlist:_git_annex_drop_--dry-run/comment_1_20ecfa8ffa52c238d21b904076ac69a2._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.47"
- subject="comment 1"
- date="2013-10-28T17:11:04Z"
- content="""
-It would be nice, but it adds quite a lot of complexity to have a --dry-run, and if I add it to just drop, the next bug is going to ask for get to have it..
-
-I feel that the right approach is to add a --wanted, which could then be used with find to find files that are and are not wanted, according to the preferred content settings. To see what it would want to get: `git annex find --wanted --not --in .` To see what it would want to drop: `git annex find --not --wanted --in .`
-"""]]
diff --git a/doc/todo/whishlist:_git_annex_drop_--dry-run/comment_2_d19bc268c9467d24baa8d8f77a6e5e09._comment b/doc/todo/whishlist:_git_annex_drop_--dry-run/comment_2_d19bc268c9467d24baa8d8f77a6e5e09._comment
deleted file mode 100644
index 3f1102985..000000000
--- a/doc/todo/whishlist:_git_annex_drop_--dry-run/comment_2_d19bc268c9467d24baa8d8f77a6e5e09._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnWwEEA3CurHkBjIYaJsJzFc4jtY2SCkrQ"
- nickname="Diego"
- subject="comment 2"
- date="2013-10-29T00:28:51Z"
- content="""
-That makes sense, and thanks for adding this feature so quickly!
-"""]]
diff --git a/doc/todo/whislist:_allow_setting_annex-ignore_from_the_webapp.mdwn b/doc/todo/whislist:_allow_setting_annex-ignore_from_the_webapp.mdwn
deleted file mode 100644
index 36e936e54..000000000
--- a/doc/todo/whislist:_allow_setting_annex-ignore_from_the_webapp.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-I would like to be able to set 'annex-ignore' for remote servers through the webapp.
-Maybe a checkbox beneath "Syncing enabled" with something like "Also sync content" that it's checked by default?
-
-> Closing per my comment. [[done]] --[[Joey]]
diff --git a/doc/todo/whislist:_allow_setting_annex-ignore_from_the_webapp/comment_1_b3b5c12f89a0a6a91d681c67e2217199._comment b/doc/todo/whislist:_allow_setting_annex-ignore_from_the_webapp/comment_1_b3b5c12f89a0a6a91d681c67e2217199._comment
deleted file mode 100644
index b864a6b63..000000000
--- a/doc/todo/whislist:_allow_setting_annex-ignore_from_the_webapp/comment_1_b3b5c12f89a0a6a91d681c67e2217199._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="216.145.95.162"
- subject="comment 1"
- date="2014-05-19T17:09:16Z"
- content="""
-This feels too complicated for the webapp. Especially because annex-ignore is intended to be used when the remote repository does not have git-annex-shell installed, so cannot contain any content. Which should be automatically detected when the webapp is used to set up a repository (or for that matter, when a repository is set up at the command line). 
-"""]]
diff --git a/doc/todo/wishlist:_Add_to_Android_version_to_Google_Play.mdwn b/doc/todo/wishlist:_Add_to_Android_version_to_Google_Play.mdwn
deleted file mode 100644
index f9016fb4d..000000000
--- a/doc/todo/wishlist:_Add_to_Android_version_to_Google_Play.mdwn
+++ /dev/null
@@ -1,9 +0,0 @@
-If possible a frequently updated daily build in separate package for those more adventurous of us.
-
-It would make installing and testing much easier and no need to change configuration settings to allow untrusted source.
-
-> While it's vaid to wish that someone might put the apk into Google Play,
-> I a) don't feel it's ready b) don't know if I want to go through
-> the rigamarole required to use that service and c) don't feel this
-> bug tracker is an appropriate place to track what is effectively a
-> nontechnical request. [[done]] --[[Joey]] 
diff --git a/doc/todo/wishlist:_An_--all_option_for_dropunused.mdwn b/doc/todo/wishlist:_An_--all_option_for_dropunused.mdwn
deleted file mode 100644
index bd35c0e55..000000000
--- a/doc/todo/wishlist:_An_--all_option_for_dropunused.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-Cleaning out a repository is presently a fairly manual process.  Am I missing a UI trick?  "dropunsed" with no arguments prints nothing at all; I think in that case it should display the list of what could be dropped.
-
-> [[done]]; comments seem satisfactory and I see no reason to complicate
-> dropunused to output something unused already outputs. --[[Joey]]
diff --git a/doc/todo/wishlist:_An_--all_option_for_dropunused/comment_1_d8726d108b3b40116b4ec3c9935f2dff._comment b/doc/todo/wishlist:_An_--all_option_for_dropunused/comment_1_d8726d108b3b40116b4ec3c9935f2dff._comment
deleted file mode 100644
index 6c728a5d0..000000000
--- a/doc/todo/wishlist:_An_--all_option_for_dropunused/comment_1_d8726d108b3b40116b4ec3c9935f2dff._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.23"
- subject="comment 1"
- date="2012-10-22T15:35:30Z"
- content="""
-`git annex unused` prints the list
-"""]]
diff --git a/doc/todo/wishlist:_An_--all_option_for_dropunused/comment_2_578248f7686ba2d80d7dc8b17c0cdf52._comment b/doc/todo/wishlist:_An_--all_option_for_dropunused/comment_2_578248f7686ba2d80d7dc8b17c0cdf52._comment
deleted file mode 100644
index a87a367d6..000000000
--- a/doc/todo/wishlist:_An_--all_option_for_dropunused/comment_2_578248f7686ba2d80d7dc8b17c0cdf52._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://hands.com/~phil/"
- nickname="hands"
- subject="and you can specify ranges to dropunused"
- date="2012-11-02T09:07:48Z"
- content="""
-so having run:
-
-    git annex unused
-
-you can then run:
-
-    git annex dropunused 1-10000
-
-or whatever, and it deletes the items in that range from the most recent <tt>unused</tt> invocation
-"""]]
diff --git a/doc/todo/wishlist:_An_option_like_--git-dir.mdwn b/doc/todo/wishlist:_An_option_like_--git-dir.mdwn
deleted file mode 100644
index 0582d9892..000000000
--- a/doc/todo/wishlist:_An_option_like_--git-dir.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-I'm currently integrating git-annex support into a filesystem synchronization tool that I use, and I have a use case where I'd like to run "git annex sync' on a local directory, and then automatically ssh over to remote hosts and run "git annex sync" in the related annex on that remote host.  However, while I can easily "cd" on the local, there is no really easy way to "cd" on the remote without a hack.
-
-If I could say: git annex --annex-dir=PATH sync, where PATH is the annex directory, it would solve all my problems, and would also provide a nice correlation to the --git-dir option used by most Git commands.  The basic idea is that I shouldn't have to be IN the directory to run git-annex commands, I should be able to tell git-annex which directory to apply its commands to.
-
-> AFAIK this is fully supported for some time, so [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_An_option_like_--git-dir/comment_1_5d877d90b8bdf21d4b8649744d229efd._comment b/doc/todo/wishlist:_An_option_like_--git-dir/comment_1_5d877d90b8bdf21d4b8649744d229efd._comment
deleted file mode 100644
index 8e7c3c03e..000000000
--- a/doc/todo/wishlist:_An_option_like_--git-dir/comment_1_5d877d90b8bdf21d4b8649744d229efd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="What about..."
- date="2012-10-16T16:43:29Z"
- content="""
-    ssh remotehost \"cd /path/to/annex && git annex sync\"
-"""]]
diff --git a/doc/todo/wishlist:_An_option_like_--git-dir/comment_2_462264821cbc48a433330cbf7ec6044d._comment b/doc/todo/wishlist:_An_option_like_--git-dir/comment_2_462264821cbc48a433330cbf7ec6044d._comment
deleted file mode 100644
index 980658dc6..000000000
--- a/doc/todo/wishlist:_An_option_like_--git-dir/comment_2_462264821cbc48a433330cbf7ec6044d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 2"
- date="2012-10-17T18:31:58Z"
- content="""
-You can use `GIT_DIR`. It would not be hard to add a --git-dir option, the only catch is how to communicate that state on to where it constructs its git repository data structure. (I suppose it could just set GIT_DIR..)
-"""]]
diff --git a/doc/todo/wishlist:_An_option_like_--git-dir/comment_3_0c3709b07a0a1091ceeee73b69e0f7ac._comment b/doc/todo/wishlist:_An_option_like_--git-dir/comment_3_0c3709b07a0a1091ceeee73b69e0f7ac._comment
deleted file mode 100644
index a76c42d9d..000000000
--- a/doc/todo/wishlist:_An_option_like_--git-dir/comment_3_0c3709b07a0a1091ceeee73b69e0f7ac._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89"
- nickname="John"
- subject="Response"
- date="2012-10-20T05:21:13Z"
- content="""
-@Justin If you have full shell access on the remote your solution works fine, but not if git-annex is the only binary you are allowed to execute.
-"""]]
diff --git a/doc/todo/wishlist:_GnuPG_options.mdwn b/doc/todo/wishlist:_GnuPG_options.mdwn
deleted file mode 100644
index 2cadf8213..000000000
--- a/doc/todo/wishlist:_GnuPG_options.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-[Maybe I should have extented [[wishlist:_simpler_gpg_usage/]], but I thought I'd make my own since it's perhaps too old.]
-
-I second Justin and [[his idea|wishlist:_simpler_gpg_usage/#comment-e120f8ede0d4cffce17cbf84564211c1]] of having per-remote GnuPG options. I'd even go one step further, and propose the option in the <tt>.gitattributes</tt> file. Indeed by default GnuPG compresses the data before encryption, which doesn't make a lot of sense for git-annex (in my use-case at least); My work-around to save this waste of CPU cycles was to customize my <tt>gpg.conf</tt>, but it's somewhat dirty since I do want to use compression in general.
-
-Here is how I envision the <tt>.git/config</tt>:
-<pre>    <code>[annex]
-        gnupg-options = --s2k-cipher-algo AES256 --s2k-digest-algo SHA512 --s2k-count 8388608 --cipher-algo AES256 --compress-algo none
-</code></pre>
-
-And compression could be enabled on say, text files, with a suitable wildcard in the <tt>.gitattributes</tt> file.
-<pre>    <code>*.txt annex.gnupg-options="--s2k-cipher-algo AES256 --s2k-digest-algo SHA512 --s2k-count 8388608 --cipher-algo AES256 --compress-algo zlib"
-</code></pre>
-
-This is something I could probably hack on if you think it'd be a worthwhile option ;-)
-
-> Done, and [[done]]! --[[Joey]]
diff --git a/doc/todo/wishlist:_GnuPG_options/comment_1_6662e8a71ce20acc62147ef41ecffa50._comment b/doc/todo/wishlist:_GnuPG_options/comment_1_6662e8a71ce20acc62147ef41ecffa50._comment
deleted file mode 100644
index b756eccad..000000000
--- a/doc/todo/wishlist:_GnuPG_options/comment_1_6662e8a71ce20acc62147ef41ecffa50._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-09T01:54:30Z"
- content="""
-I'd be happy to apply a patch implementing annex.gnupg-options and/or per-remote remote.annex-gnupg-options, and I don't think it would be very hard to do.
-
-The gitattributes thing would be harder to do efficiently, and seems overkill.
-
-
-"""]]
diff --git a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size.mdwn b/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size.mdwn
deleted file mode 100644
index 12688951d..000000000
--- a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size.mdwn
+++ /dev/null
@@ -1,10 +0,0 @@
-When using SSH remote repository, git-annex uses rsync to download or upload files one at a time. I would like to have a preview of the overall transfer size so that I can estimate the transfer duration.
-
-This could be done as an option of get, move or copy, or as a separated command.
-
-If part of get, move or copy, git-annex could print how much has been done or how much left between every files.
-
-Thanks.
-
-> [[done]]; `git-annex status .` seems to cover the requested use case.
-> --[[Joey]] 
diff --git a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_1_019a2457e07377510feaa089a93bd76c._comment b/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_1_019a2457e07377510feaa089a93bd76c._comment
deleted file mode 100644
index 4a59f37f1..000000000
--- a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_1_019a2457e07377510feaa089a93bd76c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.193"
- subject="comment 1"
- date="2013-06-25T17:26:25Z"
- content="""
-git-annex is designed to work with really large trees of files, and so it processes files one at a time in a stream. To get an overall estimate of the size, it would need to traverse the whole directory to get the total, and then traverse it again to perform the transfer. This would make no-op transfers take twice as long, which is why I'm unlikely to implement it.
-"""]]
diff --git a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_3_29a154699339bf040af0ee8aa24034f1._comment b/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_3_29a154699339bf040af0ee8aa24034f1._comment
deleted file mode 100644
index 9f0c04017..000000000
--- a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_3_29a154699339bf040af0ee8aa24034f1._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnHRhCe3qwVKQ8_NOGGSYJnAMW6FFyKbOc"
- nickname="Holger"
- subject="comment 3"
- date="2013-07-02T04:05:06Z"
- content="""
-What do you think of the following simpler variant:
-
-    % git annex size myfile1.zip
-    myfile1.zip is 1329 MB
-    % git annex size mydir/
-    mydir contains 2803 files totaling 328 GB.
-
-If you're worried about running over the tree twice, it may be a good idea to store the size of a subtree along with the other metadata.
-"""]]
diff --git a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_3_8f7e1c4a5c714cbd719ee170354d79fa._comment b/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_3_8f7e1c4a5c714cbd719ee170354d79fa._comment
deleted file mode 100644
index fa9fdfb56..000000000
--- a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_3_8f7e1c4a5c714cbd719ee170354d79fa._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 3"
- date="2013-07-02T17:04:47Z"
- content="""
-You can get info like that by running `git annex status .`
-
-This can also be used to find out how big a download is before starting it. For example, to find all files that are not present locally before running git-annex get:
-
-`git annex status . --not --in here`
-"""]]
diff --git a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_4_c7335f757e5546aa841cab38fffe7605._comment b/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_4_c7335f757e5546aa841cab38fffe7605._comment
deleted file mode 100644
index b9212a24d..000000000
--- a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_4_c7335f757e5546aa841cab38fffe7605._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnHRhCe3qwVKQ8_NOGGSYJnAMW6FFyKbOc"
- nickname="Holger"
- subject="comment 4"
- date="2013-07-02T21:09:03Z"
- content="""
-That's so cool, thanks!
-
-Do you think it'd be a major change to the repository format if the size of any directory was stored there so that this kind of status lookup becomes a constant time operation? The two most important operations are probably:
-
-* The total size of a directory, counting only files present here
-* The total size of a directory, counting all files present at any location
-
-Of course, if the above two were constant time operations, you get --not here for free, too.
-
-To implement this, each node in the directory tree could have two additional 64 bit fields that hold the number of bytes in all files present anywhere (and this set of numbers is synchronized between all repositories), and the number of bytes in all files present here (only kept locally). This is only a small storage overhead (<16 MB if you have a million nodes) and suffices for repositories of size at most 2^64 bytes = 16 exabytes (probably more since most users will be ok with float accuracy). The numbers can be updated in logarithmic time every time a file changes. Instead of two numbers, it may not be that costly to store k numbers where k is the number of locations that a repository is connected to, since k is typically pretty small.
-
-The number of files can be stored in a similar way.
-"""]]
diff --git a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_5_d2a845354f23d07880612740cf99ddd4._comment b/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_5_d2a845354f23d07880612740cf99ddd4._comment
deleted file mode 100644
index 7e160bebf..000000000
--- a/doc/todo/wishlist:_Have_a_preview_of_download_or_upload_size/comment_5_d2a845354f23d07880612740cf99ddd4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawnHRhCe3qwVKQ8_NOGGSYJnAMW6FFyKbOc"
- nickname="Holger"
- subject="comment 5"
- date="2013-07-03T02:43:32Z"
- content="""
-Btw, this would also provide a cheap test for whether we need to recurse into the folder in certain copy or get actions (e.g., if number of bytes present here equals number of bytes globally present, we don't need to recurse).
-"""]]
diff --git a/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command.mdwn b/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command.mdwn
deleted file mode 100644
index cb170dbe4..000000000
--- a/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command.mdwn
+++ /dev/null
@@ -1,45 +0,0 @@
-Simple, when performing various git annex command over ssh, in particular a multi-file get, and using password authentication, git annex will prompt more than once for a user password.  This makes batch updates very inconvenient.
-
-> I'd suggest using ssh-agent, or a passwordless ssh key. Possibly in
-> combination with [[git-annex-shell]] if you want to lock down a
-> particular ssh key to only being able to use git-annex and git-daemon.
-> 
-> Combining multiple operations into a single ssh is on the todo list, but
-> very far down it. --[[Joey]]
-
->> OTOH, automatically running ssh in ControlMaster mode (and stopping it
->> at exit) would be useful and not hard thing for git-annex to do.
->> 
->> It'd just need to set the appropriate config options, setting
->> ControlPath to a per-remote socket location that includes git-annex's
->> pid. Then at shutdown, run `ssh -O exit` on each such socket.
->> 
->> Complicated slightly by not doing this if the user has already set up
->> more broad ssh connection caching.
->> 
->> [[done]]! --[[Joey]]
-
----
-
-Slightly more elaborate design for using ssh connection caching:
-
-* Per-uuid ssh socket in `.git/annex/ssh/user@host.socket`
-* Can be shared among concurrent git-annex processes as well as ssh
-  invocations inside the current git-annex.
-* Also a lock file, `.git/annex/ssh/user@host.lock`.
-  Open and take shared lock before running ssh; store lock in lock pool.
-  (Not locking socket directly, because ssh might want to.)
-* Run ssh like: `ssh -S .git/annex/ssh/user@host.socket -o ControlMaster=auto -o ControlPersist=yes user@host`
-* At shutdown, enumerate all existing sockets, and on each:
-  1. Drop any shared lock.
-  2. Attempt to take an exclusive lock (non-blocking).
-  3. `ssh -q -S .git/annex/ssh/user@host.socket -o ControlMaster=auto -o ControlPersist=yes -O stop user@host`
-     (Will exit nonzero if ssh is not running on that socket.)
-  4. And then remove the socket and the lock file.
-* Do same *at startup*. Why? In case an old git-annex was interrupted
-  and left behind a ssh. May have moved to a different network
-  in the meantime, etc, and be stalled waiting for a response from the
-  network, or talking to the wrong interface or something.
-  (Ie, the reason why I don't use ssh connection caching by default.)
-* User should be able to override this, to use their own preferred
-  connection caching setup. `annex.sshcaching=false`
diff --git a/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command/comment_1_3f9c0d08932c2ede61c802a91261a1f7._comment b/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command/comment_1_3f9c0d08932c2ede61c802a91261a1f7._comment
deleted file mode 100644
index 2801d8e68..000000000
--- a/doc/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command/comment_1_3f9c0d08932c2ede61c802a91261a1f7._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-05-06T18:30:02Z"
- content="""
-Unless you are forced to use a password, you should really be using a ssh key.
-
-    ssh-keygen
-    #put local .ssh/id_?sa.pub into remote .ssh/authorized_keys (which needs to be chmod 600)
-    ssh-add
-    git annex whatever
-
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates.mdwn b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates.mdwn
deleted file mode 100644
index 933653578..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-(Hi, this is paulproteus@debian, AKA Asheesh).
-
-I've been enjoying using git-annex to archive my data.
-
-It's great that, by using git-annex and the SHA1 backend, I get a space-saving kind of deduplication through the symbolic links.
-
-I'm looking for the ability to filter files, before they get added to the annex, so that I don't add new files whose content is already in the annex.look  That would help me in terms of personal file organization.
-
-It seems there is not, so this is a wishlist bug filed so that maybe such a thing might exist. What I would really like to do is:
-
-* $ git annex add --no-add-if-already-present .
-* $ git commit -m "Slurping in some photos I found on my old laptop hard drive"
-
-And then I'd do something like:
-
-* $ git clean -f
-
-to remove the files that didn't get annexed in this run. That way, only one filename would ever point to a particular SHA1.
-
-I want this because I have copies of various of mine (photos, in particular) scattered across various hard disks. If this feature existed, I could comfortably toss them all into one git annex that grew, bit by bit, to store all of these files exactly once.
-
-(I would be even happier for "git annex add --unlink-duplicates .")
-
-(Another way to do this would be to "git annex add" them all, and then use a "git annex remove-duplicates" that could prompt me about which files are duplicates of each other, and then I could pipe that command's output into xargs git rm.)
-
-(As I write this, I realize it's possible to parse the destination of the symlink in a way that does this..)
-
-> [[done]]; see [[tips/finding_duplicate_files]] --[[Joey]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_10_d78d79fb2f3713aa69f45d2691cf8dfe._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_10_d78d79fb2f3713aa69f45d2691cf8dfe._comment
deleted file mode 100644
index 5dbb66cf6..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_10_d78d79fb2f3713aa69f45d2691cf8dfe._comment
+++ /dev/null
@@ -1,68 +0,0 @@
-[[!comment format=mdwn
- username="http://adamspiers.myopenid.com/"
- nickname="Adam"
- subject="comment 10"
- date="2011-12-23T17:22:11Z"
- content="""
-> Your perl script is not O(n). Inserting into perl hash tables has
-> overhead of minimum O(n log n).
-
-What's your source for this assertion?  I would expect an amortized
-average of `O(1)` per insertion, i.e. `O(n)` for full population.
-
-> Not counting the overhead of resizing hash tables,
-> the grevious slowdown if the bucket size is overcome by data (it
-> probably falls back to a linked list or something then), and the
-> overhead of traversing the hash tables to get data out.
-
-None of which necessarily change the algorithmic complexity.  However
-real benchmarks are far more useful here than complexity analysis, and
-[the dangers of premature optimization](http://c2.com/cgi/wiki?PrematureOptimization) 
-should not be forgotten.
-
-> Your memory size calculations ignore the overhead of a hash table or
-> other data structure to store the data in, which will tend to be
-> more than the actual data size it's storing. I estimate your 50
-> million number is off by at least one order of magnitude, and more
-> likely two;
-
-Sure, I was aware of that, but my point still stands.  Even 500k keys
-per 1GB of RAM does not sound expensive to me.
-
-> in any case I don't want git-annex to use 1 gb of ram.
-
-Why not?  What's the maximum it should use?  512MB?  256MB?
-32MB?  I don't see the sense in the author of a program 
-dictating thresholds which are entirely dependent on the context
-in which the program is *run*, not the context in which it's *written*.
-That's why systems have files such as `/etc/security/limits.conf`.
-
-You said you want git-annex to scale to enormous repositories.  If you
-impose an arbitrary memory restriction such as the above, that means
-avoiding implementing *any* kind of functionality which requires `O(n)`
-memory or worse.  Isn't it reasonable to assume that many users use
-git-annex on repositories which are *not* enormous?  Even when they do
-work with enormous repositories, just like with any other program,
-they would naturally expect certain operations to take longer or
-become impractical without sufficient RAM.  That's why I say that this
-restriction amounts to throwing out the baby with the bathwater.
-It just means that those who need the functionality would have to
-reimplement it themselves, assuming they are able, which is likely
-to result in more wheel reinventions.  I've already shared
-[my implementation](https://github.com/aspiers/git-config/blob/master/bin/git-annex-finddups)
-but how many people are likely to find it, let alone get it working?
-
-> Little known fact: sort(1) will use a temp file as a buffer if too
-> much memory is needed to hold the data to sort.
-
-Interesting.  Presumably you are referring to some undocumented
-behaviour, rather than `--batch-size` which only applies when merging
-multiple files, and not when only sorting STDIN.
-
-> It's also written in the most efficient language possible and has
-> been ruthlessly optimised for 30 years, so I would be very surprised
-> if it was not the best choice.
-
-It's the best choice for sorting.  But sorting purely to detect
-duplicates is a dismally bad choice.
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_11_4316d9d74312112dc4c823077af7febe._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_11_4316d9d74312112dc4c823077af7febe._comment
deleted file mode 100644
index 286487eee..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_11_4316d9d74312112dc4c823077af7febe._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 11"
- date="2011-12-23T17:52:21Z"
- content="""
-I don't think that [[tips/finding_duplicate_files]] is hard to find, and the multiple different ways it shows to deal with the duplicate files shows the flexability of the unix pipeline approach.
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_12_ed6d07f16a11c6eee7e3d5005e8e6fa3._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_12_ed6d07f16a11c6eee7e3d5005e8e6fa3._comment
deleted file mode 100644
index 909beed83..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_12_ed6d07f16a11c6eee7e3d5005e8e6fa3._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 12"
- date="2011-12-23T18:02:24Z"
- content="""
-BTW, sort -S '90%' benchmarks consistently 2x as fast as perl's hashes all the way up to 1 million files. Of course the pipeline approach allows you to swap in perl or whatever else is best for you at scale.
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_1_fd213310ee548d8726791d2b02237fde._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_1_fd213310ee548d8726791d2b02237fde._comment
deleted file mode 100644
index 094e4526e..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_1_fd213310ee548d8726791d2b02237fde._comment
+++ /dev/null
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-01-27T18:29:44Z"
- content="""
-Hey Asheesh, I'm happy you're finding git-annex useful.
-
-So, there are two forms of duplication going on here. There's duplication of the content, and duplication of the filenames 
-pointing at that content.
-
-Duplication of the filenames is probably not a concern, although it's what I thought you were talking about at first. It's probably info worth recording that backup-2010/some_dir/foo and backup-2009/other_dir/foo are two names you've used for the same content in the past. If you really wanted to remove backup-2009/foo, you could do it by writing a script that looks at the basenames of the symlink targets and removes files that point to the same content as other files.
-
-Using SHA1 ensures that the same key is used for identical files, so generally avoids duplication of content. But if you have 2 disks with an identical file on each, and make them both into annexes, then git-annex will happily retain both
-copies of the content, one per disk. It generally considers keeping copies of content a good thing. :)
-
-So, what if you want to remove the unnecessary copies? Well, there's a really simple way:
-
-<pre>
-cd /media/usb-1
-git remote add other-disk /media/usb-0
-git annex add
-git annex drop
-</pre>
-
-This asks git-annex to add everything to the annex, but then remove any file contents that it can safely remove. What can it safely remove? Well, anything that it can verify is on another repository such as \"other-disk\"! So, this will happily drop any duplicated file contents, while leaving all the rest alone.
-
-In practice, you might not want to have all your old backup disks mounted at the same time and configured as remotes. Look into configuring [[trust]] to avoid needing do to that. If usb-0 is already a trusted disk, all you need is a simple \"git annex drop\" on usb-1.
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_2_4394bde1c6fd44acae649baffe802775._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_2_4394bde1c6fd44acae649baffe802775._comment
deleted file mode 100644
index 04d58a459..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_2_4394bde1c6fd44acae649baffe802775._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkjvjLHW9Omza7x1VEzIFQ8Z5honhRB90I"
- nickname="Asheesh"
- subject="I actually *do* want to avoid duplication of filenames"
- date="2011-01-28T07:30:05Z"
- content="""
-I really do want just one filename per file, at least for some cases.
-
-For my photos, there's no benefit to having a few filenames point to the same file. As I'm putting them all into the git-annex, that is a good time to remove the pure duplicates so that I don't e.g. see them twice when browsing the directory as a gallery. Also, I am uploading my photos to the web, and I want to avoid uploading the same photo (by content) twice.
-
-I hope that makes things clearer!
-
-For now I'm just doing this:
-
-* paulproteus@renaissance:/mnt/backups-terabyte/paulproteus/sd-card-from-2011-01-06/sd-cards/DCIM/100CANON $ for file in *; do hash=$(sha1sum \"$file\"); if ls /home/paulproteus/Photos/in-flickr/.git-annex | grep -q \"$hash\"; then echo already annexed ; else flickr_upload \"$file\" && mv \"$file\" \"/home/paulproteus/Photos/in-flickr/2011-01-28/from-some-nested-sd-card-bk\" && (cd /home/paulproteus/Photos/in-flickr/2011-01-28/from-some-nested-sd-card-bk && git annex add . && git commit -m ...) ; fi; done
-
-(Yeah, Flickr for my photos for now. I feel sad about betraying the principle of autonomo.us-ness.)
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_3_076cb22057583957d5179d8ba9004605._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_3_076cb22057583957d5179d8ba9004605._comment
deleted file mode 100644
index d11119bc3..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_3_076cb22057583957d5179d8ba9004605._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkjvjLHW9Omza7x1VEzIFQ8Z5honhRB90I"
- nickname="Asheesh"
- subject="Duplication of the filenames is what I am concerned about"
- date="2011-04-29T11:48:22Z"
- content="""
-For what it's worth, yes, I want to actually forget I ever had the same file in the filesystem with a duplicated name. I'm not just aiming to clean up the disk's space usage; I'm also aiming to clean things up so that navigating the filesystem is easier.
-
-I can write my own script to do that based on the symlinks' target (and I wrote something along those lines), but I still think it'd be nicer if git-annex supported this use case.
-
-Perhaps:
-
-<pre>git annex drop --by-contents</pre>
-
-could let me remove a file from git-annex if the contents are available through a different name. (Right now, \"git annex drop\" requires the name *and* contents match.)
-
--- Asheesh.
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_4_f120d1e83c1a447f2ecce302fc69cf74._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_4_f120d1e83c1a447f2ecce302fc69cf74._comment
deleted file mode 100644
index a218ee3d5..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_4_f120d1e83c1a447f2ecce302fc69cf74._comment
+++ /dev/null
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="http://adamspiers.myopenid.com/"
- nickname="Adam"
- subject="List the duplicate filenames, then let the user decide what to do"
- date="2011-12-22T12:31:29Z"
- content="""
-I have the same use case as Asheesh but I want to be able to see which filenames point to the same objects and then decide which of the duplicates to drop myself.  I think
-
-    git annex drop --by-contents
-
-would be the wrong approach because how does git-annex know which ones to drop?  There's too much potential for error.
-
-Instead it would be great to have something like
-
-    git annex finddups
-
-While it's easy enough to knock up a bit of shell or Perl to achieve this, that relies on knowledge of the annex symlink structure, so I think really it belongs inside git-annex.
-
-If this command gave output similar to the excellent `fastdup` utility:
-
-    Scanning for files... 672 files in 10.439 seconds
-    Comparing 2 sets of files...
-
-    2 files (70.71 MB/ea)
-            /home/adam/media/flat/tour/flat-tour.3gp
-            /home/adam/videos/tour.3gp
-
-    Found 1 duplicate of 1 file (70.71 MB wasted)
-    Scanned 672 files (1.96 GB) in 11.415 seconds
-
-then you could do stuff like
-
-    git annex finddups | grep /home/adam/media/flat | xargs rm
-
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_5_5c30294b3c59fdebb1eef0ae5da4cd4f._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_5_5c30294b3c59fdebb1eef0ae5da4cd4f._comment
deleted file mode 100644
index e48a4a9b3..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_5_5c30294b3c59fdebb1eef0ae5da4cd4f._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://adamspiers.myopenid.com/"
- nickname="Adam"
- subject="Here's a Perl version"
- date="2011-12-22T15:43:51Z"
- content="""
-https://github.com/aspiers/git-config/blob/master/bin/git-annex-finddups
-
-but it would be better in git-annex itself ...
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_6_f24541ada1c86d755acba7e9fa7cff24._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_6_f24541ada1c86d755acba7e9fa7cff24._comment
deleted file mode 100644
index 5d8ac8e61..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_6_f24541ada1c86d755acba7e9fa7cff24._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 6"
- date="2011-12-22T16:39:24Z"
- content="""
-My main concern with putting this in git-annex is that finding duplicates necessarily involves storing a list of every key and file in the repository, and git-annex is very carefully built to avoid things that require non-constant memory use, so that it can scale to very big repositories. (The only exception is the `unused` command, and reducing its memory usage is a continuing goal.)
-
-So I would rather come at this from a different angle.. like providing a way to output a list of files and their associated keys, which the user can then use in their own shell pipelines to find duplicate keys:
-
-      git annex find --include '*' --format='${file} ${key}\n' | sort --key 2 | uniq --all-repeated --skip-fields=1
-
-Which is implemented now!
-
-(Making that pipeline properly handle filenames with spaces is left as an exercise for the reader..)
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_7_c39f1bb7c61a89b238c61bee1c049767._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_7_c39f1bb7c61a89b238c61bee1c049767._comment
deleted file mode 100644
index a33700280..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_7_c39f1bb7c61a89b238c61bee1c049767._comment
+++ /dev/null
@@ -1,54 +0,0 @@
-[[!comment format=mdwn
- username="http://adamspiers.myopenid.com/"
- nickname="Adam"
- subject="comment 7"
- date="2011-12-22T20:04:14Z"
- content="""
-> My main concern with putting this in git-annex is that finding
-> duplicates necessarily involves storing a list of every key and file
-> in the repository
-
-Only if you want to search the *whole* repository for duplicates, and if
-you do, then you're necessarily going to have to chew up memory in
-some process anyway, so what difference whether it's git-annex or
-(say) a Perl wrapper?
-
-> and git-annex is very carefully built to avoid things that require
-> non-constant memory use, so that it can scale to very big
-> repositories.
-
-That's a worthy goal, but if everything could be implemented with an
-O(1) memory footprint then we'd be in much more pleasant world :-)
-Even O(n) isn't that bad ...
-
-That aside, I like your `--format=\"%f %k\n\"` idea a lot.  That opens
-up the \"black box\" of `.git/annex/objects` and makes nice things
-possible, as your pipeline already demonstrates.  However, I'm not
-sure why you think `git annex find | sort | uniq` would be more
-efficient.  Not only does the sort require the very thing you were
-trying to avoid (i.e. the whole list in memory), but it's also 
-O(n log n) which is significantly slower than my O(n) Perl script 
-linked above.
-
-More considerations about this pipeline:
-
-* Doesn't it only include locally available files?  Ideally it should
-  spot duplicates even when the backing blob is not available locally.
-* What's the point of `--include '*'` ?  Doesn't `git annex find` 
-  with no arguments already include all files, modulo the requirement
-  above that they're locally available?
-* Any user using this `git annex find | ...` approach is likely to
-  run up against its limitations sooner rather than later, because
-  they're already used to the plethora of options `find(1)` provides.
-  Rather than reinventing the wheel, is there some way `git annex find`
-  could harness the power of `find(1)` ?
-
-Those considerations aside, a combined approach would be to implement
-
-    git annex find --format=...
-
-and then alter my Perl wrapper to `popen(2)` from that rather than using
-`File::Find`.  But I doubt you would want to ship Perl wrappers in the
-distribution, so if you don't provide a Haskell equivalent then users
-who can't code are left high and dry.
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_8_221ed2e53420278072a6d879c6f251d1._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_8_221ed2e53420278072a6d879c6f251d1._comment
deleted file mode 100644
index 5ac292afe..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_8_221ed2e53420278072a6d879c6f251d1._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://adamspiers.myopenid.com/"
- nickname="Adam"
- subject="How much memory would it actually use anyway?"
- date="2011-12-22T20:15:22Z"
- content="""
-Another thought - an SHA1 digest is 20 bytes.  That means you can fit over 50 million keys into 1GB of RAM.  Granted you also need memory to store the values (pathnames) which in many cases will be longer, and some users may also choose more expensive backends than SHA1 ... but even so, it seems to me that you are at risk of throwing the baby out with the bath water.  
-"""]]
diff --git a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_9_aecfa896c97b9448f235bce18a40621d._comment b/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_9_aecfa896c97b9448f235bce18a40621d._comment
deleted file mode 100644
index 82c6921eb..000000000
--- a/doc/todo/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_9_aecfa896c97b9448f235bce18a40621d._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 9"
- date="2011-12-23T16:07:39Z"
- content="""
-Adam, to answer a lot of points breifly..
-
-* --include='*' makes find list files whether their contents are present or not
-* Your perl script is not O(n). Inserting into perl hash tables has overhead of minimum O(n log n). Not counting the overhead of resizing hash tables, the grevious slowdown if the bucket size is overcome by data (it probably falls back to a linked list or something then), and the overhead of traversing the hash tables to get data out.
-* I think that git-annex's set of file matching options is coming along nicely, and new ones can easily be added, so see no need to pull in unix find(1).
-* Your memory size calculations ignore the overhead of a hash table or other data structure to store the data in, which will tend to be more than the actual data size it's storing.  I estimate your 50 million number is off by at least one order of magnitude, and more likely two; in any case I don't want git-annex to use 1 gb of ram.
-* Little known fact: sort(1) will use a temp file as a buffer if too much memory is needed to hold the data to sort. It's also written in the most efficient language possible and has been ruthlessly optimised for 30 years, so I would be very surprised if it was not the best choice.
-"""]]
diff --git a/doc/todo/wishlist:_Tell_git_annex___40__assistant__41___which_files___40__not__41___to_annex_via_.gitattributes.mdwn b/doc/todo/wishlist:_Tell_git_annex___40__assistant__41___which_files___40__not__41___to_annex_via_.gitattributes.mdwn
deleted file mode 100644
index f65a95f45..000000000
--- a/doc/todo/wishlist:_Tell_git_annex___40__assistant__41___which_files___40__not__41___to_annex_via_.gitattributes.mdwn
+++ /dev/null
@@ -1,9 +0,0 @@
-Title says it all.
-
-It would be nice if I could tell git annex (assistant) which files (not) to annex (automatically).
-
-[[!tag /design/assistant]]
-
-> [[done]]; use `annex.largefiles` git config to configure criteria for
-> which files should be annexed. The rest will be added to git as normal
-> files. --[[Joey]]
diff --git a/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes.mdwn b/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes.mdwn
deleted file mode 100644
index a04af05b4..000000000
--- a/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes.mdwn
+++ /dev/null
@@ -1,10 +0,0 @@
-Hello,
-
-i'm in the process of managing my music collection with git-annex. The initial "git annex add" using the sha1 banckend is quite long an i was wondering that it could be nice to launch multiple "sha1sum" processes in parallel to speed up things.
-
-Anyway, thanks for this wonderful piece of software.
-
-Jean-Baptiste
-
-> closing as dup of [[parallel possibilities]] (also see comments below)
-> [[done]] --[[Joey]] 
diff --git a/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_1_85b14478411a33e6186a64bd41f0910d._comment b/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_1_85b14478411a33e6186a64bd41f0910d._comment
deleted file mode 100644
index 2364b7fb8..000000000
--- a/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_1_85b14478411a33e6186a64bd41f0910d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-02-25T19:12:42Z"
- content="""
-I'd expect the checksumming to be disk bound, not CPU bound, on most systems.
-
-I suggest you start off on the WORM backend, and then you can run a job later to [[migrate|walkthrough#index14h2]] to the SHA1 backend.
-"""]]
diff --git a/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_2_82e857f463cfdf73c70f6c0a9f9a31d6._comment b/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_2_82e857f463cfdf73c70f6c0a9f9a31d6._comment
deleted file mode 100644
index 9b8240658..000000000
--- a/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_2_82e857f463cfdf73c70f6c0a9f9a31d6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-02-25T19:54:28Z"
- content="""
-But, see [[todo/parallel_possibilities]]
-"""]]
diff --git a/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_3_8af85eba7472d9025c6fae4f03e3ad75._comment b/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_3_8af85eba7472d9025c6fae4f03e3ad75._comment
deleted file mode 100644
index ee769f0dd..000000000
--- a/doc/todo/wishlist:___34__git_annex_add__34___multiple_processes/comment_3_8af85eba7472d9025c6fae4f03e3ad75._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="jbd"
- ip="89.158.228.148"
- subject="comment 3"
- date="2011-02-26T10:26:12Z"
- content="""
-Thank your for your answer and the link !
-"""]]
diff --git a/doc/todo/wishlist:___96__git_annex_fsck_--checksums__96___--_verify_checksums_but_disregard_annex.numcopies.mdwn b/doc/todo/wishlist:___96__git_annex_fsck_--checksums__96___--_verify_checksums_but_disregard_annex.numcopies.mdwn
deleted file mode 100644
index 67a7e13e1..000000000
--- a/doc/todo/wishlist:___96__git_annex_fsck_--checksums__96___--_verify_checksums_but_disregard_annex.numcopies.mdwn
+++ /dev/null
@@ -1,12 +0,0 @@
-As the title says, I would like to see an option where git-annex verifies
-that all checksums are OK but not that the required number of copies or
-other possible metrics are fulfilled.
-
--- RichiH
-
-> --numcopies is provided for times when you want to temporarily override
-> annex.numcopies. So, `git annex fsck --numcopies=0`
-> 
-> I don't see any reason to want to disable the other checks and fixups
-> fsck does (of bad location log data, for example). So, [[done]]
-> --[[Joey]]
diff --git a/doc/todo/wishlist:___96__git_annex_fsck_--checksums__96___--_verify_checksums_but_disregard_annex.numcopies/comment_1_6bcf067e4860bdfeb1d7b9fd1702a43a._comment b/doc/todo/wishlist:___96__git_annex_fsck_--checksums__96___--_verify_checksums_but_disregard_annex.numcopies/comment_1_6bcf067e4860bdfeb1d7b9fd1702a43a._comment
deleted file mode 100644
index c8f40caf7..000000000
--- a/doc/todo/wishlist:___96__git_annex_fsck_--checksums__96___--_verify_checksums_but_disregard_annex.numcopies/comment_1_6bcf067e4860bdfeb1d7b9fd1702a43a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2013-07-10T23:09:31Z"
- content="""
-As a side note, --numcopies was broken, but it's been fixed with 4.20130709.
-"""]]
diff --git a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn b/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn
deleted file mode 100644
index cd679485b..000000000
--- a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-`git annex import` would copy data over from external places into the annex. It would be run from within the annex and in the target location where the files need to end up.
-
-Two basic modes of operation:
-
-* If run on a normal directory, e.g. an SD card, it would simply copy over and `git annex add $newstuff`
-
-* If run on another indirect annex, it would copy over the symlinks, copy over the object data, verify that the checksums are OK and add to the annex
-
-An optional `git annex import --copy-only` would copy over and verify the data, but not yet add it. That would allow the user to import into a decent data structure. If run on non-annexed data, `git annex import --copy-only` would ideally calculate checksums and create symlinks already; thus ensuring data integrity as early as possible.
-
--- RichiH
-
-> [[done]] --[[Joey]] in 2012
diff --git a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_1_b9fd1bfaf9a3d238fdb7bc9c2d75fe5f._comment b/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_1_b9fd1bfaf9a3d238fdb7bc9c2d75fe5f._comment
deleted file mode 100644
index ff9030c99..000000000
--- a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_1_b9fd1bfaf9a3d238fdb7bc9c2d75fe5f._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.254.222"
- subject="comment 1"
- date="2013-07-07T18:09:20Z"
- content="""
-This is such a good idea that I went into the time machine and arranged for it to be implemented in June 2012:
-
-<pre>
-       import [path ...]
-              Moves files from somewhere outside the git work‐
-              ing copy, and adds them to the annex. Individual
-              files to import can be specified.  If  a  direc‐
-              tory is specified, all files in it are imported,
-              and any subdirectory structure inside it is pre‐
-              served.
-
-               git annex import /media/camera/DCIM/
-</pre>
-
-I don't see much use for `--copy-only` though. so did not implement it them (also I needed to spend some of my time at the race track). It seems to me that using `--copy-only` as you describe it would do everything except for add the files to git. You can get the same behavior by using `git annex import`, which only stages the new files but does not commit them, and then moving files around and running `git annex add` on them, followed by committing.
-"""]]
diff --git a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_2_56f6972413c6f0d9f414245b6f4d27b9._comment b/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_2_56f6972413c6f0d9f414245b6f4d27b9._comment
deleted file mode 100644
index ccdf2e704..000000000
--- a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_2_56f6972413c6f0d9f414245b6f4d27b9._comment
+++ /dev/null
@@ -1,62 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2013-07-10T23:25:52Z"
- content="""
-Ugh, learn to read, etc...
-
-It's not possible to import from other annexes, though. Importing just the files from an indirect repo does nothing:
-
-    ~/test-annex--foo % git annex status
-    supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-    supported remote types: git S3 bup directory rsync web webdav glacier hook
-    repository mode: indirect
-    trusted repositories: 0
-    semitrusted repositories: 2
-            00000000-0000-0000-0000-000000000001 -- web
-            8105410b-d8ca-4de4-bb6a-91b9772250dc -- here (richih@adamantium:~/test-annex--foo)
-    untrusted repositories: 0
-    transfers in progress: none
-    available local disk space: 52 gigabytes (+1 megabyte reserved)
-    local annex keys: 1
-    local annex size: 4 bytes
-    known annex keys: 1
-    known annex size: 4 bytes
-    bloom filter size: 16 mebibytes (0% full)
-    backend usage:
-            SHA256E: 2
-    ~/test-annex--foo % ls -l
-    total 4
-    lrwxrwxrwx 1 richih richih 178 Jul 11 01:21 bar -> .git/annex/objects/g7/9v/SHA256E-s4--7d865e959b2466918c9863afca942d0fb89d7c9ac0c99bafc3749504ded97730/SHA256E-s4--7d865e959b2466918c9863afca942d0fb89d7c9ac0c99bafc3749504ded97730
-    ~/test-annex--foo % cd ../test-annex
-    ~/test-annex % git annex status
-    supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL
-    supported remote types: git S3 bup directory rsync web webdav glacier hook
-    repository mode: indirect
-    trusted repositories: (merging synced/git-annex into git-annex...)
-    0
-    semitrusted repositories: 3
-            00000000-0000-0000-0000-000000000001 -- web
-            7c50da8c-dc76-4b4a-b46d-8dd16385691a -- here (richih@adamantium:~/test-annex)
-            d4104a13-a2eb-4f5c-ba54-990ece5c81df -- richih@adamantium:~/test-annex-2
-    untrusted repositories: 0
-    transfers in progress: none
-    available local disk space: 52 gigabytes (+1 megabyte reserved)
-    local annex keys: 1
-    local annex size: 4 bytes
-    known annex keys: 1
-    known annex size: 4 bytes
-    bloom filter size: 16 mebibytes (0% full)
-    backend usage:
-            SHA256E: 2
-    ~/test-annex % ls -l
-    total 4
-    lrwxrwxrwx 1 richih richih 178 Jul 11 01:20 foo -> .git/annex/objects/91/9x/SHA256E-s4--b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c/SHA256E-s4--b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c
-    ~/test-annex % git annex import ../test-annex--foo/bar
-    ~/test-annex % ls -l
-    total 4
-    lrwxrwxrwx 1 richih richih 178 Jul 11 01:20 foo -> .git/annex/objects/91/9x/SHA256E-s4--b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c/SHA256E-s4--b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c
-    ~/test-annex %
-
-"""]]
diff --git a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_3_2c094bef802a2182de4fcd0def1ad29b._comment b/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_3_2c094bef802a2182de4fcd0def1ad29b._comment
deleted file mode 100644
index d3870e7c9..000000000
--- a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_3_2c094bef802a2182de4fcd0def1ad29b._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 3"
- date="2013-07-11T11:54:25Z"
- content="""
-To expand on this a bit:
-
-* I meant \"ugh, me\" not \"ugh, anyone else\"; I simply did not see it...
-* `git annex import` on a separate annex should copy over the symlinks and the objects behind it and then run `git annex add`, thus verifying, fixing symlinks, etc, imo.
-* Something that may not be said often enough: Thanks :)
-"""]]
diff --git a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_4_14915c43001f7f72c9fe5119a104ef5c._comment b/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_4_14915c43001f7f72c9fe5119a104ef5c._comment
deleted file mode 100644
index 4d4c1fbc5..000000000
--- a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/comment_4_14915c43001f7f72c9fe5119a104ef5c._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 4"
- date="2013-07-13T15:25:56Z"
- content="""
-After more deliberation, there should probably be an option to not have `git annex import` run `git annex add` automagically (but still call `git annex fix`) so manual shuffling around of files is still possible.
-
-See [[doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op]] for more of the rationale on this.
-"""]]
diff --git a/doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__.mdwn b/doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__.mdwn
deleted file mode 100644
index df589be93..000000000
--- a/doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-I've seen the [[tips/using box.com as a special remote]] for using mounted WebDAV remote directory for storage of the tracked files.
-
-It's quite close to a scenario familiar to me, although with a difference.
-
-Let me describe my situation.
-
-I worked on a supplement to a set of textbooks. My work was dependent on the revision of the textbooks (for correct references, etc.). The textbooks were being edited by the author, and published in a WebDAV directory.
-
-So I set up a Git repo for my work, and also a branch to track the revisions of the textbooks which [I updated by copying them from the WebDAV directory (after mounting it)](http://unix.stackexchange.com/q/25015/4319). The branch where my work was in was either based on the textbooks branch (and rebased/merged and edited to reflect the changes in the new revisions of the textbooks when needed) or contained the repo with textbooks as a submodule.
-
-The textbooks were large files, so I didn't want them be a part of the Git repo with my supplement work when I publish the repo. But I wanted for those who looked into my public repo to understand how to get the textbooks I'm referring to.
-
-I haven't solved this problem for myself completely. Now I see I could use git-annex for this. I t would track the state of the textbooks in the repo, without actually storing them there, and whenever one would need to get the missing textbooks in a clone of the repo, git-annex could handle the download from the WebDAV directory for him, right?
-
-I simply wrote down the rules for reproducing these downloading and saving operations, together with source URL (as a [Makefile](https://gitorious.org/primary-school-informatics-problems/received_2011-11-mathinf-initial-edition/blobs/RULES/Makefile)):
-
-whenever I wanted to update the revisions of the textbooks (or to download them the first time), I would checkout the branch which included this Makefile and was for holding the textbooks, and the run:
-
-    make get
-
--- this target had the temporary mountpoint for the remote directory as prerequisite, and there was a rule to create it, and mount the specified URL at it; then it would sync the files, and I could use Git to track the changes. After I was done inspecting the remote directory, I had to clean up the temporary mountpoint fby unmounting and deleting it. I didn't make it do this automatically after a `get` operation for performance reasons (caching of the remote directory would help if I wanted to access it once again).
-
-So, this differs from [[tips/using box.com as a special remote]] in that the tip for WebDAV suggest to handle the mounting manually, and git-annex knows nothing about the WebDAV URL where the content comes from.
-
-So here's my wish: a [[special remote|special remotes]] to track the WebDAV URLs in the repo, and mount the remote directory automatically under the hood, whenever one wants to get a file from there. (Then I assume it should also unmount it immediately in order to clean up after itself, despite possible inefficiencies).
-
-> I think the hooks are enough.. If not, you can use a hook special remote
-> or the external special remote protocol to make your own custom special
-> remote. So, [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__/comment_1_f46b0c9b49607e9f4f7a27f5a331ce83._comment b/doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__/comment_1_f46b0c9b49607e9f4f7a27f5a331ce83._comment
deleted file mode 100644
index 32dd9c039..000000000
--- a/doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__/comment_1_f46b0c9b49607e9f4f7a27f5a331ce83._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.153.14.141"
- subject="comment 1"
- date="2012-09-25T22:56:22Z"
- content="""
-Note that git-annex already has the git configs `remote.<name>.annex-start-command` and `remote.<name>.annex-stop-command` which can be used to handle mounting and umounting.
-"""]]
diff --git a/doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__/comment_2_1b34e1dd72011c65e881dec2543a0373._comment b/doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__/comment_2_1b34e1dd72011c65e881dec2543a0373._comment
deleted file mode 100644
index 80c5ed2a9..000000000
--- a/doc/todo/wishlist:_a_spec.remote_for_network_directories_that_would_mount_them_whenever_needed___40__e.g.__44___with_WebDAV__41__/comment_2_1b34e1dd72011c65e881dec2543a0373._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://lj.rossia.org/users/imz/"
- ip="79.165.56.162"
- subject="comment 2"
- date="2012-09-25T23:33:23Z"
- content="""
-I see, thanks for pointing at these config options! Perhaps, that'll be enough.
-
-I'll have to see whether the information on how to access the remote copy (the source URL and how to mount it) saved in config variables will be transferred to the clones of the repo.
-
-AFAIU [[location tracking]], usually, git-annex would transfer the information on where to look for copies from one repo to another.
-"""]]
diff --git a/doc/todo/wishlist:_addurl_https:.mdwn b/doc/todo/wishlist:_addurl_https:.mdwn
deleted file mode 100644
index 0a62eda6d..000000000
--- a/doc/todo/wishlist:_addurl_https:.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-It would be nice if "git annex addurl" allowed https: urls, rather than just http:.
-To give an example, here is a PDF file:
-
- https://www.fbo.gov/utils/view?id=59ba4c8aa59101a09827ab7b9a787b05
-
-If you switch the https: to http: it redirects you back to https:.
-
-As more sites provide https: for non-secret traffic, this becomes more of an issue.
-
-> I've gotten rid of the use of the HTTP library, now it just uses curl.
-> [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_addurl_https:/comment_1_4e8f5e1fc52c3000eb2a1dad0624906e._comment b/doc/todo/wishlist:_addurl_https:/comment_1_4e8f5e1fc52c3000eb2a1dad0624906e._comment
deleted file mode 100644
index fa500b1dd..000000000
--- a/doc/todo/wishlist:_addurl_https:/comment_1_4e8f5e1fc52c3000eb2a1dad0624906e._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 1"
- date="2013-01-26T08:44:38Z"
- content="""
-This works fine with \"git annex addurl\". 
-
-However, with --fast, it fails:
-
-  git-annex: user error (https not supported)
-
-This is because the Haskell HTTP library doesn't support https yet. <https://github.com/haskell/HTTP/issues/17> Seems to be very little momentum on fixing that, perhaps I need to switch the code to use http-enumerator, which does.
-"""]]
diff --git a/doc/todo/wishlist:_allow_configuration_of_downloader_for_addurl.mdwn b/doc/todo/wishlist:_allow_configuration_of_downloader_for_addurl.mdwn
deleted file mode 100644
index 81f7ee4c0..000000000
--- a/doc/todo/wishlist:_allow_configuration_of_downloader_for_addurl.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-It would be neat if Git annex addurl allowed a configuration option for a download manager command to do the actual download in place of wget/curl with a placeholder for the file name to save to & URL to get from (if that's all annex needs). That would allow the user to choose a graphical download manager if desired to make progress easier to monitor. The specific circumstance I'm seeing is with [[wishlist:_an___34__assistant__34___for_web-browsing_--_tracking_the_sources_of_the_downloads]]. I found that the existing Firefox addon [FlashGot](http://flashgot.net/) can run any command with arbitrary arguments including placeholders. Right now I've got a [script](https://gist.github.com/andyg0808/5342434) that changes to a user-selected directory and then runs git-annex addurl in it with the provided url. It works fine as a download manager for FlashGot. The issue is that there is no progress information for large file downloads. If git-annex could start a separate download manager to do the actual download, then the user would be able to check status at any time, even though the git-annex command was run from a GUI and not a terminal.
-
-> [[done]], you can use `annex.web-download-command` now. --[[Joey]]
diff --git a/doc/todo/wishlist:_allow_the_same_remote_to_be_accissable_via_different_methods.mdwn b/doc/todo/wishlist:_allow_the_same_remote_to_be_accissable_via_different_methods.mdwn
deleted file mode 100644
index 849e73cc3..000000000
--- a/doc/todo/wishlist:_allow_the_same_remote_to_be_accissable_via_different_methods.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-This is a wishlist item:
-
-Please allow the same remote to be available via different remotes. So in my LAN my remote is available using a ssh-connection, and when I travel with my laptop, the git-annex can also reach this remote using the Jabber transport.
-
-> [[done]]; this has always been fully supported. --[[Joey]]
diff --git a/doc/todo/wishlist:_allow_the_same_remote_to_be_accissable_via_different_methods/comment_1_abb6263f3807160222bba1122475c89c._comment b/doc/todo/wishlist:_allow_the_same_remote_to_be_accissable_via_different_methods/comment_1_abb6263f3807160222bba1122475c89c._comment
deleted file mode 100644
index a95ba56f9..000000000
--- a/doc/todo/wishlist:_allow_the_same_remote_to_be_accissable_via_different_methods/comment_1_abb6263f3807160222bba1122475c89c._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="2001:4978:f:21a::2"
- subject="comment 1"
- date="2013-08-07T16:09:26Z"
- content="""
-You can have as many git remotes as you like all pointing at the same repository via different paths. git-annex fully supports this AFAIK. Are you having some problem with it?
-"""]]
diff --git a/doc/todo/wishlist:_allow_users_to_provide_UUID_when_running___96__git_annex_init__96__.mdwn b/doc/todo/wishlist:_allow_users_to_provide_UUID_when_running___96__git_annex_init__96__.mdwn
deleted file mode 100644
index 0dc9ec08a..000000000
--- a/doc/todo/wishlist:_allow_users_to_provide_UUID_when_running___96__git_annex_init__96__.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-As there's no way to permanently hide remotes and I have to recreate two repos now, I would love to be able to re-use the old UUIDs to remove clutter.
-
-> git-annex already provides a way to do this: Copy `.git/config` from the
-> original repo (or use `git-config` to set `annex.uuid`) *before* running
-> `git annex init`. [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_assistant_autostart_port_and_secret_configuration.mdwn b/doc/todo/wishlist:_assistant_autostart_port_and_secret_configuration.mdwn
deleted file mode 100644
index a1aec1d49..000000000
--- a/doc/todo/wishlist:_assistant_autostart_port_and_secret_configuration.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-When starting the assistant when logging in to the system (`--autostart`) it choses a new port an secret everytime. Having the assistant open in a pinned firefox tab which automatically restores when firefox starts we need to get the url from `.git/annex/url` and copy/paste it into the pinned tab. It would be very nice to have a configuration option which assigns a fixed port and secret so everytime the assistant is autostarted it uses the same settings and firefox is happy to open it automatically on start.
-
-> Closing, I've removed the option to choose webapp ports entirely.
-> [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_assistant_autostart_port_and_secret_configuration/comment_1_be53b8456eed7eadad5d4b8465c8a42b._comment b/doc/todo/wishlist:_assistant_autostart_port_and_secret_configuration/comment_1_be53b8456eed7eadad5d4b8465c8a42b._comment
deleted file mode 100644
index 651937802..000000000
--- a/doc/todo/wishlist:_assistant_autostart_port_and_secret_configuration/comment_1_be53b8456eed7eadad5d4b8465c8a42b._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 1"
- date="2013-11-22T16:58:51Z"
- content="""
-It's impossible to guarantee a program will be able to get a particular port. Any other program could be using that port number.
-
-This is why `git annex webapp` opens the webapp using whatever url the assistant has picked. I recommend that rather than using a pinned tab, you make an icon on your desktop that runs `git annex webapp`, and use that to open the app when you want it, much as you'd open any other app. If you wanted to, you could make your system run `git annex webapp` on startup instead of `git annex assistant --autostart`, and you'd get the browser tab opened automatically on start.
-"""]]
diff --git a/doc/todo/wishlist:_command_options_changes.mdwn b/doc/todo/wishlist:_command_options_changes.mdwn
deleted file mode 100644
index b15440181..000000000
--- a/doc/todo/wishlist:_command_options_changes.mdwn
+++ /dev/null
@@ -1,17 +0,0 @@
-Some suggestions for changes to command options:
-
-  * --verbose:
-    * add alternate: -v
-
-  * --from:
-    * replace with: -s $SOURCE || --source=$SOURCE
-
-  * --to:
-    * replace with: -d $DESTINATION || --destination=$DESTINATION
-
-  * --force:
-    * add alternate: -F
-      * "-f" was removed in v0.20110417
-      * since it forces unsafe operations, should be capitalized to reduce chance of accidental usage.
-
-[[done]], see comments
diff --git a/doc/todo/wishlist:_command_options_changes/comment_1_bfba72a696789bf21b2435dea15f967a._comment b/doc/todo/wishlist:_command_options_changes/comment_1_bfba72a696789bf21b2435dea15f967a._comment
deleted file mode 100644
index 0ab113211..000000000
--- a/doc/todo/wishlist:_command_options_changes/comment_1_bfba72a696789bf21b2435dea15f967a._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-04-17T23:46:37Z"
- content="""
---to and --from seem to have different semantics than --source and --destination. Subtle, but still different.
-
-That being said, I am not sure --from and --to are needed at all. Calling the local repo . and all remotes by their name, they are arguably redundant and removing them would make the syntax a lot prettier; mv and cp don't need them, either.
-
-I am not sure changing syntax at this point is considered good style though personally, I wouldn't mind adapting and would actually prefer it over using --to and --from.
-
--v and -q would be nice.
-
-
-Richard
-"""]]
diff --git a/doc/todo/wishlist:_command_options_changes/comment_2_f6a637c78c989382e3c22d41b7fb4cc2._comment b/doc/todo/wishlist:_command_options_changes/comment_2_f6a637c78c989382e3c22d41b7fb4cc2._comment
deleted file mode 100644
index 0072ae1d7..000000000
--- a/doc/todo/wishlist:_command_options_changes/comment_2_f6a637c78c989382e3c22d41b7fb4cc2._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-04-19T20:13:10Z"
- content="""
-Let's see..
-
-* -v is already an alias for --verbose
-
-* I don't find --source and --destination as easy to type or as clear as --from or --to.
-
-* -F is fast, so it cannot be used for --force. And I have no desire to make it easy to mistype a short option and enable --force; it can lose data. 
-
-@richard while it would be possible to support some syntax like \"git annex copy . remote\"; what is it supposed to do if there are local files named foo and bar, and a remotes named foo and bar? Does \"git annex copy foo bar\" copy file foo to remote bar, or file bar from remote foo? I chose to use --from/--to to specify remotes independant of files to avoid such
-ambiguity, which plain old `cp` doesn't have since it's operating entirely on filesystem objects, not both filesystem objects and abstract remotes.
-
-Seems like nothing to do here. [[done]] --[[Joey]]
-"""]]
diff --git a/doc/todo/wishlist:_command_options_changes/comment_3_bf1114533d2895804e531e76eb6b8095._comment b/doc/todo/wishlist:_command_options_changes/comment_3_bf1114533d2895804e531e76eb6b8095._comment
deleted file mode 100644
index 9fcbae6d2..000000000
--- a/doc/todo/wishlist:_command_options_changes/comment_3_bf1114533d2895804e531e76eb6b8095._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 3"
- date="2011-04-20T21:28:06Z"
- content="""
-Good point. scp fixes this by using a colon, but as colons aren't needed in git-annex remotes' names... -- RichiH
-"""]]
diff --git a/doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn b/doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn
deleted file mode 100644
index a3beaadae..000000000
--- a/doc/todo/wishlist:_define_remotes_that_must_have_all_files.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-I would like to be able to name a few remotes that must retain *all* annexed
-files.  `git-annex fsck` should warn me if any files are missing from those
-remotes, even if `annex.numcopies` has been satisfied by other remotes.
-
-I imagine this could also be useful for bup remotes, but I haven't actually
-looked at those yet.
-
-Based on existing output, this is what a warning message could look like:
-
-	fsck FILE
-		3 of 3 trustworthy copies of FILE exist.
-		FILE is, however, still missing from these required remotes:
-			UUID -- Backup Drive 1
-			UUID -- Backup Drive 2
-		Back it up with git-annex copy.
-	Warning
-
-What do you think?
-
-> I think that [[required_content]] will make it easy to configure
-> such remotes, so this is another reason to build that. Closing
-> this bug as a dup of that one; [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_define_remotes_that_must_have_all_files/comment_1_cceccc1a1730ac688d712b81a44e31c3._comment b/doc/todo/wishlist:_define_remotes_that_must_have_all_files/comment_1_cceccc1a1730ac688d712b81a44e31c3._comment
deleted file mode 100644
index 1f65fd982..000000000
--- a/doc/todo/wishlist:_define_remotes_that_must_have_all_files/comment_1_cceccc1a1730ac688d712b81a44e31c3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-04-23T16:27:13Z"
- content="""
-Seems to have a scalability problem, what happens when such a repository becomes full?
-
-Another way to accomplish I think the same thing is to pick the repositories that you would include in such a set, and make all other repositories untrusted. And set numcopies as desired. Then git-annex will never remove files from the set of non-untrusted repositories, and fsck will warn if a file is present on only an untrusted repository.
-"""]]
diff --git a/doc/todo/wishlist:_define_remotes_that_must_have_all_files/comment_2_eec848fcf3979c03cbff2b7407c75a7a._comment b/doc/todo/wishlist:_define_remotes_that_must_have_all_files/comment_2_eec848fcf3979c03cbff2b7407c75a7a._comment
deleted file mode 100644
index 1855cdda0..000000000
--- a/doc/todo/wishlist:_define_remotes_that_must_have_all_files/comment_2_eec848fcf3979c03cbff2b7407c75a7a._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="gernot"
- ip="87.79.209.169"
- subject="comment 2"
- date="2011-04-24T11:20:05Z"
- content="""
-Right, I have thought about untrusting all but a few remotes to achieve
-something similar before and I'm sure it would kind of work. It would be more
-of an ugly workaround, however, because I would have to untrust remotes that
-are, in reality, at least semi-trusted. That's why an extra option/attribute
-for that kind of purpose/remote would be nice.
-
-Obviously I didn't see the scalability problem though. Good Point. Maybe I can
-achieve the same thing by writing a log parsing script for myself?
-
-"""]]
diff --git a/doc/todo/wishlist:_detection_of_merge_conflicts.mdwn b/doc/todo/wishlist:_detection_of_merge_conflicts.mdwn
deleted file mode 100644
index 1b4caeff0..000000000
--- a/doc/todo/wishlist:_detection_of_merge_conflicts.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-A conflict during sync or merge is something that requires user intervention, or at least notification. For that reason it would be nice if git annex returned a nonzero exit status when such a conflict happened during a sync or a merge. This is what git does after a conflicting pull, and would make it easier to spot a conflict in automated syncs without having to parse annex output or the logs.
-
-> Good idea, [[done]]. --[[Joey]] 
-
-Also, it would be nice if your new `git annex status` were able to inform about remaining conflicts in the repo, for instance by reporting files with variant-XXX suffix.
-
-> Hmm, that would need a separate pass through the whole tree, since
-> currently it can use `git ls-files` to find only modified/deleted/new
-> files. I would rather not make the new `git annex status` slower for
-> this.
-> 
-> It would be possible to add it to `git annex info` (old `status`)
-> which already has to look through the entire work tree.
diff --git a/doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied.mdwn b/doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied.mdwn
deleted file mode 100644
index 837f0a587..000000000
--- a/doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied.mdwn
+++ /dev/null
@@ -1,6 +0,0 @@
-When addWatcher gets a permission denied, it would be helpful to display the name of the object on which the permission was denied, in the error message which shows in the webapp.
-
-> I have made the inotify code more robust; now it doesn't crash if it
-> cannot read a directory or a file, and only logs a warning, which includes
-> the directory name.
-> [[done]] --[[Joey]] 
diff --git a/doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied/comment_1_d2665e7347689b520d37561cfddf0aa8._comment b/doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied/comment_1_d2665e7347689b520d37561cfddf0aa8._comment
deleted file mode 100644
index de0528855..000000000
--- a/doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied/comment_1_d2665e7347689b520d37561cfddf0aa8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.152.108.220"
- subject="comment 1"
- date="2013-09-25T18:47:13Z"
- content="""
-This is an exception from the inotify library, which is what contains the `addWatch` function. I catch and display the exception. Since `addWatch` is only passed a directory to watch, the most I could do is tack on the name of the directory when displaying the exception. That does not seem likely to be much help?
-"""]]
diff --git a/doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied/comment_2_db153571a32fb072453ed583e3e9ccf4._comment b/doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied/comment_2_db153571a32fb072453ed583e3e9ccf4._comment
deleted file mode 100644
index e0199a42d..000000000
--- a/doc/todo/wishlist:_display_name_of_object_when_addWatcher_gets_a_permission_denied/comment_2_db153571a32fb072453ed583e3e9ccf4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl-g0hYpGY11pBP_42lHh5GWTyFuB4UwH8"
- nickname="Nicolas"
- subject="comment 2"
- date="2013-09-25T23:08:56Z"
- content="""
-Well, of course it would not be as helpful as if the inotify exception would contain the name of the exact object on which it got a permission denied (would this be a valid wishlist request for inotify?), but I think that displaying the name of the directory would already be better than nothing.
-"""]]
diff --git a/doc/todo/wishlist:_dropping_git-annex_history.mdwn b/doc/todo/wishlist:_dropping_git-annex_history.mdwn
deleted file mode 100644
index 8286699c7..000000000
--- a/doc/todo/wishlist:_dropping_git-annex_history.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-In real life discussions with git-annex users at DebConf, the idea was proposed to have a way to drop the history of the git-annex branch, and replace it with a new branch with just the current state of the repository. 
-
-The only thing that breaks when this is done, in theory, is `git annex log`, which can't show the location history 
-of files.
-
-The crucial thing is that this operation would only need to be done in one repository, and it would then record some information in its (new) git-annex branch, so when it was pushed to other repositories, git-annex there could notice that history had been dropped, and do the same. So, even if you have rarely used offline archive repositories, the history dropping would eventually reach them, without needing to remember to do it.
-
-There was speculation that it would be enough to record eg, the SHA of the top commit on the old branch. That may not be good enough, because another remote may have not gotten that SHA into its branch yet, or may have commits on top of that SHA. 
-
-Maybe instead we want to record the SHA of the *first* commit to the old git-annex branch. This way, we can tell if the branch that got deleted is the one we're currently using. And if it is, we create a new branch with the current state of *our* branch, and then union merge the other branch into it.
-
-Hmm, another wrinkle is that, when this indication propigates from remote A to remote B, remote B may also have some git-annex branches available for remotes C and D, which have not transitioned, and E, which has transitioned already. It seems B should first union merge C and D into B, and then flatten B to B', and then union merge A and E into B'.
-
-I think that'd work!
-
---[[Joey]]
-
-Will also allow dropping dead remotes from history. Just remove all
-references to them when rewriting the branch. May or may not be desirable;
-I sometimes care about dead remotes that I hope to one day recuscitate.
-(OTOH, I can always run git annex fsck in them to get their location
-tracking back, if I do manage to get them back.)
-
---[[Joey]] 
-
-See also : [[forum/safely_dropping_git-annex_history]]
-
-> [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_dropping_git-annex_history/comment_1_a4bee2e26b22a9bdaadc05b7227769ef._comment b/doc/todo/wishlist:_dropping_git-annex_history/comment_1_a4bee2e26b22a9bdaadc05b7227769ef._comment
deleted file mode 100644
index 043e674ed..000000000
--- a/doc/todo/wishlist:_dropping_git-annex_history/comment_1_a4bee2e26b22a9bdaadc05b7227769ef._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 1"
- date="2013-08-24T19:39:45Z"
- content="""
-BTW, a motivation for this is that some of us have old repositories that have been upgrades all the way from annex.version 1 and have a lot of cruft in them because of it. (I have repos that have been upgraded from annex.version 0, but this would not help with that cruft which is on the master branch!)
-
-Also, people worry that eg, a large copy back and forth bloats history, and having a way to unbloat it if it ever gets actually annoyingly bloated would stop them pestering me. ;)
-"""]]
diff --git a/doc/todo/wishlist:_dropping_git-annex_history/comment_2_f6d750bfe0c9d8a2aa6bc218ca5c49cc._comment b/doc/todo/wishlist:_dropping_git-annex_history/comment_2_f6d750bfe0c9d8a2aa6bc218ca5c49cc._comment
deleted file mode 100644
index a60973b82..000000000
--- a/doc/todo/wishlist:_dropping_git-annex_history/comment_2_f6d750bfe0c9d8a2aa6bc218ca5c49cc._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2013-08-27T20:02:23Z"
- content="""
-If starting commit id _and_ commit id from when history is being dropped are documented, you could potentially drop more data.
-
-* Don't have any commits in common? Full merge.
-* Only share the starting ids? Reduce local history as much as possible, and then merge.
-* Share both starting id and have the last id somewhere in history? Take history from last id up to current, reduce that, and merge.
-
--- RichiH
-"""]]
diff --git a/doc/todo/wishlist:_git-annex_replicate.mdwn b/doc/todo/wishlist:_git-annex_replicate.mdwn
deleted file mode 100644
index 9ac6ade75..000000000
--- a/doc/todo/wishlist:_git-annex_replicate.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-I'd like to be able to do something like the following:
-
- * Create encrypted git-annex remotes on a couple of semi-trusted machines - ones that have good connectivity, but non-redundant hardware
- * set numcopies=3
- * run `git-annex replicate` and have git-annex run the appropriate copy commands to make sure every file is on at least 3 machines
-
-There would also likely be a `git annex rebalance` command which could be used if remotes were added or removed.  If possible, it should copy files between servers directly, rather than proxy through a potentially slow client.
-
-There might be the need to have a 'replication_priority' option for each remote that configures which machines would be preferred.  That way you could set your local server to a high priority to ensure that it is always 1 of the 3 machines used and files are distributed across 2 of the remaining remotes.  Other than priority, other options that might help:
-
- * maxspace - A self imposed quota per remote machine.  git-annex replicate should try to replicate files first to machines with more free space. maxspace would change the free space calculation to be `min(actual_free_space, maxspace - space_used_by_git_annex)
- * bandwidth - when replication files, copies should be done between machines with the highest available bandwidth. ( I think this option could be useful for git-annex get in general)
-
-> `git annex sync --content` handles this now. [[done]]
-> 
-> You do need to run it, or the assistant, on each node that needs
-> to copy files to spread them through the network. 
->
-> A `git annex rebalance`
-> is essentially the same as sshing to the remote and running `git annex
-> sync --content` there. Assuming the remote repository itself has enough
-> remotes set up that git-annex is able to copy files around. --[[Joey]]
diff --git a/doc/todo/wishlist:_git-annex_replicate/comment_1_9926132ec6052760cdf28518a24e2358._comment b/doc/todo/wishlist:_git-annex_replicate/comment_1_9926132ec6052760cdf28518a24e2358._comment
deleted file mode 100644
index cec971ee3..000000000
--- a/doc/todo/wishlist:_git-annex_replicate/comment_1_9926132ec6052760cdf28518a24e2358._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-04-22T18:27:00Z"
- content="""
-While having remotes redistribute introduces some obvious security concerns, I might use it.
-
-As remotes support a cost factor already, you can basically implement bandwidth through that.
-"""]]
diff --git a/doc/todo/wishlist:_git-annex_replicate/comment_2_c43932f4194aba8fb2470b18e0817599._comment b/doc/todo/wishlist:_git-annex_replicate/comment_2_c43932f4194aba8fb2470b18e0817599._comment
deleted file mode 100644
index 9d50d1531..000000000
--- a/doc/todo/wishlist:_git-annex_replicate/comment_2_c43932f4194aba8fb2470b18e0817599._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-04-23T16:22:07Z"
- content="""
-Besides the cost values, annex.diskreserve was recently added. (But is not available for special remotes.)
-
-I have held off on adding high-level management stuff like this to git-annex, as it's hard to make it generic enough to cover use cases.
-
-A low-level way to accomplish this would be to have a way for `git annex get` and/or `copy` to skip files when `numcopies` is already satisfied. Then cron jobs could be used.
-"""]]
diff --git a/doc/todo/wishlist:_git-annex_replicate/comment_3_c13f4f9c3d5884fc6255fd04feadc2b1._comment b/doc/todo/wishlist:_git-annex_replicate/comment_3_c13f4f9c3d5884fc6255fd04feadc2b1._comment
deleted file mode 100644
index e7eb06b3b..000000000
--- a/doc/todo/wishlist:_git-annex_replicate/comment_3_c13f4f9c3d5884fc6255fd04feadc2b1._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 3"
- date="2011-04-23T17:54:42Z"
- content="""
-Hmm, so it seems there is almost a way to do this already.
-
-I think the one thing that isn't currently possible is to have 'plain' ssh remotes.. basically something just like the directory remote, but able to take a ssh user@host/path url.  something like sshfs could be used to fake this, but for things like fsck you would want to do the sha1 calculations on the remote host.
-"""]]
diff --git a/doc/todo/wishlist:_git-annex_replicate/comment_4_63f24abf086d644dced8b01e1a9948c9._comment b/doc/todo/wishlist:_git-annex_replicate/comment_4_63f24abf086d644dced8b01e1a9948c9._comment
deleted file mode 100644
index 3805464a6..000000000
--- a/doc/todo/wishlist:_git-annex_replicate/comment_4_63f24abf086d644dced8b01e1a9948c9._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 4"
- date="2011-09-19T18:54:46Z"
- content="""
-git annex get/copy/drop all now support a --auto flag, which makes them only act on files that have not enough or too many copies. This allows for some crude replication; it doesn't take into account which repositories should be filled up more (beyond honoring annex.diskreserve), nor does it try to optimally use bandwidth (beyond honoring configured annex-cost). You have to run it in every repository that you want to participate in the replication, too. But it's probably a Good Enough solution. See [[walkthrough/automatically_managing_content]].
-"""]]
diff --git a/doc/todo/wishlist:_git_annex_group_remote_return_the_group.mdwn b/doc/todo/wishlist:_git_annex_group_remote_return_the_group.mdwn
deleted file mode 100644
index 5c8d8b011..000000000
--- a/doc/todo/wishlist:_git_annex_group_remote_return_the_group.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-Hi,
-
-It would be good if the command 
-
-    git annex group repository
-
-returned the current list of groups the repository belongs to...(can it belong to more than one?)
-
-Currently the command requires an additional parameter to set the group.
-
-> [[done]] --[[Joey]] 
diff --git a/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults.mdwn b/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults.mdwn
deleted file mode 100644
index e1dc89a96..000000000
--- a/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults.mdwn
+++ /dev/null
@@ -1,20 +0,0 @@
-I am running centralized git-annex exclusively.
-
-Similar to
-
-    git annex get
-
-I'd like to have a
-
-    git annex put
-
-which would put all files on the default remote(s).
-
-My main reason for not wanting to use copy --to is that I need to specify the remote's name in this case which makes writing a wrapper unnecessarily hard. Also, this would allow
-
-    mr push
-
-to do the right thing all by itself.
-
-> I feel that the new `git annex sync --content` is pretty close to what's
-> requested here. [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_1_d5413c8acce308505e4e2bec82fb1261._comment b/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_1_d5413c8acce308505e4e2bec82fb1261._comment
deleted file mode 100644
index fe1d5520f..000000000
--- a/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_1_d5413c8acce308505e4e2bec82fb1261._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-04-04T18:13:46Z"
- content="""
-This begs the question: What is the default remote? It's probably *not* the same repository that git's master branch is tracking (ie, origin/master). It seems there would have to be an annex.defaultremote setting.
-
-BTW, mr can easily be configured on a per-repo basis so that \"mr push\" copies to somewhere: `push = git push; git annex push wherever`
-"""]]
diff --git a/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_2_0aa227c85d34dfff4e94febca44abea8._comment b/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_2_0aa227c85d34dfff4e94febca44abea8._comment
deleted file mode 100644
index 3090b575b..000000000
--- a/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_2_0aa227c85d34dfff4e94febca44abea8._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2011-04-04T20:45:30Z"
- content="""
-In my case, the remotes are the same, but adding a new option could make sense.
-
-And while I can tell mr what to do explicitly, I would prefer if it did the right thing all by itself. Having to change configs in two separate places is less than ideal.
-
-I am not sure what you mean by `git annex push` as that does not exist. Did you mean copy?
-"""]]
diff --git a/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_3_2082f4d708a584a1403cc1d4d005fb56._comment b/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_3_2082f4d708a584a1403cc1d4d005fb56._comment
deleted file mode 100644
index 01dc7813f..000000000
--- a/doc/todo/wishlist:_git_annex_put_--_same_as_get__44___but_for_defaults/comment_3_2082f4d708a584a1403cc1d4d005fb56._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 1"
- date="2011-04-04T10:28:01Z"
- content="""
-Going one step further, a --min-copy could put all files so that numcopies is satisfied. --all could push to all available ones.
-
-To take everything another step further, if it was possible to group remotes, one could act on the groups. \"all\" would be an obvious choice for a group that always exists, everything else would be set up by the user.
-"""]]
diff --git a/doc/todo/wishlist:_git_annex_status.mdwn b/doc/todo/wishlist:_git_annex_status.mdwn
deleted file mode 100644
index 6bb5d71f1..000000000
--- a/doc/todo/wishlist:_git_annex_status.mdwn
+++ /dev/null
@@ -1,21 +0,0 @@
-Ideally, it would look similar to this. And yes, I put "put" in there ;)
-
-    non-annex % git annex status
-    git annex status: error: not a git annex repository
-    annex % git annex status
-    annex object storage version: A
-    annex backend engine: {WORM,SHA512,...}
-    Estimated local annex size: B MiB
-    Estimated total annex size: C MiB
-    Files without file size information in local annex: D
-    Files without file size information in total annex: E
-    Last fsck: datetime
-    Last git pull: datetime - $annex_name
-    Last git push: datetime - $annex_name
-    Last git annex get: datetime - $annex_name
-    Last git annex put: datetime - $annex_name
-    annex %
-
-Datetime could be ISO's YYYY-MM-DDThh:mm:ss or, personal preference, YYYY-MM-DD--hh-mm-ss. I prefer the latter as it's DNS-, tag- and filename-safe which is why I am using it for everything. In a perfect world, ISO would standardize YYYY-MM-DD-T-hh-mm-ss-Z[-SSSSSSSS][--$timezone], but meh.
-
-[[done]]
diff --git a/doc/todo/wishlist:_git_annex_status/comment_1_994bfd12c5d82e08040d6116915c5090._comment b/doc/todo/wishlist:_git_annex_status/comment_1_994bfd12c5d82e08040d6116915c5090._comment
deleted file mode 100644
index 7b5e7bd44..000000000
--- a/doc/todo/wishlist:_git_annex_status/comment_1_994bfd12c5d82e08040d6116915c5090._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 1"
- date="2011-04-08T07:23:08Z"
- content="""
-+1 for this feature, I've been longing for something like this other than rolling my own perl/shell scripts to parse the outputs of \"git annex whereis .\" to see how many files are on my machine or not.
-"""]]
diff --git a/doc/todo/wishlist:_git_annex_status/comment_2_c2b0ce025805b774dc77ce264a222824._comment b/doc/todo/wishlist:_git_annex_status/comment_2_c2b0ce025805b774dc77ce264a222824._comment
deleted file mode 100644
index 21f9d713c..000000000
--- a/doc/todo/wishlist:_git_annex_status/comment_2_c2b0ce025805b774dc77ce264a222824._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://christian.amsuess.com/chrysn"
- nickname="chrysn"
- subject="format, respect working directory"
- date="2011-04-26T12:31:02Z"
- content="""
-we could include the information about the current directory as well, if the command is not issued in the local git root directory. to avoid large numbers of similar lines, that could look like this:
-
-    Estimated annex size: B MiB (of C MiB; [B/C]%)
-    Estimated annex size in $PWD: B' MiB (of C' MiB; [B'/C']%)
-
-with the percentages being replaced with \"complete\" if really all files are present (and not just many enough for the value to be rounded to 100%).
-"""]]
diff --git a/doc/todo/wishlist:_git_annex_status/comment_3_d1fd70c67243971c96d59e1ffb7ef6e7._comment b/doc/todo/wishlist:_git_annex_status/comment_3_d1fd70c67243971c96d59e1ffb7ef6e7._comment
deleted file mode 100644
index 39986144b..000000000
--- a/doc/todo/wishlist:_git_annex_status/comment_3_d1fd70c67243971c96d59e1ffb7ef6e7._comment
+++ /dev/null
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 3"
- date="2011-05-17T01:15:10Z"
- content="""
-What a good idea!
-
-150 lines of haskell later, I have this:
-
-<pre>
-# git annex status
-supported backends: WORM SHA1 SHA256 SHA512 SHA224 SHA384 SHA1E SHA256E SHA512E SHA224E SHA384E URL
-supported remote types: git S3 bup directory rsync hook
-local annex keys: 32
-local annex size: 58 megabytes
-total annex keys: 38158
-total annex size: 6 terabytes (but 1632 keys have unknown size)
-backend usage: 
-	SHA1: 1789
-	WORM: 36369
-</pre>
-"""]]
diff --git a/doc/todo/wishlist:_git_annex_status/comment_4_9aeeb83d202dc8fb33ff364b0705ad94._comment b/doc/todo/wishlist:_git_annex_status/comment_4_9aeeb83d202dc8fb33ff364b0705ad94._comment
deleted file mode 100644
index f006f88a0..000000000
--- a/doc/todo/wishlist:_git_annex_status/comment_4_9aeeb83d202dc8fb33ff364b0705ad94._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://christian.amsuess.com/chrysn"
- nickname="chrysn"
- subject="status of other remotes?"
- date="2011-06-15T08:39:24Z"
- content="""
-using the location tracking information, it should be possible to show the status of other remotes as well. what about supporting `--from=...` or `--all`? (thus, among other things, one could determine if a remote has a complete checkout.)
-"""]]
diff --git a/doc/todo/wishlist:_git_backend_for_git-annex.mdwn b/doc/todo/wishlist:_git_backend_for_git-annex.mdwn
deleted file mode 100644
index fd1b40bff..000000000
--- a/doc/todo/wishlist:_git_backend_for_git-annex.mdwn
+++ /dev/null
@@ -1,9 +0,0 @@
-Preamble: Obviously, the core feature of git-annex is the ability to keep a subset of files in a local repo. The main trade-off is that you don't get version tracking.
-
-Use case: On my laptop, I might not have enough disk space to store everything. Not so for my main box nor my backup server. And I would _really_ like to have proper version tracking for many of my files. Thus...
-
-Wish: ...why not use git as a version backend? That way, I could just push all my stuff to the central instance(s) and have the best of both worlds. Depending on what backend is used in the local repos, it might make sense to define a list of supported client backends with pre-computed keys.
-
--- RichiH
-
-[[done]] (bup)
diff --git a/doc/todo/wishlist:_git_backend_for_git-annex/comment_1_04319051fedc583e6c326bb21fcce5a5._comment b/doc/todo/wishlist:_git_backend_for_git-annex/comment_1_04319051fedc583e6c326bb21fcce5a5._comment
deleted file mode 100644
index a691393b1..000000000
--- a/doc/todo/wishlist:_git_backend_for_git-annex/comment_1_04319051fedc583e6c326bb21fcce5a5._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-03-28T16:01:30Z"
- content="""
-Indeed, see [[todo/add_a_git_backend]], where you and I have already discussed this idea. :)
-
-With the new support for special remotes, which will be used by S3, it would be possible to make such a git repo, using bup, be a special remote. I think it would be pretty easy to implement now. Not a priority for me though.
-"""]]
diff --git a/doc/todo/wishlist:_git_backend_for_git-annex/comment_2_7f529f19a47e10b571f65ab382e97fd5._comment b/doc/todo/wishlist:_git_backend_for_git-annex/comment_2_7f529f19a47e10b571f65ab382e97fd5._comment
deleted file mode 100644
index 14798e7a7..000000000
--- a/doc/todo/wishlist:_git_backend_for_git-annex/comment_2_7f529f19a47e10b571f65ab382e97fd5._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2011-03-28T17:47:38Z"
- content="""
-On the plus side, the past me wanted exactly what I had in mind.
-
-On the meh side, I really forgot about this conversation :/
-
-When you say this todo is not a priority, does that mean there's no ETA at all and that it will most likely sleep for a long time? Or the almost usual \"what the heck, I will just wizard it up in two lines of haskell\"?
-
--- RichiH
-"""]]
diff --git a/doc/todo/wishlist:_git_backend_for_git-annex/comment_3_a077bbad3e4b07cce019eb55a45330e7._comment b/doc/todo/wishlist:_git_backend_for_git-annex/comment_3_a077bbad3e4b07cce019eb55a45330e7._comment
deleted file mode 100644
index 8c3286d27..000000000
--- a/doc/todo/wishlist:_git_backend_for_git-annex/comment_3_a077bbad3e4b07cce019eb55a45330e7._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 3"
- date="2011-03-28T20:05:13Z"
- content="""
-Probably more like 150 lines of haskell. Maybe just 50 lines if the bup repository is required to be on the same computer as the git-annex repository.
-
-Since I do have some repositories where I'd appreciate this level of assurance that data not be lost, it's mostly a matter of me finding a free day.
-"""]]
diff --git a/doc/todo/wishlist:_git_backend_for_git-annex/comment_4_ecca429e12d734b509c671166a676c9d._comment b/doc/todo/wishlist:_git_backend_for_git-annex/comment_4_ecca429e12d734b509c671166a676c9d._comment
deleted file mode 100644
index cf649a8a2..000000000
--- a/doc/todo/wishlist:_git_backend_for_git-annex/comment_4_ecca429e12d734b509c671166a676c9d._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 4"
- date="2011-03-28T20:45:35Z"
- content="""
-Personally, I would not mind a requirement to keep a local bup repo. I wouldn't want my data to to unncessarily complex setups, anyway. -- RichiH
-"""]]
diff --git a/doc/todo/wishlist:_git_backend_for_git-annex/comment_5_3459f0b41d818c23c8fb33edb89df634._comment b/doc/todo/wishlist:_git_backend_for_git-annex/comment_5_3459f0b41d818c23c8fb33edb89df634._comment
deleted file mode 100644
index a1300f2e6..000000000
--- a/doc/todo/wishlist:_git_backend_for_git-annex/comment_5_3459f0b41d818c23c8fb33edb89df634._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 5"
- date="2011-04-08T20:59:37Z"
- content="""
-My estimates were pretty close -- the new bup special remote type took 133 lines of code, and 2 hours to write. A testament to the flexibility of the special remote infrastructure. :)
-"""]]
diff --git a/doc/todo/wishlist:_incremental_unannex___40__currently_requires_twice_the_size_of_repo_to_complete__41__.mdwn b/doc/todo/wishlist:_incremental_unannex___40__currently_requires_twice_the_size_of_repo_to_complete__41__.mdwn
deleted file mode 100644
index 420fb882c..000000000
--- a/doc/todo/wishlist:_incremental_unannex___40__currently_requires_twice_the_size_of_repo_to_complete__41__.mdwn
+++ /dev/null
@@ -1,10 +0,0 @@
-I recently tried to use unannex for a large repo and it failed because the repo size was more than half the disk size.  Unannex should work incrementally so this isn't a problem.
-
-Proposed solution:
-copy a file, hash it, iff hash check is okay, delete from objects, continue to next file
-
-> That won't work, because multiple files can point to a key.
-> 
-> I am not happy with unannex's behavior, but I was less happy
-> when people were constantly filing bugs about it misbehaving in that
-> situttion. If you dislike the copying, use --fast. [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_incremental_unannex___40__currently_requires_twice_the_size_of_repo_to_complete__41__/comment_1_067b29fc47d26b9da0766f9810684ae8._comment b/doc/todo/wishlist:_incremental_unannex___40__currently_requires_twice_the_size_of_repo_to_complete__41__/comment_1_067b29fc47d26b9da0766f9810684ae8._comment
deleted file mode 100644
index 372bb621f..000000000
--- a/doc/todo/wishlist:_incremental_unannex___40__currently_requires_twice_the_size_of_repo_to_complete__41__/comment_1_067b29fc47d26b9da0766f9810684ae8._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="GLITTAH"
- ip="78.108.63.46"
- subject="comment 1"
- date="2013-11-19T18:15:15Z"
- content="""
-Perhaps when unannex is invoked, it could check to see if there is enough disk space before it begins copying files.  Maybe even warn the user of too little disk space and remind them of --fast.
-
-(Sorry for the dupe!)
-"""]]
diff --git a/doc/todo/wishlist:_metadata_metadata_view.mdwn b/doc/todo/wishlist:_metadata_metadata_view.mdwn
deleted file mode 100644
index a4b243cdd..000000000
--- a/doc/todo/wishlist:_metadata_metadata_view.mdwn
+++ /dev/null
@@ -1,23 +0,0 @@
-Currently looking at the metadata and views.
-
-One of the things I would like to do is have a view that shows files by metadata metadata.. for example, "when the file last had tags changed".
-
-Something along the lines of
-
-    $ git annex view metadata-tag-mtime=YYYYMMDD
-    view  (searching...)
-    
-    Switched to branch 'views/metadata/tag/mtime/YYYYMMDD'
-    ok
-    
-    $ ls
-    20130816
-    20130921
-    20131015
-
-This would allow me to review files that haven't had any tag changes applied for a while and thus, may need the tags updating.
-
-I've done this in every tagging system I've used by (ab)using mtime, but that requires an additional step (of touching the file).
-
-> [[done]]; "$field-lastchanged" is automatically made available for each
-> field! --[[Joey]]
diff --git a/doc/todo/wishlist:_metadata_metadata_view/comment_1_79dbf48cf2e0d649f32bd077f0c9bc5a._comment b/doc/todo/wishlist:_metadata_metadata_view/comment_1_79dbf48cf2e0d649f32bd077f0c9bc5a._comment
deleted file mode 100644
index 126a9148c..000000000
--- a/doc/todo/wishlist:_metadata_metadata_view/comment_1_79dbf48cf2e0d649f32bd077f0c9bc5a._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.154"
- subject="comment 1"
- date="2014-03-18T17:09:55Z"
- content="""
-I think this would be pretty easy to do actually. No need to trawl through git history to find when a field changed; the metadata log file format includes the timestamp when a line was changed, so it would only need to find the newest timestamp for the field in the current version of the file.
-"""]]
diff --git a/doc/todo/wishlist:_metadata_metadata_view/comment_2_5763d0e403c476ac692c1cd50630f824._comment b/doc/todo/wishlist:_metadata_metadata_view/comment_2_5763d0e403c476ac692c1cd50630f824._comment
deleted file mode 100644
index 8b3fc3108..000000000
--- a/doc/todo/wishlist:_metadata_metadata_view/comment_2_5763d0e403c476ac692c1cd50630f824._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 2"
- date="2014-03-19T11:18:19Z"
- content="""
-Can $field be a glob? i.e. *
-
-I'm looking for the files to be organised to the last change date to *any* metadata, not a specific field.
-
-For example, I may have added some vacation photos and set some metadata (location=Malta), a couple of months later, gone through and added metadata to some of them (person=Susan, event=Wedding Reception). 3 months later, I want to see a directory containing those that were initially added and metadata'd(?) with \"location=Malta\" and not touched since, and another showing those that had gotten additional metadata so I know which ones I should be looking at.
-"""]]
diff --git a/doc/todo/wishlist:_metadata_metadata_view/comment_3_797e6578c60d8e2ed1f61a8d6403575f._comment b/doc/todo/wishlist:_metadata_metadata_view/comment_3_797e6578c60d8e2ed1f61a8d6403575f._comment
deleted file mode 100644
index aff5afbcf..000000000
--- a/doc/todo/wishlist:_metadata_metadata_view/comment_3_797e6578c60d8e2ed1f61a8d6403575f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.102"
- subject="comment 3"
- date="2014-03-19T23:14:24Z"
- content="""
-I added a toplevel \"lastchanged\" that applies to all the fields. (Also when the last change was unsetting a field, the toplevel lastchanged will show the time of that which is otherwise not visible by collecting the lastchanged-* fields).
-"""]]
diff --git a/doc/todo/wishlist:_metadata_metadata_view/comment_4_d271fe711b3fe5ffeb52f1caf44622b3._comment b/doc/todo/wishlist:_metadata_metadata_view/comment_4_d271fe711b3fe5ffeb52f1caf44622b3._comment
deleted file mode 100644
index 4bc147c4e..000000000
--- a/doc/todo/wishlist:_metadata_metadata_view/comment_4_d271fe711b3fe5ffeb52f1caf44622b3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="Xyem"
- ip="87.194.19.134"
- subject="comment 4"
- date="2014-03-20T08:14:20Z"
- content="""
-Awesome! :)
-
-Thank you for adding this, I hope others find it as useful as I will.
-"""]]
diff --git a/doc/todo/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn b/doc/todo/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn
deleted file mode 100644
index 8b6350a55..000000000
--- a/doc/todo/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn
+++ /dev/null
@@ -1,55 +0,0 @@
-as of git-annex version 3.20110719, all git-annex commits only contain the word "update" as a commit message. given that the contents of the commit are pretty non-descriptive (SHA1 hashes for file names, uuids for repository names), i suggest to have more descriptive commit messages, as shown here:
-
-    /mnt/usb_disk/photos/2011$ git annex get
-    /mnt/usb_disk/photos/2011$ git show git-annex
-    [...]
-    usb-disk-photos: get 2011
-    
-    * 10 files retrieved from 2 sources (9 from local-harddisk, 1 from my-server)
-    * 120 files were already present
-    * 2 files could not be retrieved
-    /mnt/usb_disk/photos/2011$ cd ~/photos/2011/07
-    ~/photos/2011/07$ git copy --to my-server
-    ~/photos/2011/07$ git show git-annex
-    [...]
-    local-harddisk: copy 2011/07 to my-server
-    
-    * 20 files pushed
-    ~/photos/2011/07$
-
-in my opinion, the messages should at least contain
-
-* what command was used
-* in which repository they were executed
-* which files or directories they affected (not necessarily all files, but what was given on command line or implicitly from the working directory)
-
---[[chrysn]]
-
-> The implementation of the git-annex branch precludes more descriptive
-> commit messages, since a single commit can include changes that were
-> previously staged to the branch's index file, or spooled to its journal
-> by other git-annex commands (either concurrently running or
-> interrupted commands, or even changes needed to automatically merge
-> other git-annex branches).
-> 
-> It would be possible to make it *less* verbose, with an empty commit
-> message. :) --[[Joey]] 
-
->> Closing as this is literally impossible to do without making
->> git-annex worse. [[done]] --[[Joey]] 
-
-> I'm not sure that the requested feature is that far off. There are two
-> aspects, that can be solved relatively easy:
->
->  * Recording the name of the remote the commit was issued on. This
->    information is simply constant per remote.
->
->  * While it is true that there is no 1 on 1 correspondence between commands
->    and git-annex commits, it would be entirely possible to add a "message
->    journal". Every command issued would start out with writing its
->    invocation to the message journal. At the time the journal ends up being
->    committed to the git-annex branch, the message journal is used as the
->    body of the commit message and truncated.
->
-> It is true that these suggestions do not address every aspect of the
-> original report, but they would solve about 90%. --[[HelmutGrohne]]
diff --git a/doc/todo/wishlist:_option_to_disable_url_checking_with_addurl.mdwn b/doc/todo/wishlist:_option_to_disable_url_checking_with_addurl.mdwn
deleted file mode 100644
index d0b847933..000000000
--- a/doc/todo/wishlist:_option_to_disable_url_checking_with_addurl.mdwn
+++ /dev/null
@@ -1,9 +0,0 @@
-I'm testing out an idea of using filter-branch on a git repository to both retroactively annex and AND record a weburl for all relevant files.
-
-c.f. [http://git-annex.branchable.com/tips/How_to_retroactively_annex_a_file_already_in_a_git_repo/](http://git-annex.branchable.com/tips/How_to_retroactively_annex_a_file_already_in_a_git_repo/)
-
-The bottleneck I'm hitting here seems to be the fact that `git annex addurl` diligently checks each url to see that it is accessible, which adds up quickly if many files are to be processed.
-
-It would be great if addurl had an option to disable checking the url, in order to speed up large batch jobs like this.
-
-> --relaxed added [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_option_to_disable_url_checking_with_addurl/comment_1_868a380faa1e55faa3c2d314e3258e86._comment b/doc/todo/wishlist:_option_to_disable_url_checking_with_addurl/comment_1_868a380faa1e55faa3c2d314e3258e86._comment
deleted file mode 100644
index 4bdf4c97b..000000000
--- a/doc/todo/wishlist:_option_to_disable_url_checking_with_addurl/comment_1_868a380faa1e55faa3c2d314e3258e86._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- nickname="joey"
- subject="comment 1"
- date="2013-03-11T18:19:34Z"
- content="""
-It does this to get the size of the url, so it can record this in the key. It would be possible to add a flag to skip that (--fast is already taken of course), but then you tend to get a lot of keys in your repository with no size info attached, which makes `git annex status` complain that it cannot tell you exactly how big your repo is, and is generally not the best. It also defeats annex.diskreserve checking, for example.
-
-With --fast, the size is the only info available to ensure that the content behind the url has not changed when downloading it later. I suppose for some urls you may not want that checked, and so a --relaxed type option could make sense in that use case as well, although with the above caveat.
-"""]]
diff --git a/doc/todo/wishlist:_push_to_cia.vc_from_the_website__39__s_repo__44___not_your_personal_one.mdwn b/doc/todo/wishlist:_push_to_cia.vc_from_the_website__39__s_repo__44___not_your_personal_one.mdwn
deleted file mode 100644
index f9b4c8c35..000000000
--- a/doc/todo/wishlist:_push_to_cia.vc_from_the_website__39__s_repo__44___not_your_personal_one.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-I just added a CIA bot to #vcs-home and tracking commits immediately would be nice. -- RichiH
-
-[[done]]
diff --git a/doc/todo/wishlist:_push_to_cia.vc_from_the_website__39__s_repo__44___not_your_personal_one/comment_1_3480b0ec629ef29a151408d869186bf8._comment b/doc/todo/wishlist:_push_to_cia.vc_from_the_website__39__s_repo__44___not_your_personal_one/comment_1_3480b0ec629ef29a151408d869186bf8._comment
deleted file mode 100644
index 5d0edce2e..000000000
--- a/doc/todo/wishlist:_push_to_cia.vc_from_the_website__39__s_repo__44___not_your_personal_one/comment_1_3480b0ec629ef29a151408d869186bf8._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-09-19T18:57:52Z"
- content="""
-JFTR, pushing now happens automatically from branchable.
-"""]]
diff --git a/doc/todo/wishlist:_query_things_like_description__44___trust_level.mdwn b/doc/todo/wishlist:_query_things_like_description__44___trust_level.mdwn
deleted file mode 100644
index d158850cd..000000000
--- a/doc/todo/wishlist:_query_things_like_description__44___trust_level.mdwn
+++ /dev/null
@@ -1,4 +0,0 @@
-It would be helpful to have a way to query things like a repository's description and trust level, without having to poke in the git-annex branch.  For example, "git annex describe ." currently clears the description but could print the current one instead.
-
-> `git annex status` now breaks down the repository list by type. [[done]]
-> --[[Joey]] 
diff --git a/doc/todo/wishlist:_query_things_like_description__44___trust_level/comment_1_14311384788312b96e550749ab7de9ea._comment b/doc/todo/wishlist:_query_things_like_description__44___trust_level/comment_1_14311384788312b96e550749ab7de9ea._comment
deleted file mode 100644
index 3ac4ba267..000000000
--- a/doc/todo/wishlist:_query_things_like_description__44___trust_level/comment_1_14311384788312b96e550749ab7de9ea._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-10-27T17:09:33Z"
- content="""
-`git annex describe` only sets the description to avoid complication. Imagine using it in a script for example.
-
-`git annex status` shows the description. It does not show the trust level because I have not thought of a visually pleasing and compact way to show it in the repository list there.. suggestions appreciated, since the same list is used by `whereis`, and showing trust levels there would be particularly useful.
-"""]]
diff --git a/doc/todo/wishlist:_query_things_like_description__44___trust_level/comment_2_342d1ac07573c7ef4e27f003a692e261._comment b/doc/todo/wishlist:_query_things_like_description__44___trust_level/comment_2_342d1ac07573c7ef4e27f003a692e261._comment
deleted file mode 100644
index 3bb92919f..000000000
--- a/doc/todo/wishlist:_query_things_like_description__44___trust_level/comment_2_342d1ac07573c7ef4e27f003a692e261._comment
+++ /dev/null
@@ -1,32 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
- nickname="Richard"
- subject="comment 2"
- date="2011-10-29T18:28:13Z"
- content="""
-Possible solutions:
-
-This:
-
-    trusted repositories:
-            UUID -- foo
-    semi-trusted repositories:
-            UUID -- bar
-    untrusted repositories:
-            UUID -- baz
-
-or this:
-
-            UUID -- trusted      -- foo
-            UUID -- semi-trusted -- bar
-            UUID -- untrusted    -- baz
-
-or this:
-
-    known repositories (!/*/X):
-            UUID -- ! foo
-            UUID -- * bar
-            UUID -- X baz
-
-If you want to reformat this output, putting 'here', 'origin', etc into fixed formatting might make sense, as well. -- Richard
-"""]]
diff --git a/doc/todo/wishlist:_simple_url_for_webapp.mdwn b/doc/todo/wishlist:_simple_url_for_webapp.mdwn
deleted file mode 100644
index 4549f2e74..000000000
--- a/doc/todo/wishlist:_simple_url_for_webapp.mdwn
+++ /dev/null
@@ -1,36 +0,0 @@
-### Please describe the problem.
-
-The environment is os/x with chrome as the browser.
-
-Let's say I close the tab with the webapp running in it. The 'git-annex webapp' process is still running, according to 'ps'.
-
-So I open a new tab, but then what do I  type into the browser url bar to get the app back? What is usually there is a loopback address and an authorisation hash.
-
-* Should I double-click on the git-annex icon in the dock (or Applications directory)?
-* I figured out from observing the startup that if I give the url ://localhost/Users/me/annex/.git/annex/webapp.html I will get redirected to the right place.
-Should I set up a bookmark for that?
-
-### What steps will reproduce the problem?
-
-see above.
-
-### What version of git-annex are you using? On what operating system?
-
-Version: 4.20130723-ge023649 
-Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS
-os: os/x 10.8.4
-
-### Please provide any additional information below.
-
-I notice that in the webapp ui, all the items at the top of the page highlight when one hovers over them and have useful URLs attached,
-with the exception of the 'git-annex' item at the far left.What if that had the entry point url attached to it (so one could bookmark that)?
-
-> The git-annex assistant is designed to stay running in the background whether you have the web browser open or not. You can open the web display at any time by 
-> using the git-annex menu item (on linux) or running the git-annex-webapp
-> program (which is in the DMG on OSX).
-> 
-> If the file:// url were exposed to users, it would not work if 
-> the assistant had not already been started. This is why there is a program
-> to open the webapp, not an url.
-> 
-> Not a bug; [[done]] --[[Joey]] 
diff --git a/doc/todo/wishlist:_simple_url_for_webapp/comment_1_552aad504fbb68d1f85abfde8c535e69._comment b/doc/todo/wishlist:_simple_url_for_webapp/comment_1_552aad504fbb68d1f85abfde8c535e69._comment
deleted file mode 100644
index 1211be9b5..000000000
--- a/doc/todo/wishlist:_simple_url_for_webapp/comment_1_552aad504fbb68d1f85abfde8c535e69._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkfHTPsiAcHEEN7Xl7WxiZmYq-vX7azxFY"
- nickname="Vincent"
- subject="comment 1"
- date="2013-07-24T14:46:22Z"
- content="""
-typo
-
-url should be - file://localhost/Users/me/annex/.git/annex/webapp.html
-"""]]
diff --git a/doc/todo/wishlist:_simpler_gpg_usage.mdwn b/doc/todo/wishlist:_simpler_gpg_usage.mdwn
deleted file mode 100644
index 1236ee234..000000000
--- a/doc/todo/wishlist:_simpler_gpg_usage.mdwn
+++ /dev/null
@@ -1,12 +0,0 @@
-This is my current understanding on how one must use gpg with git-annex:
-
- * Generate(or copy around) a gpg key on every machine that needs to access the encrypted remote.
- * git annex initremote myremote encryption=KEY for each key that you generated
-
-What I'm trying to figure out is if I can generate a no-passphrase gpg key and commit it to the repository, and have git-annex use that. That way any new clones of the annex automatically have access to any encrypted remotes, without having to do any key management.
-
-I think I can generate a no-passphrase key, but then I still have to manually copy it around to each machine.
-
-I'm not a huge gpg user so part of this is me wanting to avoid having to manage and keeping track of the keys.  This would probably be a non-issue if I used gpg on more machines and was more comfortable with it.
-
-[[done]]
diff --git a/doc/todo/wishlist:_simpler_gpg_usage/comment_1_6923fa6ebc0bbe7d93edb1d01d7c46c5._comment b/doc/todo/wishlist:_simpler_gpg_usage/comment_1_6923fa6ebc0bbe7d93edb1d01d7c46c5._comment
deleted file mode 100644
index f96f5c377..000000000
--- a/doc/todo/wishlist:_simpler_gpg_usage/comment_1_6923fa6ebc0bbe7d93edb1d01d7c46c5._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 1"
- date="2012-04-29T01:41:57Z"
- content="""
-Thinking about this more, I think minimally git-annex could support a
-
-    remote.<name>.gpg-options
-
-or
-
-    remote.<name>.gpg-keyring
-
-for options to be passed to gpg.  I'm not sure how automatically setting it to $ANNEX_ROOT/.gnupg/.. would work.
-
-
-I need to read the encryption code to fully understand it, but I also wonder if there is not also a way to just bypass gpg entirely and store the remote-encryption keys locally in plain text.
-"""]]
diff --git a/doc/todo/wishlist:_simpler_gpg_usage/comment_2_6fc874b6c391df242bd2592c4a65eae8._comment b/doc/todo/wishlist:_simpler_gpg_usage/comment_2_6fc874b6c391df242bd2592c4a65eae8._comment
deleted file mode 100644
index 2e12d86d4..000000000
--- a/doc/todo/wishlist:_simpler_gpg_usage/comment_2_6fc874b6c391df242bd2592c4a65eae8._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2012-04-29T02:39:20Z"
- content="""
-The encryption uses a symmetric cipher that is stored in the git repository already. It's just stored encrypted to the various gpg keys that have been configured to use it. It would certainly be possible to store the symmetric cipher unencrypted in the git repo. 
-
-I don't see your idea of gpg-options saving any work. It would still require you to do key distribution and run commands in each repo to set it up.
-"""]]
diff --git a/doc/todo/wishlist:_simpler_gpg_usage/comment_3_012f340c8c572fe598fc860c1046dabd._comment b/doc/todo/wishlist:_simpler_gpg_usage/comment_3_012f340c8c572fe598fc860c1046dabd._comment
deleted file mode 100644
index 051f17a24..000000000
--- a/doc/todo/wishlist:_simpler_gpg_usage/comment_3_012f340c8c572fe598fc860c1046dabd._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 3"
- date="2012-04-29T02:41:38Z"
- content="""
-BTW re your Tweet.. I was so happy to be able to use 'c i a' in Crypto.hs. :)
-"""]]
diff --git a/doc/todo/wishlist:_simpler_gpg_usage/comment_4_e0c2a13217b795964f3b630c001661ef._comment b/doc/todo/wishlist:_simpler_gpg_usage/comment_4_e0c2a13217b795964f3b630c001661ef._comment
deleted file mode 100644
index c9e337541..000000000
--- a/doc/todo/wishlist:_simpler_gpg_usage/comment_4_e0c2a13217b795964f3b630c001661ef._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo"
- nickname="Justin"
- subject="comment 4"
- date="2012-04-29T03:09:03Z"
- content="""
-I got a good laugh out of it :-)
-
-Storing the key unencrypted would make things easier..  I think at least for my use-cases I don't require another layer of protection on top of the ssh keys that provide access to the encrypted remotes themselves.
-"""]]
diff --git a/doc/todo/wishlist:_simpler_gpg_usage/comment_5_9668b58eb71901e1db8da7db38e068ca._comment b/doc/todo/wishlist:_simpler_gpg_usage/comment_5_9668b58eb71901e1db8da7db38e068ca._comment
deleted file mode 100644
index 60b98bde5..000000000
--- a/doc/todo/wishlist:_simpler_gpg_usage/comment_5_9668b58eb71901e1db8da7db38e068ca._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 5"
- date="2012-04-29T18:04:13Z"
- content="""
-encryption=shared is now supported
-"""]]
diff --git a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote.mdwn b/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote.mdwn
deleted file mode 100644
index 229dc258b..000000000
--- a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-The [[Web special remote|special remotes/web]] could possibly be improved by detecting when URLs reference a Youtube video page and using [youtube-dl](http://rg3.github.com/youtube-dl/) instead of wget to download the page. Youtube-dl can also handle several other video sites such as vimeo.com and blip.tv, so if this idea were to be implemented, it might make sense to borrow the regular expressions that youtube-dl uses to identify video URLs. A quick grep through the youtube-dl source for the identifier _VALID_URL should find those regexes (in Python's regex format).
-
-> This is something I've thought about doing for a while.. 
-> Two things I have not figured out:
-> 
-> * Seems that this should really be user-configurable or a plugin system,
->   to handle more than just this one case.
-> * Youtube-dl breaks from time to time, I really trust these urls a lot
->   less than regular urls. Perhaps per-url trust levels are called for by
->   this.
-> 
-> --[[Joey]] 
-
-> > There's a library for this called [quvi](http://quvi.sourceforge.net/) which supports many
-> > different sites and also allows fetching the URL (as opposed to just
-> > downloading the file). It seems to me this would be the best tool
-> > for this task. One problem to consider here is that a single youtube
-> > URL may yield different file contents depending on the quality
-> > chosen. Also, it seems that the URLs guessed by quvi may be
-> > ephemeral. --[[anarcat]]
-
-> [[done]]!!! --[[Joey]]   
diff --git a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_1_1a383c30df4fb1767f13d8c670b0c0b5._comment b/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_1_1a383c30df4fb1767f13d8c670b0c0b5._comment
deleted file mode 100644
index 5569ff94a..000000000
--- a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_1_1a383c30df4fb1767f13d8c670b0c0b5._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://rmunn.myopenid.com/"
- nickname="rmunn"
- subject="comment 1"
- date="2012-06-12T15:52:35Z"
- content="""
-* One way to handle the configuration might be with regular expressions. If the URL matches regex A, handle it with downloader A' (with option set A''). If the URL matches regex B, handle it with downloader B' and option set B''. And so on. Then if nothing is matched, the default downloader is wget/curl.
-
-* In my experience, youtube-dl breakages are fixed relatively quickly; a much more serious problem from a trust standpoint is that Youtube videos often disappear. Sometimes due to a legitimate copyright claim, sometimes due to illegitimate copyright claims. (I've seen both happen). Or because the video uploader decided to upload *other* videos that violated copyright, and Youtube closed his/her account, thereby removing *all* his/her videos from the Web. Youtube is definitely an untrustworthy repository as far as \"the file will still be there later on\" is concerned. Perhaps a default trust relationship could go along with the regexes? URLs matching regex A are semitrusted, while URLs matching regex B are untrusted.
-"""]]
diff --git a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_2_81f7f893ac36c145b31f02db6a682a17._comment b/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_2_81f7f893ac36c145b31f02db6a682a17._comment
deleted file mode 100644
index a25b3c89d..000000000
--- a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_2_81f7f893ac36c145b31f02db6a682a17._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="quvi thoughts. excited!"
- date="2013-08-22T18:22:51Z"
- content="""
-Anarcat's quvi suggestion is interesting, because it seems to simplify the whole thing down to just `addurl`, which git-annex is already good at.
-
-If quvi manages to find the url that can be used to download the actual video file, without needing to run a special downloader, then all you really need, it seems, is `git annex addurl --relaxed $(quvi youtube-url)` The --relaxed will make git-annex not care if the content or size of the url's content varies in the future. Since --relaxed skips the actual download, you'd want to follow that with `git annex get`, since we don't know how long these urls will last..
-
-I suppose git-annex could, if quvi is available, make any attempt to download a web special remote url that
-matches the `quvi --support` output run the url through quvi to get the real url and download that instead. The  difficulties with this approach:
-
-* would need to read and parse `quvi --support` every time it gets an url from the web special remote? (I don't think I'd want to link with libquvi, although that would be possible, just because this is an edge thing.)
-* what it an url that had been supported stopped being supported -- we'd not want to download the raw url in that case
-* putting the quvi support here doesn't allow relaxed mode to be set when `addurl` adds the url.
-
-Maybe it would be better to keep the support in `addurl`, and record the url generated by quvi. That url would probably be more likely to break in the future, but that kind of breakage is why `git annex untrust web` is wise..
-Keeping the support in `addurl` would also let it use the title that quvi also returns to determine the filename it creates.
-"""]]
diff --git a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_3_a7e3cd68c5e5f05139151a58f358df95._comment b/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_3_a7e3cd68c5e5f05139151a58f358df95._comment
deleted file mode 100644
index c4d8cf754..000000000
--- a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_3_a7e3cd68c5e5f05139151a58f358df95._comment
+++ /dev/null
@@ -1,13 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.63"
- subject="comment 3"
- date="2013-08-22T18:44:15Z"
- content="""
-Since the quvi urls are quite likely to break as the CDNs etc change things around, maybe it would be better to somehow have addurl tag an url as needing to be downloaded with quvi. Then `git annex get` could re-run quvi to get an url to download.
-
-We could expand url syntax for this. `quvi:http://youtube.com/foo`  
-This also allows for future expansion for other similar things. 
-
-I'd be inclined to still make `addurl` automatically try quvi to see if an url is supported, rather than requiring the user fix up the url themselves. But if trying quvi turns out to be too expensive, manually specifying it in the url would also work.
-"""]]
diff --git a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_4_a57947ed257b28bbe995a68bfeb5eeaa._comment b/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_4_a57947ed257b28bbe995a68bfeb5eeaa._comment
deleted file mode 100644
index ee0ab45e7..000000000
--- a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_4_a57947ed257b28bbe995a68bfeb5eeaa._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://rmunn.myopenid.com/"
- nickname="rmunn"
- subject="comment 4"
- date="2013-08-24T15:31:36Z"
- content="""
-Either quvi or youtube-dl might be a good possibility: youtube-dl has the --get-url option (or -g for short) that outputs just the download URL (and nothing else) to stdout. So if for some reason quvi turned out not to be suitable, it wouldn't necessarily mean the idea would have to be abandoned.
-"""]]
diff --git a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_5_a0612ae05dbda7f7935be648b42b30fc._comment b/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_5_a0612ae05dbda7f7935be648b42b30fc._comment
deleted file mode 100644
index 38ac09511..000000000
--- a/doc/todo/wishlist:_special-case_handling_of_Youtube_URLs_in_Web_special_remote/comment_5_a0612ae05dbda7f7935be648b42b30fc._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://id.koumbit.net/anarcat"
- ip="72.0.72.144"
- subject="aaaaawesome!"
- date="2013-08-26T04:43:27Z"
- content="""
-wow, thanks! i am happy my little suggestion led to an actual implentation, great!
-"""]]
diff --git a/doc/todo/wishlist:_special_remote_for_sftp_or_rsync.mdwn b/doc/todo/wishlist:_special_remote_for_sftp_or_rsync.mdwn
deleted file mode 100644
index d3c855655..000000000
--- a/doc/todo/wishlist:_special_remote_for_sftp_or_rsync.mdwn
+++ /dev/null
@@ -1,28 +0,0 @@
-i think it would be useful to have a fourth kind of [[special_remotes]]
-that connects to a dumb storage using sftp or rsync. this can be emulated
-by using sshfs, but that means lots of round-trips through the system and
-is limited to platforms where sshfs is available.
-
-typical use cases are backups to storate shared between a group of people
-where each user only has limited access (sftp or rsync), when using
-[[special_remotes/bup]] is not an option.
-
-an alternative to implementing yet another special remote would be to have
-some kind of plugin system by which external programs can provide an
-interface to key-value stores (i'd implement the sftp backend myself, but
-haven't learned haskell yet).
-
-> Ask and ye [[shall receive|special_remotes/rsync]].
-> 
-> Sometimes I almost think that a generic configurable special remote that
-> just uses configured shell commands would be useful.. But there's really
-> no comparison with sitting down and writing code tuned to work with
-> a given transport like rsync, when it comes to reliability and taking
-> advantage of its abilities (like resuming). --[[Joey]]
-
->> big thanks, and bonus points for identical formats, so converting from
->> directory to rsync is just a matter of changing ``type`` from ``directory``
->> to ``rsync`` in ``.git-annex/remote.log`` and replacing the directory info
->> with ``annex-rsyncurl = <host>:<dir>`` in ``.git/config``. --[[chrysn]]
-
-[[done]]
diff --git a/doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_1_6f07d9cc92cf8b4927b3a7d1820c9140._comment b/doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_1_6f07d9cc92cf8b4927b3a7d1820c9140._comment
deleted file mode 100644
index c513ed400..000000000
--- a/doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_1_6f07d9cc92cf8b4927b3a7d1820c9140._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 1"
- date="2011-04-28T07:47:38Z"
- content="""
-+1 for a generic user configurable backend that a user can put shell commands in, which has a disclaimer such that if a user hangs themselves with misconfiguration then its their own fault :P
-
-I would love to be able to quickly plugin an irods/sector set of put/get/delete/stat(get info) commands into git-annex to access my private clouds which aren't s3 compatible.
-"""]]
diff --git a/doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_2_84e4414c88ae91c048564a2cdc2d3250._comment b/doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_2_84e4414c88ae91c048564a2cdc2d3250._comment
deleted file mode 100644
index 6243708f9..000000000
--- a/doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_2_84e4414c88ae91c048564a2cdc2d3250._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-04-28T21:22:03Z"
- content="""
-Ask and ye shalle receive with an Abbot on top: [[special_remotes/hook]]
-"""]]
diff --git a/doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_3_79de7ac44e3c0f0f5691a56d3fb88897._comment b/doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_3_79de7ac44e3c0f0f5691a56d3fb88897._comment
deleted file mode 100644
index dc21ec488..000000000
--- a/doc/todo/wishlist:_special_remote_for_sftp_or_rsync/comment_3_79de7ac44e3c0f0f5691a56d3fb88897._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus"
- nickname="Jimmy"
- subject="comment 3"
- date="2011-04-29T10:43:31Z"
- content="""
-Cool!, I just tried adding tahoe-lafs as a remote, and it wasn't too hard.
-"""]]
diff --git a/doc/todo/wishlist:_special_remote_mega.co.nz.mdwn b/doc/todo/wishlist:_special_remote_mega.co.nz.mdwn
deleted file mode 100644
index 41164084a..000000000
--- a/doc/todo/wishlist:_special_remote_mega.co.nz.mdwn
+++ /dev/null
@@ -1,3 +0,0 @@
-mega.co.nz has 50gb for free accounts. They also have an API, so I guess it wouldn't be too hard to use it as a special remote.
-
-[[done]], see [[tips/megaannex]].
diff --git a/doc/todo/wishlist:_special_remote_mega.co.nz/comment_2_6ca08ef808d4336fc42d0f279d6627b5._comment b/doc/todo/wishlist:_special_remote_mega.co.nz/comment_2_6ca08ef808d4336fc42d0f279d6627b5._comment
deleted file mode 100644
index 542b92a67..000000000
--- a/doc/todo/wishlist:_special_remote_mega.co.nz/comment_2_6ca08ef808d4336fc42d0f279d6627b5._comment
+++ /dev/null
@@ -1,44 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmLB39PC89rfGaA8SwrsnB6tbumezj-aC0"
- nickname="Tobias"
- subject="Usage of mega hook"
- date="2013-05-21T09:09:28Z"
- content="""
-megaannex
-=========
-
-Hook program for gitannex to use mega.co.nz as backend
-
-# Requirements:
-
-    requests>=0.10
-    pycrypto
-
-Credit for the mega api interface goes to: https://github.com/richardasaurus/mega.py 
-
-## Install
-Clone the git repository in your home folder.
-
-    git clone git://github.com/TobiasTheViking/megaannex.git 
-
-This should make a ~/megannex folder
-
-## Setup
-Run the program once to make an empty config file
-
-    cd ~/megaannex; python2 megaannex.py
-
-Edit the megaannex.conf file. Add your mega.co.nz username and password
-
-Note: The folder option in the megaannex.conf file isn't yet used. 
-
-## Commands for gitannex:
-
-    git config annex.mega-store-hook '/usr/bin/python2 ~/megaannex/megaannex.py store --subject $ANNEX_KEY --file $ANNEX_FILE'
-    git config annex.mega-retrieve-hook '/usr/bin/python2 ~/megaannex/megaannex.py  getfile --subject $ANNEX_KEY --file $ANNEX_FILE'
-    git config annex.mega-checkpresent-hook '/usr/bin/python2 ~/megaannex/megaannex.py fileexists --subject $ANNEX_KEY'
-    git config annex.mega-remove-hook '/usr/bin/python2 ~/megaannex/megaannex.py delete --subject $ANNEX_KEY'
-    git annex initremote mega type=hook hooktype=mega encryption=shared
-    git annex describe mega \"the mega.co.nz library\"
-
-"""]]
diff --git a/doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y.mdwn b/doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y.mdwn
deleted file mode 100644
index b4f966abb..000000000
--- a/doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-I'd like to be able to:
-
-    git annex copy --from=x --to=y .
-
-Use case (true story) follows:
-
-My desktop hard drive was filling up. I dropped some large files which are also stored (via git-annex) on my backup drive. While these aren't irreplaceable files, I'd prefer to have at least two copies of everything I've decided I care enough about to archive. Later, I get a 2nd external drive, and I:
-
-    git annex copy --to=new-external-drive .
-
-Fantastic! Now I've got everything that was important/useful enough to keep on my desktop backed up a 2nd time onto my new drive.
-
-But my new drive doesn't have a copy of any of the files I dropped from my desktop. I would like to be able to:
-
-    git annex copy --from=old-external-drive --to=new-external-drive .
-
-on my desktop, and then my new drive would have a copy of everything, and my desktop drive would still have plenty of space (ie the files I'd dropped to make space would still not be stored on the desktop).
-
-The git repos on these external drives are both bare (as in ``git init --bare``) because they are used only for backups. Thus I operate on them only as remotes from my main (desktop) repo.
-
-> I have now implemented the --all option, and it's the default when
-> running `git annex get` inside a bare repo.
-> 
-> So, the solution is to `cd` to the repository on old-external-drive,
-> and `git remote add newdrive /path/to/new/drive/repo`. Then run `git
-> annex copy --all --to newdrive` and it'll move everything.
-> 
-> Calling this [[done]] unless there are other use cases where the double
-> copy method is really needed? --[[Joey]] 
diff --git a/doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y/comment_1_cf8e0f16b723516374c95a93e4da42fc._comment b/doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y/comment_1_cf8e0f16b723516374c95a93e4da42fc._comment
deleted file mode 100644
index cee50a345..000000000
--- a/doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y/comment_1_cf8e0f16b723516374c95a93e4da42fc._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.4.193"
- subject="comment 1"
- date="2013-06-30T17:43:50Z"
- content="""
-A reasonable use case indeed.
-
-It seems to me that [[add_-all_option]] could also satisfy this use case, as then you could run `git annex get --all` in the new bare remote.
-
-That would have the benefit of not doing a double copy.
-"""]]
diff --git a/doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y/comment_2_d35359c9dd4dd4365d9a7caf695ff833._comment b/doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y/comment_2_d35359c9dd4dd4365d9a7caf695ff833._comment
deleted file mode 100644
index 8305679a3..000000000
--- a/doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y/comment_2_d35359c9dd4dd4365d9a7caf695ff833._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://jasonwoof.com/"
- nickname="JasonWoof"
- subject="thanks, good enough for now."
- date="2013-07-15T19:27:58Z"
- content="""
-the ``--all`` option works for this use case. That takes care of my problem. Thank you!
-
-I can imagine other use cases where I'd want ``--from`` and ``--to`` at once, such as:
-
-1.    same situation with my two bare external drives, but I want to only copy my audio-book collection to the new drive, and not my movies.
-
-2.    I've got a large online storage (eg rsync.net) and want copy everything from there onto my new external drive.
-
-I leave it up to your good judgement when/if this is worth doing.
-"""]]
diff --git a/doc/todo/wishlist:_support_drop__44___find_on_special_remotes.mdwn b/doc/todo/wishlist:_support_drop__44___find_on_special_remotes.mdwn
deleted file mode 100644
index 24cacbf71..000000000
--- a/doc/todo/wishlist:_support_drop__44___find_on_special_remotes.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-Currently there is no way to drop files, or list what files are available, on a special remote.
-It would be good if "git annex drop" and "git annex find" supported the --from argument.
-
-> I agree, drop should support --from.
->> [[done]] --[[Joey]] 
-> 
-> To find files *believed* to be present in a given remote, use
-> `git annex find --in remote`
-> Note that it might show out of date info, since it does not actually go
-> check the current contents of the remote. The only reason to support
-> `find --from` would be to always check, but I don't think that's needed.
-> --[[Joey]] 
-
-For commands that don't support the --from argument, it would also be nice to print an error.
-Currently running "git annex drop --from usbdrive" doesn't behave as hoped and instead drops
-all content from the local annex.
-
-> This is done now. --[[Joey]] 
diff --git a/doc/todo/wishlist:_support_drop__44___find_on_special_remotes/comment_1_f11ed642a83d965076778a162f701e84._comment b/doc/todo/wishlist:_support_drop__44___find_on_special_remotes/comment_1_f11ed642a83d965076778a162f701e84._comment
deleted file mode 100644
index 6028933b4..000000000
--- a/doc/todo/wishlist:_support_drop__44___find_on_special_remotes/comment_1_f11ed642a83d965076778a162f701e84._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-10-27T17:13:43Z"
- content="""
-Well, I don't think you mean \"special remotes\", but just any old remote (special or not).
-"""]]
diff --git a/doc/todo/wishlist:_support_for_more_ssh_urls_.mdwn b/doc/todo/wishlist:_support_for_more_ssh_urls_.mdwn
deleted file mode 100644
index 55b8120a7..000000000
--- a/doc/todo/wishlist:_support_for_more_ssh_urls_.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-git-annex does not seem to support all kinds of urls that git does.
-
-Specifically, if I have ~/bar set up on host foo:
-
-    [remote "foo"]
-    ## this one is not recognized as ssh url at all
-    #	url = foo:bar
-    ## this one makes git-annex try to access '/~/bar' literally
-    #	url = ssh://foo/~/bar
-    ## this one works
-    	url = ssh://foo/home/tv/bar
-
-> scp-style is now supported.
-
-> `~` expansions (for the user's home, or other users)
-> are somewhat tricky to support as they require running
-> code on the remote to lookup homedirs. If git-annex grows a
-> `git annex shell` that is run on the remote side
-> (something I am [[considering|todo/git-annex-shell]] for other reasons), it
-> could handle the expansions there. --[[Joey]]
-
-> Update: Now `~` expansions are supported. [[done]]
diff --git a/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository.mdwn b/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository.mdwn
deleted file mode 100644
index 33c38046e..000000000
--- a/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-It would be nice to have a simple command that can safely turn a plain directory into a git-annex direct repository.
-
-This is the use case:
-
-* I use git-annex to manage a directory full of files, including many huge files.
-* These files are also stored in an S3 repository.
-* It takes days to download those files.
-* I have another computer with a directory that contains 80% of these files.
-* I would like to turn that directory into a git-annex repository.
-* I would like to download only the 20% missing files.
-
-What I would like to have a command that turns that directory into a direct repository without dealing with the gory details I will describe later. This command could be something like
-
-    $ cd Documents
-    $ git annex setup --direct example.org:~/annex/Documents.git
-
-This command should take care of:
-
-* cloning the git repository `example.org:~/annex/Documents.git` to `.git`,
-* switching to direct mode (carefully setting up all the needed branches),
-* create symlinks _only_ for the missing files,
-* record that the existing files are present in this repository.
-
-These are just the main problems that one faces in this task; they are mostly caused by the fact that the repo is in direct mode.
-
-There are workarounds, like those sketched at <http://unix.stackexchange.com/questions/75557/init-gix-annex-additional-repo-with-existing-files>, but they are all time-consuming and fragile.
-
-> Closing since there is a documented procedure for this
-> and I don't think it can be usefully simplified to a single command. [[done]] --[[Joey]]
diff --git a/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_1_d48a98bad77400bd8384300e324d999f._comment b/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_1_d48a98bad77400bd8384300e324d999f._comment
deleted file mode 100644
index ff173347f..000000000
--- a/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_1_d48a98bad77400bd8384300e324d999f._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://id.koumbit.net/anarcat"
- ip="72.0.72.144"
- subject="comment 1"
- date="2014-04-25T13:28:18Z"
- content="""
-take a look at [[tips/migrating_two_seperate_disconnected_directories_to_git_annex]]. it's not a single command, granted, but it should be simple enough for your use case...
-"""]]
diff --git a/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_2_1a1d15531c74eb0cc09f81dc09d95d39._comment b/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_2_1a1d15531c74eb0cc09f81dc09d95d39._comment
deleted file mode 100644
index c250e2d22..000000000
--- a/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_2_1a1d15531c74eb0cc09f81dc09d95d39._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://svario.it/gioele"
- nickname="gioele"
- subject="comment 2"
- date="2014-04-25T19:01:06Z"
- content="""
-That guide does not work for direct repositories. As soon as you switch to direct mode you cannot import the old data without jumping through hoops.
-
-The fact that these guide exist at all is a symptom that this is a widespread problem. Having a command in `git-annex` would be very handy and easy to use.
-"""]]
diff --git a/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_3_66ceb7c793a2dbbd755b9595a2199aca._comment b/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_3_66ceb7c793a2dbbd755b9595a2199aca._comment
deleted file mode 100644
index fbc52c5e2..000000000
--- a/doc/todo/wishlist:_turn_a_directory_into_a_git-annex_direct_repository/comment_3_66ceb7c793a2dbbd755b9595a2199aca._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.114"
- subject="comment 3"
- date="2014-04-27T00:05:58Z"
- content="""
-I don't see a single thing that direct mode makes harder in this situation. Every command in the linked tip will work in direct mode AFAICS.
-"""]]
diff --git a/doc/todo/wishlist:_vicfg_possible_repo_group_names.mdwn b/doc/todo/wishlist:_vicfg_possible_repo_group_names.mdwn
deleted file mode 100644
index e30cc619a..000000000
--- a/doc/todo/wishlist:_vicfg_possible_repo_group_names.mdwn
+++ /dev/null
@@ -1,16 +0,0 @@
-git annex vicfg should display valid repository group names
-
-For trust levels the possible values are displayed:
-
-    # Repository trust configuration
-    # (Valid trust levels: trusted semitrusted untrusted dead)
-    ...
-
-The same is not currently done for repository groups
- 
-    # Repository groups
-    # (Separate group names with spaces)
-
-Thanks.
-
-> [[done]] --[[Joey]]
-- 
cgit v1.2.3