comment
authorJoey Hess <joeyh@joeyh.name>
Thu, 15 Jul 2021 15:48:12 +0000 (11:48 -0400)
committerJoey Hess <joeyh@joeyh.name>
Thu, 15 Jul 2021 15:48:12 +0000 (11:48 -0400)
doc/forum/How_to_get_encrypted_name_from_special_remote__63__/comment_1_47ce17796de422fe996f45083a6b79b0._comment [new file with mode: 0644]

diff --git a/doc/forum/How_to_get_encrypted_name_from_special_remote__63__/comment_1_47ce17796de422fe996f45083a6b79b0._comment b/doc/forum/How_to_get_encrypted_name_from_special_remote__63__/comment_1_47ce17796de422fe996f45083a6b79b0._comment
new file mode 100644 (file)
index 0000000..d26d3b9
--- /dev/null
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2021-07-15T15:44:03Z"
+ content="""
+See [[tips/Decrypting_files_in_special_remotes_without_git-annex]].
+
+But there is a glacier special remote which handles its particulars.
+It's probably possible to set up a new remote using that,
+which will access the data in your S3 remote now,
+using the method described in
+[[tips/multiple_remotes_accessing_the_same_data_store]].
+"""]]