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 <ulrike@debian.org>

diff --git a/README.rst b/README.rst
index 2e198e990880fc1eec21e67b50f0d0abf60d8056..3b9d7ec21e2bda634a08165213e23202efc98bfa 100644 (file)
--- 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
 ========