summaryrefslogtreecommitdiff
path: root/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment')
-rw-r--r--doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment16
1 files changed, 0 insertions, 16 deletions
diff --git a/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment b/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment
deleted file mode 100644
index e89861730..000000000
--- a/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="joey"
- subject="""comment 1"""
- date="2016-06-02T17:10:48Z"
- content="""
-What's going on here is, you have cloned a gcrypt repository so have it as
-the origin remote. git-annex is storing files in that remote as if it were
-a regular git remote. It's not being used as a special remote at all.
-
-This is surely a bug; git-annex should notice that remote has a gcrypt-id
-and treat it as a gcrypt remote, or refuse to use it since it's not set up
-as a special remote.
-
-It also seems that only git annex sync --content behaves this way;
-git annex copy "cannot determine uuid for origin".
-"""]]