summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-11-17 18:20:06 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-11-17 18:20:06 -0400
commit8b892901a98421b9b70c131bcc7af3a5e2ce62d9 (patch)
treea220b1e2cb9f87a3c757f4287447b60e6f6e2c25
parent4f6ca37b27885e570694dc4b02fd5c56334abd04 (diff)
analysis; not a bug but a feature
-rw-r--r--doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn8
1 files changed, 8 insertions, 0 deletions
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
index 322c354a2..9d1bbc4e0 100644
--- a/doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn
+++ b/doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn
@@ -45,3 +45,11 @@ Output:
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]]