summaryrefslogtreecommitdiff
path: root/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-06-02 13:20:14 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-06-02 13:20:14 -0400
commit596a2eb0508123a73fdb035b841b8e8b79231b27 (patch)
tree3c15828b9a5ce06097c1b9aae8048355030a3166 /doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment
parent0d555aa363482ed041db2d9c63da271ba7f4ced8 (diff)
analysis
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, 16 insertions, 0 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
new file mode 100644
index 000000000..e89861730
--- /dev/null
+++ b/doc/bugs/gcrypt_special_remote_not_being_encrypted/comment_1_ec3cf082ed27b7cb3ce4ba42f8e1dc10._comment
@@ -0,0 +1,16 @@
+[[!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".
+"""]]