diff options
author | 2013-07-27 22:11:58 +0000 | |
---|---|---|
committer | 2013-07-27 22:11:58 +0000 | |
commit | 9e5a3a70d43a2d49654ec15611582d2cef40bb91 (patch) | |
tree | 25da4d0f9d7141a8edc35485e8c774b073ddac1c | |
parent | 0de0c756d2478ae86a108d4512a51cc863888038 (diff) |
-rw-r--r-- | doc/forum/how_to_decrypt_file_from_encrypted_special_remote__63__.mdwn | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/forum/how_to_decrypt_file_from_encrypted_special_remote__63__.mdwn b/doc/forum/how_to_decrypt_file_from_encrypted_special_remote__63__.mdwn new file mode 100644 index 000000000..d16131eea --- /dev/null +++ b/doc/forum/how_to_decrypt_file_from_encrypted_special_remote__63__.mdwn @@ -0,0 +1,14 @@ +I have an encrypted S3 remote with which I recently ran: + +$> git annex move . --from cloud + +which moved all my files to the local repo. When I looked at my S3 bucket, I saw some files left. I then ran: + +$> git annex unused --from cloud + +to get all the unused data. I dropped each unused data from cloud so that now I think git annex believes it has nothing on the cloud remote. + +However there is still one file left on the bucket. Is this normal? (if not I'll create a bug report) +More importantly, how can I decrypt this file so I can run git log -S'KEY' to figure out what it is (I want to make sure I haven't lost any data). + +To be clear, when I currently run 'git annex move . --from cloud' it moves nothing and when I run 'git annex unused --from cloud' it reports no unused data. |