diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-04-22 16:41:46 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-04-22 16:41:46 -0400 |
| commit | 3cf16ebe5ea70e79bc4e45214265009ef7b975d0 (patch) | |
| tree | d751054a064714d10ae70d75688fa1a1b3e9483f /doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn | |
| parent | afec3a563930bb402b66d4c3c4c4c9c0572b1aa1 (diff) | |
direct, indirect: Refuse to do anything when the assistant or git-annex watch daemon is running.
Diffstat (limited to 'doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn')
| -rw-r--r-- | doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn b/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn index f8d0155f6..b3b0eea64 100644 --- a/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn +++ b/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn @@ -50,3 +50,8 @@ that all three copies are stored in ~/Indirect, so the functionality I'm after s **Edit: Doing a git annex sync in ~/Indirect results in the continuing behaviour to be correct, so there's some issue telling Direct that Indirect is no longer in direct-mode?** This appears to fix it, but I guess shouldn't be necessary. + +> AFAICS, the entire problem is that the assistant does not notice when the +> repository it's running in is changed from direct to indirect mode. Since this +> has also been reported to cause problems with the assistant, I have added +> a check to prevent it from being done. [[done]] --[[Joey]] |