diff options
author | 2011-03-28 11:14:13 -0400 | |
---|---|---|
committer | 2011-03-28 11:14:13 -0400 | |
commit | c1da4f3deda1ecf69b36a32af6fb94886065746c (patch) | |
tree | 09f23e1828cabd0095d9294a80ce0780018aab17 | |
parent | 659f0fe980b6bff6900037d9ae52024b989613e1 (diff) | |
parent | fc363b9ca39f264566ec9299358f201c348b792a (diff) |
Merge remote-tracking branch 'branchable/master'
-rw-r--r-- | doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn b/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn index 1eebd9ecd..122224a8f 100644 --- a/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn +++ b/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn @@ -59,3 +59,14 @@ Running the copy job again, I am still getting the same error as above (as expec >>>> This should be fixed in current git. The scambled keys will be >>>> fixed up on upgrade. Thanks for your patience! [[done]] --[[Joey]] + +>>>>> I should stop reading your answers via git; by the time I got to +>>>>> "second thoughts", I had already deleted the files & directories +>>>>> in question, upgraded the bare repo and was busy uploading from my +>>>>> local repo. I agree that taking care of this in the upgrade code +>>>>> is the cleanest approach, by the way. +>>>>> No need to thank me for my patience; thank you for your quickness! +>>>>> RichiH +>>>>> +>>>>> PS: If I get a handle on the mtime issue in the SHA backend, git +>>>>> annex will be pretty much perfect :) |