summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-03 13:37:46 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-03 13:37:46 -0400
commit7ea9f52c2859a72f8e46522338c1c8a112549d84 (patch)
tree83daca33c57428bce52f09136e18b595b0805d17 /doc
parentf93b8a66971b9a8cb036258e14da6614264c800d (diff)
cannot be broken symlinks after all.. one other idea
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/git_annex_unused_seems_to_check_for_current_path.mdwn15
1 files changed, 10 insertions, 5 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
index ff318d616..df0fb50cc 100644
--- 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
@@ -25,8 +25,13 @@ I am using git-annex version 836e71297b8e3b5bd6f89f7eb1198f59af985b0b
> 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. The only way I could explain
-> what you show above is if "Software" were a separate git repository
-> than "~/annex". Or if the symlinks to the content are somehow broken
-> when looked at from within Software, but unbroken when looked at from the
-> parent directory. I can't think how that would happen. --[[Joey]]
+> 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]]