summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawmFgsNxmnGznb5bbmcoWhoQOoxZZ-io61s <Thomas@web>2011-03-03 10:31:47 +0000
committerGravatar admin <admin@branchable.com>2011-03-03 10:31:47 +0000
commitf9da8625003b29ec47baaed272bca1c772186b10 (patch)
treead3abcc4814027145ddc47bb410feb4be8bf8f3b
parent6206b46e60803b9d15c08062780d153ebfe4a9ca (diff)
-rw-r--r--doc/bugs/git_annex_unused_seems_to_check_for_current_path.mdwn21
1 files changed, 21 insertions, 0 deletions
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
new file mode 100644
index 000000000..14caee022
--- /dev/null
+++ b/doc/bugs/git_annex_unused_seems_to_check_for_current_path.mdwn
@@ -0,0 +1,21 @@
+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