From d04b7f3e1a2cc4b7de66fecb33439ff81d454439 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 14 Sep 2018 12:53:39 -0400 Subject: [PATCH] um --- ...comment_2_e4d97ac757e7da09c9c23f74177991ae._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/gcrypt__58___..but_repository_ID_is_set._Aborting./comment_2_e4d97ac757e7da09c9c23f74177991ae._comment diff --git a/doc/bugs/gcrypt__58___..but_repository_ID_is_set._Aborting./comment_2_e4d97ac757e7da09c9c23f74177991ae._comment b/doc/bugs/gcrypt__58___..but_repository_ID_is_set._Aborting./comment_2_e4d97ac757e7da09c9c23f74177991ae._comment new file mode 100644 index 0000000000..c103ce3842 --- /dev/null +++ b/doc/bugs/gcrypt__58___..but_repository_ID_is_set._Aborting./comment_2_e4d97ac757e7da09c9c23f74177991ae._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2018-09-14T16:52:56Z" + content=""" +This is gcrypt displaying an error message, not git-annex. + +Do you have any indication it's somehow a git-annex bug? The obvious guess +would be that it's a gcrypt bug. +"""]]