summaryrefslogtreecommitdiff
path: root/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-05-19 16:28:01 +0000
committerGravatar admin <admin@branchable.com>2014-05-19 16:28:01 +0000
commitd56fa9fef66a8cff679b4c2908d5fc99bcbdcd56 (patch)
tree3549a633dd58365a3f310b87566f37382ff3fa9e /doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids
parentc8c968f591bf3189ada96f4d6614101899d494a1 (diff)
Added a comment
Diffstat (limited to 'doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids')
-rw-r--r--doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment
new file mode 100644
index 000000000..d40c435db
--- /dev/null
+++ b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="216.145.95.162"
+ subject="comment 4"
+ date="2014-05-19T16:28:01Z"
+ content="""
+I can reproduce this problem on OSX.
+
+I've only gotten as far as seeing that the gcrypt repository never gets initialized as a git repository. It has a config file, but no objects are ever pushed to it. This is why gcrypt sees no repository there in subsequent runs.
+
+This is a bug in gcrypt, so filed: <https://github.com/blake2-ppc/git-remote-gcrypt/issues/15>
+"""]]