From a153a694f45b8fbbe43af2c64b28624f0962f235 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Thu, 2 May 2019 16:04:06 +0000 Subject: [PATCH] Added a comment --- ...omment_30_db7e1e3506cf7a912cf88ffe4caea20b._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/special_remotes/S3/comment_30_db7e1e3506cf7a912cf88ffe4caea20b._comment diff --git a/doc/special_remotes/S3/comment_30_db7e1e3506cf7a912cf88ffe4caea20b._comment b/doc/special_remotes/S3/comment_30_db7e1e3506cf7a912cf88ffe4caea20b._comment new file mode 100644 index 0000000000..1339e6f7c1 --- /dev/null +++ b/doc/special_remotes/S3/comment_30_db7e1e3506cf7a912cf88ffe4caea20b._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 30" + date="2019-05-02T16:04:05Z" + content=""" +\"When versioning is not enabled, this risks data loss\" -- maybe, add an option to always import before exporting? I don't want to enable versioning since that permanently loses the chance of dropping any objects (even if they're stored elsewhere). + +Also, versioning on S3 buckets can be suspended/resumed; not sure if git-annex uses current bucket versioning state or the remote configuration. +"""]]