From 5747bf49b8a22cbc2b987ab34a2364e481191a44 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" Date: Sat, 13 Apr 2013 05:45:43 +0000 Subject: [PATCH] Possible fix suggested --- .../Weird_behaviour_of_direct_and_indirect_annexes.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) 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 b8d2a441d9..f8d0155f63 100644 --- a/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn +++ b/doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn @@ -27,6 +27,8 @@ Instead, it is not a symlink. However, doing results in what I would expect (until the content of Direct/Test.File is changed, when it ceases to be a symlink in ~/Indirect once more) + + ## What version of git-annex are you using? On what operating system? git-annex version: 4.20130405 @@ -44,3 +46,7 @@ It seems to me that if I do ~/Direct$ echo Even More Content > Test.File that all three copies are stored in ~/Indirect, so the functionality I'm after seems to work. However, ~/Indirect/Test.File ends up not being a symlink, which I think is odd/unexpected. + + +**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.