From c66b318c8a30edfc0dd489542724e2e9add806e6 Mon Sep 17 00:00:00 2001 From: Ulrike Uhlig Date: Tue, 24 Jul 2018 11:29:18 +0200 Subject: Document connectivity issue error message Sometimes, git-remote-gcrypt reports 'gcrypt: Repository not found', but this can be due to all sorts of connectivity issues, or even due to ssh-agent using a wrong identity. This should at least be in the docs as it is a very unprecise error message. Signed-off-by: Ulrike Uhlig --- README.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.rst b/README.rst index 2e198e9..3b9d7ec 100644 --- a/README.rst +++ b/README.rst @@ -239,6 +239,9 @@ which means that your push can suddenly take significantly longer than you were expecting, as your whole history has to be reuploaded. This push might fail over a poor link. +git-remote-gcrypt might report a repository as not found when having +authentication, port, or network connectivity issues. + See also ======== -- cgit v1.2.3