From fed72e0e8e651313f0a14c5b5d2ae9859eba7063 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 26 Feb 2020 15:24:12 -0400 Subject: [PATCH] comment --- ...mment_2_9f75b01a1283784fb10d74c7f4c7d54e._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/gcrypt_special_remote_not_working/comment_2_9f75b01a1283784fb10d74c7f4c7d54e._comment diff --git a/doc/bugs/gcrypt_special_remote_not_working/comment_2_9f75b01a1283784fb10d74c7f4c7d54e._comment b/doc/bugs/gcrypt_special_remote_not_working/comment_2_9f75b01a1283784fb10d74c7f4c7d54e._comment new file mode 100644 index 0000000000..b628473e6f --- /dev/null +++ b/doc/bugs/gcrypt_special_remote_not_working/comment_2_9f75b01a1283784fb10d74c7f4c7d54e._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2020-02-26T19:18:09Z" + content=""" +encrypted git-lfs remotes are also affected. + +The cause is that Remote.Git is used for all remotes with an url, which +both of these have, and internally dispatches to generate them. But that +means that the configParser from Remote.Git gets used for them, and it does +not include the encryption fields. +"""]]