From 60f70ee3d69e9ca633308f085fe277b90b103d21 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 7 Nov 2012 19:02:45 +0000 Subject: [PATCH] Added a comment --- ...t_1_2cfbf6693b051c758fe5efa5ee885829._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/migrated_files_not_showing_up_in_unused_list/comment_1_2cfbf6693b051c758fe5efa5ee885829._comment diff --git a/doc/bugs/migrated_files_not_showing_up_in_unused_list/comment_1_2cfbf6693b051c758fe5efa5ee885829._comment b/doc/bugs/migrated_files_not_showing_up_in_unused_list/comment_1_2cfbf6693b051c758fe5efa5ee885829._comment new file mode 100644 index 0000000000..ee5f056175 --- /dev/null +++ b/doc/bugs/migrated_files_not_showing_up_in_unused_list/comment_1_2cfbf6693b051c758fe5efa5ee885829._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.27" + subject="comment 1" + date="2012-11-07T19:02:45Z" + content=""" +Notice where it says: + +> (checking master...) (checking rose/master...) (checking x200s/master...) + +AFAICS, every one of those branches still refers to the migrated keys. For one thing, `git annex migrate` makes changes, but it doesn't commit them to master. And then you need to wait until the other remote are updated to. + +Also, there's not really any point in worrying about getting rid of migrated keys, since `git-annex migrate` hard links the new key to the old key, so the old ones don't take up any additional disk space. + +In other words: This should take care of itself as you continue to use the repository. +"""]]