cannot be broken symlinks after all.. one other idea
This commit is contained in:
parent
f93b8a6697
commit
7ea9f52c28
1 changed files with 10 additions and 5 deletions
|
@ -25,8 +25,13 @@ I am using git-annex version 836e71297b8e3b5bd6f89f7eb1198f59af985b0b
|
||||||
> But, git annex unused absolutely does not let the current directory
|
> But, git annex unused absolutely does not let the current directory
|
||||||
> influence what it does. It always scans the entire repo from the top.
|
> 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
|
> 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
|
> it does the same thing as at the top.
|
||||||
> what you show above is if "Software" were a separate git repository
|
>
|
||||||
> than "~/annex". Or if the symlinks to the content are somehow broken
|
> There are only two ways this could happen that I can think of:
|
||||||
> when looked at from within Software, but unbroken when looked at from the
|
>
|
||||||
> parent directory. I can't think how that would happen. --[[Joey]]
|
> 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]]
|
||||||
|
|
Loading…
Reference in a new issue