From 556b7b7785069cbbb9aa96e09c30679f1b5bc2a1 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 20 Feb 2014 19:24:09 +0000 Subject: Added a comment --- .../comment_2_d34e05f9244d3a4fcec87b3c360adb4e._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/tips/using_Amazon_Glacier/comment_2_d34e05f9244d3a4fcec87b3c360adb4e._comment (limited to 'doc/tips/using_Amazon_Glacier') diff --git a/doc/tips/using_Amazon_Glacier/comment_2_d34e05f9244d3a4fcec87b3c360adb4e._comment b/doc/tips/using_Amazon_Glacier/comment_2_d34e05f9244d3a4fcec87b3c360adb4e._comment new file mode 100644 index 000000000..ed482906b --- /dev/null +++ b/doc/tips/using_Amazon_Glacier/comment_2_d34e05f9244d3a4fcec87b3c360adb4e._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.172" + subject="comment 2" + date="2014-02-20T19:24:09Z" + content=""" +@greg, the only thing you might have missed is the need to use `glacier vault sync` to build a cache if enabling the glacier remote in another place. And that whole issue with it needing a local cache may mean few people are using glacier with more than one repository accessing the remote. + +However, this sounds like a bug. There is a comment in the source code that \"glacier vault create will succeed even if the vault already exists.\" .. perhaps it has changed since that was written. Or perhaps the command failed for some other reason, I don't know. +"""]] -- cgit v1.2.3