diff options
| -rw-r--r-- | doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn b/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn index 96d1d4d2e..bbe37a8d6 100644 --- a/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn +++ b/doc/bugs/__34__annex_sync__34___gets_confused_when_operating_in_a_symlink__39__ed_directory.mdwn @@ -16,3 +16,12 @@ OS: Archlinux Shell: zsh +> I tried to reproduce this, and it doesn't happen any longer. Tested in +> both direct and indirect mode. +> +> I think this bug was another manifestation of a bug that got fixed a +> while ago where the direct mode repository updater got confused when run +> in a subdirectory of the repository, and put files under that subdir that +> were supposed to go under the root of the repository. +> +> [[done]] --[[Joey]] |