From 1f177e696891eee08b0f6633eb900486e71cb33d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 20 Jan 2016 15:17:20 -0400 Subject: respinse --- .../comment_1_09e26fdacfb5c159997671680dc95ab7._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/drop_from_special_hybrid_encryption_remote_fails/comment_1_09e26fdacfb5c159997671680dc95ab7._comment (limited to 'doc') diff --git a/doc/bugs/drop_from_special_hybrid_encryption_remote_fails/comment_1_09e26fdacfb5c159997671680dc95ab7._comment b/doc/bugs/drop_from_special_hybrid_encryption_remote_fails/comment_1_09e26fdacfb5c159997671680dc95ab7._comment new file mode 100644 index 000000000..96a96bd4f --- /dev/null +++ b/doc/bugs/drop_from_special_hybrid_encryption_remote_fails/comment_1_09e26fdacfb5c159997671680dc95ab7._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-01-20T19:14:23Z" + content=""" +What kind of special remote is this? In fact, can you just paste the output +of `git annex info thenameoftheremote` + +There are plenty of reasons that an operation like a drop can fail, +most of which are not bugs, but some kind of configuration problem, +an inaccessible remote, etc. Most or all of them should come with a +useful error message though.. +"""]] -- cgit v1.2.3