summaryrefslogtreecommitdiff
path: root/doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_1_a10aaa758daee3ca0b064c60c0382ce8._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_1_a10aaa758daee3ca0b064c60c0382ce8._comment')
-rw-r--r--doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_1_a10aaa758daee3ca0b064c60c0382ce8._comment18
1 files changed, 0 insertions, 18 deletions
diff --git a/doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_1_a10aaa758daee3ca0b064c60c0382ce8._comment b/doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_1_a10aaa758daee3ca0b064c60c0382ce8._comment
deleted file mode 100644
index bc4d5e95c..000000000
--- a/doc/bugs/Support_non-default_storage_classes_with_Google_Cloud_Storage/comment_1_a10aaa758daee3ca0b064c60c0382ce8._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="joey"
- subject="""comment 1"""
- date="2015-09-17T21:09:24Z"
- content="""
-It's now possible to use storageclass=NEARLINE, when git-annex is built
-with aws-0.13.0. So, the approach of manually creating the bucket with the
-desired storage class should work now.
-
-I'm unsure if the first method, of letting git-annex create the bucket,
-will work now. Can you test? It may work now too with
-storageclass=NEARLINE. While no storage class is currently specified when
-creating the bucket (that's not in the S3 api at all); but once the bucket
-exists, with whatever storage class is default, git-annex will specify
-NEARLINE when storing objects in it. Seems a good chance this will work,
-and it'd be easier than extending the aws library with google-specific
-features.
-"""]]